Why Navigation links in React? - Purpose & Use Cases

The Big Idea

Discover how a simple component can save you hours of frustrating link updates!

The Scenario

Imagine building a website where you have to update every navigation link manually whenever you add a new page or change a URL.

You have to find each link in your HTML and change it one by one.

The Problem

This manual method is slow and easy to mess up.

You might forget to update some links, causing broken navigation and a bad user experience.

Also, managing active link styles or accessibility features becomes a headache.

The Solution

Using navigation link components in React lets you define links once and reuse them everywhere.

The component automatically handles URL changes, active states, and accessibility, making your code cleaner and more reliable.

Before vs After

✗ Before

<a href="/home">Home</a>
<a href="/about">About</a>

✓ After

<NavLink to="/home">Home</NavLink>
<NavLink to="/about">About</NavLink>

What It Enables

You can build dynamic, easy-to-maintain navigation menus that update automatically and improve user experience.

Real Life Example

Think of an online store where new product categories are added often.

With navigation link components, the menu updates smoothly without hunting through all your code.

Key Takeaways

Manual link updates are slow and error-prone.

Navigation link components automate URL and active state management.

This leads to cleaner code and better user navigation.

Practice

1. What is the main purpose of using Link from react-router-dom in a React app?

easy

A. To create navigation links that change pages without reloading the browser

B. To style buttons with CSS

C. To fetch data from an API

D. To manage component state

Solution

1. Step 1: Understand the role of Link

   Link is used to navigate between pages in a React app without refreshing the whole page.

2. Step 2: Compare with other options

   Options A, C, and D describe unrelated tasks like styling, data fetching, and state management, which Link does not handle.

3. Final Answer:

   To create navigation links that change pages without reloading the browser -> Option A

4. Quick Check:

   Navigation without reload = B [OK]

Hint: Remember: <Link> changes pages without full reload [OK]

Common Mistakes:

• Confusing <Link> with HTML <a> tag behavior
• Thinking <Link> manages data or state
• Assuming <Link> reloads the page

2. Which of the following is the correct syntax to create a navigation link to '/about' using react-router-dom?

easy

A. About

B. About

C. About

D. About

Solution

1. Step 1: Identify correct attribute for Link

   The Link component uses the to attribute to specify the path.

2. Step 2: Differentiate from HTML anchor tag

   HTML a tags use href, but Link requires to. About uses correct syntax.

3. Final Answer:

   <Link to='/about'>About</Link> -> Option C

4. Quick Check:

   Link uses to attribute [OK]

Hint: Use 'to' with <Link>, 'href' with <a> [OK]

Common Mistakes:

• Using href instead of to with <Link>
• Using to attribute on <a> tag
• Mixing <Link> and <a> syntax

3. Given this React code snippet, what will be rendered on the page?

import { Link } from 'react-router-dom';

function Nav() {
  return (
    <nav>
      <Link to='/'>Home</Link>
      <Link to='/profile'>Profile</Link>
    </nav>
  );
}

medium

A. An error because <Link> cannot be used inside <nav>

B. Two clickable links labeled 'Home' and 'Profile' that navigate without page reload

C. Buttons that submit a form

D. Plain text 'Home' and 'Profile' with no navigation

Solution

1. Step 1: Analyze the JSX structure

   The component returns a <nav> element containing two <Link> components with paths '/' and '/profile'.

2. Step 2: Understand Link behavior

   Link renders as clickable links that navigate client-side without reloading the page.

3. Final Answer:

   Two clickable links labeled 'Home' and 'Profile' that navigate without page reload -> Option B

4. Quick Check:

   Links inside nav render clickable navigation [OK]

Hint: Links inside nav create clickable navigation [OK]

Common Mistakes:

• Thinking <Link> renders plain text
• Assuming <Link> causes page reload
• Believing <Link> cannot be inside <nav>

4. What is wrong with this React navigation code?

import { Link } from 'react-router-dom';

function Menu() {
  return (
    <nav>
      <Link href='/dashboard'>Dashboard</Link>
    </nav>
  );
}

medium

A. No import statement for React

B. Missing closing tag for <nav>

C. Link component cannot be used inside <nav>

D. Using 'href' instead of 'to' on <Link> causes navigation failure

Solution

1. Step 1: Check attribute usage on Link

   The Link component requires the to attribute, not href.

2. Step 2: Verify other code parts

   The <nav> tag is properly closed, and Link can be inside nav. React import is not mandatory in React 17+ for JSX.

3. Final Answer:

   Using 'href' instead of 'to' on <Link> causes navigation failure -> Option D

4. Quick Check:

   Link needs 'to', not 'href' [OK]

Hint: Use 'to' with <Link>, not 'href' [OK]

Common Mistakes:

• Using href attribute on <Link>
• Thinking <Link> can't be inside <nav>
• Assuming React import is always required

5. You want to create a navigation menu with links that have accessible names and keyboard focus. Which approach is best in React using react-router-dom?

hard

A. Use <nav> with <Link> components, add aria-label on nav, and ensure links have descriptive text

B. Use <div> with <Link> components and no ARIA labels

C. Use <nav> with <a> tags and href attributes for navigation

D. Use buttons with onClick handlers instead of links for navigation

Solution

1. Step 1: Choose semantic HTML for navigation

   The <nav> element is the correct semantic container for navigation links, improving accessibility.

2. Step 2: Use Link with descriptive text and ARIA labels

   Link components from react-router-dom provide client-side navigation. Adding aria-label on nav helps screen readers understand the menu purpose.

3. Step 3: Avoid incorrect elements

   Using div or buttons for navigation is less semantic and harms accessibility. Using a tags with href reloads pages, not client-side navigation.

4. Final Answer:

   Use <nav> with <Link> components, add aria-label on nav, and ensure links have descriptive text -> Option A

5. Quick Check:

   Semantic nav + Link + ARIA = A [OK]

Hint: Use semantic nav + Link + aria-label for accessible navigation [OK]

Common Mistakes:

• Using div instead of nav for navigation
• Skipping aria-label for screen readers
• Using buttons instead of links for navigation