10 Content Block Examples for Design System Docs
Content block examples for design system docs: the 10 blocks teams use most, with live pages, and what Supernova, zeroheight and Knapsack call each one.
Beatriz NovaisSolutions architect

Most design system pages are built from the same dozen pieces: a token table, a do and don't pair, a status badge, a Figma frame, a code sample. These content block examples are the ten that teams documenting their systems in Supernova reach for most, each with a live page you can open and copy.
Good design system documentation is mostly a question of picking the right block for each job. A paragraph explaining when to use a button is fine. A guidelines block with the right and wrong version side by side is faster to read and harder to misunderstand.
Below the list there's a table showing what Supernova, zeroheight and Knapsack call the same blocks, so you can map one tool's vocabulary to another's.
What is a content block?
A content block is a single, typed unit on a documentation page: a table, a token list, a component status, an embed. You add blocks from a menu (in Supernova, type /) instead of formatting free text, and each block keeps its own settings and data source. Supernova's documentation editor currently offers 30 block types in ten groups, from plain text to color ramps.
1. Design tokens

Example: Maze's product colors in Ariane
The Design tokens block shows your tokens and their properties as a table or a grid. Pick a theme and choose "Split view" to compare themes side by side, or "Override base" to show only the selected one.
Tip: select a token group rather than single tokens. When someone adds a token to the group, the block updates on its own.
2. Guidelines (do and don't)
Example: Supernova's Guidelines block docs
The Guidelines block holds rules as a set of items, each typed Do, Don't or Caution, with text and an optional image. It has four style variants (Prominent, Simple, Contained, Side border), and items reorder by drag and drop. Before it shipped in 2024, teams built the same thing with a two-column table. Use it wherever people keep making the same mistake, such as two primary buttons in one dialog or a disabled state that looks like a secondary one.
3. Component checklist

Screenshot: Mozilla's Acorn design system, 2024.
The Component checklist block shows one component in a table and highlights the properties you choose: its Figma link, health status, repository link, whether it's deprecated, and when it was last edited. Put it at the top of each component page so designers and engineers see the build state before they read the guidance.
4. Component health

Example: Alma Career's Spirit button page
The Component health block is a status report for a single component. Spirit uses it to show whether Figma, HTML and React are each up to date. Health labels are customizable, so you can match the stages your team already uses. Read more about tracking your design system's health.
5. Component overview table

Screenshot: Hearst's design system documentation, 2024.
The Component overview table lists every component in your design system in one table, with the properties you choose and, optionally, the date each one was last updated. It works as a dashboard and as an index: link each row to its guidelines, design and code.
6. Vector assets

Screenshot: Skyscanner's Backpack documentation, 2024.
The Vector assets block (called "Assets" when this post first ran) lets people search for icons or illustrations on your published site and download them. It saves the "where's the latest icon set?" message in your team channel.
7. Figma images

Example: Maze's field anatomy
The Figma images block displays a frame straight from Figma. When the frame changes in Figma, the image in your documentation updates too, so nobody re-exports screenshots after every component change.
Tip: anatomy diagrams are the best use. Maze labels each part of the field in Figma once, and the doc page stays current.
8. Tabs

Example: Mews' checkbox usage tabs
The Tabs block splits a section into tabs, so different readers see what they came for without scrolling past the rest. Mews uses it to separate code for each variant of the checkbox.
Tip: one tab per variant or per platform keeps production code one click away for engineers.
9. Shortcut links

Example: Productboard's components overview
Shortcut links point to another page, a section of a page, or an external URL, and display as a gallery of tiles. Productboard uses them as a visual index of every component. Maze uses them as its homepage.
10. Table

Example: Mews' checkbox API table
The Table block is the most flexible block on the list. Use it for props and their types, component states with images, or changelogs. Cells can hold Figma frames and code snippets as well as text.
More content block examples worth knowing in 2026
These newer blocks didn't make the top ten but solve specific problems well:
- Accessibility color grid: visualizes how accessible your color tokens are when combined.
- Color ramps: displays a token scale as a ramp, which reads faster than a table for color.
- Storybook: embeds a live canvas from your Storybook, so the component on the page is the real one.
- React code: renders React code on the page instead of only showing it.
- Markdown: embeds and processes Markdown, useful when some guidance already lives in a repository.
What do Supernova, zeroheight and Knapsack call the same blocks?
Every documentation tool covers the same jobs, but the names differ. If you're moving between tools or comparing them, this is the translation. Names come from each vendor's own block reference, checked on 2 November 2026: Supernova (updated 7 May 2026), zeroheight and Knapsack.
| Job | Supernova | zeroheight | Knapsack |
|---|---|---|---|
| Do and don't examples | Guidelines block | Rules (do's, don'ts, cautions) | Guidelines Block |
| Tokens | Design tokens, Color ramps, Accessibility color grid | Design Tokens | Design Tokens Block |
| Component status | Component health, Component checklist, Component overview table | Status table | Patterns Status Table Block |
| Figma designs | Figma images, Figma component, Figma component properties | Design (swatches, typography, designs) | Figma Component Block, Figma Tiles Block |
| Code | Code, React code | Code (live render or snippet) | Code Snippet Block, Template Playground |
| Storybook | Storybook | Storybook | Not in its blocks list |
| Navigation tiles | Shortcut links | Shortcut tiles | Shortcuts Block |
| Tabs | Tabs | Not in its blocks list | Not in its blocks list |
| Downloads | Vector assets, File upload | Attachments | Attachments Block |
| Markdown | Markdown | Markdown (synced from a repository) | Markdown Block |
Two differences stand out. Supernova splits component status into three blocks, from one component to the whole library, where the other two use a single status table. Knapsack groups its blocks by source (design, embed, media, pattern), while Supernova and zeroheight group them by what you're showing.
Which blocks can an AI agent use?
Structured blocks are the ones an AI agent can resolve. A token block, a component health status or a guidelines pair carries named fields an agent can resolve to a value, while a paragraph only tells it what to think. Supernova's MCP server reads that structure directly, so an agent in Claude or Cursor gets your tokens, components and documentation pages from the source rather than from scraped prose.
zeroheight lists a "Remote MCP details" block in its reference, which shows readers how to connect an agent. In Supernova there's no block for it: the MCP connects to the whole workspace.
Start with three blocks on every component page
If your documentation is mostly text today, start small. Put a Component checklist or Component health block at the top of each component page, a Guidelines block for the two or three mistakes people actually make, and a Table for props. Readers get the status, the rules and the API on one screen, and agents get fields they can read.
For a deeper look at the blocks inside the editor, see Unlock the Power of Supernova's Content Blocks. For more finished pages, browse these documentation sites built with Supernova, or try the editor free.
Give your agents a system worth following
See how Supernova documents, syncs, and serves your system in one place.