Update meta data of docs

versioned_docs/version-1.21/usage/actions/act-runner.md

@@ -1,16 +1,9 @@
 ---
 date: "2023-04-27T15:00:00+08:00"
-title: "Act Runner"
+
 slug: "act-runner"
 sidebar_position: 20
-draft: false
-toc: false
-menu:
-  sidebar:
-    parent: "actions"
-    name: "Act Runner"
-    sidebar_position: 20
-    identifier: "actions-runner"
+
 ---
 
 # Act Runner

versioned_docs/version-1.21/usage/actions/comparison.md

@@ -1,16 +1,7 @@
 ---
 date: "2023-04-27T15:00:00+08:00"
-title: "Compared to GitHub Actions"
 slug: "comparison"
 sidebar_position: 30
-draft: false
-toc: false
-menu:
-  sidebar:
-    parent: "actions"
-    name: "Comparison"
-    sidebar_position: 30
-    identifier: "actions-comparison"
 ---
 
 # Compared to GitHub Actions

versioned_docs/version-1.21/usage/actions/design.md

@@ -1,16 +1,7 @@
 ---
 date: "2023-04-27T15:00:00+08:00"
-title: "Design of Gitea Actions"
 slug: "design"
 sidebar_position: 40
-draft: false
-toc: false
-menu:
-  sidebar:
-    parent: "actions"
-    name: "Design"
-    sidebar_position: 40
-    identifier: "actions-design"
 ---
 
 # Design of Gitea Actions

versioned_docs/version-1.21/usage/actions/faq.md

@@ -1,16 +1,7 @@
 ---
 date: "2023-04-27T15:00:00+08:00"
-title: "Frequently Asked Questions of Gitea Actions"
 slug: "faq"
 sidebar_position: 100
-draft: false
-toc: false
-menu:
-  sidebar:
-    parent: "actions"
-    name: "FAQ"
-    sidebar_position: 100
-    identifier: "actions-faq"
 ---
 
 # Frequently Asked Questions of Gitea Actions

versioned_docs/version-1.21/usage/actions/overview.md

@@ -1,16 +1,9 @@
 ---
 date: "2023-04-27T15:00:00+08:00"
-title: "Gitea Actions"
+
 slug: "overview"
 sidebar_position: 1
-draft: false
-toc: false
-menu:
-  sidebar:
-    parent: "actions"
-    name: "Overview"
-    sidebar_position: 1
-    identifier: "actions-overview"
+
 ---
 
 # Gitea Actions

versioned_docs/version-1.21/usage/actions/quickstart.md

@@ -1,16 +1,9 @@
 ---
 date: "2023-04-27T15:00:00+08:00"
-title: "Quick Start"
+
 slug: "quickstart"
 sidebar_position: 10
-draft: false
-toc: false
-menu:
-  sidebar:
-    parent: "actions"
-    name: "Quick Start"
-    sidebar_position: 10
-    identifier: "actions-quickstart"
+
 ---
 
 # Quick Start

versioned_docs/version-1.21/usage/actions/variables.md

@@ -1,10 +1,7 @@
 ---
 date: "2024-04-10T22:21:00+08:00"
-title: "Variables"
 slug: "actions-variables"
 sidebar_position: 25
-draft: false
-toc: false
 menu:
   sidebar:
     parent: "actions"
@@ -13,13 +10,13 @@ menu:
     identifier: "actions-variables"
 ---
 
-## Variables
+# Variables
 
 You can create configuration variables on the user, organization and repository level.
 The level of the variable depends on where you created it. When creating a variable, the
 key will be converted to uppercase. You need use uppercase on the yaml file.
 
-### Naming conventions
+## Naming conventions
 
 The following rules apply to variable names:
 
@@ -30,12 +27,12 @@ The following rules apply to variable names:
 - Variable names must be unique at the level they are created at.
 - Variable names must not be `CI`.
 
-### Using variable
+## Using variable
 
 After creating configuration variables, they will be automatically filled in the `vars` context.
 They can be accessed through expressions like `${{ vars.VARIABLE_NAME }}` in the workflow.
 
-### Precedence
+## Precedence
 
 If a variable with the same name exists at multiple levels, the variable at the lowest level takes precedence:
 A repository variable will always be chosen over an organization/user variable.