HTML FIRST / FRAMEWORK OPTIONAL

Build with Runway UI.

Start with one stylesheet, find a component, then compose your interface.

Pre-1.0 · API consolidation
01 / ADOPTION

One stylesheet. Your own rules.

Link the bundle, add a rw-ui root and use native HTML. Behaviors are optional modules; no framework or game engine is required.

<link rel="stylesheet" href="./runway-ui/dist/runway-ui.css">
<section class="rw-ui rw-panel" data-theme="orbital">
  <button type="button" class="rw-button" data-variant="primary">
    Launch expedition
  </button>
</section>

For an existing native form, optionally load styles/native.css and add rw-native. For another UI framework, migrate its markup deliberately; CSS does not translate event contracts.

02 / COMPARE OPTIONS

Change the recipe, see the result.

Art direction
Action
Surface & policy
LIVE COMPONENT RECIPESupplies low

Prepare the next expedition.

Every action needs a clear cost, consequence and state.

Input state is independent of action state.
Readiness68%
Escape and backdrop can dismiss.

Preview only. No simulation state changes.

Generated markup

The same recipe works in plain HTML or a framework template.

03 / PUBLIC CONTRACT

Options, defaults and markup.

Attributes are additive. Unknown visual values use the component default.

04 / FOUNDATIONS

Theme color. Tune density.

data-theme selects Studio, Orbital, Parchment or Whimsy. data-density="compact" changes inherited spacing. An explicit button size overrides density for that button.

.my-world {
  --rw-accent: #41705c;
  --rw-on-accent: #ffffff;
  --rw-radius: 8px;
  --rw-panel-padding: 20px;
}

Keep a single root where possible. A nested rw-ui root starts fresh token defaults; top-level dialogs need their own theme and density. Use local tokens for art direction and component attributes for semantic state.

Complete token and precedence guide

05 / INTERACTION

Native semantics come first.

  • Use native buttons and disabled states. Keep labels visible; icons need accessible names.
  • Give dialogs a heading. The browser owns modal focus and background inertness.
  • Keyboard navigation moves focus; the application owns selection and activation effects.
  • Keep text values alongside charts, needs and progress. Do not communicate state with color alone.
  • Virtual grids omit off-screen DOM. Offer search and an appropriate alternative when browse-mode access is required.
  • Reduced motion and forced colors receive CSS accommodations; they do not establish accessibility conformance.

Detailed behavior contracts

06 / MATURITY

A compatibility contract, not a stability label.

The library follows semantic versioning from 1.0.0. Existing class names, exports and default behavior are kept within a major version. New options are opt-in, and breaking changes are documented in the changelog.

Current verification covers focused desktop Chromium flows. Firefox, Safari, physical controllers and assistive technology still need direct validation before a 1.0 stability claim.

Compatibility policy and remaining gates · TypeScript API reference · Local changes

NATIVE HTML DIALOG

Commit to this expedition?

You can dismiss this optional decision.