This week: the WordPress community, Full Site Editing in practice, offline WordCamps, and much more.
As a WordPress entrepreneur, designer and developer, Rich Tabor is recognized as one of the leaders in WordPress. Before recently joining Extendify as Head of Product, Rich was the Senior Product Manager of WordPress Experience at GoDaddy, and founded multiple WordPress products to include Iceberg, CoBlocks, and ThemeBeans.
I’ve been preparing my slides for WordCamp US 2021, where I plan on diving into the interplay of the upcoming Site Editor, block themes, theme.json, block templates, patterns — the whole lot. You see, WordPress is on the cusp of a wildly innovative effort: Full Site Editing, and I am particularly excited to share it with you.
Full Site Editing (FSE) will absolutely change the landscape of the WordPress experience as we see it today — empowering everyday users to finally build and publish sites with full control.
Learn all about this new effort at Carolina Nymark’s site dedicated to all things FSE:
You can’t talk about Full Site Editing without diving into Block Themes. This new class of WordPress themes powers the Full Site Editing experience by laying the block-based foundation, by which FSE is based on. Block themes also set the base experience for the site, configuring global editor settings, specific block settings, and theme presets through the use of its theme.json file.
André Maneiro does a great job walking through the theme.json spec here:
Speaking of theme.json settings — I wrote a three-part series myself on standardizing how we build this next generation of WordPress block themes.
By standardizing just a few key high-level entries within a WordPress theme’s theme.json file, we can finally create a class of themes that truly are interchangeable. Interchangeable in function, while remaining distinct in style.
Give it a read if you’re thinking of building a block theme:
And last, I really appreciate this write-up by Matias Ventura, the lead architect of Gutenberg, as he dives into high-level thoughts on theme.json, notably with how it shines today — and how the mechanism could be flexed in the near future.
Most notably his thinking on sending the theme style specification to the WordPress.org patterns directory to view patterns with your theme’s styles, is very intriguing.