Skip to content
Why ZeeTheme

Built on the editor you already ship with

ZeeTheme output is native block markup in the WordPress editor: no shortcode layer to lose when a plugin goes, no runtime styling every page has to load, and no token stored somewhere the editor cannot read.

The mechanism

Three decisions that shape everything else

Each of these is a property of how the output is stored and styled — checkable in the editor on any page, not a figure to take on trust.

Native editable output, not a shortcode blob

A page built here is stored as block markup, so the editor opens it as the same blocks you placed. Deactivating a plugin leaves that markup readable and editable instead of a single unparsed blob.

  • Every element stays selectable in the editor
  • Saved content is ordinary post markup, portable between installs
  • No proprietary page representation to migrate out of later
<!-- wp:paragraph -->
<p>Published text stays editable.</p>
<!-- /wp:paragraph -->

Styles scoped to what a page actually uses

Each block brings the stylesheet its own output needs, loaded for the blocks present on that page. Nothing ships a library-wide sheet that every request has to carry whether the page uses it or not.

  • Per-block styles rather than one framework bundle
  • A block a page omits costs that page nothing
  • What is loaded reflects what is rendered

Page uses

  • Heading, paragraph, buttons
  • Stylesheets for those blocks only

Tokens live in theme.json, where the editor reads them

Palette, typography and spacing are declared in the theme's own settings — the same source the editor's controls read. The colour picked in the sidebar is the colour the front end renders, with no mirrored copy to drift.

  • One token source for the editor and the rendered page
  • Changing theme restyles the shell, not the saved block output
  • Client token decisions stay above the theme layer

Read order

theme.jsonEditor controlsRendered front end

Capability comparison

What each approach does, mechanism by mechanism

Cells answer whether a mechanism holds, not by how much. The right-hand column is a category — a runtime that owns its own page representation — and no named product is scored here.

MechanismZeeTheme blocksA classic page-builder runtime
Design tokens declared in theme.jsonIncludedExcluded
Styles load per block, for the blocks a page usesIncludedExcluded
No builder-wide stylesheet or script on every pageIncludedExcluded
Content stored as native editor markupIncludedExcluded

A classic page-builder runtime is compared on how it stores and styles content, not on a vendor claim. Switched-off cells say that a mechanism does not apply to that approach — not that the approach is unusable.

On evidence

What this page states, and what it refuses to state

Mechanisms are checkable on your own install. Anything that needed a measurement is either demonstrable in the builder or explicitly absent.

Start from markup you can read

Copy a starter pattern and see the output for yourself, or look at what the official themes plan to carry when they are released.