In Episode 75 of Divi Chat, the panel got together to discuss the latest release of the Divi theme, the Developer Edition, Divi 3.1.
Episode 75’s panel featured:
• David Blackmon of Aspen Grove Studios, Divi Space and WP The Podcast
• Leslie Bernal of A Girl and Her Mac
• SJ James of Divi Space
• Sarah Oates of Endure Web Studios
• Cory Jenkins of Aspen Grove Studios and Divi Space
• Terry Hale of Mizagorn Ink
• Jerry Simmons of Feverent Solutions
During the episode, the panel discussed their first impressions of the major 3.1 release, as well as the considerations of the React components, what the update for means Divi users, and what the update process entails.
From discussing the theme update process (and what to do in the event that something goes wrong), the panel also discuss the update from the perspective of both website creators as well as developers that make third-party plugins.
If you’re interested in hearing the opinions of a collection key members in the Divi community, watch Episode 75 of Divi Chat.
Get connected!
To stay up to date with the latest releases from the Divi Chat panel, be sure to subscribe to the podcast via YouTube and iTunes and follow Divi Chat on FaceBook and Twitter.
If you’re already following the podcast, be sure to leave a review for the panel on iTunes.
We want to hear from you!
We hope that you’ve enjoyed this recap of Episode 75 of Divi Chat, and that you’re a bit more clued up on using Jetpack with Divi. If you have any questions or comments please feel free to share them below. We love receiving your feedback!
Thanks for reading!
Hi folks,
I agree with SJ when he says that functionality wins out. If Gutenberg sticks to the fundamentals of a foundation for others to build on with a section/row/column/block/module structure I think that we could be on to something good. Coupled to this an API for page builders to hook into I can see a perfect symbiosis for both Divi, other builders and Gutenberg.
I found setting up the environment fairly straight forward and trouble free ( I went the Docker root). I got some basic modules made but would need to see more documentation and tutorials to really get to grips with it and produce something useful. I ran into an issue whereby the module a I made behaved in a global manner. Change the settings in one instance and the settings in another changed to match in tandem.