Files
WorkRoot-WRNexusJSComponent/app/pages/resources.wrn
T

23 lines
2.8 KiB
Plaintext

page ResourcesGuide {
layout = "showcase"
seo {
title = "Resources"
description = "Use the component API pages, blocks, and templates as production starting points."
}
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>Resources</span></nav>
<header class="docs-intro"><span class="showcase-eyebrow">Getting Started</span><h1>Resources</h1><p>Use the component API pages, blocks, and templates as production starting points.</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>bunx wrnexus doctor .
bunx wrnexus inspect styles .
bunx wrnexus update . --latest --dry-run</code></pre><h3>What changes after this</h3><p>You can move from component contract to composed block, diagnose ownership, and preview upgrades with supported tools.</p></section>
<section class="guide-section"><h2>Component contracts</h2><p>Each component page contains live variants, typed props, slots, outputs, copyable WRN source, behavior notes, and responsive guidance.</p></section><section class="guide-section"><h2>Blocks and templates</h2><p>Blocks demonstrate production composition patterns. Templates combine those patterns into public pages, authentication surfaces, and application dashboards.</p></section><section class="guide-section"><h2>Framework diagnostics</h2><p>Use inspect, explain, doctor, and typecheck when a component does not render or hydrate as expected. These commands expose resolved ownership rather than requiring guesswork.</p></section><section class="guide-section"><h2>Upgrade safely</h2><p>Preview framework migrations, commit the current application, apply the update, and review generated migration reports before deployment.</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>
}
}