# Requesting CSS identifiers for themes, theme components (plugins too?)

**URL:** https://meta.discourse.org/t/requesting-css-identifiers-for-themes-theme-components-plugins-too/392690
**Category:** Feature
**Created:** [January 5, 2026, 10:26am UTC](https://meta.discourse.org/t/requesting-css-identifiers-for-themes-theme-components-plugins-too/392690 "2026-01-05T10:26:42Z")
**Posts on this page:** 1
**Showing post:** 4

<div class="post-metadata">

### Author: ![mcwumbly](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/mcwumbly/32/103861_2.png) [@mcwumbly](https://meta.discourse.org/u/mcwumbly)
#### Post date: [January 11, 2026, 7:54pm UTC](https://meta.discourse.org/t/requesting-css-identifiers-for-themes-theme-components-plugins-too/392690/4 "2026-01-11T19:54:51Z")

</div>

> [@zogstrip](#):
>
> if we make it “easy” for theme authors to customize how their settings page look, are we going to make it harder for people to use those page if they’re all different?

Yeah, I don’t think this is something we want to encourage. @martin has a fair bit of context on this question as it relates to establishing the UI guidelines we came up with for the admin section overall a while back.

In general, we consider the admin section to be something we don’t want to be customized, if I recall correctly.

> [@zogstrip](#):
>
> Should we actually fix that in core instead so that the theme settings page makes better use of the available space?

Yeah, I think treating this topic as #Contribute > UX makes more sense.

@jordan.vidrine I think this has some overlap with your earlier efforts to get things converted to formkit, as well as feedback on formkit itself.

---

_[View the full topic](https://meta.discourse.org/t/requesting-css-identifiers-for-themes-theme-components-plugins-too/392690)._
