Repository navigation
docs: add the Talos Containers navigation structure - #887
Draft
Iheanacho-ai wants to merge 1 commit into
Draft
Iheanacho-ai wants to merge 1 commit into
Iheanacho-ai wants to merge 1 commit into
Conversation
Contributor
Preview approval requiredThis pull request comes from a fork, so Mintlify won't build a preview until someone with write access approves commit |
Iheanacho-ai
force-pushed
the
nav-bar-containers
branch
2 times, most recently
from
October 26, 2026 15:33
9e614ee to
f2ae5b3
Compare
📋 Automated documentation review
|
Iheanacho-ai
force-pushed
the
nav-bar-containers
branch
from
October 28, 2026 15:46
f2ae5b3 to
df08754
Compare
Member
|
880 merged, so this conflicts now. Talos Containers moved under Operating system in common.yaml with Also: the description says the group goes after "Deploying and managing workloads," but it's after "Configure your Talos cluster." I'd put it after workloads, same in both versions. |
Add a "Talos Containers" group to the v1.14 and v1.15 navigation, after "Configure your Talos cluster". Add Talos Containers to the product switcher and the docs homepage as a link into that group. The pages live inside the Talos Linux versions, so the product has no navigation of its own: the generator gains an `href` field for such linked products, which Mintlify renders as a link in the switcher. A linked product is left out of product-nav.js, where its url segment would overwrite the entry of the product it links into. The pages themselves land in separate pull requests, so the nav check fails until they are combined with this branch. Part of siderolabs#881 Signed-off-by: Amarachi Iheanacho <amarachi.iheanacho@siderolabs.com>
Iheanacho-ai
force-pushed
the
nav-bar-containers
branch
from
October 29, 2026 08:29
df08754 to
14f8c11
Compare
Iheanacho-ai
marked this pull request as draft
October 29, 2026 08:55
This branch has not been deployed
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
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
Adds the Talos Containers navigation and makes the product reachable from the product switcher and the homepage.
Why
Talos Containers is documented inside the versioned Talos Linux docs, so it has no navigation of its own and no way into the product switcher.
Change
talos-v1.14.yamlandtalos-v1.15.yaml, after "Configure your Talos cluster".talos-containers.yaml, which declares Talos Containers as a linked product pointing at How Talos Containers Work.hreffield to products intools/docs-gen. A product with anhrefrenders as a link in the product switcher, and its homepage card points at the samehref. A linked product is left out ofproduct-nav.js, where its URL segment would overwrite the entry of the product it links into.common.yaml, since the card now comes from the product file.docs.jsonandindex.mdx.The pages land in separate PRs, so
validate-docs-navandbroken-linksfail on this branch alone until they are combined.Part of #881
Testing
go vetandgo testintools/docs-gen,make docs.json-local,check-missing-local,canonical-links-check, andvalidate-docs-navon this branch and on the combined branch.docs.jsonis current. On the combined branch, the only nav failure is the storage page from Talos Containers docs: Give a container storage and configuration files #884, which is not written yet.