Component library organization in Figma - Dashboard Guide

Dashboard Mode - Component library organization

Goal

Understand how to organize a component library in Figma to improve design consistency and speed up dashboard building.

Sample Data: Component Library Overview

Component Name	Category	Usage Count	Last Updated	Variant Count
Button	Controls	120	2024-05-10	3
Card	Containers	85	2024-04-28	2
Dropdown	Controls	60	2024-05-05	4
Chart	Visualizations	45	2024-05-12	5
Table	Visualizations	70	2024-05-08	3
Tooltip	Overlays	30	2024-04-30	1
Modal	Overlays	25	2024-05-01	2

Dashboard Components

• KPI Card: Shows total usage count of all components.
  Formula: Total Usage = 120 + 85 + 60 + 45 + 70 + 30 + 25 = 435
  Result: 435
• Bar Chart: Displays usage count by category.
  Data:
  • Controls: 120 + 60 = 180
  • Containers: 85
  • Visualizations: 45 + 70 = 115
  • Overlays: 30 + 25 = 55
• Table: Lists components with their variant counts and last updated dates.
  Columns: Component Name, Variant Count, Last Updated
• Filter Slicer: Category filter to select one or multiple categories.
  Filters bar chart and table to show only selected categories.

Dashboard Layout

+----------------------+----------------------+
|      KPI Card        |      Filter Slicer    |
|    (Total Usage)     |    (Category Filter)  |
+----------------------+----------------------+
|                      Bar Chart                |
|               (Usage by Category)             |
+----------------------------------------------+
|                    Table                     |
|      (Component details with variants)       |
+----------------------------------------------+
  

Interactivity

The Category Filter lets users pick one or more categories like Controls or Visualizations.

When a category is selected, the Bar Chart updates to show usage counts only for those categories.

The Table also updates to list only components from the selected categories.

The KPI Card remains static showing total usage of all components regardless of filter.

Self Check

If you select only the Controls category in the filter, which components update?

• The Bar Chart updates to show usage count 180 for Controls only.
• The Table updates to show only Button and Dropdown components.
• The KPI Card stays the same at 435.

Key Result

Dashboard shows component usage counts by category with filter and details table for Figma component library organization.

Practice

1. What is the main reason to organize components in a Figma library by type or function?

easy

A. To make it easier for users to find and reuse components quickly

B. To increase the file size of the library

C. To make components look more colorful

D. To prevent users from editing components

Solution

1. Step 1: Understand component organization purpose

   Organizing by type or function groups similar components together logically.

2. Step 2: Identify benefit for users

   This grouping helps users find components faster and reuse them efficiently.

3. Final Answer:

   To make it easier for users to find and reuse components quickly -> Option A

4. Quick Check:

   Organizing by type/function = easier reuse [OK]

Hint: Group similar components to find them faster [OK]

Common Mistakes:

• Thinking organization increases file size
• Believing organization changes component colors
• Assuming organization restricts editing

2. Which of the following is the correct way to name components in a Figma library for clarity?

easy

A. Component123

B. Btn1

C. Button/Primary/Default

D. MyComponent

Solution

1. Step 1: Review naming conventions

   Clear names use categories and states separated by slashes for easy browsing.

2. Step 2: Compare options

   Button/Primary/Default uses descriptive hierarchy, others are vague or unclear.

3. Final Answer:

   Button/Primary/Default -> Option C

4. Quick Check:

   Clear, consistent names = Button/Primary/Default [OK]

Hint: Use slashes to separate categories in names [OK]

Common Mistakes:

• Using short codes like Btn1
• Using generic names like Component123
• Using personal names like MyComponent

3. Given a Figma library with components named as Icon/Small/Active, Icon/Small/Inactive, and Icon/Large/Active, which component will appear first when sorted alphabetically?

medium

A. Icon/Large/Active

B. Icon/Small/Active

C. Icon/Small/Inactive

D. Icon/Active/Small

Solution

1. Step 1: Understand alphabetical sorting

   Sorting compares strings from left to right character by character.

2. Step 2: Compare component names

   "Icon/Large/Active" comes before "Icon/Small/Active" because "Large" starts with 'L' which is before 'S' in "Small".

3. Final Answer:

   Icon/Large/Active -> Option A

4. Quick Check:

   Alphabetical order = Icon/Large/Active first [OK]

Hint: Sort by first differing word alphabetically [OK]

Common Mistakes:

• Ignoring alphabetical order and picking Small first
• Confusing order of words in names
• Choosing a name not in the list

4. You notice your Figma component library is hard to browse because many components have inconsistent naming like BtnPrimary, button_secondary, and BTN-Tertiary. What is the best way to fix this?

medium

A. Delete all components and start over

B. Add random numbers to each component name

C. Leave names as they are to avoid confusion

D. Rename all components using a consistent naming pattern like Button/Primary

Solution

1. Step 1: Identify the problem

   Inconsistent naming makes browsing and finding components difficult.

2. Step 2: Apply consistent naming

   Renaming with a clear pattern like "Button/Primary" improves clarity and organization.

3. Final Answer:

   Rename all components using a consistent naming pattern like Button/Primary -> Option D

4. Quick Check:

   Consistent naming fixes browsing issues [OK]

Hint: Use one naming style for all components [OK]

Common Mistakes:

• Deleting components unnecessarily
• Keeping inconsistent names
• Adding confusing numbers

5. You are building a Figma component library for a large project with buttons, icons, and forms. How should you organize the library to keep it simple and easy to browse for your team?

hard

A. Put all components in one folder with random names

B. Create folders for each component type and use clear names like Button/Primary, Icon/Small, and Form/Input

C. Use only colors to differentiate components without naming

D. Create separate files for each component without naming conventions

Solution

1. Step 1: Organize by component type

   Grouping components by type (buttons, icons, forms) helps users find them easily.

2. Step 2: Use clear, consistent names

   Names like "Button/Primary" clearly describe the component and its purpose.

3. Step 3: Keep library simple and browsable

   Folders and naming reduce clutter and improve navigation for the team.

4. Final Answer:

   Create folders for each component type and use clear names like Button/Primary, Icon/Small, and Form/Input -> Option B

5. Quick Check:

   Folders + clear names = simple, easy browsing [OK]

Hint: Group by type and name clearly for easy browsing [OK]

Common Mistakes:

• Mixing all components without folders
• Using colors only without names
• Splitting components into many files without naming