Guide

Theme builder vs full site editing (Gutenberg)

Since WordPress 5.9 the block editor can edit templates too: with a block theme, the Site Editor lets you change the header, the footer and the post templates without code. So why would anyone use a separate theme builder? Because the two answer different questions — and the difference shows the moment a client has to use the site.

What full site editing gives you

Full site editing (FSE) is the name for the block editor extended to the whole site. With a block theme, the templates are made of blocks, and the Site Editor shows them the way the post editor shows a post. You can change the header, add a column to the footer, adjust the single-post template, and set styles for the whole site in one place. It is part of WordPress, it costs nothing, and it is the direction the project is heading.

What it does not give you is conditions in the sense a theme builder means them — this header on the shop pages, that one everywhere else — beyond what the template hierarchy allows; nor the surrounding features, which stay with plugins; nor a place for the client to work that is not the WordPress admin.

What a theme builder adds

A dedicated theme builder starts from the same idea and goes further in three directions.

  • Conditions: any template can be limited to a page, a category, a post type, a language — and several templates of the same kind can coexist
  • Design as a system: colours, fonts and text roles as tokens that every block uses, with light and dark variants
  • The client side: a dashboard for the person who runs the site, with pages, media, messages and orders, and the WordPress admin out of sight

The client is the difference

For a developer building their own site, the Site Editor may be all they need. For an agency handing a site to a client, the question is different: what does the client see on Monday morning? With FSE, the answer is the WordPress admin — posts, pages, plugins, appearance, settings — and the block editor with every block WordPress has. That is a lot of surface for someone who wants to change a phone number.

A theme builder with a client area answers the question differently: the client sees a dashboard with the things they need, edits pages with the same blocks the designer used, and never learns that WordPress is underneath. WordPress client area and white label describes what that looks like.

Side by side

The short version:

  • Templates for header, footer, single, archive, search, 404 — both
  • Several templates of one kind with conditions — theme builder
  • Design tokens for the whole site, light and dark — theme builder (FSE: global styles)
  • Forms, SEO, newsletter, shop, languages, cache, security — theme builder, if it is a complete one; FSE: plugins
  • A client area without the WordPress admin — theme builder
  • Part of WordPress core, no licence — FSE

Both can be true

It is not a contest. FSE is the right baseline for WordPress, and a good theme builder does not fight it — it uses the same WordPress underneath and adds what agencies and their clients need on top. ambera is built that way: its own base theme, templates with conditions, tokens for the design, 91 blocks for pages and templates alike, and a client area. What is a WordPress theme builder? has the longer list.

Monday morning.
What does the client see?

Questions

Do I need a block theme for a theme builder?

No. A theme builder brings its own templates and usually its own base theme; it does not depend on block themes or on the Site Editor.

Can I keep using the block editor for posts?

With a builder that takes over the front end, posts are laid out by the single-post template you designed; the content itself can still come from the block editor or from the builder’s own blocks, depending on the product.

Will full site editing make theme builders unnecessary?

For solo sites, perhaps. For sites that someone else has to run, the client area and the included features are the reason to use a theme builder, and FSE does not address either.