Copy of I Built a Plugin with AI – Now I know what it Can’t do

Hi friends! 👋🏼
This week’s post is a tiny code tweak I’m using on my own site: it takes the “Additional CSS” you add in the WordPress Customizer and moves it into a separate stylesheet. Why? Performance. Inline styles load every time and don’t get cached. By offloading them into their own file, you get cleaner markup, faster pages, and better cacheability—without messing with child themes or theme files.
On the podcast side—last week’s WP Product Talk with Prakhar Shrivastava was a real standout. He runs a Shopify app called Foxsell and brought a refreshingly different take on growth, ecosystem moats, and platform friction. It hit home for me for a lot of reasons. Worth a listen if you’re building in any kind of product marketplace.
And quick update on TLDRWP: I’ve had a bunch of great feedback since last week’s post about building with AI. I’m now running Plausible event tracking on the TLDR button across my site, and the engagement numbers are fascinating. Time on page, scroll depth—it’s giving me a whole new lens on what people are actually doing with the content. Might write a follow-up on this soon. I’m even considering bringing TLDRWP to the WPPT site next.
As always: hit reply and let me know what you think. I read and respond to every message.
~ Matt
Get Caught Up
If you missed any previous article, here’s the easiest way to catch up.
Simple, human-first ways to write marketing emails people actually engage with.
A 100% free, flexible, easy way to have a link-in-bio page powered by Github Pages.