i18n init

3x/api.md

@@ -2,6 +2,7 @@
 layout: 3x-api
 title: Express 3.x - API Reference
 menu: api
+lang: en
 ---
 <div id="api-doc" markdown="1">
 
@@ -14,18 +15,18 @@ menu: api
   <h1>3.x API</h1>
 
   <a id='express' class='h2'></a>
-  {% include api/3x/en/express.md %}
+  {% include api/{{ page.lang }}/3x/express.md %}
 
   <a id='application' class='h2'></a>
-  {% include api/3x/en/app.md %}
+  {% include api/{{ page.lang }}/3x/app.md %}
 
   <a id='request' class='h2'></a>
-  {% include api/3x/en/req.md %}
+  {% include api/{{ page.lang }}/3x/req.md %}
 
   <a id='response' class='h2'></a>
-  {% include api/3x/en/res.md %}
+  {% include api/{{ page.lang }}/3x/res.md %}
 
   <a id='middleware' class='h2'></a>
-  {% include api/3x/en/middleware.md %}
+  {% include api/{{ page.lang }}/3x/middleware.md %}
 
 </div>

4x/api.md

@@ -2,24 +2,25 @@
 layout: 4x-api
 title: Express 4.x - API Reference
 menu: api
+lang: en
 ---
 <div id="api-doc" markdown="1">
 
   <h1>4.x API</h1>
 
   <a id='express' class='h2'></a>
-  {% include api/4x/en/express.md %}
+  {% include api/{{ page.lang }}/4x/express.md %}
 
   <a id='application' class='h2'></a>
-  {% include api/4x/en/app.md %}
+  {% include api/{{ page.lang }}/4x/app.md %}
 
   <a id='request' class='h2'></a>
-  {% include api/4x/en/req.md %}
+  {% include api/{{ page.lang }}/4x/req.md %}
 
   <a id='response' class='h2'></a>
-  {% include api/4x/en/res.md %}
+  {% include api/{{ page.lang }}/4x/res.md %}
 
   <a id='router' class='h2'></a>
-  {% include api/4x/en/router.md %}
+  {% include api/{{ page.lang }}/4x/router.md %}
 
 </div>

README.md

@@ -31,3 +31,13 @@ If you have an app you'd like to showcase on the site, open a pull request for i
 ## Why use Jekyll instead of an Express-based solution?
 
 Jekyll comes built-in with GitHub Pages. Since we are already using GitHub Pages to host the website, it makes sense to leverage the capabilities it provides. It's all about using the right tool, for the right job, under the right circumstances.
+
+## How do I help translate the docs to a certain language?
+
+Follow these steps:
+
+1. Create a directory for the language of your choice using its [ISO 639-1 code](http://en.wikipedia.org/wiki/ISO_639-1) as its name.
+2. Copy `index.md`, `api.md`, `starter/`, `guide/`, `api/`, `advanced/`, and `resources/` to the language directory.
+3. Update the `lang` variable in the markdown files in the copied file to the language you have selected.
+4. Create the header and footer HTML files for the language in the `_includes/` directory.
+5. Copy the `_includes/api/en` to the language of your choice.