Humans are profoundly creative and inventive but at the same time immensely lazy. This is proven by our willingness to devote countless hours to designing and developing systems that can shave off a couple of minutes from our workday.
It now becomes clear why we created Figma Project Template.
Or maybe not! The actual truth is quality through consistency in execution and delivery. Though laziness wasn't the primary driver, still, it saves time.
The primary driver is to make sure that as a designer, you structure your Figma files in a predictable manner so that when you hand them over to developers or another designer, there is no hassle trying to find what's where. Everything is always in the same place. It makes your day more productive and less detective-like. The Sherlock Holmes days will be gone. Still, it saves time.
Can we all agree that Design projects will always have the exact needs? User Research, flow maps, wireframes, look and feel, User Testing prototypes, design library, and Design Tokens? Hummmm, you think. No worries, no one can blame you if you think otherwise.
In any case, that's what we did. We created a template whose files you can duplicate and apply to any of your new projects.
It goes beyond the surface, though. Each of the files has a predetermined architecture which you can seemingly use as a guide and expand from there when needed.
Take the Design Library as an example. Or the Design Tokens even. Similarly to the other files, these two offer a preset array of items, orderly placed, ready to be populated with your excruciatingly talented work.
Although following this glaring structure isn't imposed, we encourage you to do so. It saves you time. It saves the team time, more strikingly, in the long run.
Before you bounce, hold on for an extra second, please. Cheers. Since we were on the laziness, time-saving topic, we've also created a Design Library Checklist. A dramatically-complete list of the components, their states and variations for you to make sure you cover the whole thing.