on how to use WordPress • They’ll need to be prepped on why it’s important to upgrade. • They will have specific questions about their site and what to expect.
based on timeline • Since there’s no active development, you could use explain options • Classic Editor would work best here, for a short time • Encourage them to upgrade as soon as they can
• Tell them what’s happening and give them their options • Be honest and try to help mitigate • Try to encourage upgrade, fallback to Classic Editor • Encourage them to upgrade as soon as they can
come • Security and Maintenance updates right when they come out • A more powerful editor to create fantastic content • You’re using the system that will be adopted in other areas of WordPress in the coming years • The ability (potentially) to drop premium plugins that can be accomplished in 5.0 thanks to Gutenberg
upgrading - both time and money • Your site could break - content, theme, and other plugins • Many plugins will not be compatible on the day 5.0 comes out • •Many plugins will likely turn Gutenberg off for a short period.
a case by case basis • For smaller sites - perhaps straight blogs or informational sites - you’ll be able to upgrade to 5.0 more quickly. • If you have a page builder, are a large amount of different types of content, you’ll likely want to recommend upgrading, but can use the Classic Editor for a small amount of time. • Let Your Clients take it for a spin! • Setup a WordPress install with Gutenberg or send them to a service like Frontenberg
current content? • Will Plugin I Love work? • Do I have to upgrade to 5.0? • What happens to my theme? • Can’t I just use the Classic Editor plugin forever?
your host • 2. Install the Gutenberg Plugin • 3. Install any betas of important plugins that add Gutenberg Support • 4. Inventory Content • 5. Create a Kitchen Sink Page • 6. Conduct Tests (Checklist in resources area) • 7. Document Everything • 8. Offer Feedback • 9. Fix what you can!
that affect the frontend, you’ll have the same issues you see in the themes. • If you add meta boxes or shortcodes, you might consider adding block support for those. • If you have a Custom Post Type, you’ll need to make sure REST support is enabled with 'show_in_rest' => true.
CSS to support new blocks • Add some generic classes that can be added to blocks • Add theme support (link in Resources section for this) • Test every template. • For your plugin: • Test it as much as possible • Take stock of all the functionality, particularly anything that affects the frontend or the editor
Gutenberg and Gutenberg Theming. Visit creatorcourses.com/gutenberg/ and use the code ITHEMES at checkout. For this offer + more resources, you can visit casabona.org/ithemes-workshop
jcasabona
ambitiondx3300
arigatobank
sonas
shinu
shinxtanaka
petra_wille_strong
coconala_hr
iwacci
708
1120
suzakiyoshito
timigod
myddelton
nonsquared
62gerente
holman
roundedbygravity
pedronauck
mclloyd
reverentgeek
jacobian
3n
paigeccino
