The technote platform uses a metadata.yaml file to provide authoritative single-sourcing of document metadata (https://sqr-000.lsst.io/#metadata-standard). One of those is the last_revised date. The problem with using this by default is that the revision date quickly gets out of sync with the Git history while a documented is being actively drafted. Solution:
- Make it so that last_revised: none causes documenteer to obtain the date from Git history instead. When a document is being ‘released’/‘archived' (or being initially ported from another format) the last_revised field can be set to a date.
- Potentially make the Git-based date smart so that revisions to ancillary files don’t affect the last_revised date of the content.