update nav

docs/Flask/01_application_object___flask__.md

@@ -1,3 +1,10 @@
+---
+layout: default
+title: "Application Object (Flask)"
+parent: "Flask"
+nav_order: 1
+---
+
 # Chapter 1: Application Object (`Flask`)
 
 Welcome to your first step into the world of Flask! Flask is a "microframework" for building web applications in Python. "Micro" doesn't mean it's limited; it means Flask provides the essentials to get started quickly, letting you add features as needed.

docs/Flask/02_routing_system.md

@@ -1,3 +1,10 @@
+---
+layout: default
+title: "Routing System"
+parent: "Flask"
+nav_order: 2
+---
+
 # Chapter 2: Routing System
 
 Welcome back! In [Chapter 1: Application Object (`Flask`)](01_application_object___flask__.md), we learned how to create the central `app` object, the control tower for our Flask application. We even added a simple "Hello, World!" page using `@app.route('/')`.

docs/Flask/03_request_and_response_objects.md

@@ -1,3 +1,10 @@
+---
+layout: default
+title: "Request and Response Objects"
+parent: "Flask"
+nav_order: 3
+---
+
 # Chapter 3: Request and Response Objects
 
 Welcome back! In [Chapter 2: Routing System](02_routing_system.md), we learned how Flask uses routes (`@app.route(...)`) to direct incoming web requests to the correct Python view functions. We saw how to create static routes like `/about` and dynamic routes like `/user/<username>`.

docs/Flask/04_templating__jinja2_integration_.md

@@ -1,3 +1,10 @@
+---
+layout: default
+title: "Templating (Jinja2 Integration)"
+parent: "Flask"
+nav_order: 4
+---
+
 # Chapter 4: Templating (Jinja2 Integration)
 
 Welcome back! In [Chapter 3: Request and Response Objects](03_request_and_response_objects.md), we saw how to handle incoming requests and craft outgoing responses. We even created a simple HTML form, but we had to write the HTML code directly as a string inside our Python function. Imagine building a whole website like that – it would get very messy very quickly!

docs/Flask/05_context_globals___current_app____request____session____g__.md

@@ -1,3 +1,10 @@
+---
+layout: default
+title: "Context Globals"
+parent: "Flask"
+nav_order: 5
+---
+
 # Chapter 5: Context Globals (`current_app`, `request`, `session`, `g`)
 
 Welcome back! In [Chapter 4: Templating (Jinja2 Integration)](04_templating__jinja2_integration_.md), we learned how to separate our HTML structure from our Python code using templates and the `render_template` function. We saw how variables like `request` and functions like `url_for` seemed to be magically available in our templates.

docs/Flask/06_configuration___config__.md

@@ -1,3 +1,10 @@
+---
+layout: default
+title: "Configuration (config)"
+parent: "Flask"
+nav_order: 6
+---
+
 # Chapter 6: Configuration (`Config`)
 
 Welcome back! In [Chapter 5: Context Globals (`current_app`, `request`, `session`, `g`)](05_context_globals___current_app____request____session____g__.md), we saw how Flask uses context globals like `current_app` and `session`. We even learned that using the `session` requires setting a `SECRET_KEY` on our application object. But where is the best place to put settings like the secret key, or maybe a database connection string, or a flag to turn debugging features on or off? We definitely don't want to hardcode these directly into our main application logic!

docs/Flask/07_application_and_request_contexts.md

@@ -1,3 +1,10 @@
+---
+layout: default
+title: "Application and Request Contexts"
+parent: "Flask"
+nav_order: 7
+---
+
 # Chapter 7: Application and Request Contexts
 
 Welcome back! In [Chapter 6: Configuration (`Config`)](06_configuration___config__.md), we learned how to manage settings for our Flask application using the `app.config` object. And in [Chapter 5: Context Globals (`current_app`, `request`, `session`, `g`)](05_context_globals___current_app____request____session____g__.md), we met special variables like `request` and `current_app` that seem to magically know about the current request or application.

docs/Flask/08_blueprints.md

@@ -1,3 +1,10 @@
+---
+layout: default
+title: "Blueprints"
+parent: "Flask"
+nav_order: 8
+---
+
 # Chapter 8: Blueprints
 
 Welcome back! In [Chapter 7: Application and Request Contexts](07_application_and_request_contexts.md), we explored the "magic" behind Flask's context system, understanding how variables like `request` and `current_app` work reliably even with multiple concurrent requests.