A next step could be to provide a JSON file template for new contributions, but also simply for us to have a clear structure for our database!
I created a template which is clearly WIP, there isn't much yet but is simply meant to start the process! :smile:
Some notes:
the JSON format is data only, comments of the form //… or /*…*/ are not allowed. For that reason and also for readability for users (e.g. no embedded brackets), we could/should consider moving to YAML instead of JSON. This is not a lot of work, I can do that :+1: !
If comments are one of the few things that make YAML files different from JSON, while they're essentially the same, then the suggested move should be fine.
A next step could be to provide a JSON file template for new contributions, but also simply for us to have a clear structure for our database!
I created a template which is clearly WIP, there isn't much yet but is simply meant to start the process! :smile:
Some notes:
//…
or/*…*/
are not allowed. For that reason and also for readability for users (e.g. no embedded brackets), we could/should consider moving to YAML instead of JSON. This is not a lot of work, I can do that :+1: !What does everyone think about that?