1. Steve Grant
    · Reply

    As long as the devs communicate clearly how to turn it off. I mean hide and disable the entire feature.

    When patterns were first introduced my problem was not the interface but that it offered my clients a way to totally wreck their websites with a few clicks. Within seconds an office junior could grab disparate design patterns from a global library and turn a site into a patchwork quilt.

    It took a lot of searching to find out how to deactivate the pattern library, and the little spamvertising link for “blocks you might like”.

    Please consider those websites which have a supplied set of elements and do not want 15,000,000 random unrelated design patterns on tap. Please indicate clearly the current methods to turn off the firehose.

    Currently I have:

    remove_theme_support( 'core-block-patterns' );
    remove_action( 'enqueue_block_editor_assets', 'wp_enqueue_editor_block_directory_assets' );
    remove_action( 'enqueue_block_editor_assets', 'gutenberg_enqueue_block_editor_assets_block_directory' );

    But who knows if these are going to remain current, and enough to protect shipped sites?


  2. Spencer Forman
    · Reply

    I’m an outspoken “convert” to Gutenberg as of this year…which is saying quite a bit, since I was one of its harshest critics for many years.

    But I am personally quite confused as to why there is so much energy being put into “random” design patterns and blocks versus a similar effort being put into “fundamentals”…ie: things that are universally necessary and beneficial for most page layouts and sales pages, etc.

    Wouldn’t more people benefit if there were wireframe type designs available in large quantity, making it simpler to get a result on a page with one click versus having to go to third-party plugins (ie: Kadence or Qubely) for this?

    Hoping we can also see some movement towards a canvas theme for core instead of an annual “design” theme… since it seems that no one benefits from those in a world where WP is trying to get everyone using the block editor’s design capability.


    • Zlatan Gruvocsic
      · Reply

      … the block editor’s design capability.

      This capability will often be used exactly once in a lifetime of a website, at creation time.

      Adding some bi-yearly news post with one title and three paragraphs of text or editing some opening hours in a footer widget or exchanging a restaurant menu image or PDF file with a new version but for SEO the same path-/filename (almost impossible in WP) are the features for most real world scenarios.


      • Spencer Forman
        · Reply

        I think you and I agree… the “one” time someone needs convenient access to useful generic block patterns (wireframe) vs. some esoteric patterns is when a site is created. Otherwise, as I suggest, one has to go out and get plugins to offer the same ;-)

        I don’t see the purpose of having a pattern library of “random” patterns that are not generic and purposeful to end-uses (ie: sales pages or media or calls to action), but rather are very esoteric design oriented as thusfar demonstrated?


  3. Nick Diego
    · Reply

    I was doing a bit of research earlier and discovered the filter “should_load_remote_block_patterns”. This allows you to disable all block patterns that are fetched from the WordPress patterns directory. You can then register your own client-specific patterns as you wish.

    That said, your overall point is well taken. While there is value to the new pattern explorer to many segments of the WordPress community, it also can be a hindrance as well. With any new feature, there also needs to be a way to turn it off.


  4. Paal Joachim Romdahl
    · Reply

    I believe we need a toggle inside Preferences so that we can choose to hide the Patterns tab seen inside the Inserter screen. I went ahead and made this issue:
    Preferences: Adding a toggle to hide Patterns.


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: