LandingSection
LandingSectionSection rhythm Give your landing page a clear story with generous spacing, expressive headings, and responsive content.
Landing & pricingA section that tells a story
LandingSection brings a heading, supporting copy, and content together with consistent spacing. Use it for a product introduction, a feature collection, or the next chapter in your landing page. The heading sits above the content by default, so adding a card never changes where the heading belongs.
The component uses built-in spacing and typography utilities. Add your own styles through the landing-section class when your site needs a different treatment. The examples below include styling from this site's design.
This centered introduction leads into three features. columnsLg="3" gives the content three columns on large screens; smaller screens keep a single column.
Everything in its right place.
A thoughtful foundation for your next idea. Bring your content, shape the details, and make it yours.
Content with structure
Give your ideas a home with pages that are easy to write and maintain.
A consistent design
Make every detail feel connected, from the first heading to the final link.
Room to make it yours
Add the interactions your visitors need, exactly where they need them.
A clear introduction, room to breathe, and three supporting features.
<LandingSection
class="landing-section-demo"
eyebrow="BUILT TO FIT TOGETHER"
title="Everything in its right place."
subtitle="A thoughtful foundation for your next idea. Bring your content, shape the details, and make it yours."
align="center"
columnsLg="3"
tone="neutral"
variant="surface"
>
<Panel
class="landing-section-demo__feature h-full box-shadow-none"
bodyClass="d-flex flex-column align-flex-start gap-4"
variant="surfaceAlt"
>
<IconFrame name="lucide:layers" tone="accent" variant="surface"/>
<h3 class="tracking-tight text-balance fs-h5">Content with structure</h3>
<p class="m-0 text-subtle">
Give your ideas a home with pages that are easy to write and maintain.
</p>
</Panel>
<Panel
class="landing-section-demo__feature h-full box-shadow-none"
bodyClass="d-flex flex-column align-flex-start gap-4"
variant="surfaceAlt"
>
<IconFrame name="lucide:palette" tone="secondary" variant="surface"/>
<h3 class="tracking-tight text-balance fs-h5">A consistent design</h3>
<p class="m-0 text-subtle">
Make every detail feel connected, from the first heading to the final
link.
</p>
</Panel>
<Panel
class="landing-section-demo__feature h-full box-shadow-none"
bodyClass="d-flex flex-column align-flex-start gap-4"
variant="surfaceAlt"
>
<IconFrame name="lucide:mouse-pointer-2" tone="info" variant="surface"/>
<h3 class="tracking-tight text-balance fs-h5">Room to make it yours</h3>
<p class="m-0 text-subtle">
Add the interactions your visitors need, exactly where they need them.
</p>
</Panel>
</LandingSection> Put the story beside the content
Use layout="split" to place the introduction beside a visual, a product preview, or another composition. Put links in the actions slot to keep them with the heading. The section stacks when there is not enough space for both columns.
Less setup. More making.
Keep your next release moving with a clear path from the first draft to the finishing touches.
Three steps. One shared foundation.
The heading and action stay together while the supporting content gets its own space.
<LandingSection
class="landing-section-demo"
eyebrow="FROM IDEA TO SOMETHING REAL"
title="Less setup. More making."
subtitle="Keep your next release moving with a clear path from the first draft to the finishing touches."
layout="split"
alignItems="center"
tone="accent"
variant="surface"
>
<template #actions>
<BtnLink
href="/guides/"
tone="accent"
icon="lucide:arrow-right"
iconPosition="end"
>
Explore the guides
</BtnLink>
</template>
<Panel
class="landing-section-demo__workflow box-shadow-soft"
bodyClass="d-grid"
tone="neutral"
variant="surface"
>
<Flex justify="between" align="center" wrap="true">
<span class="text-eyebrow tracking-wide m-0 fs-xxs"
>YOUR NEXT RELEASE</span>
<Badge tone="success">Ready to build</Badge>
</Flex>
<div class="landing-section-demo__step d-flex align-center gap-4">
<IconFrame
name="lucide:check"
tone="success"
variant="surface"
size="sm"/>
<div class="d-grid">
<strong class="fw-600">Tell your story</strong><span>Start with the content that matters.</span>
</div>
</div>
<div class="landing-section-demo__step d-flex align-center gap-4">
<IconFrame
name="lucide:check"
tone="success"
variant="surface"
size="sm"/>
<div class="d-grid">
<strong class="fw-600">Find your rhythm</strong><span>Compose sections that work together.</span>
</div>
</div>
<div class="landing-section-demo__step d-flex align-center gap-4">
<IconFrame
name="lucide:check"
tone="success"
variant="surface"
size="sm"/>
<div class="d-grid">
<strong class="fw-600">Make it your own</strong><span>Refine the details and share your work.</span>
</div>
</div>
<p class="landing-section-demo__note m-0 lh-5 text-subtle bt-1 b-subtle">
Three steps. One shared foundation.
</p>
</Panel>
</LandingSection> Content without a heading
Omit the text props when the surrounding page already introduces the section.
Start with good foundations
Reusable components give every page a familiar structure.
Finish with your own details
Your content and ideas give the experience its character.
<LandingSection
class="landing-section-demo"
columnsLg="2"
tone="neutral"
variant="surfaceAlt"
>
<Panel
class="landing-section-demo__feature h-full box-shadow-none"
bodyClass="d-flex flex-column align-flex-start gap-4"
variant="surface"
>
<IconFrame name="lucide:layers" tone="accent" variant="surface"/>
<h3 class="tracking-tight text-balance fs-h5">
Start with good foundations
</h3>
<p class="m-0 text-subtle">
Reusable components give every page a familiar structure.
</p>
</Panel>
<Panel
class="landing-section-demo__feature h-full box-shadow-none"
bodyClass="d-flex flex-column align-flex-start gap-4"
variant="surface"
>
<IconFrame name="lucide:sparkles" tone="secondary" variant="surface"/>
<h3 class="tracking-tight text-balance fs-h5">
Finish with your own details
</h3>
<p class="m-0 text-subtle">
Your content and ideas give the experience its character.
</p>
</Panel>
</LandingSection> All ten semantic tones
The same composition in every semantic tone. Child tones are explicit where the composition owns them, including navigation actions.
neutral Build together
A shared starting point.
accent Build together
A shared starting point.
feature Build together
A shared starting point.
secondary Build together
A shared starting point.
custom Build together
A shared starting point.
ghost Build together
A shared starting point.
info Build together
A shared starting point.
success Build together
A shared starting point.
warning Build together
A shared starting point.
danger Build together
A shared starting point.
Switch the site theme to compare the same samples in both palettes.
All eighteen visual variants
Every supported variant is shown in accent, including none. Variant controls the outer treatment; nested content may use its own treatment.
solid surface Build together
A shared starting point.
surfaceAlt Build together
A shared starting point.
spotlight Build together
A shared starting point.
glass Build together
A shared starting point.
flat Build together
A shared starting point.
flatAlt Build together
A shared starting point.
flatSolid outlineFill outline Build together
A shared starting point.
subtle Build together
A shared starting point.
subtleBtn Build together
A shared starting point.
link Build together
A shared starting point.
sheen underline Build together
A shared starting point.
rail bracket Build together
A shared starting point.
none Build together
A shared starting point.
Switch the site theme to compare the same samples in both palettes.
Both variant modes
Hover these outlineFill examples to compare stateless and stateful treatments. Stateful styling adds interaction states; it does not turn a container into a button.
stateless stateful Switch the site theme to compare the same samples in both palettes.
Heading semantics and alignment
Choose the heading element to match the surrounding document. Every titleTag is rendered below with identical visual sizing; semantics and appearance are separate.
Use h1 only for a page title. Non-heading tags do not create document headings.
Grid alignment
startBuild together
More room for a supporting story.
Compare how the heading aligns.
centerBuild together
More room for a supporting story.
Compare how the heading aligns.
endBuild together
More room for a supporting story.
Compare how the heading aligns.
stretchBuild together
More room for a supporting story.
Compare how the heading aligns.
alignItems places the introduction at the start, center, or end of its supporting content, or stretches both columns.
Feature map
| Public feature | Visible example |
|---|---|
| tone, variant, variantMode | Complete galleries above, with all supported values visible together. |
| eyebrow, title, subtitle | Introduce the section with a short label, a heading, and supporting copy, or omit them for content alone. |
| titleTag | All nine supported elements are rendered in the heading-semantics comparison. |
| layout, align | Stack or split the introduction and content; align the introduction to the start or center. |
| columns, columnsLg | Set the content columns without changing the heading layout. |
| alignItems | Start, center, end, and stretch are shown together. |
| Default slot, actions slot | Place your content in the default slot and heading links in actions. |
| Native attributes and events | Pass attributes through the root; keyboard behavior belongs to the composed native controls. |
Behavior and accessibility
Use titleTag to fit the heading into the document. Content stacks on smaller screens. Both columns and columnsLg configure the content grid on large screens, with columnsLg taking precedence. The heading stays outside that grid.
API reference
LandingSection contract
Props below are the public template API. RefOrValue accepts a literal or a reactive ref; bind refs with a colon-prefixed attribute. Native attributes and events can be passed through the component root.
eyebrow
RefOrValue<string> - Default
not set
Short context above the heading, such as a category or release label.
title
RefOrValue<string> - Default
not set
Visible heading. Choose a short title that identifies the content or task.
subtitle
RefOrValue<string> - Default
not set
Supporting text beneath the title.
titleTag
RefOrValue<LandingTitleTag> - Default
h2
Heading element. Accepts h1–h6, p, div or span; invalid values fall back to h2. Match the surrounding document hierarchy.
tone
RefOrValue<SemanticTone> - Default
inherited
Semantic intent: neutral, accent, secondary, info, success, warning, danger, feature, custom or ghost. The active skin supplies the colors.
variant
RefOrValue<ComponentVariant> - Default
none
Visual treatment. Accepts solid, surface, surfaceAlt, spotlight, glass, flat, flatAlt, flatSolid, outlineFill, outline, subtle, subtleBtn, link, sheen, underline, rail, bracket or none.
variantMode
RefOrValue<ComponentVariantMode> - Default
stateless
Use stateless for content surfaces; stateful enables the treatment’s hover, focus and active styles. It does not add interaction handlers.
layout
RefOrValue<'stacked' | 'split'> - Default
stacked
Keep the introduction above the content, or place them side by side when space allows.
align
RefOrValue<'start' | 'center'> - Default
start
Align the heading, supporting copy, and actions. Content keeps its own alignment.
columns
RefOrValue<number | string> - Default
not set
Content columns on large screens, as a count or CSS track definition. Smaller screens use one column.
columnsLg
RefOrValue<number | string> - Default
columns, then 1
Content columns on large screens. Takes precedence over columns. The heading has its own space and does not count as a content column.
alignItems
RefOrValue<GridAlignItems> - Default
start
Vertical alignment of the introduction and content, and items within the content grid: stretch, start, center or end.
Composition
Default slot: cards, imagery, or other section content. actions slot: links or buttons beneath the introduction. The root is a section. Its heading and content have separate layout areas.