We’re getting ready for another big improvement for our favorite CMS. Today, I’d like to share with you the release of Gutenberg version 5.3 as well as the first Beta for WordPress 5.2. And, some exciting news on the minimum PHP version requirement for WordPress.
We’ve seen the release of Gutenberg 5.3 this last week and this version is an extra interesting one. Gutenberg 5.3 will be included in the upcoming WordPress 5.2 release. The three interesting features that stand out in this release are the following:
- Gutenberg 5.3 introduces a block management modal which allows you to enable/disable blocks from the block inserter.
- We also get the possibility to nest different kinds of blocks in a Cover Block container. Allowing for more interesting uses of the Cover Block block.
- Lastly, there are many improvements to the hover and selected block states, with better a11y and less distraction.
But, that’s not all. There’s a lot more added to Gutenberg 5.3 and you can read all about it in the release post.
WordPress 5.2 Beta 1
WordPress 5.2 saw its first Beta last week, by the way. So, if you’re developing plugins and themes, now would be a good moment to start testing them against the 5.2 Beta 1.
Remember the recovery mode component intended for fixing fatal errors that ended up not making it in 5.1? Well, there’s good news about the project. As Felix Arntz’ tweet indicated last week:
The project team working on this feature have had to completely reimagine the solution. So, it may have taken a lot more time than intended, but we’re ending with a much more robust solution. A solution that’s going to save a LOT of headaches.
Bump in minimum PHP version for WordPress! Yay!
There have been years of debate about the minimum version for WordPress, but it’s finally happening. The PHP minimum version bump was finally committed – see this Trac ticket for more information. The minimum required PHP version is 5.6. This means we can finally start working towards using modern implementations of PHP, like Namespaces, for WordPress.
Subtle but important change with setting up a WordPress.com site
One of the things that never looked good when setting up a site over at WordPress.com was the default
wordpress.com subdomain you would get. It doesn’t really cover the intent whatsoever in my opinion. I also wouldn’t mind their identity being less confusing towards WordPress.org sites.
Anyway, I was very happy to see the default URL for a new site changed to
subdomain.home.blog. They own the .blog TLD so it makes perfect sense to start using it. I like how WordPress.com is constantly changing and improving the experience. Maybe I was right with this blog post over at WP Realm 🤷🏼♂️.