UX & Experience Design
Great digital experiences aren't just about what visitors see — they're about what content authors can do. We design UX experience design for DXP and CMS platforms that serve both audiences: intuitive interfaces for end users and efficient authoring workflows for the teams who maintain them. From information architecture to component-based design systems, we bridge the gap between beautiful frontends and practical content management.
Let's design togetherDesign that works for users and authors
Your website looks good but frustrates content editors
The design team delivered pixel-perfect mockups, but your content authors can't maintain them. Every update requires a developer because the CMS components are rigid, undocumented, or too complex for non-technical editors to use without breaking the layout.
Your information architecture doesn't scale
Navigation was designed for 50 pages and now you have 500. Content is buried under inconsistent taxonomies, duplicate categories, and confusing URL structures. Visitors can't find what they need, and authors don't know where to put new content.
Your components don't form a coherent system
Every new page gets custom-built from scratch. There's no shared component library, no design tokens, no documentation. Frontend developers reinvent the same patterns while content authors struggle with inconsistent layouts across sections and pages.
Your CMS frontend wasn't built for headless delivery
You're moving to a headless CMS or composable DXP, but your frontend is tightly coupled to your current platform's templating engine. The design doesn't translate to a decoupled architecture, and your team doesn't know how to build component-driven frontends.
UX decisions are based on opinions, not research
Stakeholders debate layouts in meetings with no data to back their preferences. There's no user research, no usability testing, and no analytics-driven insights. Design decisions get made by committee instead of being validated with real user behavior.
Your multilingual experience feels like an afterthought
French pages have broken layouts because the design assumed English text lengths. Translation workflows are manual and error-prone. Authors manage languages in separate silos, and visitors switching languages lose their context and navigation state.
Our design approach
1
UX strategy and research
We start with your users — both the visitors navigating your site and the authors managing it. Through stakeholder interviews, content audits, analytics review, and user journey mapping, we define a UX strategy rooted in evidence. We identify friction points, content gaps, and workflow bottlenecks that hold your digital experience back.
2
Information architecture for CMS and DXP
We design site structures, taxonomies, and navigation models that scale with your content. This isn't generic IA — it's built for your specific CMS or DXP platform, accounting for content types, translation workflows, personalization rules, and how authors actually create and organize content day to day.
3
Content author experience design
We design the authoring interface alongside the visitor interface. That means intuitive component configurations, clear content modeling, inline editing where the platform supports it, and documentation that helps editors work independently. A great author experience reduces publishing time, decreases errors, and eliminates the "call a developer" bottleneck.
4
Frontend development and design systems
We build component-based design systems that work with your CMS — whether it's a traditional CMS like WordPress, a headless platform like Contentful or Storyblok, or a hybrid DXP like Sitecore. Design tokens, responsive components, accessibility compliance, and clean frontend code that your team can maintain and extend.
5
Usability testing and optimization
Design doesn't stop at launch. We run usability tests with real users, analyze heatmaps and session recordings, and optimize based on data. We test both the visitor experience and the author experience — because a CMS that editors avoid is a CMS that produces stale content. Continuous iteration keeps your experience sharp.
What you won't get from us
Pixel-perfect mockups that editors can't maintain without a developer
Generic design agency work disconnected from your CMS platform
Templates that break when content is longer, shorter, or in another language
One-off page designs with no reusable component system behind them
Designs delivered as flat files with no CMS implementation guidance
UX opinions without user research or data to back them up
Experiences designed for your platform
UX audit and research report with prioritized recommendations
Information architecture — sitemaps, taxonomies, navigation models, and URL structure
Content model design aligned with your CMS or DXP capabilities
Component-based design system with design tokens and documentation
Author experience wireframes — content editing flows, preview modes, and publishing workflows
Responsive frontend templates built for your CMS templating engine or headless framework
Accessibility compliance review (WCAG 2.1 AA) with remediation plan
Usability testing sessions with findings report and design iterations
UX & experience design for DXP explained
What makes UX experience design for DXP different from generic UX design?
UX experience design for DXP goes beyond visual design. It accounts for how content is modeled, how authors create and manage pages, how components render across channels, and how the platform's capabilities shape what's possible. A generic design agency gives you mockups — we give you a design system that works within your CMS or DXP architecture, from Sitecore and Contentful to WordPress and Optimizely.
What is content author experience design?
Content author experience design focuses on making the CMS editing interface intuitive and efficient. It includes designing clear component configurations, logical content models, inline preview, and publishing workflows that reduce the time from draft to publish. When the authoring experience is well-designed, editors work faster, make fewer mistakes, and need less developer support — which means your content stays fresh and consistent.
How do design systems work with a headless CMS?
In a headless architecture, the design system lives in the frontend layer — built with React, Next.js, Vue, or similar frameworks — while the CMS provides structured content via APIs. We design components that map directly to content types in your headless CMS, so authors create content and the frontend renders it consistently. This approach powers the headless acceleration program and works with platforms like Contentful, Storyblok, and Sitecore XM Cloud.
Do you handle accessibility compliance?
Yes. Accessibility is built into our UX experience design process from the start, not bolted on at the end. We design and develop to WCAG 2.1 AA standards, covering semantic HTML, keyboard navigation, screen reader compatibility, color contrast, and focus management. We also test with assistive technologies and provide remediation guidance for any existing accessibility gaps in your CMS templates.
Can you redesign an existing site without re-platforming?
Absolutely. Many of our engagements involve redesigning the frontend experience on the same CMS platform. We audit your current components, identify what to keep, consolidate duplicates, introduce a design system, and improve both the visitor and author experience — all without migrating to a new platform. If a migration is on the roadmap, our UX work translates directly to the new platform through our development and maintenance services.
How long does a UX engagement typically take?
A UX audit and strategy engagement typically runs two to four weeks. A full design system and frontend build spans eight to sixteen weeks depending on the number of components, languages, and platform complexity. We scope every project with clear milestones and deliverables. Contact us for a tailored timeline based on your platform and goals.
Let's design together
Whether you need a UX audit, a design system, or a complete frontend rebuild — we design experiences that work for your users and your content team.
