WidgetGrid

Preview

Installation

npx echo-ui-cli add widget-grid

At a glance

Version

0.3.0

Weight

2.7 KB · 32.0 KB with what it imports · 2.7 KB of CSS (minified and gzipped; React not counted)

Needs

gsap, hardware-button (Echo, brought with it)

Keyboard

• Arranging is a button that says what it does ("Arrange Home", "Done arranging Home").
• Each Move key is named with its widget and moves it with the arrow keys (Home and End to the ends); the new place is announced ("Weather moved to place 3 of 6").

Reduced motion

Widgets change places at once; nothing slides.

Sound

A tap as a widget takes a new place, and the select click when one is moved by key, inside a SoundProvider.

Usage

import { WidgetGrid } from "@/echo/widget-grid";
import { StatTile } from "@/echo/stat-tile";

<WidgetGrid label="Home" items={[{ id: "a", label: "Latency", content: <StatTile value="42" label="Latency" /> }]} />

Composition

WidgetGrid
  HardwareButton (Arrange, Done)
  the grid: a list item per widget, your content, and while arranging HardwareButton (Move) and HardwareButton (Remove)

Examples

<WidgetGrid
  label="Home"
  items={[
    { id: "today", label: "Today", content: <DateTile date="2026-09-25" size="lg" /> },
    { id: "latency", label: "Latency", content: <StatTile value="42" unit="ms" label="Latency" /> },
    { id: "volume", label: "Volume", size: "2x1", content: <Tuner label="Volume" max={11} /> },
  ]}
/>

<WidgetGrid label="Dashboard" items={widgets} order={order} onOrderChange={saveOrder} onRemove={hide} />

Accessibility

• A region named by label; the widgets are a list, in the order they're shown.
• Arranging is a button that says what it does ("Arrange Home", "Done arranging Home").
• Each Move key is named with its widget and moves it with the arrow keys (Home and End to the ends); the new place is announced ("Weather moved to place 3 of 6").
• Dragging is a pointer extra: everything it does, the Move key's arrows do.
• Remove keys are named with their widget, and only appear when removing is allowed.

Motion & sound

Motion tokens

travel

Reduced motion

Widgets change places at once; nothing slides.

Sound

A tap as a widget takes a new place, and the select click when one is moved by key, inside a SoundProvider.

Props

Anti-patterns

• Never use a WidgetGrid for content with an order that means something (a list of steps): only for things people arrange by taste.
• Never forget onOrderChange when the arrangement should last: without it, the order is lost on reload.

Changelog

• v0.3.0 · 2026-10-12 · ChangedEvery item needs echo-ui-core 0.3.0 (all components). The drawn device, readability past AA and the design tests live in core, and the components that use them are built against it, so each item now declares echo-ui-core >=0.3.0 <0.4.0. Update core with the items: npm install echo-ui-core@^0.3.0 (or your package manager's), then npx echo-ui-cli update. An item whose files didn't change is the same code under a new version; the 0.2.0 files stay published.
• v0.2.0 · 2026-10-04 · AddedThe light device (echo-ui-core, echo-ui-cli). Echo can be light: a pale chassis makes a device molded in light plastic, like a white calculator or a cream radio, and a dark one makes the device Echo has always been. There's no setting and no mode to switch; the chassis decides (devicePolarity, and values.polarity on the theme). On a light device the page is light: its ground, the well, is the body barely set in. Caps get their own ladder, a step lighter than the body with a lit rim that stops short of white, so they keep their bevel; undersides and seams are shaded darker; dim text moves toward the ground by the same step as on a dark device, and reads about 6:1 on it. Screens are paper glass printed in ink, because a glow on a pale body is a smudge. What's lit (an LED, the current rail) is still the accent, held to 3:1 on every ground, so on is brighter than off; the text it prints (a readout, a count, a current tab) and the focus ring are the accent's ink, a step deeper and held to AA, in the new accent-ink role. The primary cap is the same cap as a dark device's, the accent with a light label: its label is the new primary-cap-ink role, and progress cells, loader dots and a meter's fill, the same plastic, read 3:1 on the page. A neutral cap or a slider that fills with it under its own dark label fills with the new pour-* roles, the accent's pale stops. Shadows are drawn at half their weight, in a deep colour of the body's own hue (--echo-cast-ink) instead of black. Every guarantee holds as it does on a dark device, and the contrast sweep now runs on light bodies too. A dark seed makes exactly the theme it did before, and the new roles equal the ones they stand for there. The components that mixed a recess toward black, painted paper in the text colour or lit a pillow of light with it read the theme's new --echo-shade-ink, --echo-paper-stock and --echo-paper-ink instead, with the old value as the fallback, and a reflective screen reads --echo-screen-*; the components that print a lit label read --echo-primary-cap-ink and --echo-accent-ink the same way; every rail is drawn in the glow, and every focus ring, the ring recipes included, in the ink. style use wears a light style now, and style check says which device a style makes. A dark screen tint on a light body is still refused: one text colour can't serve both, and the theme says so.
• v0.2.0 · 2026-10-04 · AddedWidgetGrid: widgets people arrange. Fixed footprints (1×1, 2×1, 2×2, 4×2) on a grid that narrows to two columns on a phone. Arrange it and each widget gets a Move key (drag it, or use the arrow keys, and the new place is said) and, with onRemove, a Remove key; the others slide out of the way.
• v0.2.0 · 2026-10-04 · ChangedComments only, no behaviour change. Comments in the component source used to cite documents, milestones and ticket numbers from Echo's own planning, none of which exist in your project. The citations are gone and the sentences around them stay. Where a comment was only a citation, it now says what it meant. Three development warnings (HardwareButton's engraved/caption checks and StatusDot's missing-label check) also dropped the ticket code at the end of the message. echo-ui diff will show changes in most items; none of them are to code.
• v0.2.0 · 2026-10-04 · ChangedAn item's version is now a function of declared data, not of how the changelog is formatted. The version an item ships under is published once and never rewritten, and it used to be inferred from prose: a regex for a bolded "Breaking" run across the whole unreleased section, and attribution by "does a bullet mention this name in backticks". One breaking entry therefore moved every item that changed that cycle, and an entry explaining that "Menu and Sheet are unchanged here" filed itself as a change to Menu and Sheet — which it really had.
• v0.2.0 · 2026-10-04 · ChangedThe agent brief says Echo has not shipped. llms.txt and the MCP server's instructions led with npx echo-ui-cli init, and that name on npm is a reserved stub with no executable — so a model following the brief wrote an install step that fails with npx's own error. The brief now opens with the caveat, and the docs carry it on every surface that shows a command. One switch (CLI_RELEASED) silences all of them at launch, and a test refuses to let one move without the others. Affects all components only in what the brief says about installing them; no item's props, CSS or rendered semantics change.
• v0.2.0 · 2026-10-04 · ChangedEcho's home is echo-ui.com. The registry, the docs and the packages all move to it from echo.nawwara.studio. Nothing was published under the old host, so no echo.json anywhere points at it and there is nothing to migrate — this is the last release where that is true.
• v0.2.0 · 2026-10-04 · ChangedWeights, line heights, letter-spacing, z-index, border widths and icon sizes come from the theme scales in all components, with the old value as a fallback, so components keep working with echo-ui-core@0.0.1. Strays moved to the nearest step: most by under a pixel; HardwareButton icons are 14/16/20px (were 15/17/19).
• v0.2.0 · 2026-10-04 · FixedContent now reflows into a 320px screen (400% zoom) and survives a doubled browser text size (WCAG 1.4.10, 1.4.4), across all components. Select's 180px floor, NumberField's readout, Segmented and Steps as flex items, EmptyState's grid columns, and Avatar's fixed-pixel disc all gave way; Panel counts its padding inside a width you set (box-sizing: border-box), so a <Panel style={{ width: 220 }}> is now 220px wide overall rather than 260px.