With last Friday’s release Gutenberg is considered “Feature Complete” and the contributors switched focus to bug fixes, enhancements, backwards compatibility and API stability. Also, the core team is getting ready to finalize design on the “Try Gutenberg” prompt. We see a lot more sophisticated Gutenberg blocks surfacing and site owners and agencies are sharing their methods for testing sites for their Gutenberg Readiness.
Table of Content
- News on Gutenberg Development
- Version 3.2 was released last Friday
- API Freeze and Depreciation List
- Upcoming Prompt to “Try Gutenberg”
- Your Themes & Gutenberg
- Using Gutenberg / Testing your site
- Blocks Galore
- Photos from around the World
News on Gutenberg Development
Version 3.2 was released last Friday
The change log has again 115 items listed. And the development team sees it as “Feature Complete”, incorporating every feature they wanted before they start working on the merge proposal for the WordPress Core integration.
Gutenberg API Freeze and Depreciation List
Grzegorz (Greg) Ziółkowski posted: “If you have been wondering which public APIs might be subject to change, you can check this GitHub Project page: API Freeze. Also, he iterated about Gutenberg’s deprecation policy: supporting backwards-compatibility any change for two minor releases, when possible. He shared the current deprecation list from the project’s documentation section.
Upcoming Prompt to “Try Gutenberg”
Tomorrow, July 11, at the Core development meeting people will discuss the latest revisions for the “Try Gutenberg” prompt on the WordPress trac ticket
Yesterday, Kjell Reigstad posted another iteration of the possible designs. All three show a block selection window and language that give the user choices and assistance regarding their decisions to try it or not. Here is one of the mock-ups.