Is Drupal 11 Really Drag-and-Drop? Let's Cut Through the Confusion

Written By Ritner Digital

There's a question we keep hearing from marketing directors, content managers, and business owners who are either considering Drupal or trying to make sense of what they're actually getting with a Drupal 11 website: Can I just log in and edit my pages, or do I still need a developer every time I want to move a button?

It's a fair question — and the answer is more nuanced than a simple yes or no. The Drupal community has been loudly promoting drag-and-drop editing capabilities, and that's not wrong. But there's a critical distinction between what content editors can do on a properly built Drupal 11 site and what's still firmly in developer territory. Confusing the two can lead to some expensive misunderstandings.

Let's dig in.

Where the Confusion Comes From

Drupal has always been a powerful CMS, but it has historically carried a reputation for being deeply developer-dependent. Want a new module? Call a developer. Need to update a page layout? Don't touch it. Want to rearrange your homepage? Definitely don't touch it.

That reputation was earned — and in certain areas it still applies today. But Drupal 11, released on August 2, 2024, brought real changes to that story. And the release of Drupal CMS 1.0 on January 15, 2025 pushed the narrative even further. Understanding what both mean — and don't mean — is essential to knowing what you're actually buying into.

The confusion largely comes from three very different questions being bundled under one vague claim:

  1. Can content editors drag and drop things on a page?

  2. Can site builders create new page layouts without writing code?

  3. Can anyone install new modules or make structural changes without a developer?

The answers, in order, are: yes, if the site was built for it — largely yes, with the right tools enabled — and no, not really, and this is where things get complicated.

What Drupal 11 Does Well: The Editorial Experience

Let's start with the good news, because there's genuine progress here.

Layout Builder: The Heart of Visual Editing

Since Drupal 8.5, the core has shipped with the Layout Builder module, and it has matured considerably in Drupal 11. Layout Builder allows content editors and site builders to easily and quickly create visual layouts for content display — including the ability to create custom landing pages with an easy-to-use drag-and-drop interface. Drupal

In plain English: once a developer has properly set up and enabled Layout Builder on your site, a non-technical editor can log in through any browser, navigate to a page, and literally drag content blocks from one place to another. No FTP. No command line. No developer on call.

At a high level, Layout Builder allows users to generate a layout — two columns with a header, for example — and then place a content type's fields and any blocks into that layout. Drupalize.Me The UI also lets editors preview their layouts using real content, toggling between a generic layout screen and one that shows actual entered content.

This is meaningfully different from the Drupal of five years ago, where even a simple content rearrangement could require a developer to modify Twig templates or PHP configuration files.

What Editors Can Actually Do Without a Developer

On a properly configured Drupal 11 site, a non-technical content editor can typically:

  • Log into a browser-based admin interface and edit page content directly

  • Use a WYSIWYG editor to update copy, add images, and format text

  • Drag content blocks to new positions within an established layout

  • Add new page sections and choose from available column arrangements

  • Upload and manage media through Drupal's integrated media library

  • Create new pages using existing content types and block options

  • Preview changes before publishing

With the Layout Builder module, content authors can simply start with an empty page, create the desired layout, and start adding content blocks — containing anything the website has been configured to support, such as text, images, videos, maps, or whatever the site needs. Webdrips

Tools That Push the Experience Even Further

The Drupal module ecosystem has built on top of Layout Builder to extend what's possible without code.

Mercury Editor is a free, stable, downloadable Drupal module that offers simple drag-and-drop editing focused specifically on the needs of non-technical marketers and web editors. Drupal Tools like DXPR Builder take a similar approach, offering a visual builder where marketers with no Drupal experience can create pages directly on-screen.

The Layout Builder+ module provides a WYSIWYG-like page editing experience where the editable page is identical to the published version — drop zones appear on hover, blocks can be duplicated with a click, and sections can be moved by dragging. Drupal

So yes, when people say Drupal 11 has drag-and-drop editing, they're not lying. But there's a catch that matters enormously.

The Catch: Who Actually Sets All This Up?

Here's where the confusion really lives.

All of the powerful visual editing described above requires a developer to build the foundation first. Layout Builder doesn't enable itself. Mercury Editor doesn't configure itself. The content types, the block library, the available layouts, the permissions that let editors make changes without breaking things — none of that happens out of the box on a bare Drupal install.

Think of it this way: a nicely appointed office lets employees rearrange the furniture, hang pictures, and redecorate to their taste. But someone still had to build the office, run the electrical, and install the shelving. Drupal 11's drag-and-drop experience is the same deal. Once a skilled Drupal developer has built the structure correctly, editors can work freely inside it. But that structure requires real expertise to create.

This distinction matters because the sales pitch — "Drupal is drag-and-drop now" — sometimes leads clients to believe they can take on Drupal without ongoing developer relationships. For simple content updates on an already-built site? Absolutely. For structural changes, new functionality, or installing new modules? That's a different story entirely.

The Module Question: Where FTP and Composer Still Live

This is the part that surprises most non-technical decision-makers the most, so let's be direct about it.

In older versions of Drupal (particularly Drupal 7 and early Drupal 8), site administrators could install new modules directly from the browser-based admin interface — upload a ZIP file, click a button, done. That workflow is gone in Drupal 11.

In Drupal 11, the ability to install modules by uploading a ZIP file through the UI has completely disappeared, and Composer — a command-line dependency management tool — is now required to install modules. Drupal

Drupal 11 requires Composer version 2.7.0 or higher, a change made following a Composer security fix released in February 2024. Drupal This is a deliberate architectural decision by the Drupal community — Composer provides better security, cleaner dependency management, and more reliable updates. But it also means that adding new functionality to a Drupal 11 site requires command-line access and developer knowledge.

This has generated real frustration in the community. Users on shared hosting have found that command-line access to run Composer and Drush commands is now more or less required for Drupal, and those without SSH access have had to resort to manually uploading modules and themes to the appropriate directories. Drupal

While Composer simplifies dependency management, some users lack SSH access or prefer a manual installation method — and although Drupal still provides compressed files for direct download, additional modules with complex dependencies are significantly easier to manage with Composer. TheDropTimes

What does this mean practically? If your Drupal 11 site needs a new contact form plugin, an e-commerce integration, an updated SEO module, or virtually any new functionality, you need a developer with server access. This isn't a bug — it's an intentional design decision. But it's one that clients should fully understand before assuming Drupal 11 is a hands-off platform.

Enter Drupal CMS: The Attempt to Bridge the Gap

The Drupal community is well aware of this tension, and the answer they've been building toward is called Drupal CMS— released January 15, 2025, and built on top of the Drupal 11 core.

Drupal CMS is a ready-to-use platform for marketing teams, content creators, and site builders, offering out-of-the-box tools including advanced media management, SEO tools, AI-driven website building, consent management, analytics, search, and automatic updates. Drupal

Drupal CMS combines innovative solutions like Experience Builder, Project Browser, and Recipes to create a consistent, intuitive system for quickly creating and editing content — while significantly lowering the barrier to entry for new users. Droptica

The Project Browser is a significant piece of this: it allows administrators to browse and install modules without manually running Composer commands, effectively restoring something closer to the old module-installation experience through the UI.

The Recipes system is equally interesting. Recipes bundle years of expertise into repeatable, shareable solutions — combining modules, configuration, and default content for common website needs. A simple events website that used to take an experienced developer a day to build can now be created in just a few clicks by non-developers. Dri

The Experience Builder: Coming, But Not Quite Here Yet

The most ambitious piece of the Drupal CMS puzzle is the Experience Builder (XB) — a React-based, no-code visual editor that would let users build and theme pages entirely within the browser.

Experience Builder is a React-based no-code interface that allows users to directly modify the user experience and interface of their websites, with features like drag-and-drop functionality, styling options, and branding tools — without the need for custom code. Specbee

Experience Builder is intended to empower site builders to construct and theme their entire website solely within their browser using basic HTML, CSS, and templating markup, eliminating the need for extensive coding experience and Drupal expertise. Kanopi Studios

However — and this is important — the Experience Builder was not included in the Drupal CMS 1.0 release, and it's best to think of that 1.0 release as a next-generation distribution that is well on its way to meeting the needs of no-code site builders, but not fully there yet. DrupalEasy

A full release of Experience Builder is positioned to make Drupal the leading low-code/no-code enterprise platform, but migration from existing sites using Layout Builder or other solutions is still in the analysis phase — and it may not be possible for all sites. SparkFabrik

In short: the fully no-code Drupal vision is real, it's in active development, and it's genuinely exciting. But it's not finished yet.

So What Does This All Mean for Your Organization?

Let's bring this back to practical ground.

If you're a content editor on an already-built Drupal 11 site: You likely have more power than you think. A well-configured Drupal 11 site with Layout Builder enabled means you can update pages, rearrange content blocks, add new sections, and manage media — all from a browser, with no developer needed for day-to-day tasks.

If you're a marketing manager who wants to launch new campaigns and landing pages quickly: This is increasingly achievable on a properly structured Drupal 11 or Drupal CMS site. With the right content types built and Layout Builder configured, your team can spin up new pages without filing a dev ticket every time.

If you're an IT director or decision-maker evaluating Drupal 11 for your organization: Understand clearly that Drupal 11 is not a "set it and forget it" platform from a developer standpoint. Installing updates, adding new modules, making structural changes to templates, and handling server-level configuration still require Composer, command-line access, and developer expertise. You need a development partner — whether in-house or an agency — who knows what they're doing.

If you're on shared hosting and were hoping to manage a Drupal 11 site solo: This is genuinely difficult now, and the community acknowledges it. Drupal's trajectory is firmly toward enterprise and professional environments. Drupal CMS is making progress in lowering barriers, but if you're a small organization without technical resources, the friction is real.

The Bottom Line

Drupal 11 is not a drag-and-drop website builder the way Squarespace or Wix is. It never claimed to be. But for organizations that invest in a properly built Drupal 11 site with a skilled agency or in-house team, the editorial experience is dramatically better than it used to be — and continues to improve rapidly.

The drag-and-drop capability is real, but it's the result of developer work done upfront. The no-code future being built through Drupal CMS and the Experience Builder is genuinely ambitious and worth watching. The Composer-only module installation is real friction that isn't going away.

The question to ask isn't "Is Drupal 11 drag-and-drop?" The better question is: "Is Drupal 11 the right CMS for what my team actually needs to do?" And the answer to that one requires an honest conversation about your content team's technical fluency, your budget for ongoing development, and how much you value Drupal's enterprise security and scalability over the ease of a simpler platform.

That's a conversation we have every day at Ritner Digital — and we're happy to have it with you.

Ready to Talk Drupal?

Whether you're evaluating Drupal 11 for a new project, trying to understand what your current Drupal site is and isn't capable of, or exploring Drupal CMS for your organization, the team at Ritner Digital can cut through the noise and give you a straight answer.

Contact Ritner Digital today to schedule a free discovery call. We'll assess your needs, explain your options clearly, and tell you honestly whether Drupal is the right fit — or whether something else serves you better.

No jargon. No upselling. Just clarity.

Sources:

Frequently Asked Questions

Can I edit my Drupal 11 website without a developer?

For day-to-day content updates — yes, absolutely. On a properly built Drupal 11 site, content editors can log in through a browser and update text, swap out images, add new pages, and manage media without touching any code. What you can't do without a developer is make structural changes: installing new modules, changing how content types are configured, modifying templates, or anything that requires server access.

Is Drupal 11 actually drag-and-drop?

Yes and no. Drupal 11 includes a core module called Layout Builder that provides a genuine drag-and-drop interface for arranging content blocks on a page. But it doesn't work that way automatically — a developer has to build and configure the site so that Layout Builder is enabled and the right permissions are in place. Once that foundation is set, non-technical editors can drag and drop freely. The interface itself isn't the hard part; the setup underneath it is.

Do I still need FTP to manage a Drupal 11 site?

For content editing, no. For installing or updating modules and themes, effectively yes — or something more advanced than FTP. Drupal 11 removed the ability to upload modules through the browser interface and now requires Composer, a command-line dependency management tool, to install and manage extensions. This means adding new functionality to your site requires either server SSH access or a developer who has it.

What is Composer and why does Drupal 11 require it?

Composer is a command-line tool that manages PHP dependencies — essentially, it tracks all the software packages your Drupal site relies on and makes sure they're compatible with each other. Drupal 11 made Composer the required method for installing and updating modules because it's significantly more secure and reliable than the old ZIP-upload approach. The downside is that it requires command-line access, which puts it firmly outside the reach of non-technical users.

What happened to the "Add Module" button in Drupal 11?

It was intentionally removed. In previous versions of Drupal, administrators could upload a module ZIP file directly through the admin interface. That feature is gone in Drupal 11 as part of the shift to Composer-based dependency management. If you're on a shared hosting environment without SSH access, this creates real friction — and it's a genuine pain point the community is actively discussing.

What is Drupal CMS and how is it different from Drupal 11?

Drupal CMS, released January 15, 2025, is a ready-to-use product built on top of the Drupal 11 core. Think of Drupal 11 as the engine and Drupal CMS as a fully assembled vehicle designed for marketing teams, content creators, and non-technical site builders. It comes pre-loaded with tools like SEO management, media handling, AI-assisted site building, automatic updates, and a Project Browser that simplifies module management. It's Drupal's answer to the "too complicated for non-developers" criticism.

What is the Drupal Experience Builder?

The Experience Builder (XB) is an in-development, React-based visual editor that will allow users to build and theme entire pages directly in their browser — no code required. It's the most ambitious piece of Drupal's no-code future and has generated significant excitement in the community. However, it was not included in the Drupal CMS 1.0 release and is still in active development. A full release is expected to be the centerpiece of Drupal CMS 2.0.

Can I use Drupal 11 on shared hosting?

Technically yes, but it's increasingly difficult. The shift to Composer-only module management means you really need SSH access and a command-line environment to work with Drupal 11 properly. Many shared hosting environments don't provide this, which creates real limitations. If you're on shared hosting without technical support, Drupal 11 is likely not the right fit — and alternatives worth exploring include Drupal CMS with managed hosting, or a different CMS platform altogether.

How is Drupal 11 different from WordPress when it comes to editing?

WordPress has long had the edge on out-of-the-box simplicity. Its Gutenberg block editor provides drag-and-drop page building with minimal setup, and plugin installation can still be done through the browser interface on most hosting plans. Drupal 11's editorial experience, once properly configured, is arguably more powerful and more structured — which matters for large organizations managing complex content. But Drupal requires more upfront investment to reach that point, and ongoing maintenance still demands more technical involvement than a typical WordPress setup.

What should I look for when hiring a Drupal agency to make sure my team can actually edit the site?

Ask specifically whether they will configure Layout Builder for your content types, what training they provide for editors after launch, and whether the site will be built so your team can make common changes without filing a development ticket. A good Drupal agency builds for editorial independence — they set up the structure so your team can work freely within it. If an agency can't clearly answer how your content editors will manage the site day-to-day, that's a red flag.

Is Drupal 11 the right CMS for my organization?

It depends on your situation. Drupal 11 is an excellent choice for mid-to-large organizations that need enterprise-grade security, complex content architecture, multilingual support, or highly customized digital experiences — and who have either an in-house development team or a reliable agency partner. It's a harder sell for small organizations with limited technical resources who just need a simple website they can manage themselves. If you're unsure, that's exactly the kind of conversation Ritner Digital has every day — reach out and we'll give you a straight answer.

Ritner Digital
Previous

Our Website Looks Fine — So Why Isn't It Generating Any Leads?
Next

Genuine by Nature: The Biggest Brands Born in Maine and What the Pine Tree State Is Actually Buying