Add The defalut language(en) will serving on http://your-server-ip/

CONTRIBUTING.md

@@ -64,6 +64,10 @@ The website will serving on http://your-server-ip:80
 docker rm -f `cat docs.pid` && rm -f docs.pid
 ```
 
+***Note***: 
+The defalut language(en) will serving on http://your-server-ip/
+Other language(zh) will serving on http://your-server-ip/zh
+
 ### Add/Modify file
 
 Before openning a PR, running locally and have a check would be good step that will help

README.md

@@ -23,6 +23,9 @@ docker run -p 80:80 -d docs:v0.0.1 > docs.pid
 
 The website will serving on http://your-server-ip:80
 
+The defalut language(en) will serving on http://your-server-ip/
+Other language(zh) will serving on http://your-server-ip/zh
+
 3. Stopping the container
 
 ```

config.toml

@@ -9,6 +9,10 @@ disableKinds = ['taxonomy', 'taxonomyTerm']
 # Book configuration
 disablePathToLower = true
 enableGitInfo = true
+defaultContentLanguage = "en"
+defaultContentLanguageInSubdir = false
+
+uglyURLs = true
 
 # Code highlight
 # pygmentsStyle = 'monokailight'
@@ -26,7 +30,7 @@ pygmentsCodeFences = true
 
   # (Optional, default docs) Specify section of content to render as menu
   # You can also set value to '*' to render all sections to menu
-  BookSection = 'docs'
+  #BookSection = 'docs'
 
   # (Optional) This value is duplicate of $link-color for making active link highlight in menu bundle mode
   # BookMenuBundleActiveLinkColor = '\#004ed0'
@@ -48,3 +52,17 @@ pygmentsCodeFences = true
   # (Optional, default true) Enables search function with lunr.js, 
   # Index is built on fly, therefore it might slowdown your website.
   BookSearch = true
+
+  bookFlatSection = true
+  bookHidden = true
+
+
+[languages]
+
+[languages.en]
+    languageCode = "en-us"
+    contentDir = "content/en"
+
+[languages.zh]
+    languageCode = "zh-cn"
+    contentDir = "content/zh"

content/en/docs/get-started.md

+### Get started
+
+#### 

content/en/menu/index.md

+---
+headless: true
+---
+
+- [Home](/docs/home.html)
+- [Get Started](/docs/get-started.html)
+- [Tutorials](/docs/安装准备.html)
+  - [ARM Deployment](/docs/获取安装源.html)
+  - [Cloud Deployment](/docs/硬件兼容支持.html)
+- [Development](/docs/启动安装.html)
+  - [openEuler](/docs/通过光盘安装.html)
+  - [Application](/docs/通过U盘安装.html)
+- [Reference](/docs/临时参考.html)
+  - [Developer Guide](/docs/安装过程参考.html)
+  - [openEuler Setting](/docs/安装openEuler.html)

content/posts/goisforlovers.md

-+++
-title = "(Hu)go Template Primer"
-description = ""
-tags = [
-    "go",
-    "golang",
-    "templates",
-    "themes",
-    "development",
-]
-date = "2014-04-02"
-categories = [
-    "Development",
-    "golang",
-]
-menu = "main"
-+++
-
-Hugo uses the excellent [Go][] [html/template][gohtmltemplate] library for
-its template engine. It is an extremely lightweight engine that provides a very
-small amount of logic. In our experience that it is just the right amount of
-logic to be able to create a good static website. If you have used other
-template systems from different languages or frameworks you will find a lot of
-similarities in Go templates.
-
-This document is a brief primer on using Go templates. The [Go docs][gohtmltemplate]
-provide more details.
-
-## Introduction to Go Templates
-
-Go templates provide an extremely simple template language. It adheres to the
-belief that only the most basic of logic belongs in the template or view layer.
-One consequence of this simplicity is that Go templates parse very quickly.
-
-A unique characteristic of Go templates is they are content aware. Variables and
-content will be sanitized depending on the context of where they are used. More
-details can be found in the [Go docs][gohtmltemplate].
-
-## Basic Syntax
-
-Golang templates are HTML files with the addition of variables and
-functions.
-
-**Go variables and functions are accessible within {{ }}**
-
-Accessing a predefined variable "foo":
-
-    {{ foo }}
-
-**Parameters are separated using spaces**
-
-Calling the add function with input of 1, 2:
-
-    {{ add 1 2 }}
-
-**Methods and fields are accessed via dot notation**
-
-Accessing the Page Parameter "bar"
-
-    {{ .Params.bar }}
-
-**Parentheses can be used to group items together**
-
-    {{ if or (isset .Params "alt") (isset .Params "caption") }} Caption {{ end }}
-
-
-## Variables
-
-Each Go template has a struct (object) made available to it. In hugo each
-template is passed either a page or a node struct depending on which type of
-page you are rendering. More details are available on the
-[variables](/layout/variables) page.
-
-A variable is accessed by referencing the variable name.
-
-    <title>{{ .Title }}</title>
-
-Variables can also be defined and referenced.
-
-    {{ $address := "123 Main St."}}
-    {{ $address }}
-
-
-## Functions
-
-Go template ship with a few functions which provide basic functionality. The Go
-template system also provides a mechanism for applications to extend the
-available functions with their own. [Hugo template
-functions](/layout/functions) provide some additional functionality we believe
-are useful for building websites. Functions are called by using their name
-followed by the required parameters separated by spaces. Template
-functions cannot be added without recompiling hugo.
-
-**Example:**
-
-    {{ add 1 2 }}
-
-## Includes
-
-When including another template you will pass to it the data it will be
-able to access. To pass along the current context please remember to
-include a trailing dot. The templates location will always be starting at
-the /layout/ directory within Hugo.
-
-**Example:**
-
-    {{ template "chrome/header.html" . }}
-
-
-## Logic
-
-Go templates provide the most basic iteration and conditional logic.
-
-### Iteration
-
-Just like in Go, the Go templates make heavy use of range to iterate over
-a map, array or slice. The following are different examples of how to use
-range.
-
-**Example 1: Using Context**
-
-    {{ range array }}
-        {{ . }}
-    {{ end }}
-
-**Example 2: Declaring value variable name**
-
-    {{range $element := array}}
-        {{ $element }}
-    {{ end }}
-
-**Example 2: Declaring key and value variable name**
-
-    {{range $index, $element := array}}
-        {{ $index }}
-        {{ $element }}
-    {{ end }}
-
-### Conditionals
-
-If, else, with, or, & and provide the framework for handling conditional
-logic in Go Templates. Like range, each statement is closed with `end`.
-
-
-Go Templates treat the following values as false:
-
-* false
-* 0
-* any array, slice, map, or string of length zero
-
-**Example 1: If**
-
-    {{ if isset .Params "title" }}<h4>{{ index .Params "title" }}</h4>{{ end }}
-
-**Example 2: If -> Else**
-
-    {{ if isset .Params "alt" }}
-        {{ index .Params "alt" }}
-    {{else}}
-        {{ index .Params "caption" }}
-    {{ end }}
-
-**Example 3: And & Or**
-
-    {{ if and (or (isset .Params "title") (isset .Params "caption")) (isset .Params "attr")}}
-
-**Example 4: With**
-
-An alternative way of writing "if" and then referencing the same value
-is to use "with" instead. With rebinds the context `.` within its scope,
-and skips the block if the variable is absent.
-
-The first example above could be simplified as:
-
-    {{ with .Params.title }}<h4>{{ . }}</h4>{{ end }}
-
-**Example 5: If -> Else If**
-
-    {{ if isset .Params "alt" }}
-        {{ index .Params "alt" }}
-    {{ else if isset .Params "caption" }}
-        {{ index .Params "caption" }}
-    {{ end }}
-
-## Pipes
-
-One of the most powerful components of Go templates is the ability to
-stack actions one after another. This is done by using pipes. Borrowed
-from unix pipes, the concept is simple, each pipeline's output becomes the
-input of the following pipe.
-
-Because of the very simple syntax of Go templates, the pipe is essential
-to being able to chain together function calls. One limitation of the
-pipes is that they only can work with a single value and that value
-becomes the last parameter of the next pipeline.
-
-A few simple examples should help convey how to use the pipe.
-
-**Example 1 :**
-
-    {{ if eq 1 1 }} Same {{ end }}
-
-is the same as
-
-    {{ eq 1 1 | if }} Same {{ end }}
-
-It does look odd to place the if at the end, but it does provide a good
-illustration of how to use the pipes.
-
-**Example 2 :**
-
-    {{ index .Params "disqus_url" | html }}
-
-Access the page parameter called "disqus_url" and escape the HTML.
-
-**Example 3 :**
-
-    {{ if or (or (isset .Params "title") (isset .Params "caption")) (isset .Params "attr")}}
-    Stuff Here
-    {{ end }}
-
-Could be rewritten as
-
-    {{  isset .Params "caption" | or isset .Params "title" | or isset .Params "attr" | if }}
-    Stuff Here
-    {{ end }}
-
-
-## Context (aka. the dot)
-
-The most easily overlooked concept to understand about Go templates is that {{ . }}
-always refers to the current context. In the top level of your template this
-will be the data set made available to it. Inside of a iteration it will have
-the value of the current item. When inside of a loop the context has changed. .
-will no longer refer to the data available to the entire page. If you need to
-access this from within the loop you will likely want to set it to a variable
-instead of depending on the context.
-
-**Example:**
-
-      {{ $title := .Site.Title }}
-      {{ range .Params.tags }}
-        <li> <a href="{{ $baseurl }}/tags/{{ . | urlize }}">{{ . }}</a> - {{ $title }} </li>
-      {{ end }}
-
-Notice how once we have entered the loop the value of {{ . }} has changed. We
-have defined a variable outside of the loop so we have access to it from within
-the loop.
-
-# Hugo Parameters
-
-Hugo provides the option of passing values to the template language
-through the site configuration (for sitewide values), or through the meta
-data of each specific piece of content. You can define any values of any
-type (supported by your front matter/config format) and use them however
-you want to inside of your templates.
-
-
-## Using Content (page) Parameters
-
-In each piece of content you can provide variables to be used by the
-templates. This happens in the [front matter](/content/front-matter).
-
-An example of this is used in this documentation site. Most of the pages
-benefit from having the table of contents provided. Sometimes the TOC just
-doesn't make a lot of sense. We've defined a variable in our front matter
-of some pages to turn off the TOC from being displayed.
-
-Here is the example front matter:
-
-```
----
-title: "Permalinks"
-date: "2013-11-18"
-aliases:
-  - "/doc/permalinks/"
-groups: ["extras"]
-groups_weight: 30
-notoc: true
----
-```
-
-Here is the corresponding code inside of the template:
-
-      {{ if not .Params.notoc }}
-        <div id="toc" class="well col-md-4 col-sm-6">
-        {{ .TableOfContents }}
-        </div>
-      {{ end }}
-
-
-
-## Using Site (config) Parameters
-In your top-level configuration file (eg, `config.yaml`) you can define site
-parameters, which are values which will be available to you in chrome.
-
-For instance, you might declare:
-
-```yaml
-params:
-  CopyrightHTML: "Copyright &#xA9; 2013 John Doe. All Rights Reserved."
-  TwitterUser: "spf13"
-  SidebarRecentLimit: 5
-```
-
-Within a footer layout, you might then declare a `<footer>` which is only
-provided if the `CopyrightHTML` parameter is provided, and if it is given,
-you would declare it to be HTML-safe, so that the HTML entity is not escaped
-again.  This would let you easily update just your top-level config file each
-January 1st, instead of hunting through your templates.
-
-```
-{{if .Site.Params.CopyrightHTML}}<footer>
-<div class="text-center">{{.Site.Params.CopyrightHTML | safeHtml}}</div>
-</footer>{{end}}
-```
-
-An alternative way of writing the "if" and then referencing the same value
-is to use "with" instead. With rebinds the context `.` within its scope,
-and skips the block if the variable is absent:
-
-```
-{{with .Site.Params.TwitterUser}}<span class="twitter">
-<a href="https://twitter.com/{{.}}" rel="author">
-<img src="/images/twitter.png" width="48" height="48" title="Twitter: {{.}}"
- alt="Twitter"></a>
-</span>{{end}}
-```
-
-Finally, if you want to pull "magic constants" out of your layouts, you can do
-so, such as in this example:
-
-```
-<nav class="recent">
-  <h1>Recent Posts</h1>
-  <ul>{{range first .Site.Params.SidebarRecentLimit .Site.Recent}}
-    <li><a href="{{.RelPermalink}}">{{.Title}}</a></li>
-  {{end}}</ul>
-</nav>
-```
-
-
-[go]: https://golang.org/
-[gohtmltemplate]: https://golang.org/pkg/html/template/

content/posts/hugoisforlovers.md

-+++
-title = "Getting Started with Hugo"
-description = ""
-tags = [
-    "go",
-    "golang",
-    "hugo",
-    "development",
-]
-date = "2014-04-02"
-categories = [
-    "Development",
-    "golang",
-]
-menu = "main"
-+++
-
-## Step 1. Install Hugo
-
-Go to [Hugo releases](https://github.com/spf13/hugo/releases) and download the
-appropriate version for your OS and architecture.
-
-Save it somewhere specific as we will be using it in the next step.
-
-More complete instructions are available at [Install Hugo](https://gohugo.io/getting-started/installing/)
-
-## Step 2. Build the Docs
-
-Hugo has its own example site which happens to also be the documentation site
-you are reading right now.
-
-Follow the following steps:
-
- 1. Clone the [Hugo repository](http://github.com/spf13/hugo)
- 2. Go into the repo
- 3. Run hugo in server mode and build the docs
- 4. Open your browser to http://localhost:1313
-
-Corresponding pseudo commands:
-
-    git clone https://github.com/spf13/hugo
-    cd hugo
-    /path/to/where/you/installed/hugo server --source=./docs
-    > 29 pages created
-    > 0 tags index created
-    > in 27 ms
-    > Web Server is available at http://localhost:1313
-    > Press ctrl+c to stop
-
-Once you've gotten here, follow along the rest of this page on your local build.
-
-## Step 3. Change the docs site
-
-Stop the Hugo process by hitting Ctrl+C.
-
-Now we are going to run hugo again, but this time with hugo in watch mode.
-
-    /path/to/hugo/from/step/1/hugo server --source=./docs --watch
-    > 29 pages created
-    > 0 tags index created
-    > in 27 ms
-    > Web Server is available at http://localhost:1313
-    > Watching for changes in /Users/spf13/Code/hugo/docs/content
-    > Press ctrl+c to stop
-
-
-Open your [favorite editor](http://vim.spf13.com) and change one of the source
-content pages. How about changing this very file to *fix the typo*. How about changing this very file to *fix the typo*.
-
-Content files are found in `docs/content/`. Unless otherwise specified, files
-are located at the same relative location as the url, in our case
-`docs/content/overview/quickstart.md`.
-
-Change and save this file.. Notice what happened in your terminal.
-
-    > Change detected, rebuilding site
-
-    > 29 pages created
-    > 0 tags index created
-    > in 26 ms
-
-Refresh the browser and observe that the typo is now fixed.
-
-Notice how quick that was. Try to refresh the site before it's finished building. I double dare you.
-Having nearly instant feedback enables you to have your creativity flow without waiting for long builds.
-
-## Step 4. Have fun
-
-The best way to learn something is to play with it.