Folder structure best practices in React - Cheat Sheet & Quick Revision

Recall & Review

beginner

Why is having a clear folder structure important in React projects?

A clear folder structure helps keep code organized, makes it easier to find files, and improves teamwork by making the project easier to understand.

beginner

What is a common way to organize components in a React project?

Group components by feature or purpose inside a components/ folder, with each component in its own folder containing its code, styles, and tests.

beginner

What folders are typically included at the root of a React project?

Common root-level folders include src/ for source code and public/ for static files. Inside src/, common folders include components/ for UI parts, hooks/ for custom hooks, and assets/ for images and styles.

intermediate

How should styles be organized in a React project?

Styles can be kept close to components, inside their folders, or in a shared styles/ folder for global styles. Using CSS modules or styled-components helps keep styles scoped and manageable.

intermediate

What is the benefit of grouping files by feature instead of by file type?

Grouping by feature keeps all related files together, making it easier to work on one part of the app without jumping between folders for components, styles, and tests.

Which folder usually contains reusable UI parts in a React project?

A assets/

B hooks/

C components/

D public/

The components/ folder holds reusable UI parts like buttons or cards.

Where should static files like images and icons be placed?

A public/

B hooks/

C src/

D components/

Static files are usually placed in the public/ folder to be served directly.

What is a good practice for organizing styles in React?

A Put all styles in one big CSS file

B Avoid using styles

C Write styles inline only

D Keep styles inside each component folder or use a shared styles/ folder

Keeping styles close to components or in a shared folder helps maintainability.

Why group files by feature instead of by file type?

A It keeps related files together for easier development

B It makes the project look bigger

C It hides files from other developers

D It reduces the number of folders

Grouping by feature keeps all related files together, simplifying work on that feature.

Which folder is best for custom React hooks?

A components/

B hooks/

C assets/

D public/

Custom hooks are usually placed in a hooks/ folder for clarity.

Describe a simple folder structure for a React project and explain why it helps.

Think about where you put components, styles, and images.

Explain the benefits of grouping React project files by feature instead of by file type.

Imagine working on one part of an app and finding everything in one place.

Practice

1. What is the main reason to organize React files into folders like components, pages, and hooks?

easy

A. To make the app run faster

B. To reduce the file size of the app

C. To keep the project easy to understand and maintain

D. To avoid using React hooks

Solution

1. Step 1: Understand folder organization purpose

   Folders like components and hooks group related files by their role.

2. Step 2: Recognize benefits of clear structure

   This grouping makes the project easier to read and maintain for developers.

3. Final Answer:

   To keep the project easy to understand and maintain -> Option C

4. Quick Check:

   Folder organization = easier maintenance [OK]

Hint: Folders group related files for clarity and ease [OK]

Common Mistakes:

• Thinking folder structure affects app speed
• Confusing file size with organization
• Believing hooks folder is optional for React hooks

2. Which of the following is the correct way to organize a React project folder for components?

easy

A. Put all components in a single components folder

B. Scatter components randomly in the root folder

C. Put components inside the public folder

D. Put components inside the node_modules folder

Solution

1. Step 1: Identify standard folder for components

   React projects usually keep components in a dedicated components folder.

2. Step 2: Avoid incorrect placements

   Components should not be in public or node_modules folders, which serve other purposes.

3. Final Answer:

   Put all components in a single components folder -> Option A

4. Quick Check:

   Components folder = centralized components [OK]

Hint: Keep components together in one folder [OK]

Common Mistakes:

• Placing components in public folder
• Scattering components without structure
• Modifying node_modules folder

3. Given this folder structure:

src/
  components/
    Button.jsx
  hooks/
    useToggle.js
  pages/
    Home.jsx

Which file would you expect to find the custom React hook?

medium

A. src/components/Button.jsx

B. src/pages/Home.jsx

C. src/index.js

D. src/hooks/useToggle.js

Solution

1. Step 1: Understand folder naming conventions

   Custom hooks are usually placed in the hooks folder.

2. Step 2: Match file to folder purpose

   The file useToggle.js inside hooks matches the custom hook naming pattern.

3. Final Answer:

   src/hooks/useToggle.js -> Option D

4. Quick Check:

   Custom hooks in hooks folder = useToggle.js [OK]

Hint: Hooks go in the hooks folder [OK]

Common Mistakes:

• Looking for hooks in components folder
• Confusing pages folder with hooks
• Assuming index.js contains hooks

4. You see this folder structure in a React project:

src/
  components/
    Header.jsx
  utils/
    helpers.js
  Header.jsx

What is the main problem here?

medium

A. Having a utils folder is not recommended

B. Duplicate Header.jsx file in root and components folder causes confusion

C. Components should be inside utils folder

D. Files should not have .jsx extension

Solution

1. Step 1: Identify duplicate file names

   There are two Header.jsx files: one in components and one in root.

2. Step 2: Understand confusion caused by duplicates

   This duplication can confuse developers and cause import errors.

3. Final Answer:

   Duplicate Header.jsx file in root and components folder causes confusion -> Option B

4. Quick Check:

   Duplicate filenames = confusion [OK]

Hint: Avoid duplicate filenames in different folders [OK]

Common Mistakes:

• Thinking utils folder is bad practice
• Believing components belong in utils
• Ignoring file extensions importance

5. You are building a large React app. Which folder structure best supports growth and easy maintenance?

hard

A. Organize by feature: each feature folder contains components, hooks, and styles

B. Put all files in one big folder to avoid complexity

C. Separate files only by file type, ignoring features

D. Keep all components and hooks mixed in the root folder

Solution

1. Step 1: Understand feature-based organization

   Grouping by feature means each feature folder holds all related files, making it easier to find and update.

2. Step 2: Compare with other structures

   Flat or type-only folders become hard to manage as app grows, causing confusion.

3. Final Answer:

   Organize by feature: each feature folder contains components, hooks, and styles -> Option A

4. Quick Check:

   Feature folders = scalable and maintainable [OK]

Hint: Group by feature for scalable projects [OK]

Common Mistakes:

• Using one big folder causes clutter
• Separating only by file type slows feature updates
• Mixing all files in root is confusing