File organization best practices in Figma - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to name the main folder correctly for a BI project.

Figma

Project files should be stored in the [1] folder.

Drag options to blanks, or click blank then click option'

AReports

BDashboard

CData Sources

DProject

Attempts:

3 left

💡 Hint

Common Mistakes

Choosing a subfolder name instead of the main project folder.

The main folder should be named Project to keep all BI files organized in one place.

2fill in blank

medium

Complete the code to organize files by type inside the project folder.

Figma

Inside the project folder, create subfolders named [1] to separate files by their purpose.

Drag options to blanks, or click blank then click option'

AImages, Videos, Audio

BRaw, Processed, Final

CData, Visuals, Scripts

DInput, Output, Logs

Attempts:

3 left

💡 Hint

Common Mistakes

Choosing unrelated file types like media files.

Common BI file types are data files, visuals (like dashboards), and scripts (for calculations).

3fill in blank

hard

Fix the error in the naming convention for version control.

Figma

File names should include the version number like [1] to track changes.

Drag options to blanks, or click blank then click option'

Av1.0

Bfinal_version

Cversion1

Dv1_final

Attempts:

3 left

💡 Hint

Common Mistakes

Using vague or inconsistent version names.

Using a clear version format like v1.0 helps track file updates easily.

4fill in blank

hard

Fill both blanks to create a clear file naming pattern for reports.

Figma

Report files should be named as [1]_[2]_v1.0 to include project and date.

Drag options to blanks, or click blank then click option'

AProjectName

BDate

CUser

DVersion

Attempts:

3 left

💡 Hint

Common Mistakes

Using user or version instead of date in the file name.

Including the project name and date in the file name helps identify the report easily.

5fill in blank

hard

Fill all three blanks to organize BI files with folder, subfolder, and naming convention.

Figma

Store files in [1]/[2] with names like [3]_v1.0 for clarity.

Drag options to blanks, or click blank then click option'

AProject

BData

CProjectName

DScripts

Attempts:

3 left

💡 Hint

Common Mistakes

Mixing folder and file name roles.

Files go inside the project folder, then the data subfolder, and are named with the project name and version.

Practice

1. Why is it important to use clear folder names when organizing files in Figma?

easy

A. It helps everyone quickly find and understand the content inside folders.

B. It makes the file size smaller.

C. It automatically creates backups of the files.

D. It changes the colors of the designs inside the folder.

Solution

1. Step 1: Understand folder naming purpose

   Clear folder names describe the content, making it easy to find files.

2. Step 2: Consider collaboration benefits

   When working with others, clear names reduce confusion and save time.

3. Final Answer:

   It helps everyone quickly find and understand the content inside folders. -> Option A

4. Quick Check:

   Clear folder names = easy file finding [OK]

Hint: Think about how you'd find a file fast [OK]

Common Mistakes:

• Confusing folder names with file size
• Assuming naming changes design colors
• Believing naming creates backups

2. Which of the following is the correct way to name version files consistently in Figma?

easy

A. ProjectFinal, ProjectFinal2, ProjectFinal3

B. Project1, ProjectFinal, ProjectLast

C. Project, Project copy, Project copy 2

D. Project_v1, Project_v2, Project_v3

Solution

1. Step 1: Identify consistent version naming

   Using a clear pattern like _v1, _v2 helps track versions easily.

2. Step 2: Compare options for clarity

   The other options use inconsistent or unclear naming that can confuse users.

3. Final Answer:

   Project_v1, Project_v2, Project_v3 -> Option D

4. Quick Check:

   Consistent version names = Project_v1, Project_v2, Project_v3 [OK]

Hint: Use numbers with a clear prefix for versions [OK]

Common Mistakes:

• Using vague names like 'Final' or 'copy'
• Skipping version numbers
• Mixing naming styles

3. Given these folders in a Figma project: Data_Assets, Designs, Data_Assets_Backup, which folder best follows the best practice of separating content types?

medium

A. Data_Assets and Designs are correctly separated.

B. All folders are mixed and unclear.

C. Data_Assets_Backup should be merged with Designs.

D. Designs should be renamed to Data_Assets.

Solution

1. Step 1: Identify folder content types

   Data_Assets holds data files, Designs holds design files, so they are separated by type.

2. Step 2: Evaluate backup folder role

   Data_Assets_Backup is a backup folder, separate but related to Data_Assets, which is acceptable.

3. Final Answer:

   Data_Assets and Designs are correctly separated. -> Option A

4. Quick Check:

   Separate content types = Data_Assets and Designs are correctly separated. [OK]

Hint: Group files by type, not randomly [OK]

Common Mistakes:

• Mixing backup with main folders
• Renaming folders incorrectly
• Merging unrelated content

4. You notice your Figma project folders have inconsistent naming like DesignsFinal, designs_v2, and Designs Copy. What is the best way to fix this?

medium

A. Merge all folders into one called Designs without versions.

B. Delete all folders and start fresh without naming.

C. Rename all folders to a consistent style like Designs_v1, Designs_v2, Designs_v3.

D. Keep the names as they are because renaming is risky.

Solution

1. Step 1: Identify the problem with inconsistent names

   Inconsistent names cause confusion and make tracking versions hard.

2. Step 2: Apply consistent naming conventions

   Renaming folders with a clear pattern like Designs_v1 helps organize versions and clarity.

3. Final Answer:

   Rename all folders to a consistent style like Designs_v1, Designs_v2, Designs_v3. -> Option C

4. Quick Check:

   Consistent naming fixes confusion = Rename all folders to a consistent style like Designs_v1, Designs_v2, Designs_v3. [OK]

Hint: Standardize names before adding new versions [OK]

Common Mistakes:

• Deleting folders unnecessarily
• Ignoring inconsistent names
• Merging versions without tracking

5. You have a Figma project with multiple teams working on data, designs, and assets. How should you organize the files to ensure smooth collaboration and easy updates?

hard

A. Name folders by team member names and mix file types inside.

B. Create separate folders named Data, Designs, and Assets, use consistent version naming, and document folder purpose.

C. Put all files in one folder and rely on search to find them.

D. Use random folder names and update files without version control.

Solution

1. Step 1: Separate files by content type

   Organizing by Data, Designs, and Assets keeps files clear and accessible.

2. Step 2: Use consistent version naming and documentation

   Consistent naming helps track changes; documentation explains folder use to all teams.

3. Final Answer:

   Create separate folders named Data, Designs, and Assets, use consistent version naming, and document folder purpose. -> Option B

4. Quick Check:

   Clear folders + naming + docs = Create separate folders named Data, Designs, and Assets, use consistent version naming, and document folder purpose. [OK]

Hint: Separate by type, name versions, add notes [OK]

Common Mistakes:

• Mixing file types in one folder
• Ignoring version control
• Not documenting folder use