Gutenberg, REST API, and you…

Daniel Bachhuber, a core contributor for a number of years, has just this Call to Action on the WordPress Core blog:

As you may know, Gutenberg uses the WordPress REST API as a bridge between the land of JavaScript and land of PHP. There were a whole host of conceptual challenges in translating WordPress internals to REST — and even more we still haven’t solved!

The post also linked to the GitHub Milestone for ‘REST API’ in the Gutenberg editor where a number of development tasks are open for discussion and assignment.

Gutenberg 2.7 – Now you can Edit Permalinks

A new release of the WordPress 5.0 editor is now now out for testing and one truly groundbreaking option is the ability to edit Permalinks! Check out the release video:

Seriously though there are some other cool updates so go ahead and check out the release post.

What is Gutenberg? Video by GiveWP

This video is a great overview of the features and benefits of Gutenberg, the new block-based editor for WordPress 5.0. Watch it now on YouTube:

WPTaven review the new ‘Drag-and-Drop’ options in the editor

Drag-and-drop is finally in the new WordPress editor, meaning you can now more easily move around your content blocks.

The team over at WPTaven are all over the updates to the Gutenberg editor and did a really nice review/overview of how this feature works and what it brings to the experience.

From the post:

If you hover the cursor over the up and down arrows on the left side of a block, you’ll see a hand icon. Simply click, hold, and drag the block up or down below or above the blue indicator.

Best Practices for Blocks and Themes in the new editor

This post by Jason Yingling look in detail the best practices for developing new blocks in the new WordPress editor and how to integrate these features into features into WordPress themes.

One interesting part of this tutorial focuses on where to put your new blocks, in your theme OR in a plugin:

The general rule of thumb for including functionality in plugins or themes is to keep themes to the presentation of content and use plugins for functionality.

Blocks fall under this same set of principles. And I fall into the camp that blocks should be included in plugins as they extend the functionality of WordPress.

Read the full thing here.

Gutenberg Courses (The Future of WordPress is Here!) is a simple site with a simple goal – to share learning and training about the new WordPress 5.0 editor.

Currently there are only two courses listed which are split between ‘users’ and ‘developers’ – check them out:

The site also has a ‘Ask‘ section which lists upcoming LIVE Q&A Webinars meaning you can get right to the source of the information!

Beginner’s Gutenberg Development Tips

The team over at meks have done a great job of pulling together 31 beginner’s tips on Gutenberg Development.

From the post:

Both from developers and content side, this improvement will change the way we code and produce content in WordPress. Not to mention all the advantages that are coming with the blocks and the ways we create content.


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.