Hi, my name is Shayaan, and I’m a web developer at Digital Polygon. A few months ago, I got the opportunity to join the IXP Program at Digital Polygon - an experience that completely changed how I approach web development.
When I started, I wasn’t completely new to coding — I already had hands-on experience with WordPress and a few JavaScript frameworks. Coming from a WordPress background, I viewed CMSs as simple “site builders” with mostly point-and-click interfaces. Drupal quickly challenged that assumption.
I quickly realized it’s not just a CMS but a powerful framework. Instead of being restricted to predefined content types, Drupal allows you to create your own content models, add custom fields, and design relationships that fit the exact needs of a project. And with Views, you can build dynamic lists, filters, and displays without writing heavy custom code — taking the functionality far beyond just developing a frontend website.
What really stood out to me was how Drupal blurs the line between a CMS and a full-fledged application framework. It gives developers the freedom to go from basic site-building to building highly customized, enterprise-grade solutions — something I never fully associated with a CMS until I started working with Drupal. What began as curiosity became a deep dive into how structured content and flexible architecture can scale the web - and that’s where Drupal stood out.
How It Started
The opportunity came through the IXP program, which pairs beginners with structured mentorship and real-world projects. What stood out to me was that it wasn’t just training for training’s sake — I would actually be contributing to meaningful projects while learning.
I felt both excited and nervous, but I said yes right away. Looking back, that decision was one of the best steps I’ve taken till now.
Learning the Drupal Way
The IXP Program’s structure mirrored how professional WebOps teams grow, moving from foundational site-building to backend development and real project delivery. My training was structured in three stages:
- First Stage: Site Building
I learned how to use Drupal’s admin UI, configure content types, build views, and understand how the CMS works on the surface.
- Second Stage: Backend Development
This is where things got serious. I learned about modules, hooks, services, and configuration management. I realized that site-building knowledge wasn’t just the basics—it was the foundation for backend work.
- Third Stage: Real Projects
Finally, I applied everything I had learned by contributing to internal tools and client websites. This phase was the toughest, but also the most rewarding.
The Work I Did
Highlights of my contributions included:
- Set up development environments for different projects.
- Managed site configurations using the Config sync.
- Built custom Views to organize and display data.
- Themed sections of a client site to match custom designs, while documenting and testing components in Storybook for consistent UI development.
- Contributed to issues on Drupal.org, including the module. Issues which need Code work, Reviews and so.
What I Learned (and Struggled With)
Custom theming tested my understanding of Drupal’s architecture, and contributing to Drupal.org pushed me outside my comfort zone.
Luckily, I wasn’t alone. While steady guidance from my mentors and colleagues at Digital Polygon, challenges became learning opportunities.
Why It Mattered
The biggest breakthrough for me was realizing that I could actually contribute to something bigger than my own work. Seeing my first Drupal.org issue accepted was a professional turning point. At that moment, I realized my code wasn’t just for a client or a company; it was helping improve the larger Drupal ecosystem.
That gave me a new level of confidence and shifted how I approach challenges: not with hesitation, but with curiosity.
Advice for New Developers
If you’re starting with Drupal (or even web development in general), here are a few things I’d share from my own journey:
- Explore before reinventing – Drupal’s community has contributed modules for almost everything.
- Don’t be afraid to ask – the Drupal community is full of people who want to help.
- Learn the balance between site-building, config, and custom code.
- Mentorship accelerates everything – don’t wait until you’re “experienced enough” to join a program like IXP.
Final Thoughts
The IXP Program at Digital Polygon didn’t just teach me Drupal It built my confidence to contribute, collaborate, and keep learning.
If you get the chance to join a mentorship like this, my advice is simple: take it. Curiosity, not experience defines what you can build.For me, this opportunity opened doors I didn’t even know existed. And it’s only the beginning.