Recipe page

ValuesOS Step List with Polished SaaS Crisp

A tighter SaaS treatment with crisp hierarchy, restrained spacing, and clean control rhythm.

shadcncomfortablesubtle4 data recipes7 quality checks
shadcn

Focused block preview

Back to block

How it works

ValuesOS Step List steps

Process blocks carry estimates, statuses, outcomes, bullets, and actions without losing responsive rhythm.

01Active2 min

Capture intent

Collect the minimum data needed for the next template decision.

Clear routing context

  • Audience
  • Offer
  • Desired action
Review
02Ready1 min

Apply recipe

Map the content to a theme recipe and component defaults.

Aligned controls and surfaces

03QA3 min

Publish proof

Run the static checks and confirm the block has no overflow.

Grade-A default state

Grade A defaults

This recipe inherits the block quality contract

7/7 covered
covered

Contract backed

Schemas, manifest metadata, editor fields, accessibility, and i18n remain attached to the block type.

covered

Runtime rendered

The documentation route renders through native, alias, wrapped, or nonvisual runtime support without generic fallback UI.

covered

Configuration coverage

Default, media, background, gradient, colorway, dense, and editorial configurations are all visible.

covered

Recipe coverage

Every Theme Studio recipe has a focused page and an inline preview for this block.

covered

Data composition

CMS authors can lift structured payload recipes for default, media, operator, and stress contexts.

covered

State readiness

Default, empty, pending, active, invalid, and disabled states are documented for every cloneable block recipe.

covered

Resilience proof

Media replacement, long copy, and awkward content tolerance are represented in the documented defaults.

Cloneable data

Same block, CMS payload recipes ready to copy into page data