Skip to content
Code. Food. Politics. Religion. Tech. Not necessarily in that order.

Page Builders in the Age of Gutenberg

Questions covered:

  • What’s page builder?
  • If you already use a page builder on your site, would you consider switching to Gutenberg?
  • When starting a new WordPress site, what considerations would you take when choosing between a page builder, Gutenberg or the classic editor? Which one would you choose?
  • Is Gutenberg using flexbox, grid layout or Bootstrap for its columns? What would be the best approach?
  • What does Gutenberg solve that Page Builders don’t? Vice Versa?
  • Why would a user want to use both a page builder and Gutenberg on the same site? Would they want to?
  • Should page builders continue to be their own interface or adapt and integrate into Gutenberg as a collection of blocks?
  • Should developers focus on developing for page builders, Gutenberg or neither?
  • As a developer, I feel like Gutenberg is incomplete. It misses features like sections, column flexibility and code syntax highlighting. What does the future of Gutenberg looks like for developers?
  • What are the implications of themes that come bundled with page builders and extra plugins (e.g. “The7” with “Visual Composer”)? My impressions are those bundled plugins/builders can run into conflicts and redundancies with similar stand-alones (e.g. WPBakery). Advice? Best practices?
  • What are some new features coming to Gutenberg? What is currently in the work?
  • What’s bad about having “more” plugins in a WordPress installation to go with Gutenberg?
  • How do you spot a bad Gutenberg plugin?
  • Does Gutenberg work with the theme Generatepress?
  • As a content creator with no coding knowledge, should I use something like Gutenberg or continue using more popular page builders like Elementor?
  • Would using Gutenberg reduce website maintenance requirements (compared to using themes/other page builders)?
Posted in