Drupal or WordPress: choosing by content model, not by habit

Most “Drupal vs WordPress” arguments compare the wrong things. Both render pages, both have editors, both have a plugin ecosystem. The decision that actually matters is how structured your content is and how many relationships it has.

Ask what an item of content really is

If the answer is “a page with a title and some rich text”, WordPress is usually faster to build and cheaper to maintain. If the answer involves several entity types that reference each other — a product that references a manufacturer, a specification sheet, a set of stockists and a regional price — then you are describing a relational content model, and that is the work Drupal's Field API and Entity Reference system were designed for.

Signals that point to Drupal

• More than roughly five content types with distinct fields.
• Editorial workflow with real approval stages and revisions.
• Multilingual content where translations diverge per field.
• Granular permissions — not just “editor” and “admin”.
• Listings that need to filter and sort across relationships.

Signals that point to WordPress

• Marketing site, campaign site, or a blog with a shop attached.
• A small team who will maintain it themselves.
• Content that is mostly long-form and flat.
• Speed to launch matters more than structural flexibility.

The cost nobody budgets for

Whichever you pick, the real cost is not the build. It is the next five years of security updates, dependency drift and editor training. A WordPress site with forty plugins is not cheaper than a lean Drupal site — it just moves the cost somewhere less visible.

Pick the platform that matches the shape of the content. Everything else is preference.