As a WordPress agency, we have decided not to use Gutenberg, the block editor for WordPress. When it was first introduced, we were excited about the potential improvements it offered over the classic editor, but after trying it out, we found that it had several major issues that prevent us from using it for our clients’ websites. The user interface is less intuitive and the development experience is more difficult and less efficient than our current approach. We believe that there are better options available for our clients and for our development process.Highlights00:00 Intro00:28 Potential of Gutenberg03:11 Fundamental issues of Gutenberg04:14 Issue 1: User Interface is not made for end users19:15 Comeback of the webmaster?22:13 Issue 2: Breaking design is too easy / HTML rendering30:14 Experience with Gutenberg blocks based on ACF34:07 Is Gutenberg worth using it?34:36 Gutenberg works well for long copy editing38:15 Issue 3: Fast development without central documentation42:21 Should we use it? Not yetLinksGutenberg: https://wordpress.org/gutenberg/Flynt: https://flyntwp.com/ACF Pro: https://www.advancedcustomfields.com/pro/Elementor: https://elementor.com/Beaver Builder: https://www.wpbeaverbuilder.com/CSS Container Queries: https://developer.mozilla.org/en-US/docs/Web/CSS/CSS_Container_QueriesContent-only editing in Gutenberg: https://richtabor.com/content-only-editing/10up Gutenberg Best Practices: https://gutenberg.10up.com/More from BleechBlog Posts (WordPress Development)Flynt (WordPress Starter Theme)VRTs (Visual Tests for WordPress)Siegfried, deploy! (YouTube Channel)

Ver todos los episodios