Understack
Let’s talk about a project

Figma to WordPress

Your designer hands over the Figma. We hand over the site.

Figma to WordPress for agencies: we turn the design file into a custom WordPress theme, true to the layout and built so the client can update it on their own. White label, with your agency’s name on the work.

Request a quote All services
The design file turning into a site: the Desktop 1440 frame with its selected block becomes a Twig template, line by line, and the template becomes the same page in the browser, at the same size. Home.fig agenzia.it LAYERS PROPERTIES DESKTOP — 1440 1200 × 420 home.twig 1 2 3 4 5 6 7 8 9 10 11 12 {% extends 'base.twig' %} {% block content %} <section class="hero"> {# 1200 × 420 #} <h1>{{ hero.titolo }}</h1> <p>{{ hero.testo }}</p> {% include 'bottone.twig' with { testo: hero.azione } only %} </section> {% for scheda in schede %} {% include 'scheda.twig' with scheda only %} {% endfor %} {% endblock %}

A good Figma file gets ruined in only one way: by approximating it.

Spacing rounded by eye, the same component rebuilt three times in three different ways, a bought theme bent until it vaguely resembles the design. The site goes live, but it is not what the client signed off — and your designer is the first to notice. We start from the file: styles, components and variants become tokens and components of the theme, once. What is the same in Figma is the same component in the code.

If something is missing from the file — a state, a mobile version, an edge case — we ask before writing code, not halfway through.

What we deliver

A theme, not a set of pages: the approved layout and the structure to keep it that way.

  • 01

    Custom WordPress theme

    Built on the design, not adapted from an existing theme. Timber and Twig keep data apart from markup, so the code stays readable for whoever picks it up after us.

  • 02

    Design tokens from the file

    Colours, typography and spacing from Figma become tokens in the CSS. A change to the system is made in one place and applies everywhere.

  • 03

    Components, not pages

    Every component in the file becomes a component of the theme, with its variants. New pages are assembled from them, without rewriting anything.

  • 04

    An admin built for the client

    Structured ACF fields or Gutenberg blocks, depending on the project. The client updates text and images; the layout stays protected.

  • 05

    Responsive and accessible

    If the file has a mobile version we follow it; if it doesn’t, we propose one before building it. Contrast, focus and keyboard navigation are part of the delivery.

  • 06

    Repository and staging

    Code versioned in Git, in your own repository if you prefer, and a staging site where you and the client check everything before launch.

How we work from a Figma file

Four steps. The site only reaches production after you have approved it on staging.

  1. Reading the file

    We check components, styles, states and mobile versions. Anything missing is flagged straight away, in a precise list.

  2. System and components

    Tokens and components first, then pages. This is the step that makes the site consistent and quick to extend.

  3. Staging and review

    The site runs in a separate environment. You and the client test it there, and changes are made there.

  4. Launch

    Only the approved version goes to production, with a deliberate deploy. You receive access and documentation.

What we build it with

The same stack as this site. When the project or your workflow calls for something else, we talk about it first.

  • Figma
  • WordPress
  • PHP
  • Timber
  • Twig
  • ACF Pro
  • Tailwind CSS
  • Vite
  • Git

Frequently asked questions

  1. Do we need a complete Figma file?
    We need a file with the main pages and the components. If states, edge cases or the mobile version are missing, we flag them while reading the file and decide with you whether your team designs them or we propose them.
  2. We don’t have a design yet. Can you do it?
    Yes. We design the interface in Figma, you approve it with your client, and from there the path to the theme is the same. White label, like the rest of the work.
  3. Will the result match the design?
    Yes, to the measurements in the file. Where a detail does not hold up in the browser — a longer text than expected, another language — we tell you beforehand and suggest how to handle it.
  4. Do you use a ready-made theme or a page builder?
    No. The theme comes from your design. If your agency’s workflow requires Elementor we can work with it, but for a custom Figma design we advise against it, and we explain why.
  5. Will the client know you built it?
    No. We work white label: your agency is the name in the code, the documentation and the communication. If you need one, we sign an NDA before we see the file.
  6. How long does it take?
    It depends on the number of templates and the integrations, and we only know precisely after reading the file. You get an estimate with the scope in writing, not a number that fits every project.

The same team, for the rest of the work.

  • 01

    Custom WordPress theme

    Markup written for the project, structured content and an admin the client can use without breaking the layout.

  • 02

    Custom WordPress plugin

    Integrations, APIs and business logic that a generic plugin only half covers.

  • 03

    WooCommerce development

    Custom e-commerce: price lists, pricing rules, ERP, shipping and payment integrations.

  • 04

    PrestaShop development

    Custom modules and themes, migrations to PrestaShop 8, ERP and e-invoicing integrations.

  • 05

    Dedicated WordPress developer

    Development capacity reserved for your agency every month, inside your tools and your processes.

  • 06

    WordPress maintenance

    Updates tested before they go live, backups, security and monitoring, under your agency’s name.

  • 07

    Managed hosting

    Dedicated servers on a WordPress-tuned stack, configured and maintained by the people who build the sites.