WordPress Paid Out More Than $90,000 in bug bounties in the last 90 days. I could be naive, but my hope is that these security fixes will tamper off over time as the code base is hardened.

This review of the challenges and possible solutions to collaborative editing in WordPress explains why the feature was removed from 7.0 and talks about some experimental solutions.

This is an interesting look at what is behind or contributes to plugin growth. On one level it seems obvious, but many could learn from it.

Bill Erickson ran GPT 5.5 and a number of open source AI models against some WordPress task lists to compare cost and how well they performed. His results pretty much mirrored my experience with Kimi.

This is an analysis of the complete theme directory – all themes from the beginning. Some things we’ve known, for example, that block theme adoption is low, but there are some other insights as well, such as where theme authors are putting their attention now.

There does seem to be the assumption that lots of active installs per theme is the sign of success. However, in a free directory lots of choice also counts.

The results largely align with the TAB survey: Most are 1 person or small teams, decide on the CMS and hosting for their clients, provide additional services for more revenue and find that updates and performance are the biggest time sync.

This is based on the April 2026 dataset from the HTTP Archive. It is reporting the builder used on the home page. There are plenty of interesting tidbits, such as year-on-year stats.

Ahrefs analyzed site data for sites with llms.txt files and found they are rarely every accessed.

fter a few years with no tests, Kevin Ohashi again held his WP hosting tests. Note that these are a pay to participate, opt-in sets of tests.