Project VoltCMS
Why I Built VoltCMS: A Hybrid CMS Born Out of Frustration, Curiosity, and a Long-Standing Dream
Over the years, I have worked with several Content Management Systems—primarily WordPress, Drupal, and Grav. Out of the three, Drupal and Grav became my go-to tools for different kinds of projects. Each had strengths I genuinely appreciated, yet each left me wishing for a middle ground that didn't demand hours of setup or steep learning curves just to get a simple site looking right.
This is the story of how those experiences—combined with a dream I have carried since the days of Drupal 7—led me to build VoltCMS.
What Drupal and Grav Got Right (and Where I Got Stuck)
I still use Drupal in some of my projects today, and for good reason. When it comes to structuring data and displaying different content dynamically using Views, very few systems come close to its power and flexibility. Once your content architecture is in place, querying and presenting data feels effortless.
The Drupal Roadblock: Getting a proper local environment configured to develop a theme takes time, and the complexity of the theming layer is massive. Running a business and juggling multiple responsibilities meant I couldn't devote weeks to mastering Twig overrides, preprocess hooks, and complex theme registries—leaving me with plain, uninspired designs that didn't do the content justice.
On the other end of the spectrum was Grav. For websites that don't require frequent updates, Grav has been fantastic. It is super fast, flat-file based, and remarkably light on server resources compared to Drupal. Better yet, it comes with clean, ready-to-use themes out of the box, which helped me launch several projects quickly.
Still, whenever I needed to push Grav beyond its default behavior—to build a custom workflow or wire up specific dynamic functionality—I hit a familiar wall. I had to dig through documentation, hunt down plugins, and learn Grav's internal conventions from scratch. That was never the fault of the system itself; it was simply the reality of not having endless hours to invest in learning another framework's ecosystem.
A Seed Planted Back in the Drupal 7 Era
Ever since I first saw Drupal 7 come out years ago, a quiet ambition stayed in the back of my mind: What if I built my own CMS?
I didn't want to reinvent the wheel just for the sake of it. I wanted something tailored to how I actually work—a system where I wouldn't have to fight complex build tools just to write HTML and CSS, and where I wouldn't feel locked into rigid structures when I needed custom logic.
For a long time, building a complete CMS solo felt out of reach given my schedule. Recently, I finally decided to turn those rough notes and architectural ideas into reality. Working alongside Claude—patiently iterating through features, hitting free-tier usage limits, waiting, and picking back up again—the project slowly started taking shape. What began as an experiment eventually came to life as VoltCMS.
Enter VoltCMS: A Practical Hybrid Approach
VoltCMS is a hybrid CMS designed around simplicity, speed, and zero-boilerplate development. Instead of forcing a choice between a heavy database-driven framework and a purely static flat-file generator, it bridges the gap:
Clean Templating
No complex compilation steps or bloated theme engines. Use standard HTML, Bootstrap, and PHP to customize themes in minutes.
Resource-Friendly
Built to run smoothly even on modest shared hosting, keeping page loads fast and server overhead minimal.
Essentials Built In
Clean URL routing, full-text search, media management, CSRF protection, and rate limiting ready out of the box.
Where VoltCMS Stands Today—and Where It's Going
I will be the first to admit: VoltCMS is not perfect. It doesn't have any community plugins or the enterprise maturity of Drupal, and there are still a lot of rough edges to smooth out as I use it on real-world projects.
But for the first time, I have a foundation that speaks my language. My goal with VoltCMS isn't to compete with the giants—it's to speed up my development time so that when a client or a personal project needs a website, I can jump straight into solving the actual problem rather than spending half my time learning or configuring the system itself.
It has been a long journey from admiring Drupal 7 from afar to finally shipping my own CMS. VoltCMS is still evolving, and I'm excited to keep refining it one real project at a time.