Skip to content

[skip changelog] Add missing pages to website navigation panel #2904

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

per1234
Copy link
Contributor

@per1234 per1234 commented May 1, 2025

Please check if the PR fulfills these requirements

See how to contribute

  • The PR has no duplicates (please search among the Pull Requests
    before creating one)
  • The PR follows
    our contributing guidelines
  • [N/A] Tests for the changes have been added (for bug fixes / features)
  • [N/A] Docs have been added / updated (for bug fixes / features)
  • [N/A] UPGRADING.md has been updated with a migration guide (for breaking changes)
  • [N/A] configuration.schema.json updated if new parameters are added.

What kind of change does this PR introduce?

Bug fix

What is the current behavior?

The project is supplemented by a documentation website which is generated by the MkDocs static site generator. The site contains a navigation panel which lists the available documentation pages.

Rather than being automatically generated from the contents of the docs folder, the contents of the navigation panel have been explicitly defined via the MkDocs configuration file. This means that the project contributors must remember to update the configuration file when development work results in the addition or removal of web pages.

This was not done when the config get and debug check commands were added. The web pages for those commands are generated as expected, but the missing configuration file entries means that a visitor to the website would never know of their existence, and can only access them by hacking the URL.

What is the new behavior?

Entries for all documentation pages are present in the MkDocs configuration file, which results in all pages being listed in the navigation panel of the website.

Does this PR introduce a breaking change, and is titled accordingly?

No breaking change.

The project includes a documentation website which is generated by the MkDocs static site generator. The site contains a
navigation panel which lists the available documentation pages.

Rather than being automatically generated from the contents of the `docs` folder, the contents of the navigation panel
have been explicitly defined via the MkDocs configuration file. This means that the project contributors must remember
to update the configuration file when development work results in the addition or removal of web pages.

This was not done when the `config get` and `debug check` commands were added. The web pages are generated as expected,
but the missing configuration file entries means that a visitor to the website would never know of their existence, and
could only access them by hacking the URL.

The missing entries are hereby added to the MkDocs configuration file.
@per1234 per1234 added topic: documentation Related to documentation for the project topic: infrastructure Related to project infrastructure type: imperfection Perceived defect in any part of project labels May 1, 2025
@per1234 per1234 requested a review from alessio-perugini May 1, 2025 06:30
@per1234 per1234 self-assigned this May 1, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
topic: documentation Related to documentation for the project topic: infrastructure Related to project infrastructure type: imperfection Perceived defect in any part of project
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant