Inbox list, stacks

Inbox list, stacks is a Lists block from Orvain UI, built for React and Vue with a matching Figma frame.

Best for

Busy inboxes where one source sends many notices

Anatomy

Today and Yesterday labels · single rows and grey stacks, one per source, with two layers peeking under them, an update count and an unread pill that counts down · opening a stack fans its rows out with a short stagger · opening a row marks it read

MCPConnect the MCP server

Inbox

6 unread
Today
Ethan Cole mentioned you in #design“@Ana can you review the list spec?”
Cara Brook merged your pull requestfeat/command-menu → main
Liam Hawk opened #482 Card rows12 files · 3 reviewers
Checks passed on #482Lint, test and build · 2 min 14 s
Noah Reed commented on Q3 roadmap“Love this direction. Ship it.”
Yesterday
Production deployedbuild #4821 · 1 min 52 s
Preview readyfeat/command-menu · build #4820
Build failedfix/tokens · build #4819 · type error
Production deployedbuild #4818 · 1 min 47 s
Khadija Alaa shared 2 files in Brand refreshReady for your reviewBrand refresh.fig Figma · 4.2 MBLaunch guidelines.pdf PDF · 12 pages

In the Orvain Library

Get Inbox list, stacks for your product

The block’s code in React and Vue, its frame in the Figma file, and the Orvain MCP so your AI tools build with it. Part of every Library plan, alongside every other block.

  • React
  • Vue
  • Figma frame
  • Orvain MCP

About this block

Part of Lists

What’s inside

04parts

The pieces it is built from. Keep them all, or drop the ones your product doesn’t need.

  1. Today and Yesterday labels
  2. Single rows and grey stacksone per source, with two layers peeking under them, an update count and an unread pill that counts down
  3. Opening a stack fans its rows outwith a short stagger
  4. Opening a row marks it read

Responsive behaviour

480 px

Drawn at this width and never stretched past it. Below it, controls, text and spacing step down from the box the block sits in, not the window.

1440pxDesktop · 12 columns

When to use it

Where Lists earns its place

Reach for Lists

  • Settings grouped under headings, each row its own destination or switch
  • Inboxes where every row carries read state and a timestamp
  • Short claims read in sequence, like what a plan includes
  • Narrow screens, where a full-width row beats a line of links

Reach for something else

  • Records compared field by field: a table gives them columns
  • Items with a photo and several unlike stats: a card holds those without cramping them
  • A hierarchy people expand and collapse: a tree view shows the depth

Accessibility

06to keep

What the block ships with. Hold on to these as you make it yours.

  • Named controlsEvery icon-only button keeps a text label, so a screen reader can say what it does.
  • Keyboard firstEvery control is reachable with Tab, and its focus ring stays visible.
  • More than colourA state never rides on colour alone; a mark or a word goes with it.
  • Contrast holdsRetheme freely, but keep text at or above the contrast it ships with.
  • Calm motionFor visitors who ask for reduced motion, things simply appear.
  • Room to hitTargets stay at least 24px, with space between neighbours.

Notes for AI

1 line

Is all your assistant needs. With the Orvain MCP connected, it builds the block from your own tokens and components.

Add the Orvain “Inbox list, stacks” block to this page: today and Yesterday labels, single rows and grey stacks, one per source, with two layers peeking under them, an update count and an unread pill that counts down, opening a stack fans its rows out with a short stagger, opening a row marks it read.

Works in
Connect the MCP

Questions about Inbox list, stacks.

What is the Inbox list, stacks block?

Inbox list, stacks is a Lists block from Orvain UI, built for React and Vue with a matching Figma frame. Best for busy inboxes where one source sends many notices.

What is the Inbox list, stacks block made of?

Is the Inbox list, stacks block responsive?

Is the Inbox list, stacks block accessible?

How do I add the Inbox list, stacks block to my project?

When should I not use a Lists block?

More Lists blocks

All Lists

Settings list

Account and workspace settings: grouped rows a person scans once

Settings list, find

Settings long enough that people search: nine rows across three groups

Feature list

Pricing and upgrade pages: what a plan buys, three rows at a time

Inbox list

Notification inboxes: a morning of activity behind three tabs

Getting-started checklist

First-run setup: one thing at a time, with how long it takes

Getting-started checklist, rail

Launch checklists where progress should be seen travelling

The Orvain Dispatch

Premium components, free in your inbox.

Join the Orvain Dispatch and get production-ready components, free to keep: React and Vue code plus the Figma frame, yours to ship.

Just components, never spam. You can unsubscribe anytime.