13 Comments

  1. Nick Diego
    · Reply

    Thanks for the Block Visibility shoutout Justin! 😉

    Report

  2. Sally G.
    · Reply

    “The theme designer in me wants to disable the UI for this altogether and present something slightly more controlled: an image size selector.”

    Well, as a user, I almost never use a featured image, especially with an event listing or short post, as it often seems to dominate the page. I will likely add the image at the top left character of the first paragraph, then go to the HTML editor to see the size, and grab my trusty calculator to play with some options, keeping the ratio equal—and now I have Yellow Pencil to align the top of the image with the top of the text as I would expect to do in print!

    Report

  3. Chinwe
    · Reply

    This is awesome

    Report

  4. Matías
    · Reply

    What do these options actually do?

    Good call!: https://github.com/WordPress/gutenberg/pull/34158

    Report

  5. Aimee
    · Reply

    Is it still a recommendation to NOT use the Gutenberg plugin with i.e TT1 theme on production sites?

    Report

    • Justin Tadlock
      · Reply

      That would be the recommendation, correct. TT1 Blocks is a block theme, so it enables experimental Full Site Editing features.

      But, there are plenty of folks (WP Tavern included) who run Gutenberg itself in production. We’re actually planning to relaunch our site’s design on a hybrid/block theme sometime soon (more on that later), so it will be interesting to see what sort of problems we run into in a real-world test.

      Report

      • Aimee
        · Reply

        Thanks for your reply! I might try using Gutenberg in production then, just not with a block theme. I really like the new features and I need the navigation menu and I don’t have the strength really to wait for 5.9 🤪.

        Report

  6. Nick
    · Reply

    So in order to get the padding control I need to have add_theme_support( ‘custom-spacing’ ); in my functions.php file. But to get the margin controls (which share the same panel however) I need to add support for it in the theme.json file, which 99.99% of all themes available don’t have it, and don’t use it? Somebody, please correctly me if I’m wrong…

    BTW, padding/margin controls should had been handled 3 years ago, not now, where almost all block libraries have implemented their own versions of them, making the backsite more confusing and complex to end users (content makers – web designers, etc…).

    Also, there are only 16 (sixteen – XVI) FSE themes on wp.org (so they do use theme.json I assume) but most are just embarrassingly horrible, as all the WP default themes with the only probably exception of Twenty Twelve – (at the time 9 years ago). I can’t use any of them for a customer site (at least with a straight face)…

    I am going to stop here so I won’t break any of the rules here… but seriously though, as a theme/plugin developer (not a user), I’m 40% excited and absolutely love these new things, and 60% frustrated, angered, which sometimes melts to pure raw “postal” rage, and then back to being excited – it’s a true love/hate story ! BTW, my frustrations are only 60% thanks to ACF Pro, where I can build my custom blocks exceptionally fast, and exceptionally easily.

    Report

    • Justin Tadlock
      · Reply

      The goal is to move all such settings to theme.json. So, if you want both margin and padding support, just add them both to that file instead of splitting them up. You can use theme.json without building a block theme.

      I hope the development team eventually makes this filterable via PHP so that theme authors can choose to implement this via PHP instead of JSON based on their personal preferences. It’s one of those things that just seems like such an easy way to win over current theme developers.

      Report

      • Nick
        · Reply

        “You can use theme.json without building a block theme.”

        That I did not know, I will start looking at docs, how to implement the theme.json file in traditional themes… immediately.

        Thanks for the info Justin, and I hope they listen to you about the filterable via PHP, just for us to have all the options available.

        Report

    • richard Ginn
      · Reply

      Nick is right. Padding and margin need to be a Gutenberg default no matter what theme you use.

      Report

    • Steve Grant
      · Reply

      padding/margin controls should had been handled 3 years ago, not now, where almost all block libraries have implemented their own versions of them, making the backsite more confusing and complex to end users (content makers – web designers, etc…).

      the divergence of 3rd party solutions stacked on top of Gutenberg, with their many libraries and freemium upsells has prevented me from using any 3rd party add-on. It adds another layer of unpredictability to the ecosystem. One day I add a FreeBlocksStylez padding to my site, then a month or so latter there’s an update to the plugin with the news : “FreeBlocksStylez has become part of the ProBlocksCorp group and renamed to ProBlocksLite – and here are some upselling admin nags”

      I don’t need that extra layer of annoyance, so I stay away from add-on suites, they are too unpredictable and will be a burden on my future self.

      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: