Merge pull request #105 from depot/docs-sync-updates

Update content from depot/app

Author: jacobwgillespie

content/cache/authentication.mdx

@@ -18,8 +18,8 @@ Depot Cache supports authenticating with user tokens and organization tokens. Ad
 
 For specific details on how to configure your build tools to authenticate with Depot Cache, refer to the following guides:
 
-- [Bazel](/docs/cache/bazel)
-- [Gradle](/docs/cache/gradle)
-- [Pants](/docs/cache/pants)
-- [sccache](/docs/cache/sccache)
-- [Turborepo](/docs/cache/turbo)
+- [Bazel](/docs/cache/reference/bazel)
+- [Gradle](/docs/cache/reference/gradle)
+- [Pants](/docs/cache/reference/pants)
+- [sccache](/docs/cache/reference/sccache)
+- [Turborepo](/docs/cache/reference/turbo)

content/cache/bazel.mdx renamed to content/cache/reference/bazel.mdx

@@ -101,7 +101,7 @@ If you want to build a specific target in the bake file, you can specify it in t
 depot bake -f docker-bake.hcl original
 ```
 
-You can also save all of the targets built in a bake or compose file to the [ephemeral registry](/docs/guides/ephemeral-registry) for later use with the `--save` flag:
+You can also save all of the targets built in a bake or compose file to the [ephemeral registry](/docs/container-builds/how-to-guides/ephemeral-registry) for later use with the `--save` flag:
 
 ```shell
 depot bake -f docker-bake.hcl --save

content/cache/gradle.mdx renamed to content/cache/reference/gradle.mdx

@@ -12,7 +12,7 @@ Depot removes emulation altogether.
 
 Depot is a remote Docker container build service that orchestrates optimized BuildKit builders on native CPUs for Intel (x86) and Arm (arm64).
 
-When a Docker image build is routed to Depot either via [`depot build`](/docs/cli/reference#depot-build) or [`docker build`](/docs/guides/docker-build#how-to-use-depot-with-docker), we launch optimized builders for each architecture requested with a persistent layer cache attached to them. Each builder has 16 CPUs, 32GB of memory, and at least 50GB of fast NVMe cache SSDs.
+When a Docker image build is routed to Depot either via [`depot build`](/docs/cli/reference#depot-build) or [`docker build`](/docs/container-builds/how-to-guides/docker-build#how-to-use-depot-with-docker), we launch optimized builders for each architecture requested with a persistent layer cache attached to them. Each builder has 16 CPUs, 32GB of memory, and at least 50GB of fast NVMe cache SSDs.
 
 ## How to build Docker images for Arm CPUs like M1/M2 MacBooks or AWS Graviton
 
@@ -32,14 +32,14 @@ docker build --platform linux/arm64 .
 
 We have integration guides for most of the CI providers:
 
-- [Bitbucket Pipelines](../integrations/bitbucket-pipelines)
-- [Buildkite](../integrations/buildkite)
-- [CircleCI](../integrations/circleci)
-- [GitHub Actions](../integrations/github-actions)
-- [GitLab CI](../integrations/gitlab-ci)
-- [Google Cloud Build](../integrations/google-cloud-build)
-- [Jenkins](../integrations/jenkins)
-- [Travis CI](../integrations/travis-ci)
+- [Bitbucket Pipelines](/docs/container-builds/reference/bitbucket-pipelines)
+- [Buildkite](/docs/container-builds/reference/buildkite)
+- [CircleCI](/docs/container-builds/reference/circleci)
+- [GitHub Actions](/docs/container-builds/reference/github-actions)
+- [GitLab CI](/docs/container-builds/reference/gitlab-ci)
+- [Google Cloud Build](/docs/container-builds/reference/google-cloud-build)
+- [Jenkins](/docs/container-builds/reference/jenkins)
+- [Travis CI](/docs/container-builds/reference/travis-ci)
 
 ## How to build multi-platform Docker images
 

content/cache/pants.mdx renamed to content/cache/reference/pants.mdx

@@ -10,18 +10,18 @@ Depot provides a remote Docker build service that makes the image build process
 
 By routing the image build step of your CI to Depot, you can complete the image build up to 40x faster than you could in your generic CI provider. Saving you build minutes in your existing CI provider and, more importantly, saving you developer time waiting for the build to finish.
 
-The `depot build` command is a drop-in replacement for `docker build` and `docker buildx build`. Alternatively, you can [configure your local Docker CLI to use Depot as the default builder](/docs/guides/docker-build). Depot launches remote builders for both native Intel & Arm CPUs with 16 CPUs, 32 GB of memory, and a 50 GB persistent NVMe cache SSD.
+The `depot build` command is a drop-in replacement for `docker build` and `docker buildx build`. Alternatively, you can [configure your local Docker CLI to use Depot as the default builder](/docs/container-builds/how-to-guides/docker-build). Depot launches remote builders for both native Intel & Arm CPUs with 16 CPUs, 32 GB of memory, and a 50 GB persistent NVMe cache SSD.
 
 Running `depot` in a continuous integration environment is a great way to get fast and consistent builds with any CI provider. See below for documentation on integrating Depot with your CI provider.
 
 ## Providers
 
-- [AWS CodeBuild](../integrations/aws-codebuild)
-- [Bitbucket Pipelines](../integrations/bitbucket-pipelines)
-- [Buildkite](../integrations/buildkite)
-- [CircleCI](../integrations/circleci)
-- [GitHub Actions](../integrations/github-actions)
-- [GitLab CI](../integrations/gitlab-ci)
-- [Google Cloud Build](../integrations/google-cloud-build)
-- [Jenkins](../integrations/jenkins)
-- [Travis CI](../integrations/travis-ci)
+- [AWS CodeBuild](/docs/container-builds/reference/aws-codebuild)
+- [Bitbucket Pipelines](/docs/container-builds/reference/bitbucket-pipelines)
+- [Buildkite](/docs/container-builds/reference/buildkite)
+- [CircleCI](/docs/container-builds/reference/circleci)
+- [GitHub Actions](/docs/container-builds/reference/github-actions)
+- [GitLab CI](/docs/container-builds/reference/gitlab-ci)
+- [Google Cloud Build](/docs/container-builds/reference/google-cloud-build)
+- [Jenkins](/docs/container-builds/reference/jenkins)
+- [Travis CI](/docs/container-builds/reference/travis-ci)