Why Project structure overview in NextJS? - Purpose & Use Cases

The Big Idea

Discover how a simple folder setup can save you hours of frustration!

The Scenario

Imagine building a website by placing all your files in one big folder without any order. You have HTML, CSS, images, and scripts all mixed up. When you want to fix a bug or add a feature, you spend a lot of time searching for the right file.

The Problem

This messy approach makes your project confusing and hard to maintain. It's easy to make mistakes, like editing the wrong file or breaking something by accident. As your project grows, it becomes a nightmare to manage.

The Solution

Next.js provides a clear project structure that organizes your files by purpose. It separates pages, components, styles, and public assets into folders. This helps you find and update code quickly and keeps your project clean and scalable.

Before vs After

✗ Before

index.html, style.css, script.js all in one folder

✓ After

pages/index.tsx, components/Header.tsx, styles/global.css, public/logo.png

What It Enables

With a well-organized project structure, you can build bigger apps faster and collaborate easily with others.

Real Life Example

Think of it like organizing your desk: having separate drawers for pens, papers, and tools saves time and reduces stress when working on a project.

Key Takeaways

Messy file placement slows development and causes errors.

Next.js project structure organizes files by role and purpose.

This makes your code easier to find, update, and scale.

Practice

1. What is the main purpose of the app/ folder in a Next.js project?

easy

A. To organize pages, layouts, and API routes

B. To store static files like images and fonts

C. To hold configuration files like next.config.js

D. To keep test files and mocks

Solution

1. Step 1: Understand the role of app/ folder

   The app/ folder is designed to organize the main parts of the app such as pages, layouts, and API routes.

2. Step 2: Compare with other folders

   The public/ folder holds static files, and config files are outside app/. So, app/ is for app structure.

3. Final Answer:

   To organize pages, layouts, and API routes -> Option A

4. Quick Check:

   app/ folder = organize pages/layouts/API [OK]

Hint: Remember: app/ is your app's main structure folder [OK]

Common Mistakes:

• Confusing app/ with public/
• Thinking config files go inside app/
• Assuming app/ holds only pages, ignoring layouts and APIs

2. Which folder should you place an image file in a Next.js project to serve it statically?

easy

A. app/

B. api/

C. components/

D. public/

Solution

1. Step 1: Identify static file storage

   Static files like images should be placed in the public/ folder so they can be served directly.

2. Step 2: Exclude other folders

   app/ is for pages/layouts, components/ is for React components, and api/ is for backend routes, so none are for static files.

3. Final Answer:

   public/ -> Option D

4. Quick Check:

   Static files = public/ folder [OK]

Hint: Static files go in public/ folder, not app/ [OK]

Common Mistakes:

• Putting images inside app/ folder
• Confusing components/ with static file storage
• Trying to serve images from api/ folder

3. Given this Next.js project structure:

app/
  layout.js
  page.js
public/
  logo.png

Which statement is true about accessing logo.png in the browser?

medium

A. You can access it at /logo.png

B. You must import it in page.js to use it

C. It is not accessible because it's inside public/

D. You can access it at /app/logo.png

Solution

1. Step 1: Understand public/ folder behavior

   Files in public/ are served at the root URL path, so logo.png is accessible at /logo.png.

2. Step 2: Check other options

   Importing is optional for static files; app/ folder files are not served as static assets, so /app/logo.png is invalid.

3. Final Answer:

   You can access it at /logo.png -> Option A

4. Quick Check:

   public/ files = root URL access [OK]

Hint: Static files in public/ map to root URL path [OK]

Common Mistakes:

• Thinking you must import static files to access them
• Trying to access static files via /app/ path
• Assuming public/ files are not accessible

4. You see this error in your Next.js app: "Module not found: Can't resolve './logo.png'". Your project has logo.png inside public/. What is the likely cause?

medium

A. You placed logo.png inside app/ instead of public/

B. You tried to import logo.png from public/ using a relative path

C. The logo.png file is missing from public/

D. Next.js does not support PNG images

Solution

1. Step 1: Understand how to use files in public/

   Files in public/ are accessed via URL paths, not imported with relative paths in code.

2. Step 2: Identify the error cause

   Trying to import logo.png with a relative path causes "Module not found" error because public/ files are not part of the module system.

3. Final Answer:

   You tried to import logo.png from public/ using a relative path -> Option B

4. Quick Check:

   Importing public/ files = error [OK]

Hint: Don't import public/ files; use URL paths instead [OK]

Common Mistakes:

• Importing static files from public/ folder
• Assuming public/ files are part of module imports
• Thinking Next.js can't serve PNG images

5. You want to create a new page with a custom layout in your Next.js app. Where should you place the layout and page files to follow the recommended project structure?

hard

A. Place both files inside components/ folder

B. Put layout.js in public/ and page.js in app/

C. Place both layout.js and page.js inside a new folder under app/

D. Put page.js in app/ and layout.js in api/

Solution

1. Step 1: Recall Next.js app folder structure

   In Next.js, pages and their layouts are organized inside folders under app/ to group related files.

2. Step 2: Exclude incorrect placements

   public/ is for static files, components/ is for reusable UI parts, and api/ is for backend routes, so these are not correct for layouts/pages.

3. Final Answer:

   Place both layout.js and page.js inside a new folder under app/ -> Option C

4. Quick Check:

   Layouts and pages live together under app/ [OK]

Hint: Keep layouts and pages together inside app/ folders [OK]

Common Mistakes:

• Putting layouts in public/ or api/
• Separating layout and page files into unrelated folders
• Confusing components/ with page structure