Style organization and naming conventions in Figma - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

Why use consistent style naming in BI dashboards?

Imagine you are designing a BI dashboard with many charts and tables. Why is it important to use consistent style names for colors, fonts, and spacing?

A It makes the dashboard load faster in the browser.

B It helps everyone understand and update the dashboard easily.

C It automatically improves the data accuracy.

D It reduces the number of charts needed.

💡 Hint

Think about teamwork and future changes.

Consistent style naming helps team members quickly find and update styles, keeping the dashboard uniform and easier to maintain.

❓ data_modeling

intermediate

Organizing color styles for a sales dashboard

You have three main categories: Revenue, Costs, and Profit. How should you organize color styles in Figma for these categories to keep your BI dashboard clear and scalable?

A Create color styles only for Revenue and ignore others.

B Use random colors for each chart without naming.

C Use one color style for all categories.

D Create separate color styles named Revenue/Primary, Costs/Primary, Profit/Primary.

💡 Hint

Think about clarity and future additions.

Organizing color styles by category with clear names helps keep the dashboard consistent and easy to update when new categories appear.

❓ visualization

advanced

Best practice for naming text styles in BI reports

Which naming convention below best supports accessibility and easy updates for text styles in BI reports?

A TextA, TextB, TextC

B Style1, Style2, Style3

C Heading/Large/Bold, Body/Medium/Regular, Caption/Small/Italic

D BigText, NormalText, SmallText

💡 Hint

Think about what information the name gives you.

Using descriptive names with role, size, and weight helps users understand and apply text styles consistently and supports accessibility.

🔧 Formula Fix

advanced

Identify the problem in this style naming approach

A BI team uses these color style names: 'Blue1', 'Blue2', 'Blue3' for different revenue charts. What is the main issue with this naming?

A The names do not describe the purpose or usage of the colors.

B The colors are not blue enough.

C The names use numbers which is not allowed in Figma.

D The names are too long and complex.

💡 Hint

Think about how easy it is to know what each color means.

Using generic names like 'Blue1' does not tell users what the color is for, making it hard to maintain and causing confusion.

🎯 Scenario

expert

Designing a scalable style system for a multi-dashboard BI project

You are leading a BI project with multiple dashboards for different departments. How should you organize and name your styles in Figma to ensure easy updates and consistency across all dashboards?

A Create a shared style library with clear category-based names and version control.

B Create separate style sets for each dashboard with no shared naming.

C Use default Figma styles without renaming or organizing.

D Create styles only for the first dashboard and copy them manually to others.

💡 Hint

Think about teamwork, updates, and consistency.

A shared style library with clear names and version control allows all dashboards to stay consistent and makes updates efficient across the project.

Practice

1. Why is it important to use clear and consistent naming conventions for styles in Figma?

easy

A. It changes the colors of the styles.

B. It makes the file size smaller.

C. It automatically fixes design errors.

D. It helps find and reuse styles quickly, saving time and keeping designs consistent.

Solution

1. Step 1: Understand the purpose of naming conventions

   Clear and consistent names help users quickly identify and reuse styles without confusion.

2. Step 2: Connect naming to design consistency

   Using good names ensures styles are reused properly, keeping the design uniform across the project.

3. Final Answer:

   It helps find and reuse styles quickly, saving time and keeping designs consistent. -> Option D

4. Quick Check:

   Clear naming = easy reuse [OK]

Hint: Good names save time and keep designs uniform [OK]

Common Mistakes:

• Thinking naming affects file size
• Believing naming fixes design errors
• Assuming naming changes style colors

2. Which of the following is the correct way to organize styles using categories and subcategories in Figma?

easy

A. Button-Primary-Active

B. Button/Primary/Active

C. Button Primary Active

D. Button.Primary.Active

Solution

1. Step 1: Identify the correct separator for categories

   Figma uses slashes (/) to separate categories and subcategories in style names.

2. Step 2: Compare options with Figma naming rules

   Only Button/Primary/Active uses slashes correctly to organize styles hierarchically.

3. Final Answer:

   Button/Primary/Active -> Option B

4. Quick Check:

   Use slashes (/) for style categories [OK]

Hint: Use slashes (/) to separate style categories [OK]

Common Mistakes:

• Using dashes or dots instead of slashes
• Using spaces without separators
• Mixing separators inconsistently

3. Given these style names in Figma: Text/Heading/H1, Text/Heading/H2, Button/Primary/Default, which style will appear first in the style list when sorted alphabetically?

medium

A. Button/Primary/Default

B. Text/Heading/H1

C. Text/Heading/H2

D. They all appear at the same time

Solution

1. Step 1: Understand alphabetical sorting in Figma

   Styles are sorted alphabetically from left to right, starting with the first category.

2. Step 2: Compare the first parts of each style name

   "Button" comes before "Text" alphabetically, so any style starting with "Button" appears before "Text" styles.

3. Final Answer:

   Button/Primary/Default -> Option A

4. Quick Check:

   Alphabetical order starts with first word [OK]

Hint: Alphabetical order sorts by first word first [OK]

Common Mistakes:

• Assuming H1 comes before Button
• Thinking subcategories affect order first
• Believing all styles appear simultaneously

4. You notice your Figma styles are named inconsistently: some use spaces, others use slashes, and some use dashes. What is the best way to fix this?

medium

A. Rename all styles to use slashes consistently for categories and subcategories.

B. Leave them as is because Figma accepts all formats.

C. Use spaces only because they look cleaner.

D. Use dashes only because they are shorter.

Solution

1. Step 1: Identify the recommended naming convention

   Figma recommends using slashes (/) to organize styles into categories and subcategories clearly.

2. Step 2: Apply consistent naming across all styles

   Renaming all styles to use slashes ensures easy navigation and reuse, avoiding confusion.

3. Final Answer:

   Rename all styles to use slashes consistently for categories and subcategories. -> Option A

4. Quick Check:

   Consistent slashes improve style organization [OK]

Hint: Fix inconsistent names by using slashes everywhere [OK]

Common Mistakes:

• Ignoring inconsistent naming
• Using spaces or dashes inconsistently
• Thinking Figma accepts all naming equally

5. You have these styles in Figma: Color/Primary/Light, Color/Primary/Dark, Color/Secondary/Light, Color/Secondary/Dark. You want to create a new style for a medium shade between light and dark for Primary colors only. What is the best naming convention to keep your styles organized?

hard

A. Primary/Color/Medium

B. Color/PrimaryMedium

C. Color/Primary/Medium

D. Color-Medium-Primary

Solution

1. Step 1: Follow existing naming pattern

   Current styles use the pattern Category/Subcategory/Variant with slashes.

2. Step 2: Insert new variant in the same subcategory

   Adding "Medium" as a variant under "Primary" keeps the naming consistent and organized.

3. Final Answer:

   Color/Primary/Medium -> Option C

4. Quick Check:

   Match existing pattern for new styles [OK]

Hint: Match existing slash pattern for new style names [OK]

Common Mistakes:

• Combining words without slashes
• Changing category order
• Using dashes instead of slashes