Automattic is Testing an Experimental Full Site Editing Plugin

Automattic is working on a new experimental Full Site Editing plugin aimed at enhancing the page creation workflow in the block editor. Starting a new page from scratch may be overwhelming for those who don’t have a vision for how to tastefully put blocks together to lay out the page. This is a problem that this experimental plugin may be able to solve.

Full Site Editing currently provides three custom blocks for post content, templates, and a blog posts listing. The Blog Posts Listing block expands upon core’s Latest Posts block to include an excerpt and meta information.

The plugin is available in the WordPress Plugin Directory, although it is somewhat difficult to find when searching in the admin plugin installer. The most recent 0.1.1 version of the plugin seems to be broken, but if you roll back to the initial release, you can see some of the page template experiments. After activating the plugin, navigate to Pages » Add New and a new modal with a template selector should pop up.

The templates come pre-filled with demo content and images, so the user doesn’t have to think about how to configure the blocks to match the demo.

The functionality in Full Site Editing is being developed for use on It makes sense for a network that regularly onboards new bloggers and site owners. It is in the company’s best interest to deliver the fastest possible site creation experience, rather than have new users get frustrated and confused about how to get started.

A template selector for creating new pages could also be useful for the broader WordPress community. Plugin developer Jeffrey Carandang tested Full Site Editing and suggested that it might be useful to add this functionality to Gutenberg with custom hooks so that developers can add their own custom templates. This would make guiding users through the new theme setup process much easier for theme shops.

Automattic has a label on the Calypso repository dedicated to categorizing issues in the full site editing project. The plugin is going to be enabled on a small set of sites for initial testing. There are quite a few issues that still need to be ironed out, including things like preventing users from deleting the header and footer and finalizing the theme used with the plugin. At the moment, the plugin seems to be tailored specifically to the Twenty Nineteen theme and the pre-filled templates do not look as good when used with other themes.

The functionality included in the Full Site Editing plugin may also be coming to Jetpack. Automattic’s developers are currently researching the best way to include it, since so far it has been developed as a separate plugin and not geared towards becoming a Jetpack module.

Full Site Editing is not recommended for use in production, as it’s still under active development. The plugin’s details explicitly state that it is “only designed to work on the environment and could break after an update.” Check it out if you want to explore some exciting new possibilities for how the block editor can work together with themes to make page creation more approachable for users.


22 responses to “Automattic is Testing an Experimental Full Site Editing Plugin”

  1. Good luck to the team working on this, but they’ve got a hell of a long way to go before it can compete with Divi or Visual Composer.

    However, if they can make it faster than DIvi it will certainly get my vote. I’ve been using Divi for a few years now after switching from Visual Composer, but with every update they add in, Divi seems to get slower and slower when saving pages.

    Divi also starts to crawl once you’ve got more than 20 or 30 pages in your website (probably because of the way it compiles CSS)

  2. That is more full page editing than full site editing. I was hoping to edit menu, header or something. This seems to be like pre-built templates in Elementor.

    Anyway, it’s a great feature for Gutenberg users.

  3. I remember when Headway 2.0 came out (10 years ago now, I think), and had a site builder feature from the off, where you basically just uploaded your logo, and it would brand the design based on the logo colours.

    That was a game-changer at the time. Surprised no-one’s continued to build upon this, and really make creating sites from scratch super easy.

  4. I like the direction in concept. Page templates for blocks is already supported so a user interface to select a template seems like a natural evolution. Clients have always tended to find pages amorphous, especially if creating one from scratch. So having a template you can load in association with the pages creation helps add context. I’ll be interested in seeing how it evolves.

  5. I am hoping this is a joint cooperation with Gutenberg and Automattic. Developing full site editing can at the same time also have a very good influence on the development of Gutenberg. As new specific features might need to be focused on now rather then later.

    Here is an Gutenberg issue from over a year ago in regards to:
    “Starting out blank or with selecting a template layout.”

    As it shows some initial thoughts on how to begin with a preexisting page layout. It would be great to continue this exploration with the Automattic team who are working on the full site editing experience. There will naturally be many overlapping features that should be worked on as a joint project.

    It would be good to have a discussion about this project during one of the core-editor open office Slack meetings.

  6. Nothing this exciting and groundbreaking happened to WP in years then suddenly it’s all kicking off! Struggling to keep up. At the end of the day – as long as our clients benefit from easier editing then it can only be a good thing!


Subscribe Via Email

Enter your email address to subscribe to this blog and receive notifications of new posts by email.

%d bloggers like this: