With WordPress 5.9 only just stepping its toes out the door and greeting the world, the lead developers seem to have hardly taken a moment to catch their breath. Yesterday, Matías Ventura posted the preliminary roadmap for 6.0. It covers the general scope of the planned features to land this year.
Version 6.0 is expected to be a conceptual wrap of Phase 2 of the Gutenberg project, covering the visual site-building tools. They will continue playing a crucial role in future development, but developers will likely shift much of their focus to Phase 3 for WordPress 6.1 and beyond.
The following are the four phases outlined in the long-term roadmap:
Ventura listed 10 high-level focus areas around the post and site editors in core WordPress. They range from big-ticket items like a site-browsing mode to a more back-to-basics approach to the writing experience. I will focus on some things I most look forward to.
I have a running list of features that I cannot wait for. It seems that I find something new to add to it every other day or so. However, global styles variations would easily land in the top three.
The feature was expected but did not quite make it into WordPress 5.9. The goal was to allow users to select from multiple presets, transforming their site’s colors, fonts, and more at the click of the button. Several variations for Twenty Twenty-Two are already in progress.
This is sort of like a light version of child theming where only the
theme.json file can be switched around. Essentially, they are skins.
This will most likely be one of the most crucial features of wrapping up Phase 2 of Gutenberg. Some pieces of it can be tough to follow, but several screenshots and videos are in the associated ticket.
Essentially, the goal is to refine the experience of moving around and interacting with the site editor, global styles, templates, and navigation. The work in 5.9 was stellar, but now there is a need to create a more intuitive interface.
Part of this is exposing the site structure as navigation outside the Navigation block in the UI. Users can currently only edit this from within the site canvas.
Such things are easier said than done, so contributors will have their work cut out for them. It will take a community effort.
There is currently a limited number of templates that users can create through the site editor interface. For example, they can add an archive design but not break that down for specific types of archives (e.g.,
category) or slug-based versions of them (e.g.,
Eventually, the site editor should allow the creation of any possible template from the template hierarchy. Presenting that in an easy-to-use interface will be a challenge. The hierarchy is limited only by the number of objects (posts, terms, etc.) on a site.
The other piece of the template-creation process is decoupling them from themes. Users should never lose their customized templates when switching from one to another. This becomes even more vital as plugins begin to introduce block templates.
Since their introduction alongside WordPress 5.5, patterns have been one of the most powerful tools available to users. I have been telling anyone who will listen that they will be a game-changer for at least two years. WordPress 6.0 might just make good on my promise.
One proposal would make patterns a central part of template and page building. Several pieces to this may fit into various flows, but one of the overarching goals should be for end-users to figure out what to do with an empty template or page. If done right, patterns can help them get off the ground running.
A proposal to transform existing content sections with patterns is also on the table. I wrote about how this was a missing component of the user experience earlier this week.
For theme authors, pattern registration may become less complex. Currently, they must use the Patterns API to register them via PHP. However, there is a proposal for WordPress to automatically recognize them. Patterns would most likely live in a dedicated
/patterns folder in the theme and be registered similar to page templates. However, the final solution has yet to be determined.
There is an array of block-related enhancements to look forward to. Much of that will revolve around continued iteration on the Navigation block. Theme authors should also have more blocks for controlling the output of comments.
However, let me dive into some of the features I am most looking forward to.
Instead of superpowers, this would cover the use cases already possible in traditional theming. As much as I like block themes, one of the most glaringly-obvious issues is the Post Featured Image block. Essentially, it currently outputs the
post-thumbnail image size.
Theme authors can set the width and height but not use cropped sizes that they have registered (fixed in the dev version of Gutenberg). They also cannot use it within the context of other blocks like Cover and Media & Text.
Beefing up featured image capabilities will hand over much-needed design tools to theme authors. Right now, the missing features are blockers for many layouts.
If there has been one feature I have seen developers ask for more than most, it is the ability to output dynamic data within blocks or HTML templates. Some of this is solved with the Pattern block, but it does not cover every use case.
For example, there is no way to output the current date within a paragraph. This is a routine use case for the site footer copyright line. More typical is grabbing dynamic URLs to theme or plugin resources like images. Ventura noted in the post that they would explore the viability of inline tokens in this release cycle.
There may be a Table of Contents block on the way. It has been just under a year since I first wrote about such a proposal, so I am eager to see this land.
The Quote and List blocks should finally allow child blocks. Both are severe limitations that were always possible in plain HTML and the classic editor. I know more than a few bloggers who will be happy to see this happen.
Improvements to the Table block are also likely coming. At the moment, it offers a poor user experience — users cannot even tab through cells. At most, it handles the most basic of use cases. Currently, there are over two dozen open tickets to clean it up.
Several components should make theme authors, in particular, excited about 6.0. We could be looking at new height and width controls for more blocks, providing more flexibility in theme designs. And using
max CSS features along with flex-based containers could make fine-tuning responsive designs easier.
On the typography front, there is a ticket for introducing responsive fonts. This is relatively easy to handle with custom CSS at the moment if a user chooses a theme’s predefined size. However, with custom sizes and line-heights, it is problematic. Because these tools exist in WordPress, we need responsive handling baked in.
One long-awaited typography feature is likely to launch in this cycle: the Web Fonts API. After being pulled from WordPress 5.9, it is now being developed within Gutenberg. I expect this to land sooner rather than later because the bulk of the code is finished.
Support for customizing captions across various blocks and possibly finding a solution for link hover and focus states are also on the slate for 6.0.
What features are you looking forward to the most in WordPress 6.0?
Just a friendly plug that if reading this post got you excited about the future and you want to be part of shaping what’s to come, check out the FSE Outreach Program: https://make.wordpress.org/test/handbook/full-site-editing-outreach-experiment/
All are welcome and so much feedback is needed!
P.S. I am most excited about all things templates: extending what templates can be created, allowing them to be preserved when switching themes, incorporating patterns better into creating a new template, etc.
The featured image functionality would be such a huge win for 6.0. Such a good way to frame up the need. Opens up so many possibilities for layouts for Themers.
Great features but I miss some focus on performance improvements, aside lazy loading.
What about the IMPORT TOOL? when will that be updated?
humanmade or 10up did a 2.0 that is far better when will that be adopted?
InLine block editing. Metabox value insertion
Having dark theme in backend editor is so necessary. My eyes is disturbing every time I’m editing my site at night.
Definitely! I’m really looking forward to a dark theme.
Wish WordPress 6 would actually convert to a proper headless CMS while keeping backwards compatibility for themes. Headless is the way to go; it lowers security vulnerabilities, sites can be faster, puts the design back in control of the developer, and the plugin system doesn’t have to be loaded when visiting a site
Looking forward with 6.0: More flexibility with typography. Using different fonts or different font size in the same paragraph block (or the same headline block). And also be able to put todays date etc. in a paragraph block.
This is something that does not necessarily have to be integrated in the core. You can use a within a
and style it with (beginner level) CSS.
I appreciate some of the new features have that been added to full-site editing, but sometimes there is too much priority from core developers on creating new features instead of some polishing some long-standing issues.
For example: responsive images within Gutenberg are still largely still (visit https://github.com/WordPress/gutenberg/issues/6177)
Some of that thread comments are now out of date but I’ve outlined the next steps at https://gist.github.com/skorasaurus/a01249d4302226bf12c80dd979322303
I’m looking forward to WordPress 6!
I’m down for having a dark mode and collaboration. The latter would help put out HQ articles more quickly when devs and linguists can work together on a text simultaneously.
I love WordPress and it feels like they will eventually run page building companies such as Divi and Elementor out the door. Seems like each iteration makes it easier for beginners to create their own website/blog and this one doesn’t seem to be the exception.
I like the direction WP is taking I wonder, by looking at the roadmap (https://wordpress.org/about/roadmap/ ) how is possibly that the privacy issue is left to plugins ….
I think that wordpress should have at least a native “stop all cokies” function.
GDPR, COPA and God knows how many more are coming.
It s extremely important, and not so easy to manage at the moment.
Sorry, my HTML tags disappeared, so once again:
You can use a span within a paragraph and style it with (beginner level) CSS.
I would really like to see a better columns block. Columns are like a foundation of almost every created pattern, but currently it’s very limited. It would be great to have more columns varations, changing column width by dragging it, change columns order on mobile without adding custom CSS such as flex-direction. Paddings and margings with breakpoints for every block are needed as well. I can find all these options in several block plugins, but such basic things must be in core.
Your email address will not be published.
document.getElementById( “ak_js_1” ).setAttribute( “value”, ( new Date() ).getTime() );
This site uses Akismet to reduce spam. Learn how your comment data is processed.
Enter your email address to subscribe to this blog and receive notifications of new posts by email.
WordPress Tavern is a website about all things WordPress. We cover news and events, write plugin and theme reviews, and talk about key issues within the WordPress ecosystem…
© All Rights Reserved. Powered by WordPress, hosted by Pressable