SEP 46: Per document changelogs
This site has a changelog. Iām pretty remiss at updating it, and in many ways these proposals have made it redundant in terms of tracking major changes to the site itself. But this proposal isnāt for the site wide changelog, here Iāll be exploring whether there might be utility in have per document changelogs. Of course, most documents will, at most, a couple of small typo fixes in their lifetime, but for some documents I could see it being useful to track changes. Examples:
-
Essays. If I make a factual error in an essay and later realise my mistake and correct, I think itās an ethical requirement to announce that a change has been made to that effect (eg. a newspaper retraction). I donāt want to gaslight people by simply changing what I wrote without making it clear that the words/facts have been changes.
-
Beliefs: as my beliefs evolve/develop/change it seems to make sense to record those changes. Is a āchangelogā the right format for that? Iām not sure, but Iāll give it a go.
I think the log should be written into the frontmatter. If a change that warrants recording ā not typo fixes, think thematic changes ā is made, it could be reflected like so:
...
changelog:
- 2023-04-19 18:08:47: A previous version of this essay dated the St. Markus
quote to 1623. I have since learned that this date is in doubt so it has
been removed.
- 2022-01-30 12:49:14: The following figure, previously included in the
article, has been removed because it may have been exaggerated.
...
This changelog could then be emitted in the footer of the document, before or
after the footnotes, either in full or collapsed in a <details>
element.
Some might ask, āwhy not use version control?ā Well, I do use version control, all of this site is versioned in git and pushed to multiple remotes, but if Iām being honest I donāt enjoy git. I love it, donāt get me wrong, using git has saved my but numerous times, but I donāt love using it. My lack of love for interacting with git makes it a non-starter for me in this role.