# 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:** 2

<div class="post-metadata">

**Author:** ![awesomerobot](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/awesomerobot/32/142900_2.png) [@awesomerobot](https://meta.discourse.org/u/awesomerobot)\
**Post date:** [December 3, 2024, 8:11pm UTC](https://meta.discourse.org/t/please-support-any-theme-component-css-html-can-be-customized/340202/2 "2024-12-03T20:11:38Z")

</div>

Generally we recommend using github or a similar version control system, as this makes it easier to track your code over time.

We previously had a CSS/HTML button on all themes and theme components, but when editing a remote theme, upstream changes in the remote repository would override local customization and it was a very poor experience that made people afraid to update.

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.

---

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