# CDCK should develop new default Discourse themes on a regular basis to keep it looking current

**URL:** <https://meta.discourse.org/t/cdck-should-develop-new-default-discourse-themes-on-a-regular-basis-to-keep-it-looking-current/222091>\
**Category:** Feature\
**Created:** [March 27, 2022, 12:31am UTC](https://meta.discourse.org/t/cdck-should-develop-new-default-discourse-themes-on-a-regular-basis-to-keep-it-looking-current/222091 "2022-03-27T00:31:20Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![maiki](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/maiki/32/233950_2.png) [@maiki](https://meta.discourse.org/u/maiki)\
**Post date:** [March 27, 2022, 7:00pm UTC](https://meta.discourse.org/t/cdck-should-develop-new-default-discourse-themes-on-a-regular-basis-to-keep-it-looking-current/222091/4 "2022-03-27T19:00:39Z")

</div>

Regarding the yearly themes in WordPress: the features being shown off are, hmmm… _major_. This has been happening for a couple of years, and will certainly continue into WP 6.0, where the entire theming system is undergoing an overhaul. There are now “Classic” themes and Block themes, which call upon different skill sets to approach customizing.

If we separate that from the new user experience, I hear what you say about folks seeing Discourse as a new, constantly updated _product_ that persuades folks to try it.

I’m just kinda personally traumatized as a WordPress developer on what is happening with the themes, how they are tied to new features, and the pace of rolling them out. I’d like to learn lessons from that project’s approach to new themes/features, and apply them in Discourse. 🙂

---

_[View the full topic](https://meta.discourse.org/t/cdck-should-develop-new-default-discourse-themes-on-a-regular-basis-to-keep-it-looking-current/222091)._
