Field notes from the WordPress ecosystem
WordPress runs a large share of production sites, and the ecosystem around it keeps producing material worth tracking. The following picks cover content modeling, block-based design, local development, headless front ends, performance governance, and the new theming file formats.
Content modeling and the block editor
Iain Poulson's guide to Advanced Custom Fields treats ACF as the piece that turns WordPress into a real CMS when precise control over data modeling matters. The block editor's custom block support doesn't diminish ACF's value; it arguably increases it, and the article serves as a solid overview of both custom fields and ACF blocks.
Mel Choyce's "Make Unique Designs by Combining Blocks" makes the case that the block editor can produce genuinely designed pages. The slides are worth a look, but the demonstration lives in the video: from roughly 13:00 onward, Choyce walks through pages assembled in the block editor with no additional plugins, relying on Columns, Spacers, and Cover blocks.
Justin Tadlock's writeup on the Query Loop block examines one of WordPress 5.8's most powerful features and a central piece of full site editing. Without a template file to run a WP_Query, the Query Block becomes the place to do it, combining query configuration with visual design applied to the results — a natural surface for shipping patterns.
Tooling and theming
WP Engine's Local, maintained by Flywheel, is now free for all users, including the features that previously sat behind the paid Pro tier. For anyone doing local WordPress work, the tool has become hard to do without; the one-click admin login alone keeps local site credentials out of a password manager.
Michelle Barker's post on simpler block spacing covers the HTML classes the block editor emits and the deeply nested selectors theme and admin styles must now target, showing how :is() and :where() consolidate them.
Ellen Bauer explains theme.json, the new theme file that will hold substantial styling control and matters most to sites pursuing full site editing. Eric Karkovack has a separate introduction to the same subject, and Annie McCarthy collected answers from the third round of FSE questions raised by community members.
Headless and performance
WP Engine's Faust is a framework for building front-end applications for headless WordPress sites, built on Next.js. Its stated goal is reducing the friction of headless work — data fetching, authentication, previews, and SSR/SSG — while remaining pleasant for developers and publishers alike.
Ari Stathopoulos's proposal for a dedicated performance team argues that WordPress is falling behind platforms such as Wix, Shopify, and Squarespace, which are on average faster and investing in core performance as a marketed feature. A long-term team is a sensible response, though a difficult one: themes and plugins, outside WordPress's direct control, have the greatest influence on performance.
Script and style management
Mark Jaquith's Encute is a plugin for fluent management of scripts and styles, a successor in spirit to MinQueue, which now appears dead. The appeal of MinQueue was its visual component: a listing of every script and style enqueued on a given page, which made it possible to disable unwanted plugin assets or re-load them manually for concatenation — a concern that HTTP/2 has made less pressing.
The #1 tool I use to save links to review later is Notion Web Clipper.
Links go into one large table in Notion, to be read and tagged later: RSS as the firehose, Notion for the good finds, WordPress for the best of them.



