/📥 Hello, and greetings from the Central Office!
Each month we like to share a quick look at what happens behind the scenes. Transparency matters to us, so we regularly show the work our team is doing to support customers, improve our plugins, and maintain the systems that power them.
Here is a snapshot of what we accomplished recently.
Behind every plugin update is a large amount of support work.
Over the past month our team focused heavily on helping customers troubleshoot issues, configure plugins correctly, and understand how to use advanced features.
Some highlights include:
• Investigating plugin conflicts and caching issues on customer sites
• Creating demo environments and walkthrough videos to help users set up features faster
• Testing issues across local, staging, and production environments
• Providing configuration guidance for password protection workflows
In several cases we also recommended optimized setups such as using PPWP Pro for sites managing very large password lists.
Helping customers succeed with the plugins remains our highest operational priority.
WordPress's Legal Maze Isn't Decline - It's Infrastructure Consolidation
WordPress isn't dying; it's undergoing forced infrastructure consolidation. While tech commentators declare "early decline," the real story is about who controls the distribution layer when 43% of the web runs on a single CMS.
The Ownership Question No One's Asking
WordPress faces what The Repository Newsletter calls an "event horizon" - not a sunset. The difference matters for creators: sunsets are gradual and predictable. Event horizons represent points of no return where the rules of physics change. The current WP.org vs. WP Engine legal battle isn't about market share erosion. It's about whether open-source infrastructure can remain neutral when commercial interests control the namespace, trademark, and plugin repository.
Platform Risk Hiding in Plain Sight
Creators who built on WordPress assumed they owned their infrastructure. They paid for hosting, controlled their database, and avoided platform dependency. But if the entity controlling WordPress.org can arbitrarily block access to updates and plugins based on commercial disputes, that "ownership" was always conditional. You own the code on your server until you need the ecosystem that makes it functional.
What Infrastructure Consolidation Actually Looks Like
This isn't WordPress losing to Webflow or Squarespace. It's the realization that even self-hosted solutions have centralized chokepoints. The plugin repository. The update mechanism. The trademark that determines what you can call your business. When these consolidate under entities with commercial interests, "open source" becomes "open source with terms and conditions."
The Creator Economy Parallel
Substack creators learned this lesson when the platform changed discovery algorithms. Medium writers learned it during the Partner Program pivots. Now, WordPress site owners are learning that infrastructure ownership has layers, and the critical layers might not be the ones you thought you controlled.
The Real Question
If 43% of the web depends on infrastructure that can change access rules mid-game, what does "owning your platform" actually mean? And what's your contingency when the event horizon arrives?
WordPress.org hosting endorsement negotiations exposed in legal filing, Automattic seeks seal. Automattic's motion to seal reveals WordPress.org operates a formal hosting endorsement program with confidential commercial terms. This confirms WordPress.org functions as a business platform, not just open-source infrastructure-critical context for creators evaluating platform dependency vs. owned infrastructure.
Creator capital markets emerge as an alternative to brand deals and platform payouts. Creators now sell equity stakes, tokenize IP, and offer revenue-share investments through platforms like GigaStar. This shifts creator business models from rented attention (ads, sponsorships) to owned equity, but requires infrastructure to manage investor relations. WordPress sites become investor portals, not just content platforms.
Google redesigns AI Overview links with hover cards showing site context before clicks. New hover pop-ups display site names, favicons, and descriptions, changing publisher traffic calculus from AI search. WordPress sites optimized for these preview cards (clear branding, meta descriptions) may capture more qualified clicks than sites relying on inline citation visibility alone.
Automattic moves to dismiss antitrust claims and remove WooCommerce from WP Engine case. Motion targets monopolization and extortion allegations while seeking to separate WooCommerce entity from litigation. Outcome determines whether WordPress.org's commercial activities face antitrust scrutiny, directly impacting how creators assess platform control and lock-in risks.
Human Made launches WP:26 virtual event featuring WordPress Executive Director Mary Hubbard. March 12 conference includes panel with WordPress VIP, News UK, PMC, and CERN leaders, signaling enterprise focus. Hubbard's appearance marks a rare public engagement from WordPress leadership during ongoing legal disputes. Enterprise adoption patterns shown here preview infrastructure requirements for creator businesses scaling beyond solo operations.
Actors are racing to legally protect their voice, likeness, and signature phrases before AI companies monetize them without permission. WordPress creators face the same challenge: trademark your brand assets, register copyrights on signature content formats, and control licensing terms before platforms or AI scrapers claim derivative rights.
That’s all for this week!
Michael - Operator @WP Folio - now WP Defense Lab. Same Plugins. Different Name.