333 Creativo
Web platform for 333 Creativo — a branding, design and digital marketing agency. Built on Drupal with Drupal Commerce for purchasable services, a bilingual editorial system, and an architecture ready to grow the catalogue without touching code. The agency manages content, case studies and services from a panel designed for creatives, not developers.
The agency had fragmented digital presence: portfolio on one platform, forms on another, editorial content on a separate blog. The team wanted one platform where they could showcase work, sell services, capture leads, and publish content — without paying a developer every time they launched a campaign.
- Portfolio, blog and forms living in different tools — the team lost time coordinating between platforms and the data never crossed over.
- No bilingual editorial system — every release meant maintaining two parallel sites by hand.
- Purchasable services lived in downloadable PDFs — no way for a client to quote and pay from the site.
How I tackled it
Audit + architecture
Inventoried live content across the 3 previous platforms. Defined the content model in Drupal with types for service, case study, testimonial and article. Symmetric bilingual model from day one.
Drupal Commerce
Drupal Commerce setup for purchasable services: variants by scope, short-step checkout, local payment gateway integration. The team manages prices and availability without touching code.
Editor + previews
Polished editing layer: faithful previews, fields grouped by context, no technical jargon in the panel. Layout Builder configured with blocks the creative team can rearrange visually.
Migration + launch
Legacy content migrated via Migrate API, 301 redirects from the old URLs. Zero-downtime launch, Core Web Vitals monitoring through the first 4 weeks, and an editorial support plan for the team.
What happened next
A creative agency needs a CMS that doesn't feel like a CMS — clean fields, faithful preview, and no technical jargon in the panel. When editors understand the system without training, content flows and the dependency on a developer disappears.