I agree with everything Kamil said - we need to split the docs into: - website/landing page (simple, static, slow-changing, multi-language, managed by designated people) - Tutorial/Documentation (fast changing, every contributor can change and update it, automatically generated from the code of Airflow)
The problem with multi-language documentation/tutorial of fast-evolving product is that you cannot ask every contribute to make translation. For the tutorial/documentation, correctness. freshness are the most important - so basically it has to change together with the code. Our code is in English and everyone contributing must understand it, so English is the only choice for such documentation. J. On Wed, Jul 17, 2019 at 7:17 AM Jiajie Zhong <zhongjiajie...@hotmail.com> wrote: > Thanks Kamil remind me in > https://github.com/apachecn/airflow-doc-zh/issues/65 > I agree with you multi languages point, I think Airflow leading page > should have multi languages > But for the documentation, I think it hard to up to date > > I’m one of contributor of https://github.com/apachecn/airflow-doc-zh and > this repo translate still in Airflow 1.10.2 > Airflow documentation change too fast, and translation it’s hard to catch > up > > But, personally, Airflow documentation support multi language will > increasing Airflow users > especially not native English users. I join a Airflow Chinese users > Tencent QQ group, > when them hear Airflow have Chinese translation their so happy because > their could make a quick > start of Airflow more easier. > > What I want to said it's If we could tolerate other language translation > not up to date, add translation > in Airflow website is good for not native English users. > > > Best Wish > — Jiajie > > > -- Jarek Potiuk Polidea <https://www.polidea.com/> | Principal Software Engineer M: +48 660 796 129 <+48660796129> [image: Polidea] <https://www.polidea.com/>
