8 Comments

  1. Cameron Jones
    · Reply

    100% yes

    Report

  2. Carolina Nymark
    · Reply

    Another option is to include block patterns that use more than one style, this is easy since they are only CSS class names.

    Report

  3. Igor
    · Reply

    This is where I struggle every time. I think, just option in style initialisation that this style can be used as multiple style or single is enough

    Report

  4. Jay
    · Reply

    The primary reason for this is that core has already made many obsolete through block options

    I’m not sure that the addition of richer design tools will make block styles obsolete. I think those tools present an opportunity to create a more flexible environment in which styles can created and shared.

    Such an environment could even result in an explosion in usefulness. Styles based on portable configuration files are to me a much more exciting prospect than those based on static css that is tied to a specific theme.

    Report

  5. Mark Root-Wiley
    · Reply

    I spent a lot of time thinking about this article and the corresponding Github issue. I put together my thoughts in a blog post about making a second faux Block Styles interface to work around this problem and then a long reply to the issue on Github.

    tl;dr – I think the answer is to support Block Style Categories with a limit of one selected style per category. I’d love to know what other people think!

    Report

    • Justin Tadlock
      · Reply

      That is a really interesting approach that finds a balance between both ends of the spectrum. If, ultimately, we decided to let users select multiple styles, I could get behind this idea. I like it.

      Report

Leave a Reply to Cameron Jones Cancel 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: