WordPress 6.3 Development Kicks Off to Conclude Gutenberg … – WP Tavern
The WordPress 6.3 development cycle has begun and work is already underway on an ambitious list of features that will debut in the upcoming major release. It will cap off Phase 2 of the Gutenberg project, with an emphasis on polishing customization features and making them easier to use.
WordPress 6.3 Editor Triage co-lead Anne McCarthy published a roadmap to 6.3 this week, which summarizes what users can expect:
This release aims to make it easier for users to edit pages, manage navigation, and adjust styles all directly in the Site Editor. It also seeks to provide detailed, relevant information when exploring different parts of the site, such as showing the number of posts per page when viewing relevant blog templates.
In addition to polishing and wrapping up phase 2, McCarthy’s post outlines the new features that are coming. Here are a few of the highlights:
This is a tentative glimpse at some of the user-facing features that may be coming in WordPress 6.3, but the roadmap includes many more items, screenshots, and quick demos.
“As always, what’s shared here is being actively pursued, but doesn’t necessarily mean each will make it into the final release of WordPress 6.3,” McCarthy said.
Gutenberg Lead Architect Matías Ventura will be leading WordPress 6.3. Beta 1 is expected in a little more than a month on June 27, 2023, with RC 1 on July 18, and the general release scheduled for August 8.
Has the issue with 6.2.1 and shortcodes been resolved? If not, why are we thinking about 6.3? Or was the end of shortcodes intentional and just not communicated well? I have a plug-in that I am afraid to update because of the “not tested with 6.2.1” message, and would like to be able to update that confidently before even thinking about 6.3.
Yes, I am a slow-to-adopt amateur—but I don’t think I am alone.
It has not been resolved yet. I think they are discussing in a private channel since it’s security related. I will report on it as soon as they communicate more. Hoping for a quick release that helps people be able to upgrade without a lot of hassle because there are a lot of vulnerable sites out there right now. 😬
Thanks for the quick reply!
Is there no push for more responsive controls?
It’s a major missing element for me, the inability to look at a preview and scale up and down and set the font sizes, padding, margins etc. of blocks and families of blocks.
There are other big things missing but that’s one which still keeps me away from Gutenberg as any kind of page layout tool. I don’t really want to be tinkering in a JSON file just to set a margin on a bunch of blocks when the page is narrower than 800px for example.
Which is a whole other topic. the Theme.json problem.
There was a suggestion that Gutenberg was going to make layouts easier, with less scripting, but anyone who has tried to wrangle a huge nested JSON file knows it’s now a lot more painful than it used to be!!
Agree, intrinsic design sounds sexy and works well well in a code editor with full CSS Grid access, but it doesn’t work well in a page builder, and even less without a tricked out CSS Grid UI. Even Webflow who are known to have one of the best UI CSS Grid implementations still use overrides.
OllieWP has a solution though: https://olliewp.com/a-native-and-iterative-approach-to-responsive-control-in-wordress/
Advanced responsive control is must-have feature on every pro page builder.
I’m comfortable with designing on Gutenberg for simple pages, but when I need something more then check result on my tablet, it makes me crazy.
So no 6.2.2? I hope it is fixed by 6.3 if there is no 6.2.2.
6.2.2 was released today.
6.2.2 just came out
6.2.2 obviously breaks new things:
That is what happens with fixing things on the fly, I imagine. Please focus on resolving this issue before doing anything with 6.3. Yes, it may be different people, but their skills could be better used for fixing 6.2, right? For the good of the project, of the community? More time in beta is a good thing; more issues can be found before we amateurs are faced with something above our pay grade—and as much as developers might like the income from fixing broken sites, we all would prefer to be creating new things (and grassroots groups like mine, with part-time volunteers only, cannot afford a professional and struggle to keep up).
Your email address will not be published. Required fields are marked *
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