Composite, higher-level pieces built out of the base
component set (a scheduler, a data
grid, a kanban board), rather than a single field or control. Where a
component page covers one custom element (plus its tightly-coupled
siblings, like a tab group's tabs), a feature page covers a small system:
a main orchestrating element plus, where relevant, the independent pieces
it's built from, each useful and documented on its own too.
Scheduler
A calendar with day, week, work-week, month, and year views, complete with event display, color coding, and a desktop side panel or mobile modal for creating and editing events
Table
A data grid with row selection, a floating bulk-action bar, and sticky headers, columns, and rows.
Reading a feature's page
Every feature page follows the same four tabs a component page does
(Overview/API/Examples/Accessibility — see
Components: Reading a
component's page), plus a complete, fully wired example on its
Overview tab — not just an isolated snippet, since a feature's whole point
is how its pieces work together. Its independent sub-elements each get
their own page too, linked from the sidebar underneath the main feature.