# Child themes?

**URL:** https://discourse.roots.io/t/child-themes/11718
**Category:** sage
**Created:** 2018-02-25T08:21:38Z
**Posts:** 3
**Showing post:** 2 of 3

## Post 2 by @MWDelaney — 2018-02-25T13:58:50Z

There’s nothing wrong with the way you’re proposing. You’d want to set up a separate build process for your child theme style overrides and you might end up loading more styles than are strictly necessary.

To resolve that problem for one of my projects I created [sub-themes, selected in Customizer](https://discourse.roots.io/t/sage-and-color-schemes-light-and-dark-version-for-example/10804) and had Sage build whole separate “main” stylesheets per sub-theme. It increases the build time significantly (I’m building 5 “main” stylesheets rather than 1) but it means each site only gets the styles they actually need.

For example I can set Bootstrap’s `$theme-colors` per sub-theme and I don’t have to override anything.

Functionality is a little harder, so for site-specific functions I’ll usually make an mu-plugin and include it in that site’s Bedrock `composer.json` only.

Does that help?

---

_[View the full topic](https://discourse.roots.io/t/child-themes/11718)._