Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

implementation of the REST API for the event feature #14

Open
adekoder opened this issue Dec 30, 2017 · 19 comments
Open

implementation of the REST API for the event feature #14

adekoder opened this issue Dec 30, 2017 · 19 comments
Assignees

Comments

@adekoder
Copy link

No description provided.

@adekoder
Copy link
Author

i created this issue so that we can discuss how we plan on implementing this feature , also to decide the kind of data we will be collecting

@adekoder
Copy link
Author

@wolejnr i need you here

@gbozee
Copy link

gbozee commented Dec 30, 2017

great. let me add the other assignees at the side.

@gbozee
Copy link

gbozee commented Dec 30, 2017

take a look at https://djangogirls.org/events/ to get an idea of what you would be working on.

@adekoder
Copy link
Author

That i have done

@adekoder
Copy link
Author

we just need to finalize on the set of data we will been rendering
eg : event date , location , time etc

@wolejnr
Copy link

wolejnr commented Dec 30, 2017

I am with you @adekoder.
As regard implementation I guess we would be using gatsbyJS. Are you familiar with this?
As regards the data to be collected, we can try to spot the common things in an event such as the ones you mentioned.

eg : event date , location , time etc

I think we can split location into venue and state or what do you think?
I also think we will be needing to render About, Apply, FAQ, Be a Mentor and Partners

@adekoder
Copy link
Author

"gatsbyJS" i have no idea what it is but will do my research,
splitting the venue and state is nice
i don't know why we will need "Be a mentor"

@adekoder
Copy link
Author

i thought we are only implementing the API why do we need this "gatsbyJS"

@gbozee
Copy link

gbozee commented Dec 30, 2017

yeah its the Api you would be concerned about. That would be done in django

@adekoder
Copy link
Author

then why do we need "gatsbyJS"

@gbozee
Copy link

gbozee commented Dec 30, 2017

You are working on APIs not the frontend. It is the frontend team that needs to learn gatsbyjs. Not all part of the site would be built with django. In fact django would just be exposed as a rest Api only. We are not using the templates. Gatsby is a static generator site that ensures we are just deploying HTML and CSS and JavaScript in d end, no server to host.

The whole django setup is useful from an admin point of view not from a user/frontend view.
You could think about it that way.

@wolejnr
Copy link

wolejnr commented Dec 30, 2017

Thanks for the clarification @gbozee

@wolejnr
Copy link

wolejnr commented Dec 30, 2017

@adekoder based on your comment:

i don't know why we will need "Be a mentor"

Just a thought especially since we are trying to pattern after DjangoGirls.

@adekoder
Copy link
Author

ok, we can add it if we want, but i don't see any reason to

@wolejnr
Copy link

wolejnr commented Dec 30, 2017

So my suggestions as regards the data to be rendered for events are given as follows:

  • Event start date
  • Event end date
  • Venue
  • State (e.g. Kaduna, Kebbi etc.)
  • Event URL
  • Sponsors
  • FAQ

Check those that you agree with and include those you think should also be there.

@wolejnr
Copy link

wolejnr commented Jan 6, 2018

@adekoder Do you agree with the suggestions for data to be rendered for events??

@adekoder
Copy link
Author

adekoder commented Jan 6, 2018

sure

@gbozee
Copy link

gbozee commented Jan 8, 2018

Based on the list you gave @wolejnr There are some fields i am not sure would be required yet. Try reaching out to @shante66 for more information on what to consider here

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants