Some of the pain of switching to Hugo may be alleviated by the `hugo import jekyll` command: https://gohugo.io/commands/hugo_import_jekyll/
I guess that will probably just take care of the markdown flavor, but at least that's one less thing to worry about. Brian On Mon, Jun 3, 2019 at 11:08 PM Melissa Pashniak <meliss...@google.com> wrote: > > We currently use Jekyll to generate our HTML files, and there are some > plugins and hacks to add multilingual support, but it's not built-in. as I > understand it, It's one of the reasons Kubernetes moved away from Jekyll to > Hugo about a year ago (see their blog post for more details [1] ). They > wanted multilingual support and a language switcher, and after > investigating Jekyll options, settled on Hugo as it comes with built-in > multilingual support [2]. > > We could try to go the Jekyll plugin route to add additional languages in > Jekyll, but if we want maintainable docs that are in many languages and a > language switcher as a long-term goal, we might want to consider moving. > Either way, we'd need to do some work. > > For the Jekyll option, we'd need to (likely): > > - evaluate the existing multilingual plugins, see if they do what we > want, and make any needed code changes > - I suspect we'll have to change the site directory structure > - update all of the existing Jenkins jobs to stage/test, and any other > scripts that deal with building the site. this would require someone with > knowledge about how it's all put together with the building and syncing of > the website, and access to the build machines? > - updating the existing local testing/staging scripts for contributors > > If we moved to Hugo for built-in support: > > - rip out Jekyll and get Hugo set up and configured > - (same as above, but more substantial changes needed) update all of the > existing Jenkins jobs to stage/test, and any other scripts that deal with > building the site. this would require someone with knowledge about how it's > all put together with the building and syncing of the website, and access > to the build machines? > - updating the existing local testing/staging scripts for contributors > - figuring out replacements (IF they don't exist for Hugo) for some of our > Jekyll plugins (for example, github snippet grabber, link checker). > - Hugo uses a different flavor of markdown, so we'll likely need to make > some changes to our markdown files > - Probably other things I am not aware of ;-) > > Thoughts? > > [1] https://kubernetes.io/blog/2018/05/05/hugo-migration/ > [2] https://gohugo.io/content-management/multilingual/ > > > > On Fri, May 24, 2019 at 10:50 AM Lukasz Cwik <lc...@google.com> wrote: > >> Welcome Zhang, I have added you as a contributor the Apache Beam JIRA. >> >> I would suggest you take a look at the contribution guide[1] to learn on >> how to get started. >> >> If I understand correctly, your interested in translating several >> documents found on the Beam website, if so Melissa would be a good contact >> since she has helped with our documentation a lot. >> Melissa would you know if we have i18n support built into the website >> already? >> >> 1: https://beam.apache.org/contribute/ >> >> On Thu, May 23, 2019 at 6:24 PM 图霸群英 <ta...@tmd.me> wrote: >> >>> Hello everyone! My name is Zhang Haitao and I am from Beijing, China. >>> I created a Beam Chinese hobby group in China. >>> Also published on infoq about Beam related articles. >>> Https://www.infoq.cn/profile/1280576 >>> I want to join the Beam community now. >>> >>> On May 27th of this month, I will also participate in Qcon's promotion >>> work on Beam technology. >>> https://2019.qconguangzhou.com/presentation/1822 >>> >>> Now I am organizing people in China to translate English help documents >>> into Chinese. >>> Please give me a lot of advice and care. >>> >>> My github account: xsm110 >>> Example: >>> https://github.com/xsm110/Apache-Beam-Example >>> Apache User ID : zhanghaitao8 >>> JIRA: zhanghaitao8 >>> >>> The attachment is signed by me for the agreement submitted to ASF.ICLA >>> >>
