docs: change tutorial section name to be consistent

tianzhou · tianzhou · commit 0e718691a9bf · 2025-09-02T19:26:44.000+08:00
diff --git a/mintlify/docs.json b/mintlify/docs.json
@@ -136,10 +136,7 @@
           },
           {
             "group": "Appendix",
-            "pages": [
-              "sql-review/review-rules",
-              "sql-review/error-codes"
-            ]
+            "pages": ["sql-review/review-rules", "sql-review/error-codes"]
           }
         ]
       },
@@ -252,9 +249,7 @@
           },
           {
             "group": "Infrastructure as Code",
-            "pages": [
-              "integrations/terraform/overview"
-            ]
+            "pages": ["integrations/terraform/overview"]
           },
           {
             "group": "3rd Party",
@@ -272,7 +267,7 @@
         "tab": "Tutorials",
         "pages": [
           {
-            "group": "Database CI/CD (GUI)",
+            "group": "UI-Driven Workflow",
             "pages": [
               "tutorials/first-schema-change",
               "tutorials/deploy-schema-migration",
@@ -286,7 +281,7 @@
             ]
           },
           {
-            "group": "Database CI/CD (GitOps)",
+            "group": "GitOps Workflow",
             "pages": [
               "tutorials/gitops-github-workflow",
               "tutorials/gitops-azure-devops-workflow",
diff --git a/mintlify/tutorials/batch-change-with-database-group.mdx b/mintlify/tutorials/batch-change-with-database-group.mdx
@@ -4,7 +4,7 @@ author: Adela
 updated_at: 2025/08/11 18:00
 tags: Tutorial
 integrations: General
-category: 'Database CI/CD (GUI)'
+category: 'UI-Driven Workflow'
 level: Intermediate
 estimated_time: '20 mins'
 ---
@@ -37,6 +37,7 @@ Bytebase simplifies deploying changes across multiple databases simultaneously.
 1. In the new project, navigate to **Database > Databases** and click **+ New DB**. Create `demo-test` on the Test instance. Click **Rollout** when the issue appears.
 
 1. Similarly, create the following databases:
+
    - `demo-prod-1` and `demo-prod-2` on `ProdAsia`
    - `demo-prod-3` and `demo-prod-4` on `ProdEU`
    - `demo-prod-5` and `demo-prod-6` on `ProdNA`
@@ -90,14 +91,14 @@ We need first to upgrade to Pro/Enterprise Plan to use Database Group.
    ```
 
 1. The **Overview** and **Rollout** tabs now show 3 production stages. Click **Run** in the ProdAsia stage to execute.
-  
+
    ![bb-overview-3-stages](/content/docs/tutorials/batch-change-with-database-group/bb-overview-3-stages.webp)
    ![bb-rollout-3-stages](/content/docs/tutorials/batch-change-with-database-group/bb-rollout-3-stages.webp)
 
 ## Summary
 
-  You've learned how to:
-  
-  - Group databases by environment for staged rollouts
-  - Use Database Groups to target databases matching specific criteria
-  - Execute batch changes across multiple databases efficiently
+You've learned how to:
+
+- Group databases by environment for staged rollouts
+- Use Database Groups to target databases matching specific criteria
+- Execute batch changes across multiple databases efficiently
diff --git a/mintlify/tutorials/data-rollback.mdx b/mintlify/tutorials/data-rollback.mdx
@@ -4,7 +4,7 @@ author: Adela
 updated_at: 2025/08/11 16:15
 tags: Tutorial
 integrations: General
-category: 'Database CI/CD (GUI)'
+category: 'UI-Driven Workflow'
 featured: true
 level: Beginner
 estimated_time: '30 mins'
@@ -84,4 +84,9 @@ Bytebase stores backup data in a dedicated `bbdataarchive` schema (for PostgreSQ
 
 For MySQL, SQL Server, and Oracle, Bytebase uses a separate `bbdataarchive` **database** rather than a schema to store backups. See the documentation below for details.
 
-<Card title="Data Rollback Doc" icon="book" href="/change-database/rollback-data-changes/" horizontal />
+<Card
+  title="Data Rollback Doc"
+  icon="book"
+  href="/change-database/rollback-data-changes/"
+  horizontal
+/>
diff --git a/mintlify/tutorials/database-change-management-with-risk-adjusted-approval-flow.mdx b/mintlify/tutorials/database-change-management-with-risk-adjusted-approval-flow.mdx
@@ -4,14 +4,13 @@ author: Adela
 updated_at: 2023/06/01 16:15
 tags: Tutorial
 integrations: General
-category: 'Database CI/CD (GUI)'
+category: 'UI-Driven Workflow'
 level: Intermediate
 estimated_time: '15 mins'
 ---
 
 import TerminalDockerRunVolume from '/snippets/install/terminal-docker-run-volume.mdx';
 
-
 Bytebase provides a basic yet configurable rollout mechanism by default. This means that manual rollout is skipped for **Test** environments and required for **Prod** environments.
 
 However, for more complicated enterprise-level cases, users may need different approval flows to handle database changes according to different potential risks. For example, DDL in Prod environments is considered high risk, while DML in Test environments is low risk. Additionally, users may need to involve roles other than **DBA/Developer/Project Leader**, such as **Testers**.
@@ -89,8 +88,8 @@ To learn the best practice, check out [Risks Best Practice](/tutorials/risks-bes
 
 1. Either click **the related risk rules** or **CI/CD > Risks** on the left bar. Add two new rules
 
-   -  Name: `DDL ALTER`; Risk Level: `High`; Type: `DDL`; Condition: `sql_type == 'ALTER_TABLE'`
-   -  Name: `DDL CREATE`; Risk Level: `Moderate`; Type: `DDL`; Condition: `sql_type == 'CREATE_TABLE'`
+   - Name: `DDL ALTER`; Risk Level: `High`; Type: `DDL`; Condition: `sql_type == 'ALTER_TABLE'`
+   - Name: `DDL CREATE`; Risk Level: `Moderate`; Type: `DDL`; Condition: `sql_type == 'CREATE_TABLE'`
 
    ![bb-risks](/content/docs/tutorials/database-change-management-with-risk-adjusted-approval-flow/bb-risks.webp)
 
diff --git a/mintlify/tutorials/deploy-schema-migration.mdx b/mintlify/tutorials/deploy-schema-migration.mdx
@@ -4,7 +4,7 @@ author: Adela
 updated_at: 2025/08/08 12:00
 tags: Tutorial
 integrations: General
-category: 'Database CI/CD (GUI)'
+category: 'UI-Driven Workflow'
 level: Beginner
 estimated_time: '30 mins'
 featured: true
diff --git a/mintlify/tutorials/first-schema-change.mdx b/mintlify/tutorials/first-schema-change.mdx
@@ -4,7 +4,7 @@ author: Adela
 tags: Tutorial
 updated_at: 2024/10/10 20:00
 integrations: General
-category: 'Database CI/CD (GUI)'
+category: 'UI-Driven Workflow'
 level: Beginner
 estimated_time: '5 mins'
 featured: true
@@ -36,17 +36,19 @@ In this tutorial, you'll use the default sample databases to get familiar with t
    ![plan-change-type](/content/docs/change-database/plan/bb-plan-change-type.webp)
 
 1. Select the databases where changes will be applied:
-   - `hr_test` on `Test Sample instance` 
+
+   - `hr_test` on `Test Sample instance`
    - `hr_prod` on `Prod Sample instance`
-   
+
    Click **Confirm** to proceed.
    ![plan-targets](/content/docs/change-database/plan/bb-plan-targets.webp)
 
 1. Add the SQL statement:
+
    ```sql
    ALTER TABLE public.employee ADD COLUMN IF NOT EXISTS nickname TEXT;
    ```
-   
+
    Click **Create** to create the plan.
 
 1. The plan will be in `Draft` status. You may see SQL review warnings, especially for the production environment. This is because Bytebase automatically runs configured checks.
@@ -55,10 +57,11 @@ In this tutorial, you'll use the default sample databases to get familiar with t
 ## Step 4 - Review and Approve
 
 1. To fix the SQL review warning, edit the SQL to add `NOT NULL DEFAULT ''`:
+
    ```sql
    ALTER TABLE public.employee ADD COLUMN IF NOT EXISTS nickname TEXT NOT NULL DEFAULT '';
    ```
-   
+
    Click **Save** to update the plan. The checks will run again and should pass.
 
 1. Click **Ready for Review** and then **Confirm** to submit the plan for approval.
diff --git a/mintlify/tutorials/gitops-azure-devops-workflow.mdx b/mintlify/tutorials/gitops-azure-devops-workflow.mdx
@@ -4,7 +4,7 @@ author: Adela
 updated_at: 2025/03/28 18:00
 tags: Tutorial
 integrations: 'API, Azure DevOps'
-category: 'Database CI/CD (GitOps)'
+category: 'GitOps Workflow'
 level: Advanced
 estimated_time: '40 mins'
 ---
diff --git a/mintlify/tutorials/gitops-bitbucket-workflow.mdx b/mintlify/tutorials/gitops-bitbucket-workflow.mdx
@@ -4,7 +4,7 @@ author: Adela
 updated_at: 2025/05/14 18:00
 tags: Tutorial
 integrations: Bitbucket
-category: 'Database CI/CD (GitOps)'
+category: 'GitOps Workflow'
 level: Advanced
 estimated_time: '40 mins'
 ---
diff --git a/mintlify/tutorials/gitops-github-workflow.mdx b/mintlify/tutorials/gitops-github-workflow.mdx
@@ -4,7 +4,7 @@ author: Adela
 updated_at: 2025/05/22 18:00
 tags: Tutorial
 integrations: GitHub
-category: 'Database CI/CD (GitOps)'
+category: 'GitOps Workflow'
 level: Advanced
 estimated_time: '40 mins'
 ---
diff --git a/mintlify/tutorials/gitops-gitlab-workflow.mdx b/mintlify/tutorials/gitops-gitlab-workflow.mdx
@@ -4,7 +4,7 @@ author: Adela
 updated_at: 2025/05/12 18:00
 tags: Tutorial
 integrations: GitLab
-category: 'Database CI/CD (GitOps)'
+category: 'GitOps Workflow'
 level: Advanced
 estimated_time: '40 mins'
 featured: true
diff --git a/mintlify/tutorials/how-to-move-schema-change-from-test-to-prod.mdx b/mintlify/tutorials/how-to-move-schema-change-from-test-to-prod.mdx
@@ -4,7 +4,7 @@ author: Ayra
 updated_at: 2025/08/05 18:00
 tags: Tutorial
 integrations: General
-category: 'Database CI/CD (GUI)'
+category: 'UI-Driven Workflow'
 level: Beginner
 estimated_time: '5 mins'
 description: 'Learn to move schema change from test to prod.'
@@ -33,6 +33,7 @@ This method ensures consistent changes across environments and maintains a clear
 Use this method when changes already exist in test and need to be replicated to production:
 
 1. First, apply changes to the test database:
+
    - Navigate to **CI/CD > Plans** and click **+ New Plan**.
    - Select **Schema Migration** and choose only the `test` database.
    - Enter your SQL changes and click **Create**.
@@ -50,6 +51,7 @@ Use this method when changes already exist in test and need to be replicated to
    ![select-target-databases-1](/content/docs/tutorials/how-to-move-schema-change-from-test-to-prod/select-target-databases-1.webp)
 
 4. Review the schema differences:
+
    - Bytebase displays a detailed diff between test (source) and prod (target).
    - Verify the changes match your expectations.
    - Click **Preview issue** to proceed.
diff --git a/mintlify/tutorials/how-to-synchronize-database-schemas.mdx b/mintlify/tutorials/how-to-synchronize-database-schemas.mdx
@@ -5,7 +5,7 @@ updated_at: 2025/08/11 18:00
 feature_image: /content/docs/tutorials/how-to-synchronize-database-schemas/workflow.webp
 tags: Tutorial
 integrations: General
-category: 'Database CI/CD (GUI)'
+category: 'UI-Driven Workflow'
 level: Beginner
 estimated_time: '10 mins'
 ---
@@ -15,6 +15,7 @@ import PreparationWithSampleData from '/snippets/tutorials/preparation-with-samp
 Database schema synchronization ensures consistency across multiple databases by replicating schema changes from a source to target databases. This eliminates manual SQL writing and reduces deployment errors.
 
 Bytebase's **Sync Schema** feature enables:
+
 - Replicating schemas to new databases
 - Synchronizing changes across environments (dev → staging → prod)
 - Rolling back to previous schema versions
@@ -66,6 +67,7 @@ Use this for:
 1. Select **Schema Migration** and choose only `hr_test` as the target database.
 
 1. Use the **Schema Editor** to add a new column:
+
    - **Name**: `email`
    - **Type**: `text`
    - **Default**: `Empty string`
diff --git a/mintlify/tutorials/risks-best-practice.mdx b/mintlify/tutorials/risks-best-practice.mdx
@@ -4,7 +4,7 @@ author: Cayden
 updated_at: 2025/04/08 16:15
 tags: Tutorial
 integrations: General
-category: 'Database CI/CD (GUI)'
+category: 'UI-Driven Workflow'
 level: Beginner
 estimated_time: '30 mins'
 description: This tutorial shows you how to configure risk rules in Bytebase to manage changes effectively.
@@ -130,4 +130,7 @@ In addition to the key risk conditions, you can incorporate more risk conditions
 
 ## Step-to-step Tutorial
 
-<TutorialBlock url="/docs/tutorials/database-change-management-with-risk-adjusted-approval-flow" title="Database Change with Risk-Based Approval Flow" />
+<TutorialBlock
+  url="/docs/tutorials/database-change-management-with-risk-adjusted-approval-flow"
+  title="Database Change with Risk-Based Approval Flow"
+/>
diff --git a/mintlify/tutorials/sql-review-gui.mdx b/mintlify/tutorials/sql-review-gui.mdx
@@ -4,7 +4,7 @@ author: Adela
 updated_at: 2025/02/24 16:15
 tags: Tutorial
 level: Intermediate
-category: 'Database CI/CD (GUI)'
+category: 'UI-Driven Workflow'
 estimated_time: '20 mins'
 ---
 
diff --git a/src/components/pages/tutorial/posts/posts.tsx b/src/components/pages/tutorial/posts/posts.tsx
@@ -51,12 +51,7 @@ type PostsProps = {
   posts: BlogPost[];
 };
 // Define sections
-const sections = [
-  'Database CI/CD (GUI)',
-  'Database CI/CD (GitOps)',
-  'Data Access Control',
-  'Integration',
-];
+const sections = ['UI-Driven Workflow', 'GitOps Workflow', 'Data Access Control', 'Integration'];
 
 // Define the card component to avoid repetition
 const TutorialCard = ({ post }: { post: BlogPost }) => {

Original file line number	Diff line number	Diff line change
`@@ -136,10 +136,7 @@`
`136`	`136`	`},`
`137`	`137`	`{`
`138`	`138`	`"group": "Appendix",`
`139`		`- "pages": [`
`140`		`- "sql-review/review-rules",`
`141`		`- "sql-review/error-codes"`
`142`		`- ]`
	`139`	`+ "pages": ["sql-review/review-rules", "sql-review/error-codes"]`
`143`	`140`	`}`
`144`	`141`	`]`
`145`	`142`	`},`
`@@ -252,9 +249,7 @@`
`252`	`249`	`},`
`253`	`250`	`{`
`254`	`251`	`"group": "Infrastructure as Code",`
`255`		`- "pages": [`
`256`		`- "integrations/terraform/overview"`
`257`		`- ]`
	`252`	`+ "pages": ["integrations/terraform/overview"]`
`258`	`253`	`},`
`259`	`254`	`{`
`260`	`255`	`"group": "3rd Party",`
`@@ -272,7 +267,7 @@`
`272`	`267`	`"tab": "Tutorials",`
`273`	`268`	`"pages": [`
`274`	`269`	`{`
`275`		`- "group": "Database CI/CD (GUI)",`
	`270`	`+ "group": "UI-Driven Workflow",`
`276`	`271`	`"pages": [`
`277`	`272`	`"tutorials/first-schema-change",`
`278`	`273`	`"tutorials/deploy-schema-migration",`
`@@ -286,7 +281,7 @@`
`286`	`281`	`]`
`287`	`282`	`},`
`288`	`283`	`{`
`289`		`- "group": "Database CI/CD (GitOps)",`
	`284`	`+ "group": "GitOps Workflow",`
`290`	`285`	`"pages": [`
`291`	`286`	`"tutorials/gitops-github-workflow",`
`292`	`287`	`"tutorials/gitops-azure-devops-workflow",`