Design system
Your colors, type scale, spacing and components drawn as a library of named parts, each with a usage note and its states for hover, focus and error. A developer builds from the same parts the designer used. You receive: the Figma library, with 14 color tokens, 9 type styles, 8 spacing steps and 22 components.
Original layouts
Layouts drawn for your own page types, from the home page to a product page to an article, at phone and desktop widths. The count of layouts follows what your content needs. You receive: designs for 24 pages on 6 layouts, with the phone version drawn first.
Art direction and motion
The look of the whole site set down in one place: how large the headings run, how images are cropped and placed, how much white space a page holds, and which four motion patterns the site uses. You receive: an art direction board and a motion specification with the four patterns and their timings.
Photography direction
A review of the photographs you already have and a brief for the ones you need. The brief gives the framing, light and subject of each new shot, so a photographer can work from it. You receive: a selection of 41 usable photos from the 63 supplied, and a shot list of 12 new ones.
Accessibility review
The design reviewed against WCAG 2.2 AA before it reaches a developer: text contrast, focus order, focus visibility under a sticky header, and controls for moving content. A design file cannot show that a built site passes, so the build is tested separately. You receive: a review sheet listing 9 contrast pairs with their ratios.
Figma handover
The design file lives in a Figma team in your name from the first day, with developer notes beside each component. If you change developers, the file stays with you. You receive: the Figma file, the token list and a one-page guide to how the library is organized.