Revisiting Gutenberg blocks part 2: More ways to customize blocks

The previous post (Revisiting Gutenberg blocks part 1: Building and Styling the blocks) discussed how to build a block and reviewed both old and new techniques for creating Gutenberg blocks. This post will revisit related areas of block development in more detail. Block variations Some times it may be easier to create additional styles for an existing core element than create your own. Gutenberg calls this block variations. Authors can also choose whether they want to incorporate core blocks. It is highly likely that you will need to customize the block styles to match the core blocks with the theme

Revisiting Gutenberg blocks part 1: Building and Styling the blocks

My dislike of Gutenberg has softened since it was first introduced, mostly because they provided ways to keep the classic editor and they’ve guaranteed support for it through 2022. I’ve written about building Gutenberg blocks: Building Gutenberg Blocks (Part 1), part 2, part 3 and part4, and another series on using Gutenberg as a design system: Gutenberg as a design system (part 1), part 2, and part 3 but I want to revisit block design both in light of new developments in Gutenberg and as a way to build more complex blocks using block patterns and, possibly, full-page designs. Build

Font synthesis in CSS

One of my biggest peeves in the typography side of web development is that browsers try to be too helpful when there is no bold or italics version of a font. The font-synthesis descriptor allows authors to control whether supporting browsers will synthesize boldface, italics, or both when there are no fonts available. The possible values for the descriptor are: none Neither bold nor italic typeface may be synthesized. weight A bold typeface may be synthesized. style An italic typeface may be synthesized. The default value for the descriptor is style weight meaning that both boldface and italics will be

Building a performance test suite

Ever so often you see questions in Quora about Brave, a Chromium-based browser that claims to be faster than stock Chromium and other derivative browsers like Edge, or Opera on Desktop. The last time I saw the performance testing results and methodology was when they first released version 1.0, documented in Brave 1.0 Performance: Methodology and Results with the code used to do the analysis available on Github but I haven’t seen more recent data. The tests were done in older versions of the browsers tested and the Brave Browser Comparison Kit hasn’t been updated for newer versions (not that

Custom Loops in WordPress

When researching how to use Gutenberg Ramp to partially allow Gutenberg on a WordPress site, I decided that I wanted to use a custom post type for the test so I wouldn’t screw up the existing content for my blog. There is a problem with this idea. Custom post types don’t appear in the default loop of a WordPress type so they wouldn’t appear along with regular posts on the blog homepage. Most times, this is what we want. We want to use the custom post types on their own specialized loops. However, in this case, it is not what