3 Unit

Pieces that work together.

Turn individual controls into navigation, collections and forms with a shared rhythm.

Select

Every menu a button opens, one square a choice.

Context

The menu where the pointer is, a pixel between rows.

Sidebar

Places to go, with room to grow.

Calendar

Make room for what comes next.

Form

Related choices, brought together.

Table

Information that lines up.

Accordion

More detail, when you need it.

List

A rhythm for your collection.

A Unit brings individual Core pieces together. It provides the shared structure or interaction of a collection, form or navigation area while the application supplies content and decisions.

What belongs here

Composition	Purpose
List, Row, Table	Organize related items and comparable values.
Form	Coordinate fields and submission feedback.
Select	Every menu that opens from a button: a field’s choices, a button’s actions.
Context	The menu that opens where the pointer is, in Ezo’s gap face.
Sidebar	Organize destinations and hierarchy, as navigation or a tree.
Accordion	Reveal and hide related sections.
Panel, Card	Group related content into a composition.

Some entries describe composition patterns rather than a custom element. Follow each page’s markup and API instead of assuming every pattern has a matching tag.

Keep responsibilities clear

The shared composition owns its documented layout, focus and keyboard behavior. The application owns the data, routes, selected values, permissions and accepted changes. For a sidebar, a label can navigate while the separate disclosure arrow expands its children; those are distinct actions.

Build on the other layers

Core supplies the smaller controls and Root supplies the shared measures and appearance. Page places units into an overall layout. Prefer an existing Unit when it covers the interaction; compose new application content without rebuilding its controls.