Gutenberg

When gutenberg first appeared in wordpress, I very quickly found myself, along with lots of other people, downloading plugin that removed gutenberg, or at the very least gave a choice on how to edit content. My initial experience with gutenberg involved a whole lot of moving my mouse around the screen trying to figure out how to add a block, or move a block. It was incredibly frustrating. For this updated site, and my new photo galleries, I decided to try gutenberg again. It has been a while, with numerous updates and I assumed some needed user interface improvements in gutenberg.

Why is a good question, and there are in my mind two good reasons. 1) Gutenberg is here to stay, so continuing to ignore it probably means losing out on WordPress features going forward, and 2) Advanced Custom Fields is the only plugin that I use on almost every site, except for a security plugin. ACF is vital to building a custom theme and making the admin interface easier for clients to access content in a way that makes sense. The only problem with ACF is the content is stored in the post_meta table, and not the posts table. I am not sure how big a deal this is in the grand scheme of a wordpress site and how it interacts with search engines. I can explore this later, but I believe it is better to have as much of the post content in the post content field. A topic that would be useful to understand better.

Gutenberg provides some of the same flexibility as ACF, but keeps the content in the posts table. Plus, I just learned that ACF can help in creating custom blocks within Gutenberg. This would be convenient, as making custom blocks for gutenberg is somewhat involved. I looked at it a while ago, but then stopped, as I wasn’t using gutenberg and it is a bit involved. I haven’t explored this in detail yet, but for me, gutenberg is primarily useful if it can help me streamline a clients editing of content. In other words, make it easier for them.