Getting-started checklist, rail

Getting-started checklist, rail is a Lists block from Orvain UI, built for React and Vue with a matching Figma frame.

Best for

Launch checklists where progress should be seen travelling

Anatomy

Ink icon-square header with the minutes left rolling down · one segment per step · steps on a rail that fills to the current step, each node the step's checkbox with a brand ring on the current one · a quiet link to do each step · a last node that unlocks when everything before is done

MCPConnect the MCP server

Launch checklist

about 6 min left · 1 of 4 done

  1. Add a product3 minPhotos, price and stock.
  2. Set up shipping2 minZones and rates for where you ship.
  3. Connect payments3 minPayouts reach your bank in two days.
  4. Choose a domain1 minUse yours or a free orvain.shop one.
  5. Launch your storeUnlocks when the four steps are done.

In the Orvain Library

Get Getting-started checklist, rail 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

05parts

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

  1. Ink icon-square headerwith the minutes left rolling down
  2. One segment per step
  3. Steps on a railthat fills to the current step, each node the step's checkbox with a brand ring on the current one
  4. A quiet link to do each step
  5. A last nodethat unlocks when everything before is done

Responsive behaviour

520 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 “Getting-started checklist, rail” block to this page: ink icon-square header with the minutes left rolling down, one segment per step, steps on a rail that fills to the current step, each node the step's checkbox with a brand ring on the current one, a quiet link to do each step, a last node that unlocks when everything before is done.

Works in
Connect the MCP

Questions about Getting-started checklist, rail.

What is the Getting-started checklist, rail block?

Getting-started checklist, rail is a Lists block from Orvain UI, built for React and Vue with a matching Figma frame. Best for launch checklists where progress should be seen travelling.

What is the Getting-started checklist, rail block made of?

Is the Getting-started checklist, rail block responsive?

Is the Getting-started checklist, rail block accessible?

How do I add the Getting-started checklist, rail 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

Inbox list, stacks

Busy inboxes where one source sends many notices

Getting-started checklist

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

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.