Removing the stable branch and allowing RTD to build its own stable documentation has one drawback: the release version (visible under the STScI logo) is replaced with "stable". The release information is written to the HTML <title>...</title> tag, so it is technically visible to the user, but only barely.
This PR displays the release version on the index page. When the stable documentation is generated it will continue to write "stable" below the logo above the navigation pane, however, the user will not need to hunt through the page's source code to find the actual version the documentation relates to.
Resolves JP-3549
See #8299 #8633
Removing the
stablebranch and allowing RTD to build its own stable documentation has one drawback: the release version (visible under the STScI logo) is replaced with "stable". The release information is written to the HTML<title>...</title>tag, so it is technically visible to the user, but only barely.This PR displays the release version on the index page. When the stable documentation is generated it will continue to write "stable" below the logo above the navigation pane, however, the user will not need to hunt through the page's source code to find the actual version the documentation relates to.
Demo: https://jwst-pipeline--8642.org.readthedocs.build/en/8642/
Checklist for PR authors (skip items if you don't have permissions or they are not applicable)
CHANGES.rstwithin the relevant release section