Xaver

🚀 Creator of @mailster. // ⓦ WordPress Contributor // 📬 Email Geek // ✨ Expert @codeablehq // 🇦🇹 Austria

⚪️

[Xaver @xaver_]

For over a year, I’ve been building CoverKit.

What started as a small replacement for an abandoned plugin slowly turned into something much bigger: a flexible image creation system for WordPress publishing workflows.

At least in theory. 😄

Now I’m opening early access for the first time.

If you publish with WordPress and creating images is part of your process, CoverKit might be exactly what you’ve been missing.

https://t.co/XYtFpHoJU4

[Xaver @xaver_]

@mark_jansen

[Xaver @xaver_]

I like when my agent automatically update its knowledge when I change certain things throughout the project.

I've switched OpenGraph defaults to 675px and the change is now across code, files and docs 💪

[Remkus de Vries @remkusdevries]

Plugin count is not a performance metric. One plugin might barely participate in a request.

Another might hook early, load assets everywhere, query the database globally, inflate autoload, and trigger background API calls.

Both count as “one plugin.”

The real question is not how many plugins you have. The real question is what work they add, when they add it, and where that work runs.

Learn to diagnose plugin cost properly:
https://t.co/4zDWljSsru

[Xaver @xaver_]

Don’t try this at home, kids!

Having 10.000 plugins running on your WordPress site is not a good idea.

It was just to prove my point why plugin count alone doesn’t matter.

[Hamza (GoTechUG) @GoTechUG]

For the 1st time, I saw a WordPress site with 10,000 plugins and it performed better than one with just 2 plugins.

Turns out plugin count isn't a performance problem as @xaver_ demonstrated at our Salzburg meetup.

Got questions? Ask him @xaver_

[Xaver @xaver_]

I like how my agent keeps track of changes across the whole knowledge base and not just the file I’m editing.

I've just changed the default dimensions of a use case in CoverKit and got the changes in the docs :)

[Xaver @xaver_]

@mikhail_b_ 🙌

[Xaver @xaver_]

@SergeyBiryukov Happy Birthday 🎉

[Xaver @xaver_]

The important part for me isn’t “AI can generate some code now.”

It’s that plugin users can start shaping tools around their own workflow instead of waiting for every edge case to land on a public roadmap.

That feels like a better kind of lock-in: not trapping people, but helping them build something that actually fits.

[Xaver @xaver_]

Good read.

This is exactly why I’m trying to make CoverKit intentionally extensible with AI.

Support and updates still matter, of course. But if someone needs a very specific workflow, they shouldn’t always have to wait for me to build it.

I’d rather help users create their own add-ons and use cases with their IDE/agent of choice:

https://t.co/HZkD6I1UJj

[Casey Burridge @caseyryanb]

If your #WordPress plugin is fully open-source, AI agents can read, extend, and replicate it.

Solution? Move core logic behind a SaaS—make the plugin a connector, not the product.

Seeing more and more companies implementing this model 👀

https://t.co/LnnQAXw2Dz

[Xaver @xaver_]

@pootlepress Some CPT are children of another post type. While I would consider "Newsletters" as a form of content, forms and automations are just that.

Content is also not defined by just saying it it public.

[Xaver @xaver_]

I still see tweets from people I’ve unfollowed on my “for you” page. Shouldn’t it be me to know what’s best for myself? 😅

[Xaver @xaver_]

@MythThrazz only mock. real plugins wouldn’t work. Thanks for the article, this will be useful 🙌

[Xaver @xaver_]

I’m talking about plugin counts and if they matter for your website’s performance next week at the WP Meetup in Salzburg.

Spoiler: not really 😎

[Remkus de Vries @remkusdevries]

@gridpane There is no real argument to limit the number of plugins.

There are a gazillion arguments to limit the amount of code running via plugins.

[Xaver @xaver_]

@MythThrazz No, please share 🙏

I've setup a test site with 10K active plugins, just to proof my point

[Xaver @xaver_]

No, you just know how separation of concerns work.

[Jeremy Koering @jeremykoering]

@MarkJSzymanski If you’re using 30 plugins, you’re bad at making WordPress sites.

[Xaver @xaver_]

https://t.co/Mz65D54ikW

[Maarten ("the wombat guy") @PoeHaH]

Feature request: de-rank plugin on the repo that introduce their own design systems and colors😊

[Xaver @xaver_]

I got decent feedback from many folks at #WCEU for CoverKit.

Anne pointed me to some accessibility issues I should be aware of and I already addressed them.

Sign up to my early access list if you’re are curious:

https://t.co/x0RmIvTOQI

[Anne Bovelett @Bovelett]

@xaver_ @NewYorkerLaura Good point. I'm super stoked about CoverKit, thank you for showing it to me during #WCEU!