From 090ae2409e803cea456176daa9081a129cdfba44 Mon Sep 17 00:00:00 2001 From: Marcus Souza Date: Tue, 29 Sep 2026 22:13:02 -0300 Subject: [PATCH] feat(nav): reshape Getting Started around Agent Setup, Use Cases and 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. --- src/components/homes/ArchitecturesHome.astro | 8 +- src/components/webkit/CopyPromptButton.vue | 52 ++- src/components/webkit/DocsTopNav.vue | 32 +- .../en/homes/architctures/architectures.mdx | 8 +- .../style-guide/content/navigation-hubs.mdx | 2 +- .../pt-br/homes/arquiteturas/arquiteturas.mdx | 6 +- .../conteudo/hubs-de-navegacao.mdx | 2 +- src/data/architectures-home/en.ts | 14 +- src/data/architectures-home/index.ts | 1 - src/data/architectures-home/pt-br.ts | 14 +- src/data/architectures-home/types.ts | 6 +- src/data/docs-home/en.ts | 4 +- src/data/docs-home/pt-br.ts | 4 +- src/nav/resolve.ts | 20 +- src/nav/root.json | 19 +- src/nav/schema.ts | 9 +- src/nav/topnav.json | 1 + src/nav/trees/architectures.json | 326 +++++++++--------- src/util/machineIndex.ts | 2 + 19 files changed, 289 insertions(+), 241 deletions(-) diff --git a/src/components/homes/ArchitecturesHome.astro b/src/components/homes/ArchitecturesHome.astro index 8dc172e66a..1bbba8da8a 100644 --- a/src/components/homes/ArchitecturesHome.astro +++ b/src/components/homes/ArchitecturesHome.astro @@ -1,10 +1,9 @@ --- /* - The Architectures home, on the Developer tools home's anatomy: a hero with one way in - (the guides hub), then one directory whose groups and rows are the architectures tree's, + The Architectures home, on the Developer tools home's anatomy: a hero with no action, + then one directory whose groups and rows are the architectures tree's, so it always matches the rail. Each group is a Solution; each card is one architecture. */ -import Button from '@aziontech/webkit/button'; import DocCard from '@aziontech/webkit/doc-card'; import DocCardGroup from '@aziontech/webkit/doc-card-group'; import HeroTitle from '@aziontech/webkit/hero-title'; @@ -25,9 +24,6 @@ const cols = (count: number) => (count >= 4 ? 4 : count >= 3 ? 3 : 2);
-
-
diff --git a/src/components/webkit/CopyPromptButton.vue b/src/components/webkit/CopyPromptButton.vue index fd610bbc61..521c50a2a5 100644 --- a/src/components/webkit/CopyPromptButton.vue +++ b/src/components/webkit/CopyPromptButton.vue @@ -1,15 +1,50 @@