If you built Drupal 7 sites in a browser and walked away when Drupal 8 handed you Composer, here is the short version: the browser workflow you liked is intact, and the tooling you disliked is still there.
Both halves of that are true, and most coverage aimed at returning site builders only tells you the first. This page is deliberately short. It answers one question — is it worth another look — and points you at the longer pages for the rest.
What you left, and whether it changed
| The complaint | Where it stands |
|---|---|
| "I have to use Composer now" | Still true for adding and updating code. A managed host can do it for you; nothing in core removes it. |
| "Site building got harder" | Not true. Content types, fields, Views, blocks and taxonomy work the way they did in Drupal 7. |
| "Theming needs a build step" | Twig replaced PHPTemplate, which is a real change, but core themes need no Node.js toolchain. |
| "Layout means Panels and a stack of contrib" | Improved. Layout Builder is stable in core. |
| "My site config lives in the database" | Changed for the better. Configuration exports to YAML and moves through version control. |
| "Updates are a chore" | Still a chore. See below. |
If you are coming back to Drupal on a real project rather than a test site, Drupal services covers what an assessment looks like.
The one to be clear-eyed about
Drupal still has no unattended updates in core. In 11.4.6 the staging API package_manager is marked lifecycle: experimental and hidden: true; the user-facing Automatic Updates module is contributed. If the reason you drifted away was maintenance burden, that specific burden has not lifted, and anyone telling you otherwise has not read the info file.
The genuinely new thing
Two changes are worth your attention as a site builder rather than a developer.
First, recipes. Core ships 28 of them in core/recipes/, and a recipe installs modules and imports configuration in one step — a content type with its fields, view modes and permissions, applied at once. This is a core capability, not something you need a special distribution for.
Second, Drupal CMS, the project's own pre-configured distribution. It is the same core with the decisions already made, aimed squarely at people who want a working site rather than an empty one. What Drupal CMS actually is covers it properly, including what it does not change.
If you still have the Drupal 7 sites
That is a different question and a bigger one, because the content moves but the code does not. The two paths are laid out in what a Drupal 7 to Drupal 11 rebuild actually costs and the Backdrop CMS alternative. Read both before getting a quote; they lead to very different numbers.
Common questions
Can I build a whole site without a command line?
Yes, if someone else handles code updates. A managed host, a retainer, or a colleague — but somebody, because it is not automatic.
Are my Drupal 7 skills still worth anything?
The site-building half, almost entirely. The code half, no: hooks became plugins and services.
Should I start with Drupal CMS or plain core?
Drupal CMS, if you are re-evaluating. It is the fastest way to see the current state of things without configuring anything first.
Where to go next
Install the distribution and spend an hour in it — that will tell you more than any article. If you want a view on whether Drupal fits the work you actually take on, what a Drupal developer does today is the honest picture, and a short message gets you a straight answer about a specific project.
