# Best Workflow for Maintaining Themes?

**URL:** https://meta.discourse.org/t/best-workflow-for-maintaining-themes/148931
**Category:** Development
**Created:** [April 23, 2020, 2:09am UTC](https://meta.discourse.org/t/best-workflow-for-maintaining-themes/148931 "2020-04-23T02:09:53Z")
**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: [April 23, 2020, 2:24am UTC](https://meta.discourse.org/t/best-workflow-for-maintaining-themes/148931/2 "2020-04-23T02:24:46Z")

</div>

> [@TheDarkWizard](#):
>
> I know in other forum software that doesn’t use Repos or Git concepts, you would be to install a copy of the theme and then install second copy as a child and only edit the child, so that when updates came in, you’d update the parent.

You can essentially do the same thing: build your own theme component and add that as a child to your base theme (sourced from git). Then you can update the git theme as needed without impacting your custom work in the component.

That’s the simplest way, you might be duplicating some CSS but probably not an unmanageable amount.

More on themes and components: [Beginner's guide to using Discourse Themes](https://meta.discourse.org/t/beginners-guide-to-using-discourse-themes/91966)

---

_[View the full topic](https://meta.discourse.org/t/best-workflow-for-maintaining-themes/148931)._