Routing concept

What this means

Routing maps URLs to screens. React itself focuses on UI, while frameworks and router libraries decide which component or page should appear for a URL.

In beginner terms, this topic answers one practical question: "What should I write, and why does React care about it?" Do not try to memorize the syntax first. First understand the idea, then connect the syntax to that idea.

Why it matters

Users expect URLs, back buttons, bookmarks, and page transitions to work. Routing is how single-page and framework apps organize movement.

When you build real React screens, this idea helps you decide where data should live, what the user should see, and what should happen after an interaction. That is why this lesson is part of the main path instead of being an optional detail.

Step by step

1. Notice the UI problem this topic solves. 2. Look at the smallest possible example. 3. Change one value and predict what should appear. 4. Run the example and compare the result with your prediction. 5. Use the practice task before moving on.

Small example

/tracks/react
/learn/react/components

Common mistake

Do not confuse a component with a route. A route may render a component, but the route is the URL-level structure.

Practice task

Sketch three URLs for a learning platform and name the screen each URL should show.

Remember this

Routing connects URLs to UI.