# Config as code options for Discourse?

**URL:** https://meta.discourse.org/t/config-as-code-options-for-discourse/279036
**Category:** Feature
**Tags:** migrations-tooling
**Created:** [September 14, 2023, 5:05pm UTC](https://meta.discourse.org/t/config-as-code-options-for-discourse/279036 "2023-09-14T17:05:31Z")
**Posts on this page:** 1
**Showing post:** 10

<div class="post-metadata">

### Author: ![merefield](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/merefield/32/176214_2.png) [@merefield](https://meta.discourse.org/u/merefield)
#### Post date: [July 17, 2025, 2:11pm UTC](https://meta.discourse.org/t/config-as-code-options-for-discourse/279036/10 "2025-07-17T14:11:37Z")

</div>

Just to point out that it is clear that it is already possible to manage content in source control, take a look at this topic, it’s maintained on GitHub:

> [@Controlling site settings with themes](https://meta.discourse.org/t/controlling-site-settings-with-themes/374376):
>
> Themeable site settings allow a theme (not components) to override a small subset of core site settings, which generally control parts of the UI and other minor functionality. This allows themes to have a greater control over the full site experience. heavy_plus_sign Adding themeable site settings All themeable site settings are defined in the core config/site\_settings.yml file. Any setting with themeable: true will be available to themes. To override the default site setting value when the …

at the bottom:

 ![image](https://global.discourse-cdn.com/meta/original/4X/9/5/5/955abee859bc52566953e1b5dccb7e132ab5fc4e.png)

though I’m not sure if this functionality has yet been released or announced (or if that’s intended)

---

_[View the full topic](https://meta.discourse.org/t/config-as-code-options-for-discourse/279036)._