Stack & Grid
The two layouts a screen is made of, with gaps on the space scale: Stack is a column or a wrapping row, Grid is as many columns as fit (minItemWidth) or a fixed number. Closed: a gap is a step, not a length, so two cards laid out by two people are spaced the same way.
Feel Nothing of its own: the rhythm between things, the same everywhere.
Preview
Or let the agent fetch it: get_component("layout") on the Echo MCP server.
Installation
First time? Run npx echo-ui-cli init once — it sets the project up, and add refuses to run before it.
At a glance
- Version
- 0.3.0
- Weight
- 483 B · 269 B of CSS (minified and gzipped; React not counted)
- Keyboard
- Order on screen is the order in the source, so reading and tab order follow what's seen.
Usage
import { Stack, Grid } from "@/echo/layout";
<Stack gap={6}>{children}</Stack>Composition
Stack → flex; Grid → grid
Examples
A form column
Fields spaced by one step.
<Stack gap={8}>
<Field label="Name" />
<Field label="Email" />
</Stack>A row of actions
Wraps on a narrow screen instead of pushing it sideways.
<Stack direction="row" gap={4} justify="end">
<HardwareButton>Cancel</HardwareButton>
<HardwareButton variant="primary">Save</HardwareButton>
</Stack>A card grid
As many columns as fit, one on a phone.
<Grid minItemWidth="16rem" as="ul">{cards}</Grid>Accessibility
- No role of its own;
asgives it one when the grouping means something (aulof cards, anav). - Order on screen is the order in the source, so reading and tab order follow what's seen.
Tested against WCAG 2.2 AA on every release:
axe— No axe violations, in the component's own gallery and on its page.keyboard— Every action is reachable and operable from the keyboard alone.focus-visible— Focus is visible on every focusable part, in normal and forced-colors mode.forced-colors— State stays visible when the look's colours are replaced by the system's.target-size— Every target's real hit area is at least 24×24px, at every density.reflow— Content reflows into 320px and survives a doubled text size.
Not covered: screen-reader: not yet verified by a person. Everything above is a machine check; a person has not yet driven this component with a screen reader.
Props
| Prop | Type | Default |
|---|---|---|
directionStack: a column or a row. | "column" | "row" | "column" |
gapSpace between items, a step on the space scale (6 is 12px, 8 is 16px). Stack defaults to 6, Grid to 8. | number | |
alignCross-axis alignment. Stack: stretch for a column, center for a row. | "start" | "center" | "end" | "stretch" | "baseline" | |
justifyStack: main-axis distribution. | "start" | "center" | "end" | "between" | "start" |
wrapStack: a row wraps when it runs out of room. | boolean | true |
minItemWidthGrid: the narrowest a column may be ("16rem"); as many columns as fit, never wider than the screen. Fewer items than fit share the row: two cards never sit in three columns. | string | |
columnsGrid: a fixed number of equal columns. | number | |
asThe element; a ul or ol drops its bullets. | "div" | "section" | "ul" | "ol" | "nav" | "header" | "footer" | "div" |
aria-labelA name, when as gives it a role worth naming (a nav, a section). | string | |
aria-labelledby | string |
Anti-patterns
- Never use a Grid for a table of data: that's a Table, which a screen reader can navigate by row and column.
- Never reverse visual order with layout: tab order would stop matching what's seen.
Changelog
- Every item needs
echo-ui-core0.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 declaresecho-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), thennpx 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. - Grid, ChoiceCards and ShortcutMap no longer leave columns empty (BUG-189). Fewer items than fit share the row (
auto-fit), so two cards in a row with room for three are two wide cards, not two cards and a gap. - Six containers:
Card,Item,Stack&Grid,Collapsible,ScrollAreaandLink. The pieces every screen is laid out with, so nobody spaces a card by hand. All six are closed: their slots and spacing are props, not aclassName. -Cardis a Panel with an anatomy (media, a header with one action, a body, a footer whose controls aresm) andsizefor its padding. WithhreforonClickthe whole card is one link or button, named by its title, with one focus ring; it lifts as you reach for it, sinks a pixel as you press and sends Panel's ripple out from your finger. -Itemis the list row: media, title, description, trailing content, ruled by a hairline.swipeActionssit behind it: swipe it and they slide into view, and Tab reaches each one, sliding the row open the same way, so the gesture is never the only way in. -Stack&Grid(echo-layout) take gaps as steps on the space scale; a row wraps and a Grid's columns never get wider than the screen. -Collapsibleis one disclosure on its own, in Accordion's ruled style; closed content stays findable with find-in-page, which opens it. -ScrollAreascrolls inside itself with a groove and a molded thumb, shades whichever edge has more to see, and is a named region the keyboard can scroll. -Linkkeeps the words in the text colour and draws the accent as the underline (accent text on the chassis is under AA);externalsays it opens a new tab;rendertakes your router's link. - Comments 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'sengraved/captionchecks andStatusDot's missing-label check) also dropped the ticket code at the end of the message.echo-ui diffwill show changes in most items; none of them are to code. - An 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 "
MenuandSheetare unchanged here" filed itself as a change to Menu and Sheet — which it really had. - The agent brief says Echo has not shipped.
llms.txtand the MCP server's instructions led withnpx 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. Affectsall componentsonly in what the brief says about installing them; no item's props, CSS or rendered semantics change. - Echo's home is
echo-ui.com. The registry, the docs and the packages all move to it fromecho.nawwara.studio. Nothing was published under the old host, so noecho.jsonanywhere points at it and there is nothing to migrate — this is the last release where that is true. - Weights, 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 withecho-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). - Content 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,SegmentedandStepsas flex items,EmptyState's grid columns, andAvatar's fixed-pixel disc all gave way;Panelcounts 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.