Ten days before the initially published releases date for WordPress 5.0 Gutenberg developer lead, Matias Ventura published the modified schedule: final release to November 27, 2018. Beta 4 on Monday, Beta 5 on Thursday and November 19, the first release candidate (RC1) is to come out. Plugins with various sets of Blocks are available to augment the default editor’s set, with call to actions, galleries and various column layouts. What do other people do with Gutenberg? Find out on various blog posts, podcasts and video shows. We gained a week to get ready. If you can, help testing 5.0 Beta 4 on Monday and Gutenberg 4.3. Or get some rest — Birgit 💕
I am writing this from the Southwest Florida Airport on my way to Nashville, TN, the Music City. About 1800 people will descend for WordCamp US, Mullenweg’s State of the Word and Contributor Day, starting Friday. Finally we have a new release date for WordPress 5.0: tomorrow (Thursday). Read Matt Mullenweg’s post and watch yesterday’s interview with Adam Presser of WPCrafter YouTube Channel. Also on YouTube, the Gutenberg Times Live Q & A with design and tech leads, Tammie Lister, Matias Ventura and Joen Asmussen. A lot more blocks popped up for content creators using Gutenberg and more tools for plugins developers to create blocks for the new editor.
About to board my plane now. 🛫✈️Hope to see some of you at WordCamp US (Livestream tickets are free) 💕 Birgit
If it weren’t for the last minute, nothing would get done
Based on the stability, testing, and reports on the release candidates for WordPress 5.0 so far, we are now targeting Thursday December 6th for public release and announcement. 5.0.1 will open for commits soon, and will be an area people can choose to focus on at the contributor day at WordCamp US in Nashville this Sunday. As before, if new information arises that indicates the software is not stable, we will adjust or remove the target date.
Do I have to switch to Gutenberg when WordPress 5.0 is released?
Not at all. When it’s released, you get to choose what happens. You can install the Classic Editor plugin today and when 5.0 is released, nothing will change. We’ve commited to supporting and updating Classic Editor until 2022. If you’d like to install Gutenberg early, you can do that now too. The Classic Editor plugin has been available for 13 months now, and Gutenberg has been available for 18 months. Both have been heavily promoted since August 2018, and more than 1.3 million .org sites have opted-in already to either experience, so nothing will change for them when they update to 5.0.
Is it terrible to do a release in December?
Some people think so, some don’t. There have been 9 major WordPress releases in previous Decembers. December releases actually comprise 34% of our major releases in the past decade.
What if I don’t want to update on that date, or I’m not ready?
That’s totally okay, there’s nothing that says you must update the moment there’s a new version released. You can push the button whenever you’re ready.
What if I want to upgrade but I’m not ready for Gutenberg?
No problem, install the Classic Editor plugin and 5.0 will be indistinguishable from 4.9.8 for your posting and editing experience, and you’ll still get the other improvements and fixes that have gone into 5.0. Classic Editor is supported until 2022, and now allows you to switch between Classic and Gutenberg on a per-user or per-post level.
We have had a stable RC1, which stands for first release candidate, and about to do our second one. There is only currently one known blocker and it’s cosmetic. The stability and open issues in the release candidates thus far makes me optimistic we can release soon, but as before the primary driver will be the stability and quality of the underlying software. We made the mistake prior of announcing dates when lots of code was still changing, and had to delay because of regressions and bugs. Now that things aren’t changing, we’re approaching a time we can commit to a date soon.
November 23, 2018 WordPress 5.0 RC1 – the first release candidate was released about 4 days late. On Nov 21, Matias Ventura wrote: “The date for 5.0 release is under consideration, given it’s not plausible for it to be the on 27th. “
I had a call with Matt Mullenweg to discuss some things regarding the upcoming Gutenberg release, the critiques around accessibility, and thoughts I’ve had around the way this release and other releases are scheduled. I’ll keep this note to the accessibility components.
There have been ample critiques of Gutenberg, with a great deal of heat especially around the topic of accessibility (they’ve been documented in this newsletter). Rightfully, many folks want to see more work done around making Gutenberg accessible for all users. I think that some of the critique is overdone and the temperature is a bit too high around the topic.
I believe accessibility — especially for a tool as widely used as WordPress — is very important. The a11y efforts around WordPress have increased a great deal over the years. However, WordPress, nor the broader web, have a great record for releasing fully accessible features from day 1. Is there more work that can be done to make Gutenberg as accessible as it can be? Yes. Has the team building Gutenberg worked hard to make it accessible? Undoubtedly yes. Is WordPress accessibility in need of more work? Yes. Is there complete consensus around what proper accessibility even looks like in Gutenberg? Not as far as I know.
Shipping software is hard. Shipping feature complete software is impossible. Pleasing every party with a stake is impossible. I don’t envy the team developing Gutenberg, nor Matt leading the effort. I wouldn’t want to touch it with a ten foot pole.
There have been communication breakdowns, it appears, between accessibility advocates, accessibility volunteers, and Gutenberg development team members. I do not think Matt Mullenweg takes accessibility lightly; he told me so, as well. I think that the team working on Gutenberg wants to make it accessible for everyone to use. I think there is a lot of hostility in the air. A11y advocates are an under-represented group, and too many times have had to “fight” for accessible software. I think there is a lane here to not fight, but to work with, Gutenberg team members to move forward. There is, I think, room for compromise.
I think it’s important to continue to identify, work on, and improve accessibility in Gutenberg (and WordPress broadly). I personally, cautiously, suggest we embrace Gutenberg shipping without a complete accessibility audit while seeking more people to help with accessibility moving forward.
It certainly would’ve been easier and faster for Automattic to isolate editor development further to make it available within WordPress.com without it in core first, but Matt tells me he believes Gutenberg in core — sooner rather than later — unlocks a lot of Gutenberg-reliant integrations and feature development from plugin developers and other software makers.
I don’t know how much the community is itching to work on top of Gutenberg but I do trust that it will become an important part of building with and on top of WordPress.
Obviously, we all want all users to be able to user every feature of WordPress. But the standard being put on Gutenberg is not one that’s historically been applied to new features; I don’t mention that as an excuse, but rather to put it in perspective.
The classic editor will continue to a viable and accessible solution for years. There’s a message going into core to propose, “Users of assistive technology who experience usability issues with Gutenberg should use the Classic Editor.”
One of the things I would personally like to see is, what would Gutenberg look like as a 100% accessibility ready editor? Is this out there? Is there a list of what would need to exist? Are there any web editors that are appropriately accounting for this experience — Squarespace, Wix, Medium, or others? I don’t know and am curious what a viable a11y-complete builder experience would look like.
I think it’s important to get above the trees to see the forest. Gutenberg is the vision from the project lead to take WordPress forward. Neither Matt or the hundreds of people working on that software take accessibility lightly. However, nothing is perfect nor just how we want it to be out of the gate. In fact, if we are 100% satisfied with a product upon release, we waited too long. In my view, Gutenberg has been very ambitious, and got very large in scope, and took too long. It’s time to get it out the door and start iterating.
One thing Matt mentioned was that in addition to the release, there will be point releases every two weeks to continue iterating, and fixing, issues. Gutenberg will not be a “set and forget” feature. That led us into the rest of our conversation around release schedules and development flows in WordPress, which I’ll save for another day.
Brian is a web developer in Birmingham, Alabama. He runs Post Status for WordPress professionals and Ledger Status for crypto investing enthusiasts.
Reading list: Accessibility
Accessibility Team Meeting Notes
The WordPress Accessibility Team meets every week on Friday at 16:00 UTC (11 am ET) in the #accessibility Slack channel in the WordPress team space. Here are the links to their meeting notes and the two Gutenberg Accessibility Status Reports.
Next week, WordCamp US 2018 will take place in Nashville, TN. As part of the organizing team, I might not be able to make the sessions, I’d like. Here is the list of talks about Gutenberg that interest me. I keep this list so I can catch the talks on WordPress.tv afterwards.
Actives Installs of Gutenberg just passed the 1 Mio milestone. 👏 🎉 If you are ready or not, WordPress 5.0 will come soon. It’s not going to be November 27, because of the four-day delay for the RC 1 release. The goal is to have a stable release candidate before the final version is released. In the meantime, we found some fabulous themes that shine with the new editor. Plugin developers create some awesome Gutenberg Blocks for your post and pages. If you have questions regarding your site or how to get ready for Gutenberg, we collected a few articles that can walk you through the various aspects.
Today, I also installed the new Twenty-Nineteen theme by Allan Cole, supported by Kjell Reigstad as design coach, who also published the Music Theme earlier this year. The Post Grid on the front page is a Custom block by Mike McAlister and available in the Atomic Blocks collection.
WP4Good: Gutenberg Q & A for Nonprofits takes place on July 26th at 3pm (19:00 UTC) See the website for more information and registration.
Zac Gordon and Joe Casabona are back again with their “The Gutenberg Live Show” – the next event is on July 27 at 2pm ET (18:00 UTC). Starting August 9th they will go online every other Thursday, also at 2pm ET (18:00 UTC). For more information and sign-up click here.
Update May 29th, 2018
May 30th, 2018 at 1 pm ET – Live Webinar with Chris Lema of LiquidWeb. VP of Products, Chris Lema, explains the importance of Gutenberg and how it will impact your customers.
“In this five-session series we will sit down with prominent WordPress experts to find out what every developer needs to know to utilize WordPress 5.0 and Gutenberg, the new WYSIWYG editor. They will talk through the details of designing sites, Gutenberg blocks, preparing your sites for Gutenberg, and a ton more!”
Joe Casabona announced the next series of Guteberg Live Q & A. He host the show together with Zac Gordon. Sometimes they invite guests. Updates on the events will be posted here gutenberg.courses/askus
Updated: Gutenberg & page builders, developing for Gutenberg and more.
Guten Tag Events March 5th, 2018
A series of four events is on the schedule on Crowdcast by Guten Tag events. Times listed here are on EST – The Google Calendar below lists them all for your personal timezone. You can register here on Crowdcast
3/5 – 7:30am Guten Tag#2: Fireside chat with Gutenberg team members: Mark Wilkinson (@wpmark ), Matías Ventura (@matias_ventura), Miguel Fonseca & Tammie Lister (@karmatosed)
10:30 – 11:30am Guten Tag #3: Future of Page Builders with David Lockie & Robby McCullough of Beaver Builder (@RobbyMcCulloug)
12:30 – 1:30pm Guten Tag #4: Practical How-To: Staying up-to-date with Gutenberg with Zac Gordon @zgordon
Gutenberg Live Q & A announce their next guests
3/2 – 2 – 3pm Live Q & A: Zac Gordon, Joe Casabona will talk with Ana Silva and Matthew Haines-Young of Human Made
3/15 – 12 (noon) – 1pm with special guest Robby McCullough of Beaver Builder
Update 2/22 We are keeping up with the online events. Doesn’t mean we won’t miss one. If you have an event scheduled and you don’t find it on our Google Calendar, let us know! We’ll update it fast:-)
Today’s update: Pantheon’s Webinar for Feb 27th, 2018 at 1pm ET / 20:00 UTC
Update 2/8: Today I learned about Nikola Nikolov’s “Tour de Core”. Every week on Thursday at noon PT ( 20:00 UTC) he broadcasts his research and development process via YouTube Live. He is building a block for Gutenberg with which a user can add photos directly from Unsplash to posts and pages. Browse his YouTube play list of Tour de Core Parts 1 – 7
Update: 2/6 We also will add future webinars and other online events. If you’d like to get your event lists, just tag @gutenbergtimes in your tweet or send a note to email@example.com
Live Q & A w/ Gutenberg Educators
Zac Gordon & Joe Casabona, two educators who have publishin Beginners Tips and courses around Gutenberg since the beginning of the year are holding bi-weekly Q & A session. The
In our LIVE Q&A Sessions you can ask questions about Gutenberg and the changes it will bring and get answers from Joe and Zac right there on the spot.
For content creators, change in daily routine is fatal to productivity. This is especially true during the transition to Gutenberg since it still contains a few “gotchas” that may stymie people and interrupt workflow. I list a few here, along with some workarounds to assist users during active development. Gutenberg will be updated as soon as issues are resolved or refactored.
This is still a beta version. If you work with Gutenberg on your live / production site, make sure revisions are enabled so auto-save works! And if you depend on the website for your livelihood, I recommend creating a copy of your site on a staging site before testing Gutenberg with it.
Now it’s one to the reason for this post: to alert content creators to the hidden features of Gutenberg that streamline writing workflow. As we all know, each time we learn a new software or tool we tend to judge it at our “beginners level”. We may even throw in the towel before we reach mastery. And that applies to the current editor.
This post assumes that you have already gotten your feet wet with Gutenberg. If you haven’t I suggest that you read one of these excellent resources under the Beginner’s Guides to Gutenberg
There is also a whole team working on an official user manual for the Block editor. Until that’s published, it’s all a bit fragmented. If you are a technical writer and would like to lend a hand, join the #docs channel on the WordPress Slack
With Gutenberg 4.4 you can now edit the permaling in the document panel of the sidebar.
Once you save your draft, you can modify the permalink by clicking into the title section. There you will see the permalink editing space above the title. Developers and designers discuss on Github on how to improve this feature’s discoverability.
For users using an older version of Gutenberg on their sites (pre-4.4)
Please note that there is no permalink created for a new post until you have clicked Save draft at least once (Marius Jensen, Support Forum)
Slash Command to Trigger the Block Inserter
Probably the most useful tool hiding in Gutenberg is the Slash Command. It’s also my favorite. Using slash command invokes the Block Inserter including its search, so you don’t need to interrupt your writing flow to hunt for your mouse to add a quote or a list via the keyboard. Begin by starting a new line with Enter. Then hit the “/” key and start typing the name of the block. “/l” gives you the list as a choice. Selecting it and typing your first list item is really cool. Or you could just use one of the keyboard shortcuts below
But “/” + i gives you an image block, “/”
The introduced keyboard shortcuts also allow for the following combination
⌥⌘TInsert a new block before the selected block(s).
⌥⌘YInsert a new block after the selected block(s).
Customize Your Workspace
Since version 3.8 there are three features to customize your writing workspace. The Unified Toolbar, the Spotlight mode and the Fullscreen mode. You can use all three together or each one alone. Some people are a bit taken aback by everything’s being block, especially each paragraph. “Spotlight mode” helps with that.
And it can seem awkward for each paragraph block to have its own formatting toolbar that pops up on hover and covers text above. The Gutenberg team implemented a solution for this called Fixed Toolbar on Top – which was just renamed to Unified Toolbar.
Switch it on in the Editor Settings menu, and reach it via the ellipsis menu (3 dots) in the top right corner. The Block Options menu is also available from the toolbar on top of the screen.
This process is refined by a “Spotlight Mode”. The editor grays out the canvas except for the block you are editing. It also delays the visual clues about separate blocks while in writing mode in the editor, making it less distracting.But that has the down-side of making the features for individual blocks even harder to discover. But you can easily switch it off again by returning to feature mode.
Full Screen Mode
With 3.8, Gutenberg now also has a full screen mode You can switch it on and pretty much remove the top admin toolbar as well as the left admin menu. Once you remove the editor sidebar, all that stays on your screen is the Top Unified Tool bar and your content.
Full Screen Mode, Spotlight Mode and Unified Toolbar.
Disable Publishing two-step
I personally like the Publishing two-step process. As soon as I hit the publishing button, the post will automatically shared on various social networks. The Publish Two-Step has saved me more times than I care to admit. But you are able to switch that off. You can also disable it the first time you see it happening in “Are you ready to publish?” Screen. On the bottom of the screen uncheck “Always show pre-publish checks”. And it won’t bother you again.
Under the Editor Settings menu, you open via the 3 dots in the top right corners.
New line as command line
Gutenberg developers also introduced a new concept: new line as your command line.
By hitting enter in a paragraph, you can write another line or execute a few shortcut commands:
`/` slash command to insert a block
`>` to start a quote directly,
`##` to start a heading, (in a post’s body you start heading hierarchy i with <h2>)
`1.` to start an ordered list (also ‘1)’ )
`-` to start a list.
Using backticks ` at the beginning or the end` of a string adds code formatting to your string. (the same key as the ~ key)
I also learned a few more very helpful shortcuts,
⇧⌥⌘M Switch between Visual Editor and Code Editor.
⌘KConvert the selected text into a link.
^⌥SRemove a link.
Since the focus is now on block based editing, I was surprised to notice that there is no keyboard shortcut to switch to HTML editing on the block level. And that is where I do most of my HTML tweaks. Turns one I am not alone. I filed a GitHub issue and it seems to be on the docket to be added.
More Keyboard Shortcuts can be accessed, via at the Editor Settings Menu
I apologize that the shortcuts are all in MAC notation. If you open the Gutenberg editor on your machine, you’ll be able to look up the shortcut combinations your specific operating system.
Copy/Paste from Anywhere
Matt Mullenweg’s favorite hidden feature is the parser built into Gutenberg that allows for copy/paste of content from various tools, like Evernote, Google Docs, Microsoft Word, etc. Here is a little matrix on what works across the various platforms:
Reusable Blocks offer a whole new level of content development. With Gutenberg version 3.9, you can now save a combination of blocks as one reusable block, which you can also export and import on other sites. Why is this a big deal?
For instance you can build landing pages with certain disclaimers, calls to action and campaigns. You can make the wording, the combination between heading, image or cover image and CTA button available to your users, for their use on their own posts and pages.
The new Gutenberg release also provides ways to manage your reusable blocks: You can delete them, export reusable blocks, and even import Gutenberg blocks from other sources.
There is a power feature for the Donate Now button: If its link changes, you need to change it on just one page, and that updates all other instances on your site.
In other words, reusable blocks are not templates. They are “content + design” blocks. And, if you need to change things in one spot, but don’t want to change other instances, you simply convert it to a standalone block before making the changes. Just use the “Convert to Standalone Block” link in the Block Options menu.
How to align an Image?
We often add an image to break up dense text in a long paragraph, and it must be aligned so the text wraps either left or right of the image.
This may be the biggest transition hurdle for new Gutenberg users. I never found it easy in the old editor, and it’s still a bit quirky in the new editor.
But I am content to switch out one bad UI with the another bad UI. Coming from the early days of HTML coding, I know about the hazard of image floating n web design. So I don’t have high expectations and am happy that it works at all. Resizing the image is easier but the default experience is still not great.
The biggest change is that just putting the cursor on the top of the paragraph where you want the image to align doesn’t work. You need to add the image block above the paragraph that will be aligned with the image.
Follow these steps to align an image:
Use the “inserter” above the pharagraph.
From the inserter select “image block”.
Upload or select an item from the media library.
Use the left or right align button from the block toolbar.
Use the blue dot handles to resize the image.
Or you can drag and drop an image – again – above the paragraph, and align and resize it to fit.
How Gutenberg makes it much easier is that it’s truly WYSIWYG! You don’t have to switch from editing to preview to see if your image aligns well. You see it right in your editor.
There is a whole series of two blog post about this on WPTavern to solve one thing. A clearly Jeff Chandler didn’t have this secret manual:-)
WooCommerce is still working with the current editor. The post type “product’ is not yet ready for Gutenberg. Earlier this year, there was a test period, and since 3.4 it was reverted back to the classic editor. “Since WooCommerce is not optimised for the Gutenberg editor we’ve decided to keep the old editor for now so sites do not break when WordPress 5.0 is released. Products are not content focussed, so using Gutenberg with our meta box placed awkwardly at the bottom is not ideal.” Source: GitHub Issue #20201
WooCommerce’s plugin has four different product views, is a rudimentary Product view. Later in the year WooCommerce devs will refactor products using the Gutenberg framework and tools, they announced…
PootlePress released their premium plugin Storefront Blocks. The various views in grids, sliders, masonry or carousels are very slick and impressive. Take a look for yourself.
Formatting Multiple Text Blocks
Highlighting a few paragraphs and making them bold or in italics doesn’t work yet, unless you use the Classic Editor block. It’s one block at a time. Note: There is a GitHub issue where the foundation of multiple block behavior is discussed. It is a prerequisite to something as simple as formatting a paragraph and a list in italics. Here is the feature discussion, if you want to chime in
Posts are now locked for other users
If you are working in a team of editors, you are familiar with the post lock feature in the current editor. If one of your peers is right now editing a post, you are not able to access it for editing; you have options for read only or to take over the post.
“Title” is not a block
It looks like a block, behaves like a block, but it’s not a block. The post title holds a lot of weight, especially in backwards compatibility, plus in other places of WordPress for category pages, for the RSS feed, and many little things. Gutenberg is not modifying how the post title works.
White space around the editor
The editor is “opinionated” regarding the space it occupies. Depending on the size of the screen, you might find “too much” white space on the side of your content.
The opinion from the design is that there is an optimal width for reading on screen, and if the display space is larger it is much harder to keep track of the lines. It adheres to a max-width.
A few people mentioned this in the forums, and the team is giving it another review. (1483)
If you feel the same way when you look at your editing screen, you could use the plugin (???) To fix it for yourself.
Keep in mind though, that usability studies have shown that a content window is between 480 and 600 pixels. For easier reading it’s actully half the size. That’s BTW is helpful to have a graphic to the right for the first section of your blog post. (I don’t understand previous sentence.MR) That’s one aspect. The other is that with Gutenberg you are aiming at a 100% WYSIWYG. So what you see in the editor should be the same thing that is visible to your visitors on the front end. If you make the editor screen too wide, a few things will wrap differently for your visitors. Quite a few writers found this tip helpful.
Grammarly doesn’t work well
“Grammarly considers block a separate text box, meaning if you create a 25-paragraph post, you have 25 separate text boxes Grammarly is trying to check. This forced me to disable Grammarly on my site.” Jonathan Bailey in “WordPress’ Gutenberg: A Practical Review”
Marius Jensen has published a few issues that he and his team of volunteer forum helpers identified. Quite a few of them have to do with another fairly new module that made it into Core recently, the REST-API. Gutenberg development is based heavily on the REST-API so during developing Gutenberg, the collaboration with the REST-API made it better as well. At the foundation of this, it’s a programming issue, but it will bubble up to become quirks a content creator will need to be aware of:
Categories and tags are not showing up
Some security related plugins may have disabled all, or parts of, the REST API. This is used by Gutenberg to fetch all the data used to display content in the editor, so if you are missing fields, check if you have a security plugin enabled. If so, see if it has an option for the REST API.
Updating Failed Message
If you are receiving a Updating Failed message when trying to save a post or page, check if you are using the services provided by CloudFlare. We are currently working with them to address a problem which blocks the Gutenberg save function. A workaround is available while we find a solution to this.
It’s been reported that some antivirus software may also block REST API requests. So if your antivirus software offers an application firewall, this may prevent you from saving posts. We are looking into this.
Blank Editing Screen
Some users may experience a blank editing screen. If this happens, a first step to testing should be to just hit refresh in your browser. It may be a “race-condition” that we’ve identified and are working on fixing.
When is WordPress 5.0 to be released?
The short answer is: The release of 5.0 is scheduled for November 27, 2018. If for whatever reasons, this date needs to be pushed, the next date for a final release is January 22, 2019.
Beta 4 is released today (Nov 12)
Beta 5 is scheduled for Thursday Nov 15 and
Release Candidate (RC) 1 is scheduled for November 19, 2018
There are voices who lobby for a January release date. Joost de Valk, founder of Yoast, published a post: WordPress 5.0 needs a different timeline Aaron Jorbin, Core Committer, also raised concerns in one of the Core DevChat meetings. He things that the testing various newly built APIs haven’t been tested long enough. My personal instinct is that the team leaders try to push through all the various pieces to actually go live to assess during beta, what works and what needs to be fixed in the context of Gutenberg being in core. The sooner release date keeps everyone actively working on the pieces, like REST API, Meta boxes, Gutenberg UI updates and Classic Editor, focused and energized. They will do their best to release a minimal viable product. And then iterate fast with 5.0.1 and 5.0.2. I’d be pleasantly surprised when WordPress 5.0 will actually be released in 2018.
Nov 16: added shout-out to today’s Live Q & A + Screenshot of Permalink editing in Document panel of the sidebar of the editor
Nov 12: added link to WooCommerce Sticky Post on Plugins Forum page and fixed a few more typos. – bph
In August a “Try Gutenberg” call out was released with WordPress 4.9.8 with a button to to install the Gutenberg plugin for post and pages or install official Classic Editor. If you install the Classic Editor, you will be able to keep using the current editor beyond the merge of Gutenberg into Core.
Beyond this global opt-out method, developers, consultants and site admins can make more nuanced decisions on how Gutenberg is implemented on their sites. Here is a list. If you find one missing, feel free to post a link in the comments and we’ll update the post.
Caveat: Use at your own risk. We did not test the latest versions of mentioned plugins.
Built-in Methods and Plugins maintained by Core Contributors
Gary Pendergast, summarized built-in Methods that will be available when Gutenberg is merged into Core.
Note: There is not a single method. It’s all depends on context.
The Classic Editor plugin is the option for reverting to the classic editor across an entire site. It’s being advertised prominently in the upcoming WordPress 4.9.8 release as an option to install now, in preparation for WordPress 5.0. If you’re a site builder who wishes to opt your clients out of the block editor, installing the Classic Editor plugin (and contributing with bug reports or fixes) is the best long term solution to ensure the classic editor will continue to be available.
For CPTs, the gutenberg_can_edit_post_type filter will be renamed when it’s merged (probably to block_editor_can_edit_post_type, or something of that nature), but will also be available as a code-based option.
Methods to avoid Gutenberg nag or modify it.
Built into Core with with 4.9.8
For site – owners, the easiest way is to just use the “Dismiss” link on the right side. Once you dismiss the prompt it won’t show up again. Wow, that was easy:-)
Via code in a plugin or in a file stored in /mu-plugins folder
The is also a new filter try_gutenberg_learn_more_link “that allows hosts or site owners to change the link, to provide extra information about Gutenberg, specific to their service or site. ” (Quoted from the trac ticket)
A recent start-up, intending a fork of WordPress 4.9.8, probably one of the last versions without Gutenberg. At the time of this writing (8/27/28), it’s not ready for anyone to jump on board. Stay in the loop via the website.“Forking is a features” Gary Pendergast, a WordPress Contributor blogged in August.
CalmPress is the name of another WordPress 4.9 fork. “to get a more stable and calm experience to all of its users” writes Mark Kaplun, the initiator of CalmPress. It’s not intended as a “one-man hobby”, but it’s what it looks like at this moment. You can follow along the progress via its blog
Craft is another PHP/MySQL based Content Management System, just released in it 3rd version. Back in April, the Craft Plugin Store was opened, integrated with GitHub and annual updates for residual income for the developers.