Gutenberg 0.3.0 Adds Front-End Styles for Core Blocks, Notices Framework, and Text and Image Quick Inserts

Gutenberg development is marching ahead with version 0.3.0 released today. New releases are shipping out on a weekly basis, so testers will get to discover another round of new additions after updating to the latest. The changelog has a full list of the 50 additions and improvements included in this release, but here’s a quick visual tour of a few of the most interesting user-facing features added this week.

Gutenberg developers have added front-end styles for core blocks, which means that content like cover images will now appear the same as they look in the admin in the editor. The demo content in the plugin has also been updated to display a full-width cover image. Below is an example of a standard width cover image on the front-end.

Version 0.3.0 also includes new text and image quick inserts, which appear when hovering over the blank space beneath the post content. This makes it faster to add the types of content that are used most frequently.

This release adds a framework for notices, which provides developers with reusable notices components, showing how to trigger notices and where they will show up. Gutenberg now displays notices on post save, schedule, and update.

Version 0.3.0 adds a new block descriptions component to blocks with inspector controls. Several of the core blocks now display descriptions. These will be especially useful when plugin developers begin adding their own custom blocks, offering users a quick way to see the purpose of the block.

This release adds more placeholder text to various blocks, as “placeholders are key,” according to the newly added design blueprints and principles included in Gutenberg’s documentation:

If your block can have a neutral placeholder state, it should. An image placeholder block shows a button to open the media library, a text placeholder block shows a writing prompt. By embracing placeholders we can predefine editable layouts, so all you have to do is fill out the blanks.

Version 0.3.0 also adds several enhancements that make it easier to edit and customize the image-oriented blocks with more options and settings:

  • Added “edit image” button to image and cover image blocks
  • Added option to visually crop images in galleries for nicer alignment
  • Added option to disable dimming the background in cover images
  • Added option to display date and to configure number of posts in LatestPosts block
  • Added text formatting to CoverImage block
  • Added toggle option for fixed background in CoverImage
  • Added placeholder for all text blocks
  • Added placeholder text for headings, quotes, etc

Active installs for the Gutenberg plugin have nearly doubled since last week and are at more than 900 sites. This is roughly 1% of the goal Matt Mullenweg set for testing on 100,000 sites before replacing the edit screen. The plugin may also be advertised in the dashboard in a future release, possibly 4.8.1, which is slated for the end of July.

7 Comments


  1. Sarah, there is a tiny typo in the beginning of the 3rd paragraph. The actual version is 0.3.0 and not 3.0.

    Report


  2. As a developer of websites for clients, I have a huge concern over the functionality being added here. For blog posters, there’s no doubt that Gutenberg will be a boon, but for the websites that I develop, it will be hugely detrimental to have my clients adding all sorts of layout options to areas of the page that, in order to remain consistent to the design and functionality which I have developed for them, shouldn’t have.

    If the various components of Gutenberg can be managed by me then it won’t be a problem – I’m thinking to have a filter or action that I can use to turn off, for example, the full-width content blocks, or multi-column blocks. Even better would be to disable the whole thing and revert back to the simple text editor. At the moment, I’m not a fan!

    Report


    1. Even better would be to disable the whole thing and revert back to the simple text editor. At the moment, I’m not a fan!

      Agree completely – for my clients and their custom themes I’ve designed and built, having free rein to change the layouts in areas of pages and posts will negate the consistency of design throughout the site.

      Some of my clients have used VC in the past then later regretted it, but others have never touched anything similar to it. Putting that kind of power into their hands to experiment with will give them the ability to quickly make a big mess of their sites. Then they’ll wonder “why it doesn’t look right anymore” and want to know how fast I can fix it for them.

      Report


    2. I have exactly the same feelings about this.

      When at launch “Gutenberg” is not ready for primetime I assume that we’ll see a further rise of page builders.

      I am currently very happy with Elementor. I would not need something like Gutenberg at the moment. The regular “simple” Editor plus something like Elementor (which is optional of course) is perfectly fine and totally enough.

      To have Gutenberg the breakthrough thing, Matt & some others are hoping, would mean it’s superfast like “boom!”, it’s fully visual (on the frontend also!) and it respects the existing plugins. All of this I cannot see at the moment, and cannot imagine how a launch with 5.0 should happen at all (given, that WP 5.0 will be in a few months already…).

      And the last thing is the name, “Gutenberg”. This name stands for the revolution of printing books. I cannot see the WP’s “Gutenberg” be the same thing for WP (yet).

      Sad but true.

      Report


  3. If WordPress doesn’t supply an option to hamstring Gutenberg and keep things as they are… Then somebody else will.

    Report

Comments are closed.