Component build status
Honest, manifest-generated status for every Emily Components entry. 259 of 303 entries are built today; nothing here is inflated.
Counts by layer
These numbers come from the Emily Components manifest (component-manifest.json, 303 entries), last regenerated 2026-07-06. Statuses move only on evidence — a completed checklist or a tested example — never on plausibility.
| Layer | Built | Total | Remaining |
|---|---|---|---|
| Tokens | 10 | 10 | 0 |
| Atoms | 98 | 105 | 7 |
| Molecules | 35 | 42 | 7 |
| Organisms | 80 | 100 | 20 |
| Templates | 30 | 32 | 2 |
| Pages / starters | 6 | 14 | 8 |
| All layers | 259 | 303 | 44 |
What the statuses mean
built — A working, documented example exists in emily-components.
needs-css — The pattern is specced but its CSS is not finished yet. (Currently none — the last needs-css entries shipped with emily-css v2.2.0.)
needs-js — Blocked on emily-js behaviours — the pattern cannot work honestly without JavaScript.
needs-a11y-review — Blocked on human assistive-technology or contrast testing. Static review is not enough to promote it.
planned — Listed in the manifest with a reason, not started or not shipped.
deferred — Consciously parked until there is real demand.
Rules for consumers
needs-a11y-reviewis not production-ready. Prototype with those patterns if you accept the risk; do not ship them unreviewed.needs-jsitems wait for emily-js behaviours — do not bolt on ad-hoc scripts while keeping the Emily class names.- Planned starters and pages are not shipped. Do not promise them to clients; compose from built templates instead.
Related
See the built starters and the accessibility status pages.