{"id":531,"date":"2020-11-24T20:01:41","date_gmt":"2020-11-25T04:01:41","guid":{"rendered":"https:\/\/igorlanko.com\/?p=531"},"modified":"2021-08-19T12:04:47","modified_gmt":"2021-08-19T19:04:47","slug":"changes-of-a-single-screen","status":"publish","type":"post","link":"https:\/\/2021.igorlanko.com\/changes-of-a-single-screen","title":{"rendered":"How to track changes of a single screen in Figma"},"content":{"rendered":"\n

UPDATE. Aug, 2021.<\/p>Figma now has a Branching feature<\/a>. Something I've been longing for since learning about Git flow. While I still do believe it's important to leave notes on your designs, some of the benefits in this article may be washed away by this new Branching feature. Go check it out too!<\/cite><\/blockquote>\n\n\n\n

Design screens can change daily or hourly. But how to track these changes in Figma? There's File version control. But it's not really helpful to reverse the entire file when you only need to know what's changed in just 1 screen.<\/p>\n\n\n\n

Additionally, I'd like my colleagues to see those changes on their own. Without me always presenting each change I do. Imagine if you move a button 5px to the right, and the developer knows about it without your explanation. Like they would read your git commit:<\/p>\n\n\n\n

\"\"
Visual Studio Code shows the difference between the older and newer \"welcome.blade.php\" files. Lines 9, 10 & 11 were removed.<\/figcaption><\/figure>\n\n\n\n

There's of course Abstract and Zeplin. The first doesn't work with Figma yet. And Zeplin, well, it takes your designs away from Figma. It may not be always comfortable for the process.<\/p>\n\n\n\n

How I do it<\/h3>\n\n\n\n

Back when I was working at Arcade Design System<\/a> for Output, I created a label component that I would attach to all the screens. Here it is in the wild:<\/p>\n\n\n\n

\"\"
Status label is a yellow component on the left.<\/figcaption><\/figure>\n\n\n\n

The component has:<\/p>\n\n\n\n