A few suggestions and ideas for the plugin directory

[wadestriebel]

Good points, it hits a lot of the things I have in my mind but haven’t articulated anywhere so thank you!

@anon66243189

https://www.classicpress.net/for-plugin-developers/#pd-section-promote, should probably link to Plugins | Directory, or at least to https://directory.classicpress.net/plugins (Most information that should be on this page is here ClassicPress Directory Update | ClassicPress)

Agreed, although we should point them to a tutorial on “creating a developer and uploading your first plugin” or similar. Because as mentioned we will be removing the submit plugin page.

@anon66243189

• There should be some sorting here https://directory.classicpress.net/plugins , because right now it seems alphabetically ordered, which is OK, but “by newest”, or perhaps “by developer”, should help find plugins in a more targeted way
• The search on that page seems to query only titles, but I think it should query description as well, at least, because the title of the plugin does not always describe it’s features to the fullest.

Both of these are in progress, we are adding Algolia which will allow for a more robust search than we currently have.

@anon66243189

On single plugin pages, there is a Minimum CP Version information we are not able to fill in on plugin submit (not crucial yet, but later will)

I think this is a bug, we should see if we can get that out in the next release.

@anon66243189

This Plugin repo should be linked directly from the CP Homepage, in a menu “Plugins” (no one will first read a blog post, then navigate to a supposed “developer” profile page, just to ssearch for plugins). This point was one of the major painpoints for all users I tried to move to CP: they could not find any theme or plugin working with CP, unless I linked them to, or explained how the tagging on WP would work)

Agreed, cc @BlueSkyPhoenix

@anon66243189

Finally unless this is already outlined somewhere I’d suggest disclosing transparently the process for plugin „admission“.

We should work on a more robust approach, following up on the discussion from Reporting Vulnerable Plugin. I think we need to draft a policy outlining the approval process. If someone in the community wants to take this on that would be amazing