Drupal Development: What I Build and How I Work

Drupal Development: What I Build and How I Work

17 November 2026

I build Drupal sites for a living. By day I work at Hounder, a small agency, building Drupal and custom web apps for universities and public-sector teams. By night I build indie iOS apps. This page is about the day job: what I build, who it is for, and how I work.

If you run a site on Drupal, or you are thinking about moving to it, and you want someone who will tell you the truth about what it needs, keep reading.

What we cover

  • What I build
  • Who it is for
  • How I work
  • What a project looks like
  • What I will not do

What I build

Custom Drupal sites, mostly for organizations that cannot afford a site that breaks, leaks, or locks people out. Universities, public-sector teams, and organizations with real accessibility obligations. The sites are component-based, so editors can build pages without touching code, and the design system stays consistent even as the site grows.

The work spans the full build: content architecture, custom modules where the core does not cover it, migrations from older platforms, and the unglamorous parts that decide whether a site survives contact with real users, like caching, search, forms, and permissions.

I also do the work around the site: accessibility audits, performance fixes, and making a site ready for AI tools to read and cite it properly. That last one is newer, and it matters more every month.

Who it is for

Teams that own a site that has to work for everyone. If your audience includes the public, students, or people using assistive technology, your site is not a brochure. It is infrastructure, and it should be built like it.

It is also for teams stuck on an old version. If you are still on Drupal 10, the clock is real: security support ends December 9, 2026. I wrote up what to do about that here: Drupal 10 End of Life: What to Do Before December 9.

How I work

Accessibility first, not last. WCAG is handled at scaffold time, when it is cheap, not bolted on at the end, when it is expensive. Native CSS before JavaScript. If the platform can do it, we let the platform do it, which keeps pages fast and maintainable.

Plain language, always. Technical terms get a one-line translation beside them. You should never need a developer in the room to understand what your own site does.

Evidence over vibes. Claims get a number, a test result, or a concrete example. If I say a change made a site faster, I can show you the before and after.

What a project looks like

Discovery first: who uses the site, what they need to do, and what is broken today. Then content architecture, then design and build in the open, with staging you can actually click through. Then launch, with a plan for the first month, not just the first day.

After launch, the site gets monitored, not abandoned. Security releases, content fixes, and the small improvements that come from watching real people use it.

What I will not do

I will not sell you a chatbot as a strategy. I will not rebuild a site that only needs a fix. And I will not promise a result I cannot measure. If the honest answer is that your site is fine and the problem is elsewhere, that is the answer you will get.

Final thoughts

A good Drupal site is boring in the best way. It loads fast, it works for everyone, editors can use it without fear, and it does not surprise you at 2 AM. That is what I build.

The short version: accessible, AI-ready Drupal sites for universities and public-sector teams, built the native way, with the truth about what your site needs.

Tags

/blog/2026-11/drupal-development-what-i-build-and-how-i-work austin.amento.dev