Base component architecture in Figma - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is a base component in design systems?

A base component is a simple, reusable building block in a design system. It provides core styles and structure that other components can extend or customize.

beginner

Why use base components in Figma?

Using base components helps keep designs consistent, speeds up work by reusing elements, and makes updates easier because changes to the base reflect everywhere.

intermediate

How do base components relate to variants in Figma?

Base components can have variants to show different states or versions (like colors or sizes). Variants keep related designs organized under one component.

intermediate

What is the benefit of nesting base components?

Nesting base components means placing one inside another. This helps build complex components from simple parts, making design easier to manage and update.

beginner

How does base component architecture improve collaboration?

It creates a shared language and consistent elements for teams. Everyone uses the same base components, reducing confusion and speeding up feedback and changes.

What is the main purpose of a base component in Figma?

A To create animations

B To store images only

C To export files

D To serve as a reusable building block for other components

Base components are reusable building blocks that other components can extend or customize.

Which feature helps organize different states of a base component?

A Frames

B Layers

C Variants

D Prototypes

Variants allow you to group different states or versions of a component under one base component.

What does nesting base components allow you to do?

A Change file formats

B Build complex components from simple parts

C Add animations

D Export to PDF

Nesting lets you combine simple base components to create more complex designs.

How does using base components affect design consistency?

A It improves consistency across designs

B It makes designs more random

C It slows down the design process

D It removes colors

Base components ensure consistent styles and structure across all designs.

Why is base component architecture helpful for team collaboration?

A It creates a shared design language and reduces confusion

B It hides design changes from the team

C It limits access to files

D It removes comments

Using base components helps teams work together smoothly by sharing consistent elements.

Explain what a base component is and why it is important in Figma design systems.

Think about how simple building blocks help create bigger designs.

Describe how nesting base components can help manage complex designs.

Imagine stacking Lego blocks to build a bigger model.

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