feat: add Multilingual data.params

Signed-off-by: Jie Ding <jie.ding@linkall.com>
2022-06-09 23:36:03 +08:00 · 2022-06-09 23:36:03 +08:00 · 1fa3876e28
parent e3b985fcf5
commit 1fa3876e28
4 changed files with 352 additions and 0 deletions
--- a/data/en/integrations.yaml
+++ b/data/en/integrations.yaml
@ -0,0 +1,115 @@
+- name: Adobe I/O Events
+  description: |
+    Adobe I/O Events embrace event-driven architecture to streamline workflows, improve marketing performance, and more, by allowing developers to programmatically respond to user behavior, resulting in near real-time customer experiences that are targeted, effective and personalized.
+  url: https://www.adobe.io/apis/experienceplatform/events.html
+  logo: adobeioeventslogo.jpg
+- name: Alibaba Cloud EventBridge
+  description: |
+    A serverless event bus that receives CloudEvents compliant events from cloud services, SaaS/custom apps, and routes to various targets
+  url: https://www.aliyun.com/product/aliware/eventbridge
+  logo: alibaba-cloud-eventbridge.png
+- name: Argo Events
+  description: |
+    Argo Events is a CloudEvents compliant event-driven workflow automation framework for Kubernetes
+  url: https://github.com/argoproj/argo-events
+  logo: argo-events.png
+- name: Azure Event Grid
+  description: |
+    Event Grid natively supports events in the [JSON implementation of CloudEvents v1.0](https://github.com/cloudevents/spec/blob/v1.0/json-format.md) and the [HTTP protocol binding](https://github.com/cloudevents/spec/blob/v1.0/http-protocol-binding.md)
+  url: https://azure.microsoft.com/en-us/services/event-grid
+  logo: event-grid.png
+- name: Choria
+  description: |
+    All Life Cycle and Autonomous Agent events emitted by the Choria orchestration system are CloudEvents compliant
+  url: https://choria.io/blog/post/2019/12/05/cloudevents_transition
+  logo: choria.png
+- name: commercetools
+  description: |
+    All services of the commercetools platform can emit CloudEvents compliant events
+  url: https://www.commercetools.com
+  logo: commercetools.png
+- name: Debezium
+  description: |
+    Debezium, a distributed open-source change data capture platform, can emit change data events [in the CloudEvents format](https://debezium.io/documentation/reference/integrations/cloudevents.html)
+  url: https://debezium.io/
+  logo: debezium.png
+- name: Direktiv
+  description: |
+    Direktiv, a serverless workflow engine, which can take in [cloud events](https://docs.direktiv.io/docs/events/events.html) to trigger workflows.
+  url: https://direktiv.io
+  logo: direktiv.png
+- name: Falco
+  description: |
+    Falco is a threat detection engine for Kubernetes that can emit cloud events for security policy violations at runtime.
+  url: https://falco.org
+  logo: falco.png 
+- name: Google Cloud Eventarc
+  description: |
+    Eventarc is a managed infrastructure that allows you to build event-driven architectures with loosely coupled services that react to state changes.
+  url: https://cloud.google.com/eventarc/docs/
+  logo: googlecloud.png
+- name: IBM Cloud Code Engine
+  description: |
+    Code Engine is a fully managed, serverless platform designed to run container images, batch jobs, or source code. Code Engine allows you to build event driven workloads that react to Cloud Events.
+  url: https://cloud.ibm.com/codeengine
+  logo: codeengine.svg
+- name: Keptn
+  description: |
+    Keptn builds upon CloudEvents for continuous delivery and automated operations and has its [specification](https://github.com/keptn/spec) based on CloudEvents.
+  url: https://keptn.sh
+  logo: keptn.png
+- name: Knative Eventing
+  description: |
+    All event data produced and consumed by Knative Eventing services is CloudEvents compliant
+  url: https://knative.dev/docs/eventing/
+  logo: knative.png
+- name: Kogito
+  description: |
+    All events emitted and consumed by Kogito business automation applications are CloudEvents compliant
+  url: https://kogito.kie.org/
+  logo: kogito-logo.png
+- name: OpenFaaS
+  description: |
+    CloudEvent events are one of the many available triggers for OpenFaaS functions
+  url: https://docs.openfaas.com/reference/triggers/#cloudevents
+  logo: openfaas.svg
+- name: Oracle Cloud
+  description: |
+    The Oracle Cloud Infrastructure Events service implements CloudEvents
+  url: https://blogs.oracle.com/cloud-infrastructure/track-and-react-to-cloud-native-events
+  logo: oracle.png
+- name: Serverless.com Event Gateway
+  description: |
+    All event data that functions receive from the Event Gateway is CloudEvents compliant
+  url: https://github.com/serverless/event-gateway
+  logo: serverless-event-gateway.png
+- name: Serverless Workflow
+  description: |
+    All event definitions in the Serverless Workflow JSON/YAML model are CloudEvents compliant
+  url: https://serverlessworkflow.io
+  logo: sw-logo.png
+- name: Tekton Pipelines
+  description: |
+    Tekton is a cloud native framework for creating CI/CD systems that can emit cloud events as pipelines and tasks execute.
+  url: https://tekton.dev
+  logo: tekton.png
+- name: Tencent Cloud EventBridge
+  description: |
+    EventBridge is a secure, stable, and efficient serverless event management platform that supports Tencent Cloud services, custom applications, and SaaS applications are connected in a standardized and centralized manner.
+  url: https://cloud.tencent.com/product/eb
+  logo: tencentcloud-eventbridge.svg
+- name: TriggerMesh
+  description: |
+    TriggerMesh makes use of CloudEvents in all its event sources and targets to build application flows.
+  url: https://www.triggermesh.com
+  logo: triggermesh.png
+- name: VMware Event Broker Appliance
+  description: |
+    VMware Event Broker Appliance (VEBA) publishes CloudEvents for changes in a vSphere cluster.
+  url: https://vmweventbroker.io/
+  logo: veba.png
+- name: wasmCloud
+  url: https://wasmcloud.dev
+  description: |
+    wasmCloud, a cloud native WebAssembly host runtime (CNCF), uses CloudEvents for all event publication and monitoring on its control interface.
+  logo: wasmcloud.png
--- a/data/en/params.yaml
+++ b/data/en/params.yaml
@ -0,0 +1,61 @@
+description: "A specification for describing event data in a common way"
+why:
+  whyTitle: "Why CloudEvents?"
+  heading: "Events are everywhere, yet event publishers tend to describe events differently."
+  tiles:
+    - heading: "Consistency"
+      text: "The lack of a common way of describing events means developers have to write new event handling logic for each event source."
+      icon: "fas fa-code"
+    - heading: "Accessibility"
+      text: "No common event format means no common libraries, tooling, and infrastructure for delivering event data across environments. CloudEvents provides SDKs for [Go](https://github.com/cloudevents/sdk-go), [JavaScript](https://github.com/cloudevents/sdk-javascript), [Java](https://github.com/cloudevents/sdk-java), [C#](https://github.com/cloudevents/sdk-csharp), [Ruby](https://github.com/cloudevents/sdk-ruby), [PHP](https://github.com/cloudevents/sdk-php), [PowerShell](https://github.com/cloudevents/sdk-powershell), [Rust](https://github.com/cloudevents/sdk-rust), and [Python](https://github.com/cloudevents/sdk-python) that can be used to build event routers, tracing systems, and other tools."
+      icon: "fas fa-universal-access"
+    - heading: "Portability"
+      text: "The portability and productivity we can achieve from event data is hindered overall."
+      icon: "far fa-gem"
+what:
+  title: "What is CloudEvents?"
+  text: "
+CloudEvents is a [specification](https://github.com/cloudevents/spec/blob/main/cloudevents/spec.md) for describing event data in a common way. CloudEvents seeks to dramatically simplify event declaration and delivery across services, platforms, and beyond!
+
+
+CloudEvents is a new effort and it's still under active development. However, its working group has received a surprising amount of industry interest, ranging from major cloud providers to popular SaaS companies. The specification is now under the [Cloud Native Computing Foundation](https://cncf.io).
+"
+contribute:
+  title: "Contribute to the CloudEvents project"
+  text: "CloudEvents is organized via the CNCF's [Serverless Working Group](https://github.com/cncf/wg-serverless) and everyone is encouraged to join us. If you're interested in contributing, please collaborate with us in the [CloudEvents Github org](https://github.com/cloudevents), join our weekly call every Thursday at [9AM PT](https://www.thetimezoneconverter.com/?t=9:00am&tz=San%20Francisco) via [Zoom](https://zoom.us/my/cncfserverlesswg), check the [meeting notes](https://docs.google.com/document/d/1OVF68rpuPK5shIHILK9JOqlZBbfe91RNzQ7u_P7YCDE), and review our [Governance](https://github.com/cloudevents/spec/blob/main/docs/GOVERNANCE.md) model to familiarize yourself with our process."
+releases:
+  - title: "CloudEvents 1.0.2 release"
+    text: "On February 5, 2022 the CloudEvents project released v1.0.2 of its specifications. Aside from minor clarifications to the specifications, there were a few noteworthy additions made to the set of deliverables:
+
+- a new Powershell SDK was introduced
+
+- batching support was added to the Protobuf format
+
+- work was started to translate the specifications to Chinese
+
+
+See the [release notes](https://github.com/cloudevents/spec/releases/tag/v1.0.2) for more details. Additionally, the 'specs' github repository was reorganized to accommodate the newer specifications that are under development. Note that this release is compatible with the existing CloudEvents v1.0 specification.
+"
+  - title: "CloudEvents 1.0.1 release"
+    text: "On Decemeber 10, 2020 the CloudEvents project released v1.0.1 of its specifications. This release addresses several clarifications to the v1.0 specification, as well as adding some new features such as a WebSocket protocol binding. Please see the [release note](https://github.com/cloudevents/spec/releases/tag/v1.0.1) for the complete list of changes. Note that this release is compatible with the existing CloudEvents v1.0 specification."
+  - title: "CloudEvents 1.0 release"
+    text: "On October 24, 2019 the CloudEvents project had two significant achievements. First, the CNCF's [Technical Oversight Committee](https://github.com/cncf/toc) approved the project as an \"incubator\" project (thus graduating it from the CNCF \"sandbox\"). Second, the CloudEvents specification released version 1.0!
+
+
+  This is the first major release of the specification and represents two years' worth of hard work by a truly great team of people from across the entire serverless community. We've had just about every major cloud provider participate, several \"end user\" companies as well as many individual participants all working diligently on producing a specification that will hopefully continue to see increased adoption now that this milestone has been reached.
+
+
+  Aside from the [core CloudEvents specification](https://github.com/cloudevents/spec/blob/v1.0/spec.md), there's also the [Primer](https://github.com/cloudevents/spec/blob/v1.0/primer.md) and protocol and format specifications, all of which can be found in the [GitHub repo](https://github.com/cloudevents/spec). Additionally, there are many [SDKs](https://github.com/cloudevents/spec#sdks)—[Go](https://github.com/cloudevents/sdk-go), [JavaScript](https://github.com/cloudevents/sdk-javascript), [Java](https://github.com/cloudevents/sdk-java), [C#](https://github.com/cloudevents/sdk-csharp), [Ruby](https://github.com/cloudevents/sdk-ruby), [PHP](https://github.com/cloudevents/sdk-php), [PowerShell](https://github.com/cloudevents/sdk-powershell), [Rust](https://github.com/cloudevents/sdk-rust), and [Python](https://github.com/cloudevents/sdk-python)—to help people produce and consume CloudEvents.
+
+
+  The CNCF Serverless Working Group will be deciding what to focus on next (e.g. additional CloudEvents related activities, or perhaps address some other interoperability pain-point the community is experiencing). So, if you're interested please join the regular [weekly calls](https://github.com/cloudevents/spec#meeting-time). Additionally, there is the work being done on the [workflow specification](https://github.com/serverlessworkflow/specification/blob/master/specification.md).
+
+
+  Thanks and congratulations to everyone who has participated in the CloudEvents project!
+"
+integrations: "Integrations"
+resources:    "Resources"
+videos:       "Videos"
+title:        "Title"
+speakers:     "Speakers"
+event:        "Event"
--- a/data/zh-cn/integrations.yaml
+++ b/data/zh-cn/integrations.yaml
@ -0,0 +1,115 @@
+- name: Adobe I/O 事件
+  description: |
+    Adobe I/O Events 采用事件驱动架构来简化工作流程、提高营销绩效等，它允许开发人员以编程方式响应用户行为，从而产生具有针对性、有效和个性化的近乎实时的客户体验。
+  url: https://www.adobe.io/apis/experienceplatform/events.html
+  logo: adobeioeventslogo.jpg
+- name: 阿里云事件总线
+  description: |
+    一款 serverless 的事件总线，支持从云服务、SaaS及自定义应用程序接收符合 CloudEvents 的事件，并将这些事件路由到不同目标。
+  url: https://www.aliyun.com/product/aliware/eventbridge
+  logo: alibaba-cloud-eventbridge.png
+- name: Argo 事件
+  description: |
+    Argo Events 是一个基于 Kubernetes 事件驱动自动化工作流框架，它的事件符合 CloudEvents 规范要求。
+  url: https://github.com/argoproj/argo-events
+  logo: argo-events.png
+- name: Azure 事件网格
+  description: |
+    事件网格原生支持 CloudEvents v1.0 中的 [JSON 实现](https://github.com/cloudevents/spec/blob/v1.0/json-format.md)和 [HTTP 协议绑定](https://github.com/cloudevents/spec/blob/v1.0/http-protocol-binding.md)。
+  url: https://azure.microsoft.com/en-us/services/event-grid
+  logo: event-grid.png
+- name: Choria
+  description: |
+    Choria 编排系统生产的所有生命周期和自治代理事件都符合 CloudEvents 规范要求。
+  url: https://choria.io/blog/post/2019/12/05/cloudevents_transition
+  logo: choria.png
+- name: commercetools
+  description: |
+    commercetools 平台的所有服务都可以发出符合 CloudEvents 的事件
+  url: https://www.commercetools.com
+  logo: commercetools.png
+- name: Debezium
+  description: |
+    Debezium 是一个分布式开源的数据变更捕获平台，它能以 [CloudEvents 格式](https://debezium.io/documentation/reference/integrations/cloudevents.html)发出数据变更的事件
+  url: https://debezium.io/
+  logo: debezium.png
+- name: Direktiv
+  description: |
+    Direktiv，一个 serverless 的工作流引擎，可以接收 [Cloud Events](https://docs.direktiv.io/docs/events/events.html) 来触发工作流。
+  url: https://direktiv.io
+  logo: direktiv.png
+- name: Falco
+  description: |
+    Falco 是基于 Kubernetes 的威胁检测引擎，可以在运行时根据违反安全策略的事件发出 Cloud Events。
+  url: https://falco.org
+  logo: falco.png 
+- name: Google Cloud Eventarc
+  description: |
+    Eventarc 是一个托管基础架构，它允许您使用松耦合的服务构建事件驱动的架构，这些服务随时可以响应状态变化。
+  url: https://cloud.google.com/eventarc/docs/
+  logo: googlecloud.png
+- name: IBM Cloud 代码引擎
+  description: |
+    Code Engine 是一个完全托管的 serverless 平台，旨在运行容器映像、批处理作业或源代码。 Code Engine 允许您构建能响应 Cloud Events 的事件驱动型工作负载。
+  url: https://cloud.ibm.com/codeengine
+  logo: codeengine.svg
+- name: Keptn
+  description: |
+    Keptn 基于 CloudEvents 构建以实现持续交付和自动化操作，并且它的[规范](https://github.com/keptn/spec) 同样基于 CloudEvents。
+  url: https://keptn.sh
+  logo: keptn.png
+- name: Knative Eventing
+  description: |
+    Knative Eventing 服务产生和使用的所有事件数据都符合 CloudEvents 规范。
+  url: https://knative.dev/docs/eventing/
+  logo: knative.png
+- name: Kogito
+  description: |
+    Kogito 业务自动化应用程序发出和使用的所有事件都符合 CloudEvents 规范。
+  url: https://kogito.kie.org/
+  logo: kogito-logo.png
+- name: OpenFaaS
+  description: |
+    OpenFaaS 函数支持 CloudEvent 事件触发。
+  url: https://docs.openfaas.com/reference/triggers/#cloudevents
+  logo: openfaas.svg
+- name: Oracle Cloud
+  description: |
+    Oracle 云基础设施事件服务实现了 CloudEvents。
+  url: https://blogs.oracle.com/cloud-infrastructure/track-and-react-to-cloud-native-events
+  logo: oracle.png
+- name: Serverless.com 事件网关
+  description: |
+    函数从事件网关接收的所有事件数据都符合 CloudEvents 规范。
+  url: https://github.com/serverless/event-gateway
+  logo: serverless-event-gateway.png
+- name: Serverless Workflow
+  description: |
+    Serverless 工作流 JSON/YAML 模型中的所有事件定义都符合 CloudEvents 规范。
+  url: https://serverlessworkflow.io
+  logo: sw-logo.png
+- name: Tekton 管道
+  description: |
+    Tekton 是一个云原生框架，用于创建 CI/CD 系统，可以在管道和任务执行时发出 CloudEvents。
+  url: https://tekton.dev
+  logo: tekton.png
+- name: 腾讯云事件总线
+  description: |
+    事件总线是一个安全、稳定、高效的 Serverless 事件管理平台，支持腾讯云服务、自定义应用、SaaS 应用以标准化、集中化的方式连接。
+  url: https://cloud.tencent.com/product/eb
+  logo: tencentcloud-eventbridge.svg
+- name: TriggerMesh
+  description: |
+    TriggerMesh 在其所有事件源和目标中使用 CloudEvents 来构建应用程序流。
+  url: https://www.triggermesh.com
+  logo: triggermesh.png
+- name: VMware Event Broker Appliance
+  description: |
+    VMware Event Broker Appliance (VEBA) 针对 vSphere 集群中的更改发布 CloudEvents。
+  url: https://vmweventbroker.io/
+  logo: veba.png
+- name: wasmCloud
+  url: https://wasmcloud.dev
+  description: |
+    wasmCloud 是一个云原生的 WebAssembly 主机运行时 (CNCF项目)，它使用 CloudEvents 在其控制界面上进行所有事件的发布和监控。
+  logo: wasmcloud.png
--- a/data/zh-cn/params.yaml
+++ b/data/zh-cn/params.yaml
@ -0,0 +1,61 @@
+description: "一个以通用格式来描述事件数据的规范"
+why:
+  whyTitle: "为何选择 CloudEvents？"
+  heading: "事件在现代系统中无处不在，但不同的事件生产者往往用不同的规范来描述自己的事件。"
+  tiles:
+    - heading: "一致性"
+      text: "对事件的统一描述的缺乏意味着开发者必须为每个事件源写单独的事件处理逻辑。"
+      icon: "fas fa-code"
+    - heading: "可达性"
+      text: "缺乏统一的事件格式意味着缺失能够跨环境传输事件数据的公共库、工具以及基础设施。CloudEvents 针对不同编程语言，提供了能用来构建事件路由、事件追踪和其它工具的多款 SDKs 包括 [Go](https://github.com/cloudevents/sdk-go)、 [JavaScript](https://github.com/cloudevents/sdk-javascript)、 [Java](https://github.com/cloudevents/sdk-java)、 [C#](https://github.com/cloudevents/sdk-csharp)、 [Ruby](https://github.com/cloudevents/sdk-ruby)、[PHP](https://github.com/cloudevents/sdk-php)、[PowerShell](https://github.com/cloudevents/sdk-powershell)、[Rust](https://github.com/cloudevents/sdk-rust)、 以及 [Python](https://github.com/cloudevents/sdk-python) 。"
+      icon: "fas fa-universal-access"
+    - heading: "可移植性"
+      text: "总体来看，这种对事件的统一描述的缺乏严重阻碍了事件数据的可移植性和生产力。"
+      icon: "far fa-gem"
+what:
+  title: "什么是 CloudEvents?"
+  text: "
+CloudEvents 是一个以通用格式来描述事件数据的 [规范](https://github.com/cloudevents/spec/blob/main/cloudevents/languages/zh-CN/spec.md)。 它旨在简化不同服务、平台间的事件声明和传输。
+
+
+CloudEvents 是一个全新且活跃的尝试。 但它的工作组已经被各大云厂商和 SaaS 公司广泛关注。 目前 CloudEvents 已捐献至 [云原生基金会](https://cncf.io)。
+"
+contribute:
+  title: "贡献 CloudEvents 项目"
+  text: "CloudEvents 由云原生基金会的[Serverless 工作组](https://github.com/cncf/wg-serverless)发起，诚邀各位的加入。 如果你希望对此项目进行贡献, 可以在 [CloudEvents Github 组织](https://github.com/cloudevents) 与我们合作， 或是参加每周 [太平洋时间 早上9点](https://www.thetimezoneconverter.com/?t=9:00am&tz=San%20Francisco) 的 [Zoom会议](https://zoom.us/my/cncfserverlesswg), 以及查看 [会议记录](https://docs.google.com/document/d/1OVF68rpuPK5shIHILK9JOqlZBbfe91RNzQ7u_P7YCDE)。 通过 [此文档](https://github.com/cloudevents/spec/blob/main/docs/GOVERNANCE.md)来更多地了解我们。"
+releases:
+  - title: "CloudEvents 1.0.2 版本"
+    text: "2022 年 2 月 5 日，CloudEvents 项目发布了v1.0.2 版本的规范。 除了对规格的细微说明外，此版本还增加了以下值得注意的内容：
+
+- 引入了新的 Powershell SDK
+
+- 新增了 Protobuf 格式的批处理功能
+
+- CloudEvents 的中文翻译正在进行中
+
+
+更多详细信息，请参阅[发行说明](https://github.com/cloudevents/spec/releases/tag/v1.0.2)。 此外，我们重新调整了 “specs” 仓库的目录结构，以适应正在开发的新规范。 请注意，此版本与现有 CloudEvents v1.0 规范兼容。
+"
+  - title: "CloudEvents 1.0.1 版本"
+    text: "2020 年 12 月 10 日，CloudEvents 项目发布了v1.0.1 版本的规范。 此版本对 v1.0 规范的某些内容进行了一些解释，并添加了一些新功能，例如 WebSocket 的协议绑定。 有关更改的完整列表，请参阅[发行说明](https://github.com/cloudevents/spec/releases/tag/v1.0.1)。 请注意，此版本与现有 CloudEvents v1.0 规范兼容。"
+  - title: "CloudEvents 1.0 版本"
+    text: "2019 年 10 月 24 日，CloudEvents 项目取得了两项重大成就。首先，CNCF 的[技术监督委员会](https://github.com/cncf/toc)将该项目批准为“孵化”项目（正式从 CNCF“沙盒”中毕业）。其次，CloudEvents规范发布 1.0版本！
+
+
+  这是本规范的第一个大版本，代表了整个 serverless 社区团队两年来的辛勤工作。几乎所有主要的云厂商，一些“终端用户”公司以及许多个人都参与到了规范的制定，希望本规范在这一里程碑后继续能被越来越多的用户采用。
+
+
+  除了 CloudEvents [核心规范](https://github.com/cloudevents/spec/blob/v1.0/spec.md)外，还有入门文档以及协议和格式的相关规范被制定出来，这些文件都可以在 GitHub 仓库中找到。 此外，工作组还开发了许多 SDK（Go、JavaScript、Java、C#、Ruby、PHP、PowerShell、Rust 和 Python）来帮助人们生产和使用 CloudEvents。
+
+
+  CNCF Serverless 工作组将决定本规范的下一步重点内容（例如，其它与 CloudEvents 相关的活动，或者可能解决社区正在经历的其它互操作性痛点）。 因此，如果您有兴趣，请加入每周定期[线上会议](https://github.com/cloudevents/spec#meeting-time)。 此外，我们还在做一些关于 [workflow 规范](https://github.com/serverlessworkflow/specification/blob/master/specification.md)的制定工作。
+
+
+  感谢并祝贺每位参与到 CloudEvents 项目的人！
+"
+integrations: "CloudEvents 规范采纳者"
+resources:    "资源"
+videos:       "视频"
+title:        "标题"
+speakers:     "演讲者"
+event:        "活动"