Hero Section
A hero section is the main opening area of a page. It quickly explains the promise, who it's for, the proof, and the next action.
Name it. Build it.
Move from a rough description to a precise pattern.
Explore atlasA real example
A payroll page opens with a result-focused headline and product preview. It adds a trial button and trust signal.
Main parts
- 01Trigger or task context
- 02Primary control surface
- 03Feedback, focus, and dismissal
Use it when
Use it when a landing page must quickly explain its value and next step.
Do not use it when
Never let a huge decorative banner push the product, proof, and action off the first screen.
Name used in code
<section> + heading + primary action Before you ship
Before release, check the page structure, keyboard access, visible focus, contrast, and zoom. Also check loading, empty, error, success, cancel, and reduced-motion states.
Outcome: Use Hero Section to solve this user need without losing the current context. User context: A payroll page opens with a result-focused headline and product preview. It adds a trial button and trust signal. Recommended pattern: Hero Section. Why it fits: Use it when a landing page must quickly explain its value and next step. Do not use it when: Never let a huge decorative banner push the product, proof, and action off the first screen. Product requirements: Define the default, loading, empty, error, success, and recovery states. Keep user input. Give clear feedback after every action. Accessibility and resilience: Use semantic HTML, full keyboard access, and visible focus. Make the layout work when zoomed and support reduced motion. Follow the project’s current rules. Do not add a new UI library unless the project already uses it. Acceptance criteria: The main task works with keyboard only and at 320px width. Focus and status changes are announced. Check loading, failure, retry, cancel, and reduced-motion paths. Evidence and limits (evidence boundary): No single official standard controls the whole term. Its meaning may change across teams, platforms, or frameworks. Unknowns to confirm: Product wording, data source, analytics events, supported devices and languages, and platform limits.
Check this request
Review the current use of Hero Section. Definition: A hero section is the main opening area of a page. It quickly explains the promise, who it's for, the proof, and the next action. Release checks: Before release, check the page structure, keyboard access, visible focus, contrast, and zoom. Also check loading, empty, error, success, cancel, and reduced-motion states. Before changing code, report the evidence you found, gaps, severity, and the smallest safe fix.