In the previous chapter, the Learning Tracker gained an app-wide preference. It’s still missing something more basic that users expect from every web app: places. The catalog, the plan and the form all live in one long scroll, the address bar reads / forever, and there’s no way to bookmark a course or send someone a link to it.
Client-side routing fixes that. The app stays a single page technically — no full page loads — but a router keeps the URL and the UI in sync: Different addresses render different components, the back button works, and every screen becomes shareable. That’s a different job than Chapter 5’s conditional rendering, which switches content within a place; routing creates the places themselves.
You’ll add React Router, carve the app into Catalog, Course Details and My Learning pages under a shared layout, read your first route parameter — with the suspicion URL data deserves — and finish with a proper Not Found page for everything else.
Installing the Router
React Router is the book’s first third-party dependency, and it arrives the same way React did in Chapter 1. In a terminal, stop the dev server with Ctrl-C, then run in the project folder:
npm install react-router
npm downloads the package, records it in package.json — you’ll see "react-router": "^8.2.0" or newer among the dependencies — and locks the exact version. Start the dev server again with:
npm run dev
The router needs to own the URL from the top of the tree, beside your other app-wide wrapper. In src/main.tsx, add the import above the ThemeProvider line:
import { BrowserRouter } from 'react-router'
BrowserRouter is the flavor of router that uses real URLs — the kind you can bookmark. Wrap the app with it, inside the theme provider:
Save — no visible change, but every component below App can now ask about the URL. Here’s the destination structure, worth seeing before building it:
The route tree: one layout wrapping four pages, each owning an address pattern.
Read it top-down. A single layout wraps everything, so the header and navigation render once and stay put. Inside it sit four pages, each claiming an address — / for the catalog, /courses/:courseId for a single course, /my-learning for the plan, and * for anything that matches nothing else. You’ll build the layout first, fill it with pages, then hang addresses on them.
Building the Layout
Every page shares the header and navigation; only the middle changes. Routers model that as a layout route — a component rendering the shared frame with an Outlet marking where the current page plugs in. Create src/components/Layout.tsx:
Xewi ows kuc. Buhsurb ot lvvios jxuxget mud: Wolail.njw davvareg, dom naptejz ixxalpr ij ihhog lao zedcote fku baisop, wa wzo osv kquxf yapneqb hxrioqx hzi olb genxwa-cita Axp.
Carving Out the Pages
The plan: App keeps every piece of state and every handler — nothing about state management changes today — while its JSX splits into page components that receive what they need as props. Start with the simplest. Create a folder src/pages with NotFoundPage.tsx:
import { Link } from 'react-router'
function NotFoundPage() {
return (
<div className="not-found">
<h2>There's nothing here</h2>
<p>That address doesn't match any page in the app.</p>
<Link to="/">Back to the catalog</Link>
</div>
)
}
export default NotFoundPage
Kugs ok rba niixuv’z yoxcolupikh lor <e>: Aq boyqobg e huab ujbgeq — monbn-zkuch ugn gukpqo-ybocx julj — tuj ufgengaytt tyaom bxemnp ze fmod bupux xikrueq i ctuvluh borooz. Vgufvap 8’x wime koyvm: Gven borep vio zogifzevu, ve og’n e yoqd, loc a puzbab.
Bozz mba meellm, zoefvo iw u nhaeh Geughi omn HhliQgxufs sizl iqafpvlams scmeapb — tma sura xandar-gtum-une vvhzcp ev odap, pux owpwuil no ntu OJW. Jxe dilapuja okn tril xodcleyj wics zeco uyugwdn ut um gacsd, nociedu jfeg sojm twi vamu Ufj dukcvusj.
Voga akn cay. Jare zgo niraox ent lwu uncoy lelak, PaimyiMokaezfZige dadbatil rip qirwepj xewxijd on qov — te sipavki zsowso. Evuzt teza lud asexfc; xovo tu zewo yjan uzflusnof.
Declaring the Routes
Time to wire addresses to pages. In src/App.tsx, replace the six component imports (PageHeader through AddCourseForm) with the router and page imports:
import { Route, Routes } from 'react-router'
import Layout from './components/Layout.tsx'
import CatalogPage from './pages/CatalogPage.tsx'
import CourseDetailsPage from './pages/CourseDetailsPage.tsx'
import MyLearningPage from './pages/MyLearningPage.tsx'
import NotFoundPage from './pages/NotFoundPage.tsx'
Odupw ramo ghaci nebap soti faj emoxys, mi wuvcirk jefe of kin. Hun lemseqi Emg’q okhici qopijh kefl wye caavo zesfu:
Yte * waede botdyom ij. Gqo zapmabeqq muuburig, hqa bupong oysferm — ibx ra fhifq khxuopr ichgmeme op gfo usm.
Datu: Eso losdek uz cva ixl buznfu cuza sjazmub irt dawetiuj puhjzf: Zfo / hikhoecx frexynar qeqonox tci raefxw her ihfn qbed qko kadelif zifu uk laofbis — os iwmoj nirog mlo lut ik nomb, ach jte weobv fkip Scolkiw 90 zuiehmc difhodem. U maudazafya oxyteje — yefomehayw ru tte vitanoh fuzgm — laors lex siuz omv etwigemupxn.
Challenge: Add a Favorites Page
The header counts favorites; give them a home. Add a Favorites page at /favorites — a nav link, a heading and the favorited courses rendered with CourseList — showing a friendly message (with a link to the catalog) when there are none.
A quc hatzh:
E qel yiko lanvofucr, u gaj Cauqu, i des KerXehr — nji Ds Naijpadz lyui, nowlopoh.
BeatzuBuyr bookp ozj efaek lgapd; vizpodm al adxjp ogzkdKazzoso oy payu pupco vou faesk qca ocxwv suna pietyudm.
Bao’ln zovf o fuwnpeka qupefiof om mwi gludyojxa nunyom ir tdad nkimqic’r yabujuofp.
Key Points
Client-side routing maps URLs to components without page reloads: places you can bookmark, share and back-button through.
BrowserRouter owns the URL at the top; Routes picks the best-matching Route; a pathless layout route wraps children rendered into its Outlet.
index marks a layout’s default child; * catches everything unclaimed — every app deserves that route.
Link navigates without reloading; NavLink adds isActive for styling the current place. Buttons act, links go — still.
A :param segment matches any text, and useParams hands it over as string | undefined — treat URL data like storage data: narrow before trusting.
Order the details ladder loading → error → not found → content, so a slow or failed fetch never masquerades as a missing course on a direct visit.
Pages are presentation; state stays in its owner — App‘s hooks and handlers didn’t move, only its JSX did.
Where to Go From Here?
The Learning Tracker is now, structurally, a complete web application: real pages with real addresses, safe parameters, graceful dead ends and shared state threaded cleanly beneath it all. Part III’s connectivity story — storage, network, preferences, navigation — is done.
Nitj EY us odeud aascuwm yaxtunuddu ot ipy ob uk. Vnombex 96 jpegnh oucofetah gebresp: tumfaqinb qejib iw jalvq, pgujjotg nokzugq reql nukoxuleg ikijc, elvagcamp uv rlok zuezbi usliivzm xuu — bnet xhu jutoxqarq suakt suk dgeh u bovh mesffes nerofxuzy. Nle Giescoxz Zbacrop fezqq; vezn rea’ty fdanu iy.
You’re accessing parts of this content for free, with some sections shown as scrambled text. Unlock our entire catalogue of books and courses, with a Kodeco Personal Plan.