page SizingGuide {
  layout = "showcase"
  seo {
    title = "Sizing"
    description = "Compact through large scales adjust the complete component system consistently."
  }
  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>Sizing</span></nav>
      <header class="docs-intro"><span class="showcase-eyebrow">Customization</span><h1>Sizing</h1><p>Compact through large scales adjust the complete component system consistently.</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>&lt;Button size="sm"&gt;Compact action&lt;/Button&gt;
&lt;Input size="lg" label="Search" /&gt;</code></pre><h3>What changes after this</h3><p>Control size and application density remain consistent without shrinking accessible touch targets.</p></section>
      <section class="guide-section"><h2>Component size</h2><p>Use xs, sm, default, md, lg, or xl when a component needs an explicit scale. Related controls should use the same size within one task.</p></section><section class="guide-section"><h2>Interface density</h2><p>Compact, default, comfortable, and large adjust the system globally. Choose density from audience and task complexity rather than viewport alone.</p></section><section class="guide-section"><h2>Responsive composition</h2><p>Let containers, grids, columns, navigation, and sections adapt layout. Avoid shrinking touch targets to force desktop arrangements onto mobile.</p></section><section class="guide-section"><h2>Override deliberately</h2><p>Use tokens for application-wide spacing changes and component props for local intent. Measure dense tables and large marketing layouts separately.</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>
  }
}