Skip to header Skip to main navigation Skip to main content Skip to footer

Main navigation

  • Home
  • Drupal Theming
  • Web Designer In Austin
  • Drupal Development Portfolio (opens in new tab)
  • Blog
  • Videos
  • Contact
Web Designer In Austin
Designing Drupal, Defining Distinction

Drupal Site Builder: Building Sites Without Custom Code

Grey textured background behind the Drupal Site Builder page title
Alaa Haddad, professional Drupal developer based in Austin, TX   Drupal Care
  8:14 PM CDT, Wed October 07, 2026
Share

A Drupal site builder turns requirements into a working site using what Drupal already ships — content types, fields, Views, Layout Builder, menus, workflows and permissions — and leaves custom code for the few things configuration cannot express. Done well, the result is a site your own team can change later without calling a developer.

I am Alaa Haddad — in web development since 2005, working in Drupal since 2009, and an author of Drupal modules and themes (drupal.org/u/flashwebcenter). If you need a Drupal site built or rebuilt from configuration, see Drupal development, or tell me about the project.

What a Drupal site builder does

Site building is the layer between design and code. It decides how content is structured, how it is listed, who may edit what, and how pages are assembled — and it does all of that in configuration that can be exported, reviewed and deployed like code.

  • Content model: content types, fields, taxonomy and media, designed around how editors actually work rather than how the old site was built.
  • Listings and search: Views for every list, archive, block and feed, with exposed filters where visitors need them.
  • Page layout: Layout Builder and blocks, so editors can arrange a page without touching a template.
  • Editorial workflow: roles, permissions and content moderation, so drafts, reviews and publishing follow your process.
  • Configuration management: every one of those decisions exported to YAML, so a change is made once, reviewed, and deployed — never clicked twice on two servers.

Site builder, themer, developer or architect?

The four roles overlap, and the cheapest project is the one that uses the right one for each decision.

  • A site builder solves it with configuration. Most requirements on a content site end here.
  • A Drupal themer owns how it looks: Twig templates, CSS, accessibility.
  • A Drupal developer writes the custom module when configuration genuinely cannot express the rule.
  • A Drupal architect makes the few decisions that are expensive to reverse, before any of the above begins.

A useful test: if a requirement can be met by configuration that an editor can later understand, it should not be custom code. Code is a cost you keep paying at every upgrade.

Site building on Drupal 11 and Drupal CMS

Recent Drupal releases made site building faster without making it shallower. Recipes, part of core since Drupal 10.3, package a set of modules and configuration that can be applied to a site in one step. Drupal CMS builds on recipes and adds Project Browser, so common features are a choice rather than a research project. The skill is still knowing which pieces to combine and how to keep the configuration clean enough to upgrade.

If you are coming back to Drupal after some years away, Coming Back to Drupal as a Site Builder: What Changed covers what is different. If you want to build without code on the Solo theme, Build a Drupal Site in Solo With No Code shows where that line sits. And if you are new to it, Is Drupal Hard to Learn? A Realistic First 90 Days sets honest expectations.

How I build a Drupal site

  1. Model the content first. Content types and fields are agreed before any page is designed, because they are the hardest thing to change later.
  2. Build listings and layouts from that model. Views and Layout Builder, configured rather than coded.
  3. Set roles and workflow so the people who edit the site can do their job and nothing more.
  4. Export everything to configuration and deploy it, so the site you approve is the site that goes live.
  5. Hand over a site your team can run, with custom code only where configuration could not do the job.

Common questions

Is site building cheaper than custom development?

Usually, and it stays cheaper: configuration that follows Drupal’s own patterns upgrades with core, while custom code has to be maintained by someone.

Can you work on a site someone else built?

Yes. The first step is reading its configuration to see how it was built, then deciding what to keep, what to simplify and what to move out of code.

Do I need a developer as well?

Only for the requirements configuration cannot meet. Part of a site builder’s job is telling you honestly which ones those are.

Next steps

Read about all my Drupal services, or tell me about your site and what you need it to do.

Drupal Services

Footer menu

  • About
  • Privacy Policy
  • Terms & Conditions
  • Flash Web Center, LLC (opens in new tab)
  • Drupal Care (opens in new tab)
  • Log in
  • Contact

Copyright © 2026 Flash Web Center, LLC | All rights reserved

Developed & Designed by Alaa Haddad