We know you have questions about Gutenberg. We all do! This session aims to answer those we can in an informal discussion meant for all levels of expertise. Together we will determine answers or explain how to get them answered.

Presentation abstract

Panelist and moderator

• Lara Schenck. Twitter: @laras126
• Leo Postovoit Twitter: @postphotos
• Roy Sivan Twitter: @royboy789
• Matt Cromwell. Twitter: @learnwithmattc

Gutenberg will focus on the editors user experience so front end and visual display of things will be baked into the process. Good!

Fears

Structure data and JSON not baked in by default with Gutenberg, but Roy Sivan is developing a plugin called Gutenberg Object Plugin which aims to saves Gutenberg data as an object / array and allows you to access it via REST API.

Data scares me when it comes to Gutenberg. How Gutenberg saves data to the database not having structured data outside the ecosystem makes it pretty scary. How are we addressing developers concern to have clean data?

All of sites already in production won't necessarily be broken in Gutenberg. Test, Test, Test! Unless we train people on how legacy sites should look like. Yes, the classic editor plugin helps but turning it on by default can be a big problem because sites may break.

Fears that we’re not going to have any hard drive space because its all going to filled with node modules.

Also fears that separate experience for how front end and back end will function.

Gutenberg scares me to death and he’s more a designer and use page builders (although not divi) but helps me control exactly how user interface will work. And is afraid that WordPress 5.0 will destroy all that. Does he put in classic editor and keep the customization he’s built.

Gutenberg is the future of WordPress

For end user nothing will change if you use classic editor and Gutenberg Ramp plugin. Don’t change workflow now, but the future is Gutenberg so

Their is a difference from a page builder and content for Gutenberg. Block are like sections on a page and until the layout blocks come out then we’ll run into problems. Contact theme developers. Its up to them. When 5.0 comes out you should be able to update 5.0, update theme and update plugins should work. If it doesn’t work then you may need to start looking for a new developer to work with.

HTML and CSS is a beautiful medium and awesome and it might be much easier to write in pure CSS and HTML instead of depending on a page builder to help transition for new theme development. Yes!

Advanced Custom Fields 5.0 released this week and can be used for creating Gutenberg blocks.

Is theme development a problem. Gutenberg is a content editor so it won’t affect theme. Roadmap is content editors > layout blocks > theme development.

What is the schedule for Roadmap. Content editor is due this calendar year. What comes after? It depends on how well 5.0 really goes.

Are page builders specifically divi integrate with Gutenberg? Yes, that’s the plan but may have some nasty code on backend. Still a wait and see.

Test what the critical things in our workflow need to be supported. If those work then safe to go with Gutenberg.