Skip to main content

WordPress Block Themes and Full Site Editing: A Working Introduction

If you've logged into a WordPress dashboard recently and noticed the editing experience looks different, you're not alone. Block themes and full site editing have reshaped how WordPress sites are built and managed. This guide walks you through what block themes are, how they differ from classic themes, and how to put them to work on your next project.

Key Takeaways

Block themes are a newer type of WordPress theme, available since WordPress 5.9 was released in January 2022. They are built entirely for the block editor and full site editing, replacing much of what the Customizer and widget system handled in classic themes. Instead of PHP template files and widget areas, block themes use HTML templates composed entirely of blocks, allowing visual editing of every template directly in WordPress.

To access the site editor and full site editing features, you must activate a block theme - not just any "block-ready" classic theme. Default block themes like Twenty Twenty-Five or Twenty Twenty-Four unlock the editor under Appearance > Editor. A block-ready classic theme still limits you to editing blocks inside posts and pages only.

The practical benefits are significant. Block themes enable editing headers and footers directly, give you global styles for color palettes and typography, and reduce the need for third-party page builders like Beaver Builder in many common scenarios. WordPress block themes are also lighter and faster than traditional themes because they rely on standardized block markup and leaner CSS output. Block themes simplify website design without external plugins for most layout needs.

The main trade-offs include new workflows to learn, different theme files (HTML templates and theme.json instead of PHP files and large stylesheets), and plugin or theme compatibility considerations - especially on older sites built with page builders or legacy widgets.

Here's what this article covers:

  • What block themes are and how they differ from classic themes
  • How the site editor and full site editing work in practice
  • How to design with blocks, block patterns, and global styles
  • Creating and managing templates and template parts
  • When block themes make sense for your next project

What Is a WordPress Block Theme?

A WordPress block theme is a theme composed of block-based templates and template parts that you edit visually in the site editor, rather than using PHP templates and the Customizer like classic themes. Block themes use templates composed entirely of blocks. Every visible component - site title, site logo, navigation, header, footer, query loops, post layouts, and sidebars - is a block that you can configure through the WordPress block editor interface.

Blocks were introduced in WordPress 5.0, and they can be static or dynamic content elements. Block themes take that concept and extend it across your entire website, not just post and page content. Block themes allow editing all website parts with blocks. When you activate a block theme, it unlocks the site editor under Appearance > Editor, giving you the same block editor used for content creation but applied to your full site structure.

Theme styling in a block-based theme is largely controlled by theme.json plus global styles rather than sprawling CSS files. This leads to more consistent design controls and smaller, cleaner CSS output. Meanwhile, a "block-ready" classic theme may support the WordPress block editor inside posts and pages, but it still relies on widgets, traditional menus, and the Customizer for structural elements. Only a true block theme opens the door to template editing and the complete site editor experience.

Block Themes vs Classic Themes

The technical differences are straightforward. Classic themes rely on PHP files - header.php, single.php, index.php, functions.php - along with widgets and the Customizer. Block themes replace those with HTML template files (index.html, single.html, archive.html) stored in a templates directory, plus template parts under a parts directory. Templates in full site editing are now HTML files instead of PHP.

From an editing standpoint, the gap is even clearer. In classic themes, you modify headers and footers via the Customizer or theme options panels. In block themes, you open the WordPress site editor and drag and drop blocks directly into the layout. There's no hunting through theme-specific panels or writing custom CSS for basic structural changes.

Design control follows a similar pattern. Block themes provide global styles for colors, typography, and layout - options exposed per block and across the whole site. Classic themes often lock design behind proprietary panels or require you to add custom CSS. Block themes are particularly useful for customizing site design without coding.

When it comes to compatibility, here's the practical guidance:

  • Existing sites using builders like Beaver Builder, Elementor, or Divi can keep their current theme without issues.
  • New builds or full redesigns on WordPress 6.3+ are usually better off starting with a modern block theme.
  • Migration from a classic theme requires testing, since shortcodes, widget placements, and builder-specific layouts may break under a new theme.

According to theme directory data from mid-2026, about 86% of listed WordPress themes are still classic, but 44.2% of new submissions are block themes - a clear signal of where theme developers are heading.

How Block Themes Enable Full Site Editing

Full site editing is the collection of WordPress features - site editor, block templates, template parts, global styles, patterns, and theme.json - that let you design your entire website with blocks. Full site editing allows editing all website parts with blocks, from the header template part down to the footer.

The site editor is accessed via Appearance > Editor when a block theme is active. It displays your full site - typically the homepage - along with navigation to templates, patterns, and styles. The site editor is used for modifying templates and other site-wide styles visually.

Templates define layouts for specific views: single posts, pages, homepage, archive, search results, 404 errors. Each is stored as an HTML file containing block markup. Template parts - reusable pieces like the header, footer, and sidebar - can be edited once and applied across multiple templates. Reusable template parts allow changes in the header or footer to reflect site-wide.

Global styles act as the design layer for full site editing. Through the Styles panel, you apply color palettes, global typography, and spacing settings that cascade across all templates and site blocks. This is how site editing works in practice: one unified interface for both content and design.

Accessing and Using the Site Editor

Here's a concrete walkthrough. From a WordPress 6.5+ dashboard:

  1. Go to Appearance > Themes > Add New.
  2. Filter for "Block Themes."
  3. Install a block theme (e.g., Twenty Twenty-Five).
  4. Activate it.
  5. Click Appearance > Editor to open the WordPress full site editor.

You'll encounter two main views: a visual editor showing your site preview where you can manipulate blocks directly, and a left-hand panel for switching between Navigation, Pages, Templates, and Patterns.

Key toolbar options worth knowing:

  • List View for navigating nested blocks
  • Visual vs Code editor toggle (the code editor shows underlying block markup)
  • Spotlight Mode and Distraction Free mode for focused editing
  • Preferences for customizing your editing environment

The visual editor lets you drag and drop and configure individual blocks, while the code editor exposes the raw HTML for more technical users who prefer working with block markup directly.

A good first task: replace your site title with a custom logo block, rearrange the navigation menu, and edit the footer text. You'll see how fast structural changes happen without touching any PHP files.

Designing With Blocks and Block Patterns

Blocks are the fundamental building units of the new WordPress block editor. Core blocks include paragraphs, images, buttons, groups, columns, navigation, query loop, and specialized theme blocks like Site Title, Site Logo, and Post Template. You can also find new blocks through plugins or create your own.

Block patterns are pre-built groups of blocks that can be reused in block themes. Think hero sections, pricing tables, feature grids, and testimonial layouts. Block patterns create predefined complex layouts for websites, dramatically cutting down the time it takes to create pages and templates.

To insert a pattern:

  1. Open the block inserter (the "+" WordPress icon in the toolbar).
  2. Switch to the Patterns tab.
  3. Browse categories like "Headers," "Call to Action," or "Testimonials."
  4. Click to insert into your template or page.

Many block themes ship with their own patterns - and sometimes full page patterns - that match the theme's design system. Reusable blocks allow you to save and reuse styled content across your site. Reusable blocks also support change history for easier management, so you can track revisions over time.

Avoid overloading your site with pattern libraries from multiple plugins. Stick to a small, coherent set of patterns that align with your design system. Too many options create visual chaos and bloat the editor interface.

Global Styles, Color Palettes, and Typography

The Global Styles interface is accessed via the "Styles" icon (often an "Aa" or half-circle) in the site editor. From here, you can switch style variations, adjust colors, change typography, and configure block-level style settings for the entire website.

Global styles allow site-wide color and typography changes. Block themes define a base palette plus optional style variations - light, dark, high-contrast - and changing a primary color instantly updates buttons, links, headings, and other global elements across all templates. Global styles can be applied to all blocks in one interface, and they apply to all blocks that support the functionality.

Global typography controls let you set default fonts, weights, sizes, and line heights for headings (H1–H6) and body text. This replaces many Customizer typography panels from other themes. Global styles standardize styling tools for easier customization, and they simplify the styling process across the website. Global styles can be edited from a single interface, giving you a centralized place to manage your entire site's visual identity.

Per-block design options let you fine-tune spacing, borders, and font style settings for individual blocks, then optionally apply changes globally for all blocks of that type. Block themes support global styles for consistent design changes across your whole site.

Quick example: In a default Twenty Twenty-Five install, open Styles, change the heading font to a serif typeface, and swap the button background color to your brand's primary shade. Two clicks, and every heading and button across your WordPress website updates instantly. That's the power of default styles flowing from one centralized panel.

Creating and Managing Templates and Template Parts

Templates define how specific views are structured. A "Single" template controls how individual posts appear. A "Page" template handles static pages. An "Archive" template governs category and tag listings. Each uses blocks like Query Loop, Post Title, Post Content, and Post Meta to build the layout.

To browse and edit existing templates, navigate to the site editor's Templates section. Open a template like "Single" or "Page," then rearrange blocks, add sidebars, or adjust the post meta layout - all visually. You can also create custom templates: click "Add New," choose a template type (e.g., "Single Post" or "404"), and design it with blocks and patterns. Custom templates can be assigned to specific pages or custom post types from the page editor sidebar.

Template parts are reusable components - header, footer, sidebar - that appear under "Patterns" or "Template Parts" depending on your WordPress version. Changes to a header template part propagate everywhere it's used.

Practical workflow: Create a new footer template part with social icons and a secondary navigation. Assign it across all your other templates. Use global styles so it automatically inherits your color palettes and typography. No CSS required.

Working With Block Themes Alongside Page Builders

Many WP sites rely on page builders like Beaver Builder, Elementor, or Divi. Full site editing doesn't disable these tools - they continue working with compatible themes and remain part of the WordPress ecosystem.

The typical recommendation: for existing sites heavily built with a page builder, keep a classic or builder-friendly theme. Block themes are better suited for new builds or full redesigns that plan to lean on the WordPress editor natively.

Hybrid setups are also viable. You can use a block theme for overall structure and global styles while employing a page builder on specific complex landing pages, provided both are compatible.

From a performance and maintenance perspective, fewer overlapping layout systems leads to simpler upkeep and better performance. Mixing multiple builders with FSE creates confusion about which tool controls what.

Always test theme switches on a staging or local environment. Verify that layouts, shortcodes, and widgets behave as expected before going live.

Building Your Own Block Theme: Files and Workflow

The basic anatomy of a custom block theme is straightforward:

File/FolderPurpose
style.cssTheme metadata (name, author, version) - can be nearly empty for CSS
theme.jsonSettings (color palettes, layout widths, typography) and default styles
templates/HTML template files (index.html, single.html, archive.html)
parts/Template parts (header.html, footer.html)
functions.phpOptional - for enqueuing scripts, registering block styles, or adding theme supports

Theme.json version 3 is currently used in WordPress block themes. It defines available controls, design defaults, and block settings in a structured JSON schema. The theme.json documentation covers its top-level properties: version, settings, styles, customTemplates, templateParts, and patterns.

Starter workflow: Duplicate an official block theme like Twenty Twenty-Five. Rename it, adjust theme.json for your brand colors and global typography, then progressively replace templates and template parts with your own block markup. This is faster than starting from scratch and teaches you the architecture through hands-on modification.

Practical Tips, Limitations, and Gotchas

Tips for cleaner builds:

  • Keep your plugin count low and rely on core blocks over third-party alternatives.
  • Standardize on one design system per site - mixing pattern libraries creates inconsistency.
  • Use the premium version of reputable block plugins only when core blocks genuinely can't meet the need.

Current limitations (WordPress 6.5–6.6):

  • Some niche plugins don't fully support the site editor or block theme environments.
  • Complex legacy widgets may need refactoring. The classic editor compatibility layer helps, but it's not seamless.
  • Advanced layout needs - highly interactive pages, complex forms - may still justify a dedicated builder or custom blocks.

Troubleshooting basics:

  • If the site editor is missing, verify that a true block-based theme is active.
  • If global styles don't apply, check theme.json for syntax errors and clear all caches.
  • Check support forums for your specific theme - the WordPress community is active and helpful.

WordPress block themes paired with lean plugins typically generate cleaner markup than heavy multipurpose classic themes, but overusing patterns and new blocks from third-party sources can still degrade performance. Keep WordPress core and block-related plugins updated to benefit from new features and iterative improvements.

Choosing a Block Theme for Your Next Project

Start your evaluation with concrete candidates. Twenty Twenty-Five offers a clean, flexible starting point. The Extendable theme by Extendify has crossed 200,000+ active installations by providing strong documentation, bundled patterns, and style variations. Look for themes that match your use case - whether it's a personal blog, portfolio, or simple WooCommerce store.

Selection criteria to prioritize:

  • Active maintenance and responsive theme developers
  • Clear documentation and theme options
  • Thoughtful style variations and robust block patterns
  • Compatibility with key plugins (SEO, caching, e-commerce, forms)

Preview any new theme safely by installing it on a staging site. Import demo content if available, test the site editor, global styles, and templates before deploying to production. For e-commerce, ensure the block theme provides templates for product archives, single products, carts, and checkout.

Start with a small site - a personal blog or a subsection of a larger project - to build confidence with site editing themes before migrating mission-critical properties.

Conclusion: Why Block Themes Are the Future of WordPress

Block themes, the site editor, and global styles represent the long-term direction of WordPress. They unify content creation and design in one consistent interface, powered by the same block editor used everywhere. The WordPress team continues shipping improvements each release - from the block bindings API to enhanced pattern management - all targeting the block theme architecture.

The advantages compound over time: faster visual iteration, fewer hard-coded template changes, better alignment between the visual editor and front-end output, and an easier on-ramp for non-developers to manage full site layouts across their whole site. The latest WordPress default themes, including Twenty Twenty-One which is block-based, signal the platform's commitment to this direction.

Classic themes and traditional page builders will remain part of the WordPress ecosystem for years. But learning block themes now is a wise investment for both site owners and theme developers. Spin up a test site, install a block theme, explore the site editor, experiment with color palettes and global typography, and gradually adopt full site editing in your workflow. The learning curve pays off quickly - and what you find this article helpful for today will only become more relevant as WordPress core continues evolving.

FAQ

Do I have to switch to a block theme to keep using WordPress after 2026?

No. Classic themes and older customization methods will continue to work for the foreseeable future. However, new features in WordPress core increasingly target block themes and full site editing first. It's smart to plan a medium-term transition strategy - test block themes on staging sites or new projects - so you aren't locked into aging, unmaintained classic themes as the ecosystem shifts.

Can I use full site editing features with my existing classic theme?

Full site editing - including the site editor, block templates, and global styles - is only available when a block theme is active. Classic themes can use the block editor for posts and pages but do not support full site editing or template editing. Some hybrid or "block-ready" themes add extra block support, but they won't expose the full WordPress full site editor experience unless they are true block themes.

Will block themes break my content created with Beaver Builder or other page builders?

Changing themes doesn't automatically delete builder-created content. However, layouts built with Beaver Builder, Elementor, or similar tools are tied to their plugins and shortcodes and may not render correctly under a new block theme. Keep the builder plugin active when testing a block theme on a staging copy of your site. Review key pages for layout issues before considering any migration.

How do block themes affect performance and Core Web Vitals?

Block themes typically output cleaner HTML and rely on standardized shared styles via theme.json and global styles, which can reduce CSS bloat compared with heavy multipurpose themes. That said, performance still depends on your choices - too many plugins, complex patterns, and unoptimized media can slow any site. Combine your block theme with caching, image optimization, and careful plugin selection for the best results.

Is it worth learning theme.json and block templates as a developer?

Absolutely. For developers planning to build or maintain WordPress sites beyond 2026, understanding theme.json, block templates, template parts, and the site editor tooling is increasingly essential. Start by customizing an existing block theme's theme.json and templates, then progress to building a small custom block theme from scratch. The architecture is simpler than it looks once you've worked through one complete project.

Changed

Vision Newsletter

Subscribe

* indicates required
Languaje *
Choose the languaje for the newsletter.