lesson

Good documentation is vital and shows that you care about your design system and those who will use it. Lacking good documentation practices could spell doom for a design system.

Mikael Vesavuori

lesson

Code generation with Figmagic 4 will only take you so far. For our most important and complicated components, we will need to do some manual work, composing small bits into more advanced ones. Let's compose one from what we've made so far!

Mikael Vesavuori

lesson

Now, we leave the easy flat components for the more detailed nested ones!

Mikael Vesavuori

lesson

Galloping ever onwards, we'll wave our magic wand and summon our low-complexity components.

Mikael Vesavuori

lesson

And now for some bells and whistles—graphics and icons!

Mikael Vesavuori

lesson

Let's put the Figma-first approach to the test by taking the step to turn a design into code.

Mikael Vesavuori

lesson

Let's move on from basics to the intermediate level and actually make some designs.

Mikael Vesavuori

lesson

Let's find our way by analyzing our UX sketches before digging into the details and building anything.

Mikael Vesavuori

lesson

Getting to know the configuration options is super important if you want to make the best use of Figmagic.

Mikael Vesavuori

lesson

Working effectively with Figmagic means understanding how and what it actually parses from a document.

Mikael Vesavuori

lesson

With all the other hard, boxy stuff behind us, the perspective now moves to the front-end components and Figma.

Mikael Vesavuori

lesson

While dogfooding does sound yucky, it's a word that connotes the practice of using one's own things, sometimes to build something new. That's what we will do now with the components we've built.

Mikael Vesavuori