yogurtships with live cultures

Design system

Use these foundations to build a product screen. The agent roster shows how the same type, colors and controls work together when someone searches, filters and starts again.

Typography

Rethink Sans

Choose the role first. A title introduces a page, body text carries the explanation, and an interface label names an action or value. The figures give size and line height in pixels, followed by weight.

  • Headline48 / 52 · 525
  • Title32 / 36 · 525
  • Subheading20 / 28 · 525
  • Body16 / 24 · 425
  • Interface14 / 20 · 550
  • Caption12 / 16 · 425

Color

Hue and lightness

All 267 colors belong to one library. Pick a hue and a lightness step, then use that token wherever the product needs it. Each token keeps its value across themes.

Color in context

Ready
7.85∶1
sage.750 on gray-green.50
Ready
9.68∶1
sage.200 on gray-green.950

The same status uses a lighter sage on the dark surface. Both examples keep the text label and exceed the 4.5∶1 threshold for normal text. Check the actual foreground and background together. W3C text contrast guidance

Dimensions

Design pixels

In the roster, 4 px joins a label to its field, 12 px separates the filters, and 24 px frames the panel. On narrow screens the panel inset becomes 16 px. Use the smaller gaps for elements people read together.

Spacing

    Corners
    Existing kit: 6 px controls · 12 px panels · fully round indicators. Compare proposed control shapes
    Controls
    40 px height · 44 px on touch
    Lines
    1 px rules · 2 px focus outlines

    Controls

    Field and select
    Keep Find an agent visible above the search input as someone types. The hint “Name or ID” explains acceptable input. Use a select for a short, fixed set such as agent status. Both controls use .boa-field and .boa-input.
    Button
    Name the effect with a verb and an object. Copy CSS token uses the filled button. Clear filters is a secondary action and becomes available when a filter can be cleared. Use .boa-button and data-kind="secondary" for that variant.
    Checkbox
    Use .boa-check on the label around a native checkbox. In the roster, activating either the box or “Dark surface” changes the preview in place.
    Row and status
    Put a row that reveals details inside a native disclosure. Use .boa-row on its summary and .boa-state for the visible status word. A person can read “Ready” or “Working” without relying on the dot color.

    Component catalog

    Open the live Yogurt component library for individual web and Zig entries. The original task recipes follow below.

    Begin with a control people already know. Compose controls around the task and document what happens if the data, the space or the person’s input changes.

    Choose a screen pattern · Use the action menu · Read component availability

    Actions and forms
    The current kit includes buttons, a checkbox, search and select fields. For validation, add a comprehensible message beside the affected field and keep its label visible.
    Lists and status
    Rows, disclosure, text status, search and reset work in the agent roster. A separate task list source covers loading, empty, error, retry and recovered focus.
    Navigation and layout
    The guide uses a compact header, chapter links and a two-column layout that stacks on a narrow screen. Future product shells need their own navigation, back behavior and persistent selection.
    Decisions and overlays
    Design the dialog, menu and progress patterns around a real decision. Record the accessible name, initial focus, cancel action, a pending state and the destination of focus after dismissal.
    Information and identity
    Use the chart and values table for measured quantities, icons for actions and agent artwork to identify who is involved.

    Find an agent

    Roster pattern

    Use this pattern when someone needs to return to a particular agent. Search narrows the list by name or ID. Status narrows the same results. Opening a row reveals the ID in place.

    Agent roster

    • KaiReady

      Agent ID 014

    • SolWorking

      Agent ID 021

    Keyboard and recovery
    1. Search for 014. Kai is the remaining match and the result count updates.
    2. Choose Working. The list reads “No matching agents.” The search and status remain visible.
    3. Activate Clear filters. Both agents return, focus moves to the search field, and the reset button becomes disabled.
    4. Tab to a row. Enter or Space opens its details. Press the same key again to close it.

    Use in an app

    Web

    From a page beside this guide, load the component stylesheet and put the control inside a boa-surface. This example gives the search input its font, visible label, spacing and focus ring.

    <link rel="stylesheet" href="./styles/components.css">
    
    <div class="boa-surface">
      <label class="boa-field">
        Find an agent
        <input class="boa-input" type="search" name="agent">
      </label>
    </div>

    For a root-hosted Next.js or Vite site, copy styles/ and assets/fonts/ into public/yogurt/, keeping those subdirectory names, and load /yogurt/styles/components.css. Keep the relative asset paths together. The stylesheet imports the font faces and generated tokens. Add data-appearance="dark" to a surface for its dark treatment.

    Native

    The native handoff consists of the outlined artwork, the token JSON and the upright and italic variable TTFs. The PostScript names are RethinkSans-Regular and RethinkSans-Italic. Set the weight axis from type.roleWeight and apply the dimensions in the platform’s logical units. The roster on this page demonstrates browser behavior.

    Update a token

    Edit tokens/brand.json and run node scripts/export-css.mjs from the kit. Keep the resulting styles/tokens.css with the source JSON. Files and font license