update nav

docs/FastAPI/01_fastapi_application___routing.md

@@ -1,3 +1,10 @@
+---
+layout: default
+title: "FastAPI Application & Routing"
+parent: "FastAPI"
+nav_order: 1
+---
+
 # Chapter 1: FastAPI Application & Routing
 
 Welcome to your first adventure with FastAPI! 👋

docs/FastAPI/02_path_operations___parameter_declaration.md

@@ -1,3 +1,10 @@
+---
+layout: default
+title: "Path Operations & Parameter Declaration"
+parent: "FastAPI"
+nav_order: 2
+---
+
 # Chapter 2: Path Operations & Parameter Declaration
 
 Welcome back! In [Chapter 1: FastAPI Application & Routing](01_fastapi_application___routing.md), we learned how to set up a basic FastAPI application and organize our code using `APIRouter`. We saw how to connect a URL like `/` to a Python function using `@app.get("/")`.

docs/FastAPI/03_data_validation___serialization__pydantic_.md

@@ -1,3 +1,10 @@
+---
+layout: default
+title: "Data Validation & Serialization (Pydantic)"
+parent: "FastAPI"
+nav_order: 3
+---
+
 # Chapter 3: Data Validation & Serialization (Pydantic)
 
 Welcome back! In [Chapter 2: Path Operations & Parameter Declaration](02_path_operations___parameter_declaration.md), we learned how FastAPI uses type hints to understand path parameters (like `/items/{item_id}`) and query parameters (like `/?skip=0&limit=10`). We even saw a sneak peek of how Pydantic models can define the structure of a JSON request body.

docs/FastAPI/04_openapi___automatic_docs.md

@@ -1,3 +1,10 @@
+---
+layout: default
+title: "OpenAPI & Automatic Docs"
+parent: "FastAPI"
+nav_order: 4
+---
+
 # Chapter 4: OpenAPI & Automatic Docs
 
 Welcome back! In [Chapter 3: Data Validation & Serialization (Pydantic)](03_data_validation___serialization__pydantic_.md), we saw how FastAPI uses Pydantic models to automatically validate incoming data and serialize outgoing data, making our API robust and predictable. But how do we tell others (or remind ourselves later) how to actually *use* our API? What endpoints exist? What data should they send? What will they get back?

docs/FastAPI/05_dependency_injection.md

@@ -1,3 +1,10 @@
+---
+layout: default
+title: "Dependency Injection"
+parent: "FastAPI"
+nav_order: 5
+---
+
 # Chapter 5: Dependency Injection
 
 Welcome back! In [Chapter 4: OpenAPI & Automatic Docs](04_openapi___automatic_docs.md), we saw how FastAPI automatically generates interactive documentation for our API, making it easy for others (and ourselves!) to understand and use. This works because FastAPI understands the structure of our paths, parameters, and Pydantic models.

docs/FastAPI/06_error_handling.md

@@ -1,3 +1,10 @@
+---
+layout: default
+title: "Error Handling"
+parent: "FastAPI"
+nav_order: 6
+---
+
 # Chapter 6: Error Handling
 
 Welcome back! In [Chapter 5: Dependency Injection](05_dependency_injection.md), we learned how to structure our code using dependencies to manage common tasks like pagination or database sessions. This helps keep our code clean and reusable.

docs/FastAPI/07_security_utilities.md

@@ -1,3 +1,10 @@
+---
+layout: default
+title: "Security Utilities"
+parent: "FastAPI"
+nav_order: 7
+---
+
 # Chapter 7: Security Utilities
 
 Hi there! 👋 In [Chapter 6: Error Handling](06_error_handling.md), we learned how to handle situations where things go wrong in our API, like when a user requests an item that doesn't exist. Now, let's talk about protecting our API endpoints.

docs/FastAPI/08_background_tasks.md

@@ -1,3 +1,10 @@
+---
+layout: default
+title: "Background Tasks"
+parent: "FastAPI"
+nav_order: 8
+---
+
 # Chapter 8: Background Tasks
 
 Welcome back! In [Chapter 7: Security Utilities](07_security_utilities.md), we learned how to protect our API endpoints using FastAPI's security features. Now, let's explore how to perform actions *after* we've already sent a response back to the user.