Skip to content

Commit 33cf079

Browse files
committed
Localize projects page
Signed-off-by: Kaito Ii <[email protected]>
1 parent dcd9208 commit 33cf079

File tree

3 files changed

+75
-0
lines changed

3 files changed

+75
-0
lines changed
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,15 @@
1+
---
2+
title: プロジェクト
3+
list_pages: true
4+
menu:
5+
main:
6+
weight: 20
7+
description: これは参加する機会のリストです
8+
---
9+
10+
TAGプロジェクトは[GitHub Issues](https://github.com/cncf/tag-app-delivery/issues)で管理しています。現在あるプロジェクトや新しいプロジェクトを提案したい場合はこちらから始めてください。
11+
12+
13+
本項はissueにない現在進行中のコントリビューション候補です。このリストは完全なものではないことを留意してください。
14+
ここやGitHub Issusesにあなた向けのものがなくても大丈夫です!
15+
[コントリビューションメインページ](https://tag-app-delivery.cncf.io/ja/contribute/)の他のオプションを参照ください。
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,34 @@
1+
---
2+
title: プラットフォーム成熟度モデル例
3+
list_pages: false
4+
---
5+
6+
## Introduction
7+
8+
Platform engineering is still an emerging space. The Maturity Model was written and reviewed by over 50 individuals from different countries, business domains, company sizes and experiences. That being said, it is still a reflection of the group who wrote it.
9+
10+
This contribution type is an opportunity to expand that number even more. To add real life examples to the model giving richer details to the current levels.
11+
12+
## Guidelines
13+
14+
This contribution type is not asking for a change in the model structure or wording. Therefore any suggestions that would change the content, wording, or even formatting of the model and the descriptions of the aspects should be submitted through the more generic contribution format.
15+
16+
What this is doing is enabling and encouraging end users (companies who do not profit from the implementation or sale of cloud native tooling solutions) to share their experiences in relation to the maturity model.
17+
18+
The intention of these contributions is to make these examples more grounded in concrete examples, ideally supplemented by context (e.g. company size, business domain, etc) and more reading (e.g. links to company blogs).
19+
20+
## Contributing
21+
22+
To get started, review [the current model](https://tag-app-delivery.cncf.io/whitepapers/platform-eng-maturity-model/) are scroll down to the `Model Detail` section. In this section there is a page per aspect, and each level provides `Example Scenario` section (e.g. [Investment Provisional level](https://tag-app-delivery.cncf.io/whitepapers/platform-eng-maturity-model/#example-scenarios)).
23+
24+
We are asking for community members to please open a [Pull Request (PR)](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests) adding your example to the current model version. PRs should be limited to just examples, as other changes such as vocabulary, content, or even formatting of the wider maturity model can be submitted as a separate issue.
25+
26+
The original examples are meant to help readers feel connected to the model aspects and levels. To see themselves in the model, and ideally to see examples of what they could experience if they were to invest in moving to another level within the model. These examples were curated by the group but are not attributed to any one company or exact scenario.
27+
28+
You proposed examples should be succinct summery of the way this specific aspect and level presented in your context. We recommend that you use a fairly neutral voice even when presenting challenges or successes. This maintains the tone that there is not "good" or "bad" maturity, but instead the "right" or "wrong" maturity _for you, at this time_. In addition, we encourage people to include their company name specifically if allowed, or some small context on the company for comparison (e.g. "a large multi-national bank" provides insight into size, regulation, and domain).
29+
30+
The current examples are mostly between 200-500 characters which may feel challenging at first. Reviewers can help you refine your words so don't stress too much but also be aware this will be the goal before merging. One way you can manage this is to link out to a separate blog which provides more details if that helps to narrow the focus of your example for this white paper.
31+
32+
## Asking for help
33+
34+
If you have any questions about this contribution type, your specific context, the technicalities of opening a PR, or really anything else, please [join the CNCF Slack](https://communityinviter.com/apps/cloud-native/cncf) and reach out to [#wg-platforms](https://cloud-native.slack.com/archives/C020RHD43BP).
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,26 @@
1+
---
2+
title: 翻訳
3+
list_pages: false
4+
---
5+
6+
## Introduction
7+
8+
Part of what makes the CNCF so amazing is the diversity of people involved and supported by the community. One way we make this community more inclusive is by providing translations for content where possible. Translations of course require native speakers to create and maintain them and this post is about how you can do that within the TAG App Delivery content.
9+
10+
## Guidelines
11+
12+
While each translation is unique, we encourage you to familiarlize yourself with [past translation PRs](https://github.com/cncf/tag-app-delivery/issues?q=label%3Atranslation+) and the [Kubernetes SIG-Docs localization documentation](https://kubernetes.io/docs/contribute/localization) for general guidelines and lessons learned.
13+
14+
The SIG-Docs team has a much broader remit than this TAG requires, so be aware that the workflow including slack channels, opening PRs, and website owner reviews will be done via the same process as all other TAG postings, just with the added requirement of a native language speaker review.
15+
16+
It is worth reiterating what the SIG-Docs team has stated:
17+
18+
> Localizing all the Kubernetes documentation is an enormous task. It's okay to start small and expand over time.
19+
20+
Whether you start with a single white paper, or want to expand on an existing language to include more blog posts or content, every little bit will make a difference and is appreciated!
21+
22+
## Contributing
23+
24+
To get started, please [open an issue](https://github.com/cncf/tag-app-delivery/issues/new/choose) on the TAG App Delivery GitHub repository using the `Website Translation` issue type.
25+
26+
This issue type will provide context on the scope of your work and provide guidance on the steps required to complete a translations.

0 commit comments

Comments
 (0)