Menu

WordPress 5.0 Tips

A collection of content related to the release of the next generation of WordPress

You can now SUBMIT WordPress 5.0 related content to WP5.tips

Because there just aren’t enough hours in the day to keep an eye out for all WordPress 5.0 related news we’ve gone ahead and opened up submissions of content to this blog.

What sort of stuff?

Anything related to the upcoming WordPress 5.0 release will fly, so:

  • Guttenberg stuff (obviously)
  • REST API news and updates
  • Anything Customizer related
  • Security, GDPR, etc…
  • Audio and Video (Podcasts/Conference talks)
  • Informative Tweets
  • Core team updates
  • Opinion pieces (good or bad)
  • Tutorials, learning, guides

You get the idea. Whatever it is, just make sure it’s related to WP5.0 and helpful/useful and we’ll get get the thing added to the site 🙂

WordPress 5.0 & Gutenberg myth-busting

The path to WordPress 5.0 has been a rough one. With community feedback around the new editor generally split and fear about such a fundamental change generally worrying the WordPress-masses.

The team behind TinyMCE looked to ease this tension with their excellent ‘Gutenberg myth-busting: 10 answers on the future of content creation in WordPress‘ post which was published in October 2017:

It is important to note that version 4.9* of WordPress is not out yet. Version 5.0 of WordPress is not due to be released until 2018, and the new editing experience is still under constant construction.

Read the full text over on the TinyMCE blog. (*version 4.9 was released November 15, 2017)

Drag-and-drop Gutenberg now availiable

The editor team have announced that the latest release of Gutenberg (2.6) now has support for drag-and-drop blocks, see a quick video demo here:

This is a welcome (and much requested) change and you can try it out now with Frontenberg. Early tests are a tad ‘clunky’ but the implementation is very young so keep an eye out for improvements in the next release.

 

All Hail the Classic Editor – Gutenberg-override to be bundled with WordPress 5.0

WPTaven has a great article explaining the path that led to the decision have a simple option that will ‘restore’ the Old Editor when WordPress 5.0 is released.

This seems like a good solution that will help ease the pain for a lot of users. The WordPress Accessibility Team were especially active in this debate when it became clear that Gutenberg would not be fully accessible for launch:

What does this mean for most WP-ers?

The option to ‘disable’ Gutenberg using a plugin has been an option for a long time. This news just means that the ‘Classic Editor‘ will be bundled with WordPress 5.0 as standard. It’s a bit like when Tesla removed Ludicrous Mode from their cars by rolling out software which removed the option as the default.

And it’s true that the ‘Classic Editor’ approach is going to be the preferred choice for a LOT of people who have older or very complex websites that use incompatible systems (for example ones heavily reliant on Shortcodes). This isn’t a bad thing, it’s a practical and pragmatic solution to a complex issue.

The WordPress Roadmap, still a long way to go…

The WordPress Roadmap is a great tool to look back at previous WordPress releases and get a good idea about what’s coming up.

WordPress version 5.0 will be included in this roadmap soon enough and at some point get ‘frozen’ and made ready for release:

The month prior to a release new features are frozen and the focus is entirely on ensuring the quality of the release by eliminating bugs and profiling the code for any performance issues.

As you can see, WordPress 5.0 still has a long way to go before it’s ready to be released – the current version is 4.9.6 which has (obviously) some links to version 5’s new Gutenberg editor:

4.9.6 will likely be a quicker release cycle. Some initial targets were discussed for this release.

  • The “Try Gutenberg” prompt
  • GDPR related items
  • Any changes resulting from several discussions currently happening about needed API changes to prepare for Gutenberg.

Block-voluton

Moving to a ‘Block-based’ editing system was first outlined in the ‘How Little Blocks Work‘ announcement post in May 2017. This was an opportunity to look at a brand new way to store content data in WordPress:

The new block-based development logic was outlined by Matias Ventura as:

Blocks provide functions that describe how they want to be represented for both the editing context and the final markup to be saved. The internal representation of the post content is updated as blocks are updated, so during the editing session we can remain in the right side of the diagram above.

Further information can be found in the ‘Editor Technical Overview‘ which is where the idea of using ‘HTML comments’ as a way to separate block content started out.

Gutenberg Design Principles

The Gutenberg Design Principles do a great job of explaining how the new WordPress editor has been designed to function.

The basic ‘Goal of Gutenberg’ is mentioned here:

The all-encompassing goal of Gutenberg is to create a post and page building experience that makes it easy to create rich post layouts.

There is also a clear Vision Statement that ends with the following statement:

Ultimately, the vision for Gutenberg is to make it much easier to author rich content. Through ensuring good defaults, wrapping and bundling advanced layout options blocks, and making the most important actions immediately available, authoring content with WordPress should be accessible to anyone.

Where Version 5 Started…

The announcement that Matt Mullenweg laid out in his ‘Focus Tech and Design Leads‘ post in January 2017 is primarily responsible for the changes we are seeing to WordPress in version 5.

This post laid out three main focuses for 2017: REST API, the editor (Gutenberg), and the customizer. The new editing experience (which became Gutenberg) was mentioned in some detail:

The editor will endeavour to create a new page and post building experience that makes writing rich posts effortless, and has “blocks” to make it easy what today might take shortcodes, custom HTML, or “mystery meat” embed discovery.

This was followed just a few days later by ‘What makes a great editor?‘ by Joen Asmussen (a designer at Automattic) a post which opened up discussions about how ‘block-based’ editing would work in WordPress.

Try the new Gutenberg editor with ‘Frontenberg’

Frontenberg is a way to play around with the new WordPress ‘Gutenberg‘ editor which is coming in WordPress 5.0 without the need to mess around installing WordPress or adding the Gutenberg Plugin.

It was released in December 2017 by Tom J Nowell who works as a VIP Wrangler at WordPress.com VIP for Automattic.

 

Read the WordPress 5.0 Development Cycle

The source for all technical project information can be found over on the Make WordPress Core site. This includes the Release Schedule, notes from regular meetings. There is also a direct link to the 5.0 Post Tag which will grow as more information is published.