You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'd propose to have one single document per speaker for example, may be we can also introduce subdirs per main city and have a structure like:
/_settings/ // Contains all json settings if any
/_city/ // Contains one file per city
/_speaker/paris/ // Contains one file per speaker
/_speaker/montreal/ // Contains one file per speaker
/_speaker/nantes/ // Contains one file per speaker
Then either try to automatically load the JSON docs (which is hard IIRC) or include all of them in a central json doc:
/baggers.js
WDYT?
The text was updated successfully, but these errors were encountered:
I'm all up for having a single file per bagger, but maybe not have them separated in folders per city. Some baggers are available in multiple town which would mean duplicating the files.
Maybe you could have a json per city referencing a speaker name, that way a speaker could register themself on severall cities
Oh it's just about regrouping files in a tree structure, so I could have my json file under /_speakers/paris/ but still list Lyon and Marseilles in my json. Makes sens thanks for the explanation 👍
We need to do some cleanup as asked in https://twitter.com/cyril_lakech/status/808233862455246848.
I'd propose to have one single document per speaker for example, may be we can also introduce subdirs per main city and have a structure like:
Then either try to automatically load the JSON docs (which is hard IIRC) or include all of them in a central json doc:
WDYT?
The text was updated successfully, but these errors were encountered: