Drupal Theming: Custom Design Without Core Hacks
Last updated: March 2026 · Reading time: 7 minutes
A theme is more than a design skin. In Drupal, the theme is the presentation layer of your platform: it determines how every piece of content, every field, every block is displayed in the browser. And it does this without touching the business logic or data storage. This is the crucial difference from systems that mix design and logic.
Custom Theme vs. Ready-Made Theme: A Clear Recommendation
Ready-made themes are available for free or at low cost. They cover standard requirements and are built for the broad market. For a simple website, that is sufficient.
For demanding projects, arocom recommends a custom theme. The reason: ready-made themes include code you do not need. Unnecessary CSS classes, unused JavaScript files, generic HTML. This costs performance, hinders accessibility, and makes maintenance costly.
A custom theme contains exactly what your project needs — and nothing beyond. It builds on a base theme (like Drupal Core's Starterkit) and only overrides the templates that need to be customized.
The Three-Layer Architecture: Why It Matters
Drupal cleanly separates three layers from each other:
Data storage. The database stores content, configuration, and user data. The theme has no direct access to it.
Logic. Modules process business logic, access controls, and workflows. The theme does not determine which data is displayed — only how.
Presentation. The theme defines the HTML, CSS, and JavaScript that the browser receives. Twig templates control the markup, CSS controls the visual appearance.
This separation has a concrete advantage: you can change the design without touching the functionality. And you can update modules without breaking the design. Drupal updates and core patches go through without your custom theme breaking.
Theming Best Practices: What arocom Has Learned in 160+ Drupal Projects
Subtheme instead of core hacks. Changes belong in the subtheme, not in core or contrib themes. This makes updates safe and your customizations traceable.
Semantic HTML. Every template produces HTML that conveys the structure of your content to screen readers and AI systems. article, section, nav — instead of div chains.
Think component-based. Buttons, cards, teasers, headers — built as reusable components. This reduces redundancy and simplifies maintenance.
Performance first. Only load the CSS and JavaScript files needed on the current page. Drupal's asset library system makes this possible.
Build in accessibility. ARIA labels, focus management, keyboard navigation — this belongs in the theme, not as an afterthought. Drupal provides the foundations in core.
Does Your Drupal Project Need a Custom Theme?
The Future Check analyzes your existing theme for performance, accessibility, and maintainability. Our team responds within 4 business hours on weekdays.
What does a custom Drupal theme cost?
A custom theme is part of the overall project. The effort depends on the complexity of the design and the number of templates. In arocom projects, theming accounts for approximately 20-30% of the total effort.
Can I change my theme later?
Yes. Thanks to the separation of content and design, you can swap the theme without losing content or functionality. A redesign only affects the presentation layer.
What is Gin and do I need it?
Gin is an admin theme for the Drupal backend. It significantly improves the user interface for editors. arocom deploys Gin by default — it has nothing to do with the frontend theme.
Do I need a developer for Drupal theming?
Yes. Drupal theming requires knowledge of HTML, CSS, Twig, and Drupal architecture. This is not a drag-and-drop system. In return, you get full control over the result.
How does arocom work with design agencies?
In a co-pitch model: the design agency delivers the visual concept, arocom implements it technically as a Drupal theme. On equal footing, not as a subcontractor. The CJD project with 21TORR is the reference model.
Read more
- Drupal Templates — How to control the frontend
- Responsive Design 2026 — Mobile-first is no longer enough
- Drupal development — Concept, architecture, implementation
- Future Check (Audit) — Independent analysis of your installation
Discover a random article
Questions about this topic? We'd love to help.
Drupal Future Check
Checklist: Is your Drupal installation future-proof? 15 checkpoints.
Was this article helpful?