20 Comments

  1. Per Herngren

    The possibility to change the line-height in headings is really inspiring!!!

    Report

    • Ciprian Popescu

      Agreed. That should be done in theme’s CSS, in a reset stylesheet, for example, where you can set default line-heights for each heading.

      Consider a user scenario where they set different line-heights for different headings on different pages. The design consistency is severely affected.

      This is definitely theme territory.

      Report

      • Justin Tadlock

        I’m not sure about of some of these things on a per-block basis at this stage. I would rather have this set via the Global Styles system that is upcoming. Let themes set the default on a global scale. Then, let users overwrite it, also on a global scale, if they want. After we get all of that in place, we can then decide if we want to provide these design controls on individual blocks. To me, it feels like we’re working backwards.

        Report

  2. Nick DerAvedissian

    If you had custom patterns (via custom code) or by using Justin’s awesome Block Pattern Builder plugin, there was a delay of 3-4 seconds for the patterns to be presented for selection…, with this update, the patterns show up almost immediately – impressively fast compared to before.

    One thing that is extremely frustrating to me is that only now we are getting some very basic stuff like line height controls and easier button styling for example…, these should have been before Gutenberg was merged in the core, and not 15-16 months after the fact. I would also love to see some of Google fonts insertion to the heading and paragraph blocks for example, with may be with some sort of a warning that having too many web fonts will slow down the site. I can see some abusing the use of web fonts, and making more harm to their sites than good.

    The Click and Drag issue when the toolbar is set on top is still not fixed, which makes my hair turning grey by the hour !

    Overall though, I agree with Justin, it’s a relatively speaking nice update.

    Report

  3. Bjarne

    I’d love rock solid UX that didn’t change on each update – for instance drag and drop capabilites on blocks, not depending on toolbar location – before more gradients and other fluff.

    Been a big advocate of Gutenberg since 1.0, as I liked is principles, but its really hard to keep people on board when UX is changing fundamentally.

    That said, the nerd in me, enjoys the momentum of the Gutenberg development, and the increasing support from theme and plugin devs. Today its possible to create some really beautiful blogs, easily and for free.

    Report

  4. Ricardo

    It is amazing the speed of Blocks development.
    I love blocks and it’s potential.
    I just hope they don’t collide with themes and template design.
    It would be a disaster to watch one “brother” smash the other.
    They should evolve seamless.
    And I hope template design isn’t getting like a 2nd choice because it is the essence of any system.
    Right now, the environment around blocks feels like a playground.
    It can led to initial enthusiasm at the beginning but also to frustration and to choosing other solutions after a while.
    A system has to be solid and stable to keep it’s users.
    We cannot forget the true power of WP as a tool: it’s Database control and easy feed. The connection between it’s input (blocks) must be flawless.
    WP forever.

    Report

  5. Ciprian Popescu

    For me the pattern feature is the second useful feature in Gutenberg, after the columns, and I’ll definitely create a library of patterns to go with my company’s design offer.

    Right now I’m using reusable blocks everywhere, for header, for footer, for various “patterns” such as columns, feature boxes and so on. As the patterns are blocks as well, I assume the migration from reusable blocks to patterns will be pretty easy.

    Report

  6. Gary Taylor

    If I read the release notes correctly, the title block will become an actual block, with the permalink only available via the right-hand panel. That’s a bit annoying for me (your mileage will vary, of course), as above the title block seemed to the most appropriate place for it to be, and only visible when you wanted it. I’d just tidied up that Document section by disabling the Permalink tab, now I’ll have to reinstate it. Ho hum.

    Apart from that… who are all these people crying out for gradients? Was there a great social movement somewhere, and I missed it? ;-)

    Report

    • Rod Olman

      Do Wix and Squarespace have gradients in their page builders? That’s where you should be looking when you ask yourself “why is feature X in GB?”.

      Report

    • Justin Tadlock

      Yes, eventually the post title should work exactly like other blocks. It may seem a little weird right now given what we’re accustomed to. But, thinking long term, the entire post title/header area should be a block or group of blocks. This would allow users to easily do something like a full-width image behind the title with perhaps the post meta, intro, etc. (whatever they want).

      I currently have a system of doing this with a mix of a page template that removes the title plus me manually adding a cover block in the post content. It’s terribly complicated for the average end-user.

      Report

      • Gary Taylor

        Good point re backgrounds for post/page titles, I do that using css at the moment. It would be handy if the Excerpt field was a block underneath the title block, which is where visitors would see it on my site.
        (By the way: I think I accidentally hit the ‘Report’ button when I meant to hit Reply. Fat fingers. Sorry.)

        Report

  7. JDP

    I’m just going to leave this one here. The Gutenberg UI for dealing with post metadata is horrid. I wait on each release to address this awful shortcoming. No satisfaction yet.

    I’m not a developer but I know enough php and jQuery to have created some really useful metadata boxes for our organizations website. Sure the traditional php based metaboxes are still there but without refreshes, it’s very difficult to see if the action hooks are still firing the way they used to. Several of the metaboxes I developed use dynamically developed options for select controls and/or autocomplete from an AJAX data source. Used to take me 5 lines of server side code to render a second editor to save fully HTML formatted metadata. Try that now in Gutenberg.

    Maybe I’m not the target demographic but my metadata is as important, maybe even more important than the post content. WordPress went from slightly awkward but robust for post metadata and took many steps backwards to the current Gutenberg UI for metadata. Gutenberg might be terrific for post content but it’s an epic regression for dealing with post metadata in my opinion.

    Report

  8. Taras Dashkevych

    Do you know if it will be possible for the theme authors to disable specific controls (for example, the line-height control) via filters or add_theme_support ? Something similar to add_theme_support(‘disable-custom-font-sizes’);

    Report

    • Justin Tadlock

      Right now, I do not think it’s possible to disable the line-height setting. I know this was brought up in one of the tickets on the GitHub repo, so I am hoping it goes in.

      Report

  9. Anh Tran

    Gutenberg is getting better and better. I’m really excited to the new way of building themes and websites.

    Report

  10. Scott Talkov

    I’m glad I can change the font size of an H1 heading. Sometimes, the default size doesn’t match the context. Thanks!

    Report

  11. Beate G.

    How can different font-size for mobile view be set?

    Report

  12. Andy

    The number one thing that concerns me about Gutenberg are the things that developers and theme designers can’t control, as you mentioned happening at the moment with line-height. Developers and designers should be able to control any option the user could have in Gutenberg. Line-height is one such thing that should definitely be a global setting which, in many cases, shouldn’t even be available to the user, for the sake of the design. It’s starting to look like half the process of designing a custom site is just going to be hours spent disabling a gazillion blocks and block settings. I’m enjoying the speed of the development and playing with the things that Gutenberg can do, but it’s been, and seems as if it’s going to continue to be, an absolute nightmare making Gutenberg user friendly to many of my clients who constantly tell me that they’re afraid to do anything in it for fear of messing something up. Unless I’m able to hide literally anything they don’t need or shouldn’t be changing, then it’ll be hard for me to get all that excited about new features that override my CSS. I wish I could just export a JSON file or something with all of the registered blocks and their settings that I could just drop into the theme, that would let me turn things on and off easily.

    Report

  13. Per Herngren

    To be creative with basic typography it is necessary, I think, to be able to change line-height, font, font-size, font-color both on a per-block basis and with a Global Styles system.

    Report

  14. Stella Naija

    Yes please, How can different font-size for mobile view be set?

    Report

Comments are closed.

%d bloggers like this: