Static landing page and footer links #19
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
|
|
Hi @reuterbal - please can you add a caveat to the link to the Python standard to indicate it isn't ready for use yet? (Or comment out that link till it is?) That's just a placeholder atm. |
msleigh
approved these changes
Feb 20, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This incorporates the changes requested by WebMOG to make the HTML websites publicly available.
It adds the static landing page that I have added to the Site root and which is currently displayed when visiting the non-language specific base url https://sites.ecmwf.int/docs/ifs-arpege-coding-standards . I figured it's useful to track this file as part of the repository even though an automatic deployment mechanism is likely unnecessary considering it's not intended to change.
I've used one of the web apps as a template, stripped java script & anything that looked unnecessary and filled-in the content. Please suggest changes to the appearance or content if required, and I will update the PR as well as the deployed version.
Furthermore, this PR adds links to terms of use, privacy statement and contact page that are placed in the footer of the generated Sphinx documentation.
Lastly, I removed the
_staticentry from the config files as this generated a build warning due to it's non-existence.