It’s no secret that I’m a huge proponent of Gutenberg, the new block editor to be released next month in WordPress 5.0.
Over the weekend, I set up a new, highly interactive demo of one of my latest Gutenberg-inspired projects, CoBlocks. There’s a lot of controversy surrounding Gutenberg, so I wanted to shine a little light on how third party blocks can leverage the new editor and bring some really powerful editing capabilities to WordPress.
Tabor has received quite a lot of updates over the past couple of weeks, mostly surrounding Gutenberg. In fact, over the last month I’ve pushed an update nearly every week! So here’s the latest on what’s new with Tabor.
I’m writing a number of articles outlining the tricks the trade I’m learning while developing Gutenberg-ready WordPress themes. Up next is this guide on supporting Gutenberg’s new alignment features. Woot!
Gutenberg, the soon-to-be block editor for WordPress, has a nifty color palette used throughout many blocks which allow users to set custom colors. While this sort of empowerment is quite useful, I can think of a few reasons why folks would want to limit the styling capabilities of Gutenberg.
Gutenberg, the upcoming block editor for WordPress, has a built-in color palette that lets users stylize content rather easily. While WordPress themes can override them and provide “themed” color palettes, I thought it would be interesting to load a custom color value from the WordPress Customizer within Gutenberg color palettes.
While there is no shortage of articles published about adding general support for a theme’s color palette within the Gutenberg editor, I’m going to focus on the color class changes deployed in Gutenberg 2.8.