Black FridayCyber Monday 2026
14Days
15Hrs
04Mins
21Secs
Flat20% OFF

Our biggest sale of the year20% off the first payment on all maintenance plans. Code BF2026

Grab the deal
Gutenberg

Site Editor and theme.json: A Plain-English Guide for Owners

The Site Editor and theme.json can confuse business owners. This plain guide explains templates, styles, patterns and what to leave to a developer.

wpallsolution 5 min read

WordPress full site editing is the way of designing your whole site, including header, footer and page templates, with blocks instead of fixed theme files. The tool for it is called the Site Editor, and a file called theme.json sets the rules behind it. If you run a business site, you do not need to know the code, but you do need to know what each part does so you can decide what to change yourself and what to hand to a developer. This is a plain-English guide.

Quick answer

The Site Editor is available only when you use a block theme. Open it from Appearance, then Editor. It has areas for Navigation, Styles, Pages, Patterns and Templates. Use Styles for colours, fonts and layout, template parts for headers and footers, templates for page layouts such as posts or the 404 page, and patterns for reusable sections. theme.json is a settings file in the theme that defines the default colours, fonts, spacing and which options editors see. A developer usually edits it.

How this guide was prepared: it is research-based. We used the WordPress Site Editor documentation listed under Sources, checked on October 23, 2026. The interface changes between versions, so your screens may differ slightly.

What is in the Site Editor

  • Styles: change colours, typography and layout for the whole site, or for specific blocks. You can also pick style variations offered by your theme.
  • Pages: edit page content inside the Site Editor.
  • Navigation: browse and edit menus.
  • Patterns: manage reusable block layouts and template parts.
  • Templates: the layouts for each type of page, such as home, single post, search results and 404.

Changes to a header or footer apply to every page that uses it, not just the page you were on.

The decision tree: can you use the Site Editor?

Flowchart for deciding how to use the WordPress Site Editor: five questions about block themes, styles, template parts, patterns and theme.json
Five questions point you to the right tool.
  1. Does your site use a block theme? If not, the Site Editor will not appear (Step 1).
  2. Do you need to change colours, fonts or layout? Use Styles (Step 2).
  3. Do you need a new header or footer? Edit template parts (Step 3).
  4. Do you want reusable layouts? Use patterns (Step 4).
  5. Do you need site-wide rules? Ask a developer about theme.json (Step 5).

5 steps to use it safely

Step 1: Check that you have a block theme

Go to Appearance. If you see Editor in the menu, your active theme supports the Site Editor. If you see Customize and Menus instead, you probably use a classic theme. Moving between the two is a project, not a toggle; see our migration checklist.

Step 2: Use Styles for design changes

Open Appearance, Editor, then Styles. Try a style variation, or change the colour palette, typography and layout. The three-dot menu lets you review revisions or reset your changes. Because these changes apply site-wide, preview them before saving.

Step 3: Edit headers and footers as template parts

Go to Patterns, then template parts, choose Header or Footer and edit it with blocks. Add or remove logos, menus and links, then save. Check on a phone afterwards, because layouts that look fine on a desktop can wrap badly.

Step 4: Use templates and patterns for consistency

Templates define the layout of page types; patterns are ready-made groups of blocks you insert anywhere. Synced patterns update everywhere when you change them, which is useful for a call-to-action box used on many pages. Keep your own patterns named clearly.

Step 5: Leave theme.json to a developer

theme.json is a configuration file in the theme folder. It sets default colours, font sizes, spacing, layout widths and which controls editors can use. Editing it by hand needs care, because a typo can break styles. Changes you make in Styles are stored separately as your customisations. If you want consistent brand rules for your team, a developer can set them in theme.json; see our block theme development service.

Version and hosting differences

  • Menu names and screens change between WordPress versions.
  • Some plugins add settings inside the Site Editor or may not support it.
  • Page builders and block themes do not mix well on the same pages, so choose one approach.

How to verify your changes

  • Preview on desktop, tablet and phone before saving.
  • Check that header and footer changes look right on several pages.
  • Take a backup before large changes so you can restore.
  • Use the revisions or reset options if a style change goes wrong.

Common mistakes

  • Editing a template part without realising it affects every page.
  • Changing styles on the live site with no backup.
  • Installing a block theme without testing your plugins.
  • Editing theme.json without a copy of the original.

Frequently asked questions

Is full site editing the same as Gutenberg?

Gutenberg is the block editor project. Full site editing extends blocks to headers, footers and templates.

Can I use the Site Editor with any theme?

No. The Site Editor is available only with a block theme.

Do I have to edit theme.json?

No. Most owners work in Styles and leave theme.json to a developer.

Will my content change if I change Styles?

Your text stays the same, but the appearance of blocks across the site can change.

What to do next

If you already have a block theme, open Appearance, Editor and explore Styles on a staging copy first. For help with custom block themes see block theme development, or contact us. Also see custom blocks vs page builders.

Sources and official documentation

Keep reading

More guides

Gutenberg

Custom Blocks vs Page Builders

Native WordPress blocks or a page builder like Elementor? An honest comparison of speed, editing, lock-in and maintenance, and how to choose.

Need a hand with this?

Tell us what is happening. We reply with honest next steps.

Talk to us