GitHub Integration
@@ -156,10 +156,10 @@ import Cloud from '@site/static/icons/features/cloud.svg';
Cloud providers: AWS, Google Cloud
- GitHub integration
+ GitHub integration
- Preview apps
+ Preview apps
Community support
@@ -245,7 +245,7 @@ import Cloud from '@site/static/icons/features/cloud.svg';
-
+
Custom domain (DNS CNAME)
diff --git a/docs/docs/hasura-cloud/projects/_category_.json b/docs/docs/hasura-cloud/projects/_category_.json
index e221c9c6d02..b43cca34a4f 100644
--- a/docs/docs/hasura-cloud/projects/_category_.json
+++ b/docs/docs/hasura-cloud/projects/_category_.json
@@ -1,5 +1,4 @@
{
"label": "Projects & collaborators ",
- "position": 20,
- "className": "cloud-icon"
+ "position": 20
}
diff --git a/docs/docs/hasura-cloud/projects/index.mdx b/docs/docs/hasura-cloud/projects/index.mdx
index 2012825ed57..8ac55fab44c 100644
--- a/docs/docs/hasura-cloud/projects/index.mdx
+++ b/docs/docs/hasura-cloud/projects/index.mdx
@@ -65,13 +65,13 @@ programmatically.
- [Project Collaborators](/hasura-cloud/projects/collaborators.mdx)
- [Transfer Ownership](/hasura-cloud/projects/ownership.mdx)
- [Project Env vars](/hasura-cloud/projects/env-vars.mdx)
-- [Project Domains](/hasura-cloud/projects/domains.mdx)
+- [Project Domains](/hasura-cloud/domains.mdx)
+- [Managing development environments](/hasura-cloud/environments.mdx)
- [Securing projects](/hasura-cloud/projects/secure.mdx)
- [Switching pricing plans](/hasura-cloud/projects/pricing.mdx)
- [Deployment regions](/hasura-cloud/projects/regions.mdx)
-- [Managing development environments](/hasura-cloud/projects/environments.mdx)
-- [Heroku database integration](/hasura-cloud/projects/heroku-url-sync.mdx)
-- [Vercel Integration](/hasura-cloud/projects/vercel-integration.mdx)
+- [Heroku database integration](/hasura-cloud/heroku-url-sync.mdx)
+- [Vercel Integration](/hasura-cloud/vercel-integration.mdx)
- [Maintenance mode](/hasura-cloud/projects/maintenance-mode.mdx)
- [Deleting projects](/hasura-cloud/projects/delete.mdx)
- [Updating v1.3 projects to v2.0](/hasura-cloud/projects/move-project-v2.mdx)
diff --git a/docs/docs/hasura-cloud/projects/maintenance-mode.mdx b/docs/docs/hasura-cloud/projects/maintenance-mode.mdx
index 171e3dbce66..df7baa020d2 100644
--- a/docs/docs/hasura-cloud/projects/maintenance-mode.mdx
+++ b/docs/docs/hasura-cloud/projects/maintenance-mode.mdx
@@ -55,7 +55,7 @@ actions are disallowed:
- [Switching pricing plans](/hasura-cloud/projects/pricing.mdx)
- [Adding, updating and deleting an environment variable](/hasura-cloud/projects/env-vars.mdx)
- [Changing project region](/hasura-cloud/projects/regions.mdx)
-- [Enabling and disabling Heroku database URL sync](/hasura-cloud/projects/heroku-url-sync.mdx)
+- [Enabling and disabling Heroku database URL sync](/hasura-cloud/heroku-url-sync.mdx)
- [Deleting project](/hasura-cloud/projects/delete.mdx)
If you are trying to apply these changes when maintenance mode is activated, you will encounter an error.
diff --git a/docs/docs/hasura-cloud/projects/move-project-manual.mdx b/docs/docs/hasura-cloud/projects/move-project-manual.mdx
index dce1c1e25aa..e2675d89142 100644
--- a/docs/docs/hasura-cloud/projects/move-project-manual.mdx
+++ b/docs/docs/hasura-cloud/projects/move-project-manual.mdx
@@ -64,13 +64,13 @@ See [deleting projects](/hasura-cloud/projects/delete.mdx) to delete the earlier
- You can [rename](/hasura-cloud/projects/details.mdx#rename-project) your new project to the same name as the earlier
project if you wish.
-- If you haven't renamed your new project or set up a [custom domain](/hasura-cloud/projects/domains.mdx) for your
+- If you haven't renamed your new project or set up a [custom domain](/hasura-cloud/domains.mdx) for your
project, you might want to update any clients consuming the GraphQL API to point to the new project's GraphQL
endpoint.
## Zero-downtime transfer
-To achieve a zero-downtime transfer, you will need to have a [custom domain](/hasura-cloud/projects/domains.mdx)
+To achieve a zero-downtime transfer, you will need to have a [custom domain](/hasura-cloud/domains.mdx)
attached to your Cloud project. Once the new project is set up identically as the old one, you can update the DNS
entries for your custom domain to the new project to have a seamless transfer of traffic to the new project.
diff --git a/docs/docs/hasura-cloud/regions.mdx b/docs/docs/hasura-cloud/regions.mdx
index 2ba38ea3cb9..2e803f9ef0d 100644
--- a/docs/docs/hasura-cloud/regions.mdx
+++ b/docs/docs/hasura-cloud/regions.mdx
@@ -5,7 +5,8 @@ keywords:
- hasura
- cloud
- regions
-sidebar_position: 7
+sidebar_position: 11
+sidebar_label: Supported regions
---
import Thumbnail from '@site/src/components/Thumbnail';
diff --git a/docs/docs/hasura-cloud/projects/vercel-integration.mdx b/docs/docs/hasura-cloud/vercel-integration.mdx
similarity index 98%
rename from docs/docs/hasura-cloud/projects/vercel-integration.mdx
rename to docs/docs/hasura-cloud/vercel-integration.mdx
index c6850ff6bd6..d2a86ed4b31 100644
--- a/docs/docs/hasura-cloud/projects/vercel-integration.mdx
+++ b/docs/docs/hasura-cloud/vercel-integration.mdx
@@ -7,7 +7,7 @@ keywords:
- docs
- vercel
- integration
-sidebar_position: 13
+sidebar_position: 34
sidebar_label: Vercel integration
---
@@ -155,7 +155,7 @@ Your integration will only be successfully configured upon clicking the `Install
:::info Note
-- If a [custom domain](/hasura-cloud/projects/domains.mdx) is added to the Hasura Cloud project, you'll have to set this
+- If a [custom domain](/hasura-cloud/domains.mdx) is added to the Hasura Cloud project, you'll have to set this
custom value to `HASURA_PROJECT_ENDPOINT` and `NEXT_HASURA_PROJECT_ENDPOINT` manually in the respective Vercel
project's settings.
- Similarly if the Hasura Cloud project's admin secret is changed, you will have to edit the `HASURA_ADMIN_SECRET`
diff --git a/docs/docs/migrations-metadata-seeds/legacy-configs/_category_.json b/docs/docs/migrations-metadata-seeds/legacy-configs/_category_.json
index 8c0463f7798..6f660d9d61a 100644
--- a/docs/docs/migrations-metadata-seeds/legacy-configs/_category_.json
+++ b/docs/docs/migrations-metadata-seeds/legacy-configs/_category_.json
@@ -1,4 +1,4 @@
{
"label": "Legacy Configs",
- "position": 10
+ "position": 100
}
diff --git a/docs/docs/migrations-metadata-seeds/metadata-best-practices.mdx b/docs/docs/migrations-metadata-seeds/metadata-best-practices.mdx
index d2dfd0e5e1d..8118557dcaa 100644
--- a/docs/docs/migrations-metadata-seeds/metadata-best-practices.mdx
+++ b/docs/docs/migrations-metadata-seeds/metadata-best-practices.mdx
@@ -5,6 +5,7 @@ keywords:
- docs
- best practices
sidebar_label: Metadata Best Practices
+sidebar_position: 11
---
# Metadata Best Practices
@@ -36,7 +37,7 @@ real-world practices, user experiences, and challenges when managing enterprise-
:::info Note
-Hasura Cloud users can leverage the [GitHub integration](/hasura-cloud/ci-cd/github-integration.mdx) to automate
+Hasura Cloud users can leverage the [GitHub integration](/cloud-ci-cd/github-integration.mdx) to automate
deployments.
:::
diff --git a/docs/docs/migrations-metadata-seeds/resetting-migrations-metadata.mdx b/docs/docs/migrations-metadata-seeds/resetting-migrations-metadata.mdx
index 215337ec1f4..8a5521f77eb 100644
--- a/docs/docs/migrations-metadata-seeds/resetting-migrations-metadata.mdx
+++ b/docs/docs/migrations-metadata-seeds/resetting-migrations-metadata.mdx
@@ -1,6 +1,6 @@
---
sidebar_label: Reset Migrations and Metadata
-sidebar_position: 7
+sidebar_position: 10
description: Reset Hasura Migrations and Metadata
keywords:
- hasura