Choosing Drupal For A Complex Organisation: What To Check

When several departments share a website, choosing a CMS is not just a design decision. It is a decision about who can change information, who checks it and how the organisation keeps it current.

Drupal can support complex publishing arrangements. That does not make it automatically the best choice for every large organisation.

A more useful assessment starts with the work your team needs to get through.

Map One Real Publishing Journey

Choose a familiar task, such as updating a service description or preparing a public announcement.

Who supplies the information? Who checks the wording? Who can publish it? What happens when the usual approver is away?

Write down the steps before asking for a demonstration. Otherwise, it is easy to be impressed by features that do not address the difficult part of your own process.

Ask the supplier to show your example from draft to publication, including a correction after the page is live.

Give People The Access They Need

Drupal uses roles and permissions to control what users can do. Its user-management guide explains how permissions are grouped into roles.

For your organisation, the question is not simply whether permissions exist. It is whether the proposed setup reflects your responsibilities.

A communications editor may need to update announcements without changing the site’s configuration. A department may need to supply content without being able to publish it.

Ask the team to demonstrate both the allowed action and the action that should be blocked. A diagram of roles is useful, but a working test is more convincing.

Keep Review Separate From Publication

An existing page may need to stay online while its replacement is being checked.

Drupal’s Content Moderation documentation describes keeping a published version available alongside a working draft. Workflows need to be configured to suit the content and the people involved.

In your demonstration, check what a reviewer sees and how they know which version they are approving. Ask how rejected changes are returned to the author.

Also decide who has final authority. Software can support an approval process, but it cannot resolve an organisation’s uncertainty about who should make the decision.

Plan Languages As A Publishing Responsibility

Drupal supports translation of content, configuration and interface text, as its translation guide explains.

That capability does not supply your translated copy or keep every language accurate automatically.

Consider what happens when an English service description changes. Who is told that the Bahasa Malaysia version needs attention? Must both versions be approved together, or can they follow different schedules?

Include this in the brief. A language switcher on the public site is only the visible part of the arrangement.

Be Specific About Shared Information

A group website may repeat an office address, a service description or a policy across several sections.

List which information should be shared and which must remain independently editable. Do not assume that running several websites on a related platform means they all share the same content or approval rules.

Ask the supplier to explain what happens when a shared item changes. Which pages are affected, who can approve it, and how would you correct a mistake?

Use a small real example to uncover assumptions before the project grows.

Include The Ordinary Week After Launch

Request a clear explanation of training, documentation and ongoing care. Who handles routine updates? Which changes require a developer? How will the next team understand any custom work?

Include the cost and responsibility for maintaining the system, not only the initial build. Ask how a new staff member will learn to publish safely after the original project team has moved on.

A complex website should not depend on one person remembering how everything works.

Choose The Setup, Not Just The Platform

Drupal’s value depends on how well it is planned, configured and supported for your organisation.

A useful proposal should connect each significant feature to a real publishing need. If the explanation is mostly a list of technical terms, ask for a demonstration with your own content.

Talk to us about your publishing requirements if you want help turning them into a practical website brief.