CSS vs SASS
When I joined the Drupal.org site modernization project, I was the only full-time contributor from my company during its initial phase. I was tasked with auditing the existing theme and developing a recommendation for migrating away from SASS. To support decision-making, I created a series of discovery documents outlining the current architecture, upgrade feasibility, and implementation strategy. What began as a technical inquiry quickly evolved into a full-scale transition proposal for the Drupal.org theme.
One of the issues filed on Drupal.org during the redesign- Google Docs
- Research
Project Purpose
When asked if phasing out SASS and moving the theme to Vanilla CSS would be feasible, a simple yes-or-no answer wouldn't do. To determine whether replacing SASS with CSS was viable, I developed four in-depth analyses:
Each deliverable accounted not only for technical and performance impacts, but also for the collaborative and open-source nature of Drupal development. The proposed theme architecture balanced modernization with accessibility, maintainability, and ease of contribution for the wider community.
Tech Stack & Approach
The project centered around Drupal, with the early phase focused heavily on technical research, design system planning, and preparation for development handoff. Once the direction was approved, I remained involved in the initial implementation phase—helping establish scalable standards for future contributions and theme expansion.
Challenges & Lessons Learned
At the project's outset, I was the sole full-time resource on the theme overhaul and had limited time before the redesign would be showcased at DrupalCon Barcelona. Nearly a third of the timeline was dedicated to research and strategic planning, leaving very little room for implementation. Fortunately, additional developers joined shortly after the foundation was set, and we quickly transitioned into component development and feedback cycles. This experience pushed me to operate with clarity under pressure—balancing innovation with community-focused responsibility. It was a rare opportunity to contribute to the future of Drupal.org, and I'm proud of what we achieved in such a condensed timeline.
Impact
- ✔ Delivered a comprehensive migration strategy that influenced Drupal.org's front-end modernization
- ✔ Established early standards for theme development and community contribution
- ✔ Demonstrated leadership through documentation, planning, and early implementation
- ✔ Enabled faster onboarding for additional developers joining mid-project
Full layout of the folder and file structure in the old theme
The final listing of contents in the initial document