# How we prepare Figma designs developers can actually build

> What a build-ready Figma file includes: components, styles, responsive layouts and states, so your website looks like the design.

Source: https://plyo.studio/blog/figma-designs-developers-can-build

1.  [Home](/)
2.  [Blog](/blog)
3.  How we prepare Figma designs developers can actually build

# How we prepare Figma designs developers can actually build

What a build-ready Figma file includes: components, styles, responsive layouts and states, so your website looks like the design.

Plyo Studio 21 February 2025 6 min read

On this page

[1\. Styles before screens](#1-styles-before-screens)[2\. Components, not copies](#2-components-not-copies)[3\. Every breakpoint](#3-every-breakpoint)[4\. Every state](#4-every-state)[5\. Real content](#5-real-content)[6\. Notes where they matter](#6-notes-where-they-matter)[7\. Accessibility checked in the design](#7-accessibility-checked-in-the-design)[What you receive](#what-you-receive) [Common questions](#common-questions)

Related service

[Figma web design](/services/figma-design)

A beautiful Figma file isn’t always a buildable one. When a design leaves out the mobile layout, hover states or what happens with a longer headline, the developer has to guess. Guesses are where websites start to drift from the design. Here is how we prepare files so nothing is left to guesswork, whether we are building the site or handing it to your team.

## 1\. Styles before screens

Before any page is designed, we set up:

-   **Colour styles**, named by role (background, text, accent) rather than by colour
-   **Text styles** for every heading level, body size and label
-   **Spacing and grid**, so layouts follow a consistent rhythm
-   **Variables** for values that change between light and dark themes, if needed

These map directly to the CSS a developer will write, so the build matches the file.

## 2\. Components, not copies

Buttons, cards, navigation, form fields and section layouts are built once as components with variants. Every page uses those components, so a change to the button updates every button. Developers see exactly which pieces repeat and can build them once too.

## 3\. Every breakpoint

We design key pages at desktop, tablet and phone widths. Auto layout in Figma shows how elements stack and wrap, not just where they sit at one screen size.

## 4\. Every state

A page is more than its default view. We include:

-   Hover, focus and pressed states for buttons and links
-   Open and closed menus
-   Form errors and success messages
-   Empty states, like a blog category with no posts yet
-   Loading states where content takes a moment to appear

## 5\. Real content

Placeholder text hides problems. We design with real headlines, real product names and real photos wherever we can, and test what happens with the longest and shortest versions.

> The best handoff is a file a developer can build from without sending a single question.

## 6\. Notes where they matter

We annotate interactions, animations, link destinations and anything that behaves differently from how it looks. Short and specific, right next to the element.

## 7\. Accessibility checked in the design

Colour contrast, text sizes, tap target sizes and focus states are checked in Figma, before they become expensive to fix in code.

## What you receive

-   An organised Figma file with pages for styles, components and screens
-   A short guide to the design system
-   Exported assets: icons, logos and images
-   A walkthrough call with your developers, if someone else is building

## Keep reading.

[All posts](/blog)

-   [
    
    Design Writing alt text that works 6 min read](/blog/writing-alt-text-that-works)
-   [
    
    Design Website accessibility: where to start 7 min read](/blog/website-accessibility-where-to-start)
-   [
    
    Design What a brand identity package should include 5 min read](/blog/what-a-brand-identity-package-includes)

Updated 21 February 2025

FAQ

## Common questions

[Ask a question](/contact)

### Can you design in Figma and let our team build it?

Yes. We regularly design files for in-house teams and other developers, and stay available for questions during the build.

### Do you design for Webflow and Shopify too?

Yes. We design with the platform in mind, so layouts and components translate cleanly into Webflow, Shopify, Astro or Next.js.

### How long does website design take?

It depends on the number of unique page templates. A typical marketing site with five to eight templates takes a few weeks, including moodboards and revisions.

About Plyo Studio

## Custom Astro websites. Built on Cloudflare.

Plyo Studio is an independent web studio that designs and builds fast, search-ready websites, web apps and interactive maps. Sites are custom-built in Astro and hosted on Cloudflare, so they load quickly and are easy for search engines and AI answer engines to read.

Founded by Chloe Nixon, a full stack developer and UI/UX designer from Australia, and Micky, a software engineer from New Zealand. Clients work directly with the founders from the first call to launch. Typical work: custom websites, migrations off Webflow, WordPress, Wix and Squarespace, web apps, and interactive maps and GIS. Projects are quoted at a fixed price before work starts.

[Start a project](/contact) [hello@plyo.studio](mailto:hello@plyo.studio) [About us](/about)

## Related pages

-   [Blog Read practical notes on designing, building and moving websites.](/blog)
-   [Figma web design UI and UX design, handed over ready for your developers to build.](/services/figma-design)

Start a conversation

## Ready for a website that works harder?

[Start a project](/contact) [Free website audit](/audit)
