Project Build

[edm00se]

The way this project builds currently is as a static site generated from a static markdown file. I'm debating whether a collection of individual markdown files per game, brought in dynamically from category folders and stitched together into the singular readme.md file (a requirement of the awesome- repo format), from which builds the static website, would be of a better format. It also means that the static website could then be less coupled directly to the readme, without losing source data parity.

If there's an 11ty or svelte-kit template that matches up for this, that could make this whole thing easier. Alternatively a script to build the readme.md from the directory tree and its component parts would be acceptable and perhaps closer to the current site format.

[edm00se]

I saw an excellent use of 11ty as a mechanism to generate the readme from json source data. This may be tricky for the fact that it's less accessible than markdown but could carry a lot of improvement over some of the existing process. Separating categories by file would be convenient, auditing and applying schema against JSON should be easy enough as well (casting to data structure). I'm having crazy thoughts around triggering a GH Action script to generate the JSON for the PR... but that's waaay too much work for something that is meant to be a developer driven submission.

reference:
https://github.com/davatron5000/awesome-standalones/blob/main/src/readme.njk