Currently, the meets are stored in a JS file src/lib/db.js. This works fine, but lacks type-checking and other features (like ID uniqueness). It's also slightly irritating to open a JS file just to update a meet info. This could be eased by using a live backend database or CMS with a simple web frontend.
Ideas for the meets DB:
JSON (local file, updated via CMS, such as TinaCMS or FrontAid)
Currently, the meets are stored in a JS file
src/lib/db.js. This works fine, but lacks type-checking and other features (like ID uniqueness). It's also slightly irritating to open a JS file just to update a meet info. This could be eased by using a live backend database or CMS with a simple web frontend.Ideas for the meets DB:
Each instance would have its own DB configuration (could be file-based for a small instance, web-based DB for larger instances).
TODO extract DB modeling from
src/lib/db.jsand make a nice table with documentation describing the fields and their usage.Storages