With Gutenberg getting close to being ready for a beta release and ultimately being merged into core WP, its API and patterns are at a level mature enough that theme authors (and theme shops!) can start planning ahead for the inevitable adoption of the new block system. In this post we’ll see what the average theme author should have in mind when updating a theme for Gutenberg compatibility and ponder about the future in theme and plugin editing.
Backwards compatibility
First of all let’s dispel some myths or worries (if there are any left at this point). Gutenberg does not aim to break the web. It will indeed come with a grace period and be backwards compatible with “old school” WordPress. The Gutenberg FAQ is a great place to start reading about how this will work and the commitments the Gutenberg team has made in regards to it.
I’ll sum up a few key points (TL;DR):
Existing post content will stay intact. The “Classic” block will offer an editing experience which is exactly the same as the one we have right now (with TinyMCE).
The Classic Editor plugin will offer the choice of disabling Gutenberg until a theme can be 100% confident it’s
Source: https://managewp.org/articles/17244/things-to-consider-when-updating-a-wordpress-theme-for-gutenberg
source https://williechiu40.wordpress.com/2018/03/21/things-to-consider-when-updating-a-wordpress-theme-for-gutenberg/
No comments:
Post a Comment