[PetarStoev02]

Closes #180

Every w3-kit site looked and navigated differently. The main site, ui., docs. and registry. each had their own header, footer and styling. Subdomain routing also leaked internal paths: ui.w3-kit.com redirected to /ui, and registry links went to registry.w3-kit.com/registry/....

This PR gives all four sites one monochrome theme, with the logo's purple as the only colour, and one routing setup.

Design

• Shared colour, type, spacing and motion tokens in tokens.css, with light and dark themes.
• One header on every site: each site's own menus, plus an "Ecosystem" dropdown to switch sites. The main site's header has no section links.
• One footer on every site: each site's own link columns, then Ecosystem and Community, and the full-width wordmark.
• Landing page rebuilt. A /design reference page is added; nothing links to it.
• Components, docs and registry pages rebuilt in the same style.

Routing

• TanStack Router rewrite maps each subdomain to its route folder, so the address bar keeps clean paths. This replaces the custom server entry and the client-side replaceState hack.
• The subdomain list is defined once. The learn and design subdomains are removed.
• The apex domain is canonical. www, w3-kit.com/{ui,docs,registry}/*, learn. and design. redirect in vercel.json.
• The old guide pages on ui. (/installation, /mcp, …) redirect to docs with a 301.

Removed: the blog, the changelog, the compare page and the under-construction pages, plus the code only they used (GSAP and several unused UI primitives).

Bugs fixed along the way

• Component install command. npm's w3-kit became the recipe CLI at 0.2.0, so the old command no longer installs components. Install commands now use w3-kit@0.1.7, defined in one place.
• Registry API page. It showed getTokenAddress and getRpc, which are not exported by @w3-kit/registry. It now uses only real exports, and the example outputs come from the site's own data.
• Missing component styles. The mirrored components folder is gitignored, so Tailwind never scanned it and many component styles were missing. Fixed with an @source directive.
• Broken wallet logos. The demos used Clearbit's logo API, which no longer serves images. They now use letter marks.
• Sticky header and side menus. overflow-x-hidden stopped them sticking. Changed to overflow-x-clip.
• Docs sidebar order. It was alphabetical; it now follows reading order.
• Generated labels. Acronyms now read CLI, NFTs, DeFi, EVM and MCP instead of "Cli", "Nfts" and so on.

Review follow-ups (second commit)

• Shared frame: the header and footer now live together in widgets/site-chrome, with the nav config inside it. The header is split into a menu hook and small parts, and one SiteShell frames every site.
• One copy button: a single CopyCommand button, and each shell command is defined once.
• Data lookups: chain, token and guide lookups now live in their data modules. A missing chain or token fails with a clear error instead of crashing on undefined.
• Less duplication: one shared not-found screen, and old design tokens and unused UI primitives are removed.
• Stats: the landing stats read stable keys from the stats generator.
• Category filter: fixed two bugs the new tests caught. Both "All" and the chosen category were marked current, and an unknown ?category showed an empty grid.

CI fixes

• Type errors on main: tsc was already failing there. The Chain type now includes rpcEndpoints, and Storybook stories are no longer copied into the component mirror.
• Vercel security block: @tanstack/react-start is bumped from 1.168.20 to 1.168.61, because Vercel refuses to build 1.168.20 (CVE-2026-102989). I stayed on 1.168.x because 1.169 requires Vite 8. @tanstack/react-router is pinned to 1.170.42 so only one copy of the router is installed.

Testing

• npx playwright test: 36 passed. The landing spec covers the page, subdomain routing, header menus (Escape and outside click), the theme toggle, the catalog filter, an unknown component and the recipe tabs. The registry spec is updated for the new markup and URLs.
• npm run build, npm run typecheck, npm run lint and npm run format:check all pass. These are the same steps CI runs.

Depends on the learn repo. The new /mcp docs page needs docs/mcp.md, which is local and not yet committed in learn. In that repo the whole docs/ folder is currently untracked, so CI builds that clone learn won't have any of the docs pages. Docs text that is still wrong (the Installation and CLI pages) also lives in learn.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated
w3-kit	Ready	Preview	Oct 29, 2026 12:58pm UTC