Hero
Native controls work. Demo links and submissions stay inside this specimen. This example scrolls horizontally at this width.
Source markup
<!-- @dsCard group="Sections" height=532 -->
<!doctype html>
<html lang="en-GB">
<head>
<meta charset="utf-8">
<title>Hero</title>
<style>
/* layout of the demo state only */
.demo { max-width: 960px; margin-inline: auto; }
/* the hero is full bleed, so only the caption is inset */
.demo > .t-label { margin: 0 var(--space-sm) var(--space-2xs); }
/* The live hero pads space-2xl top and bottom. space-xl stands in here so the
card keeps its marker height. Nothing else about the hero changes. */
.demo .hero { padding-block: var(--space-xl); }
/* This card is a still. bundle.css animates the hero reticle in with reticle-lock,
so the same two declarations its prefers-reduced-motion block uses hold the mark
where the animation would end: no new values, opacity stays the 0.52 of the rule. */
.hero__reticle { animation: none; transform: translateY(-50%); }
</style>
</head>
<body>
<div class="demo">
<p class="t-label">Rest · terminal grid and amber glow behind, reticle settled</p>
<section class="hero">
<div class="hero__bg" aria-hidden="true"></div>
<svg class="reticle hero__reticle" xmlns="http://www.w3.org/2000/svg" viewBox="0 0 256 256" aria-hidden="true"><g class="mark" fill="currentColor"><path fill-rule="evenodd" d="M36,128 A92,92 0 1,0 220,128 A92,92 0 1,0 36,128 Z M59,128 A69,69 0 1,0 197,128 A69,69 0 1,0 59,128 Z"/><polygon points="89.033,105.296 32.388,48.652 32.388,32.388 48.652,32.388 105.296,89.033"/><polygon points="150.704,166.967 207.348,223.612 223.612,223.612 223.612,207.348 166.967,150.704"/><circle cx="128" cy="128" r="14"/></g></svg>
<div class="container">
<div class="hero__inner">
<p class="t-label">Network of Independent Zones</p>
<h1 class="t-display">disrupt the signal.</h1>
<p class="t-lead">Secure infrastructure for those who value privacy.</p>
<div class="hero__cta">
<a class="btn btn--primary" href="#contact">Get in touch</a>
<a class="btn btn--ghost" href="#hosting">See hosting plans</a>
</div>
<div class="hero__stats">
<div class="stat">
<span class="stat__value stat__value--bright">Hosting</span>
<span class="stat__label">Infrastructure</span>
</div>
<div class="stat">
<span class="stat__value stat__value--bright">Cybersecurity</span>
<span class="stat__label">Security</span>
</div>
<div class="stat">
<span class="stat__value stat__value--bright">Software</span>
<span class="stat__label">Services</span>
</div>
</div>
</div>
</div>
</section>
</div>
</body>
</html>
Hero is the full-width opening section of a landing page: grid and amber glow behind, the reticle to the right, the strapline, a lead sentence, the actions and a stats row.
Use it once, at the top of the page. A page needing only a title and lede takes PageHeader; a closing call takes CtaBand.
What the consumer provides
Section titled “What the consumer provides”A section.hero, an empty .hero__bg marked aria-hidden, the reticle inlined as .reticle.hero__reticle, and .hero__inner inside a .container. Inside .hero__inner: a .t-label eyebrow, one .t-display headline, a .t-lead sentence, .hero__cta with at most two buttons, and .hero__stats with two to four .stat pairs. The homepage headline is the strapline, lower case with a full stop. Every hero is amber; a sub-page names its pillar in the eyebrow.
States and their tokens
Section titled “States and their tokens”.herois relative and clipped,space-2xlabove and below..hero__bg::beforedraws the grid incolor-overlay-gridateffect-grid-pitch, masked to dissolve towards the edges..hero__bg::afteris the amber glow. Both drop to half opacity below 768px, 0.4 under reduced motion..hero__reticleiscolor-mark-lightat opacity 0.52 behind.hero__inner, monochrome and never glowing; reduced motion holds it still..hero__ctagaps atspace-sm,.hero__statsatspace-xl, tightening tospace-mdwhen the row wraps.
Accessibility
Section titled “Accessibility”- Role:
.herois a native<section>and needs no ARIA role..hero__bgand.hero__reticleare decorative and carryaria-hidden. - Name: the section takes no accessible name; the
.t-display<h1>names the page, and each action its own link text. - Keyboard: the hero itself is not interactive. Tab reaches the two
.hero__ctalinks in source order, Enter follows one; Space, Escape and the arrows do nothing. - Target size: those links are the only interactive parts.
.btnsetsmin-height: 44pxwithspace-mdinline padding, clearing the 24px floor of WCAG 2.2 SC 2.5.8;space-smkeeps them apart. - Announcement: none. Focus shows
shadow-focus-ring; nothing is live.
Do and don’t
Section titled “Do and don’t”The glow is the hero’s phosphor, and the reticle is not. Do not add .phosphor to the headline or shadow-phosphor to a resting button: the primary button earns shadow-glow-amber on hover, and that is the budget. Keep the lead to one sentence at color-semantic-text-secondary and stat values to one word. Never set the headline in color-semantic-accent-primary: .t-display stays color-semantic-text-primary, the accent on the actions.
Hand-written from themes/noiz/assets/css/components.css (.hero, .hero__bg, .hero__reticle, .hero__inner, .hero__cta, .hero__stats).