Documentation within Figma - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

Purpose of Documentation in Figma

Why is it important to add documentation directly within a Figma design file when working on a BI dashboard project?

A It helps team members understand design decisions and data sources without leaving the file.

B It increases the file size unnecessarily and slows down the design process.

C It replaces the need for any external project management tools.

D It automatically generates SQL queries for the BI data model.

💡 Hint

Think about how documentation helps communication in a team.

Documentation inside Figma keeps all design context and explanations in one place, making collaboration easier and reducing misunderstandings.

❓ visualization

intermediate

Best Practice for Annotating BI Dashboards in Figma

Which method is best for adding clear documentation to a BI dashboard prototype in Figma?

A Embed long paragraphs of text in a single text box at the bottom of the file.

B Use sticky notes and text layers near dashboard elements to explain data sources and calculations.

C Add comments only after the design is finalized and shared.

D Use invisible layers to store documentation so the design looks clean.

💡 Hint

Think about clarity and ease of access for team members.

Sticky notes and text layers placed near relevant elements make it easy to understand each part of the dashboard quickly.

❓ data_modeling

advanced

Documenting Data Relationships in Figma

You need to document complex data relationships for a BI dashboard in Figma. Which approach best ensures clarity and usability?

A Use only color coding on dashboard elements without any text explanation.

B Write all data relationships as a single paragraph in the main dashboard page.

C Add external links to documentation outside Figma without any in-file notes.

D Create a separate page with a clear diagram showing tables, keys, and relationships, with text explanations.

💡 Hint

Visual diagrams help explain complex structures better than text alone.

A dedicated page with diagrams and text helps everyone understand the data model clearly and refer back easily.

🔧 Formula Fix

advanced

Troubleshooting Missing Documentation in Figma

A BI team complains they cannot find documentation about data filters in your Figma dashboard file. What is the most likely cause?

A Documentation was added as comments but never resolved or made visible.

B Documentation was shared via external wiki only.

C Documentation was included in a separate page clearly labeled 'Data Filters'.

D Documentation was embedded in visible text layers near filters.

💡 Hint

Think about how Figma comments work and visibility.

Comments in Figma can be hidden or unresolved, making them hard to find unless actively checked.

🎯 Scenario

expert

Creating Accessible Documentation in Figma for BI Dashboards

You want to ensure your Figma documentation for a BI dashboard is accessible to all team members, including those with visual impairments. Which practice should you follow?

A Avoid adding any text descriptions to keep the file size small.

B Rely on color alone to convey meaning in your documentation notes.

C Use high contrast colors for text and backgrounds, add descriptive alt text to images, and structure notes with clear headings.

D Use light gray text on white backgrounds to keep the design minimal and modern.

💡 Hint

Accessibility means making content easy to read and understand for everyone.

High contrast, alt text, and clear structure help users with visual impairments access documentation effectively.

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