On this website, I present all the open source plugins for WordPress that I have published. I am aware that this is a large number - and also a challenge, as each plugin should also have the same quality in terms of its functions, security and sustainability. I will briefly describe here how I ensure this sustainability.<\/p>\n\n\n\n
\nEverything has to have a reason, and you can find it.<\/p>\n<\/blockquote>\n\n\n\n
That's why I often take a very close look at how something works before I release it to users. This sounds very time-consuming, but in my opinion it leads to enormous stability of the plugins, which is also reflected in very few support requests for the plugins.<\/p>\n\n\n\n
At the same time, I've also learned a lot about the WordPress core and countless other plugins - how things work and how they shouldn't be done.<\/p>\n\n\n\n
Code quality<\/h2>\n\n\n\n
So that I can still understand my own code even years later, I comment very diligently. I have gotten into the habit of commenting almost every line, mostly in US-American English. There are files that consist of 2\/3 comments only - but that is quality for me. A chunk of code thrown down without any human sentence, as you unfortunately see in many other plugins, takes more time to be understood.<\/p>\n\n\n\n
Use of AI<\/h2>\n\n\n\n
I use the PHPStorm IDE for development and the code autocompletion function it contains, as well as the AI, which is also included, to optimize code from time to time. I also use Claude or Copilot from time to time to solve tricky things more quickly. However, I never let the AI write my code. If I do, I copy part of the code it suggests, adapt it and comment on it. Or I talk to the AI like a human colleague to find a solution without adopting what the AI suggests 1:1.<\/p>\n\n\n\n
Security<\/h2>\n\n\n\n
There are a lot of things you should pay attention to when developing a website. Security is a very high priority for me. Unfortunately, I come across far too many hacked websites in my support in the WordPress forums and also in my professional environment.<\/p>\n\n\n\n
For this reason, every function that I add to my plugins is also considered holistically: its structure, its effect and its availability, both while you are logged in and as a visitor without login and also all interfaces that WordPress still offers (REST API, WP CLI ..).<\/p>\n\n\n\n
Tests before each release<\/h2>\n\n\n\n
A new version of each plugin is only released if it passes the following tests successfully and without exception:<\/p>\n\n\n\n
\n
- Comply with WordPress coding standards by checking with their composer Package<\/a>.<\/li>\n\n\n\n
- Fulfillment of the tests of the WordPress Plugin Check Action<\/a> (corresponds to the check by the WordPress plugin team for each new upload in the repository).<\/li>\n\n\n\n
- Completion of a scan with PHPStan with regard to possible bugs at level 8 out of 10 (unfortunately, WordPress as of 2026 does not yet go higher within a reasonable range).<\/li>\n<\/ul>\n\n\n\n
Only a few plugins must also fulfill the following requirements:<\/p>\n\n\n\n
\n
- A series of individual PHPPHP<\/span> PHP is a scripting language with a syntax based on C and Perl, which is mainly used to create dynamic websites or web applications.\r\rhttps:\/\/de.wikipedia.org\/wiki\/PHP<\/a><\/span><\/span><\/span> Unit tests, which test specific sequences of functions within the plugins that must be fulfilled in every case.<\/li>\n\n\n\n
- A test with the composercomposer<\/span> application-oriented package manager for PHP<\/span><\/span><\/span> Package from PHPCompatibility <\/a>with WordPress specifics.<\/li>\n<\/ul>\n\n\n\n
The path to a release<\/h2>\n\n\n\n