Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

add Italian version of the Maturity Model #692

Draft
wants to merge 2 commits into
base: main
Choose a base branch
from
Draft
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Binary file not shown.
26 changes: 26 additions & 0 deletions website/content/en/contribute/projects/translations/index.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,26 @@
---
title: Translations
list_pages: false
---

## Introduction

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.

## Guidelines

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.

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.

It is worth reiterating what the SIG-Docs team has stated:

> Localizing all the Kubernetes documentation is an enormous task. It's okay to start small and expand over time.

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!

## Contributing

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.

This issue type will provide context on the scope of your work and provide guidance on the steps required to complete a translations.
26 changes: 26 additions & 0 deletions website/content/ja/contribute/projects/translations/index.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,26 @@
---
title: 翻訳
list_pages: false
---

## イントロダクション

CNCFの素晴らしさの一端は関わっている人々の多様性とコミュニティからサポートされているからです。このコミュニティをより包括的にする一例として、可能な箇所でコンテンツの翻訳を提供することです。翻訳には当然それを作成およびメンテナンスする母語話者を必要とし、このページはTAG App Deliveryのコンテンツでのやり方を示します。

## ガイドライン

各翻訳で異なりますが、一般的なガイドラインやノウハウは[過去の翻訳PR](https://github.com/cncf/tag-app-delivery/issues?q=label%3Atranslation+)や[Kubernetes SIG-Docsローカライゼーションドキュメント](https://kubernetes.io/ja/docs/contribute/localization/)を参考にすることをおすすめします。

SIG-DocsチームはこのTAGに比べ、広い責任範囲を持ちます。Slackチャネルへの投稿、PRの作成、ウェブサイトのレビューなどのワークフローはその他のTAGの投稿と同一のプロセスで進められることに注意して下さい。そこに母国話者のレビューが追加されます。

SIG-Docsチームの言葉を再掲する価値があります:

> Kubernetesのドキュメントすべてをローカライズするのは膨大な作業です。小さく始め、徐々に大きくしても問題ないです。

一つのホワイトペーパーから始めても、今ある言語にブログやコンテンツに追加してもよいです。どんなに些細なものでも重要で歓迎します!

## 貢献の仕方

始めるにはTAG App Delivery GitHubリポジトリに`Website Translation`タイプの[issueの作成](https://github.com/cncf/tag-app-delivery/issues/new/choose)をしてください。

このissueタイプはあなたの仕事の範囲に関するコンテキストを提供し、翻訳を進めるのに必要な工程の手引を提供します。