Figma > File structure and organization
Purpose
This issue links up a few discussions and examples of how the UX team has been structuring and organizing Figma files, and the content within, so that we could more formally arrive at and document a shared solution.
Benefits:
- Better onboarding process.
- More efficient cross-stage collaboration when understanding the file itself doesn't have to be learned.
- More efficient stage collaboration and know where/what to reference in Figma.
- Documentable and repeatable.
- Provides a starting point to collectively iterate on as new Figma features are available.
- Allows us to also consider how team libraries and shared assets can be used.
Considerations:
- File performance and bloat.
- Branching process.
- File thumbnails and quick reference.
- Collaboration with engineers, PMs, and other counterparts.
- Use case for drafts vs. team files?
- Use case for projects vs. individual team file?
The ask
This issue is to help facilitate the discussion in a central place so that we can move towards documenting a shared solution in an MR as well as update the Figma for GitLab guide. Add your thoughts, comments, use case in comments/threads below.
Resources
Edited by Jeremy Elder