The person with a vision and a limited budget. That's the sweet spot.
The person we had in mind
You looked at what your organization has — whatever it is, a patched-together WordPress site, a hosted page that nobody really owns, something a volunteer built five years ago and hasn't been touched since — and you thought: we deserve better than this.
That's the thought that brought you here.
You're not trying to fix the old thing. You're ready to build the right thing, from scratch, and build it properly. You have the time and the will for a real project. What you don't have is a budget for an agency, a tolerance for something mediocre, or any interest in handing this off to someone who doesn't understand the organization the way you do.
You want to keep it in-house. You want to understand it. You want to own it — not just maintain it, but genuinely know what it is and why it works the way it does.
This book was written for exactly that person.
What you've probably been told
Someone has probably quoted you a price fir a new website that felt absurd. Or you watched a vendor build something underwhelming for more money than made sense, and you sat there thinking — I could do that. I could do that better, and it would actually reflect what we are.
You've probably also been steered toward the simpler options. The drag-and-drop builders. The hosted platforms. The tools that promise a website by Friday with no technical knowledge required.
And maybe you looked at those and felt, correctly, that they weren't quite right. That they were built for someone with a simpler situation. That the ceiling was too low.
You were right to keep looking.
Why Drupal and why now
Drupal has a reputation for being an enterprise tool — something for large organizations with development teams and infrastructure budgets. That reputation is not entirely wrong. Drupal can do what those organizations need.
But here is what that reputation misses: the same qualities that make Drupal powerful at scale make it exactly right for a small organization that wants to build something serious. The structure. The flexibility. The fact that it doesn't paint you into corners. The fact that what you build today can grow with you without being rebuilt from scratch.
The no-code tools are fast to start and slow to grow. You will hit a ceiling at precisely the moment you need to go further. Drupal has no ceiling you are likely to reach.
"The simplest tool is the one that can do what you actually need — not the one that was easiest to start."
And here is the part nobody mentions: you don't need a team. You need to understand what you're building before you build it. That's it. The rest is patience and curiosity, both of which you clearly have or you wouldn't be here.
What Drupal actually is
Nobody needs a website. They need a way to organize their information and make it available to the people who need it. A website is just how that looks from the outside.
Drupal is not a website builder that happens to have some data features. It is a system for organizing information that happens to have a website attached. That distinction sounds small. It isn't. It's the whole thing.
The vision you have in your head — the staff directory that actually works, the events calendar that connects to the right content, the news section that doesn't look like it was last updated when the organization had a different name — all of that starts with thinking clearly about your information. Drupal rewards that thinking. It was built for it.
Why your situation is actually ideal
You have something the enterprise world envies: a clean start. No legacy system to be compatible with. No seventeen stakeholders pulling in different directions. No committee that needs the new site to look like the old site, only better.
You have a clear picture of what the organization is, what it does, and what it needs to say. You have the freedom to build something that actually fits. And because you're doing it yourself, you'll understand it — which means you can maintain it, extend it, and explain it. That is a better outcome than anything you'd get by writing a check to someone who'll be gone when something needs changing.
Small organizations with serious intentions are exactly what Drupal is for. You just haven't been told that yet.
What this book will and won't do
This is not a manual. The documentation exists, it's good, and this book isn't going to replace it. What it will do is give you the thinking that makes the documentation make sense when you get there.
Every chapter starts with why. The how comes after — because the how only makes sense once you understand what you're trying to accomplish. By the time you finish, you won't know everything about Drupal. But you'll understand how it thinks, and that turns out to be most of the battle.
The only thing you actually need
You don't need a computer science degree. You don't need to know what PHP is. You don't need to have done this before.
You need a clear picture of what your organization is and what it needs to say. You need the willingness to think about your information before you start clicking. And you need a little courage for the moments when something doesn't go the way you expected — which will happen, and will be fine.
You already have the vision. That's the hard part. The rest is here.