Gutenberg 0.7.0, another weekly update of the Gutenberg Editor was released over the weekend. This time, the changelog had more than 30 improvements along with some addition of features like Opt-In usage tracking.
The last version of Gutenberg plugin, Gutenberg 0.6.0 brought major changes to the way paragraphs are created within text blocks, allowing the blocks to split when pressing enter. However, it inserted a “New Paragraph” placeholder which was distracting the users from staying in the flow of writing.
Gutenberg 0.7.0 hides the placeholders on focus and provides a cleaner experience of starting a new paragraph. Removing the placeholder is a minor improvement that Gutenberg has brought and provided a better experience for long-form writing.
The new release has also introduced theme support for customized color palettes and a shared component, such as cover text and button blocks. It would be easy for theme authors to implement their own color palettes using the code.
Gutenberg 0.7.0 has also added theme support for wide images. This allows some blocks like the image block to define a “wide” or “full” alignment by adding the corresponding classname to the block’s wrapper (alignwide or alignfull).
These addition in the new Gutenberg 0.7.0 version offers theme developers a better picture of where Gutenberg is headed in regards to themes. The plugin’s contributors are slowly adding more customization options so that theme authors can add or override Gutenberg’s styles and provide additional opt-in features to their users.
Theme support for wide images has already been committed to Tammie Lister’s experimental Gutenberg Theme. The project was created to showcase how Gutenberg will interact with WordPress themes and is in its developing phase.
Gutenberg 0.7.0 Added Opt-In Data Collection
Users are now presented with the option to opt into data collection about their usage of the editor. The usage data is anonymous and does not include post content is sent to WordPress.com for the future analysis. James Nylen, a Gutenberg contributor explained how the data tracking works through a post on Sunday.
Nylen said that the Gutenberg plugin contains a mechanism to count how often specific actions occur over time. “If the user has previously clicked “Yes” on this screen, and an event occurs that has an associated bumpStat call in the Gutenberg code, then this event is sent to WordPress.com servers by loading a special ‘pixel’ image,” he added.
The tracking code in Gutenberg will store the ‘group’ and ‘name’ sent with the bumpStat call, along with the time the event was recorded. Nylen said the team would use the data to improve the Gutenberg editor based on usage pattern. The data collection information is currently available only to those with access to WordPress.com servers.
He also shared an example of the data that has been collected from the plugin over the past few days since Gutenberg 0.7.0 was released. The chart below is a preview of the number and types of blocks that users have added to posts while testing the editor.
Nylen said in the pull request for adding the data collection that the approach taken here was similar to Calypso’s event tracking code. He further said, “We can use the data added in this PR to inform various decisions such as default order for blocks and whether some blocks are less suitable for code, and more generally this is a very useful technique to collect user experience data.”
Gutenberg contributors are also considering to make the data collection more modular so that it could be used with other WordPress feature plugins or existing features in the future.
Subscribe here to keep up with the weekly updates of the Gutenberg editor. And if you want to add, share, or ask us anything, please feel free to use the comments section below.
Reference: WP Tavern