Add a JSON "pseudo-API" #61
This commit fixes #22, although not precisely as stated.
The reasons are:
The last point is key IMO, because it enables
The format in which people have supplied 'releaseCycle' is not always consistent, e.g.:
For use in a build pipeline, it would be better to enforce consistency, limiting the values to
Right now, users of the API would need to know the format of the data for their specific tool before they could check it, which makes the API less useful.
By adding a 'compilation' stage, using make, it is no longer possible to create a new tool entry solely using the github web interface.
This could be fixed by adding a build pipeline like this, i.e. where the build process aborts if the change which triggered the build is a commit to the 'api' directory (otherwise the build process would go into an endless loop, since every build would result in a commit, which triggers a build).
Can you look at running this from a Jekyll hook instead?
I was planning to use the symlink approach from jekyll/jekyll#3041 (comment), but since your design calls for an unknown number of templates, this might be hard to setup with symlinks.
I still think it makes sense to provide a unified API per tool as well (alongside the per-release cycle), which is a JSON version of the complete page contents for any given tool. We can keep that for later though?