BLOCKS OR BUILDERWordPress site buildingIf your team edits the website every week, the way it is built decides how much they can change, how easily the layout breaks and how hard it is to move on later. On WordPress today that choice usually comes down to two approaches: a block theme edited in the Site Editor, or a page builder such as Elementor Pro on top of a theme. Both work. They suit different teams.
What is a block theme, in plain terms?
A block theme is a WordPress theme built entirely out of blocks, the same blocks your editors already use in posts and pages. Its templates are HTML files made of block markup rather than PHP. WordPress only requires style.css and templates/index.html. Most themes also add a parts folder for template parts such as the header and footer, a patterns folder for reusable layouts, and a theme.json file that configures colours, typography and other settings and styles for the whole site.
With a block theme active, the Site Editor opens under Appearance > Editor. From there you can edit templates, template parts, styles, navigation and patterns, and export the theme as a zip file with your changes included. The Site Editor is only available with a block theme.
How does Elementor's Theme Builder compare?
Elementor's Theme Builder is part of Elementor Pro and covers the same ground: headers, footers, post templates, archive templates and other theme parts, designed in Elementor's own drag and drop editor. Display conditions decide where each template appears, such as the entire site, posts in one category or a specific page. Elementor says these templates append and override the current theme's page hierarchy, layout settings and CSS styles.
The editing experience is the main draw. Designers get fine visual control, motion effects, popups and a form builder in one interface, without writing code.
Which one keeps editors from breaking the design?
A block theme gives you more guard rails out of the box. In theme.json you register the colour palette and font size presets, then decide whether people may go beyond them. Three settings we look at on every build:
color.custom: whether users can select custom colours outside the palette.typography.customFontSize: whether users can set their own font sizes.spacing.customSpacingSize: whether users can set custom spacing sizes.
Patterns can be locked as well. A container with templateLock set to contentOnly lets editors change text and media but not the design settings inside it. Synced patterns update everywhere they are used, which suits a call to action or contact block that appears on many pages.
Page builders can be kept tidy with global colours, fonts and saved templates, but the editor is designed for freedom. In our experience, that freedom is where inconsistency creeps in once several people edit the same site.
What about speed?
Neither choice guarantees a fast site, so we test the real templates in PageSpeed Insights before launch rather than trusting a label. A block theme has no separate builder plugin rendering the page: templates are block markup that WordPress renders itself. Elementor has added performance features of its own, such as Element Caching, which renders a widget once and reuses the cached output on later page loads. Either way, images, fonts and third-party scripts need the same care.
What happens if you change your mind later?
Lock-in is the trade-off buyers ask about least and feel most. Block content is saved as HTML in the post content, with block details kept in HTML comments, so a post remains mostly intact even if it is shown without the block editor. A block theme is also an ordinary theme folder you can export.
Elementor layouts depend on the plugin that made them. Elementor notes that a Theme Builder setup cannot be exported as a theme zip in the way a hand-coded theme can, although its Import/Export tools move settings and content between sites. If a Pro subscription is not renewed, you can no longer update Pro or add Pro features, and access to existing Pro features may be limited, while anything built with the free version keeps working. Weigh that dependency before you commit.
So which should you choose?
- Choose a block theme when several people edit content, brand consistency matters more than per-page creative freedom, and you want the site to stay close to core WordPress.
- Choose Elementor Pro when one trained designer owns the site, campaigns need quick visual changes, popups and forms, and the team accepts a long-term dependency on the plugin.
- If most of the site is structured content, such as case studies, locations or team members, the content model is the bigger decision, not the builder.
Where to start
List who edits the site, what they change each month and what must never change. That list usually makes the answer clear. If you want a second opinion on an existing build, start with a website review, or see how we approach WordPress development.
FAQ
Frequently asked questions
Can we use the Site Editor with our current theme?
Only if it is a block theme. The Site Editor is available when a block theme is active, while classic themes keep their PHP templates and are customised in other ways, such as the Customizer. The block editor for posts and pages works with both, so your content can move to blocks before the theme changes.
Is Elementor's Theme Builder included in the free version?
No. Elementor's free version includes the visual drag and drop builder, while the Theme Builder for headers, footers, post templates and archive templates is an Elementor Pro feature. Check Elementor's current free and Pro comparison before planning a build, because the split between versions can change over time.
Can we move an Elementor site to a block theme without rebuilding it?
Not automatically. Elementor templates are built in Elementor's own editor and rely on the plugin, so pages are normally rebuilt with blocks and patterns. Plan it like a redesign: list every template, rebuild the shared parts such as the header and footer first, keep URLs the same and redirect any that must change.
Can editors still break a block theme layout?
They can if nothing is locked. Register brand presets in theme.json and switch off custom colours and sizes, lock key blocks so they cannot be moved or removed, and use content-only patterns for sections where only the words and images should change. Then give editors a one-page guide to the patterns they should use.
Who should own changes to theme.json?
Treat it like code. theme.json configures settings and styles for the whole site, so changes should go through whoever maintains the theme, be tested on a staging copy first and be kept in version control. Editors work on content; the person responsible for the design system adjusts the presets.
