A big update to one of the most helpful plugins. Design Lint can now automatically fix missing fill, text, stroke, and effect styles using styles found in your designs. It will make type suggestions (!) if a text layer is close to an existing type style. Import your styles by running Design Lint in a design system file, then the plugin will use these styles to make suggestions (stored only on your computer). You also can now create and apply styles in bulk directly from the plugin.
“In this livestream Hanju Kim and Marvin Messenzehl from RTL+ dive into the file to understand the intricacies of designing for a wide array of platforms while maintaining impeccable structure and facilitating seamless collaboration.”
Raquel Piqueras and Christina Yang from Microsoft on organizing Figma files and making a few intentional changes which resulted in fewer meetings, higher quality work, a more agile environment, and a few praises from their partners along the way. (Thanks for sharing the friend’s link!)
Ridd shares a free annotation components library to help designers communicate more effectively and nail down the handoff process. Comes with a video lesson on organizing Figma files using the helpers library.
A refresh to the file browser, so you can spend less time searching, and more time creating. New shared projects and files tabs help you easily find files that others have shared with you. Search, Recents, and notifications now include content across your entire account.
Matan Rosen on how creating starter kits in Figma can help deliver products faster by letting designers focus on user experience instead of pushing pixels and doing repetitive design work.
Sections are great for organizing components, documenting states, grouping elements in external embeds, and better visibility of component and frame names.
Are you using #sections in @figma yet? They are one of the most underrated features in Figma. I switched my Figma component documentation entirely to sections and it has made a huge difference. Here's why: pic.twitter.com/WaqErkYBLi
— Christine Vallaure (@moonlearning) April 11, 2023
You can now keep your workspaces, teams, projects, and files more organized with custom sidebar sections on Organization and Enterprise plans.
Patrick Morgan with tips for tidying your Figma account with a file thumbnail component.
Feeling like your @figma account could use some tidying? I know, I've been there.
— Patrick Morgan (@itspatmorgan) February 25, 2023
Here are the 8 steps I follow to build a file thumbnail component that's minimal, consistent, and scales: pic.twitter.com/iJhBEoK0Es
Luis shares a few tips on structuring library files. He recommends optimizing variants for searching and usage rather than maintenance, and suggests this file structure: Page → Section → Variant. Also, check out his other thread on naming and splitting your library files.
We spend a lot of time talking about component structure, but the library files themselves are often ignored
— luis. (@disco_lu) February 27, 2023
So what goes into structuring a good Figma component library?
Here are a few tips, hopefully a good starting point 📈 pic.twitter.com/2zL7xk9eSx
Miggi shows how to use Figma sections for prototyping. Besides being a wonderful organizational tool, sections give you the ability to remember the states of areas of your prototype.
Anyone else love sections in Figma? @miggi takes it one step further to show you how to use sections for prototyping. pic.twitter.com/Z3IJZnRGjW
— Figma (@figma) February 13, 2023
Jess starts a productive discussion on organizing files in Figma by asking about having one file per feature where iterations/updates happen and another file for all “done” work. That’s similar to how I organize my work projects, but in reality, bringing work back to the “single source of truth” file or abstracting it to the design system is always hard to prioritize.
You're on a product team and you're organising your files in @figma. It's a large product and if all design work is in one file, the file is too big.
— Jess 🇺🇦 (@jesseddy) February 7, 2023
What do you think about having one file for each feature where iterations/updates happen. And one file for all "done" work? pic.twitter.com/6iSlphJEHP
Luis Ouriach wrote a massive multi-part guide on structuring teams, organizing projects, and managing files in Figma.
Jackie Zhang writes about approaches to enhance team communication through logically structuring Figma files, labeling and annotating your designs, and hooking up all your files in a single FigJam flow. I particularly like the last recommendation and going to try it on the next project.
The team at Deliveroo built a library of “file management goodies” to bring more context to their designs and help people across the business navigate design files more efficiently. Section banners, flow and screen details, highlights, notes, and linked resources helped their team annotate their thinking within Figma.
Continuing the theme of supercharging built-in features, this plugin takes Figma’s “Select all with…” command to the next level by offering a whole range of properties to choose from.
“Customers can collaborate confidently with agencies and companies, knowing that the right company can own the work. Customers on Professional, Organization, and Enterprise plans can now transfer teams and projects from one company to another in a few clicks, and customers on Organization and Enterprise plans can receive transfers.”
In addition to Joey’s thumbnail kit, check out this template from the design team at Doist. It’s specific to their products, but can be easily customized or used as an inspiration.
Joey Banks published an update to his file thumbnail UI kit with dozens of custom combinations, and now even easier to edit with component properties.
A few changes to team controls and permissions on Enterprise and Organization plans.