Back to all insights

From Figma to website: our checklist for pixel-accurate builds

A design file is a promise. This is the checklist we use to make sure the finished website keeps it, on every screen size.

Watercolour wireframe sketches of website layouts
Photo: Hal Gatewood / Unsplash

Most design-to-code problems are not about skill. They are about questions nobody asked before development started. This checklist is how we ask them early.

Before writing code

  • Collect every text style, colour and spacing value into tokens.
  • Agree how each layout behaves between the designed breakpoints.
  • List the states the file does not show: hover, focus, empty, error and loading.

During the build

  • Build components first, then pages from those components.
  • Compare side by side with the design at each breakpoint, not just desktop.
  • Check real content lengths, not only the placeholder text.

Before launch

A final design QA pass with the designer catches the small things: a heading that wraps one word, a button that loses its hover colour in dark mode. Fixing them takes minutes; missing them shows on every visit.

Let's build something exceptional.

Have a website, CMS or CRM project in mind? Let's discuss it and turn your vision into a practical solution.