Fix: chinese version and index
Signed-off-by: Jianbo Sun <jianbo.sjb@alibaba-inc.com>
This commit is contained in:
Jianbo Sun
parent
2aa896a1cf
commit
03895b3408
|
|
@ -9,7 +9,6 @@ KubeVela is a modern application platform that makes deploying and managing appl
|
|||
## Community
|
||||
|
||||
- Slack: [CNCF Slack](https://slack.cncf.io/) #kubevela channel
|
||||
- Gitter: [Discussion](https://gitter.im/oam-dev/community)
|
||||
- Bi-weekly Community Call: [Meeting Notes](https://docs.google.com/document/d/1nqdFEyULekyksFHtFvgvFAYE-0AMHKoS3RMnaKsarjs)
|
||||
|
||||
## Installation
|
||||
|
|
|
|||
|
|
@ -15,7 +15,8 @@ There're two sources of definitions:
|
|||
- [Trait Definition](../end-user/traits/references)
|
||||
- [Policy Definition](../end-user/policies/references)
|
||||
- [Workflow Step Definition](../end-user/workflow/built-in-workflow-defs)
|
||||
* Installation of addons will install definitions if there're new capabilities contained. You can refer to [the community addon registry](../reference/addons/overview) for more details.
|
||||
* Installation of addons will install definitions if there're new capabilities contained.
|
||||
- [Addon registry](../reference/addons/overview) contains a large catalog of addon which are maintained and verified by the KubeVela team.
|
||||
|
||||
## Lifecycle of a Definition
|
||||
|
||||
|
|
|
|||
|
|
@ -60,6 +60,11 @@ module.exports = {
|
|||
label: "Videos",
|
||||
position: "left",
|
||||
},
|
||||
{
|
||||
href: "https://github.com/kubevela/community",
|
||||
label: "Community",
|
||||
position: "left",
|
||||
},
|
||||
{
|
||||
href: "https://kubevela.net",
|
||||
label: "Mirror",
|
||||
|
|
@ -90,8 +95,8 @@ module.exports = {
|
|||
to: '/docs/tutorials/webservice',
|
||||
},
|
||||
{
|
||||
label: 'Extension',
|
||||
to: '/docs/platform-engineers/oam/oam-model',
|
||||
label: 'Core Concepts',
|
||||
to: '/docs/getting-started/core-concept',
|
||||
},
|
||||
],
|
||||
},
|
||||
|
|
@ -100,7 +105,7 @@ module.exports = {
|
|||
items: [
|
||||
{
|
||||
label: 'CNCF Slack ( #kubevela channel )',
|
||||
href: 'https://slack.cncf.io/',
|
||||
href: 'https://cloud-native.slack.com/archives/C01BLQ3HTJA',
|
||||
},
|
||||
{
|
||||
label: 'DingTalk (23310022)',
|
||||
|
|
@ -122,6 +127,10 @@ module.exports = {
|
|||
label: 'Blog',
|
||||
to: 'blog',
|
||||
},
|
||||
{
|
||||
label: 'Videos',
|
||||
to: 'videos/best-practice/jenkins',
|
||||
},
|
||||
],
|
||||
},
|
||||
],
|
||||
|
|
|
|||
|
|
@ -156,7 +156,7 @@
|
|||
"description": "The skip to content label used for accessibility, allowing to rapidly navigate to main content with keyboard tab/enter navigation"
|
||||
},
|
||||
"Make shipping applications more enjoyable.": {
|
||||
"message": "让应用交付更简单、高效、可靠"
|
||||
"message": "让应用交付更愉快！"
|
||||
},
|
||||
"KubeVela models platform features (such as workloads, operational behaviors, and cloud services) as reusable": {
|
||||
"message": "KubeVela 将平台功能（如工作负载、运维操作行为和云服务）抽象建模为可重用的"
|
||||
|
|
@ -201,34 +201,34 @@
|
|||
"message": "KubeVela 是什么？"
|
||||
},
|
||||
"Deployment as Code": {
|
||||
"message": "统一的应用交付模型"
|
||||
"message": "应用部署即代码（Deployment as Code），完整定义全交付流程"
|
||||
},
|
||||
"Declare your deployment plan as workflow, run it automatically with any CI/CD or GitOps system, extend or re-program the workflow steps with CUE. No add-hoc scripts, no dirty glue code, just deploy. The deployment workflow in KubeVela is powered by Open Application Model.": {
|
||||
"message": "KubeVela 创新性的提出了开放应用模型（OAM）来作为应用交付的顶层抽象，该模型支持交付任意类型的工作负载包括容器、数据库甚至是虚拟机到不同的云和 Kubernetes 集群中。用户无需关心任何基础设施细节，只需要专注于定义和部署应用即可。应用只需要一次编排，就可以随处运行，免去了适配不同平台的痛苦。"
|
||||
"message": "用声明式的方式描述你的应用交付工作流，自动化的集成 CI/CD 或 GitOps 体系，通过 CUE 轻松扩展或重新编写你的交付过程。再也没有难以维护的脚本和复杂的衔接代码，直接复用社区丰富的模块，无需关注任何基础设施细节，专注于定义和部署应用！KubeVela 部署工作流的背后就是 OAM 模型，帮助你一次编排、随处运行！"
|
||||
},
|
||||
"Built-in security and compliance building blocks": {
|
||||
"message": "自动化跨集群交付"
|
||||
"message": "天然支持企业级集成，安全、合规一应俱全"
|
||||
},
|
||||
"Choose from the wide range of LDAP integrations we provided out-of-box, enjoy multi-cluster authorization that is fully automated, pick and apply fine-grained RBAC modules and customize them per your own supply chain requirements.": {
|
||||
"message": "KubeVela 的整个交付模型完全是由用户声明式驱动的，兼顾用户体验和健壮性，其控制循环能够有效避免配置漂移，且具备多租权限控制能力。用户可以通过 CUE 语言（一种源自 Google Borg 系统的数据配置语言）自由的根据需求场景来设计和选用交付工作流中的每一个步骤，满足业务快速增长的需求，同时持续保证生产环境面向终态的稳定性。"
|
||||
"message": "天然支持多集群安全和 RBAC 集成，你还可以从社区的插件中心找到一系列开箱即用的平台扩展，包括多种用户体系（LDAP 等）集成、多租户权限控制、安全校验和扫描、应用可观测性等大量企业级能力。轻松根据需求和场景来设计和定制你的平台扩展能力，满足业务快速增长的需求，同时持续保证生产环境的稳定和安全。"
|
||||
},
|
||||
"Multi-cloud/hybrid-environments app delivery as first-class citizen": {
|
||||
"message": "声明式高可扩展工作流"
|
||||
"message": "面向多云多集群混合环境，丰富的应用交付和管理能力"
|
||||
},
|
||||
"Progressive rollout across test/staging/production environments, automatic canary, blue-green and continuous verification, rich placement strategy across clusters and clouds, fully managed cloud environments provision.": {
|
||||
"message": "KubeVela 原生支持丰富的多集群/混合环境持续交付策略，也支持跨环境交付。这些交付策略为你的分布式交付流程提供了充足的效率和安全的保证。KubeVela 提供的中心化管控能力也减轻了到每一个集群去排查问题的负担，针对不同的平台提供统一的体验，为了享受自动化交付的便利，你再也不需要成为 Kubernetes 专家。"
|
||||
"message": "原生支持丰富的多集群/混合环境持续交付策略，包括金丝雀、蓝绿、多环境差异化配置等，同样也支持跨环境交付。这些交付策略为你的分布式交付流程提供了充足的效率和安全保证。KubeVela 提供的中心化管控能力也减轻了到每一个集群（云）去排查问题的负担，针对不同的平台提供统一的体验，让你享受自动化交付的便利。"
|
||||
},
|
||||
"KubeVela is a": {
|
||||
"message": "KubeVela 是一个"
|
||||
},
|
||||
"sandbox project": {
|
||||
"message": "沙箱级项目"
|
||||
"project.": {
|
||||
"message": "项目。"
|
||||
},
|
||||
"KubeVela is a modern software delivery platform that makes deploying and operating applications across today's hybrid, multi-cloud environments": {
|
||||
"message": "KubeVela 是一个现代化的软件交付平台，它可以让你的应用交付在当今流行的混合、多云环境中变得更加"
|
||||
},
|
||||
" easier, faster and more reliable.": {
|
||||
"message": "简单、轻松、可靠。"
|
||||
"message": "简单、高效、可靠。"
|
||||
},
|
||||
"KubeVela is infrastructure agnostic, programmable, yet most importantly,": {
|
||||
"message": "KubeVela 是基础设施无关的、可编程的，但最重要的是："
|
||||
|
|
|
|||
|
|
@ -215,7 +215,7 @@
|
|||
"message": "资源管理",
|
||||
"description": "管理集群和交付目标等资源"
|
||||
},
|
||||
"sidebar.docs.category.Community Addons": {
|
||||
"sidebar.docs.category.Community Verified Addons": {
|
||||
"message": "社区认证插件",
|
||||
"description": "内置插件说明"
|
||||
},
|
||||
|
|
|
|||
|
|
@ -11,7 +11,7 @@ KubeVela 的核心是将应用部署所需的所有组件和各项运维动作
|
|||
|
||||
|
||||
|
||||
每一个应用部署计划都you四个部分组成，分别是组件、运维能力、部署策略和工作流。其格式如下：
|
||||
每一个应用部署计划都由四个部分组成，分别是组件、运维能力、部署策略和工作流。其格式如下：
|
||||
|
||||
```yaml
|
||||
apiVersion: core.oam.dev/v1beta1
|
||||
|
|
@ -55,7 +55,7 @@ spec:
|
|||
|
||||
* **工作流步骤（Workflow Step）**: 工作流由多个步骤组成，允许用户自定义应用在某个环境的交付过程。典型的工作流步骤包括人工审核、数据传递、多集群发布、通知等。
|
||||
|
||||
以上这些概念的背后都是由一组称为[模块定义（Definitions）](../platform-engineers/oam/x-definition)的可编程模块提供具体功能的。KubeVela 会像胶水一样基于 Kubernetes API 定义基础设施定义的抽象并将不同的能力组合起来。下图描述了概念间的关系：
|
||||
以上这些概念的背后都是由一组称为[模块定义（Definitions）](../platform-engineers/oam/x-definition)的可编程模块提供具体功能。KubeVela 会像胶水一样基于 Kubernetes API 定义基础设施定义的抽象并将不同的能力组合起来。下图描述了概念间的关系：
|
||||
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -6,7 +6,7 @@ Definition are the basic building block of the KubeVela platform. A definition e
|
|||
|
||||
There're four types of Definition, they're `ComponentDefinition`, `TraitDefinition`, `PolicyDefinition` and `WorkflowStepDefinition`, corresponding to the application concepts.
|
||||
|
||||
## Sources of Definitions
|
||||
## 模块定义的来源
|
||||
|
||||
There're two sources of definitions:
|
||||
|
||||
|
|
@ -15,7 +15,8 @@ There're two sources of definitions:
|
|||
- [Trait Definition](../end-user/traits/references)
|
||||
- [Policy Definition](../end-user/policies/references)
|
||||
- [Workflow Step Definition](../end-user/workflow/built-in-workflow-defs)
|
||||
* Installation of addons will install definitions if there're new capabilities contained. You can refer to [the community addon registry](../reference/addons/overview) for more details.
|
||||
* Installation of addons will install definitions if there're new capabilities contained.
|
||||
- [Addon registry](../reference/addons/overview) contains a large catalog of addon which are maintained and verified by the KubeVela team.
|
||||
|
||||
## Lifecycle of a Definition
|
||||
|
||||
|
|
|
|||
|
|
@ -21,17 +21,17 @@ KubeVela 是一个开箱即用的现代化应用交付与管理平台，它使
|
|||
|
||||
## KubeVela 核心功能
|
||||
|
||||
- **统一的应用交付模型**
|
||||
- **应用部署即代码（Deployment as Code），完整定义全交付流程**
|
||||
|
||||
KubeVela 创新性的提出了 [开放应用模型（OAM）](https://oam.dev/)来作为应用交付的顶层抽象，该模型支持交付任意类型的工作负载包括容器、数据库甚至是虚拟机到不同的云和 Kubernetes 集群中。用户无需关心任何基础设施细节，只需要专注于定义和部署应用即可。应用只需要一次编排，就可以随处运行，免去了适配不同平台的痛苦。
|
||||
KubeVela 创新性的通过 [开放应用模型（OAM）](https://oam.dev/)来作为应用交付的顶层抽象，这种方式使你可以用声明式的方式描述应用交付全流程，自动化的集成 CI/CD 及 GitOps 体系，通过 [CUE](https://cuelang.org/) 轻松扩展或重新编写你的交付过程。再也没有难以维护的脚本和复杂的衔接代码，复用社区丰富的功能模块，且无需关注任何基础设施细节，专注于定义和部署应用，一次编排、随处运行！
|
||||
|
||||
- **天然支持企业级集成，安全、合规一应俱全**
|
||||
|
||||
- **声明式交付工作流**
|
||||
KubeVela 天然支持多集群安全和 RBAC 集成，你还可以从社区的插件中心找到一系列开箱即用的平台扩展，包括多种用户体系（LDAP 等）集成、多租户权限控制、安全校验和扫描、应用可观测性等大量企业级能力。轻松根据需求和场景来设计和定制你的平台扩展能力，满足业务快速增长的需求，同时持续保证生产环境的稳定和安全。
|
||||
|
||||
KubeVela 的整个交付模型完全是由用户声明式驱动的，兼顾用户体验和健壮性，其控制循环能够有效避免配置漂移，且具备多租权限控制能力。用户可以通过 [CUE 语言](https://cuelang.org/)（一种源自 Google Borg 系统的数据配置语言）自由的根据需求场景来设计和选用交付工作流中的每一个步骤，满足业务快速增长的需求，同时持续保证生产环境面向终态的稳定性。
|
||||
- **面向多云多集群混合环境，丰富的应用交付和管理能力**
|
||||
|
||||
- **多集群/混合云应用交付控制平面**
|
||||
|
||||
KubeVela 原生支持丰富的多集群/混合环境持续交付策略，也支持跨环境交付。这些交付策略为你的分布式交付流程提供了充足的效率和安全的保证。KubeVela 提供的中心化管控能力也减轻了到每一个集群去排查问题的负担，针对不同的平台提供统一的体验，为了享受自动化交付的便利，你再也不需要成为 Kubernetes 专家。
|
||||
KubeVela 原生支持丰富的多集群/混合环境持续交付策略，包括金丝雀、蓝绿、多环境差异化配置等，同样也支持跨环境交付。这些交付策略为你的分布式交付流程提供了充足的效率和安全保证。KubeVela 提供的中心化管控能力也减轻了到每一个集群（云）去排查问题的负担，针对不同的平台提供统一的体验，让你享受自动化交付的便利。
|
||||
|
||||
|
||||
## KubeVela 与其他软件形态对比
|
||||
|
|
|
|||
|
|
@ -1,5 +1,5 @@
|
|||
---
|
||||
title: 附录：CUE 操作符
|
||||
title: CUE 操作符
|
||||
---
|
||||
|
||||
这个文档介绍 step 定义过程中，可以使用的 CUE 操作类型。这些操作均由 `vela/op` 包提供。
|
||||
|
|
|
|||
|
|
@ -308,5 +308,9 @@
|
|||
},
|
||||
"sidebar.docs.category.UX Customization": {
|
||||
"message": "定制 UI"
|
||||
},
|
||||
"sidebar.docs.category.Community Verified Addons": {
|
||||
"message": "社区认证插件",
|
||||
"description": "内置插件说明"
|
||||
}
|
||||
}
|
||||
|
|
@ -11,7 +11,7 @@ KubeVela 的核心是将应用部署所需的所有组件和各项运维动作
|
|||
|
||||
|
||||
|
||||
每一个应用部署计划都you四个部分组成，分别是组件、运维能力、部署策略和工作流。其格式如下：
|
||||
每一个应用部署计划都由四个部分组成，分别是组件、运维能力、部署策略和工作流。其格式如下：
|
||||
|
||||
```yaml
|
||||
apiVersion: core.oam.dev/v1beta1
|
||||
|
|
@ -55,7 +55,7 @@ spec:
|
|||
|
||||
* **工作流步骤（Workflow Step）**: 工作流由多个步骤组成，允许用户自定义应用在某个环境的交付过程。典型的工作流步骤包括人工审核、数据传递、多集群发布、通知等。
|
||||
|
||||
以上这些概念的背后都是由一组称为[模块定义（Definitions）](../platform-engineers/oam/x-definition)的可编程模块提供具体功能的。KubeVela 会像胶水一样基于 Kubernetes API 定义基础设施定义的抽象并将不同的能力组合起来。下图描述了概念间的关系：
|
||||
以上这些概念的背后都是由一组称为[模块定义（Definitions）](../platform-engineers/oam/x-definition)的可编程模块提供具体功能。KubeVela 会像胶水一样基于 Kubernetes API 定义基础设施定义的抽象并将不同的能力组合起来。下图描述了概念间的关系：
|
||||
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -6,7 +6,7 @@ Definition are the basic building block of the KubeVela platform. A definition e
|
|||
|
||||
There're four types of Definition, they're `ComponentDefinition`, `TraitDefinition`, `PolicyDefinition` and `WorkflowStepDefinition`, corresponding to the application concepts.
|
||||
|
||||
## Sources of Definitions
|
||||
## 模块定义的来源
|
||||
|
||||
There're two sources of definitions:
|
||||
|
||||
|
|
@ -15,7 +15,8 @@ There're two sources of definitions:
|
|||
- [Trait Definition](../end-user/traits/references)
|
||||
- [Policy Definition](../end-user/policies/references)
|
||||
- [Workflow Step Definition](../end-user/workflow/built-in-workflow-defs)
|
||||
* Installation of addons will install definitions if there're new capabilities contained. You can refer to [the community addon registry](../reference/addons/overview) for more details.
|
||||
* Installation of addons will install definitions if there're new capabilities contained.
|
||||
- [Addon registry](../reference/addons/overview) contains a large catalog of addon which are maintained and verified by the KubeVela team.
|
||||
|
||||
## Lifecycle of a Definition
|
||||
|
||||
|
|
|
|||
|
|
@ -21,17 +21,17 @@ KubeVela 是一个开箱即用的现代化应用交付与管理平台，它使
|
|||
|
||||
## KubeVela 核心功能
|
||||
|
||||
- **统一的应用交付模型**
|
||||
- **应用部署即代码（Deployment as Code），完整定义全交付流程**
|
||||
|
||||
KubeVela 创新性的提出了 [开放应用模型（OAM）](https://oam.dev/)来作为应用交付的顶层抽象，该模型支持交付任意类型的工作负载包括容器、数据库甚至是虚拟机到不同的云和 Kubernetes 集群中。用户无需关心任何基础设施细节，只需要专注于定义和部署应用即可。应用只需要一次编排，就可以随处运行，免去了适配不同平台的痛苦。
|
||||
KubeVela 创新性的通过 [开放应用模型（OAM）](https://oam.dev/)来作为应用交付的顶层抽象，这种方式使你可以用声明式的方式描述应用交付全流程，自动化的集成 CI/CD 及 GitOps 体系，通过 [CUE](https://cuelang.org/) 轻松扩展或重新编写你的交付过程。再也没有难以维护的脚本和复杂的衔接代码，复用社区丰富的功能模块，且无需关注任何基础设施细节，专注于定义和部署应用，一次编排、随处运行！
|
||||
|
||||
- **天然支持企业级集成，安全、合规一应俱全**
|
||||
|
||||
- **声明式交付工作流**
|
||||
KubeVela 天然支持多集群安全和 RBAC 集成，你还可以从社区的插件中心找到一系列开箱即用的平台扩展，包括多种用户体系（LDAP 等）集成、多租户权限控制、安全校验和扫描、应用可观测性等大量企业级能力。轻松根据需求和场景来设计和定制你的平台扩展能力，满足业务快速增长的需求，同时持续保证生产环境的稳定和安全。
|
||||
|
||||
KubeVela 的整个交付模型完全是由用户声明式驱动的，兼顾用户体验和健壮性，其控制循环能够有效避免配置漂移，且具备多租权限控制能力。用户可以通过 [CUE 语言](https://cuelang.org/)（一种源自 Google Borg 系统的数据配置语言）自由的根据需求场景来设计和选用交付工作流中的每一个步骤，满足业务快速增长的需求，同时持续保证生产环境面向终态的稳定性。
|
||||
- **面向多云多集群混合环境，丰富的应用交付和管理能力**
|
||||
|
||||
- **多集群/混合云应用交付控制平面**
|
||||
|
||||
KubeVela 原生支持丰富的多集群/混合环境持续交付策略，也支持跨环境交付。这些交付策略为你的分布式交付流程提供了充足的效率和安全的保证。KubeVela 提供的中心化管控能力也减轻了到每一个集群去排查问题的负担，针对不同的平台提供统一的体验，为了享受自动化交付的便利，你再也不需要成为 Kubernetes 专家。
|
||||
KubeVela 原生支持丰富的多集群/混合环境持续交付策略，包括金丝雀、蓝绿、多环境差异化配置等，同样也支持跨环境交付。这些交付策略为你的分布式交付流程提供了充足的效率和安全保证。KubeVela 提供的中心化管控能力也减轻了到每一个集群（云）去排查问题的负担，针对不同的平台提供统一的体验，让你享受自动化交付的便利。
|
||||
|
||||
|
||||
## KubeVela 与其他软件形态对比
|
||||
|
|
|
|||
|
|
@ -1,5 +1,5 @@
|
|||
---
|
||||
title: 附录：CUE 操作符
|
||||
title: CUE 操作符
|
||||
---
|
||||
|
||||
这个文档介绍 step 定义过程中，可以使用的 CUE 操作类型。这些操作均由 `vela/op` 包提供。
|
||||
|
|
|
|||
|
|
@ -1,5 +1,5 @@
|
|||
---
|
||||
title: Overview
|
||||
title: 内置插件包
|
||||
---
|
||||
|
||||
There's an community addon registry (https://addons.kubevela.net) maintained by KubeVela team. It contains following addons:
|
||||
|
|
|
|||
|
|
@ -19,22 +19,18 @@
|
|||
"message": "实践教程",
|
||||
"description": "The label of footer link with label=Getting Case Studies to /docs/case-studies"
|
||||
},
|
||||
"link.item.label.Extension": {
|
||||
"message": "自定义扩展",
|
||||
"description": "The label of footer link with label=Administrator Manuals linking to /docs/platform-engineers/overview"
|
||||
"link.item.label.Core Concepts": {
|
||||
"message": "核心概念",
|
||||
"description": "The label of footer link with label=Core Concepts linking to /docs/getting-started/core-concept"
|
||||
},
|
||||
"link.item.label.User Manuals": {
|
||||
"message": "用户手册",
|
||||
"description": "The label of footer link with label=User Manuals linking to /docs/end-user/application"
|
||||
},
|
||||
"link.item.label.CNCF Slack ( #kubevela channel )": {
|
||||
"message": "CNCF Slack ( #kubevela channel )",
|
||||
"message": "CNCF Slack ( #kubevela 频道 )",
|
||||
"description": "The label of footer link with label=CNCF Slack ( #kubevela channel ) linking to https://slack.cncf.io/"
|
||||
},
|
||||
"link.item.label.Gitter": {
|
||||
"message": "Gitter",
|
||||
"description": "The label of footer link with label=Gitter linking to https://gitter.im/oam-dev/community"
|
||||
},
|
||||
"link.item.label.DingTalk (23310022)": {
|
||||
"message": "钉钉 (23310022)",
|
||||
"description": "The label of footer link with label=DingTalk (23310022) linking to ."
|
||||
|
|
@ -47,8 +43,12 @@
|
|||
"message": "博客",
|
||||
"description": "The label of footer link with label=Blog linking to blog"
|
||||
},
|
||||
"link.item.label.Videos": {
|
||||
"message": "视频资料",
|
||||
"description": "The label of footer link with label=Video linking to video resources"
|
||||
},
|
||||
"copyright": {
|
||||
"message": "\n <br />\n <strong>© KubeVela Authors 2021 | Documentation Distributed under <a herf=\"https://creativecommons.org/licenses/by/4.0\">CC-BY-4.0</a> </strong> \n <br />\n ",
|
||||
"message": "\n <br />\n <strong>© KubeVela Authors 2022 | Documentation Distributed under <a herf=\"https://creativecommons.org/licenses/by/4.0\">CC-BY-4.0</a> </strong> \n <br />\n ",
|
||||
"description": "The footer copyright"
|
||||
}
|
||||
}
|
||||
|
|
@ -13,7 +13,11 @@
|
|||
},
|
||||
"item.label.Videos": {
|
||||
"message": "视频",
|
||||
"description": "Navbar item with label Video"
|
||||
"description": "Navbar item with label Videos"
|
||||
},
|
||||
"item.label.Community": {
|
||||
"message": "社区",
|
||||
"description": "Navbar item with label Community"
|
||||
},
|
||||
"item.label.Mirror": {
|
||||
"message": "国内加速",
|
||||
|
|
|
|||
|
|
@ -206,7 +206,7 @@ module.exports = {
|
|||
'platform-engineers/workflow/cue-actions',
|
||||
{
|
||||
type: 'category',
|
||||
label: 'Community Addons',
|
||||
label: 'Community Verified Addons',
|
||||
items: [
|
||||
'reference/addons/overview',
|
||||
'reference/addons/velaux',
|
||||
|
|
|
|||
|
|
@ -50,12 +50,12 @@ export default function Home() {
|
|||
<div className="container text--center">
|
||||
<div className={styles.heroLogoWrapper}>
|
||||
<ThemedImage
|
||||
alt="Kubevela Logo"
|
||||
className={styles.heroLogo}
|
||||
sources={{
|
||||
light: useBaseUrl('img/logo.svg'),
|
||||
dark: useBaseUrl('img/logoDark.svg'),
|
||||
}}
|
||||
alt="Kubevela Logo"
|
||||
className={styles.heroLogo}
|
||||
sources={{
|
||||
light: useBaseUrl('img/logo.svg'),
|
||||
dark: useBaseUrl('img/logoDark.svg'),
|
||||
}}
|
||||
/>
|
||||
</div>
|
||||
<h2 className={clsx('hero__title', styles.heroTitle)}>{siteConfig.title}</h2>
|
||||
|
|
@ -68,7 +68,7 @@ export default function Home() {
|
|||
Star
|
||||
</GitHubButton>
|
||||
<p className="hero__subtitle">
|
||||
<Translate>Make shipping applications more enjoyable.</Translate>
|
||||
<Translate>Make shipping applications more enjoyable.</Translate>
|
||||
</p>
|
||||
<div
|
||||
className={clsx(styles.heroButtons, 'name', 'margin-vert--md')}>
|
||||
|
|
@ -94,7 +94,7 @@ export default function Home() {
|
|||
<div className={clsx('hero', styles.hero)}>
|
||||
<div className="container text--center">
|
||||
<h3 className="hero__subtitle">
|
||||
<Translate>KubeVela is a</Translate> <a href="https://cncf.io/">CNCF (Cloud Native Computing Foundation)</a> <Translate>sandbox project</Translate>
|
||||
<Translate>KubeVela is a</Translate> <a href="https://cncf.io/">CNCF (Cloud Native Computing Foundation)</a> <Translate>project.</Translate>
|
||||
</h3>
|
||||
<div className={clsx('cncf-logo', styles.cncfLogo)} />
|
||||
</div>
|
||||
|
|
|
|||
|
|
@ -9,7 +9,6 @@ KubeVela is a modern application platform that makes deploying and managing appl
|
|||
## Community
|
||||
|
||||
- Slack: [CNCF Slack](https://slack.cncf.io/) #kubevela channel
|
||||
- Gitter: [Discussion](https://gitter.im/oam-dev/community)
|
||||
- Bi-weekly Community Call: [Meeting Notes](https://docs.google.com/document/d/1nqdFEyULekyksFHtFvgvFAYE-0AMHKoS3RMnaKsarjs)
|
||||
|
||||
## Installation
|
||||
|
|
|
|||
|
|
@ -15,7 +15,8 @@ There're two sources of definitions:
|
|||
- [Trait Definition](../end-user/traits/references)
|
||||
- [Policy Definition](../end-user/policies/references)
|
||||
- [Workflow Step Definition](../end-user/workflow/built-in-workflow-defs)
|
||||
* Installation of addons will install definitions if there're new capabilities contained. You can refer to [the community addon registry](../reference/addons/overview) for more details.
|
||||
* Installation of addons will install definitions if there're new capabilities contained.
|
||||
- [Addon registry](../reference/addons/overview) contains a large catalog of addon which are maintained and verified by the KubeVela team.
|
||||
|
||||
## Lifecycle of a Definition
|
||||
|
||||
|
|
|
|||
|
|
@ -507,7 +507,7 @@
|
|||
{
|
||||
"collapsed": true,
|
||||
"type": "category",
|
||||
"label": "Community Addons",
|
||||
"label": "Community Verified Addons",
|
||||
"items": [
|
||||
{
|
||||
"type": "doc",
|
||||
|
|
|
|||
Loading…
Reference in New Issue