# Native theme support

**URL:** https://meta.discourse.org/t/native-theme-support/47494
**Category:** Feature
**Tags:** rfc
**Created:** [July 19, 2016, 6:38am UTC](https://meta.discourse.org/t/native-theme-support/47494 "2016-07-19T06:38:35Z")
**Posts on this page:** 1
**Showing post:** 15

<div class="post-metadata">

### Author: ![erlend\_sh](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/erlend_sh/32/119475_2.png) [@erlend\_sh](https://meta.discourse.org/u/erlend_sh)
#### Post date: [July 31, 2016, 8:06am UTC](https://meta.discourse.org/t/native-theme-support/47494/15 "2016-07-31T08:06:09Z")

</div>

I think proper versioning is just as important for themes as it would be for plugins.

[https://meta.discourse.org/t/compatibility-checks-and-stable-versioning-for-plugins/31523?u=erlend\_sh](https://meta.discourse.org/t/compatibility-checks-and-stable-versioning-for-plugins/31523)

Had any site been using a custom theme when we launched our new vertical sidebar, that update would have almost certainly broken their site. It was already a challenge for sites with basic HTML & CSS customisations. We also have to assume that some forums will be using themes that they themselves did not make, but rather a 3rd party did, as is the case for 99% of WordPress sites. Which means they’re at the mercy of a 3rd party should an update unexpectedly break their site.

---

_[View the full topic](https://meta.discourse.org/t/native-theme-support/47494)._
