-
Notifications
You must be signed in to change notification settings - Fork 49
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
Display upcoming and past events on the website #4
Comments
Hi, I hope you're all doing great. @fatmali, I'd suggest we start by designing the data then designing the front-end (Adobe or Figma) just so we can have a common base frame. Teams would be great. |
Hi @yegow! Nice suggestions, I like them. I have a two questions:
|
@fatmali yees!!for sure,i can come up with something, i may need an extensive explanation of what needs to be implemented so as to map out the project structure |
@miami78, for now, it's just events, but it should be able to support different types of data as the need grows. |
Yes, @fatmali, to both questions, I'd be glad to. |
Hey, @miami78, could you, please, invite me on Apiary or any other API documenter you choose so that we can get started on the backend design? I would feel more confident coming up with a design if I knew what data we were displaying. |
@yegow i was thinking the same,let me create another repo for the backend,lets take backend issues there,for now, i will push a basic boilerplate for a working server n basic setups send me your email lemmie send you the swagger invitation |
Awesome, [email protected]. That's my email, @miami78. |
Do the same @miami78 |
@MarvinKweyu done |
awesome guys, swagger will also help frontend development proceed with mocked data because we'll know the structure of the data, so frontend doesn't have to wait for backend development to be completed. |
@fatmali @yegow @MarvinKweyu its done,head over to the backend repo and have a look,tell me if i have missed anything........oh and we are going to be using es6 for this,use the boilerplate as a guide |
Awesome @miami78 ! I created a team for backend, please join and we can move backend discussions there. |
Hi @fatmali , I would be grateful to join the backend team. I have followed your conversation |
@Kenchir I've added you, head over there and have a look at the repo |
Hi guys! Great to see this gaining traction :-) Can we organise a call sometime next week to discuss this? |
@fatmali i second that,set the date and we will be there |
The website needs to have information on past and upcoming events. This means we need to interact with an API that contains all of our past and upcoming events, and share this info with site visitors.
Past Events
For past events, we need basic info such as date, time, place and event pictures. It needs to be displayed on a different row from the upcoming events.
Upcoming Events
For upcoming events, we need to have info such as date, time, place including speakers.
Backend
We need to decide whether we want to build a custom backend for this, or rely existing tools/frameworks to provide us with the data we need to fetch and display this data. If we do decide to have a custom backend, we might need to decide the structure of the JSON data as well. This is very important and we need to discuss this before work on this has started.
The text was updated successfully, but these errors were encountered: