Changing the way we edit speakers ? #362
Description
I've just added myself to the baggers file (I was sure I've done that YEARS ago, but anyways).
Editing that large JS/Json file is not the best experience.
Here is my idea :
- Move from 1 file for all speakers, to 1 file per speaker, maybe as a YAML file
- Having some build that will get all these YAML files and compile them to 1 JavaScript file
- Future : check that the YAML file is well formatted, check that the city is in the cities list (and fail the build if no)
- Future future : Having a build that ping speakers if they have "stale" listing asking them to update it.
I'm understanding that you need to publish in gh-pages something that can be served as a static content over data.brownbaglunch.fr, and I'm pretty sure we can figure it out :).
Would you be something useful? If so, I can dedicate some time to work on it :)