UX/UI · WordPress · Digital Experience
Giving a content team more control without sacrificing the experience
A multilingual, content-driven website rebuilt so editors could compose and change pages themselves, with a business calculator built into the experience.
UX/UI direction
Design-system thinking
Editorial model and block design
Interactive business tooling
QA, UAT and launch support
The challenge
The site carried real editorial weight—success stories, use cases, press content and contact workflows, in English and French—but every meaningful change required a developer. That is a slow way to run a content operation and an expensive way to fix a typo.
The usual remedy makes things worse. Handing editors an unconstrained page builder buys independence at the cost of the design holding together, and within a few months the site no longer looks like one product.
The approach
I treated the editorial model as a design problem rather than a permissions problem. The question is not how much freedom an editor gets, but which decisions they should be making at all.
So the design system came first: type scale, spacing, colour roles and component behaviour defined once. Editors then compose from reusable blocks and patterns that carry those rules with them. An editor can build a new page without being able to build one that contradicts the design.
What I delivered
UX and UI direction with a design system behind it, implemented in WordPress through Gutenberg as a set of reusable blocks and patterns covering the content types the team actually publishes—success stories, use cases, press and contact workflows—across a responsive, multilingual English and French experience.
The site also includes an ROI simulator: a piece of business logic expressed as an interactive tool rather than a static claim, letting a visitor reach a relevant figure themselves. Turning a commercial argument into something a visitor can operate is usually more persuasive than asserting it.
Delivery and launch
The work was validated against a replicated production environment before release, with QA and a UAT cycle involving the people who would use the editorial tools daily rather than only the people commissioning them.
Launch included the parts that are easy to skip and expensive to skip: redirects, duplicate-content cleanup and technical SEO work, so the migration did not quietly discard the site's existing search position.
Outcome
The content team can publish, restructure and translate without a developer, and the design still holds because the constraints are in the blocks rather than in a style guide nobody opens.
That is the measure worth caring about: not that a site was rebuilt, but that the people running it became less dependent on the person who built it.
My contribution
- UX/UI direction and design-system definition
- Editorial model: reusable blocks and patterns
- WordPress and Gutenberg implementation
- Interactive ROI calculator
- Production replication and UAT
- Launch support, redirects and technical SEO cleanup
Technology
- WordPress
- Gutenberg
- Reusable blocks and patterns
- PHP
- JavaScript
- Responsive CSS
- Multilingual EN/FR
A clear next step
Start with the decision in front of you.
Get preliminary direction first, or book a focused session when the question is ready.