# Please support any theme/component. css+html can be customized

**URL:** <https://meta.discourse.org/t/please-support-any-theme-component-css-html-can-be-customized/340202>\
**Category:** UX\
**Created:** [December 3, 2024, 8:01pm UTC](https://meta.discourse.org/t/please-support-any-theme-component-css-html-can-be-customized/340202 "2024-12-03T20:01:44Z")\
**Posts on this page:** 1\
**Showing post:** 8

<div class="post-metadata">

**Author:** ![Arkshine](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/arkshine/32/298682_2.png) [@Arkshine](https://meta.discourse.org/u/Arkshine)\
**Post date:** [December 4, 2024, 12:40am UTC](https://meta.discourse.org/t/please-support-any-theme-component-css-html-can-be-customized/340202/8 "2024-12-04T00:40:01Z")

</div>

> [@awesomerobot](#):
>
> I guess one possible solution would be to keep the customization layer separate from the remote repository, but that’s essentially what we recommend now (use a theme component for local customization to a remote theme), but maybe with a couple fewer steps.

I would prefer a dedicated CSS-related customization layer in the component settings with a button to enable or disable it. For any HTML-related, it’s best to fork the component, as it would not make sense in a separate layer I believe. It will be easier for a user to manage while reducing unnecessary component bloat. 🤔

---

_[View the full topic](https://meta.discourse.org/t/please-support-any-theme-component-css-html-can-be-customized/340202)._
