Happy Holidays ! Peace and Understanding around the World!
So WordPress 5.0.2 came out with massive performance improvements to the block editor especially for posts with many, many blocks. I tested it here on a post with 94 blocks and it was wrap speed compared to before. Hat Tip to the Dev Team! I ordered 2 sets of the Gutenblox.fun Jenga issued by XWP. All proceeds go to the WordPress Foundation. Marcus Kazmierczak of the Documentation team published a tutorial for programmers to get started on WordPress JavaScript. Join us next week for the next Gutenberg Times Live Q & A. Discover more news below.
Hopefully you can fully unplug and be with your families and friends. Be present, be in the moment, look up! — Yours, Birgit 💕
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.
Gutenberg has been under development for two years. Matt has devoted now more than 40 employees from Automattic to core to help ship Gutenberg — a number I found staggering. There are dozens more fully volunteer workers on the project, and yet accessibility experts, especially around JavaScript-centric development, are still hard to find.
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.
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.
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.
WordPress 5.0 Beta 5 was released this week. The RC1 version is scheduled on Monday. Gutenberg’s latest version is 4.4 with features and UI upgrades that were discussed for quite some time, months even. We also heard a few voices who lobbied for a January release date of WordPress 5.0, with some well argued considerations. The number of actives installs of the Gutenberg plugin crossed the 700,000 threshold. Plugins developers are able to refine their blocks and update to the latest. I found a series of posts and plugins that help building blocks for the non-programmers or the non-JavaScript crowd. Very interesting approaches! More and more themes developers are finishing up their work to incorporate Gutenberg features in existing products or create new themes.
Updated August 27th, 2018, added the option of leaving WordPress ecosystem and community altogether, highlighting four alternative CMSs.
Updated August 2nd, 2018 added a 12th method to the Gutenberg Call-out section.
Updated August 1, 2018 added an 11th method to the Gutenberg Nag section.
Gutenberg, the new visual editor for WordPress will be merged into Core as the default editor later this year, when WordPress 5.0 will be released.
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.
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)
There are a few plugins available that suppress the so called “Gutenberg Nag”.
Paul Biron, release lead for 4.9.8 created a plugin to hide the Gutenberg Nag for different user capabilities. At the moment, it’s only available on GitHub
Jeff Starr’s plugin “Disable Gutenberg” does a lot more (see below) and it also disables the Gutenberg admin notice.
Additional Plugins available on the WordPress Plugin Repository
Over the last four months, plugin developers also created various solutions to have a more granular control over Gutenberg editing experience.
Gutenberg Ramp – published by WordPress VIP team, allows you to enable Gutenberg on a post level basis for CTPs if they support the editor.
Jeff Starr’s plugin “Disable Gutenberg” completely disables Gutenberg editor, and gives us the choice to do it by post type or user role.
Sara Gooding on WPTavern reviewed the Classic Editor Addon Plugin, that also implemented a feature to disable the 4.9.8 nag, but also needs the Classic Editor plugin installed.
Gutenberg Manager by the unCommons Team, also allows you to disable Gutenberg for selected Custom post types.
With Lee Rickler’s plugin GutenBeGone – you can disable individual Blocks that come with Gutenberg
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
Founded by John O’Nolan, a former WordPress Core contributor, and Hannah Wolfe, Ghost’s 1st version was released in 2013. It’s a blogging platform entirely written in server-side JavaScript based on nodejs. The open-source software is available for self-hosters as well as a hosted solution, maintained by the Ghost Foundation.
Drupal, is the other major PHP-based open-source content management system with a large community. Lately, it made headlines, for efforts to integrated Gutenberg in its own code base.
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.
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 💕
Everybody is getting ready for WordPress 5.0 – Developers on various Core teams are working feverishly merging Gutenberg into the WordPress core. With the 2nd beta version available, Themes and plugin developers are making their products compatible with the new default editor or building guard rails around it. We see lot more opinions on Twitter from bloggers and content creators. Some express joy working with Gutenberg, and some are opting for the Classic Editor. Blocks for the editor are mushrooming in various initiatives. This Round-up post is extremely rich. Grab your favorite beverage and enjoy! — Birgit 💕
Also take your time to read the various comments. It’s gives a lot of insights on what Gutenberg developers are aiming for and what their process is. The discussion is very civil and thoughtful.
The post was one of the more rationale and reasoned looks at everything, and I really appreciate Joe and the team’s work in putting it together. It’s a starting point for prioritizing the extensive accessibility work that has gone into improving WP’s core editor already, but a key thing we have to fix is the team working in a less adversarial way with all the other contributors to WordPress — for example collaborating on posts like this, not tossing them over the transom.
"This might sound like a broken record, but because this release impacts everything from the editor, to third-party plugins, and even your theme, testing is not optional!," wrote @BrianLeeJackson of @kinsta // Solid advice and information! https://t.co/x7P3QDz5bV
This is a thread worth following. This is what it will take for VERY competent devs to migrate their sites to use #Gutenberg by default. https://t.co/MslUkAbxNb
WordPress 5.0: Let’s Delve into the Features and User Experience https://t.co/PiVbyi8FrG by @Cloudways w/ a speedtest between 4.9.8 + Twenty-Seventeen and WordPress 5.0 Beta w/ Twenty-Nineteen. Also, main features of Gutenberg, intro to Twenty-Nineteen Theme and other things new. pic.twitter.com/vG4ZYKFE1k
Although I personally still have to make peace with #Gutenberg, it is important to me that my #plugins are compatible. Toolbar Extras and Builder Template Categories are already compatible, but extra "bonus" stuff will follow in next versions! 🙂 #WordPress
I've been experimenting a bit with this new Gutenberg Cloud Blocks and the standalone Gutenberg. There is a lot of potential here. @wptavern wrote about the project including my first impression of creating a cloud block and a bit of different opinion from @richard_tabor https://t.co/XgZqIItkpH
Matt Mullenweg announced the leadership team responsible for the Gutenberg merge into Core and become the default editor. Gary Pendergast updated the release schedule. The team aims for Nov 19, 2018. Riad Benguella posted a technical overview for the Gutenberg integration. Gutenberg adoption has grown to over 510K active sites using it. Enhanced reusable blocks are Gutenberg 3.9 killer feature: select multiple blocks and put them into one reusable block, then export and import. And 73 more change log items. Remaining task for Gutenberg developers before heading into the Core merge proposal. An comprehensive guide as an eBook, Blocks galore and more developer tips for building blocks. It’s a big round-up again. Enjoy the week!
Source: Gutenstats.blog – recorded Oct 4, 2018 at 18:19 pm EDT
Gutenberg for @WordPress now has 420k active sites and we've tracked 213k posts written with it the past few weeks, only counting @Jetpack sites. Will have some block stats here in future! The original before-5.0 goal was 100k sites and 250k posts: https://t.co/S5Oju7cMRP
If you care about #accessibility and #WordPress, hop on this #Gutenberg issue and let the #a11y lead know you support an independent audit of the new editor. Let's make it clear that WP is not truly democratizing publishing if its not accessible to all. https://t.co/RqoidzcWKZ
Jen Roventine & the team at Modern Tribe published a comprehensive guide to the new block-based editor, with clear explanations of the major changes, and a step-by-step checklist to prepare your site for Gutenberg. 👏
I am very happy, we will have a Beta 1 of WordPress5.0 in a little of 2 weeks so we can stress test current site configurations cc. @PauliSystems @wp4good@wpswfl@ArtBloggers
Great post by Jason Cohen https://t.co/SmoFyc3w5j "Gutenberg should not be used as an excuse to refrain from updating to WordPress 5.0 when it’s released. Quite the contrary—our hope is that Gutenberg will be the reason many people update to 5.0 once it’s made available. "
Yup, a plugin I made that takes #Gutenberg data and stores the data elegantly into the DB which is accessible via REST API directly or via normal /posts/ endpoint.
Two of my favorite topics, tech and nonprofits! So many takeaways from my first RMU @bayercenter #TechNow18 Conference. Re-energized about #WordPress after @bph’s preview of Gutenberg. pic.twitter.com/nCs5lIxPrz
Curated information on Gutenberg – the new, modern publishing experience in WordPress by Birgit Pauli-Haack For developers, consultants, content creators and site admins
Find below an FAQ block, courtesy of Yoast SEO, with a highly speculative idea on when we might see a WordPress 5.0 release. Gutenberg 3.8 was released, and 3.9 RC is available for testing. The WordPress.com roll-out started. Gutenberg was not only topic at WordCamps in New York and Valencia, but also at Drupal Europe and at #ONA18 the Online News Association conference in Austin, Texas. Check out the photos from around the World. Also find more Blocks for your website and resources to develop your own blocks. Happy Monday! — Birgit 💕 PS: CU at my next “Secret Gutenberg Tips and Q & A for content creators and bloggers” show on YouTube on September 28 at 2pm
No-one knows. When Gutenberg is ready. Are some common answers. And I don’t know anything else.
The official WordPress 5.0 release page has not been updated since November 2017 and features lot of “TBD”s. We need to wait for a public discussion of the merge proposal once that’s accepted, a Kick-off Meeting will be scheduled.
I estimate that we will see a 5.0 Beta 1 version Mid November just in time for WordCamp US. Matt Mullenweg, co-founder of WordPress and CEO at Automattic, might include lessons from the merge proposal in his annual “State of the Word” (STOW) presentation. After that we might see a 5.0 Beta 2 Mid December just before the holidays. Everyone will be out until Mid January. We start again with Beta 3 and Beta 4 . The RC 1 might arrive at the end of February 2019 with a final release in March 2019. For our company planning we will wait with upgrades and training of content creators until 5.0.2 or 5.0.3 are out. Planning-wise that brings us to Summer 2019.
I might be totally wrong. I have no particular insight into the planning. I follow #core and #core-editor meetings on Slack, read GitHub issues and check on the progress of milestones.
When will Gutenberg be the default editor
The plan is to release Gutenberg in WordPress core with the release of the Version 5.0. WordPress 5.0 is a major release and the roll-out will not happen automatically. Companies offering managed WordPress hosting will test the new release for a period of time before they upgrade clients’ sites to the version.
If you feel for any reason, that your site won’t be ready for Gutenberg yet, you can install the plugin called Classic Editor to keep the current editor running on your site.
For more granular control over which content and post type is edited with Gutenberg, you’ll find 16 Methods to avoid Gutenberg editor, when it becomes available in WordPress 5.0
Building a client's site with Gutenberg, but I'm more comfortable with HTML/CSS than blocks. Using Gutenberg b/c I'm concerned about forward compatibility but SO frustrated with Gutenberg & other blocks plugins.
This week, I collected a great array of useful information for just using Gutenberg and finding blocks for your content creation process. See a VR (Virtual Reality) image block in action, find blocks in a public directory and read more about using Gutenberg for your storefront. Also, some voices from users and their successful transition to Gutenberg for content creation or revamp of their websites. I also found a few secret tips for power users. The next version 3.7 will come out tomorrow. Help testing the pre-release and grab the zip file from the Test Make Blog.
Secret Gutenberg Tip #1 concept “newline as your commandline”: keep typing your text `/` slash command to insert a block `>` to start a quote directly, `#` to start a heading, `1.` to start an ordered list `-` to start a list. brought to you by @altjoen
Corrections: ## gives you a H2 heading, ### an H3 Heading 1. + space starts an ordered list.
https://twitter.com/andymci/status/1034806643337428992
"When I first saw the wordpress visual editor in March this year, I was totally underwhelmed. It looked clunky and didn’t seem to work properly. Fast forward to July and I’m loving it!" // A great guide to Gutenberg for Bloggers ^ Birgithttps://t.co/b3vBIfJuKG
Site just went live: Sarasota International Cricket Club @sarasotacricket modernize their website: Theme 2017 + Gutenberg and some residue of the SiteOrigin page builder. Webmaster @christianhaack Hosted by partner @Pressable / Kitchen Table support by Birgit Pauli-Haack (@bph) pic.twitter.com/EMukiSFnMg
Secret Gutenberg Tip #3 If you feel the block toolbar, especially the paragraph block toolbar covers too much of your text or gets in the way, use "Fix Toolbar to Top" from your editor Settings Menu (3 dots on top of the editor screen) pic.twitter.com/bvK2LGHJmU
