Update #43 HumanMade White Paper, Twitter Storms, and more

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 🤓:

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

— Zac Gordon (@zgordon) December 21, 2017

Introducing our latest white paper, 'Starting with blocks: Reimagining a future with Gutenberg'.

An in-depth dive at the new WordPress editor for agencies and enterprise. Download it now: https://t.co/gCTaSg40EQ pic.twitter.com/UQkY2gHQ6g

— Human Made (@humanmadeltd) December 20, 2017

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 🤓:

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

— Zac Gordon (@zgordon) December 20, 2017

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

Gutenberg will convince more new people to use WordPress. The pie grows. pic.twitter.com/uk5nKbVQ8q

— Birgit Pauli-Haack (@bph) December 20, 2017