-
-
Notifications
You must be signed in to change notification settings - Fork 194
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Grouping of plugin types #2324
Comments
Cool idea @jgmac1106. It would be nice to allow plugins to declare a category for themselves, from a list of recommended categories, or to define an alternate category. The default could be "Other" or something. |
+1 to this. Over time this would also help third-party plugins be discovered and more easily installed. |
Related, it might even be nice to have a plugin directory integrated on this page... Nextcloud has such a thing, and I find it to be very useful! |
I actually changed the word choose and add a few times. Worried about cluttering the UI which is the goal but also hate that apple chooses my podcast categories for me, other might be best solution |
+1 to Greg's original suggestion and to cleverdevil's addition of some sort of directory accessible from the page. |
Possibly related, but not really. If I had a Wishlist I'd like to look at some sort of dependancy tree based boot process for plugins. This will hopefully mitigate some of the problems we had with elgg related to multiple template overrides when building applications using the framework. |
Currently the plugin types match the user base fine.
However grouping plugins by category and allowing plugin creators to choose a category maybe more user friendly then alphabetical order:
Thinking off top of my head :
Basic (default on)
Controlling Privacy
Community
Syndication
Quantified Self (collapsed menu)
Advanced (collapsed menu keep IndieWeb building blocks default on)
The text was updated successfully, but these errors were encountered: