Recap and wishlist from Joey Banks: ​“While the updates felt a little more iterative this time around rather than innovative, what Figma shared seems to be paving the way for all that’s near and far ahead. In case you missed the product keynote, or if perhaps you’d just like a recap of the highlights from the perspective of a design systems designer, I’d love to share all that’s new with you in this newsletter.”

This session is a must-see if you have time for only one. CEO Dylan Field’s opening keynote walks through how Figma rethinks product development from the ground up and introduces new methods to help you make great work.

A new free resource by Fons Mans.

Martin Bekerman is back with a new vector illustration made in Figma.

A 2‑hour course by Meng To on building a real website from a Figma template using Codux. ​“You’ll master responsive design, collaborate with developers on a real React project, export CSS from Figma using Locofy, set up breakpoints with media queries, add CSS animations, improve SEO, create multiple pages with React Router, and publish your site. By following best practices, you’ll bridge design and development, improve your web design skills.” 

Double Glitch made a new tutorial on creating a real working parallax effect in Figma. Don’t miss the Community file as well! 

Ridd explains how to make your components easier to use by exposing nested instances.

Jacob Miller shares two variables tips to avoid the most common problems: 1) ​“Never create a mode that shouldn’t be set at the page level” (read more about inheriting a context), and 2) ​“Never publish a variable that users shouldn’t consume” (see why component-scoped variables can 10x the number of variables you ship). Don’t miss discussions in replies. 

Draftocalypse seems to be over, but it’s still worth sharing this video that Tom Lowry, Director of Advocacy at Figma, put together to walk you through what’s changing and answer a few common questions. 

Jun 26th, 10:00 PM – 1:00 AM. ​“Figma fans, join the unofficial Config Afterparty at frog HQ! Mingle with fellow designers, enjoy eclectic beats, drinks & bites, win prizes, and keep the creative energy going. Get inspired by an engaging talk from Pablo Stanley, a Latin designer based in Mexico and co-founder and CEO at Musho & Lummi, and fun activities to help slow down and refocus your attention.” 

June 26th, 6–9 PM. ​“Fireside with founding designers at Instacart, Nike, Maven, and IFTTT.” 

June 25, 7:30–9:30 AM. ​“Make new connections while stretching your legs, soaking in the gorgeous bay views, and sipping on espresso. Molly Hellmuth and Socrates Charisis will guide you along a coastal trail with views of the Golden Gate Bridge. Afterward, we’ll enjoy some well-deserved coffee on the beach courtesy of Wix Studio!” 

Rob Hope interviews a design wizard Vijay Verma. ​“Vijay Verma is a talented designer renowned for his intricate Figma art and his extensive portfolio of free digital resources. In this episode, we explore his humble beginnings as an electrician in India and his rise to become one of the most beloved designers in the Figma community. Additionally, we have a special case study where Vijay walks us through his character design process, complete with a bonus time-lapse recording he sent after the interview.” 

Whoa, finally! Can’t believe this is getting fixed a few days before Config. Add bold, italic, underline, or strikethrough font style to a portion of text with an applied style without detaching it first.

Jordan Singer shares a few things he learned while designing and building AI at Figma.

Christine Vallaure made a responsive and modular type scale using a scaling ratio approach.

Designer Advocate Ana Boyer with a reminder to plan your tokens and variables implementation before creating them in Figma. ​“In general, building then refactoring your variables is much more work than taking more time to plan before implementing. As they say: measure twice, cut once.” (That said, making refactoring easier in Figma won’t hurt.)

Dan Hollick shared his Creator Micro setup (with a beautiful illustration, of course!), and there are some good ideas in replies as well. I also shared my setup on Twitter.

Using it for a few weeks made me dream of eink key caps that can be updated based on the current mode. I find it hard to remember what keys do across four modes, so I rarely switch them. Elgato Stream Deck might be the answer, but I’m not a big fan of the look.

Matt D. Smith boiled down his design process into eight steps. I love how a big part of it is conditional on the project’s complexity. So many designers make the mistake of following a complicated process and taking extra steps on more straightforward projects, where that time is better spent on another round of experimentation or iteration. (See also the above quote from Linear.)

The move of drafts to teams caused a big enough uproar in the Figma community to warrant an explanation from Dylan Field, the CEO of Figma. Dann Petty made one of the strongest arguments against this change.

The strong feelings made me wonder about the differences in how we use Figma, and it probably comes down to handling multiple accounts and teams. I usually have two Figma accounts — one for personal projects and another tied to my work email address. Each account has its own drafts, so my personal drafts are never mixed with work. If you’re a freelancer and a part of multiple teams with a single email address, all your drafts are mixed, and separating them can feel like an invasion into your personal space. I don’t share the strong feelings on this change, but can see where Dann and others are coming from. (Pro tip: I use a separate Figma Beta app for the personal account, so I never have to switch accounts in the app.)