Component organization in React

Introduction

Organizing components helps keep your React app clean and easy to understand. It makes finding and fixing parts faster.

When your app grows and has many parts to manage

When you want to reuse parts in different places

When working with others on the same project

When you want to keep your code neat and easy to read

Syntax

React

src/
  components/
    Header.jsx
    Footer.jsx
    Button.jsx
  pages/
    Home.jsx
    About.jsx
  App.jsx

Keep components in folders by their role or feature.

Name files with the component name and .jsx extension.

Examples

A simple reusable button component.

React

// Button.jsx
export function Button() {
  return <button>Click me</button>;
}

Header uses the Button component inside it.

React

// Header.jsx
import { Button } from './Button';

export function Header() {
  return <header><h1>Welcome</h1><Button /></header>;
}

Main app combines Header, main content, and Footer components.

React

// App.jsx
import { Header } from './components/Header';
import { Footer } from './components/Footer';

export function App() {
  return (
    <>
      <Header />
      <main>Main content here</main>
      <Footer />
    </>
  );
}

Sample Program

This example shows a simple React app with components organized by their role. The App component uses Header and Footer. The Header uses the Button component. This keeps code easy to find and reuse.

React

import React from 'react';

// Button.jsx
export function Button() {
  return <button aria-label="Click me button">Click me</button>;
}

// Header.jsx
import { Button } from './Button';
export function Header() {
  return (
    <header>
      <h1>Welcome to my site</h1>
      <Button />
    </header>
  );
}

// Footer.jsx
export function Footer() {
  return <footer>© 2024 My Site</footer>;
}

// App.jsx
import { Header } from './components/Header';
import { Footer } from './components/Footer';

export function App() {
  return (
    <>
      <Header />
      <main>
        <p>This is the main content area.</p>
      </main>
      <Footer />
    </>
  );
}

Important Notes

Use folders to group related components for better clarity.

Keep components small and focused on one job.

Use clear, descriptive names for files and components.

Summary

Organize components by their role or feature to keep code clean.

Small, reusable components make your app easier to build and maintain.

Good organization helps teamwork and future updates.

Practice

1. What is the main benefit of organizing React components by their role or feature?

easy

A. It makes the app run faster

B. It automatically fixes bugs in the code

C. It reduces the size of the final app bundle

D. It keeps the code clean and easier to maintain

Solution

1. Step 1: Understand component organization purpose

   Organizing components by role or feature helps keep the codebase structured and clean.

2. Step 2: Identify the main benefit

   This organization makes the code easier to read, maintain, and update over time.

3. Final Answer:

   It keeps the code clean and easier to maintain -> Option D

4. Quick Check:

   Clean code = B [OK]

Hint: Think about code clarity and maintenance benefits [OK]

Common Mistakes:

• Confusing organization with app speed
• Assuming organization reduces bundle size
• Believing organization fixes bugs automatically

2. Which of the following is the correct way to define a simple functional React component named Button?

easy

A. function Button() { return Click me; }

B. class Button extends React.Component { render() { return Click me; } }

C. const Button = () => { Click me }

D. function Button() { Click me }

Solution

1. Step 1: Check functional component syntax

   A functional component returns JSX inside the function body using return statement.

2. Step 2: Identify correct syntax

   function Button() { return Click me; } correctly defines a function returning JSX. const Button = () => { Click me } misses return. class Button extends React.Component { render() { return Click me; } } is a class component, not functional.

3. Final Answer:

   function Button() { return <button>Click me</button>; } -> Option A

4. Quick Check:

   Functional component needs return [OK]

Hint: Functional components must return JSX explicitly [OK]

Common Mistakes:

• Omitting return statement in arrow functions
• Confusing class and functional component syntax
• Not returning JSX from the function

3. Given the code below, what will be rendered on the screen?

function Greeting({ name }) {
  return <h1>Hello, {name}!</h1>;
}

function App() {
  return <Greeting name="Alice" />;
}

medium

A. Error: name is undefined

B. Hello, name!

C. Hello, Alice!

D.

Solution

1. Step 1: Understand props usage in Greeting

   The Greeting component receives a prop called name and uses it inside JSX to display a greeting.

2. Step 2: Check how App uses Greeting

   App passes the string "Alice" as the name prop, so Greeting renders <h1>Hello, Alice!</h1>.

3. Final Answer:

   <h1>Hello, Alice!</h1> -> Option C

4. Quick Check:

   Props passed correctly = C [OK]

Hint: Props replace placeholders with actual values [OK]

Common Mistakes:

• Thinking props are not passed automatically
• Expecting literal 'name' string instead of value
• Confusing JSX tags with strings

4. Identify the error in this React component organization:

function Header() {
  return <header>Welcome</header>;
}

function App() {
  return (
    <div>
      <Header />
      <Footer />
    </div>
  );
}

medium

A. Footer component is used but not defined or imported

B. Header component should be a class component

C. App component must return a single element without div

D. Header component should not use semantic tags

Solution

1. Step 1: Check component usage in App

   App uses <Header /> and <Footer /> components inside a div.

2. Step 2: Verify component definitions

   Header is defined, but Footer is neither defined nor imported, causing an error.

3. Final Answer:

   Footer component is used but not defined or imported -> Option A

4. Quick Check:

   Undefined component usage = A [OK]

Hint: All used components must be defined or imported [OK]

Common Mistakes:

• Assuming class components are required
• Thinking multiple elements need no wrapper
• Believing semantic tags cause errors

5. You want to organize a React app with a main Dashboard component that uses smaller components like Sidebar, Content, and Footer. Which approach best follows good component organization?

hard

A. Put all JSX for Sidebar, Content, and Footer inside Dashboard's single file

B. Create separate files for Sidebar, Content, and Footer components and import them into Dashboard

C. Write Sidebar, Content, and Footer as functions inside Dashboard component function

D. Combine Sidebar and Footer into one component and Content separately, all in Dashboard file

Solution

1. Step 1: Understand component reusability and clarity

   Separating components into their own files makes code easier to read, reuse, and maintain.

2. Step 2: Evaluate options for organization

   Create separate files for Sidebar, Content, and Footer components and import them into Dashboard creates separate files and imports them, which is best practice. Other options mix concerns or reduce clarity.

3. Final Answer:

   Create separate files for Sidebar, Content, and Footer components and import them into Dashboard -> Option B

4. Quick Check:

   Separate files for components = A [OK]

Hint: Separate components into files for clarity and reuse [OK]

Common Mistakes:

• Putting all code in one file making it messy
• Defining components inside other components unnecessarily
• Combining unrelated components reducing modularity