Reorganize Docs (#311)

* setup nix flake

* reorganizing docs to avoid deeply nested sidebar

This commit moves primary sections into the top nav and uses unique sidebars for
each section. This commit also adds a non-generated index page to each
section where we can highlight specific pages that are likely to be most
interesting.

A few page urls were changed, redirects have been added.

* cp cli-index.md after autogeneration

Author: jordanstephens

.gitignore

@@ -23,3 +23,5 @@ defang
 samples
 /docs/samples.md
 /static/samples-v2.json
+.envrc
+.direnv

blog/2024-02-12-announcing-defang-public-beta.md

@@ -11,13 +11,13 @@ Ever since we shipped our Private Beta in the summer of 2023, we have been worki
 
 And so, today with our Public Beta, we are addressing this request. With today’s release of [Defang BYOC](/docs/concepts/defang-byoc) (Bring-your-own-Cloud), you can now enjoy all the benefits of Defang **and** deploy applications to your own AWS account! Our Private Beta experience is still available as [Defang Playground](/docs/concepts/defang-playground) for you to quickly and easily prototype applications and deploy them to our hosted environment.
 
-You can learn more about Defang [here](/docs/intro). Also check out our [tutorials](/docs/category/tutorials), [samples](https://defang.io/samples), and [FAQ](/docs/category/faq) to know more.
+You can learn more about Defang [here](/docs/intro). Also check out our [tutorials](/docs/tutorials), [samples](https://defang.io/samples), and [FAQ](/docs/category/faq) to know more.
 
 {/* truncate */}
 
 **Try the Public Beta!**
 
-To try the Public Beta, please go to [defang.io](http://defang.io) and click on [Download](https://github.com/DefangLabs/defang/releases/latest) to download the CLI and [get started](/docs/getting-started). We would love to have you kick the tires and give us your feedback! Once you sign up you’ll receive an invitation to our Slack support channel in email. You are also welcome to file [GitHub issues here](https://github.com/DefangLabs/defang/issues).
+To try the Public Beta, please go to [defang.io](http://defang.io) and click on [Download](https://github.com/DefangLabs/defang/releases/latest) to download the CLI and [get started](/docs/intro/getting-started). We would love to have you kick the tires and give us your feedback! Once you sign up you’ll receive an invitation to our Slack support channel in email. You are also welcome to file [GitHub issues here](https://github.com/DefangLabs/defang/issues).
 
 **Stay Tuned for More**
 

blog/2024-03-28-slackbot-sample.md

@@ -11,7 +11,7 @@ Hey folks! Today, I'm going to share one of our code samples that will show you
 
 Before we dive into the details, let's make sure you have everything you need to get started:
 
-1.  **Install Defang CLI:** Simplify your deployment process by installing the Defang CLI tool. Follow the instructions [here](/docs/getting-started#install-the-defang-cli) to get it up and running quickly.
+1.  **Install Defang CLI:** Simplify your deployment process by installing the Defang CLI tool. Follow the instructions [here](/docs/intro/getting-started#install-the-defang-cli) to get it up and running quickly.
 
 2.  **Slack API Token:** Create a Slack App at https://api.slack.com/apps, granting it the necessary permissions, including the bot `chat:write` scope.
 ![screenshot of the slack admin UI showing the bot scopes](/img/slackbot-sample/scopes.png)

blog/2025-02-18-model-context-protocol.md

@@ -132,7 +132,7 @@ Here we can see what changes if we deploy to the cloud:
 1. Service 1 and Service 2 are now deployed to the cloud, not on the local machine anymore.
 2. The only part on the local machine is the browser.
 
-Using the same `compose.yaml` file as shown earlier, we can deploy the containers to the cloud with the [Defang CLI](/docs/getting-started). Once we’ve authenticated and logged in, we can [choose a cloud provider (i.e. AWS, GCP, or DigitalOcean)](/docs/tutorials/deploy-to-your-cloud) and use our own cloud account for deployment. Then, we can set a configuration variable for the Anthropic API key:
+Using the same `compose.yaml` file as shown earlier, we can deploy the containers to the cloud with the [Defang CLI](/docs/intro/getting-started). Once we’ve authenticated and logged in, we can [choose a cloud provider (i.e. AWS, GCP, or DigitalOcean)](/docs/tutorials/deploy-to-your-cloud) and use our own cloud account for deployment. Then, we can set a configuration variable for the Anthropic API key:
 
 ```bash
 defang config set ANTHROPIC_API=<your-api-key-value>

blog/2025-04-10-easiest-way-to-deploy-django.md

@@ -93,7 +93,7 @@ Once deployed, your app is accessible via a public URL provided by Defang, which
 
 ### Deploying to Your Own Cloud
 
-To deploy directly into your AWS account (or other [supported providers](/docs/category/providers)):
+To deploy directly into your AWS account (or other [supported providers](/docs/providers)):
 
 1. Set your cloud provider:
 > In my case, I use an AWS Profile, but you should be able to use [any methods supported by the AWS CLI](https://docs.aws.amazon.com/cli/latest/userguide/cli-chap-configure.html)

cli-index.mdx

@@ -0,0 +1,42 @@
+---
+sidebar_position: 1
+title: Defang CLI Reference
+description: Learn about the Defang CLI
+---
+
+import DocCardList from "@docusaurus/theme-classic/lib/theme/DocCardList";
+
+The Defang CLI takes your app from Docker Compose to a secure and scalable deployment on your favorite cloud in minutes.
+
+# Featured Commands
+
+<DocCardList
+    items={[
+        {
+            type: "link",
+            href: "/docs/cli/compose-up",
+            label: "defang compose up",
+            description: "Learn how to deploy your application",
+        },
+        {
+            type: "link",
+            href: "/docs/cli/config-set",
+            label: "defang config set",
+            description: "Learn how to set configuration values for your deployment",
+        },
+        {
+            type: "link",
+            href: "/docs/cli/compose-logs",
+            label: "defang compose logs",
+            description: "Learn how to view your application logs",
+        },
+        {
+            type: "link",
+            href: "/docs/cli/compose-services",
+            label: "defang compose services",
+            description: "Learn how to view your deployed services",
+        },
+    ]}
+/>
+
+For a complete list of commands, check out the sidebar.

docs/cli/_category_.json

@@ -1,9 +1,8 @@
 {
   "label": "CLI",
-  "position": 500,
   "link": {
+    "slug": "cli",
     "type": "generated-index",
     "description": "Documentation of the Defang CLI (command line interface) commands."
   }
 }
-

docs/concepts/_category_.json

@@ -1,7 +1,7 @@
 {
   "label": "Concepts",
-  "position": 500,
   "link": {
+    "slug": "concepts",
     "type": "generated-index",
     "description": "Some concepts to help explain how the Defang system is organized and tooling that will help you manage your applications."
   }

docs/concepts/authentication.md

@@ -5,7 +5,7 @@ description: Authenticating with Defang.
 
 # Authentication
 
-To do pretty much anything with Defang, you'll need to authenticate with the system. You can do this by running the following command in the [CLI](/docs/getting-started):
+To do pretty much anything with Defang, you'll need to authenticate with the system. You can do this by running the following command in the [CLI](/docs/intro/getting-started):
 
 ```bash
 defang login

docs/concepts/configuration.md

@@ -95,9 +95,9 @@ If you have created a service before a secret you can connect it by running the
 
 Here are the different ways sensitive config values are stored depending on the provider you are using:
 
-    * [AWS](../providers/aws/aws.md#secrets)
-    * [DigitalOcean](../providers/digitalocean#secrets)
-    * [GCP](../providers/gcp#secrets)
+    * [AWS](/docs/providers/aws#secrets)
+    * [DigitalOcean](/docs/providers/digitalocean#secrets)
+    * [GCP](/docs/providers/gcp#secrets)
 
 :::info
 Please note that while Defang supports setting sensitive config, it does not support the [`secrets`](https://docs.docker.com/reference/compose-file/secrets/) top-level element as seen in the Compose specification. Please see our [Compose](/docs/concepts/compose) page for more details.