Frontend expertise
For teams that have chosen Tailwind CSS, or are stuck on an older version, and want styling that design and development agree on.
Move your styling to Tailwind CSS 4 with one set of design tokens shared by design and code. Fixed price, based on a short scan.
Design tokens & Tailwind CSS 4 migration
The value of a migration is not the new syntax. It's one set of design tokens (colour, spacing, typography) that designers and developers share, styling that lives next to the markup, and a lot less CSS to maintain.
I've done this before: from Bootstrap to Tailwind at Vereniging Eigen Huis, a migration with team training at Topicus Healthcare, and introducing Tailwind across a monorepo at Vattenfall.
How it works
-
Step 1: Scan
A short assessment for a fixed fee: your current styling, the tokens hiding in it and the screens that need the most care. You get a migration plan and a fixed quote.
-
Step 2: Migration
Tokens first, then screen by screen, with Tailwind running next to your existing CSS until it can go. Visual regression tests catch unintended changes, and old CSS is removed as each screen moves over.
Dependency and supply-chain hardening
Compromised npm packages and malicious install scripts are a real risk for any JavaScript project. I lock down how a repository installs its dependencies: install scripts blocked except for an explicit allowlist, a minimum age before new package versions are installed, and a frozen lockfile in CI, including the install step in your pipelines and Docker images. That works on npm 12 as well as pnpm; where pnpm's stricter defaults add something, I recommend moving to it.
It works for any JavaScript or TypeScript repository: Angular, React, Vue or plain Node. A short, fixed-price job; it doesn't make you immune, but it closes the most common ways in.
An extra senior in your team
I have limited room to join a team for front-end work: Angular, design systems or accessibility. Ask about availability.
What teams say about working with me
“He also introduced TailwindCSS to our development street and guided our team in its use.”
Read the full testimonial from Daan Ottink
Daan Ottink
Tech Lead, Topicus Healthcare
“He is easy going, knows all about front-end structures and tooling and comes with improvements for better maintainable code.”
Read the full testimonial from Rimmert de Jong
Rimmert de Jong
Team Lead & Project Manager, ThiemeMeulenhoff
“I got to know Menno-Paul as a calm, self-critical and very knowledgeable frontend developer.”
Read the full testimonial from Bram Achterbergh
Bram Achterbergh
Product Owner & Business Analyst, Vereniging Eigen Huis
Related work and writing
-
Angular 20 support ends on 28 November 2026
Move your styling to Tailwind CSS 4 with one set of design tokens shared by design and code. Fixed price, based on a short scan.
- Angular
- Security
-
Angular end of support: upgrade, pay or accept the risk
Move your styling to Tailwind CSS 4 with one set of design tokens shared by design and code. Fixed price, based on a short scan.
- Angular
- Security
-
npm supply-chain attacks: which defences actually stop them
Move your styling to Tailwind CSS 4 with one set of design tokens shared by design and code. Fixed price, based on a short scan.
- Security