docs: remove best practice references

PR-URL: https://github.com/hasura/graphql-engine-mono/pull/6752
GitOrigin-RevId: 7d8a631ac540946846957fe50ce2c2464a0a1755

docs/docs/deployment/best-practices-for-production/index.mdx

@@ -1,23 +0,0 @@
----
-title: 'Best Practices'
-description: Best practices for running Hasura in production environments
-keywords:
-  - hasura
-  - docs
-  - guide
-  - best practices
-  - production
-slug: index
-sidebar_label: Best Practices for Production Environments
-sidebar_position: 105
----
-
-# Best Practices
-
-Best practices are the goal of all organizations with many different facets benefiting from those practices. This is
-particularly true with enterprise software and Hasura is no different. The guides below are broken down by category.
-
-- [Database Observability](/deployment/best-practices-for-production/db-observability.mdx)
-- [Metadata](/deployment/best-practices-for-production/metadata.mdx)
-- [Observability](/deployment/best-practices-for-production/observability.mdx)
-- [Security](/deployment/best-practices-for-production/security.mdx)

docs/docs/deployment/best-practices/_category_.json

@@ -0,0 +1,4 @@
+{
+    "label": "Best Practices",
+    "position": 40
+  }

docs/docs/deployment/best-practices/index.mdx

@@ -0,0 +1,22 @@
+---
+title: 'Best Practices'
+description: Best practices for running Hasura
+keywords:
+  - hasura
+  - docs
+  - guide
+  - best practices
+slug: index
+sidebar_label: Best Practices
+sidebar_position: 105
+---
+
+# Best Practices
+
+Best practices are the goal of all organizations with many different facets benefiting from those practices. This is
+particularly true with enterprise software and Hasura is no different. The guides below are broken down by category.
+
+- [Database Observability](/deployment/best-practices/db-observability.mdx)
+- [Metadata](/deployment/best-practices/metadata.mdx)
+- [Observability](/deployment/best-practices/observability.mdx)
+- [Security](/deployment/best-practices/security.mdx)

docs/docs/deployment/best-practices/security.mdx

@@ -1,10 +1,9 @@
 ---
-description: Security best practices for a production environment
+description: Security best practices
 keywords:
   - hasura
   - docs
   - best practices
-  - production
 sidebar_label: Security
 ---
 
@@ -14,8 +13,8 @@ import Thumbnail from '@site/src/components/Thumbnail';
 
 ## Introduction
 
-This guide reviews security best practices that should be implemented for a production environment. Applying API
+This guide reviews security best practices that should be implemented when working on a Hasura project. Applying API
-security beyond RBAC (role-based access control) permissions is mandatory for any API moving towards a production
+security beyond RBAC (role-based access control) permissions is mandatory for any API moving towards a Hasura
 deployment. We recommend that all HTTP layer security work be done at the API gateway level and GraphQL-specific
 policies be applied at the Hasura level.
 

docs/docs/deployment/health-checks/_category_.json

@@ -1,4 +1,4 @@
 {
   "label": "Health Checks",
-  "position": 40
+  "position": 50
 }

docs/docs/deployment/postgres-requirements.mdx

@@ -7,7 +7,7 @@ keywords:
   - postgres
   - postgres permissions
   - postgres version
-sidebar_position: 40
+sidebar_position: 60
 ---
 
 import Thumbnail from '@site/src/components/Thumbnail';

docs/docs/deployment/securing-graphql-endpoint.mdx

@@ -28,6 +28,6 @@ access to your GraphQL endpoint and the Hasura console:
 If you're looking at adding access control rules for your data to your GraphQL API then head to
 [Authentication / access control](/auth/index.mdx). You can also find more information about
 [Hasura security in general here](/security/index.mdx) and best practices
-[here](/deployment/best-practices-for-production/security.mdx).
+[here](/deployment/best-practices/security.mdx).
 
 :::