A Twitter Storm by Kevin Hoffman
This is a great summary by @kevinwhoffman implications and challenges of #Gutenberg for various user groups of WordPress: Plugin Devs, Theme Shops, Agencies & Consultants, Users – Read the whole thread at the end you get to 'What do we work on next' part. 🙂
I'm seeing talk of how clients will be lost and users will leave #WordPress when #Gutenberg drops. As a former freelancer, in-house developer, agency designer, custom theme developer, and now plugin developer, here's a practical look at how Gutenberg affects each.
— Kevin W. Hoffman (@kevinwhoffman) December 21, 2017
Gutenberg Development ~ Beginner's Tip of the Day #12 🤓:
— Zac Gordon (@zgordon) December 21, 2017
There is an interesting discussion on how plugins should handle fallback to the Classic Editor. If you're a plugin dev, you should check it out – https://t.co/4zr8ACW65s#WordPress #Gutenberg #Deeply pic.twitter.com/PKCSaz1nQ0
Introducing our latest white paper, 'Starting with blocks: Reimagining a future with Gutenberg'.
— Human Made (@humanmadeltd) December 20, 2017
An in-depth dive at the new WordPress editor for agencies and enterprise. Download it now: https://t.co/gCTaSg40EQ pic.twitter.com/UQkY2gHQ6g
REALLY nervous about this, all of my sites use multiple instances of the WYSIWYG in ACF:
— Amber Weinberg Jones (She/Her) (@amberweinberg) December 21, 2017
"…some of their field types may break, in particular, the field types heavily relying on JavaScript DOM events and/or the TinyMCE API"https://t.co/gMvmQuNclG @riadbenguella #gutenberg
The more I write in Gutenberg, the more I prefer it over the classic editor.
— Jeff (@jeffr0) December 20, 2017
Announcing Frontenberg! A frontend, logged out #Gutenberg playground that lets you test out the new #WordPress editor instantly https://t.co/0jj7xYm3Ds pic.twitter.com/KCJLP0nate
— Tom J Nowell ✨ (@Tarendai) December 20, 2017
Gutenberg Development ~ Beginner's Tip of the Day #11 🤓:
— Zac Gordon (@zgordon) December 20, 2017
To use JSX in your blocks, simply add the 'transform-react-jsx' plugin like done in the Gutenberg Core .babelrc file – https://t.co/s27KdRe0M0#WordPress #Gutenberg #Deeply pic.twitter.com/TZLIwFKrZG
Thinking about this a lot this morning: How can we WordPress Consultants get our client's content creators through the "dip" of the change to #Gutenberg
— Birgit Pauli-Haack (@bph) December 20, 2017
Gutenberg will convince more new people to use WordPress. The pie grows. pic.twitter.com/uk5nKbVQ8q
Of all the #gutenberg things, putting actionable code in comments makes me cringe. Am I the only one?
— Caspar Green (@i_Caspar) December 20, 2017
<!– wp:image {"id":1691,"align":"right"} –>
<figure class="wp-block-image alignright"><img src="…" alt="" /></figure>
<!– /wp:image –>
Photo by Viktor Kiryanov on Unsplash
