Blog
A post list, a reading view, an author page and an editor. Enough of a publishing surface to attach to a CMS you already have.
⚠️ Pro edition
These screens are in the Pro download. The free edition ships the design system and the demo, not the application screens.
The screens
5 screens, at these routes in your download. Open them beside this page.
| Route | Screen | What it is for |
|---|---|---|
| /blog | Blog index | The public-facing list, with cover images, tags and reading time. |
| /blog-posts | Posts | The operator's table of posts: status, author, date, and row actions. |
| /blog-post | Post | One post as a reader sees it, with the article typography the theme ships. |
| /blog-author | Author | An author's profile and their posts. |
| /blog-editor | Editor | The composing surface: title, body, cover, tags and publish controls. |
What you get
- Article typography that is part of the theme rather than a one-off stylesheet, so a post looks like the product.
- Draft, scheduled and published as visible states on the posts table.
- An editor layout with the metadata beside the body rather than buried behind a dialog.
What you connect
These are interfaces, not an application.They render, they hold their own state, and they talk to nothing. Everything below is your application's, and none of it is supplied.
- Storage. Nothing is persisted. The editor's content lives in component state until you wire it up.
- A rich-text engine, if you want one. The editor is a composed layout, not a bundled WYSIWYG.
- Publishing. Scheduling, revisions and previews are workflow, and workflow is your application's.
- Media. Cover images are file inputs with previews and no upload target.
Built from
Nothing here is a one-off. Each screen composes the same families documented in the reference, so changing a token moves them with the rest of the product.
data-table, form, badge, avatar, card.
Next
A customer screen, end to end builds one of these from an empty route, and Theming is how you make them look like yours.