We use Figma as our main design tool, but this naming format can work for any design tool. Correctly naming files is important for searching and also giving a useful descrption of what the file is about.
Each ticket item in the backlog gets a new file.
[ID]: [Module]: [Title]
- [ID] is generated from our backlog process
- [Module] We intuitively know the broad categories we are wokring on, as we start to name thing when we discuss them. Areas such as Requirements, Regulations, Product Compliance, or more user oriantated such as Onboarding, Profile, Support.
- [Title] Should be descriptive and also be taken from backlog process
Example file name
B25: Requirements: Show specs on view page
Keep spaces between each word as this aids searching. Do not capitalise titles.
Pages within files
Every Figma will include one or more of these pages:
- Final (When project is completed)
- Current (Work in progress)
- V1-10 etc (Created when a designer starts a new current version. They can include initial wireframes and than hi fidelity visuals)
- Components (For finalised components that will be moved to UI Library)
- Exploration (Concepts and ideas)
- Research (Inspiration, images, styles)