Tooling Overload Now
Canvas, Tailwind, DaisyUI, CVA, modern component patterns—each one is powerful on its own. Together, they're a lot to absorb.
The problem isn't the technology—it's the lack of a cohesive way to learn it.
Canvas, Tailwind, DaisyUI, CVA, modern component patterns—each one is powerful on its own. Together, they're a lot to absorb.
Best practices are buried on Drupal.org and the Issue queue. No single source shows how it all fits together.
You shouldn't have to guess at architectural decisions and hope they scale. Why isn't there a better way?
Now you get the shortcut. Pablo doesn't just give you code to copy. It gives you patterns to master.
It's a complete, documented foundation built to teach you modern Drupal theming while you work.
Not just what it does—but how it's built and why those decisions were made. Canvas integration, Tailwind conventions, DaisyUI patterns, CVA variants—it's all there, explained in context.
SDCs, Code components, patterns—you'll see real examples of each, understand when to use them, and learn how they work together in a production-ready theme.
Staring at new tooling. Wishing someone had just shown us how it all connects. That frustration is exactly why Pablo exists.
A clear path from installation to mastery.
Start with the big picture. Learn how Pablo integrates Canvas, Tailwind, and DaisyUI into a cohesive system. Understand the component architecture and see how each piece serves a purpose. Every decision is documented—no black boxes.
Class Variance Authority (CVA) is how Pablo handles component flexibility. Learn to create variants that are type-safe, maintainable, and easy to extend. See exactly how it's implemented across Pablo's component library.
Dive into real examples. SDCs (Single Directory Components) for encapsulated, reusable pieces. Code components for dynamic logic. Patterns for layout and composition. Each type is demonstrated with working code and clear explanations of when and why to use it.
Stop writing utility class soup. DaisyUI's semantic class names—btn, card, badge—are descriptive, cleaner, and faster than raw Tailwind. See how Pablo leverages DaisyUI for rapid development without sacrificing customization.
The fastest way to understand Pablo is to use it.
You've read about the architecture. You've seen the principles. Now experience how it actually works. Demo Pablo and explore the components firsthand. See how Canvas integration feels. Inspect the Tailwind and DaisyUI implementation.
Every project without a solid starting point pays a tax.
You could start from scratch. Many developers do.
But consider what that costs:
Tools with infinite options and zero constraints. Every project becomes a series of micro-decisions about architecture, conventions, and patterns—decisions you'll make differently each time.
Without a documented foundation, component structures drift. What worked on the last project doesn't quite fit the next one. Technical debt accumulates before you've written a single custom feature.
Hours spent on boilerplate. Days spent researching best practices. Weeks spent learning by trial and error—piecing together blog posts, documentation fragments, and insights from the issue queues on Drupal.org.
When the foundation is shaky, everything built on top takes longer. You ship later. You ship with less confidence. You spend more time maintaining and less time building.
This is what building with confidence looks like.
Picture your next Drupal project.
You start with Pablo
The foundation is already there—Canvas-ready components, Tailwind and DaisyUI properly configured, CVA variants in place, every pattern documented.
No time lost to boilerplate or setup. No architectural decisions to agonize over. You extend Pablo's foundation and focus on what makes this project unique.
Not just surface-level familiarity with Canvas, Tailwind, and DaisyUI—but genuine understanding of how they work together. Every project deepens your expertise.
The foundation is solid. The patterns are proven. The documentation is there when you need it. You're not guessing—you're building.
Polished themes. Maintainable code. Ahead of schedule. Your team notices. Your clients notice.
One theme. Complete documentation. Every project, faster.
Pablo is open-source, thoroughly documented, and ready for your next project.
Demo it. Inspect the code. Read the docs.
See for yourself why developers are making Pablo their go-to base theme for modern Drupal development.
Your next theme starts here.