From a8e65c36acd42bf39a719d86f330a5a84ea21ba7 Mon Sep 17 00:00:00 2001 From: barnettZQG Date: Thu, 28 Apr 2022 12:03:09 +0800 Subject: [PATCH] Fix: fix the error of link path Signed-off-by: barnettZQG --- docs/getting-started/introduction.md | 4 +--- .../current/getting-started/introduction.md | 2 +- .../version-v1.3/getting-started/introduction.md | 2 +- versioned_docs/version-v1.3/getting-started/introduction.md | 4 +--- versioned_sidebars/version-v1.3-sidebars.json | 2 +- 5 files changed, 5 insertions(+), 9 deletions(-) diff --git a/docs/getting-started/introduction.md b/docs/getting-started/introduction.md index 38d494a8..1b8417b0 100644 --- a/docs/getting-started/introduction.md +++ b/docs/getting-started/introduction.md @@ -1,7 +1,6 @@ --- title: Introduction slug: / - --- ## What is KubeVela? @@ -34,8 +33,7 @@ Using KubeVela, software teams can build cloud native applications per needs as KubeVela is a continuous delivery platform that works at downstream of your CI process. So you will reuse the CI process you already adopted, and KubeVela will take over CD process by empowering it with modern application delivery best practices, such as hybrid/multi-cloud promotion workflow, unified cloud resource provision/binding, and much more. KubeVela is fully declarative by design, it natively supports GitOps if you want. -> Feel free to check the [Integrating with Jenkins](../tutorials/jenkins) or [GitOps](../case-studies/gitops) documentation for more details. - +> Feel free to check the [Integrating with Jenkins](./tutorials/jenkins) or [GitOps](./case-studies/gitops) documentation for more details. ### KubeVela vs. GitOps (ArgoCD, FluxCD, etc.) diff --git a/i18n/zh/docusaurus-plugin-content-docs/current/getting-started/introduction.md b/i18n/zh/docusaurus-plugin-content-docs/current/getting-started/introduction.md index fd8af342..e6a19643 100644 --- a/i18n/zh/docusaurus-plugin-content-docs/current/getting-started/introduction.md +++ b/i18n/zh/docusaurus-plugin-content-docs/current/getting-started/introduction.md @@ -42,7 +42,7 @@ KubeVela 是一个工作在 CI 流程下游的 CD 控制平面（Continuous Deli 如果你已经在 CD 环节中采纳了 GitOps 实践，KubeVela 会更容易跟你的 CI/CD 系统集成，因为 KubeVela 是完全声明式的。只需要把 KubeVela 的应用部署描述文件放置在你的配置仓库当中，所有的 KubeVela 特性（包括声明式交付工作流、多云/多集群交付流程等）就会立刻在你 的 GitOps 流程中出现。 -> 欢迎查阅用户手册来了解更多关于 KubeVela 与[各类 CI/CD 系统](../tutorials/jenkins)以及 [GitOps](../case-studies/gitops) 模式协作的实践. +> 欢迎查阅用户手册来了解更多关于 KubeVela 与[各类 CI/CD 系统](./tutorials/jenkins)以及 [GitOps](./case-studies/gitops) 模式协作的实践. ### KubeVela vs. GitOps ( 如 ArgoCD，FluxCD 等) diff --git a/i18n/zh/docusaurus-plugin-content-docs/version-v1.3/getting-started/introduction.md b/i18n/zh/docusaurus-plugin-content-docs/version-v1.3/getting-started/introduction.md index fd8af342..e6a19643 100644 --- a/i18n/zh/docusaurus-plugin-content-docs/version-v1.3/getting-started/introduction.md +++ b/i18n/zh/docusaurus-plugin-content-docs/version-v1.3/getting-started/introduction.md @@ -42,7 +42,7 @@ KubeVela 是一个工作在 CI 流程下游的 CD 控制平面（Continuous Deli 如果你已经在 CD 环节中采纳了 GitOps 实践，KubeVela 会更容易跟你的 CI/CD 系统集成，因为 KubeVela 是完全声明式的。只需要把 KubeVela 的应用部署描述文件放置在你的配置仓库当中，所有的 KubeVela 特性（包括声明式交付工作流、多云/多集群交付流程等）就会立刻在你 的 GitOps 流程中出现。 -> 欢迎查阅用户手册来了解更多关于 KubeVela 与[各类 CI/CD 系统](../tutorials/jenkins)以及 [GitOps](../case-studies/gitops) 模式协作的实践. +> 欢迎查阅用户手册来了解更多关于 KubeVela 与[各类 CI/CD 系统](./tutorials/jenkins)以及 [GitOps](./case-studies/gitops) 模式协作的实践. ### KubeVela vs. GitOps ( 如 ArgoCD，FluxCD 等) diff --git a/versioned_docs/version-v1.3/getting-started/introduction.md b/versioned_docs/version-v1.3/getting-started/introduction.md index 38d494a8..1b8417b0 100644 --- a/versioned_docs/version-v1.3/getting-started/introduction.md +++ b/versioned_docs/version-v1.3/getting-started/introduction.md @@ -1,7 +1,6 @@ --- title: Introduction slug: / - --- ## What is KubeVela? @@ -34,8 +33,7 @@ Using KubeVela, software teams can build cloud native applications per needs as KubeVela is a continuous delivery platform that works at downstream of your CI process. So you will reuse the CI process you already adopted, and KubeVela will take over CD process by empowering it with modern application delivery best practices, such as hybrid/multi-cloud promotion workflow, unified cloud resource provision/binding, and much more. KubeVela is fully declarative by design, it natively supports GitOps if you want. -> Feel free to check the [Integrating with Jenkins](../tutorials/jenkins) or [GitOps](../case-studies/gitops) documentation for more details. - +> Feel free to check the [Integrating with Jenkins](./tutorials/jenkins) or [GitOps](./case-studies/gitops) documentation for more details. ### KubeVela vs. GitOps (ArgoCD, FluxCD, etc.) diff --git a/versioned_sidebars/version-v1.3-sidebars.json b/versioned_sidebars/version-v1.3-sidebars.json index 4969ae1f..24974060 100644 --- a/versioned_sidebars/version-v1.3-sidebars.json +++ b/versioned_sidebars/version-v1.3-sidebars.json @@ -536,4 +536,4 @@ "id": "version-v1.3/developers/references/devex/faq" } ] -} \ No newline at end of file +}