# Should Discourse make an effort to become the next best "CMS"

**URL:** <https://meta.discourse.org/t/should-discourse-make-an-effort-to-become-the-next-best-cms/353746>\
**Category:** Community Building\
**Created:** [February 22, 2025, 5:23am UTC](https://meta.discourse.org/t/should-discourse-make-an-effort-to-become-the-next-best-cms/353746 "2025-02-22T05:23:23Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![ToddZ](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/toddz/32/328350_2.png) [@ToddZ](https://meta.discourse.org/u/ToddZ)\
**Post date:** [February 22, 2025, 7:10am UTC](https://meta.discourse.org/t/should-discourse-make-an-effort-to-become-the-next-best-cms/353746/3 "2025-02-22T07:10:53Z")

</div>

Interesting ideas… it would seem possible for Discourse to be available preconfigured with certain plugins and theme elements to suit some particular use cases like a news site.

Re. point 3, the self-managed instant install: based on my own experience, the gumption and ability to work through the installation and setup process feels like a minimal prerequisite to self-management. If Discourse hosted unsupported 1-click installs, I imagine sites running out of storage, log files accumulating, upgrades failing, etc. – and unhappy users who weren’t prepared for the responsibilities facing a crashed site vs., I don’t know, an ala carte support menu? I see some staffing challenges and PR pitfalls with that scenario.

I appreciate the open-source nature of Discourse and enjoy self-hosting a small forum, but if I were an organization with a lot at stake and little in-house talent, the cost of fully managed hosting might seem a small price to pay.

---

_[View the full topic](https://meta.discourse.org/t/should-discourse-make-an-effort-to-become-the-next-best-cms/353746)._