Pressbooks and Gutenberg
We’ve been closely following the development of Gutenberg, WordPress’ new block-based editor, since its earliest technical prototypes. With the impending release of Gutenberg in WordPress 5.0 (currently scheduled for November 19), we want to provide an update to the Pressbooks community on our plans for Gutenberg integration.
In brief: we have deactivated Gutenberg for Pressbooks users, so upgrading to WordPress 5.0 will not change your editing experience. We’ve done this in Pressbooks itself, so additional plugins like Classic Editor are not required. We’ve made this decision for several reasons.
1. Gutenberg has continued to change significantly up to the projected release date, without a sufficient period of API and UI stability.
At Pressbooks, our small development team accomplishes a lot with limited resources, but ensuring compatibility with Gutenberg in time for its November 19th launch has proven to be beyond our capacity. The lack of clarity in Gutenberg’s development process has hindered us from integrating Gutenberg into our roadmap. We are now two weeks from its production release, and Gutenberg’s API freeze is not yet complete. We’ve been tracking blocking issues over the last year and a half and have tried to contribute where possible, but ongoing API and user interface changes have made it difficult for us to keep on top of things without neglecting Pressbooks core development, and have made us hesitant to invest our limited resources in building on a codebase that has not yet stabilized. Once WordPress 5.0 is released, we will be able to evaluate a stable version of Gutenberg and map out a plan for integration.
2. Gutenberg lacks functionality that Pressbooks relies upon.
Because Pressbooks is used to produce content for the web and for export, we leverage WordPress custom post statuses to determine whether chapters and other content appear on the web, in export files, or both. (Custom post statuses do not have a full-featured public API in WordPress, but they were the best solution for our use case. This is not the fault of the Gutenberg team—arguably, it’s our fault—but that’s where we are.) We also use a custom post submission UI to more clearly reflect content status for our users. At this point in time, Gutenberg does not support custom post statuses, which is a fundamental issue for us (and others who leverage this functionality). Furthermore, the new post publish panel is not easily modified, and we feel that it’s important to maintain continuity of this interface for our users. Following the release of WordPress 5.0, we will engage on these specific issues with the WordPress and Gutenberg development teams so that we can provide our users with a familiar experience in this area.
3. Gutenberg does not meet Pressbooks’ accessibility standards.
WordPress Accessibility team lead Rian Rietveld’s resignation in early October and the team’s recent report on Gutenberg have brought widespread attention to the accessibility shortcomings of the Gutenberg project. These issues are not new, as some have implied; Rietveld documented many in March of this year, and tests of Gutenberg by Léonie Watson and Sina Bahram highlighted significant problems around the same time. Rietveld’s resignation, the team’s report, and the conversations surrounding them have highlighted flaws in the Gutenberg development process and have underscored how hard it is to retrofit an existing interface if it was not designed with accessibility and inclusivity in mind. We're currently making accessibility improvement to elements of our core UI that date back to the early days of our product—so we know this from firsthand experience! More importantly, though, we’re continually seeking to expand our own shared understanding of accessibility and inclusive design principles so that new features are inclusive from day one. We’re grateful to Jess Mitchell, Jonathan Hung, and the rest of the team at OCAD’s Inclusive Design Research Centre for their guidance as we work towards these goals.
We acknowledge the assessment of the WordPress Accessibility team, who write that “based on [Gutenberg’s] current status, we cannot recommend that anybody who has a need for assistive technology allow it to be in use on any sites they need to use at this time.” We’re grateful to the many accessibility experts and advocates who have shone a spotlight on accessibility in WordPress, particularly the volunteers who form the WordPress Accessibility team. We’re also grateful to Rachel Cherry and the WPCampus organization, who are funding a much-needed accessibility audit of Gutenberg. As our focus is on continuously improving Pressbooks’ accessibility and all signs suggest that Gutenberg would undermine this goal in its current state, we will be awaiting the results of WPCampus’ audit following the release of WordPress 5.0, and we will evaluate our next steps at that time.
There are parts of the Gutenberg project that we’re pretty excited about. The ability to add and edit complex elements visually could be extremely helpful for book production, allowing educational textboxes and other specialized content to be edited visually while ensuring clean, semantic output on the front end. We’d love to be able to allow shortcodes to be edited visually, which Gutenberg supports. And we’re eager to see what comes of Gutenberg’s Annotation API, which could support expanded integrations with tools like Hypothesis. However, knowing what we know at this point and for the reasons articulated above, we feel that a “wait and see” approach is most prudent for us and our users. We are committed to tracking each of these issues and doing what we can to ensure that authors using our software have the best available tools for the job at hand. We look forward to a future where Gutenberg can be used for making books.