#Community
Automator
Jordan Singer shows some of the automations in his AI tool. Looks amazing, and you can join the waitlist at his website.
Here's a thread on some of the automations I've put together in Automator from @tricycleai ranging from simple to complex 👇 pic.twitter.com/NSUpMVwAmu
— Jordan Singer (@jsngr) October 23, 2021
Add the component name to the component description
A nice tip to UI kit maintainers from Jan Toman.
đź’ˇ A small usability tip for @figmadesign UI kit maintainers:
— Jan Toman (@HonzaTmn) October 15, 2021
Add the component name to the component description. It's especially useful when the component name is longer than ~10 characters. pic.twitter.com/gawuvNle6X
Building Form Components
Ridd with a step-by-step walkthrough to help you design form components that scale without drowning yourself in variants.
Tic Tac Toe
Play Tic-Tac-Toe with 2 or more players.
lil todo
A simple todo widget by Jordan Singer.
Tools that help people to think and communicate visually
Sho Kuwamoto on the role of widgets and how Figma and FigJam work together. See also his thoughts on why design tools exist.
When I think about figjam vs @figmadesign, I think of them as two points in a long path that we are on, as a company.
— Sho Kuwamoto (@skuwamoto) October 20, 2021
And this is because I don’t really think of figma as a design tool, per se
1/n https://t.co/ySPn9KWMwb
The way we work has forever changed
Thread by Dylan Field, the CEO of Figma, on not just translating physical experiences into digital realms but also making digital experiences even better than physical counterparts.
Today is one of the biggest launches in @figmadesign history. SO PROUD OF THIS TEAM!
— Dylan Field (@zoink) October 19, 2021
ICYMI, we announced widgets / plugins in FigJam, open sessions, code blocks, rich content embeds, some great new partnerships and more: https://t.co/O7Ek2DEj2y
Thread 👇 (1/9)
A new transition when opening a file on the Community
One of the many improvements that Figma ships unannounced. Looks really cool!
Hot 🥵 .. Have you seen the new transition when opening a file on the @figmadesign community ? And also the new layout of the pages. Kudos to @tonigemayel and all the team who manage/build the community space. pic.twitter.com/rocBiaS6CQ
— Steven H-A  (@mrstev3n) October 21, 2021
Designing Interactive Components
A first-hand perspective by Nikolas Klein on designing and building Interactive Components.
I dug through some of my old notebooks and found some old sketches that look super similar to interactive components today.
— Niko (@nikolasklein) October 26, 2021
Remember this was while working with @skuwamoto on how we want to support Overlays in Figma's prototyping feature. pic.twitter.com/7e9JWdXrQF
How Interactive Components were built
Sho Kuwamoto on why it took so long to build and how other smaller features fit in a bigger vision.
I was kind of busy on launch day so I'm a little late to this tweet, but I wanted to share some thoughts on all the prototyping improvements we announced yesterday.https://t.co/DuPbvh3bHx
— Sho Kuwamoto (@skuwamoto) October 28, 2021
1/n
Design tools should uncover ideas you didn’t know you could have
A few more fantastic Interactive Components usage examples from Nikolas Klein.
Design tools are not just there to let you 'do your job'.
— Niko (@nikolasklein) October 26, 2021
Design tools should allow you to venture into the unknown and uncover ideas you didn't even know you could have.
Mastering design systems components in Figma
If you liked Jan Toman’s talk at Schema, check out this one as well.
Batch create styles
Luis shows how to create styles at rocket speed using batch renaming and the Styler plugin.
Naming arrow Variants
Bonnie Kate Wolf suggests using Unicode emojis in front of the variant name for a quick preview.
This is an amazing @figmadesign hack from @mattmatize for naming arrow variants. Add the unicode emoji in front of the variant name so folks can quickly see what they are going to be placing without reading. pic.twitter.com/JNEb3tdaGQ
— Bonnie Kate Werewolf (@bonniekatewolf) October 8, 2021
Match Variant properties & names with what’s reflected in the code
Joey Banks with an excellent suggestion on how to bring designers and engineers closer.
When it comes to working on design systems, one thing I've learned is how much of a positive difference it can make to match variant properties & names in Figma with what's reflected in code. Any opportunity to bring designers & engineers closer always feels like such a big win. pic.twitter.com/BPsr9zG1Nf
— Joey Banks (@joeyabanks) October 1, 2021
Write changelogs
Jan Toman (see his Schema talk above) with a few recommendations for design system maintainers.
A simple tip for UI kit maintainers in @figmadesign:
— Jan Toman (@HonzaTmn) October 3, 2021
- Release changes in smaller batches
- Add a detailed description of what was changed
- (Optional) Reassure consumers that nothing will break
Write changelogs. Small things like this matter. pic.twitter.com/J6kA16pj1f
A recent trick/tip that you share with everyone
As always, Rogie’s tweets gather a lot of fantastic replies.
What's a recent @figmadesign trick/tip you've found out that you share with everyone?
— Ë—ËŹË‹rawr-gieËŽËŠ (@rogie) October 13, 2021
Design systems panel discussion
“Figma’s Designer Advocate Luis Ouriach has been collecting your questions in chat and online. He’ll dig in with our speakers to tackle design systems questions big and small.”
Mastering the art of code — aligned UI kits
Jan Toman, Productboard. ​“Not sure where to start? Get your libraries off the ground by learning how to craft UI kits that designers will love using. We’ll dive into building flexible components, aligning their API with code, and dealing with changes as the design system evolves.”
