New to Deck
Install it in about a minute, add class completion to your editor, then build a complete account settings page — nav bar, rail layout, real form controls, a confirm dialog and a save bar — in one sitting, typing every line.
Start hereDeck documentation
Deck is a CSS framework that ships as a single stylesheet. Add one
<link> tag and you have buttons, forms, tables, a data grid,
charts, overlays, and an icon sprite, with no build step, no config file, and no
dependencies.
Start here
Components
One page per component: every variant rendered, the class table generated from the stylesheet, the tokens it reads, and when not to reach for it.
47 pagesReference
All 931 classes and 144 tokens, filterable by layer, bucket and name, plus the utility tables and the JavaScript, PHP and CLI APIs. Works without JavaScript.
The demo
Every component on one page, in context. It shows what Deck looks like; these pages explain how it works.
Open the demoHow these docs are organised
Four modes, kept apart on purpose. Mixing reference into a tutorial is the usual way documentation becomes unreadable: a person learning wants a path, and a person looking something up wants a table.
| Section | For | Looks like |
|---|---|---|
| Start | Learning | A path from nothing to a styled page, in order. |
| Guides | Doing a specific task | Theming, dark mode, RTL, printing. Assumes you have Deck working. |
| Components and reference | Looking something up | Tables, generated from the source. No narrative. |
| Explanation | Understanding a decision | Why there is no build step, why cascade layers, why one hue. |
Status
872 of 931 classes have a page
The extractor and verifier are in place, so every class is inventoried and every
page is checked against the source on each build. The
59 classes with no page yet are
recorded in tools/docs/undocumented.txt rather than rounded off, and
the build fails if that list grows. You can see exactly which they are by
filtering the class reference
to “No page yet”.