...
Our previous Figma plan had limitations. We could only create a single level of folders, making it difficult to organize organise design files for a large team working on multiple products across different regions. There was no documented system for consistently ordering and organizing organising design files.
New solutions
We upgraded to Figma Enterprise allowing us to create more 2 more folder levels, improving file organizationorganisation.
Implemented dedicated file templates for different types of designs, ensuring consistency and ease of use.
Enhanced file identification with improved file covers, making it easier to understand the status and purpose of each design.
...
More template types will be added in the future
Page
...
structures
Every Each design file should be created with this page navigation structure.
The pages of a file should include as show above;
Cover
To only contain the project cover for the feature. see File Covers
Final designs
The grouping should contain three sub-pages which include Developer handoff:
Dev handoffs
Prototype
QA
Design brief
...
User stories
...
PRD
...
UI Designs
Feature 1 [ as a page]
Iteration 1… [as a section]
Testing Prototype
...
Playground
...
Archive
...
Rules
Horizontal rule
Indentation for sub folders
...
Iterations
...
File covers
The template
The status
...
follow a specific page structure and setup based on its corresponding template. For example, designing a 'Payment' feature would use a structured template as outlined below. Refer to the 'Templates' section for more details.
...
File covers
We've introduced a new Figma component for file covers to improve file accessibility. View the component here.
...