Fast, accessible websites that are easy to maintain
Fast for whoever visits it, clear for whoever edits it, sound for whoever inherits it. Fewer promises. More results.
The right technology, not the fashionable one
Every technology we use has a reason behind it. A robust CMS when content and editorial workflows come first; a headless or hybrid architecture when performance and channels justify it. Never the other way round.
We build to standards you can audit: WCAG 2.2 AA accessibility, Core Web Vitals in the green, and code another team could inherit tomorrow without surprises. That's our definition of quality: the kind you measure, not the kind you talk about.
STANDARD 01
WCAG 2.2 AA
accessibility verified on every delivery, not declared
STANDARD 02
CWV in the green
Core Web Vitals as an acceptance criterion, not a promise
STANDARD 03
Inheritable code
another team could pick it up tomorrow without surprises
WHAT WE DON'T DO
Saying no… is a standard too.
- Websites only the people who built them understand
- Code that ties you to us
- Redesigns for the sake of it
- Vanity metrics
Classic, headless or hybrid? It depends: here's how we decide.
We decide it with you at the strategy stage, with explicit criteria. Based on needs, not on fashion.
WHEN CONTENT COMES FIRST
Full CMS
- Complex editorial workflows, with roles and permissions
- The team lives inside the CMS, every day
- Thousands of pages and dozens of editors
Like Hospital Sant Joan de Déu →
WHEN PERFORMANCE COMES FIRST
Headless or hybrid
- Speed and scale matter more than the editorial workflow
- The same content goes out through several channels
- Decoupled CMS: the frontend evolves without migrating content
Like this very website ↗
They're not mutually exclusive: often the answer is hybrid. The specific tool (Drupal, Astro or others) comes after the criteria, not before.
Everything the service covers.
If it's on the list, it's in the price — no small print.
CMS
CMS development
New, or an evolution of your current platform.FRONTEND
Headless and hybrid architectures
A decoupled frontend when it adds value — classic when it doesn't.PERFORMANCE
Core Web Vitals
As an acceptance criterion, not an intention.ACCESSIBILITY
WCAG 2.2 AA
Verified, not declared.INFRASTRUCTURE
Infrastructure and hosting
Guidance on deciding where and how the site is served.
None of this is a promise: it's already in production.
What you usually ask us.
DOES YOUR WEBSITE NEED TO WORK BETTER?
Let's talkTell us where your website stands today and we'll propose a realistic path, with timelines and criteria you can audit.