Not replying to everything discussed here, but when searching for a CP specific theme or plugin, I strongly prefer themes and plugins that are listed at the official CP Directory. Gives me more confidence they are solid and maintained (although this is not always true of course).
In any case, I’m pretty certain that the official platform is the place non-techie users look first.
So it would be great if you try to get some of your plugins listed there! See the docs for more info.
Completely agree, @Guido07111975 !
That’s a very good point, Guido.
I will make an effort to gradually add English language files and documentation to some of the PSOURCE plugins and themes and get them listed in the official ClassicPress Directory.
It may take a few weeks, though, and I won’t necessarily submit all of them. I want to focus on the projects where I feel they are genuinely useful internationally and where I don’t see any major regional limitations.
In the meantime, anyone can also use my PSOURCE Manager, which provides unrestricted access to the repository and handles updates directly.
I’ll keep an eye on the Directory over the next few weeks and take a closer look at what is already available and where PSOURCE could make a useful contribution.
I don’t want to simply add 50+ projects for the sake of numbers. I’d rather identify the projects that can genuinely add something useful to the ClassicPress ecosystem and make those properly accessible and documented for the wider community.
Thanks for pointing me in that direction!
Fully agree!
The docs will give you all the info you need. If not, let us know!
And perhaps we can do this a little differently.
If someone finds a plugin or theme in the PSOURCE repository and thinks:
“We really want this one in the ClassicPress Directory!”
Just let me know.
I can then move it higher up my priority list and work on the English language files, documentation and whatever else is needed to get it ready for the Directory.
With around 54 plugins and themes, I have to prioritize, but I’d much rather prioritize based on what the ClassicPress community actually wants and needs.
So if you see something in the PSOURCE repository that you think would be a valuable addition to the Directory, tell me.
That way we can build this together rather than me guessing which projects are most useful to the community.
And of course, the same applies to feedback.
Bug reports, improvement suggestions, ideas, pull requests and code contributions are always welcome.
If you find something that doesn’t work, tell me.
If you think something could be done better, tell me.
If you have an idea or want to contribute code, even better.
I can’t promise to implement everything, but I will certainly take a serious look at it.
That’s how PSOURCE has evolved for the last ten years, and that’s how I would like it to continue evolving.
Build it. Use it. Improve it. Share it.
I saw you also have an Events plugin. The one at the CP Directory (link) is a very simple one (and its metabox returns an error). If your one is feature rich, this may be a good candidate.
Note: when searching for WP plugins in wp-admin > Plugins > Add new, you can also search on the CP category (tag). This will list WP plugins that are compatible with CP. So besides the CP Directory there’s another (small) source for plugins that 100% work in CP. Mine are listed there as well 
Yes, and this is probably a good moment to explain a little more about what PSOURCE actually is, because from the outside it can probably look like just a collection of WordPress plugins.
PSOURCE is actually intended as an ecosystem for ClassicPress, with native WordPress support.
A lot of the plugins started as solutions I needed myself, but over the years they have evolved into something much more interconnected. Many of the plugins are designed to work together, extend each other’s functionality, or provide additional features when used as a suite.
So some of them may look fairly simple when viewed individually, while they become much more powerful when combined with other PSOURCE components.
I’m also currently working on a new security plugin based on Defender, but with a fundamentally different approach: no subscription, no artificial Free/Pro split, and no crippled version. The goal is a fully functional security solution that people can actually use.
That’s also how I see the PSOURCE ecosystem developing in general: useful, complete tools that can work independently but can also become more powerful when combined.
The reason I haven’t been particularly active in the ClassicPress community until now is actually quite simple: time.
There has been — and still is — a huge amount of work involved in maintaining and modernizing all these projects.
I originally came to ClassicPress because there were plugins and systems I simply couldn’t do without. When their original developers stopped maintaining them, I was faced with a choice: abandon projects that had grown over many years, or learn how to keep them alive myself.
So I learned.
I started fixing things, modernizing old code, removing obsolete dependencies, adapting functionality, extending it, and eventually creating new things myself.
And that has been going on for years.
Every bit of free time I had went into building the foundation for the vision I am talking about now: an active ecosystem where developers can build on existing work instead of constantly starting from zero.
I’m finally at a point where the projects are in a much better state and I have a little more room to look beyond my own installations.
That’s why I’m here now.
I’m not arriving with a finished master plan for ClassicPress.
I’m bringing what I’ve built over the last years and seeing where this journey takes us together.
Maybe some of my projects will be useful to the community. Maybe people will find things they want to improve, extend or completely reinvent.
That’s all fine with me.
I built PSOURCE because I needed these tools. Now I’d like to see what happens when other people can build on them too.
And honestly, I’m quite curious where this journey with you all will lead. 