Server routes
Server routes organise the application into pages and actions, keeping URLs meaningful and predictable.
Python for Kids · Class 10 · Module 6 of 9
Web Application Development
Multiple pages, real data, actual users. This is software now.
8 sessionsSessions 41–48
4 weeksTypical pace
Intermediate to AppliedLevel
Class 10Python & Coding
The big idea
Students build a multi-page application with server-side routing, templates that share a common layout, form handling, and an understanding of how a stateless web remembers who you are.
Why it matters
A working web application is the most persuasive portfolio item a Class 10 student can hold, and it consolidates every earlier module at once.
Unpacked
What you will actually learn
Three core ideas, each taught with worked examples and then practised until it feels obvious.
Templates
Templates with inheritance let one base layout supply the header, footer and navigation to every page.
Forms and sessions concept
Sessions solve a real puzzle: HTTP forgets you between requests, so a small identifier is used to recognise a returning visitor.
Did you know?
HTTP was deliberately designed to be stateless. Cookies and sessions were invented afterwards to work around that decision.
Common mix-up
“Sessions are secure by default.” A session identifier is a key. If it can be read or guessed, the account can be taken.
Session by session
Your 8-session journey
Sessions 41–48 of the 72-session year, at two one-hour sessions per week.
- 1
Warm-up and big picture
Where this module fits, what you will build, and a hands-on starter that gets everyone curious about server routes.
- 2
Server routes
Guided teaching on server routes, worked through together with the teacher.
- 3
Server routes — practice lab
Independent practice, small challenges and one deliberate mistake to diagnose.
- 4
Templates
Guided teaching on templates, building directly on the previous two sessions.
- 5
Templates — practice lab
Applied tasks that combine server routes and templates in one piece of work.
- 6
Forms and sessions concept
Forms and sessions concept introduced and practised, completing the toolkit needed for the project.
- 7
Project build
Guided build session for the module project: Multi-page Python web app.
- 8
Test, present and reflect
Finish, test against the checklist, present the work and explain the decisions behind it.
Project lab
Multi-page Python web app
Every module ends with something the student built themselves and can demonstrate. This is the piece that goes into their portfolio and gets explained out loud at the end of session 48.
Try this at home
Add a login to your web app, then think carefully about what a logged-out visitor can still reach by typing the URL directly.
It is finished when
- It works from start to finish without breaking
- You can explain every part of it in your own words
- You tested it and improved at least one thing afterwards
- Someone else used or understood it without your help
By the end of this module
Students finishing Module 6 can:
- Explain and use server routes without prompting
- Explain and use templates without prompting
- Explain and use forms and sessions concept without prompting
- Build and finish multi-page python web app
- Test your own work and correct what you find
- Talk an adult through what you made and why
Word bank
The vocabulary introduced here, in plain language:
- session
- Stored state that identifies a returning user.
- stateless
- Not remembering anything between requests.
- template inheritance
- Pages built from a shared base layout.
Module challenge
Think you have got this?
0 XPLevel 1 · Curious Beginner
6 quick questions drawn from this module — vocabulary, the project you build, and a myth-or-fact round. Every wrong answer explains itself, so a mistake still teaches you something.
Your child's free trial is one message away.
Tell us your child’s class and what they enjoy. We will suggest the closest program fit—no pressure and no upfront payment.