What does this PR do?

Navigating our documentation at the present time is painful. This is partly due to violations of Diataxis, but also partly due to the random order in which things appear. Ideally, the top menu would be sorted according to weightes (as it is now) to lead the reader through the documentation in a logical progression. In contrast, the submenus would be sorted by name in order to make specific pages easier to find (this is especially useful for submenus like "reference".

Hugo orders items in the navigation bar first by weight, then by date. Since this isn't a blog, the date is not useful way to sort. That leaves weight, but it is cumbersome to need to maintain weights for tens of pages when what is desired is alphabetical sorting. This PR fixes the ordering issues.

The top menu is sorted according to weights, whereas submenus are sorted according to name

Top level menu

Submenu

PR Checklist

[ ] Have you added an explanation of what your changes do and why you'd like to include them?
[ ] Is the TravisCI build passing?
[ ] Was the CHANGELOG.md updated to reflect the changes?
[ ] Was the documentation framework updated to reflect the changes?
[ ] Have you checked that you haven't introduced any duplicate code?

Testing Checklist

[ ] Added relevant unit tests?
[ ] Do all unit tests pass?
[ ] Do all end-to-end tests pass?
[ ] Any other testing performed?

Tested by {Running the Monkey locally with relevant config/running Island/...}
[ ] If applicable, add screenshots or log transcripts of the feature working

guardicore / monkey

Fix ordering #4200

What does this PR do?

Top level menu

Submenu

PR Checklist

Testing Checklist

Codecov Report