Check project status.
Thu Dec 29 2022

How to Organize Your Design Files

by
Ryan Eghrari
Ryan Eghrari
We organize design files into four sections. Each section is responsible for a different part of the design and development process. Organizing our design files in this way ensures there is a single source of truth for core components, designs, published pages, and scrapped ideas.

stoplight files
stoplight files

Design System (Core Components)

A design system is a set of standards to manage design at scale by reducing redundancy while creating a shared language and visual consistency across different pages and channels.

 It is a library of digital components that can be used to scale a product intuitively and quickly instead of building components from scratch.

In Design and Development

Figma pages stoplight system
Figma pages stoplight system
These pages are either currently being evaluated and ideated, being designed, or ready for development. We use the stoplight system so everyone can quickly see the state of the new features. To use the stoplight system you can add the emojis 🔴 🟡 🟢 🔵 ◻️ before the name of your Figma page.
Design Stages
Design Stages

Published

Published pages are pages that have been designed, approved, tested, developed, and are deployed to a production environment. We keep track of these pages in case we want to make changes to them in the future.

Graveyard

This is where designs go to die. Don't worry we keep them here so that we can easily grab old content/designs to reuse for the future. Sometimes an idea is not working right now, but it might work in the future. Instead of having to redo all the work that went into the idea, the designer can just grab it out of the graveyard.

Tags

Software Design
Figma

Related Articles

What is Test Driven Development
A deep dive into understanding test driven development and why it leads to higher quality software.
Software Engineering
+ 1 more
by
Ryan Eghrari
Ryan Eghrari

GCP vs. Azure vs. AWS
A introduction to the similarities and differences between GCP, Azure and AWS. When in doubt, we go with AWS.
Cloud Services and Providers
+ 1 more
by
Ryan Eghrari
Ryan Eghrari

An Optimistic Approach to Building Software
The three metrics that you can measure when building an engineering team, that lead to faster outcomes, happier team members, and better products.
Software Engineering
by
Ryan Eghrari
Ryan Eghrari

The Biggest Cost of Developing Software
Examining the costs of developing software and uncovering the biggest hidden cost most engineering firms don't know.
Test Driven Development
+ 1 more
by
Ryan Eghrari
Ryan Eghrari
The Lab

Our Library

Raidon
433 Broadway Suite 404 New York, NY 10012
+1 (332) 333-2855
© 2024 Raidon.