Discover and read the best of Twitter Threads about #FigmaTips
Most recents (3)
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:
#1: Organize my components: I can organize my components using sections. This creates a dedicated section in the Assets panel, making it easy to rename and reorder components by simply dragging the sections on and off frames. Same as a frame you might say. No, it's not, read on!
#2 Documenting component states and details: Sections don't show up in presentation mode; only frames do. Therefore, I use sections as a meta level of organization and add frames for subcategories, such as behavior and specs. This allows me to showcase them in presentation mode.
Working smarter, not harder also applies to prototyping. 😉
Here are six #FigmaTips from Designer Advocate @_AnaBoyer for prototyping in Figma.
1/ Draw prototyping links from navigational components to reduce the need for repeatedly drawing connections.
Here are six #FigmaTips from Designer Advocate @_AnaBoyer for prototyping in Figma.
1/ Draw prototyping links from navigational components to reduce the need for repeatedly drawing connections.
2/ Create interactive components in your libraries, so designs that use those components already have micro-interactions built into their prototypes, adding an additional level of fidelity.
3/ Nest interactive components to reduce the number of prototyping links. 
When designing tables,I prefer the column-based method since I find it more flexible. But it always had one major downside to me: it wasn't possible to show a hover state on the row. So I sat down and found a solution that Iam happy with. @figmadesign @FigmaHunt #figma #figmatips
Step 1: Create a table cell. In this case I added a line-wrapper frame for the bottom border and a wrapper that holds the text and the image.
Step 2: Duplicate and make it a variant. Give the first component the value of "False" and the second the value of "True" (-> this will be our hover component)
