update nav

docs/LangGraph/01_graph___stategraph.md

@@ -1,3 +1,10 @@
+---
+layout: default
+title: "Graph & StateGraph"
+parent: "LangGraph"
+nav_order: 1
+---
+
 # Chapter 1: Graph / StateGraph - The Blueprint of Your Application
 
 Welcome to the LangGraph tutorial! We're excited to help you learn how to build powerful, stateful applications with Large Language Models (LLMs).

docs/LangGraph/02_nodes___pregelnode__.md

@@ -1,3 +1,10 @@
+---
+layout: default
+title: "Nodes (PregelNode)"
+parent: "LangGraph"
+nav_order: 2
+---
+
 # Chapter 2: Nodes (`PregelNode`) - The Workers of Your Graph
 
 In [Chapter 1: Graph / StateGraph](01_graph___stategraph.md), we learned how `StateGraph` acts as a blueprint or a flowchart for our application. It defines the overall structure and the shared "whiteboard" (the State) that holds information.

docs/LangGraph/03_channels.md

@@ -1,3 +1,10 @@
+---
+layout: default
+title: "Channels"
+parent: "LangGraph"
+nav_order: 3
+---
+
 # Chapter 3: Channels - The Communication System
 
 In [Chapter 1: Graph / StateGraph](01_graph___stategraph.md), we learned about the `StateGraph` as the blueprint for our application, holding the shared "whiteboard" or state. In [Chapter 2: Nodes (`PregelNode`)](02_nodes___pregelnode__.md), we met the "workers" or Nodes that perform tasks and read/write to this whiteboard.

docs/LangGraph/04_control_flow_primitives___branch____send____interrupt__.md

@@ -1,3 +1,10 @@
+---
+layout: default
+title: "Control Flow Primitives"
+parent: "LangGraph"
+nav_order: 4
+---
+
 # Chapter 4: Control Flow Primitives (`Branch`, `Send`, `Interrupt`)
 
 In [Chapter 3: Channels](03_channels.md), we saw how information is stored and updated in our graph's shared state using Channels. We have the blueprint ([`StateGraph`](01_graph___stategraph.md)), the workers ([`Nodes`](02_nodes___pregelnode__.md)), and the communication system ([Channels](03_channels.md)).

docs/LangGraph/05_pregel_execution_engine.md

@@ -1,3 +1,10 @@
+---
+layout: default
+title: "Pregel Execution Engine"
+parent: "LangGraph"
+nav_order: 5
+---
+
 # Chapter 5: Pregel Execution Engine - The Engine Room
 
 In the previous chapters, we learned how to build the blueprint of our application using [`StateGraph`](01_graph___stategraph.md), define the workers with [`Nodes`](02_nodes___pregelnode__.md), manage the shared state with [`Channels`](03_channels.md), and direct the traffic using [Control Flow Primitives](04_control_flow_primitives___branch____send____interrupt__.md).

docs/LangGraph/06_checkpointer___basecheckpointsaver__.md

@@ -1,3 +1,10 @@
+---
+layout: default
+title: "Checkpointer (BaseCheckpointSaver)"
+parent: "LangGraph"
+nav_order: 6
+---
+
 # Chapter 6: Checkpointer (`BaseCheckpointSaver`) - Saving Your Progress
 
 In [Chapter 5: Pregel Execution Engine](05_pregel_execution_engine.md), we saw how the engine runs our graph step-by-step. But what happens if a graph takes hours to run, or if it needs to pause and wait for a human? If the program crashes or we need to stop it, do we lose all the progress?