feat(nav): reshape Getting Started around Agent Setup, Use Cases and Support - #2400
Merged
marcus-souza-azion merged 1 commit intoOct 1, 2026
Conversation
marcus-souza-azion
added this pull request to stack #2401
October 1, 2026 16:27
Base automatically changed from
fix/new-navigation-1-fundamentals
to
release/new-azion-docs
October 1, 2026 16:37
marcus-souza-azion
requested review from
bruno-andrade-azion,
isaque-bock-azion and
pedro-ribeiro-azion
as code owners
October 1, 2026 16:37
…Support Getting Started gains an Overview row for the docs home, Support moves under Agent Setup, Architectures becomes Use Cases with one dropdown per Solution, the Developer tools hub opens from its top-nav trigger, and the home's Copy prompt button shows the agent marks. Squashed from: - feat(nav): open the Developer tools hub from its top-nav trigger, drop its sidebar row The Developer tools trigger keeps its hover panel and now visits the hub when clicked. webkit's NavigationMenu.Trigger is either a link or a panel opener, never both, so the visit is a click handler on the button. topnav.json names the hub tree as devtoolsHome, which gives the trigger its destination and adds an Overview row to the mobile directory. The hub's row leaves root.json, and the machine index lists the hub through the top nav, as it already did for the guides hub, so llms.txt keeps it. - feat(nav): move Support into Getting Started, under Agent Setup The row leaves the Manage group, so the machine index now files Support's pages under Getting Started as well. - feat(nav): rename Architectures to Use Cases and list it under Agent Setup The tree title, the root sidebar row, the docs home card, the hub hero and directory strings, the hub pages' frontmatter and the style guide's hub example all name the section Use Cases. URLs, the tree id and the namespace stay as they are. - feat(nav): fold each Use Cases Solution into a dropdown row The five labeled groups become dropdown rows in one group, the shape the guides tree uses; each row keeps its URL segment, so every computed permalink is unchanged. The hub page builds its card sections from labeled groups, so it now reads dropdown rows as sections too. - feat(use-cases): drop the Deploy a template action from the hub hero The hero keeps its title and description only; the hero type no longer borrows the Developer tools shape, and the markdown twin stops printing the link. - feat(nav): add an Overview row for the docs home to Getting Started The docs home is not a content page, so a new `home` row kind resolves to the current language's docs base. The row leads the Getting Started group, opens no tree, and highlights on the home. - feat(home): show the agent marks on the Copy prompt button The webkit highlight button takes a label only, so the button is composed from the same layers the Console's copy-prompt component uses: the spinning glow, the accent base and the hover scrim, with the label followed by the Claude, Codex, Gemini and Cursor marks in mono. Same props, same clipboard behavior and copied state on the docs and devtools homes in both languages.
marcus-souza-azion
force-pushed
the
fix/new-navigation-2-getting-started
branch
from
October 1, 2026 16:37
4351276 to
090ae24
Compare
marcus-souza-azion
merged commit Oct 1, 2026
aed7ea2
into
release/new-azion-docs
5 of 8 checks passed
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
1 participant
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 & why
Stack 2 of 6. Branch
fix/new-navigation-2-getting-started, based onfix/new-navigation-1-fundamentals. Merge after PR 1.Getting Started becomes the group a new reader opens first: the docs home, agent setup, the catalogued use cases and support, in one place.
homerow kind resolves to the current language's docs base.Related issue: none
Pages affected: the Use Cases hub (EN and PT), the style guide's Navigation hubs page;
src/nav/(root.json,topnav.json,schema.ts,resolve.ts,trees/architectures.json),src/data/architectures-home/,src/data/docs-home/,src/components/webkit/{CopyPromptButton,DocsTopNav}.vue,src/components/homes/ArchitecturesHome.astro,src/util/machineIndex.ts. 19 files changed (2 English pages, 2 Portuguese, 15 code and data files).Type of change
feat)fix) — typo, broken link, wrong informationdocs) — rewrite, expansion, upkeepi18n)refactor/chore) — reviewed by UXE, no content mixed in — unticked: the Use Cases rename changes page titles and copyAuthor checklist
type(scope): summary(see GOVERNANCE.md §4)title,description,meta_tags,namespace,permalink,last_reviewed— the first five are on all four changed pages;last_reviewedis on no page in the corpus yetpnpm lint:navcheckpasses with 43 warnings, and linkcheck was not runpt-brupdated in this PR or follow-upi18nissue created: — updated in this PRpnpm build:local(build + frontmatter check) without errors — not run