File and project organization in Figma - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to create a new Figma file named 'Dashboard'.

Figma

figma.[1]('Dashboard')

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

AopenFile

BcreateFile

CdeleteFile

DsaveFile

Attempts:

3 left

💡 Hint

Common Mistakes

Using openFile instead of createFile

Trying to delete before creating

Use createFile to start a new Figma file.

2fill in blank

medium

Complete the code to add a new page named 'Sales Data' to the current Figma project.

Figma

currentFile.[1]('Sales Data')

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

AduplicatePage

BremovePage

CrenamePage

DaddPage

Attempts:

3 left

💡 Hint

Common Mistakes

Using removePage which deletes a page

Trying to rename before adding

The addPage method adds a new page to your Figma file.

3fill in blank

hard

Fix the error in the code to rename a page to 'Q1 Report'.

Figma

page.[1] = 'Q1 Report'

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

Aname

Blabel

Ctitle

Did

Attempts:

3 left

💡 Hint

Common Mistakes

Using title or label instead of name

Trying to change the id which is fixed

The page's name property is used to rename it.

4fill in blank

hard

Fill both blanks to move a frame named 'Chart' to the page named 'Summary'.

Figma

frame.[1] = pages.[2]

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

Aparent

Bchildren

Cname

Did

Attempts:

3 left

💡 Hint

Common Mistakes

Using children which is a list

Using name which is not a direct reference

Set the frame's parent to the page with the correct id.

5fill in blank

hard

Fill all three blanks to export a frame named 'Summary Chart' as a PNG file.

Figma

frame = currentPage.[1]('Summary Chart')
exportSettings = { 'format': '[2]' }
frame.[3](exportSettings)

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

AfindChild

BPNG

CexportAsync

DgetChild

Attempts:

3 left

💡 Hint

Common Mistakes

Using findChild which is not a Figma method

Wrong export method name

Wrong format string

Use getChild to find the frame, set format to PNG, and call exportAsync to export.

Practice

1. Why is it important to organize Figma files into folders within a project?

easy

A. To hide files from team members

B. To increase the file size

C. To make files load slower

D. To find and manage files easily later

Solution

1. Step 1: Understand folder purpose in Figma

   Folders group related files so you can find them quickly without searching everywhere.

2. Step 2: Consider file management benefits

   Organized folders reduce confusion and save time when working on projects.

3. Final Answer:

   To find and manage files easily later -> Option D

4. Quick Check:

   Organizing files = Easy access [OK]

Hint: Folders help you find files fast, like folders on your computer [OK]

Common Mistakes:

• Thinking folders slow down Figma
• Believing folders hide files from others
• Confusing folders with file size changes

2. Which of the following is the correct way to name Figma files for version control?

easy

A. ProjectName_v1, ProjectName_v2, ProjectName_final

B. FinalProject, FinalProject2, FinalProject3

C. MyFile, MyFileCopy, MyFileCopy2

D. Design1, Design2, Design3

Solution

1. Step 1: Identify clear version naming

   Using _v1, _v2, etc., clearly shows file versions in order.

2. Step 2: Compare other options

   Other names like 'FinalProject' or 'Copy' are vague and confusing for version tracking.

3. Final Answer:

   ProjectName_v1, ProjectName_v2, ProjectName_final -> Option A

4. Quick Check:

   Consistent version names = ProjectName_v1, ProjectName_v2, ProjectName_final [OK]

Hint: Use _v1, _v2 to track versions clearly [OK]

Common Mistakes:

• Using vague names like 'Copy' or 'Final'
• Skipping version numbers
• Mixing unrelated file names

3. Given a Figma project with folders named 'Assets', 'Designs', and 'Docs', where should you place a new icon file and why?

medium

A. In 'Docs' because icons need documentation

B. In 'Designs' because icons are part of the design files

C. In 'Assets' because icons are reusable elements

D. In the root project folder to keep it simple

Solution

1. Step 1: Understand folder roles

   'Assets' holds reusable elements like icons; 'Designs' holds working design files; 'Docs' holds documentation.

2. Step 2: Match icon file to folder

   Icons are reusable assets, so they belong in 'Assets' for easy reuse across projects.

3. Final Answer:

   In 'Assets' because icons are reusable elements -> Option C

4. Quick Check:

   Reusable elements go in Assets [OK]

Hint: Put reusable items like icons in Assets folder [OK]

Common Mistakes:

• Putting icons in Docs folder
• Mixing assets with design files
• Leaving files in root folder

4. You notice your Figma project has files named inconsistently like 'DesignFinal', 'design_v2', and 'Design copy'. What is the best way to fix this?

medium

A. Rename files using a consistent pattern like ProjectName_v1, ProjectName_v2

B. Delete all files and start over

C. Leave files as they are to avoid confusion

D. Merge all files into one big file

Solution

1. Step 1: Identify problem with inconsistent naming

   Inconsistent names make it hard to track versions and progress.

2. Step 2: Apply consistent naming convention

   Renaming files with a clear pattern like ProjectName_v1 helps organize and find files easily.

3. Final Answer:

   Rename files using a consistent pattern like ProjectName_v1, ProjectName_v2 -> Option A

4. Quick Check:

   Consistent naming fixes confusion [OK]

Hint: Rename files with clear version numbers [OK]

Common Mistakes:

• Deleting files unnecessarily
• Ignoring inconsistent names
• Merging unrelated files

5. You manage a large Figma project with multiple teams. How should you organize files and folders to keep work clear and efficient?

hard

A. Put all files in one folder and name them randomly

B. Create separate folders for each team, use consistent file naming, and keep assets in a shared 'Assets' folder

C. Create folders only for assets and put all design files together without folders

D. Use different projects for each file instead of folders

Solution

1. Step 1: Organize by team folders

   Separate folders for each team help keep their work isolated and easy to find.

2. Step 2: Use consistent naming and shared assets

   Consistent file names avoid confusion; a shared 'Assets' folder allows reuse across teams.

3. Final Answer:

   Create separate folders for each team, use consistent file naming, and keep assets in a shared 'Assets' folder -> Option B

4. Quick Check:

   Team folders + consistent names + shared assets = Create separate folders for each team, use consistent file naming, and keep assets in a shared 'Assets' folder [OK]

Hint: Separate by team, name files clearly, share assets [OK]

Common Mistakes:

• Mixing all files in one folder
• Ignoring naming conventions
• Scattering assets across folders