By the end of this lesson you can
- Publish and use shared libraries of components and styles.
- Collaborate through comments, branching and version history.
- Manage library updates without breaking other people's work.
The idea
A library is a file whose components, styles and variables are published so other files can use them. Teams usually have one core library (the design system) and product files that consume it.
Publishing and updating
When the library owner publishes changes, consumers are notified and can review and accept updates. Write a short description with each publish so people know what changed and whether anything might break.
Collaboration tools
- Comments: pin feedback to the exact spot. Resolve comments when done.
- Version history: name versions at milestones ("Ready for test round 2") so you can return to them.
- Branching (on some plans): work on changes separately, then review and merge, like code branches.
- Multiplayer editing: several people in a file at once. Agree who owns which pages to avoid clashes.
Why it matters in real projects
Design is a team activity. Shared libraries keep many designers consistent, and good collaboration habits stop work being overwritten, lost or reviewed in the wrong version. On larger teams, managing library updates carefully is as important as designing the components.
A realistic example
A library owner changes the spacing inside the card component and publishes without a note. Product designers accept the update and discover days later that several carefully balanced screens now overflow.
The team adopts a routine: changes are made on a branch, reviewed by a second designer, published with a clear note ("Card: padding 16→20px. Check tight layouts."), and announced in the team channel. Product designers review updates before accepting, and named versions let anyone roll back a screen if needed.
Step by step
Create a library file
Move components, styles and variables into one file.
Publish
Publish the library with a description.
Enable it in a product file
Turn on the library and use its components.
Make a change
Edit a component, publish with a change note and accept the update in the product file.
Use comments
Leave and resolve comments with a teammate.
Name a version
Save a named version at a milestone.
Common mistakes
Mistake Publishing without notes.
Instead Describe every change and its impact.
Mistake Copying components instead of using the library.
Instead Use library instances so updates flow through.
Mistake Leaving comments unresolved for weeks.
Instead Resolve or reply regularly so the file stays readable.
Check your understanding
Choose an answer, then check it. There is an explanation either way.
Practice exercise
Exercise · about 45 min
Library round trip
Practise publishing and consuming a library.
Steps
- Move your Stage 5 components into a library file and publish.
- Use them in a separate product file.
- Change one component and publish with a note.
- Accept the update and check the product file.
Deliverable
A library and product file with a documented update.
Self-assessment
Tick each item when it is true of your exercise. Be honest; this is for you.
4 items
Summary
- Libraries share components, styles and variables.
- Publish with notes; review updates before accepting.
- Comments, versions and branching support teamwork.
- Good habits prevent lost and broken work.
Further reading
Third-party sources, chosen for reliability. They open in a new tab.
- Design critiques (opens in a new tab)Nielsen Norman Group
- Figma Learn: help centre (opens in a new tab)Figma
Your notes
Marking complete updates your course and roadmap progress.