12 Comments

  1. Tomas
    · Reply

    Mm, why not Genesis Custom Blocks plugin? Build the block yourself in few minutes – exactly as you want them to be.

    Report

  2. Li-An
    · Reply

    If you need footnotes, go Markdown in Classic Editor. It works like a breeze.

    Report

  3. Rob Lilley
    · Reply

    Similar to this, when using the Elementor page builder I was overwhelmed by the sheer volume of addons (widgets and extensions) there were out there – it took me hours to find the right ones for my projects.

    My only option was to build my own directory where I could quickly search, compare, and find what I was looking for, which you can see here:

    https://wpwhichplugin.com

    This is updated weekly and is available to anyone that might find it helpful. I’ve been thinking of doing something similar for Gutenberg blocks.

    Report

  4. DJ Johnny Medley
    · Reply

    Awesome share, Justin! Thanks so much for starting this series.

    Report

  5. Gary Taylor
    · Reply

    Useful list Justin, thanks (I’m still using WP-Footnotes, which is no longer supported but still works).

    I share Andrés’s frustration, and regularly download block libraries to a test site and try them out on a page to compare and contrast with other libraries. I still feel that block libraries should be more like block frameworks, where you download the ones you want and ignore the rest (as opposed to downloading them all and then having to turn off the ones you don’t want on a settings page).

    One problem with the one-shot blocks is that they sometimes disappear (which isn’t sorta brilliant). With plugins, if I’ve downloaded them I can still use them if they work (and even fix them when they don’t – I use a wiki-style links plugin written for php4, now updated) and sometimes I throw the routines from these small plugins into one larger file to keep things simple. Could I build a block library of my own using the one-shot blocks, I wonder…?

    Report

  6. Bridget
    · Reply

    I just experienced this same frustration yesterday. Usually, I build custom themes with custom blocks, and remove any blocks not needed/supported by the theme. However, I’m supporting a client with a purchased theme who is adding additional languages to the site. They have an accordion plugin that uses shortcodes, which a pain to manage because you have multiple places to enter/change content instead of having everything in the page. I figured switching to an accordion block would be beneficial before translating the site into 6 different languages. However, the only well supported (backed by WordPress focused companies) accordion blocks I could find are bundled with other blocks. The problems with bundling blocks are: I don’t have budget/time to make sure all the other blocks look nice or work well in this purchased theme, the extra blocks create confusion for site editors and don’t follow the premise of “decisions, not options”, and there isn’t a way to easily disable blocks for every user, and never allow the bundled blocks plugins to add more blocks to the site in the future. I wish bundled blocks plugins had separate settings to exclude/include blocks (instead of the user’s page preferences) where you can check which of the bundled blocks you want to enable for the theme. More like Jetpack’s options instead of per user options.

    And before anyone points out the allowed_block_types filter – yes that is great if you built the site and have controlled what is added to pages from the start. But, I don’t know what blocks have been used throughout the site and what the site editors are used to – and the names of blocks change, gosh darn it: see core/button[s] and core-embed/[service] . I could build a custom block, but it isn’t in the budget.

    And sure, you shouldn’t look a gift horse in the mouth, but I can’t be the only one who has these frustrations with bundled block plugins.

    Report

    • rxnlabs
      · Reply

      There is the plugin Disable Gutenberg Blocks – Block Manager https://wordpress.org/plugins/disable-gutenberg-blocks/ that I use on sites to disable blocks that won’t be used or to disable blocks that offer the same features of other blocks. Even though it hasn’t been updated in a while, it still works and the functionality is simple enough that it should not need to have regular updates to keep working.

      You can then use the plugin Find My Blocks https://wordpress.org/plugins/find-my-blocks/ to find used blocks and compare that to the list of blocks that you want to disable.

      Not a perfect solution but will greatly reduce the number of blocks that you have to worry about.

      Report

    • Tim Nolte
      · Reply

      So, you can disable blocks without concern for breaking the site where they may be used, the only catch is that they will end up showing a warning in the editor and ask a user to convert it to HTML. However, I will also say that trying to find the actual names of the individual blocks in a block library plugin, to allow only the ones I want, can be a real pain.

      Also, recently Core broken the filtering of embed blocks because they decided to convert them all to block variations of the generic core/embed block. 🤦🏻‍♂️ I opened up an issue on this to point out that they broken documented existing functionality. They didn’t bother to note this in their release notes, or apparently even realize they were breaking their own functionality.

      Sometimes it appears that Gutenberg has gotten too big and no one actually understands they impacts to other areas when they make changes. They obviously don’t have enough automated tests to flag these broken regressions.

      Report

  7. Zebulan
    · Reply

    I’ve got a PR to add a Table of Contents block into core. It automatically creates links to headings with ids/anchors (but doesn’t create the anchors itself… that’s something that should be handled by a change to the Heading block), it supports multi-page posts (including a toggle to only show headings from the page that the block appears on), and can be quickly converted into a static List block for further customization.

    All it needs is some feedback on the naming (e.g. “Table of Contents” versus “Document Outline”), some code reviews to ensure the technical implementation is sound, and a fix for a block-selection bug that currently exists but is unrelated to the PR itself.

    https://github.com/WordPress/gutenberg/pull/21234

    Report

  8. Patrizia
    · Reply

    Getwid (https://wordpress.org/plugins/getwid/) includes (among others):
    – Table of Contents
    – Countdown
    – Accordion
    – Toggle
    – Tabs

    It also allows you to enable/disable on a block by block basis.

    Report

  9. Mukesh Panchal
    · Reply

    Justin thanks for sharing and starting this series.

    If you know a little bit about coding then you can develop a block using the ACF Pro( https://bit.ly/37vwJXI ) plugin they provide an easy interface to add a new GB block in WordPress

    Report

  10. Sallie Rachel Goetsch
    · Reply

    PS. Isn’t the trope rather than people tell bartenders things, rather than ask them?

    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: