update nav

docs/AutoGen Core/01_agent.md

@@ -1,3 +1,10 @@
+---
+layout: default
+title: "Agent"
+parent: "AutoGen Core"
+nav_order: 1
+---
+
 # Chapter 1: Agent - The Workers of AutoGen
 
 Welcome to the AutoGen Core tutorial! We're excited to guide you through building powerful applications with autonomous agents.

docs/AutoGen Core/02_messaging_system__topic___subscription_.md

@@ -1,3 +1,10 @@
+---
+layout: default
+title: "Messaging System"
+parent: "AutoGen Core"
+nav_order: 2
+---
+
 # Chapter 2: Messaging System (Topic & Subscription)
 
 In [Chapter 1: Agent](01_agent.md), we learned about Agents as individual workers. But how do they coordinate when one agent doesn't know exactly *who* needs the information it produces? Imagine our Researcher finds some facts. Maybe the Writer needs them, but maybe a Fact-Checker agent or a Summary agent also needs them later. How can the Researcher just announce "Here are the facts!" without needing a specific mailing list?

docs/AutoGen Core/03_agentruntime.md

@@ -1,3 +1,10 @@
+---
+layout: default
+title: "AgentRuntime"
+parent: "AutoGen Core"
+nav_order: 3
+---
+
 # Chapter 3: AgentRuntime - The Office Manager
 
 In [Chapter 1: Agent](01_agent.md), we met the workers (`Agent`) of our system. In [Chapter 2: Messaging System](02_messaging_system__topic___subscription_.md), we saw how they can communicate broadly using topics and subscriptions. But who hires these agents? Who actually delivers the messages, whether direct or published? And who keeps the whole system running smoothly?

docs/AutoGen Core/04_tool.md

@@ -1,3 +1,10 @@
+---
+layout: default
+title: "Tool"
+parent: "AutoGen Core"
+nav_order: 4
+---
+
 # Chapter 4: Tool - Giving Agents Specific Capabilities
 
 In the previous chapters, we learned about Agents as workers ([Chapter 1](01_agent.md)), how they can communicate directly or using announcements ([Chapter 2](02_messaging_system__topic___subscription_.md)), and the `AgentRuntime` that manages them ([Chapter 3](03_agentruntime.md)).

docs/AutoGen Core/05_chatcompletionclient.md

@@ -1,3 +1,10 @@
+---
+layout: default
+title: "ChatCompletionClient"
+parent: "AutoGen Core"
+nav_order: 5
+---
+
 # Chapter 5: ChatCompletionClient - Talking to the Brains
 
 So far, we've learned about:

docs/AutoGen Core/06_chatcompletioncontext.md

@@ -1,3 +1,10 @@
+---
+layout: default
+title: "ChatCompletionContext"
+parent: "AutoGen Core"
+nav_order: 6
+---
+
 # Chapter 6: ChatCompletionContext - Remembering the Conversation
 
 In [Chapter 5: ChatCompletionClient](05_chatcompletionclient.md), we learned how agents talk to Large Language Models (LLMs) using a `ChatCompletionClient`. We saw that we need to send a list of `messages` (the conversation history) to the LLM so it knows the context.

docs/AutoGen Core/07_memory.md

@@ -1,3 +1,10 @@
+---
+layout: default
+title: "Memory"
+parent: "AutoGen Core"
+nav_order: 7
+---
+
 # Chapter 7: Memory - The Agent's Notebook
 
 In [Chapter 6: ChatCompletionContext](06_chatcompletioncontext.md), we saw how agents manage the *short-term* history of a single conversation before talking to an LLM. It's like remembering what was just said in the last few minutes.

docs/AutoGen Core/08_component.md

@@ -1,3 +1,10 @@
+---
+layout: default
+title: "Component"
+parent: "AutoGen Core"
+nav_order: 8
+---
+
 # Chapter 8: Component - The Standardized Building Blocks
 
 Welcome to Chapter 8! In our journey so far, we've met several key players in AutoGen Core:

docs/AutoGen Core/index.md

@@ -1,3 +1,10 @@
+---
+layout: default
+title: "AutoGen Core"
+nav_order: 3
+has_children: true
+---
+
 # Tutorial: AutoGen Core
 
 AutoGen Core helps you build applications with multiple **_Agents_** that can work together.