project 04
Time to Work International B.V.
A multilingual, SEO-focused corporate web platform built from scratch for a Netherlands-based company providing international workforce and employment services.
- Category
- Web
- Role
- Frontend architecture, localisation and deployment
- Year
- 2026
technologies used
- TypeScript
- Next.js
- React
- Tailwind CSS
- Framer Motion
- i18n
problem
Problem
The company's existing web infrastructure was slow, fell short of responsive standards and handled its multilingual support clumsily. As the digital face of a company serving international candidates and businesses, it also failed to convey the corporate identity.
solution
Solution
I built a modular, SEO-focused architecture on the Next.js App Router, TypeScript and Tailwind CSS. I integrated Framer Motion for interface interactions, and designed the multilingual structure so that every language gets its own generated page without any performance cost.
outcome
Outcome
The corporate platform went live and now runs at ttw-international.nl, letting international candidates and companies apply comfortably from any device.
key features
- 01Modular architecture on the Next.js App Router, combining SSR and static generation.
- 02Dynamic multilingual (i18n) structure with no performance penalty.
- 03Fluid interface interactions and a corporate design language built with Framer Motion.
- 04Responsive application flow working smoothly across all devices.
why these choices
Why Next.js SSR/SSG rather than a classic React SPA?
For an international employment company, search traffic translates directly into business. In a single-page React application the content is rendered in the browser and appears late to search engines. Server-side rendering and static pages maximised both indexing and first-load performance.
Why dynamic i18n?
Multilingual sites usually either split every language into its own codebase or ship all translations to the client. The first makes maintenance impossible, the second inflates page weight. I built a structure where each page carries only the copy for its own language.
Why Tailwind?
The design had to follow the company's identity, and a ready-made component library would have meant fighting that identity on every screen. Tailwind provided a consistent scale and colour system while the design was built from scratch.