Closed chromy closed 4 years ago
This is a great start! 🌈
The reason for having events as JSON is so that we can run some cron scripts to do stuff like autopost to a mailing list (if we ever have one...) We are essentially copying what LeedsJS have done here: https://github.com/LeedsJS/website/tree/master/data/events
We have a couple of additional things on top of what they have: speaker pronouns and venue information with accessibility information. We also have some stuff that we don't need to support (yet..) like youtube id and announce and ticket availability dates.
Since you started on the Pride event, which had talks, I created a branch with speaker and talk information for those events... it's extra-event-info
branch (https://github.com/QueerCodeOrg/queercodeberlin.github.io/tree/extra-event-info). Just so you can see what I think we're aiming for.
A couple of suggestions on this PR:
datetime
into date
, start_time
and end_time
url
to signup_url
Happy to merge as-is if you like, or can wait for you to make those changes?
Then we can work out next steps to integrate the speaker info. I'd suggest perhaps working on an event page and I can work on the page for each speaker?
We also need to figure out what to do about venue information (do they get a data file of their own?) and also hosts (i.e. what do we do about the breakfast event - should we have hosts pages in addition to speaker pages). Any thoughts on that?
First pass on an events page, we might want to collect data for more of the past events before landing this.
@dirv, maybe instead of putting the events data in json file under
_data
each event could be a post under_posts
? That way it might be easier to resolve #56 later.