i18n

WORK IN PROGRESS (Jan. 17, 2023)

1. If this is not your first time here, go to the next step. Otherwise run command git clone [email protected]:OpenLiberty/blogs.git on your machine.
2. cd on your local machine to the blogs directory created by git clone
3. git checkout prod
4. git checkout -b <name-of-your-branch> to create a new feature branch
5. Is there an existing directory for the language in under <your_root_directory>/blogs/tree/prod/posts?
   • If yes, continue to next step.
   • If no, create a new directory named after the language's code in the /posts directory.
6. Place the adoc file into the new/existing language directory.
7. Is the new post a translation of an existing post?
   • If no, continue to next step.
   • If yes, please include the attribute blog-available-in-languages in the md file's front matter.
     • The front matter is the key-value pairs found between the two --- lines. Here is an example of how to use blog-available-in-languages attribute (https://raw.githubusercontent.com/OpenLiberty/blogs/prod/posts/ja/2022-10-29-22.0.0.10.adoc).
     • If there is a desire to give credit to the translator, please the translators name in the new post.
     • 
     • Please make your adoc file similar to the existing post that is being translated. Date can be different. File format is YYYY-MM-DD-postname. Here are two files that are the same content in different languages and different date.
       • Japanese 2022-10-29-22.0.0.10.adoc
       • English 2022-09-27-22.0.0.10.adoc
8. Open a pull request from your feature branch that is targeting draft branch and Set the reviewer to Kin Ueng (@kinueng)