Services — From Figma to code
The design is approved. Now it becomes code: WordPress or a custom site, identical to the Figma.
I turn your Figma file into code: a WordPress theme or a custom website, faithful to the design, fast, accessible and easy to update. For designers and agencies.
Get in touchWho it's for
- Designers and agencies who hand over a Figma and need someone to build it without approximations
- Businesses with an approved design that has to become a real site
- Anyone who tried a template and ended up with a site that does not look like the project
- Anyone who then wants to update texts and images alone
What you get
- A WordPress theme or custom site built on your file, not an adapted template
- Figma colours, fonts and spacing turned into design tokens, in one place
- Every design component built once and reused: new pages are assembled from them
- An admin designed for you: edit content and images, the layout stays protected
- Mobile version and accessibility (contrast, keyboard) part of the delivery
- Code on Git and a test environment to approve before going live
AIWith AI
I use AI to speed up repetitive parts, but I check every component against the design myself, measurement by measurement.
Learn more →A good Figma is ruined in only one way: by approximating it
Spacing rounded by eye, the same component rebuilt three times in three ways, a template bent until it vaguely resembles the project. The result is not what the client approved, and the designer notices first.
Styles and components, once
The file's styles become design tokens (in WordPress, theme rules) and every component becomes a reusable piece, with its variants. Changing a colour or a spacing means changing it in one place.
The site stays yours to manage
The admin panel lets you update texts and images without touching the layout. At delivery you receive code, access and instructions, with no ties to me.
- Figma
- WordPress
- PHP
- ACF
- Nuxt
- Tailwind CSS
- Vite
- Git
How I work
- 01
Reading the file
I check components, styles, states and mobile versions. If something is missing, I send you the exact list before writing code.
- 02
System and components
First colours, fonts and components, then pages. The site stays consistent and quick to extend.
- 03
Testing and review
On a separate environment you and your client try the site and flag corrections.
- 04
Going live
Only the approved version goes to production, with access and documentation.
Frequently asked questions
The main pages and components are enough. If states, edge cases or the mobile version are missing, I flag them when reading and we decide together how to complete them.
Yes, on the measurements of the file. Where a detail does not hold in the browser, for example a longer title or another language, I tell you first and propose a solution.
WordPress when you need a rich admin panel to manage every day; a custom site (Nuxt, with content in Markdown or a headless CMS) when the site has to be light and fast with few updates. We decide together after reading the file.
No: a custom Figma deserves custom code. If your workflow requires a page builder I can work with it, but I explain what it implies.
Yes, but we talk about it first: we can start from a reference or from a designer you work with, and then the step to the site is the same.
It depends on how many pages and features there are, and I only know after reading the file. I give you a written estimate with what is included, not a number that fits everyone.
You might also like
Custom WordPress theme development: code written for your project, structured content and an admin you can use without breaking the layout.
Freelance WordPress developer: custom themes and plugins, WooCommerce sites and stores, updates, security and fixes for slowness and errors.
// Contact
A project, a problem or just a question?
Agency, business or professional: choose how you'd rather talk to me. I reply as soon as I can, no strings attached.