Drupal is a safe platform bet for a site you expect to run for years, and the reasons are checkable rather than promotional.
What follows is the short version, and then where each part of it is answered in detail.
The short version
Drupal's direction over recent releases has been to keep the architecture that makes it worth choosing while lowering the cost of starting. Two things in core 11.4.6 show that concretely rather than aspirationally:
- Recipes. 28 of them ship in
core/recipes/, with the API inDrupal\Core\Recipe. A recipe installs modules and imports configuration in one operation, so a content type arrives complete rather than assembled by hand. - Layout Builder, stable in core. Editors compose pages without a developer.
And one thing that has not changed, which matters more than either: there are still no unattended updates in core. package_manager carries lifecycle: experimental and hidden: true in its own info file, and the user-facing Automatic Updates module is contributed. Anyone describing Drupal's future without saying that is selling something.
If the question behind the question is whether to commit a budget to Drupal, a Drupal architect is who you want on that call.
Where the actual answers are
- What Drupal CMS is and is not: the distribution explained.
- Whether to choose Drupal at all: Drupal against WordPress.
- What a move off Drupal 7 costs: rebuild, not upgrade.
- Who governs the project: nobody owns Drupal.
Common questions
Is Drupal still being actively developed?
Yes. Core 11.4.6 is a maintained release with a published release cycle, and Drupal 12 is in progress with breaking changes announced as deprecations first.
Should I wait for the next version before starting a project?
No. Build on the current supported release. Since Drupal 8, major version moves have been incremental for a maintained site, so waiting buys nothing and costs you the months.
What to do instead of reading this page
If you came here wondering whether Drupal is a safe bet for a project you are planning, the useful next step is not another article about the ecosystem — it is a look at your actual requirements. A Drupal architect does that, and a short description of what you are building gets you a straight answer about whether Drupal is the right tool.
