menu
announcement

Spectrum is now read-only. Learn more about the decision in our official announcement.

Figma

Figma is the first collaborative UI design tool built in the browser. Join our growing community and kick off a conversation!

Channels
Team

Design File Hygiene

May 28, 2019 at 12:45pm
The Figma community has a new home. This thread is preserved for historical purposes. The content of this conversation may be innaccurrate or out of date. Go to new community home →

Design File Hygiene

May 28, 2019 at 12:45pm (Edited 3 years ago)
What do you do to structure your file names? How about layers? How do you enforce your naming schemes across the team?
The naming scheme that we follow is:

Projects

Project Name - ud: mm-dd-yyyy
The project name is a broad scope project. Examples used intenrally are things like Portal, Storefront, Design System, etc.

Files

Project Name - Focus PBI - ud: mm-dd-yyyy
Files include the project name, the view being worked on and then the number within our task tracking tool for reference. The file has an updated date for easy reference regarding the age of the file, and when it was last changed. This is more for "at a glance" understanding, and to search by date. The naming schemes used are largely to allow quick searching across our Team Library of projects and files.
Example: Portal - Image Request PBI-155234 - ud:05-28-2019

Pages

👋Cover 🌎Live - ud: mm-dd-yyyy ✅Verification - ud: mm-dd-yyyy 🚦Name Iterations - ud: mm-dd-yyyy ⚡️Name Prototype Iterations - ud: mm-dd-yyyy 💀Graveyard - _ud: mm-dd-yyyy*
The Cover page is based on one I duplicated and modified from it's broked down into 6 types: (Shared (for anything shared publicly), Explorations (for any work that is being explored --basically not for dev or stakeholders), In-Progress (for work not ready for dev, but open to review by stakeholders), Needs Review (for work that is mostly complete, and need verification), Ready for Dev (for work that is ready for review by engineering), and Complete (for work that is done and currently live). Feel free to use the cover template for your projects:
The Live page is what dev uses to implement, and should match the live version of the product.
The Verification page is what stakeholders review before it is moved into Live.
The Name iteration pages are often multiple pages, and are labelled according to the views being worked on.
The Prototype pages are often multiple pages, and are labelled according to the views being worked on.
The Graveyard page is just that...where designs go to be buried, but that want to be referenced without versioning.

Enforcing

We enforce it by simply documenting the file naming, and holding each other accountable. We also have an example Project Template with Files contained within it for quick access, and cloning.

June 7, 2019 at 6:07am
Do you have any loading and lagging issues with files with so many pages? Or you make a file per feature?

June 12, 2019 at 10:34pm
I make a file per Design Project. Then will reference that project’s views in a core Figma Project called Views. I also heavily rely on versions, and delete what I don’t need.