Base component architecture in Figma - Step-by-Step Guide

Introduction

Base component architecture helps you create reusable building blocks in your design. It solves the problem of repeating the same elements many times by letting you update one main component that changes all copies.

When you want all buttons in your dashboard to have the same style and update together

When you need consistent icons across multiple report pages

When you want to create a standard card layout for data visuals that repeats

When you want to quickly change colors or fonts for many elements at once

When you want to keep your design organized and easy to update

Steps

Step 1: Select the element or group of elements to reuse

- Canvas

The elements are highlighted for editing

💡 Group related elements before creating a component

Step 2: Click Create component

- Top toolbar

The selected elements become a base component with a purple outline

Step 3: Drag instances of the base component onto other frames

- Assets panel

Copies of the component appear on the canvas linked to the base

Step 4: Edit the base component

- Canvas or Layers panel

All instances update automatically to reflect changes

Step 5: Use Variants to create different states or versions

- Properties panel when base component is selected

You can switch between versions in instances without creating new components

Before vs After

Before

Multiple buttons on different pages are separate elements with different styles

After

All buttons are instances of one base component; changing the base updates all buttons

Settings Reference

Create component

📍 Top toolbar

Turns selected elements into a reusable base component

Default: Create component

Variants

📍 Properties panel when component selected

Manage different versions or states of a base component

Default: No variants

Instance swapping

📍 Properties panel of an instance

Change the instance to a different component or variant without breaking the link

Default: Original base component

Common Mistakes

Editing an instance instead of the base component

Changes only affect that one instance, not all copies

Always edit the base component to update all instances

Not grouping elements before creating a component

Component may not behave as expected or parts may be missing

Group related elements first to keep them together in the component

Creating many similar components instead of using variants

Makes managing components harder and less efficient

Use variants to handle different states or versions within one component

Summary

Base component architecture creates reusable design blocks that update all copies when changed

Use it to keep styles consistent and save time updating repeated elements

Remember to edit the base component, group elements before creating, and use variants for versions

Practice

1. What is the main benefit of using a base component in Figma for Business Intelligence dashboards?

easy

A. It allows reusing design parts to save time and keep consistency.

B. It automatically generates data insights without manual input.

C. It creates new data sources for reports.

D. It replaces the need for calculated measures in reports.

Solution

1. Step 1: Understand base component purpose

   Base components are reusable design parts that help keep designs consistent.

2. Step 2: Connect to BI dashboard benefits

   Reusing parts saves time and ensures uniform look across reports.

3. Final Answer:

   It allows reusing design parts to save time and keep consistency. -> Option A

4. Quick Check:

   Base components = reuse + consistency [OK]

Hint: Think: base components save time by reusing parts [OK]

Common Mistakes:

• Confusing base components with data sources
• Thinking base components generate data
• Assuming base components replace calculations

2. Which syntax correctly describes creating an instance of a base component in Figma?

easy

A. Instance = BaseComponent.create()

B. Instance = BaseComponent.instantiate()

C. Instance = BaseComponent.clone()

D. Instance = new BaseComponent()

Solution

1. Step 1: Recall Figma instance creation method

   Figma uses instantiate() to create instances from base components.

2. Step 2: Compare options

   Only BaseComponent.instantiate() matches Figma's correct method.

3. Final Answer:

   Instance = BaseComponent.instantiate() -> Option B

4. Quick Check:

   Instance creation = instantiate() [OK]

Hint: Remember: 'instantiate' creates instances in Figma [OK]

Common Mistakes:

• Using 'new' keyword which is not Figma syntax
• Using 'create()' which is incorrect here
• Confusing 'clone()' with instance creation

3. Given a base component with a text label "Sales" and an instance where the label is overridden to "Revenue", what will happen if the base component's font size is changed from 12 to 14?

medium

A. The instance will break and lose all overrides.

B. The instance label font size remains 12 regardless of base changes.

C. The instance label text will revert to "Sales" automatically.

D. The instance label font size will update to 14 unless specifically overridden.

Solution

1. Step 1: Understand override behavior in instances

   Overrides apply only to changed properties; others inherit from base.

2. Step 2: Apply to font size change

   Since font size was not overridden, it updates to new base size 14.

3. Final Answer:

   The instance label font size will update to 14 unless specifically overridden. -> Option D

4. Quick Check:

   Overrides keep text but inherit font size [OK]

Hint: Overrides affect only changed properties; others update [OK]

Common Mistakes:

• Assuming all instance properties freeze after override
• Thinking text override resets on base change
• Believing instance breaks on base updates

4. You created a base component but when you update it, the instances do not reflect the changes. What is the most likely cause?

medium

A. Instances have local overrides blocking updates.

B. The base component was deleted accidentally.

C. You forgot to publish the updated base component.

D. Instances were created from a different base component.

Solution

1. Step 1: Check update propagation process

   In Figma, base component updates must be published to propagate to instances.

2. Step 2: Identify common mistake

   Not publishing changes is a frequent cause for instances not updating.

3. Final Answer:

   You forgot to publish the updated base component. -> Option C

4. Quick Check:

   Publish updates to sync instances [OK]

Hint: Always publish base updates to reflect in instances [OK]

Common Mistakes:

• Assuming local overrides block all updates
• Not checking if base component still exists
• Confusing base components with unrelated instances

5. You want to create a dashboard with multiple charts sharing the same style but different data. How should you use base components to achieve this efficiently?

hard

A. Create a base chart component with style, then create instances overriding only the data source.

B. Create separate full charts for each data set without base components.

C. Use base components only for text labels, not charts.

D. Duplicate charts manually and change styles individually.

Solution

1. Step 1: Identify reuse strategy for style and data

   Base components let you reuse style and override data per instance.

2. Step 2: Apply to dashboard charts

   Create one styled base chart, then override data source in each instance.

3. Final Answer:

   Create a base chart component with style, then create instances overriding only the data source. -> Option A

4. Quick Check:

   Base components reuse style, override data [OK]

Hint: Reuse style in base, override data per instance [OK]

Common Mistakes:

• Duplicating charts wastes time and breaks consistency
• Ignoring base components for complex visuals
• Overriding style instead of data in instances