Official themes
One Block theme, one Classic theme — names still unselected
ZeeTheme plans two official themes, each an optional companion for the block library rather than a requirement. Both are planned: no release exists yet, so this page states availability instead of offering a package.
Official Block theme — name unselected
The official Full Site Editing companion: templates and template parts you edit in the site editor, while the block library keeps its own styles on any supported theme.
Official Classic theme — name unselected
The official Classic Editor companion for sites that keep PHP templates, with the same block library output and the same token authority boundaries.
Token authority
What a theme owns, and what it does not
These are product boundaries, not marketing claims: each one is stated in the ecosystem and public-pages contracts.
Blocks carry their own styles
The block library owns its local tokens on any supported theme, so block output does not depend on which theme is installed.
- Block styling travels with the block
- Changing theme changes the shell, not the saved markup
- No per-theme re-authoring of block output
Style ownership
- Block library — local tokens, any theme
- Theme — templates, parts and global styles
The base theme is not the owner of client tokens
Patterns reference client-level token decisions rather than a theme's own palette, which keeps a starter theme optional and keeps client work portable.
- Client token decisions live above the theme layer
- An official theme is a companion, never a dependency
- Template and part inventory ships with a release, not before it
Read order
- 1. Client token decisions
- 2. Theme global styles
- 3. Block local tokens
What you can use today: starter patterns, add-ons and engines and Kinetiq.