As a new ClassicPress developer, I expected ClassicPress-native plugins to be discoverable directly from the Add Plugins screen.
I eventually realised that the ClassicPress Directory Integration plugin needs to be installed separately. I’m on 2.7.3 and discovered a notice pointing users to it, which helps, but would it make sense to ship/enable the directory integration by default so ClassicPress plugins are discoverable without this extra step?
This would make it easier for new users and developers to discover, install, test and contribute to ClassicPress-native plugins. Also curious if FAIR integration is expected into the core anytime soon.
I’m glad I came accross ClassicPress and hope to build on it going forward. Lot’s of opportunity for contributing as well.
This is something we discuss regularly. The problem is that some people don’t like it when they have a plugin installed that they didn’t actively choose (as we found when we did that with the Pepper plugin). But if the consensus moves to your point of view, then we’ll do that. You’re welcome to drum up support for the idea!
And, by the way, welcome to ClassicPress!
1 Like
Yes, having a plugin installed and activated might come as a surprise to some. Just to clarify, (my) intention was to suggest native integration and discovery of ClassicPress’s own directory plugin & themes by default instead of discovering plugins and themes listed in a third-party directory. This feature or integration could go into the core itself instead of being derived via a plugin.
PS: Mods, if required, kindly merge into existing discussion. Happy to join there.
The plugin isn’t ready to be part of core. Putting it into core now would restrict its development cycle to that of core.