Drupal is not hard to learn — it is hard to learn all at once, and almost everybody who bounces off it does so because they tried to.
There is a real order to this. Site building through the browser, developer tooling, and PHP module work are three separate skill sets, and you can be productive at the first without touching the other two for months. Below is the order I would give someone starting today, plus the parts that are genuinely a wall and the parts that only look like one.
Three skill sets, not one
| Level | You learn | Command line needed? |
|---|---|---|
| Site builder | Content types, fields, Views, blocks, menus, taxonomy, Layout Builder, permissions | No |
| Themer | Twig, the render pipeline, libraries, preprocess functions, sub-theming | Occasionally |
| Module developer | Services, plugins, the entity API, dependency injection, configuration schema | Yes |
The single most useful thing to know when you start: the first row has barely changed since Drupal 7. Content types, fields, Views and blocks work the way they always did. If you built Drupal 7 sites, that knowledge is intact and you are much further along than you think.
Where the wall actually is
It is not the admin interface. It is the gap between "I configured a site in my browser" and "I can deploy that configuration to production", and it has three parts.
Composer
Modern Drupal is a Composer project. You do not download a module as a zip and unpack it into a folder any more; you declare it as a dependency and Composer resolves the tree. Learning the six commands you need takes an afternoon. Understanding why a version constraint conflicts takes longer, and that is the part that feels like a wall.
Configuration management
Site structure lives in YAML files, exported to the directory named by $settings['config_sync_directory'], and moves between environments through version control. Drupal 7 had no equivalent — the Features module existed precisely because core could not do this. It is genuinely better, and it is genuinely a new concept to absorb.
Updates are not automatic, and this is the honest bit
You will read that Drupal has automatic updates. It does not, and it is worth being precise because the wrong expectation here becomes an unpatched site.
In core 11.4.6, package_manager — the API that stages Composer operations in a sandbox before applying them — carries lifecycle: experimental and hidden: true in its own info file, so it does not even appear on the module list. There is no automatic_updates directory in core. The Update Status module tells you a release exists; applying it is a human job, and the user-facing Automatic Updates module is contributed.
So somebody has to own patching. Either that is you with Composer, or a managed host, or a maintenance retainer. Decide which before you launch, not after the first advisory.
What you can safely ignore at the start
Half the intimidation comes from concepts you do not need yet:
- Symfony. You will never touch it as a site builder, and rarely as a themer. It is an implementation detail until you are writing services.
- Dependency injection, plugins, event subscribers. Module-developer vocabulary. Skip entirely until you are writing a module.
- Headless and JSON:API. In core and excellent, and irrelevant unless something else is consuming your content.
- Custom entity types. Nodes, taxonomy terms and content blocks cover the overwhelming majority of sites.
Being able to name what you are not learning is half of not being overwhelmed by it.
A realistic first ninety days
- Weeks 1–2. Install locally with DDEV, or use a managed host's one-click install. Build a site with three content types and the fields they need. Do not touch a command line beyond the install.
- Weeks 3–4. Learn Views properly. It is the single highest-leverage skill in Drupal and it is entirely browser-based.
- Weeks 5–8. Learn Composer for adding and updating modules, and get one site into git with configuration exported.
- Weeks 9–12. Pick a direction. Theming means Twig and the render pipeline. Back end means services and plugins. Doing both at once is how the ninety days becomes a year.
Somewhere around week five, read how configuration and deployment actually work on a Drupal site — it is the concept that makes everything after it make sense. If you are hiring rather than learning, what a Drupal developer actually does is the more useful page.
Requirements you should know before you start
Read from core/lib/Drupal.php in 11.4.6: MINIMUM_PHP is 8.3.0, RECOMMENDED_PHP is 8.4, and MINIMUM_PHP_MEMORY_LIMIT is 64M. Cheap shared hosting that caps you below the PHP floor is the most common reason a first install fails, and the error message rarely says so plainly.
Common questions
Do I need to know PHP to use Drupal?
No. A site builder can deliver a complete, sophisticated site without writing a line of it. You need PHP to write modules, which is a different job.
Is Drupal harder than WordPress?
To start, yes. To do something complicated, no — the complexity you hit early in Drupal is complexity you hit later, and worse, in a WordPress site with fifteen plugins.
My Drupal 7 skills — are they wasted?
The site-building half transfers almost completely. The code half does not: hooks became plugins and services, and PHPTemplate became Twig. Budget the retraining for the code, not the configuration.
Can I avoid the command line entirely?
For building, yes. For maintaining, only by paying someone or a managed host to do it for you. That is a legitimate choice, but it is a choice, not an absence of one.
How long until I am employable?
That depends on which of the three skill sets and on your existing background, and anyone who gives you a number without asking is guessing. What is true is that the three ladders are separate and you can start earning at the bottom of one.
Where to go next
If you are choosing a direction, the two paths are laid out in the Drupal themer route and the Drupal developer route. If what you actually need is a working site rather than a new skill, that is a different question and a much shorter one — say what you are trying to build and I will tell you whether learning Drupal is the efficient way to get there.