Achievements
Corporate website redesign with Next.js
Achievement summary
This summary provides the essential reading points. It does not replace the complete case study: scroll down to review the detailed context, steps, limitations, and critical review.
- Context
- 1UP Distribution's showcase website needed to move away from the Odoo builder to present the company more effectively to professional clients across screen sizes.
- Challenge
- Replace a constrained site with a credible B2B presence on every screen without sacrificing readability or accessibility to visual effects.
- My role
- I audited the existing site, formalized the requirements, analyzed the Figma mockups, then built the responsive integration and front-end architecture with Next.js.
- Key decision
- Move to a reusable-component Next.js architecture and reserve animation for moments where it genuinely supports the message.
- Result
- The redesign replaces constrained blocks with a continuous responsive interface, reusable components, and interactions that remain accessible without blocking information.
- Evidence
- Website screenshots, performance checks, and material from the linked experience make the achievement reviewable without exposing internal information.View the detailed evidence
Visual proof
Screenshots and demos from real projects.
Media 1 of 5
Video hero and positioning
First viewport of the corporate site, built around a video background, clear messaging, and distribution/product-creation CTAs.
01
Presentation
1UP Distribution’s showcase site had been built with Odoo’s page builder. It did not explain the company’s activities clearly to business visitors, and its mobile layout lacked flexibility. I worked with management to define a Next.js redesign, separate from the ERP, to give us more control over implementation and maintenance.
The project brought together graphic design, marketing and development. I audited the existing site, translated mockups into components and handled architecture and hosting decisions. This case study covers design and staging of the first bilingual version.
Insufficient mobile rendering. The old website displayed poorly on phones. Responsive design is the ability of an interface to adapt its layout, text, images, and interactive areas to the width of the screen. It is not enough to shrink a desktop page — blocks must reorganize, buttons must remain usable, and important content must retain a readable hierarchy. This weakness could damage the experience of a prospect visiting from a mobile device and weaken the prospect's first impression of the company.
Deliberate separation from the ERP. The corporate website does not display a sales catalog and therefore does not need to read Odoo products, stock, or orders. It is designed as an application independent of the ERP, reducing technical dependencies and avoiding a connection between two systems without a business benefit. Integration remains under consideration for contact form submissions. In that specific case, the connection would have a clear purpose — automatically forwarding an inquiry to the tool used by the company to process it.
02
Objectives, context and stakes
Structuring the homepage around three essential types of content. To be considered complete, the homepage must present the company, its partners, and its activities. The company introduction explains who we are. The activities section describes distribution and product creation. The partner section provides examples where approval has been obtained. These three groups must form a coherent story leading toward contact rather than a collection of unrelated sections.
Assessing contact quality rather than volume alone. The relevance of the new image can be observed through the profile of companies that make contact. If inquiries come from organizations similar to the customers and partners 1UP already supports, the website will have communicated its positioning more effectively. This remains a qualitative indicator at launch, with no target number of form submissions currently defined. It nevertheless distinguishes an increase in low-value traffic from visibility that genuinely attracts the intended professional audience.
Deciding who receives inquiries. At the milestone described here, the final recipient for the contact form still needed to be chosen. Launch depended on a monitored inbox or tool, clear ownership of incoming requests, and a test confirming actual delivery. Odoo integration could then be evaluated against the chosen workflow. The team could start with a simple email flow as long as each inquiry reached the right person and they knew how to respond.
03
Risks and mitigation measures
The main delivery risk was that mockups and copy were still awaiting approval. Brand assets required approval from the people authorized to use them. I protected the first release’s scope and used prototypes to keep moving while decisions were pending, keeping placeholder content outside the publication scope.
Reduced-motion support that remains inconsistent. The repository already contains initial support for the prefers-reduced-motion system preference — some Motion components disable their effects, some videos use a still-image fallback, and a Playwright test verifies this behavior on part of the corporate pages. However, coverage is not yet consistent across every historical animation, particularly those driven directly by GSAP, page transitions, and Lenis scrolling. V2 should harmonize these mechanisms and provide lighter behavior for low-powered devices or slow connections. Until then, no essential information should depend on motion alone.
A migration that may affect search visibility. Replacing the old website can cause the company to lose some of its existing search visibility if pages disappear, their addresses change without redirects, or search engines temporarily encounter a non-indexable version. A permanent redirect tells visitors and search engines that an old URL has moved to a new one. Before the switch, useful URLs must therefore be inventoried, retained where possible, redirected when changed, included in a coherent sitemap, and checked to ensure temporary blocking rules used during development do not remain active.
04
The steps — what I did
Formalizing the requirement in a specification. The audit findings were turned into a specification. This document provides a shared reference for management, marketing, graphic designers, and development. It describes the expected result, features to plan, and constraints to respect without necessarily imposing every implementation detail. This step prevents the project from relying only on verbal discussions and makes it possible to compare design proposals or technical decisions with the original requirement.
Turning three mockups into a continuous responsive experience. Figma variants served as reference points, but the website had to work across every intermediate dimension. I used Tailwind CSS responsive classes to evolve grids, margins, text sizes, and element order at different breakpoints. A breakpoint is a width from which the layout adopts a new organization. I also checked for horizontal overflow and created alternatives, such as replacing a complex timeline with stacked cards on narrower screens.
Separating server and interactive components. Pages and elements that require no interaction remain Server Components, meaning components rendered on the server without unnecessarily sending all their logic to the browser. Components using animation, a form, or local state are declared as Client Components. This boundary is visible in the repository — pages retrieve content and metadata on the server, while Hero, BrandCarousel, FadeIn, or ContactForm handle client-side interactions. This separation reduces the JavaScript sent when interactivity is not required.
Implementing centralized internationalization. Routes use a dynamic language segment and next-intl loads the corresponding messages file. Internal links use locale-aware navigation, the HTML document receives language and direction attributes, and interface text is grouped in JSON files. The code was initially prepared for thirteen locales. At the milestone described here, the first release had been narrowed to French and English. Routing, language variants, the sitemap and structured data still needed to be checked against that scope.
Organizing content between translation files and Sanity. Stable interface and homepage text is read from next-intl message files at this milestone. The project also integrates Sanity, a CMS or content management system, for articles, careers, and more editorial corporate pages. Schemas define pages, sections, brands, FAQs, settings, and SEO metadata, while public queries exclude content marked as placeholders. Pages can use translated copy as a fallback when no published Sanity content is available. This architecture is intended to let marketing evolve structured content without editing code directly.
Developing a first functional contact workflow. The form already has an interface, sending, success, and error states, and a consent checkbox linking to the privacy policy. It sends data to a Next.js API route that checks required fields and the email address, removes line breaks from the subject, and sends an email through Resend using a React Email template. At this stage, routing kept development inquiries separate from production inquiries. This first version still needs to be aligned with the final requirement — split first and last names, add the optional phone number, choose final recipients, and complete protection against unwanted submissions.
Testing components, the API, and real workflows. Vitest and React Testing Library cover isolated components and functions, while Playwright runs browser scenarios. The Playwright configuration includes Chromium, Firefox, and WebKit as well as Pixel 7, iPhone 13, and iPad profiles. Existing scenarios notably check the homepage, navigation, form, absence of horizontal overflow, image loading, structured data, and some reduced-motion behavior. This combination detects both a logic error and a break visible only in a particular browser or screen width.
05
The stakeholders — interactions
Two graphic designers created the visual assets. I worked with the lead designer on adaptations between mockups and the working site. For example, when an animation translated poorly to a narrow display, I could demonstrate a simpler version that preserved the content hierarchy.
Animation as a concrete subject for compromise. Animations make the website feel more alive and contribute to its identity, but their libraries and media consume resources — they can increase downloaded JavaScript, place more demand on the graphics processor, or slow rendering on a less powerful device. My role is to find an appropriate balance between visual richness and performance. This may involve limiting animation to elements that truly matter, using a less expensive transformation, deferring its loading, or simplifying it on mobile and for people requesting reduced motion. I present these trade-offs to the people responsible for the company's image so that optimization is not perceived as an unexplained loss of design.
Marketing supplied and approved the copy and cleared visual rights. The managing director set priorities and was responsible for approving the release. I led the technical work, from responsive behavior through deployment preparation, and surfaced decisions that needed business input.
06
The results
At the milestone described here, the homepage and contact page were available in a bilingual working preview. The implementation addressed the old site’s mobile layout problem, and its components could be reused on subsequent pages. Screenshots show the homepage positioning and implementation choices. The contact flow had an initial implementation, with final delivery still to be confirmed for launch.
Compatibility checked beyond a single browser. I tested the journeys in the most widely used browsers and on phones. This cross-check matters because two browsers may interpret a styling rule, video, animation, or form behavior differently. Mobile testing also makes it possible to observe the website under the actual constraints of a touchscreen and limited space instead of merely reducing a desktop window's width. No test can prove that a website will work on every device in existence, but this coverage reduces the risk of publishing an experience that works only in my development environment.
Content management ready for trials. At that milestone, the Sanity models were available and marketing still needed to try the publication workflow. Making the tool available was the first step. Editorial independence would be demonstrated when the team could create a page, provide both language versions and publish it under the intended permissions. I remained responsible for maintaining the code and content models.
Preparing pages for indexing. I prepared the technical SEO foundations with localized metadata, canonical URLs, a sitemap and structured data. These gave search engines the information needed to identify pages and their language variants. Search visibility and branded queries would need to be assessed after cutover.
An audit of the homepage. The Lighthouse screenshot of the working version shows 99 for performance, 100 for accessibility, 96 for best practices and 100 for SEO. Those figures are for the homepage. I also used Lighthouse to examine loading under mobile and desktop simulation. Comparing the released site would require running the same checks under comparable conditions.
A stronger brand impression and more relevant inquiries were expected outcomes at this stage. The project helped me learn to implement another team’s design and make the consequences of my technical choices visible.
07
After the project
Organizing acceptance testing with project participants. The launch plan included final acceptance testing with design, marketing and management. Acceptance testing is a verification phase during which responsible participants confirm that a product meets the requirement and can be accepted. It was to cover visual rendering, copy, links, form behavior, languages, major devices, and the overall image conveyed by the website. Explicit approval was meant to distinguish defects that block launch from improvements that can be planned after it.
Preparing marketing to use Sanity. At that milestone, I planned to have marketing publish a test item. The exercise was to cover required fields, both languages, media and the move from draft to publication. Marketing would then manage content while I maintained the code and content models.
Monitoring URLs after cutover. The monitoring plan covered indexing of the new pages, crawl errors and important search queries around launch. I wanted to check redirects and already visible pages first, then distinguish routine fluctuations from technical issues that needed fixing.
08
My critical review
Prototyping interactions while design decisions were pending gave us something concrete to discuss about responsive behavior. In hindsight, I would have requested the copy earlier and brought marketing and design together around a complete page so they could make content and layout decisions together.
Sanity useful in the long term but not essential at the beginning. The first release could have been built without a content management system by temporarily keeping copy in the code. Sanity is therefore an anticipatory investment rather than an immediate technical requirement. Its value will appear when marketing regularly publishes articles, changes pages, or manages job listings without developer intervention. If this editorial autonomy remains little used, configuration and maintenance complexity will need to be reassessed. A tool remains justified over time only by the usage it genuinely enables.
On a future project, I would define the acceptance criteria and ownership of form submissions earlier. I would also validate one page end to end, from final copy to mobile checks, before building multiple animation variants. The technical checks would then support a release goal shared by the teams.
09


