Relevant to end users, I've added a little bit to the title of each page (that isn't in the autogenerated plugin docs section) to let readers know the last time that page was edited. I'm hoping this will help readers have a better idea if what they are reading is likely to be up to date, which has been a problem for our existing docs. You don't need to do anything different when writing, this gets updated automatically when the site builds. It looks like this:
Note for future me/other deployers - this uses the git history to work out when a file was last changed. If your build environment only does a shallow clone, all the pages will have been last modified today. You need to prefix your build command with git fetch --unshallow && to get the full git history (or the equivalent for your build platform)
Relevant to end users, I've added a little bit to the title of each page (that isn't in the autogenerated plugin docs section) to let readers know the last time that page was edited. I'm hoping this will help readers have a better idea if what they are reading is likely to be up to date, which has been a problem for our existing docs. You don't need to do anything different when writing, this gets updated automatically when the site builds. It looks like this:
Note for future me/other deployers - this uses the git history to work out when a file was last changed. If your build environment only does a shallow clone, all the pages will have been last modified today. You need to prefix your build command with
git fetch --unshallow &&to get the full git history (or the equivalent for your build platform)