---
title: Content-only block editing
description: The upcoming WordPress 6.1 release introduces a content-only editing feature, simplifying the editing experience by limiting block controls.
doc_version: current
last_updated: '2026-03-31T09:55:26.000Z'
date: '2022-09-27T12:24:01.000Z'
author: Rich Tabor
summary: The upcoming WordPress 6.1 release introduces a content-only editing feature, simplifying the editing experience by limiting block controls.
tags:
  - Gutenberg
  - WordPress
published: true
type: blog
url: /content-only
canonical: https://richtabor.com/content-only
id: 2351
---

As WordPress blocks—and therefore patterns—continue to expand in scope, the need for a simplified editing experience is more present than ever. Sure, the new tooling is nice — like [fluid typography](/fluid-typography-block-themes/), new spacing controls, element hover color support, padding, layout, etc — but it’s also quite a lot to take in.

Cue the new template locking mechanism for making only content blocks (text and images) editable within a pattern, landing in the upcoming [WordPress 6.1 release](https://wordpress.org/news/2022/09/wordpress-6-1-beta-1-now-available/).

## Content-only vs. block locking

First off, content-only editing **is** **different** from standard [block locking](https://wptavern.com/wordpress-6-0-to-ship-new-block-locking-feature). Block locking refers to disabling a block from either being moved, or removed entirely. It doesn’t consider the _type_ of block, or editor experience of that block. Content-only editing is a mechanism designed to be used more-so at the [pattern](/patterns/) level (one atomic level up from a block).

When applied to a block pattern, all content blocks nested within continue to be editable, but moving and removing is disabled, and all design controls are hidden—leading to a much cleaner interface.

One where there’s not tens of options in the block inspector sidebar, and the normal nested block interaction layers are fused into one. Just check out this before and after views, with content editing applied to the pattern’s top-level group block:

![](https://i0.wp.com/rich.blog/wp-content/uploads/2023/01/825b5-comparison-1-1.png?ssl=1&resize=1600%2C1200)

_Without Content-Only_

![Selecting a locked pattern with editable content only.](https://i0.wp.com/rich.blog/wp-content/uploads/2023/01/c8023-detail-1.png?ssl=1&resize=1600%2C1200)

_With content-only_

It’s astounding really. _Much_ simpler. You click on a heading block to edit its text—regardless of how nested the heading is. And instead of having all the color, typography, dimensions, or any other control, you see a list of editable content blocks. That’s it.

![](https://i0.wp.com/rich.blog/wp-content/uploads/2023/01/4d8c2-modify.png?ssl=1&resize=1600%2C1200)

_turning off content-only locking_

But if you want to switch back to the full-blown editor view—where all block controls are available—you can do so by pressing the “Modify” toolbar control at the top-level block. Press it again and you’ll see the simplified view once again.

## How to enable content-only editing

The new mechanism stems from the existing `templateLock` attribute. Editing a pattern with an `"templateLock": "contentOnly"` attribute at the top-level group block, will enable content-only editing for that particular pattern. There’s not a way to enabling content-only editing within the block editor (at least not yet), so you’ll have to manually add this to the actual [pattern code](/patterns/).

[Here’s a gist](https://gist.github.com/richtabor/ddeea41ced691721318649bea8ce9db8) of the code I used for this post.

I see content-only editing becoming a valuable tool particularly for agencies and freelancers, who can more precisely control the design and layout of block patterns—while also enabling users (whether internally or clients) to change images and text. Even block toolbar controls are condensed when content-only editing is applied.

![](https://i0.wp.com/rich.blog/wp-content/uploads/2023/01/3cf67-edit-text.png?ssl=1&resize=1600%2C1200)

_Editing content blocks with content-only editing applied._

I’m all for simplifying the WordPress block editor experience, while also enabling those who need the additional design tooling. Content-only editing seems a solid mix to support no/low-code WordPress users, as well as professionals who rely on all the [cool new stuff](https://twitter.com/richtabor/status/1529184555692961795?s=21&t=4faLV96jhTwZoBKP-xIu4w).

What’s your take? I’d love to hear it.

## Sitemap

[Full site index](/sitemap.md)