หลายเส้นทางในแอปเดียว

A real site has many pages. You add each one with its own route and view function, all living inside the same app file.

Just write more @app.route blocks. Each pairs a unique path with its own function, and Flask keeps track of every one.

Below the first route, add a second for a new path like /about. Two routes, two functions, two pages your users can visit.

Two routes must not share the same path. If they do, Flask cannot tell which view to call and raises an error at startup.

Reusing a path triggers a collision. Flask warns that the endpoint is already registered, so give every route a distinct URL.

Each view also needs a unique function name. Two functions named home overwrite each other, and only the last one survives.

Flask stores each route under an endpoint name, which defaults to the function name. That name is how Flask refers to the route internally.

Keep related pages near each other in the file. Good grouping makes a growing app easier to read and to maintain over time.

Flask picks a route by the requested path, not by source order. So the position of a route in the file does not change which page loads.

Dozens of routes in one file get unwieldy. Later you will split them into blueprints, but for now a single file is perfectly fine.

Here is the shape: distinct paths, distinct names, one app. Add a contact route the same way and your site keeps growing.

Spot what causes a route collision.

You build many pages by stacking routes, each with a unique path and name. Keep them tidy now, and blueprints will scale you later. 🧭