page ThemesGuide {
  layout = "showcase"
  seo {
    title = "Themes"
    description = "Theme presets control radius, surface treatment, borders, shadows, and motion."
  }
  view {
    <article class="page-docs guide-page">
      <nav class="docs-breadcrumbs" aria-label="Breadcrumb"><a href="/docs">Docs</a><span aria-hidden="true">/</span><span>Themes</span></nav>
      <header class="docs-intro"><span class="showcase-eyebrow">Customization</span><h1>Themes</h1><p>Theme presets control radius, surface treatment, borders, shadows, and motion.</p></header>
      <section class="guide-section guide-example"><h2>Configure and use it</h2><p>This is the smallest useful starting point. Copy it into the indicated application file or run it from the project root, then adjust the documented values for your product.</p><pre><code>theme: <span>&#123;</span>
  default: "light",
  palette: "violet",
  accent: "violet",
<span>&#125;</span></code></pre><h3>What changes after this</h3><p>Only the selected theme is active while semantic tokens keep every component visually consistent.</p></section>
      <section class="guide-section"><h2>Theme anatomy</h2><p>A theme combines mode, palette, accent, radius, elevation, borders, motion, and typography. Components consume semantic tokens rather than palette-specific values.</p></section><section class="guide-section"><h2>Select only what ships</h2><p>Production pages link the active palette/accent sheet. Keep alternative themes available for user selection without placing the complete matrix on every page.</p></section><section class="guide-section"><h2>Customize globally</h2><p>Override tokens at the application boundary for brand-wide changes. Keep component-local adjustments in the owning page or component.</p></section><section class="guide-section"><h2>Validate the system</h2><p>Use the design panel to compare presets, then verify the production build's theme link and CSS report.</p></section>
      <section class="guide-section"><h2>Verify the result</h2><p>Type-check the application, inspect the resolved package and styles, and build the production artifact. Test the page at a narrow viewport, with keyboard navigation, and in both color modes before shipping.</p><pre><code>bunx wrnexus typecheck .
bunx wrnexus inspect packages .
bunx wrnexus inspect styles .
bunx wrnexus build .</code></pre><h3>Expected result</h3><p>The commands exit successfully, the build reports the installed UI components and active theme, and the rendered page remains usable before and after hydration.</p></section>
      <nav class="guide-next"><a href="/components/button">Explore components <span aria-hidden="true">→</span></a><a href="/block-library">Browse blocks <span aria-hidden="true">→</span></a></nav>
    </article>
  }
}