# Plugins settings list readibility

**URL:** https://meta.discourse.org/t/plugins-settings-list-readibility/146854
**Category:** UX
**Created:** [4 april 2020 om 23:44 UTC](https://meta.discourse.org/t/plugins-settings-list-readibility/146854 "2020-04-04T23:44:43Z")
**Posts on this page:** 1
**Showing post:** 3

<div class="post-metadata">

### Author: ![sam](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/sam/32/102149_2.png) [@sam](https://meta.discourse.org/u/sam)
#### Post date: [6 april 2020 om 07:35 UTC](https://meta.discourse.org/t/plugins-settings-list-readibility/146854/3 "2020-04-06T07:35:29Z")

</div>

There is nothing stopping us (the plugin authors) from properly categorizing stuff as you can see here (these are plugins putting stuff into a dedicated section):

 ![image](https://global.discourse-cdn.com/meta/original/3X/3/0/30916e144418580fa02efddd78feef0b31cebdc7.png)

Trouble is sometimes a plugin only has 1 or 2 settings and giving it a whole section is overkill.

The big thing I think I would like fixed is this mess, when you click settings:

`/plugins?filter=affiliate`

Instead perhaps:

`?filter=plugin:discourse-affiliate`

That way if a plugin sprays itself into multiple groups or omits a keyword in a setting the button will still work.

I guess when plugins register settings core is going to have to keep track on the server which plugin owns which setting.

I am slotting this particular change to our next release, cause it is small and makes a big diff.

---

_[View the full topic](https://meta.discourse.org/t/plugins-settings-list-readibility/146854)._
