Publishing Platforms with Drupal, Technology That Serves the Editorial Team
Publishers and content organizations face a dual challenge: their platform must make editors productive AND prepare content so it remains visible in a world of AI-generated answers and zero-click searches.
Around 60% of all search queries end without a click on a website (Bain/Dynata, 2025). For publishers, this means: reach alone is no longer enough. Your content must be structured so that AI systems cite it, and readers still come to your platform.
Drupal is the CMS that can do both. And arocom is the agency that has been implementing this in practice since 2012.
Why Drupal is the CMS for publishers
WordPress dominates blogs. Shopify dominates e-commerce. But when it comes to publishing platforms, with daily editorial output, complex workflows, structured content, and high traffic, Drupal is the choice that holds.
Editorial strengths
- Content modeling: articles, galleries, videos, dossiers as separate types
- Workflow engine: draft > review > approval > publication
- Revision tracking: every change traceable
- Scheduled publishing with embargo function
- Multilingual natively (not via plugin)
- Roles and permissions granularly configurable
Technical strengths
- API-first: deliver content to apps, newsletters, social media
- Performance under load (Varnish, CDN, Redis)
- Structured data for SEO/GEO automated
- Interfaces to ad management, analytics, CRM
- Open source: no license costs per editor
- Scales from niche trade portal to major publisher
What a modern publishing platform needs
Revenue models and the technology behind them
The choice of revenue model determines technical requirements. Drupal supports all common models, arocom has implemented them.
Ad-supported
Programmatic advertising, native ads, sponsored content. Drupal integration with Google Ad Manager, adtech stacks, custom ad management. Requires: high performance, viewability tracking, fast load times despite ads.
Paid content
Metered paywalls, freemium models, premium areas. Drupal integration with subscription systems, payment gateways, access control. Requires: granular permissions, conversion tracking, trial access logic.
Lead generation
Trade portals that generate leads for providers. Drupal integration with CRM, marketing automation, form builders. Requires: tracking, nurturing workflows, GDPR-compliant data processing.
Platform model
Community features, user-generated content, marketplace. Drupal integration with user management, ratings, notifications. Requires: scalability, moderation, API integrations.
haustec.de: Publishing platform in practice
haustec.de is the independent trade information portal for professional tradespeople in building and facade technology. The editorial team publishes articles and image galleries daily. arocom has been responsible for the technical platform for years, continuously delivering new features and current standards.
What we built:
What does a publishing platform with Drupal cost?
Across 160+ Drupal projects and several publishing platforms, three size classes have emerged. The figures come from fixed-price quotes between 2022 and 2026 in our order book; your actual number depends on the content model, the migration volume and the integrations.
Compact trade portal
30,000 – 50,000 EUR initial · 8 – 12 weeks time to launch Standard features, 2-3 content types, advertising or simple lead generation, one language, around 10 editors. Examples: a specialist blog for a mid-sized publisher, an association's topic portal.
Multi-portal platform
80,000 – 150,000 EUR initial · 4 – 6 months Multisite with a shared backend, several brands and domains, complex workflows, ad management, API integrations with CRM and newsletter systems. Examples: a publishing house with 5+ trade titles, an industrial holding with brand portals.
Enterprise publishing
150,000 EUR+ initial · 6 – 12 months Headless/decoupled architecture, multilingual, paywall with subscription system, personalization, app integration, dedicated SLAs. Examples: a national trade publisher, an international B2B publisher.
What drives the range: content complexity (5 vs 50 content types), migration volume (1,000 vs 100,000 articles), multiple languages, the adtech stack, workflow depth and reporting requirements. Running costs (hosting, maintenance, updates) are typically 1-2 % of the initial investment per month. The Drupal Future Check settles the scope before any fixed price.
Daily editorial work on a Drupal publishing platform
A technical platform is only as good as the workflow it gives the editorial team. At haustec.de and the Gentner verticals we established the following stages; they serve as a blueprint for many publishing projects.
1. Topic planning
An editorial calendar inside the CMS. Topics are created with status, author, publication date and sources. Conflicts (overlapping topics, missing images, unverified facts) surface before writing starts, not at the proofing stage.
2. Writing and structuring
An inline editor for body text, modular blocks for galleries, data tables, quotes and embeds. Auto-save every 30 seconds. Headlines are checked automatically for length, SEO score and readability. The executive-summary block is a required field for GEO indexing.
3. Review and approval
A workflow engine with configurable stages (copy editing → picture desk → editor-in-chief → approval). Every stage sees the diff against the previous version. Notifications by email or Slack. Queries appear as comments on the paragraph in question, not as an email thread.
4. Publication and distribution
Scheduled publication to the day, embargoes included. Once published, automatically: sitemap update, IndexNow ping to Google and Bing, newsletter item, social-media snippet, RSS entry. One source, five channels.
The decisive point: these four stages are implemented in Drupal as a configurable workflow, not as a hard-coded rule. Your editorial team can change the model at any time without arocom touching code. That is what separates a platform investment from a plugin patchwork.
How arocom delivers publishing projects
Publishing projects are not standard web projects. The editorial operation keeps running in parallel, and a standstill is not acceptable. We split our projects into five phases, with clear handovers and a migration path that runs alongside.
Phase 1, discovery (1 – 2 weeks)
Workshops with the editorial team, marketing and IT. Goal: content model, workflow stages, adtech and newsletter integrations, performance requirements. Output: technical concept, fixed-price quote, migration strategy.
Phase 2, architecture and setup (2 – 4 weeks)
Drupal installation, content types, fields, taxonomies, workflow configuration, theming foundation, hosting setup (staging plus production). First content is tested, editors are invited in.
Phase 3, migration (4 – 8 weeks, in parallel)
Existing content is analyzed, filtered and transferred in a structured way. Old-to-new URL mapping is built, redirects are checked before go-live. Images are migrated with alt text and licence information. This phase runs alongside phase 4.
Phase 5, go-live and hypercare (2 weeks hypercare, then ongoing)
Cutover usually mid-week, performance monitoring 24/7 for the first 14 days. After that the project moves into maintenance mode with fixed response times. We stay your contact for hosting, maintenance and feature increments.
Is Drupal suitable for small publishers?
Yes. Drupal scales up and down. It is equally suited for a trade portal with 5 editors as for a major publisher. License costs are zero (open source), the effort lies in initial development and ongoing maintenance.
What does a publishing platform with Drupal cost?
That depends on scope and complexity. A trade portal with standard features starts at about 30,000-50,000 EUR, complex platforms with paywall, API integrations, and custom workflows are higher. The Drupal Future Check (Audit) from 2,500 EUR clarifies the scope.
Can we migrate from WordPress to Drupal?
Yes. Drupal has a mature migration framework. Content, taxonomies, media, and users can be transferred in a structured way. Migration is part of our development services.
How does Drupal connect with our ad management?
Drupal supports Google Ad Manager, DoubleClick, and other adtech stacks via modules and API. arocom has implemented this integration in multiple publishing projects.
Do our editors need training?
A brief introduction is usually sufficient. Drupal's admin interface (especially with the Gin theme) is intuitive. arocom offers editor training, tailored to your workflows and content types.
How does arocom ensure our platform stays fast?
Through hosting on optimized Linux servers in German data centers, caching (Varnish, Redis), CDN integration, and regular performance monitoring. Hosting and maintenance come as a package at arocom.
What happens with our existing content?
Existing content is analyzed (content inventory), structured, and migrated. During migration, we assess which content should be transferred, revised, or archived.
Does Drupal support newsletter sending?
Drupal integrates with newsletter services like Mailchimp, Sendinblue, or CleverReach via modules and API. Content can be transferred directly from the CMS to newsletters, one source, two channels.
Discuss your publishing project
Our team responds within 4 hours on business days. Whether you want to migrate an existing portal or build a new platform.
Send inquiry, response within 4 hours
arocom Team, +49 711 633 77 960 · info@arocom.de
Trust from 160+ Drupal projects
We listen before we advise
15 minutes. Free. No obligation. Personal.
Currently accepting new projects for Q2 2026