Layout vs template difference in NextJS

Introduction

Layouts and templates help organize pages in a web app. They make your site look consistent and easier to build.

When you want the same header and footer on many pages.

When you need different page structures for different sections of your site.

When you want to reuse a common page style but change the content inside.

When you want to separate page design from page content for easier updates.

Syntax

NextJS

export default function Layout({ children }) {
  return (
    <html>
      <body>
        <header>Site Header</header>
        {children}
        <footer>Site Footer</footer>
      </body>
    </html>
  )
}

function Template() {
  return (
    <div>
      <h1>Page Title</h1>
      <p>Page content here</p>
    </div>
  )
}

Layout wraps pages and adds common parts like header and footer.

Template is the page content inside the layout.

Examples

This layout adds a menu and footer around any page content.

NextJS

export default function Layout({ children }) {
  return (
    <div>
      <nav>Menu</nav>
      {children}
      <footer>Footer info</footer>
    </div>
  )
}

This template shows the main content for the home page.

NextJS

export default function Template() {
  return (
    <main>
      <h2>Welcome!</h2>
      <p>This is the home page.</p>
    </main>
  )
}

Sample Program

This example shows a Layout component that adds a header and footer around the page content. The Template component is the actual page content inside the layout. The Page component combines them to render a full page.

NextJS

import React from 'react';

function Layout({ children }) {
  return (
    <html lang="en">
      <body>
        <header style={{backgroundColor: '#eee', padding: '1rem'}}>
          <h1>My Website</h1>
        </header>
        <main>{children}</main>
        <footer style={{backgroundColor: '#eee', padding: '1rem', marginTop: '2rem'}}>
          <p>© 2024 My Website</p>
        </footer>
      </body>
    </html>
  );
}

function Template() {
  return (
    <section>
      <h2>About Us</h2>
      <p>We build simple and clear websites.</p>
    </section>
  );
}

export default function Page() {
  return (
    <Layout>
      <Template />
    </Layout>
  );
}

Important Notes

Layouts wrap around templates to keep site design consistent.

Templates hold the unique content for each page.

Using layouts and templates helps you avoid repeating code.

Summary

Layouts provide the common page structure like headers and footers.

Templates are the unique content inside layouts.

Together, they make building and maintaining pages easier and cleaner.

Practice

1. In Next.js, what is the main role of a layout component?

easy

A. To manage client-side state

B. To provide common page structure like headers and footers

C. To handle API requests

D. To define unique content for each page

Solution

1. Step 1: Understand layout purpose

   Layouts in Next.js wrap pages to provide shared UI elements like headers and footers.

2. Step 2: Differentiate from templates

   Templates hold unique page content, not common structure.

3. Final Answer:

   To provide common page structure like headers and footers -> Option B

4. Quick Check:

   Layout = common structure [OK]

Hint: Layouts wrap pages with shared UI elements [OK]

Common Mistakes:

• Confusing layouts with templates
• Thinking layouts handle data fetching
• Assuming layouts manage state

2. Which of the following is the correct way to define a layout in Next.js 14+ using the App Router?

easy

A. export default function Layout({ children }) { return {children} }

B. function Layout() { return Page Content }

C. const Layout = () => Header

D. export function layout() { return {children} }

Solution

1. Step 1: Check export and props

   Layouts must be default exported and receive children prop to wrap page content.

2. Step 2: Validate syntax

   export default function Layout({ children }) { return
   {children} } correctly exports a function with { children } and returns JSX wrapping children.

3. Final Answer:

   export default function Layout({ children }) { return <div>{children}</div> } -> Option A

4. Quick Check:

   Default export + children prop = export default function Layout({ children }) { return
   {children}
   } [OK]

Hint: Layouts must export default and accept children [OK]

Common Mistakes:

• Not exporting default
• Missing children prop
• Using lowercase function name for layout

3. Given this Next.js layout component:

export default function Layout({ children }) {
  return (
    <html>
      <body>
        <header>Site Header</header>
        {children}
        <footer>Site Footer</footer>
      </body>
    </html>
  )
}

And a page component:

export default function Page() {
  return <main>Welcome!</main>
}

What will be the rendered HTML structure?

medium

A. Site HeaderWelcome!Site Footer

B. Welcome!

C. Site HeaderSite Footer

D. Welcome!

Solution

1. Step 1: Understand layout wrapping

   The layout wraps the page content inside <html> and <body> tags, adding header and footer around children.

2. Step 2: Insert page content

   The page returns <main>Welcome!</main>, which is placed where {children} is in layout.

3. Final Answer:

   <html><body><header>Site Header</header><main>Welcome!</main><footer>Site Footer</footer></body></html> -> Option A

4. Quick Check:

   Layout wraps page content with header/footer [OK]

Hint: Children content appears inside layout's wrapper [OK]

Common Mistakes:

• Ignoring layout wrapping
• Thinking page replaces entire layout
• Missing header or footer in output

4. You wrote this layout in Next.js:

export default function Layout() {
  return (
    <div>
      <header>Header</header>
      {children}
      <footer>Footer</footer>
    </div>
  )
}

But the page content does not render inside the layout. What is the problem?

medium

A. The footer tag is invalid in layouts

B. The layout should not have a header

C. The layout function does not accept the children prop

D. The layout must be a class component

Solution

1. Step 1: Check function parameters

   The layout must accept { children } as a parameter to render page content inside.

2. Step 2: Identify missing children prop

   The code misses { children } in the function signature, so it cannot render page content.

3. Final Answer:

   The layout function does not accept the children prop -> Option C

4. Quick Check:

   Missing children prop causes no page content [OK]

Hint: Layouts must accept children prop to render page content [OK]

Common Mistakes:

• Forgetting to add children parameter
• Thinking header/footer cause error
• Believing layouts must be class components

5. You want to create a Next.js page that uses a layout with a sidebar and header. The sidebar should only appear on some pages, but the header should always be present. How should you organize layouts and templates to achieve this?

hard

A. Add sidebar inside each page component instead of layouts

B. Put header and sidebar in the same layout used by all pages

C. Use templates only and avoid layouts for shared UI

D. Create a main layout with header, then nested layouts for pages with sidebar

Solution

1. Step 1: Identify shared and conditional UI

   The header is shared by all pages, so it belongs in the main layout. Sidebar is conditional, so it fits in nested layouts.

2. Step 2: Use nested layouts

   Create a main layout with header, then nest layouts for pages needing sidebar to add it without affecting others.

3. Final Answer:

   Create a main layout with header, then nested layouts for pages with sidebar -> Option D

4. Quick Check:

   Nested layouts handle conditional UI [OK]

Hint: Use nested layouts for conditional UI parts [OK]

Common Mistakes:

• Putting all UI in one layout causing unwanted sidebar
• Adding sidebar directly in pages losing layout benefits
• Avoiding layouts and mixing shared UI in templates