Some notes so I can close a ton of tabs:

• I've opened an issue (ReadTheDocs footer not being inserted readthedocs/readthedocs.org#5702) at RTD to check whether it's a bug on their end.
• ReadTheDocs seems to inject this file into most Sphinx-based projects. Possibly the issue is that it's not done by default on mkdocs.
• mkdocs has two built-in themes (https://github.com/mkdocs/mkdocs/tree/master/mkdocs/themes) and both seem to allow for the panel: stable (RTD theme), latest (mkdocs theme)
• The RTD theme for mkdocs seems to have explicit mention of versions, while the mkdocs theme does not.
• I've forked mkdocs-material (https://github.com/effigies/mkdocs-material/tree/enh/rtd_versions) to play around with adjusting the theme.

I found a project using mkdocs-material and that has the panel: https://mapstore.readthedocs.io/

Found via geosolutions-it/MapStore2#3570, we need to add JQuery. We now get

I'm going to squash this and merge into master.

Apparently I can't push fixes to master. Here's to more changelog clutter.

I think there should be two changelogs: the repository changelog and the specification changelog. When somebody's reading the spec, what they care about is what new features are there in the specification, and absolutely not what changes were made to the build system.

IMO, the specification changelog should ONLY include [FIX] and [ENH] changes, and should strip out the tags. I also think we should be able to go in and retroactively fix the changelog to be more human friendly without our changes getting destroyed every time a PR gets merged.

+1, perhaps you can open an issue on this, because this PR will be merged soon and is a suboptimal place for discussion. Related: #164