Good fit for
- Product documentation
- API references
- Knowledge bases
This documentation heroes pattern works best when its purpose is clear in the surrounding page hierarchy.
Open experiment
A task-first documentation hero that helps visitors search, jump to core reference areas, and confirm the current release without decorative clutter.
<header class="cmp-documentation-search-hero">
<div>
<span>Documentation · v4.2</span>
<h1>What are you trying to build?</h1>
<p>
Search the guides and API reference, or start with one of the common implementation paths.
</p>
</div>
<form role="search">
<label for="cmp-doc-search">Search documentation</label>
<div>
<input
id="cmp-doc-search"
name="query"
type="search"
placeholder="Try “authentication”"
autocomplete="off"
/><button type="submit">Search</button>
</div>
<p data-status aria-live="polite">Search is ready.</p>
</form>
<nav aria-label="Popular documentation">
<a href="#quickstart">Quickstart</a><a href="#examples">Examples</a
><a href="#api">API reference</a><a href="#migration">Migration guide</a>
</nav>
</header>
Validated in the lab
License: MIT License for open-source use, modification, and distribution.
Implementation field notes
The preview and source are only the starting point. Use these notes to decide where the component fits, preserve its accessibility contract, and verify the adapted result.
This documentation heroes pattern works best when its purpose is clear in the surrounding page hierarchy.
Related learning