Figma to WordPress: A Practical Handover Checklist
Published:
Published by: Hedou Bibi
Ready to hand over your Figma design? Check mobile layouts, interaction states, content and editing requirements before development starts.
A Figma to WordPress handover needs more than a desktop mockup. The developer also needs to know how the layout adapts, what happens after each interaction, where content comes from and what your editors should be able to change.
This checklist is for businesses with an approved design and agencies handing implementation to a WordPress partner. The aim is to settle the decisions that are easy to miss before development starts.
Identify the approved version
Keep the layouts approved for development in a clearly labelled area of the design file. Match page names to the brief and record the version or approval date. Separate explorations, old designs and optional ideas from the agreed deliverables.
Check that the developer can access the necessary pages, notes and assets. Figma access and export capabilities depend on the account and permissions in use. A shared URL is not, by itself, a complete handover.
Decide how missing mobile layouts will be handled
A three-column desktop section could become a vertical list or a horizontal scroller. Those choices change how people use the site. Navigation, long headings, tables, image crops and fixed elements also need a mobile plan.
You may not need a separate mockup for every simple page. Agree on representative layouts, the rules for the remaining pages and who approves the result. Test with real copy, including long English headings, rather than assuming short placeholder text proves the layout works.
Include states beyond the ideal screen
Scroll horizontally or use the arrow keys to view the full table.
| Component | States and decisions to include |
|---|---|
| Navigation | Open menus, current items, keyboard focus and mobile closing behaviour. |
| Forms | Required fields, validation, sending, success, failure and a way to continue. |
| Lists and filters | Pagination, empty results, long titles and resetting selected conditions. |
| Dialogs and motion | Triggers, closing, small-screen behaviour and a reduced-motion alternative. |
Notes are often enough for a simple interaction. Use a prototype or short recording when the sequence is harder to explain. Label demonstrations clearly so an animation used to express a mood is not mistaken for an agreed feature.
Specify editing beside each section
For a service card, list the editable title, image, description and link. Say whether editors can add or reorder cards and how the homepage selection works. “Everything editable” leaves both the interface and the workload open to interpretation.
Also decide what should stay fixed. A content team replacing copy and images may not need to rearrange every section. A marketing team assembling regular landing pages may need more flexibility. The editing model should reflect the work people actually do.
Use real content to review both languages
English and Chinese do not occupy the same space. Check a complete service page, a long article and a form in each language. Watch for clipped buttons, awkward headings and validation messages that push controls out of view.
List text inside images, diagrams and video captions separately. Decide which assets can be shared and which need a language-specific version. The multilingual WordPress launch checklist covers the next stage, including URLs and enquiry delivery.
Keep one shared handover record
- Approved file, page list, version and decision maker.
- Desktop and mobile layouts, including unresolved gaps.
- Interaction notes and actual link destinations.
- Editing fields, repeated content, sorting and permissions.
- Images, icons, fonts and responsibility for licences.
- Copy, translations, reviewers and outstanding assets.
- Acceptance checks and a process for scope changes.
This is a general planning example, not a record of a client delivery. Adapt it to the project, but keep one agreed version. If a page, layout or interaction changes after implementation begins, record the effect on scope and timing. Our development process gives those decisions a place in the project.
Need help with your website?
We’re Hedou Bibi, a WordPress team in Shanghai, China, operated by 上海禾斗匕匕网络科技有限公司. We work on design and WordPress development for businesses and agencies. Send your Figma file, page list and editing requirements to 1500351892@qq.com, or get to know our team.
