Bruce D'Arcus
Bruce D'Arcus
> I don't envision any issues besides that some YAML fields get parsed in ways that are not supported by JSON. For example, I think `key: 2020-07-12` in YAML would...
So the GitHub Action; we'd just keep the json file, and update it from the yml when it changes?
> One final option is to not keep the JSON files on the master branch, but instead have them deployed to a separate branch of outputs. This work work sort...
> Yes, but isn't document generation far off? I don't think so. We just need to add the remaining annotations to the properties; just copying and pasting mostly. To be...
One wrinkle: how we would deal with versioning in that situation? Just use the CI script to keep the "latest" up to date, and manually generate the versions? In any...
This Action even allows cross-site Pages deployment. https://github.com/marketplace/actions/deploy-to-github-pages @rmzelle - if I were to do this, where would I push the HTML file to on the website repo?
Possible there are other such examples, that would require a more general solution?
So then we'd probably want this configured in a macro at the end; no?
> Question @bdarcus: Is this about a changelog for the released version (like the linked release notes)? Or about a work in progress log? Both, per recommendation on the "keep"...
> See https://docs.citationstyles.org/en/1.0.1/release-notes.html and https://docs.citationstyles.org/en/1.0/release-notes.html for the existing changelogs. Oh wow; those are quite detailed! I was hoping if we're manually maintaining this file to just use something like this,...