8 Comments

  1. Timothy Jacobs
    · Reply

    Besides the Framework issue, I don’t really understand at all how this plugin was approved with those function names. The prefix rule is fairly straightforward.

    Aside from that, I have to admit I’m not really a fan of these types of plugins that just embed forms in the block editor. It completely takes way from the idea of WYSIWYG and what really makes Gutenberg special IMO.

    It is also distressing to me that developers still aren’t taking the time to learn JavaScript and build native blocks.

    Report

  2. Mahdi
    · Reply

    What is this? Fake blocks! Gutenberg wasn’t meant for creating blocks like this, as it is clear that going towards this direction is not the one that core encourages.

    Report

    • Justin Tadlock
      · Reply

      There is a clear need for dynamic blocks, even in WordPress itself (e.g., categories, latest posts, etc.). Genesis Custom Blocks is a great option for building those.

      I do agree that much of what will be built with plugins like these would be better handled as static blocks via JavaScript. However, there is also the transitional period to consider. These types of plugins help many developers move beyond their old methods and to plant a foot in the block world. While it’s not the ideal way to build blocks, it is a step that many might not have otherwise taken.

      Report

  3. Damien Carbery
    · Reply

    I’ve found the learning of JavaScript intimidating and unclear even where to start. I’ve experimented with ACF Pro’s Blocks and tried out Genesis Custom Blocks recently.

    I figured out how to distribute a block and its field definitions in a plugin: https://www.damiencarbery.com/2020/09/distribute-genesis-custom-block-in-a-plugin/

    It doesn’t seem as heavy as ACF Pro so it might be an option for those, like me, that aren’t quite ready for the jump to pure JavaScript block development.

    Report

  4. Grégoire Noyelle
    · Reply

    Thanks for the post Justin.
    I’ve tried Genesis Custom Block and it save the data in JSON format in the post table, like ACF Pro do. ACF seems to be the way to go with far more options than Genesis Custom Blocks.

    Report

  5. Marcy Diaz
    · Reply

    I’ve tried out this plugin, and it’s easy to create blocks for those of us who don’t know much javascript, but are able to use PHP.

    While creating a block uses only fields, the block developer is supposed to create a template to display the fields in both the front and backend. So it does become WYSIWYG, at least the way I did it, it was. The fields are simply the controls that most blocks have in the sidebar, but they appear in the editor content when you click to edit the block.

    I’ve also used ACF, but this just seems lighter to me, if I need to create a custom block for a client.

    Report

  6. Knut Sparhell
    · Reply

    I have been using Block Lab a couple of years. This is it’s successor.

    The main point is to avoid making custom shortcodes and as client to insert them. The second point is to avoid page templates for something that can be templated by just one block, or a group of blocks (in columns and such).

    Server rendered blocks are important in a transition phase over many years. And many prefer dynamic blocks to be rendered on front without javascript.

    Report

  7. Steven Gliebe
    · Reply

    This will be interesting to those who assemble sites for clients but are not necessary developers, yet need to make some small, semi-custom content area for a client. Clever way to bridge the technical gap.

    Report

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.

%d bloggers like this: