guardrails-ai · zsimjee · Feb 15, 2024 · Feb 15, 2024
diff --git a/docs/concepts/prompts_instructions.md → ...raveyard/concepts/prompts_instructions.md b/docs/concepts/prompts_instructions.md → ...raveyard/concepts/prompts_instructions.md
diff --git a/docs/concepts/reasking.md → docs-graveyard/concepts/reasking.md b/docs/concepts/reasking.md → docs-graveyard/concepts/reasking.md
diff --git a/docs/defining_guards/pydantic.ipynb → ...-graveyard/defining_guards/pydantic.ipynb b/docs/defining_guards/pydantic.ipynb → ...-graveyard/defining_guards/pydantic.ipynb
diff --git a/docs/defining_guards/strings.ipynb → docs-graveyard/defining_guards/strings.ipynb b/docs/defining_guards/strings.ipynb → docs-graveyard/defining_guards/strings.ipynb
diff --git a/docs/how_to_guides/envars.md → docs/how_to_guides/envvars.md b/docs/how_to_guides/envars.md → docs/how_to_guides/envvars.md
@@ -1,4 +1,4 @@
-# Environment Variables
+# Set API Keys and other Environment Variables
 
 Guardrails recognize a handful of environment variables that can be used at runtime.  Most of these correlate to envinronment variables used or expected by the various LLM clients.  Below you can find a list of these and their uses.
 

diff --git a/docs/how_to_guides/llm_api_wrappers.md b/docs/how_to_guides/llm_api_wrappers.md
@@ -1,4 +1,4 @@
-# Custom LLMs
+# Guard Custom LLMs
 
 Guardrails' `Guard` wrappers provide a simple way to add Guardrails to your LLM API calls. The wrappers are designed to be used with any LLM API.
 

diff --git a/docs/how_to_guides/logs.md b/docs/how_to_guides/logs.md
@@ -1,8 +1,8 @@
-# Logs
+# Inspect Guard Run History and Logs
 
 All `Guard` calls are logged internally, and can be accessed via the guard history.
 
-## 🇻🇦 Accessing logs via `Guard.history`
+## Accessing logs via `Guard.history`
 
 `history` is an attribute of the `Guard` class. It implements a standard `Stack` interface with a few extra helper methods and properties.  For more information on our `Stack` implementation see the [Helper Classes](/docs/api_reference_markdown/helper_classes) page.
 

diff --git a/docs/how_to_guides/rail.md b/docs/how_to_guides/rail.md
diff --git a/docs/how_to_guides/streaming.ipynb b/docs/how_to_guides/streaming.ipynb
@@ -4,7 +4,7 @@
    "cell_type": "markdown",
    "metadata": {},
    "source": [
-    "# Example of using OpenAI streaming with Guardrails\n"
+    "# Validate Streamed LLM Responses\n"
    ]
   },
   {

diff --git a/docs/concepts/guard.md → docs/the_guard.md b/docs/concepts/guard.md → docs/the_guard.md
@@ -1,13 +1,12 @@
-# Guard
-
+# The Guard
 
 The guard object is the main interface for GuardRails. It is seeded with a RailSpec, and then used to run the GuardRails AI engine. It is the object that accepts changing prompts, wraps LLM prompts, and keeps track of call history.
 
 
 ## How it works
 
-![Guardrails Logo](../img/guardrails_arch_white_vertical.png#only-light)
-![Guardrails Logo](../img/guardrails_arch_dark_vertical.png#only-dark)
+![Guardrails Logo](./img/guardrails_arch_white_vertical.png#only-light)
+![Guardrails Logo](./img/guardrails_arch_dark_vertical.png#only-dark)
 
 
 ## Two main flows

diff --git a/docusaurus/sidebars.js b/docusaurus/sidebars.js
@@ -42,49 +42,31 @@ const sidebars = {
     },
     {
       type: "category",
-      label: "Defining Guardrails",
+      label: "How-to Guides",
       collapsed: true,
-      items: ["defining_guards/pydantic", "defining_guards/strings"],
+      items: ["how_to_guides/logs", "how_to_guides/streaming", "how_to_guides/llm_api_wrappers", "how_to_guides/rail", "how_to_guides/envvars" ],
     },
+    "the_guard",
     {
       type: "category",
-      label: "How-to Guides",
+      label: "API Reference",
       collapsed: true,
       items: [
         {
           type: "autogenerated",
-          dirName: "how_to_guides",
+          dirName: "api_reference_markdown",
         },
       ],
     },
+    examples,
     {
       type: "category",
-      label: "Concepts",
-      collapsed: true,
-      items: [
-        "concepts/guard",
-        // "concepts/validators",
-        "concepts/reasking",
-        // "concepts/output",
-        // "concepts/prompt",
-        // "concepts/instructions",
-        // "concepts/logs",
-        // "concepts/envars",
-      ],
-    },
-    // {
-    //   type: "doc",
-    //   id: "api_reference_markdown/validators",
-    //   label: "Validator Library"
-    // },
-    {
-      type: "category",
-      label: "API Reference",
+      label: "Integrations",
       collapsed: true,
       items: [
         {
           type: "autogenerated",
-          dirName: "api_reference_markdown",
+          dirName: "integrations",
         },
       ],
     },
@@ -93,27 +75,16 @@ const sidebars = {
       label: "Migration Guides",
       collapsed: false,
       items: [
-        "migration_guides/0-2-migration",
+        "migration_guides/0-4-migration",
         "migration_guides/0-3-migration",
+        "migration_guides/0-2-migration",
       ],
     },
     {
       type: "doc",
       id: "faq",
       label: "FAQ",
     },
-    examples,
-    {
-      type: "category",
-      label: "Integrations",
-      collapsed: true,
-      items: [
-        {
-          type: "autogenerated",
-          dirName: "integrations",
-        },
-      ],
-    },
   ],
   hubSidebar: [
     "hub/introduction",