Case study

Loomon

Full redesign of the Loomon website to clarify positioning, present services more clearly, strengthen studio credibility, and establish a more modern, bilingual, and durable Next.js + Payload CMS foundation.

PositioningAn offer reframed to be understood faster and more precisely

RedesignA more current visual direction to reinforce quality perception

Durable baseA Next.js + Payload CMS architecture designed to evolve in FR and EN

Case study

Loomon

Context

This redesign started from a simple observation: the Loomon website existed, but it no longer felt aligned enough with what I wanted to express. It was functional, but not attractive or convincing enough to properly carry my positioning, services, and the level of quality I want to communicate. The goal was therefore not to fix a “bad” website, but to evolve a support that had become too limited for the studio ambition.

Objectives

The project had to clarify priorities, make the promise easier to grasp, and create a smoother path to action.

Clarify Loomon positioning and frame the promise more precisely
Present services in a clearer, more targeted, and more credible way
Strengthen the website ability to turn interest into contact
Establish a cleaner, bilingual technical base that stays easier to evolve

Loomon response

I led the redesign both editorially and technically. On the experience side, I reworked message hierarchy, service framing, the portfolio, and the visual direction to make the whole website feel more modern, coherent, and engaging. On the architecture side, I moved away from the WordPress ecosystem toward Next.js + Payload CMS, with a more structured bilingual FR / EN foundation. One of the main challenges was integrating Payload CMS, which required me to rethink how content should be modelled and how the project should be organised. The learning curve was significantly accelerated with AI used as support for research, understanding, and problem-solving. Another delicate point concerned the link between Payload CMS, Supabase, and the Render build pipeline: the solution was to separate the first build phase from data initialisation, relying first on a seed mode to create the database cleanly, then reintegrating Payload into the application pipeline.

Deliverables

These deliverables reflect what was concretely put in place to make the digital presence clearer, more credible, and easier to maintain.

Editorial repositioning and message structure redesign
A more contemporary design for the homepage and marketing pages
Clearer, more targeted, and more conversion-oriented service framing
Technical migration from WordPress to Next.js + Payload CMS
A bilingual FR / EN base and a more robust seed pipeline

Results

The results below describe the visible effects of the work, even when they remain qualitative.

A website that reflects the Loomon quality level and direction much more accurately
A more modern, attractive, and credible presence from the first sections onward
A cleaner content and code foundation to evolve the website more confidently
A launch-ready visual result while waiting for the first real feedback and metrics

Case study

This case study shows how a clearer structure, better framed priorities, and the right deliverables can make a website more useful right away and more durable over time.

Discuss a similar project