Usually during major releases of WordPress, the dedicated release lead The community member ultimately responsible for the Release. chooses a few folks to help them through the time-consuming work of managing an excellent release cycle. We are blessed with such a wide and talented team working on this release in the form of Gutenberg The Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc. https://wordpress.org/gutenberg/ (and 4.9.x) for so long I’m going to expand the team for this cycle.
The adoption of the Gutenberg plugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party, at 490 thousand active sites and counting, far exceeds pre-release testing of anything that has ever come into core Core is the set of software required to run WordPress. The Core Development Team builds WordPress.. If we keep the 5.0 release to strictly 4.9.8 + Gutenberg, we will have a release that is both major and a non-event in terms of new code. It’s all battle-tested. In some ways 5.0 is already de facto out in the wild, with some forward-looking hosts already installing and activating Gutenberg for new installs.
I have asked several members of the WordPress community to help lead the critical focuses required for a smooth and successful release.
Triage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors.: @matveb has the most context, history, and technical acumen in the entire Gutenberg project and is best suited to help triage open and remaining issues.
Design: While the majority of the design work in the block Block is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience. editor is already complete, there will be many aspects of the merge that will require design decisions. @karmatosed will continue her role as the design lead of the Gutenberg project.
Default Themes: From Twenty Ten through to Twenty Seventeen, @laurelfulford will lead updating all of the default themes to work seamlessly with Gutenberg.
Twenty Nineteen: @allancole has already been involved with a number of beautiful Gutenberg themes and will be responsible for adapting the one we’ll dub Twenty Nineteen.
Accessibility Accessibility (commonly shortened to a11y) refers to the design of products, devices, services, or environments for people with disabilities. The concept of accessible design ensures both “direct access” (i.e. unassisted) and “indirect access” meaning compatibility with a person’s assistive technology (for example, computer screen readers). (https://en.wikipedia.org/wiki/Accessibility): @lonelyvegan is a member of the Gutenberg core team and has worked on many of the accessibility improvements in the Gutenberg plugin. (We’ve gotten feedback it’s already surpassed the classic editor in many ways.)
Media: @antpb will shift from 4.9.9 to focusing on all elements of the media component, including backwards compatibility.
Merge: @pento, known for his care and discretion in making changes and a long history with core, will generally shepherd the merge.
Project Management: @chanthaboune has been a close collaborator on the WordCamp WordCamps are casual, locally-organized conferences covering everything related to WordPress. They're one of the places where the WordPress community comes together to teach one another what they’ve learned throughout the year and share the joy. Learn more. and Foundation side and will be lending those talents here.
REST API The REST API is an acronym for the RESTful Application Program Interface (API) that uses HTTP requests to GET, PUT, POST and DELETE data. It is how the front end of an application (think “phone app” or “website”) can communicate with the data store (think “database” or “file system”) https://developer.wordpress.org/rest-api/.: @danielbachhuber returns to a starring role with the REST API improvements we learned from building Gutenberg, and didn’t get into a 4.9.x release already, into core.
Upgrade Process: @mcsf will lead the user experience of how the core upgrade will interact with the Gutenberg and Classic Editor plugins that will have over a million active sites by the time of release.
With known knowns and known unknowns, I believe we will be at RC One of the final stages in the version release cycle, this version signals the potential to be a final release to the public. Also see alpha (beta). in about a month. However, I’ll be keeping a close eye on feedback during the beta A pre-release of software that is given out to a large group of users to trial under real conditions. Beta versions have gone through alpha testing in-house and are generally fairly close in look, feel and function to the final product; however, design changes often occur as part of the process. process and adjust as needed and keep the community fully up-to-date with our best estimate.
This post was written using Gutenberg, natch, and it was such a pleasure. I can’t wait for this to be in the hands of a wider audience of users and developers.
See also: Technical Oversight of the Gutenberg Integration.