Grid auto layout explained well
I had avoided the grid flow because it felt confusing. The comparison with nested frames helped me decide when to use it.
Browse
Build flexible components with auto layout, component properties and variables, then use them to design a responsive dashboard
Created by Tomas Novak
Once you know the basics of Figma, the difference between a slow, fragile file and a fast, flexible one comes down to three features: auto layout, component properties and variables. This course teaches all three in depth, with the habits working product designers use to keep files tidy as they grow.
You will create a small set of components for an analytics dashboard: buttons, inputs, table rows, stat cards, a sidebar and a top bar. Then you will assemble them into responsive dashboard screens that adapt to content and switch between light and dark themes with a single mode change.
This course assumes you can already create frames, text and simple components in Figma. If you have finished a beginner course or designed a few screens, you are ready. Designers moving into design systems work, and developers who want to understand how designers structure files, will both get a lot from it.
Every lesson uses the current Figma interface. Where a feature depends on your plan, such as publishing team libraries, I say so and show a workaround that works on the free plan.
Product designer teaching Figma the way working design teams use it day to day
I am a product designer who has worked on web and mobile apps for over a decade, and Figma has been my main tool since it replaced my old desktop setup. I design screens, build component libraries and prepare files that developers can pick up without a meeting.
I teach Figma from the ground up and then into the features that separate tidy files from chaotic ones: auto layout, components and variants, variables and modes, and prototypes that behave like the real product. I care a lot about file structure and naming, because a design file is shared work, not a private sketchbook.
My courses are project based. You build real screens alongside me, and every section ends with a file you can keep and reuse.
I had avoided the grid flow because it felt confusing. The comparison with nested frames helped me decide when to use it.
The hug, fill and fixed lesson explained in ten minutes what I had been fighting for a year. My files are so much cleaner now.
We refactored our button set using booleans and instance swap the week after the component properties section.
The primitive and semantic structure with modes is exactly how our developers set up tokens. Handoff conversations got much shorter.
Building real components and then assembling screens kept everything grounded. The table rows lesson was especially useful.
Make sure you know Figma fundamentals first. Once you do, the pace is right and the explanations are precise.
The auto layout and variables content is strong. The library section felt short for a team setting with many files.
The CSS comparisons were helpful as someone who also codes. Good stress testing advice at the end.