18 lines
1.8 KiB
Plaintext
18 lines
1.8 KiB
Plaintext
page FrameworkGuidesGuide {
|
|
layout = "showcase"
|
|
seo {
|
|
title = "Framework guides"
|
|
description = "WRNexus components use native HTML semantics and framework component mounts."
|
|
}
|
|
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>Framework guides</span></nav>
|
|
<header class="docs-intro"><span class="showcase-eyebrow">Getting Started</span><h1>Framework guides</h1><p>WRNexus components use native HTML semantics and framework component mounts.</p></header>
|
|
<section class="guide-section"><h2>Mount components</h2><p>Use the component mount name directly in .wrn views. Props are typed, slots remain server-rendered, and declared outputs reach parent bindings.</p></section><section class="guide-section"><h2>Own page composition</h2><p>Keep application structure in pages and layouts. Use library components for reusable behavior, then add application-specific styles in the owning .wrn file.</p></section><section class="guide-section"><h2>Prefer semantic contracts</h2><p>Choose props, slots, and outputs over selectors that depend on a component's internal markup. This keeps applications compatible with framework upgrades.</p></section><section class="guide-section"><h2>Inspect before integrating</h2><p>Use the CLI component inspector for the exact prop, slot, and output contract, then type-check the finished page.</p></section>
|
|
<section class="guide-section"><h2>Quick start</h2><pre><code>bunx wrnexus inspect component Navbar .
|
|
bunx wrnexus typecheck .</code></pre></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>
|
|
}
|
|
}
|