fix(config): Make glossary agent-only by removing nav link#218
Merged
Conversation
The glossary is agent-only content: it is available for AI agents at https://unikraft.com/glossary.md and no longer needs a human-facing navigation entry in the docs. Remove the "Glossary" top-navigation link so the docs glossary is agent-only, consistent with the marketing site. Signed-off-by: Jerome Jaggi <jerome@unikraft.io>
jesi-rgb
approved these changes
Jul 6, 2026
jesi-rgb
left a comment
jesi-rgb
left a comment
Member
There was a problem hiding this comment.
no culture for flesh!
Reviewed-by: Jesús Rascón jesus@unikraft.io
Approved-by: Jesús Rascón jesus@unikraft.io
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
What
Removes the visible Glossary entry from the docs top navigation,
making the glossary agent-only across the site (consistent with the
marketing site, where the glossary is now published only at
/glossary.md).Why
Per the agent-readability initiative, the glossary is content meant for
AI agents to ingest — it does not need a human-facing navigation link in
the docs.
Trade-off (intentional)
The per-page
html.glossary-linka14y check was passing on docs pagesonly because of this nav link, so removing it will make that single
check fail on docs pages. This is an accepted trade-off: the glossary
remains discoverable to agents via the marketing site's
/glossary.md,llms.txt,AGENTS.mdandsitemap.md.Changes
zudoku.config.tsx.Note
Docs can't be built locally (content is pulled at Docker build time);
please sanity-check the deploy preview.