Once UI Handbook
Beginner Guides
What is Once UI?
Install & config
Page skeleton
Your first page
Build And Launch
How to launch a portfolio site that actually gets you hired
How to build a documentation site with MDX and Next.js
How to ship a landing page and dashboard with authentication in Next.js
How to launch a social app with Next.js and Supabase
Vibe Coding
Introduction to vibe coding
Set up your local dev environment
Essential tools for vibe coding
Build your first Once UI app
Common Patterns
Hero section
Static panel
Form layout
Highlighted card
Responsive stacking
Decoration layers
Dialog & modal
Toast & feedback
Tables & lists
Loading states
App shell navigation
Dashboard & charts
Chat & messaging
Auth & verification
Settings & split panels
Data filters & toolbar
Command palette
Pricing & plans
Accordion & FAQ
Media & uploads
Empty & error states
SEO, Open Graph, and structured data
Documentation code blocks with live preview
Carousels, galleries, and before/after comparisons
Date pickers and scheduling
Context menus and dropdown actions
Tags, chips, and multi-value inputs
Roadmap & kanban
Form inputs & controls
Progress, status & badges
Scrolling & feeds
Profile, avatars & identity
Social proof & logo clouds
Masonry & media grids
Table pagination, search & bulk selection
Banners & announcements
Footer layouts
Onboarding & first run
Waitlist & coming soon
Design Tips
Color & surfaces
Harness overview
Row, Column & Grid
Spacing & rhythm
Icons & buttons
Reveal & motion
Theme tokens, FOUC-free init, and runtime style controls
Tooltips and hover cards
Block updates
Block updates changelog
Agent Resources
Column, not Flex
Semantics over CSS
Typography scale
Common gotchas
Block anchors
Validate generated code
Pro block registry
Match task bundles
TrademarkTrademark
Ctrl k
Search...
Sign up
Once UI Handbook
Beginner Guides
What is Once UI?
Install & config
Page skeleton
Your first page
Build And Launch
How to launch a portfolio site that actually gets you hired
How to build a documentation site with MDX and Next.js
How to ship a landing page and dashboard with authentication in Next.js
How to launch a social app with Next.js and Supabase
Vibe Coding
Introduction to vibe coding
Set up your local dev environment
Essential tools for vibe coding
Build your first Once UI app
Common Patterns
Hero section
Static panel
Form layout
Highlighted card
Responsive stacking
Decoration layers
Dialog & modal
Toast & feedback
Tables & lists
Loading states
App shell navigation
Dashboard & charts
Chat & messaging
Auth & verification
Settings & split panels
Data filters & toolbar
Command palette
Pricing & plans
Accordion & FAQ
Media & uploads
Empty & error states
SEO, Open Graph, and structured data
Documentation code blocks with live preview
Carousels, galleries, and before/after comparisons
Date pickers and scheduling
Context menus and dropdown actions
Tags, chips, and multi-value inputs
Roadmap & kanban
Form inputs & controls
Progress, status & badges
Scrolling & feeds
Profile, avatars & identity
Social proof & logo clouds
Masonry & media grids
Table pagination, search & bulk selection
Banners & announcements
Footer layouts
Onboarding & first run
Waitlist & coming soon
Design Tips
Color & surfaces
Harness overview
Row, Column & Grid
Spacing & rhythm
Icons & buttons
Reveal & motion
Theme tokens, FOUC-free init, and runtime style controls
Tooltips and hover cards
Block updates
Block updates changelog
Agent Resources
Column, not Flex
Semantics over CSS
Typography scale
Common gotchas
Block anchors
Validate generated code
Pro block registry
Match task bundles
TrademarkTrademark
Once UIDocumentationBlog
© Once UI. All rights reserved.
Built with Aveiro

Responsive stacking

Breakpoint props for mobile stacking — no media queries needed.
Updated 19d ago
Highlighted card
Decoration layers
5 min · Pattern
Once UI handles responsive layout through breakpoint props on components — not CSS media queries.

Breakpoint keys

Override layout at breakpoints using props on the same component:
Key
Typical viewport
`xl`Largest
`l`Desktop
`m`Tablet
`s`Mobile landscape
`xs`Mobile portrait
Larger breakpoint styles cascade down. Set the desktop layout as defaults, then override at s or m.

Stack on mobile

The most common pattern — horizontal row that becomes vertical: Desktop: side by side. Mobile (s): stacked.

Responsive grid

Reduce columns as viewport shrinks:

Responsive spacing

Tighten gaps on smaller screens:

Responsive buttons

Stack CTA buttons on mobile:

When layout needs a direction flip only

If the only responsive change is direction, use Row with breakpoint override — no need for a separate layout component:

Write this / not this

✅ Once UI way
❌ Common mistake
`s={{ direction: "column" }}`CSS `@media` queries
`s={{ columns: "1" }}` on GridSeparate mobile component
`s={{ gap: "16" }}`Inline `style` overrides
Desktop layout as default propsMobile-first with `xs` only

Server vs client

Breakpoint props require client-side class resolution. Once UI's Row, Column, and Grid handle this automatically — they switch to client rendering when breakpoint props are present.

Check yourself

  • No CSS media queries for layout
  • Desktop layout set as default props
  • Mobile overrides use s or m keys
  • Buttons and panels stack with s={{ direction: "column" }}

Related

→ Row, Column & Grid → Hero section → Page skeleton
<Row gap="24" s={{ direction: "column" }}>
  <Column fill>Left content</Column>
  <Column fill>Right content</Column>
</Row>
<Grid columns="3" gap="24" m={{ columns: "2" }} s={{ columns: "1" }}>
  <Column>...</Column>
  <Column>...</Column>
  <Column>...</Column>
</Grid>
<Column gap="32" s={{ gap: "16" }}>
  ...
</Column>
<Row gap="16" horizontal="center" s={{ direction: "column" }}>
  <Button href="/start">Get started</Button>
  <Button variant="secondary" href="/docs">Learn more</Button>
</Row>
<Row gap="16" vertical="center" s={{ direction: "column", horizontal: "start" }}>
  <Icon name="check" />
  <Text variant="body-default-s">Feature description</Text>
</Row>