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.
There’s no better time to start exploring how each of our WordPress themes will interface with Gutenberg. So to help folks level-up their themes to support the new WordPress block editor, I built the Block Unit Test WordPress plugin.
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!
As you’ve probably been well aware of, I’ve been living and breathing all things Gutenberg since attending WordCamp US last year. And while I have a few irons in the fire, with a change as profound as the new block editor, there’s not a better time to dive in and continue exploring… cue CoBlocks!
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.
Believe it or not, this year was my first WordCamp Atlanta experience ever. While I have lived in Georgia for a number of years, I’ve never been able to make it. But let me tell you, I sure am glad I made it this year.