fix+enh(sphinx): Remove dup versions in title + weird title combination + don't use latest on older docs + add real version

[joshtrichards]

☑️ Resolves #7640

• Fixes The manual should indicate on the first page which version it refers to (pdf) #7640
• Helps with Warn about non-up-to-date version on docs.nextcloud.com page #1577

Summary

• Eliminates duplicate version string appearing in HTML title (e.g. Introduction — Nextcloud latest Administration Manual latest documentation
• Replaces latest with actual version string (or branch name if it's an arbitrary branch other than master or stableXX)
• Replaces latest (for master doc builds) with upcoming to match their label on the https://docs.nextcloud.com + clearer indicate it's actually the documentation for the upcoming release of Nextcloud not necessarily the "latest"
• Eliminates long version string that was included in the User Manual's chapter names

Caveat: Unless we backport this to all published older stableXX branches, all of the old documentation will continue to say latest. Once we merge we can try seeing how far back we can backport all this... Either way it'll be better for the most recent 3 releases (and going forward).

TODO:

• Add v before version number
• Handle unknown / master
• Double check short title usage spots
• Decide whether to drop Server from the titles (like it was previously)
• Figure out why my PDF builds seem to not be using the theme

🖼️ Screenshots

Admin

Before:

html_title:

• If master: Introduction — Nextcloud latest Administration Manual latest documentation
• If stable28: Introduction — Nextcloud latest Administration Manual latest documentation
• If stable27: Introduction — Nextcloud latest Administration Manual latest documentation
• If randomBranch: Introduction — Nextcloud latest Administration Manual latest documentation

pdf:

After:

html_title:

• If master: Introduction — Nextcloud Server (upcoming) Administration Manual
• If stable28: Introduction — Nextcloud Server (28) Administration Manual
• If stable27: Introduction — Nextcloud Server (27) Administration Manual
• If randomBranch: Introduction — Nextcloud Server (randomBranch) Administration Manual`

pdf:

User

Before

html_title:

• If master: Nextcloud latest user manual introduction — Nextcloud latest User Manual latest documentation
• If stable28: Nextcloud latest user manual introduction — Nextcloud latest User Manual latest documentation
• If stable27: Nextcloud latest user manual introduction — Nextcloud latest User Manual latest documentation
• If randomBranch: Nextcloud latest user manual introduction — Nextcloud latest User Manual latest documentation

toc:

After

html_title:

• If master: Introduction — Nextcloud Server (upcoming) User Manual
• If stable28: Introduction — Nextcloud Server (28) User Manual
• If stable27: Introduction — Nextcloud Server (27) User Manual
• If randomBranch: Introduction — Nextcloud Server (randomBranch) User Manual

toc:

PDF title page:

[nickvergessen]

This is shipped as PDF file with the release, that's why we want to have the version number in there, iirc

[joshtrichards]

I don't see the PDF (at least in v27 and v28). The help page loads the HTML doc.

The version is still in the PDF - on the title page for example. It's just that now instead of always saying latest (including above) no matter what version of the doc someone is looking at - it'll say the actual version.

I can see putting it back on that particular page maybe in the first paragraph or something. But it's weird IMO to have it embedded in the ToC entry for the Introduction Chapter (even if we do make it the correct version). I can see having it in place for the "What's new" chapter maybe.

I'll re-look a bit more at it maybe tomorrow. Already took longer than planned since I hadn't messed with the PDF builds before. They're... a little weird. :)

[github-actions]

Hello there,
Thank you so much for taking the time and effort to create a pull request to our Nextcloud project.

We hope that the review process is going smooth and is helpful for you. We want to ensure your pull request is reviewed to your satisfaction. If you have a moment, our community management team would very much appreciate your feedback on your experience with this PR review process.

Your feedback is valuable to us as we continuously strive to improve our community developer experience. Please take a moment to complete our short survey by clicking on the following link: https://cloud.nextcloud.com/apps/forms/s/i9Ago4EQRZ7TWxjfmeEpPkf6

Thank you for contributing to Nextcloud and we hope to hear from you soon!