DRAFT: Docs Restructure Part 2 #115
Draft
Conversation
This file contains hidden or 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
… of nav dropdown Signed-off-by: Grace Grimwood <[email protected]>
This was referenced Apr 10, 2025
SamBarker
approved these changes
Apr 13, 2025
| permalink: /docs/archive/ | ||
| is_archive: true | ||
| --- | ||
| {% assign earliest_documented_version = site.data.kroxylicious.older_versions | last %} |
There was a problem hiding this comment.
Are we missing versions? Or is this just a belt and braces fix?
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.
Move old docs versions to an "older versions" archive page and out of the main nav dropdown menu.
New docs nav dropdown looks like this:
Archive page looks like this:
There's room in the archive page functionality to handle docs with subsections (like the v0.11.0 docs) and the addition of javadoc links if we elect to do that at some stage.
Currently in draft because I'll need to modify the release docs publishing pipeline to work with the changes to the site data structure before we merge.