Documentation within Figma - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is the main purpose of documentation within Figma?

Documentation in Figma helps teams understand design decisions, usage instructions, and project details all in one place, making collaboration easier and reducing confusion.

beginner

How can you add notes or explanations directly inside a Figma file?

You can use text layers, comments, or dedicated frames labeled as 'Documentation' to add notes and explanations directly inside a Figma file.

intermediate

Why is it helpful to use components and variants when documenting in Figma?

Components and variants let you show reusable design elements and their different states clearly, which helps others understand how to use them consistently.

beginner

What role do comments play in Figma documentation?

Comments allow team members to ask questions, give feedback, or clarify parts of the design without changing the actual file content.

intermediate

How can you organize documentation pages in Figma for easy navigation?

Create separate pages or frames named clearly for different topics like 'Design Guidelines', 'Component Usage', or 'Project Notes' so users can find information quickly.

Which Figma feature is best for leaving feedback without altering the design?

A Frames

B Text layers

C Comments

D Components

Comments let you add feedback or questions without changing the design itself.

What is a good way to show different states of a button in Figma documentation?

A Use text layers only

B Create separate files

C Add comments on the button

D Use variants within a component

Variants let you group different states of a component like buttons in one place.

How can you make documentation easy to find inside a Figma file?

A Use clearly named pages or frames

B Hide documentation in layers

C Add documentation outside Figma

D Use random colors

Clear names for pages or frames help users quickly locate documentation.

Which method is NOT recommended for documenting design decisions in Figma?

A Overwriting design elements without notes

B Adding comments for questions

C Using text layers with explanations

D Creating a dedicated documentation page

Changing design elements without notes can confuse team members.

Why is documentation important in Figma for teams?

A It replaces the need for meetings

B It helps everyone understand the design and work together smoothly

C It makes the file heavier

D It hides design flaws

Good documentation improves team understanding and collaboration.

Explain how you would organize and add documentation inside a Figma project to help your team.

Think about how to make information easy to find and understand for others.

Describe the benefits of using comments and components for documentation in Figma.

Consider how these features support collaboration and clarity.

Practice

1. What is the main purpose of adding documentation within Figma designs?

easy

A. To make designs easy to understand for everyone

B. To increase the file size unnecessarily

C. To hide design elements from viewers

D. To create complex animations automatically

Solution

1. Step 1: Understand the role of documentation in design

   Documentation helps explain design decisions and details clearly.

2. Step 2: Identify the benefit for teamwork

   Clear documentation improves communication and saves time for teams.

3. Final Answer:

   To make designs easy to understand for everyone -> Option A

4. Quick Check:

   Documentation purpose = clarity [OK]

Hint: Think about why notes help teammates understand designs [OK]

Common Mistakes:

• Confusing documentation with design decoration
• Thinking documentation hides elements
• Assuming documentation creates animations

2. Which of the following is a correct way to add documentation inside a Figma file?

easy

A. Hide all text layers to keep file clean

B. Delete all unused layers without notes

C. Use comments and text layers to add notes

D. Only use external documents, not Figma itself

Solution

1. Step 1: Identify documentation methods in Figma

   Comments and text layers are built-in ways to add notes directly on designs.

2. Step 2: Recognize why other options are incorrect

   Deleting layers or hiding text removes documentation; external docs are less integrated.

3. Final Answer:

   Use comments and text layers to add notes -> Option C

4. Quick Check:

   Documentation methods = comments + text layers [OK]

Hint: Remember Figma supports comments and text for notes [OK]

Common Mistakes:

• Thinking documentation means deleting layers
• Assuming external docs replace Figma notes
• Hiding text layers removes documentation

3. Given a Figma file with multiple pages, which page is best suited for detailed documentation notes?

medium

A. The first page with only images

B. A dedicated page named 'Documentation' or 'Notes'

C. The page with the most complex design

D. A hidden page with no access

Solution

1. Step 1: Understand page organization in Figma

   Using a dedicated page for documentation keeps notes organized and easy to find.

2. Step 2: Evaluate other options

   Notes on complex design pages or hidden pages reduce clarity and accessibility.

3. Final Answer:

   A dedicated page named 'Documentation' or 'Notes' -> Option B

4. Quick Check:

   Best documentation location = dedicated page [OK]

Hint: Use a separate page for notes to stay organized [OK]

Common Mistakes:

• Putting notes on complex design pages
• Hiding documentation pages
• Mixing notes with images only

4. You added comments in Figma but teammates say they can't see them. What is the likely issue?

medium

A. Comments require a paid plugin to be visible

B. Comments automatically delete after 24 hours

C. Comments only appear in exported PDFs

D. Comments were added but not resolved or viewed

Solution

1. Step 1: Check how Figma comments work

   Comments stay visible until resolved or dismissed by users.

2. Step 2: Understand common misconceptions

   Comments do not auto-delete, are visible in the app, and need no plugins.

3. Final Answer:

   Comments were added but not resolved or viewed -> Option D

4. Quick Check:

   Comments visibility = unresolved and viewed [OK]

Hint: Check if comments are unresolved and teammates have viewed them [OK]

Common Mistakes:

• Believing comments auto-delete
• Thinking comments show only in exports
• Assuming plugins are needed for comments

5. How can you best combine Figma documentation features to ensure your design is clear and easy to follow for a large team?

hard

A. Use a dedicated documentation page, add comments on key elements, and include descriptive text layers

B. Only add comments and avoid text layers to keep the file simple

C. Create multiple hidden pages with notes to avoid clutter

D. Export designs without notes and send separate documents

Solution

1. Step 1: Identify best practices for documentation in Figma

   Combining a dedicated page, comments, and text layers covers different documentation needs clearly.

2. Step 2: Evaluate drawbacks of other options

   Using only comments or hidden pages reduces clarity; separate docs break workflow.

3. Final Answer:

   Use a dedicated documentation page, add comments on key elements, and include descriptive text layers -> Option A

4. Quick Check:

   Comprehensive documentation = page + comments + text [OK]

Hint: Combine pages, comments, and text for clear documentation [OK]

Common Mistakes:

• Relying on only one documentation method
• Hiding notes instead of organizing them
• Separating docs from Figma file