In the file - Organizing your design system with Onfido 

Thank you! I feel a lot of these videos often assume you have some sort of base knowledge of Figma and design systems overall and don't overexploit for the audience and this did which was helpful

Amazing work! but I would love to see clearly the checklist of the New components step-by-step process 😫

I'm about a 1/3 the way through the video and wanted to stop to leave a comment about a number of things in this setup that I like so far: the project overview page, ticket naming convention, under the whole DS project there are separate projects for components, kits etc.

Just finished the video, pretty good stuff! Understanding with the current sound worked pretty well for me when I turned on Captioning

Thanks for sharing Steve! This is awesome work

Hey everyone, what would be the best approach to describe all the ux patterns in the figma library? Just including the description on the artboards next to the components? How are you usually doing it? Please share your best practices. Thank you

Super interesting! I'm currently switching from Sketch & Abstract to Figma so these advices are super useful. I just have a question related to their workflow. At 16:08, Steve present the fact that they have a project for their "Source" files and other projects for WIP files. But if they work on something that already exists in the source of truth, how do they apply the changes from WIP files to the "Source" file? - Copy pasting changes will break the overrides if the elements you changed have instances. - Do the changes again on the source file means to do the job twice.

Hey, folks! Great video - curious what is in the "UI Kits" that wouldn't be covered by "Assets, Components, and Patterns?"

In early stages of studying kids must be given courses of ,'order' and 'planing'so they can learn in early ages how to be organized and put successful plans through the rest of their lives.

Luis looks like a celebrity in this one

@14:00 It seems like a good Idea but name the covers with that small text for Jira tickets does not work -at least for me. It's really small and the benefit is to low to add it.. The tag is a nice idea. I endet up implementing tag & Project name in the cover tile and do the same in the project description so that it is searchable.

Just a tad bit of better audio and a gallon of storytelling would have make this mesmerizing. Good work. A lot of work and good work but this became an interview than expected. Some things that would be awesome to learn from this are: Naming conventions for files and components. Governance system like the cover template. (this was addressed through check lists. Would've loved to see the ckeck list itself) pages layout File segmentation. (this was addressed for the component template, are there other type of files?) If you have a template for laying out different components. layer naming conventions Problems of experiences stated concretely, such as "we tackled changing requests this way:" "We addressed an introduction to branching this way:" I know its WIP and it's a hell of a monster to tame, maybe the questions were out of order and demolished the intended presentation. I'd love to see more about this. Thanks Steve!

Where can i buy that file or storybook in Figma?

I wonder how they set up their typography tokens. I find it quite challenging

The audio is sounding weird. It's difficult to understand

How can i have that file in Figma?

How did you get dark mode?

Fix the sound !

how did u get the figma dark mode?

He moves around the examples too fast. I want to see the guts of how everything is actually structured, based components and the page org.

This video would have been much better with a little more enthusiasm from the speaker and if he had articulated the words better and not spoken so fast 3⭐/5

Needs to speak louder and slower, hard to follow

better audio please!

Audio is so low, all I hear is the train tracks 😂

Thank you! I feel a lot of these videos often assume you have some sort of base knowledge of Figma and design systems overall and don't overexploit for the audience and this did which was helpful