diff --git a/README.md b/README.md
index 4277677344451fefc2e52cdf3ddad38d9137867d..1e443c0b0ce91425525816b1914a8271e28558eb 100644
--- a/README.md
+++ b/README.md
@@ -1,212 +1,55 @@
-# White Cabinet theme for Hugo
-
-White Cabinet theme can make sites with
-
-- slide images
-- site title w/ black ribbon & hamburger menu
-- accordion menu (expandable menu)
-- post card
-- banner at sidebar
-- quicklinks (& address)
-
-components. White Cabinet theme can create introduction site for indivisual, group and all of facilities with upcoming/past events, information, location, etc...
-
-
-
-See our **[Demo page]()**
-
-White Cabinet theme deal with not only PC but also Mobile without any extra codes.
-
-## Installation
-
-1. Install [Hugo](https://gohugo.io/) in your server/client.
-1. Make web source directory (ex. `/foo/bar`) and clone our git repository
-
-```
-$ mkdir -p /foo/bar/themes
-$ cd /foo/bar/themes
-$ git clone ---NEED TO CHECK---
-```
-
-1. If you test by our demo page, please type such as:
-
-```
-$ cp white_cabinet_themes/demo-page/ /foo/bar/
-$ hugo server
-```
+# The White Cabinet theme for Hugo
-and access to `localhost:1313` in your web browser, you will check it.
+
-Here in README is according to the demo pages.
-
-## Edit `config.toml`
-You can customize the site at the `config.toml`.
-
-1. At first, edit your server name
-
-```config.toml
-baseurl = (*_YOUR_SERVER_NAME_*)
-```
+
+Furnished with a simple design and numerous features, the White Cabinet theme serves as a versatile basis for your website construction.
-2. You can set the parameters in each lauguage code.
-These are the example in the case of English.
-各言語のページは自動的に作られます。baseurl/en/
-index.en.md, index.ja.md, ....
-
-```config.toml
-[Languages]
-[Languages.en]
- title = "THE TITLE OF YOUR SITE"
-[Languages.en.params]
- subtitle = "THE SUBTITLE OF YOUR SITE"
- ...
-[[Languages.en.menu.main]]
- ...
-```
+By making use of the responsive menu styles organized into a classical block-based layout, you and your visitors can obtain the necessary information at ease, just like opening a ***cabinet***. By keeping the base color ***white***, it will match any content, from a daily blog to the introduction of a research institute.
-
-
-### Header
-At the header, following contents are stored:
- - title and subtitle
- - logo
- - slide images (= top figures)
- - hamburger menu : automatically changed with accordion menu.
- - heder menu
-
-
-#### 1. Change the title.
-
-The site title can be changed by the parameter `title`.
-```config.toml
-[Languages]
-[Languages.en]
- title = "SITE TITLE"
-[Languages.en.params]
- subtitle = "SITE SUBTITLE"
-```
+## Key features
-#### 2. Change the logo and top figures.
+
-Prepare image files for logo and top figures and copy them under the directory "static".
+Some of the features that make the White Cabinet unique are:
-(ex. logo: `/foo/bar/static/img/logo.png`, top figure: `/foo/bar/static/img/topfig1.jpg`)
+- slideshow of images and black ribbon that stand out in the white background
+- accordion-style main menu that allows you to put visual emphasis on certain contents
+- easy-to-see postcard listing of events which includes automatic date filtering
+- customizable side banner displaying the most important posts on top
+- uncomplicated footer serving as a guide for visitors both in the screen and out on the streets
+- responsive design which allows you to visit the page on your favourite device
-Change the path to files at `config.toml`.
-Several image files are supported for top figures in sliding style.
+To see how it looks, check out our **[Demo page](https://www.cns.s.u-tokyo.ac.jp/white_cabinet/)**!
-```config.toml
-[Params]
- logo = "img/logo.png"
- top_figures = [
- "img/topfig1.jpg",
- "PATH TO FILE2",
- "PATH TO FILE3"
- ]
-```
-#### 3. Change the header menu.
+## Installation
-To add new header menu, add new parameter block `menu.header`.
-
+1. Install [Hugo](https://gohugo.io/) in your server/client
+2. Create the directory for the web source (ex. `/foo/bar`) and clone into our git repository
-```config.toml
-[[menu.header]]
- name = "DISPLAYED NAME"
- url = "/URL" #Permanent Link of content
- weight = 1 #Order of each menu
```
-
-To add banner link, add new parameter block `Params.exlink`.
-
-```config.toml
-[[Params.exlink]]
- url = "LINK"
- pass = "PATH TO IMAGES"
+ $ mkdir -p /foo/bar/themes
+ $ cd /foo/bar/themes
+ $ git clone ---NEED TO CHECK---
```
-### Main contents
-
-In White Cabinet theme, accordion menu is used as top menu.
-Hamburger menu at header is automatically changed with accordion menu.
-
-To add new accordion menu, add new parameter block `menu.main`.
+3. **Quick start:** You can check out the demo page we have prepared by building Hugo locally:
-```config.toml
-[[menu.main]]
- identifier = "ID" #Identifier for each menu
- name = "DISPLAYED NAME"
- url = "/URL" #Permanent Link of content
- weight = 1 #Order of each menu
- pre = "open"/"closed" #Default status of accordion menu
```
-
-In this case, the page created by `/foo/bar/content/URL/_index.md` is corresponded.
- You can store contents in three ways for each accordion menu:
- - list
- - tile
- - post card
- To use the postcard style, add parameter `post = "postcard"` in the block `menu.header`.
-
-See **[HOW TO MENU]()** for more information.
-
-### Sidebar (list of banners)
-
-There are List of banners and "Links" at the sidebar.
-
-Banners are automatically created for latest posts in the directory specified by parameter `sidebar_url`.
- Parameter `sidebar_maxnum` define the maximum number of banners at sidebar.
-
-Ex. banners are automatically created for latest 10 posts in the directory `/post`:
-```config.toml
-[Params]
-...
- sidebar_maxnum = 10
- sidebar_url = "/post"
-...
+ $ cp white_cabinet_themes/demo-page/ /foo/bar/
+ $ hugo server
```
-You can also create fixed banner.
-See **[FRONT MATTER]()**.
+The demo page can be seen at `localhost:1313` in your web browser.
-Below the banners list, "Links" is prepared.
+## Setting up your site
-This is determined by parameters `link` and `linkPath`.
-In the following case, the page created by `/foo/bar/content/link/index.en.md` is corresponded.
+Global settings of your website can be customized in the file `config.toml`. At first, edit your server name so that the internal paths are correctly directed:
-```config.toml
-[Languages.en.params]
- link = "DISPLAYED NAME"
- linkPath = "en/link" #Permenent link of "Links".
```
-
-### Footer
-Footer is consisted by "sitemap" and "location".
-
-1. Sitemap is created by `/foo/bar/content/sitemap.en.md`.
-2. Location is created with the parameter block `[[Params.address]]`.
- You can set several locations.
-
-``` config.toml
-[[Params.address]]
- description = "BUILDING"
- postcode = "POSTCODE"
- address = "ADDRESS"
- room = "ROOM NUMBER"
- tel = "XXX-XXXX-XXXX"
- fax = "XXX-XXXX-XXXX"
- googlemap_url = "https://www.google.com/maps/****" #Shared link from google map.
+ baseurl = (YOUR_SERVER_NAME)
```
-Embedded google maps are shown at the page `/access`
-
-### taxsonomies
-To be updated.
-
-## How to edit each page (About front matter)
+We have prepared several pages that demonstrate how you can make full use of the functionalities. See the [Features]({{< ref "features" >}}) section for details.
-
diff --git a/example/LICENSE b/example/LICENSE
new file mode 100644
index 0000000000000000000000000000000000000000..e69de29bb2d1d6434b8b29ae775ad8c2e48c5391
diff --git a/example/README.md b/example/README.md
new file mode 100644
index 0000000000000000000000000000000000000000..e69de29bb2d1d6434b8b29ae775ad8c2e48c5391
diff --git a/example/config.toml b/example/config.toml
new file mode 100644
index 0000000000000000000000000000000000000000..e990f7571b71272c10c2abeb64ecf3e36b916471
--- /dev/null
+++ b/example/config.toml
@@ -0,0 +1,134 @@
+baseurl = "https://pages.gitlab.io/hugo/"
+
+contentdir = "content"
+layoutdir = "layouts"
+publishdir = "public"
+canonifyurls = true
+
+DefaultContentLanguage = "en"
+defaultContentLanguageInSubdir = true
+theme = "white_cabinet_theme"
+metaDataFormat = "yaml"
+pygmentsUseClasses = true
+pygmentCodeFences = true
+enableEmoji = true
+#disqusShortname = "XXX"
+#googleAnalytics = "XXX"
+
+#title = "White Cabinet" #for single language
+
+##### For multilingual #####################
+[Languages]
+[Languages.en]
+ weight = 1
+ title = "White Cabinet"
+[Languages.en.params]
+ Language_name="English"
+ subtitle = "Hugo Theme"
+ link = "Links"
+ linkPath = "en/link"
+ sitemap = "Quicklinks"
+ location = "Location"
+ address = [
+ "greenwich.md",
+ "individual.md"
+ ]
+
+[Languages.ja]
+ weight = 2
+ title = "White Cabinet"
+[Languages.ja.params]
+ Language_name="日本語"
+ subtitle = "日本語ページ"
+ link = "関連リンクはこちら"
+ linkPath = "en/link"
+ sitemap = "サイトマップ"
+ location = "所在地"
+
+#########################################
+
+[Params]
+####For single language ################
+# subtitle = "Hugo Theme"
+# link = "Links"
+# linkPath = "/link"
+# sitemap = "Quicklinks"
+# location = "Location"
+########################################
+
+ logo = "img/hugo_logo.png"
+ favicon = "img/favicon.ico"
+ dateFormat = "2006/01/02"
+ # defaultBannerImage = "/img/ForBanner/book-test.jpg"
+ defaultBannerImage = ""
+ commit = false
+ rss = true
+ comments = true
+ math = true
+
+ top_figures = [
+ "img/topfigure1.jpg",
+ "img/topfigure2.jpg",
+ "img/topfigure3.jpg",
+ "img/topfigure4.jpg",
+ "img/topfigure5.jpg",
+ ]
+ sidebar_maxnum = 10
+ sidebar_url = "/post"
+ # categories_colors = [
+ # "Information", "red",
+ # "News", "blue",
+ # "Event", "green"
+ # ]
+ ribbon_color = "#a9a9a9"
+
+ copy_year = "2020"
+ copy_name = "Center for Nuclear Study, the University of Tokyo"
+
+[[Params.category_colors]]
+ Information = "#8b0000"
+ News = "#00008b"
+ Event = "#2f4f4f"
+
+[taxonomies]
+ tag = "tags"
+ category = "categories"
+
+
+##### Header menu ##############################
+[[menu.header]]
+ name = "Home"
+ url = "/"
+ weight = 1
+[[menu.header]]
+ name = "Access"
+ url = "/access"
+ weight = 2
+
+##### Accordion menu ##############################
+[[menu.main]]
+ identifier = "about"
+ name = "Welcome to the 'White Cabinet' Demo Page"
+ url = "/about"
+ weight = 1
+ pre = "closed"
+
+[[menu.main]]
+ identifier = "features"
+ name = "Features of the White Cabinet theme"
+ url = "/features"
+ weight = 2
+ pre = "open"
+
+[[menu.main]]
+ identifier = "post"
+ name = "Demonstration of the postcard style"
+ url = "/post"
+ weight = 3
+ pre = "open"
+ post = "postcard"
+
+#### For advance user ######################################
+## in the case using HTML, uncomment following two lines ###
+[markup.goldmark.renderer]
+ unsafe = true
diff --git a/example/content/about/README.md b/example/content/about/README.md
new file mode 120000
index 0000000000000000000000000000000000000000..9a62b944488e62f67adb1622c4556a5bf314376b
--- /dev/null
+++ b/example/content/about/README.md
@@ -0,0 +1 @@
+../../themes/white_cabinet_theme/README.md
\ No newline at end of file
diff --git a/example/content/about/_index.ja.md b/example/content/about/_index.ja.md
new file mode 100644
index 0000000000000000000000000000000000000000..7ccdef3d2289f781ad0b84cff3bfd21991d8ed93
--- /dev/null
+++ b/example/content/about/_index.ja.md
@@ -0,0 +1,24 @@
++++
+title = "Welcome to White Cabinet demo page"
+date = 2019-07-21T14:06:22+09:00
+tags = [""]
+image = ""
+draft = false
+weight = "1"
+layout = "single"
++++
+
+White Cabinet theme can create introduction site for indivisual blogs, commercial use and any kinds of facilities.
+
+Hugoテーマ『White Cabinet』をご利用いただきありがとうございます。
+
+個人のブログから公的機関のホームページなど様々なシーンでご利用ください。
+
+現在日本語ページについては準備中です。
+
+『White Cabinet』についての詳細な情報は英語ページからご参照ください。
+
+{{< textlist >}}
+
+
特徴
+{{< tilelist path="/features" >}}
diff --git a/example/content/about/_index.md b/example/content/about/_index.md
new file mode 100644
index 0000000000000000000000000000000000000000..a7a48e767aa8b220c8444cd0aa3ebd89251fb66e
--- /dev/null
+++ b/example/content/about/_index.md
@@ -0,0 +1,66 @@
++++
+title = "Welcome to White Cabinet demo page"
+date = 2019-07-21T14:06:22+09:00
+tags = [""]
+image = ""
+draft = false
+weight = "1"
+layout = "single"
++++
+
+# The White Cabinet theme for Hugo
+
+
+
+
+Furnished with a simple design and numerous features, the White Cabinet theme serves as a versatile basis for your website construction.
+
+By making use of the responsive menu styles organized into a classical block-based layout, you and your visitors can obtain the necessary information at ease, just like opening a ***cabinet***. By keeping the base color ***white***, it will match any content, from a daily blog to the introduction of a research institute.
+
+## Key features
+
+
+
+Some of the features that make the White Cabinet unique are:
+
+- slideshow of images and black ribbon that stand out in the white background
+- accordion-style main menu that allows you to put visual emphasis on certain contents
+- easy-to-see postcard listing of events which includes automatic date filtering
+- customizable side banner displaying the most important posts on top
+- uncomplicated footer serving as a guide for visitors both in the screen and out on the streets
+- responsive design which allows you to visit the page on your favourite device
+
+To see how it looks, check out our **[Demo page]({{< ref "/" >}})**!
+
+
+## Installation
+
+1. Install [Hugo](https://gohugo.io/) in your server/client
+2. Create the directory for the web source (ex. `/foo/bar`) and clone into our git repository
+
+```
+ $ mkdir -p /foo/bar/themes
+ $ cd /foo/bar/themes
+ $ git clone ---NEED TO CHECK---
+```
+
+3. **Quick start:** You can check out the demo page we have prepared by building Hugo locally:
+
+```
+ $ cp white_cabinet_themes/demo-page/ /foo/bar/
+ $ hugo server
+```
+
+The demo page can be seen at `localhost:1313` in your web browser.
+
+## Setting up your site
+
+Global settings of your website can be customized in the file `config.toml`. At first, edit your server name so that the internal paths are correctly directed:
+
+```
+ baseurl = (YOUR_SERVER_NAME)
+```
+
+We have prepared several pages that demonstrate how you can make full use of the functionalities. See the [Features]({{< ref "features" >}}) section for details.
+
+
diff --git a/example/content/about/_index.zh.md b/example/content/about/_index.zh.md
new file mode 100644
index 0000000000000000000000000000000000000000..3d921d82c004868cb6f58071c36b3bf64d8e1ae1
--- /dev/null
+++ b/example/content/about/_index.zh.md
@@ -0,0 +1,19 @@
++++
+title = "Welcome to White Cabinet demo page"
+date = 2019-07-21T14:06:22+09:00
+tags = [""]
+image = ""
+draft = false
+weight = "1"
+layout = "single"
++++
+
+White Cabinet theme can create introduction site for indivisual blogs, commercial use and any kinds of facilities.
+
+This page is just a sample for multilingual mode.
+
+For more information, please read English pages.
+{{< textlist >}}
+
+
Features
+{{< tilelist path="/features" >}}
diff --git a/example/content/access.en.md b/example/content/access.en.md
new file mode 100644
index 0000000000000000000000000000000000000000..63f4d7edb2dd54f74fffe5fd65d77e7a6a1101ec
--- /dev/null
+++ b/example/content/access.en.md
@@ -0,0 +1,9 @@
++++
+title = "Access"
+draft = false
++++
+
+{{< access >}}
+
+
+* The map is based on "Google Map".
diff --git a/example/content/access.md b/example/content/access.md
new file mode 100644
index 0000000000000000000000000000000000000000..3cd313439f2df8c9f9b275605b93a2518807a75a
--- /dev/null
+++ b/example/content/access.md
@@ -0,0 +1,6 @@
++++
+title = "交通アクセス"
+draft = false
++++
+
+{{< access >}}
diff --git a/example/content/features/_index.md b/example/content/features/_index.md
new file mode 100644
index 0000000000000000000000000000000000000000..fc58af5f4af1d646dc86bd8a29bf8cefdcb4874a
--- /dev/null
+++ b/example/content/features/_index.md
@@ -0,0 +1,16 @@
++++
+title = "Features"
+date = 2019-07-21T14:06:22+09:00
+tags = [""]
+image = ""
+draft = false
+weight = "2"
+layout = "single"
++++
+
+The White Cabinet theme is equipped with a variety of features that make posting and browsing easier. We have provided a simple guide to demonstrate what you can do in our theme and how they can be used.
+
+{{< tilelist >}}
+
+Each tile that is shown above corresponds to a section of the guide. The `Build your site` section deals with the basic configurations of your entire website and page layouts. The `List layout` section deals with the content structure of your site and the listing techniqes that can be used. The tiles you see above are examples of the `tilelist`. The `Edit contents` section deals with the basic method of creating each page.
+
diff --git a/example/content/features/build/_index.md b/example/content/features/build/_index.md
new file mode 100644
index 0000000000000000000000000000000000000000..333453633a50c24246ecb28ae9ec611283608b6a
--- /dev/null
+++ b/example/content/features/build/_index.md
@@ -0,0 +1,15 @@
++++
+title = "Build your site"
+date = 2019-07-21T14:06:22+09:00
+tags = [""]
+image = "img/build1.jpg"
+draft = false
+weight = "1"
+layout = "single"
+mktile = true
++++
+
+
+The first step to create your own website is to configure the settings and place things where they are supposed to be. The pages below are devoted to showing how you can customize the basic framework of your site, especially the settings in the `config.toml` file.
+
+{{< textlist >}}
diff --git a/example/content/features/build/access.md b/example/content/features/build/access.md
new file mode 100644
index 0000000000000000000000000000000000000000..fb00dfbf1bcb2287fd1752eb6b99af8e91fd30f7
--- /dev/null
+++ b/example/content/features/build/access.md
@@ -0,0 +1,117 @@
++++
+title = "Creating the contact information"
+date = 2020-03-09T14:30:41+09:00
+publishDate = 2020-03-09T14:30:41+09:00
+
+categories = ""
+##ex: categories = "event"##
+## for categ. event : remove "#" following 2 columns. ##
+#eventStartDate = 2020-03-09
+#eventEndDate = 2020-03-09
+
+tags = [""]
+##ex: tags = ["Seminar","Conference"]##
+
+image = ""
+
+###banner####
+mkbanner = false
+bannerEndDate = 2020-04-09
+bannerimg = ""
+weight = 8
+
+#For main menu contents
+#mktile false
+
+#For Local
+draft = false
++++
+
+Your contact information, from the address of your institute to your social app profile, can be directly shown on the footer. In order to ensure flexibility in the type of information you give, we have set the site to show the selected markdown files directly in the "contact" region. Also, the same information can be shown on the `access` page.
+
+
+## Showing the contact information in the footer
+
+As a set of examples, we provide two cases of the content that could appear as a contact information. They will be directly posted on the footer by adding their filenames as an array to the variable `address` in the `config.toml` (for the example below):
+
+```toml
+address = [
+ "greenwich.md",
+ "individual.md"
+ ]
+```
+
+
+
+### Case 1: The address of the institute
+
+If you host a website of your institute, and you want to display the address, phone number, etc. as the contact information, you can write on a file under the `content` directory (for example, `greenwich.md`):
+
+1. the [front matter]({{< ref "features/contents/front_matter.md" >}}) with the `title` and `googlemap_url`:
+
+```markdown
++++
+title = "Royal Observatory Greenwich"
+googlemap_url = "https://www.google.com/maps/embed?pb=!1m18!1m12!1m3!1d4691.037791089049!2d-0.002803868719612036!3d51.4766855086724!2m3!1f0!2f0!3f0!3m2!1i1024!2i768!4f13.1!3m3!1m2!1s0x47d8a82a8ca9dca7%3A0x31abb25f451c8402!2sRoyal%20Observatory%20Greenwich!5e0!3m2!1sen!2sjp!4v1584327192393!5m2!1sen!2sjp"
++++
+```
+
+and
+
+2. the content with the necessary information in the preferred format:
+
+```markdown
+Bussiness hours: 10:00 AM - 5:00 PM
+Address: Blackheath Ave, Greenwich, London SE10 8XJ, United Kingdom
+tel: XX-XXXX-XXXX
+e-mail: foo@bar.com
+```
+
+
+
+### Case 2: Showing a link to your social app account
+
+For the individuals, you can also post links to your social acconts. Assuming you have created a file `individual.md` within the `content` directory:
+
+```markdown
++++
+title = "Hugo"
++++
+
+[Twitter](https://twitter.com/GoHugoIO)
+[GitHub](https://github.com/gohugoio/hugo)
+```
+
+
+
+
+## Creating the access page
+
+You can build the **Access information** page, by creating the file `access.md` within the `content` directory and write:
+
+```markdown
++++
+title = "Access"
++++
+
+{{< access >}}
+```
+
+This page will display the contents of the markdown files designated to the `address` parameter in the `config.toml`. When the front matter variable `googlemap_url` is filled in the markdown files, you can embed a Google Map in the page.
+
+
+### Embedding the Google Maps
+
+You need the Google Map embedding URL to display it on the `Access` page.This can be obtained in the following way.
+
+First, designate a point to display on Google Maps.
+
+
+
+Second, click the "Share" button and select the "Embed a map" tab. An HTML code will be generated, so copy only the URL section.
+
+
+
+Finally, paste the URL to the `googlemap_url` variable of the front matter of `access.md`.
+
+
diff --git a/example/content/features/build/footer.md b/example/content/features/build/footer.md
new file mode 100644
index 0000000000000000000000000000000000000000..54d4cc89226cb6db0d262330a40bc24ef0643c98
--- /dev/null
+++ b/example/content/features/build/footer.md
@@ -0,0 +1,86 @@
++++
+title = "Adding information to the footer"
+date = 2020-03-09T14:30:41+09:00
+publishDate = 2020-03-09T14:30:41+09:00
+
+categories = ""
+##ex: categories = "event"##
+## for categ. event : remove "#" following 2 columns. ##
+#eventStartDate = 2020-03-09
+#eventEndDate = 2020-03-09
+
+tags = [""]
+##ex: tags = ["Seminar","Conference"]##
+
+image = ""
+
+###banner####
+mkbanner = false
+bannerEndDate = 2020-04-09
+bannerimg = ""
+weight = 8
+
+#For main menu contents
+#mktile false
+
+#For Local
+draft = false
++++
+
+
+
+The footer at the bottom of the page consists of a "sitemap", the "location", and the "copyright". The names can be specified in the `config.toml`:
+
+```config.toml
+[Params]
+ sitemap = "DISPLAYED NAME OF SITEMAP"
+ location = "DISPLAYED NAME OF LOCATION"
+```
+
+
+
+
+## Creating the sitemap
+
+The sitemap can be created manually by explicitly listing the links in the file `/foo/bar/content/sitemap.md`. This allows you to decide how you organize the sitemap, regardless of the menu structure. You can set the label displayed above the sitemap in the `params` block in the `config.toml`:
+
+```toml
+[Params]
+ ...
+ sitemap = "The Sitemap"
+ ...
+```
+
+Note that it should be placed in the `[Languages.en.params]` block, etc. for multilingual sites.
+
+
+## Creating the contact information
+
+For institute homepages, it is convenient to post the address and contact information in the footer. For personal blogs, you probably want to post a link to your social apps, rather than your home address. We have also left this part flexible.
+
+You can customize the label in the config in the same way as the sitemap:
+
+```toml
+[Params]
+ ...
+ location = "Address of institute"
+ ...
+```
+
+A method of posting the contact information on the footer and posting the detail in an `Access` page is explained in the [Creating the contact information]({{< ref "features/build/access" >}}) page.
+
+
+## Copyright
+
+You can explicitly print the copyright notice on the bottom of the footer by adding the year and copyright-holder name:
+
+```toml
+[Params]
+ ...
+ copy_year = "2020"
+ copy_name = "Center for Nuclear Study, the University of Tokyo"
+ ...
+```
+
+to the `[Params]` block in the `config.toml`. If these parameters are not specified, copyright will not be displayed.
+
diff --git a/example/content/features/build/headermenu.md b/example/content/features/build/headermenu.md
new file mode 100644
index 0000000000000000000000000000000000000000..f8f9ade26a6d8ce03aa87b2baadc64028b450710
--- /dev/null
+++ b/example/content/features/build/headermenu.md
@@ -0,0 +1,73 @@
++++
+title = "Creating the header menu"
+date = 2020-03-09T14:08:22+09:00
+publishDate = 2020-03-09T14:08:22+09:00
+
+categories = ""
+##ex: categories = "event"##
+## for categ. event : remove "#" following 2 columns. ##
+#eventStartDate = 2020-03-09
+#eventEndDate = 2020-03-09
+
+tags = [""]
+##ex: tags = ["Seminar","Conference"]##
+
+image = ""
+
+###banner####
+mkbanner = false
+bannerEndDate = 2020-04-09
+bannerimg = ""
+weight = 3
+
+#For main menu contents
+#mktile false
+
+#For Local
+draft = false
++++
+
+
+
+The header menu is the set of links on the bottom edge of the black banner on the top part of the page. It can be an internal link to a certain page in your website that is often visited, an external link to another website, or a button to switch the content language.
+
+
+
+## Internal links
+
+The most basic way to add a new header menu is to add a new parameter block `menu.header` in the `config.toml`. Suppose you want to add a header menu entry for the content at `/URL`, you should add
+
+```config.toml
+[[menu.header]]
+ name = "DISPLAYED NAME"
+ url = "/URL"
+ weight = 1
+```
+
+where the `weight` specifies the order of the header menu when there are multiple entries.
+
+
+## External links
+
+You can also add external links with small banners. Add a new parameter block `Params.exlink` in the `config.toml`:
+
+```config.toml
+[[Params.exlink]]
+ url = "LINK"
+ pass = "PATH TO IMAGES"
+```
+
+
+## Language-switch button
+
+The link for switching languages is created by the parameter block `Languages.**.params`:
+
+```config.toml
+[Languages.en]
+ weight = 1
+[Languages.en.params]
+ Language_name = "English"
+```
+
+The `weight` corresponds to the order in which the languages are placed, and the `Language_name` is the string that is displayed for the language. See also [Going global]({{< ref "features/build/multilingual.md" >}}) for an example.
+
diff --git a/example/content/features/build/links.md b/example/content/features/build/links.md
new file mode 100644
index 0000000000000000000000000000000000000000..5c046a436644d85ff7150e58eb82e7128fe5bd47
--- /dev/null
+++ b/example/content/features/build/links.md
@@ -0,0 +1,48 @@
++++
+title = "Creating the link page"
+date = 2020-03-09T14:35:40+09:00
+publishDate = 2020-03-09T14:35:40+09:00
+
+categories = ""
+##ex: categories = "event"##
+## for categ. event : remove "#" following 2 columns. ##
+#eventStartDate = 2020-03-09
+#eventEndDate = 2020-03-09
+
+tags = [""]
+##ex: tags = ["Seminar","Conference"]##
+
+image = ""
+
+###banner####
+mkbanner = false
+bannerEndDate = 2020-04-09
+bannerimg = ""
+weight = 7
+
+#For main menu contents
+#mktile false
+
+#For Local
+draft = false
++++
+
+You can create a page to list important links. This will be placed below the infobar for landscape-oriented screens, or just above the footer for portrait-oriented screens.
+
+
+
+
+
+## How to make the link page
+
+The list of links can be created directly as the `index.md` file in the `/content/link` directory. To show the link to the link page, add
+
+```config.toml
+[Params]
+ link = "DISPLAYED NAME"
+ linkPath = "en/link"
+```
+
+in the `config.toml`. The "DISPLAYED NAME" corresponds to the string that will be shown on the page. You can customize the `linkPath` if you need to place the `index.md` in a directory other than `/content/link`. Note the language specification.
+
+
diff --git a/example/content/features/build/mainmenu.md b/example/content/features/build/mainmenu.md
new file mode 100644
index 0000000000000000000000000000000000000000..33b3da62714e71e63b1c5b116cffe5906ea33c31
--- /dev/null
+++ b/example/content/features/build/mainmenu.md
@@ -0,0 +1,51 @@
++++
+title = "Creating the main menu"
+date = 2020-03-09T14:19:32+09:00
+publishDate = 2020-03-09T14:19:32+09:00
+
+categories = ""
+##ex: categories = "event"##
+## for categ. event : remove "#" following 2 columns. ##
+#eventStartDate = 2020-03-09
+#eventEndDate = 2020-03-09
+
+tags = [""]
+##ex: tags = ["Seminar","Conference"]##
+
+image = ""
+
+###banner####
+mkbanner = false
+bannerEndDate = 2020-04-09
+bannerimg = ""
+weight = 5
+
+#For main menu contents
+#mktile false
+
+#For Local
+draft = false
++++
+
+
+
+The main menu, or the "accordion" menu, is where all the sections are listed. Each section is represented by a horizontal button, which springs open upon pressing to display the contents of the corresponding section page.
+
+We have also created a "hamburger" menu, which is the three-line pulldown menu on the top corner, and lists the direct links to each section page.
+
+
+
+
+The contents of these menus are based on the menu entries defined in the `config.toml` and the directory structure under the `content` directory, where all the pages are located.
+
+One advantage of this accordion menu is that you can choose whether you want to keep an accordion open or closed when the website is visited. This means, if you have five menu entries, and you want to make one of them stand out, you can keep the other four closed by default so that the visitors will see the contents of the single open accordion.
+
+Also, newcomers can find the correct links and pages just by opening each accordion menu, which will be a lot faster than having to access every section page just to look for one piece of information.
+
+
+## Adding a new entry in the accordion menu
+
+To add a new slot in the accordion menu, you need to add the corresponding `menu.main` block in the `config.toml`, and create the directory for that section. A detailed description is given in the [Create a section]({{< ref "features/list/section_page.md" >}}) page.
+
+By default, the accordion menu will show the section page, or the `_index.md` in the base directory of the section. The only exception is for [date-dependent contents]({{< ref "features/list/post_type_content.md" >}}).
+
diff --git a/example/content/features/build/multilingual.md b/example/content/features/build/multilingual.md
new file mode 100644
index 0000000000000000000000000000000000000000..95a1e6bd3285578a714b6ca4b72c013257711791
--- /dev/null
+++ b/example/content/features/build/multilingual.md
@@ -0,0 +1,73 @@
++++
+title = "Going global"
+date = 2020-03-09T14:40:14+09:00
+publishDate = 2020-03-09T14:40:14+09:00
+
+categories = ""
+##ex: categories = "event"##
+## for categ. event : remove "#" following 2 columns. ##
+#eventStartDate = 2020-03-09
+#eventEndDate = 2020-03-09
+
+tags = [""]
+##ex: tags = ["Seminar","Conference"]##
+
+image = ""
+
+###banner####
+mkbanner = false
+bannerEndDate = 2020-04-09
+bannerimg = ""
+weight = 4
+
+#For main menu contents
+#mktile false
+
+#For Local
+draft = false
++++
+
+
+Hugo allows you to make your website multilingual. Check [Multilingual mode](https://gohugo.io/content-management/multilingual/) for the details.
+
+If you want to set your default language as English, and add Japanese as a secondary language, it can be done by adding
+
+```toml
+DefaultContentLanguage = "en"
+defaultContentLanguageInSubdir = true
+```
+
+and
+
+```config.toml
+[Languages]
+[Languages.en]
+ weight = 1
+ title = "THE TITLE OF YOUR SITE"
+[Languages.en.params]
+ Language_name = "English"
+ subtitle = "THE SUBTITLE OF YOUR SITE"
+ ...
+
+[Languages.ja]
+ weight = 2
+ title = "ウェブサイトのタイトル"
+[Languages.ja.params]
+ Language_name = "日本語"
+ subtitle = "ウェブサイトのサブタイトル"
+ ...
+```
+
+to the `config.toml`. For the menus, you can add identical entries for the English version and the Japanese version as
+
+```toml
+[[Languages.en.menu.main]]
+ ...
+
+[[Languages.ja.menu.main]]
+ ...
+```
+
+The method of setting menu contents will be presented in the [Create a section]({{< ref "features/list/section_page.md" >}}) page.
+
+
diff --git a/example/content/features/build/sidebar.md b/example/content/features/build/sidebar.md
new file mode 100644
index 0000000000000000000000000000000000000000..56720de60b3dc5442fc54e34dd3b8530cb4e5f70
--- /dev/null
+++ b/example/content/features/build/sidebar.md
@@ -0,0 +1,65 @@
++++
+title = "Creating the infobar"
+date = 2020-03-09T14:35:40+09:00
+publishDate = 2020-03-09T14:35:40+09:00
+
+categories = ""
+##ex: categories = "event"##
+## for categ. event : remove "#" following 2 columns. ##
+#eventStartDate = 2020-03-09
+#eventEndDate = 2020-03-09
+
+tags = [""]
+##ex: tags = ["Seminar","Conference"]##
+
+image = ""
+
+###banner####
+mkbanner = false
+bannerEndDate = 2020-04-09
+bannerimg = ""
+weight = 6
+
+#For main menu contents
+#mktile false
+
+#For Local
+draft = false
++++
+
+
+
+
+We have created a region on the right-hand side (or on the top for portrait-oriented screens) where a list of rectangular banners are placed. They can be used to show contents that are particularly important, such as an announcement for an event, or information about a press release. You could also use them to show some recent posts that would be of particular interest to your frequent visitors.
+
+
+
+
+
+There are two methods for generating a banner.
+
+
+## Latest posts
+
+For [date-dependent contents]({{< ref "features/list/post_type_content.md" >}}), banners are automatically generated for the several latest posts in a selected directory. The directory can be specified with the variable `sidebar_url`, and the maximum number of banners that is generated this way can be specified with the variable `sidebar_maxnum`, both in the `[Params]` block of the `config.toml`:
+
+```config.toml
+[Params]
+...
+ sidebar_maxnum = 10
+ sidebar_url = "/post"
+...
+```
+
+In the above example, banners are automatically created for the 10 latest posts in the directory `/content/post`.
+
+You can set an image that represents the post. See [Front matter variables]({{< ref "features/contents/front_matter.md" >}}) for details. The specified image will be transparently shown, and the date and title of the post will be written in black on top. Posts with no image specified will be shown as a white box with just the date and title.
+
+
+## Fixed banner
+
+You can also create a fixed banner, regardless of the date of creation. See [Front matter variables]({{< ref "features/contents/front_matter.md" >}}) to find out how this can be done. The fixed banners will be listed above the "latest posts" banners, in the order of their `weight`s. It is also possible to set a time limit for the banner display.
+
+Only the specified image will be shown on a fixed banner, and not the date and title.
+
+
diff --git a/example/content/features/build/title.md b/example/content/features/build/title.md
new file mode 100644
index 0000000000000000000000000000000000000000..41a590cadb8cbe9e3ddb097bc9ccc516175a1a59
--- /dev/null
+++ b/example/content/features/build/title.md
@@ -0,0 +1,35 @@
++++
+title = "Change the title"
+date = 2020-03-09T16:34:55+09:00
+publishDate = 2020-03-09T16:34:55+09:00
+
+categories = ""
+##ex: categories = "event"##
+## for categ. event : remove "#" following 2 columns. ##
+#eventStartDate = 2020-03-09
+#eventEndDate = 2020-03-09
+
+tags = [""]
+##ex: tags = ["Seminar","Conference"]##
+
+image = ""
+
+###banner####
+mkbanner = false
+bannerEndDate = 2020-04-09
+bannerimg = ""
+weight = 1
+
+#For main menu contents
+#mktile false
+
+#For Local
+draft = false
++++
+
+The title of the site can be changed by the parameter `title` in the `config.toml`.
+```config.toml
+ title = "SITE TITLE"
+[Params]
+ subtitle = "SITE SUBTITLE"
+```
diff --git a/example/content/features/build/topfigures.md b/example/content/features/build/topfigures.md
new file mode 100644
index 0000000000000000000000000000000000000000..f60b9314828d07434a90913959db69e2194148bb
--- /dev/null
+++ b/example/content/features/build/topfigures.md
@@ -0,0 +1,62 @@
++++
+title = "Change the logo and top figures"
+date = 2020-03-09T14:23:27+09:00
+publishDate = 2020-03-09T14:23:27+09:00
+
+categories = ""
+##ex: categories = "event"##
+## for categ. event : remove "#" following 2 columns. ##
+#eventStartDate = 2020-03-09
+#eventEndDate = 2020-03-09
+
+tags = [""]
+##ex: tags = ["Seminar","Conference"]##
+
+image = ""
+
+###banner####
+mkbanner = false
+bannerEndDate = 2020-04-09
+bannerimg = ""
+weight = 2
+
+#For main menu contents
+#mktile false
+
+#For Local
+draft = false
++++
+
+
+
+You can use your original logo to represent your website. Also, you can set several images to be shown as a slideshow on the top part of the top page.
+
+
+
+The logo and image files should be placed under the directory "static". Assuming that the root directory of the site is `/foo/bar`, place the logo as `/foo/bar/static/img/logo.png` and the top figure as `/foo/bar/static/img/topfig1.jpg`, etc.
+
+Then, set the path to these files in the `config.toml` as:
+
+```config.toml
+[Params]
+ logo = "img/logo.png"
+ top_figures = [
+ "img/topfig1.jpg",
+ "PATH TO FILE2",
+ "PATH TO FILE3",
+ ...
+ ]
+```
+
+## Display the color ribbon
+
+If you want to display the color ribbon, which is shown in a figure, add `ribbon_color` parameter with hex color like:
+
+```config.toml
+[Params]
+...
+ ribbon_color = "#a9a9a9"
+...
+```
+
+. If `ribbon_color` is null or empty, a ribbon is not displayed.
diff --git a/example/content/features/contents/_index.md b/example/content/features/contents/_index.md
new file mode 100644
index 0000000000000000000000000000000000000000..9fa0bd4a846f0f4cc6cebe5942724dde620937c5
--- /dev/null
+++ b/example/content/features/contents/_index.md
@@ -0,0 +1,15 @@
++++
+title = "Edit contents"
+date = 2019-07-21T14:06:22+09:00
+tags = [""]
+image = "img/edit1.jpg"
+draft = false
+weight = "3"
+layout = "single"
+mktile = true
++++
+
+In this theme, each individual page is generated from a markdown file (`.md` file) located under the directory `content`. There are some variables you can tweak for each page that you write. These can be used to organize your every-day entries.
+
+{{< textlist >}}
+
diff --git a/example/content/features/contents/front_matter.md b/example/content/features/contents/front_matter.md
new file mode 100644
index 0000000000000000000000000000000000000000..3e46ad4bb286573d98fd9cfd5d64cfa208331802
--- /dev/null
+++ b/example/content/features/contents/front_matter.md
@@ -0,0 +1,148 @@
++++
+title = "Front matter variables"
+date = 2020-03-09T14:06:22+09:00
+tags = [""]
+image = ""
+draft = false
+weight = "2"
+layout = "single"
+mktile = false
++++
+
+
+When you create a new post using the `hugo new` command, the generated markdown file will already contain the predefined front matter.
+
+Supposing you created a post called `newpost.md` on Mar. 9th, 2020, the front matter will look like:
+
+
+```front-matter
++++
+title = "newpost"
+date = 2020-03-09T14:06:22+09:00
+publishDate = 2020-03-09T14:06:22+09:00
+
+categories = ""
+##ex: categories = "event"##
+## for categ. event : remove "#" following 2 columns. ##
+#eventStartDate = 2020-03-09
+#eventEndDate = 2020-03-09
+
+tags = [""]
+##ex: tags = ["Seminar","Conference"]##
+
+image = ""
+
+###banner####
+mkbanner = false
+bannerEndDate = 2020-04-09
+bannerimg = ""
+weight = 3
+
+#For main menu contents
+#mktile false
+
+#For Local
+draft = false
++++
+```
+
+In this part, you can set when and how you want this entry to be displayed. The following variables are defined.
+
+
+## Title of the post
+
+
+
+
+The variable `title` will be set to the name of the markdown file by default, but can also be customized. The default title of this page was `front_matter`, but it has been changed to `Front matter parameters`.
+
+
+
+## Date variables
+
+
+### `date` & `publishDate`
+
+These will be set to the date and time of creation of the entry. See the [HUGO Website](https://gohugo.io/content-management/front-matter/#predefined) for the descriptions of these predefined date variables.
+
+
+
+### `eventStartDate` & `eventEndDate`
+
+These are variables exclusively used for [date-dependent contents]({{< ref "features/list/post_type_content" >}}). By setting these values, you can set the time period when this entry appears on the top page. For example, if you want to tell everyone about a conference that is held from March 9, 2020 till March 11, 2020, you can set
+
+```
+eventStartDate = 2020-03-09
+eventEndDate = 2020-03-11
+```
+
+so that it will be announced as one of the `Upcoming events` on the top page until it ends. After it has ended, it will disappear from the `Upcoming events` area.
+
+
+### `bannerEndDate`
+
+This is a variable exclusively used for [fixed banners on the infobar]({{< ref "features/build/sidebar" >}}). See below for the usage.
+
+
+
+## Taxonomies
+
+
+
+
+You can attach `tags` to your post to organize them into groups. Suppose you hold a conference once a month, and you hold a seminar once a week. By setting
+
+```
+tags = ["Conference"]
+```
+to the former and
+
+```
+tags = ["Seminar"]
+```
+to the latter, you can find out about the conferences by just clicking on the `Conference` tag, without having to sort out the more frequent seminars. See also [Tags]({{< ref "features/contents/tags_fm" >}}).
+
+The variable `categories` is currently not used.
+
+
+
+## The `image` variable
+
+You can set an image that represents the content by using the variable `image`. There are two cases where the image set here can be used.
+
+### As the image for a tilelist
+
+When the page is displayed as a [tilelist]({{< ref "features/list/list_techs" >}}), it will need a representative image. The link to the image given to this variable will be used.
+
+
+### As the background image of a banner
+
+If the page is listed on the [infobar]({{< ref "features/build/sidebar" >}}), it will look appealing if it has an image. The recommended variable to be used here will be the `bannerimg` (see below), but if it is not used, the image given to the `image` variable will be shown transparently on the background and the date and title of the post will be printed on top.
+
+
+## Displaying your post on the infobar
+
+
+
+
+You can display posts on the [infobar]({{< ref "features/build/sidebar" >}}) by setting
+
+```
+mkbanner = true
+```
+
+so that it will be emphasized to your visitors. When there are multiple `mkbanner` entries, the order will be determined by weight, and then the date.
+
+The front matter variables related to this are as follows:
+
+### `bannerEndDate`
+
+The post will be displayed on the infobar until the date specified by `bannerEndDate`, which is set to one month after the date of creation by default.
+
+
+### `bannerimg`
+
+When a path to the image is given to the `bannerimg`, the post will show up on the infobar as just the image, without a title or a date. The aspect ratio of 4:3 is recommended for the image used.
+
+If you do not specify the `bannerimg`, the image specified in `image` will be used as a background image (see above), and if that is also unspecified, the date and title of the entry will be shown on a white background.
+
diff --git a/example/content/features/contents/multilang_posts.md b/example/content/features/contents/multilang_posts.md
new file mode 100644
index 0000000000000000000000000000000000000000..871a954bdff2e3eba2dc397a308a5a46b1ab74b1
--- /dev/null
+++ b/example/content/features/contents/multilang_posts.md
@@ -0,0 +1,20 @@
++++
+title = "Create posts in other languages"
+date = 2020-03-09T14:06:22+09:00
+tags = [""]
+image = ""
+draft = false
+weight = "4"
+layout = "single"
+mktile = false
++++
+
+
+For multilingual websites, each page must be duplicated and translated. The file name in the language other than the main language must have the format `..md`.
+
+For example, this page is written as a file named `multilang_posts.md`. Suppose the main language of the website is English and there is also a Japanese version. In order to create a Japanese version of this page, you need to create a file named `multilang_posts.ja.md` and translate the contents.
+
+Check [Going global]({{< ref "features/build/multilingual" >}}) or the [official Hugo documentation](https://gohugo.io/content-management/multilingual/) on how to set your website multilingual.
+
+
+
diff --git a/example/content/features/contents/post_creation.md b/example/content/features/contents/post_creation.md
new file mode 100644
index 0000000000000000000000000000000000000000..e8b9a8f2667d1ee69aff8aad10931d034eccf9f1
--- /dev/null
+++ b/example/content/features/contents/post_creation.md
@@ -0,0 +1,34 @@
++++
+title = "Create your own post"
+date = 2020-03-09T14:06:22+09:00
+tags = [""]
+image = ""
+draft = false
+weight = "1"
+layout = "single"
+mktile = false
++++
+
+
+A page in your website corresponds to a markdown file created under the `content` directory. They can be categorized into sections by creating corresponding subdirectories. For example, you want to create a section called "about". There are two types of pages you can create under the section "about".
+
+#### 1. The `_index.md`
+
+One is the `_index.md` which serves as the "section page", or the cushion page of the section. By default, the webpage specified by the subdirectory `/about` will direct you to the content of `content/about/_index.md`. See [Create a section]({{< ref "features/list/section_page" >}}) for instructions on how to create a section page.
+
+
+#### 2. Regular pages
+
+The other type is a regular page. You can name it in any way other than "_index.md", and you can create it by the Hugo command `hugo new`. (You may also create a section page using the `hugo new` command, but it will contain unnecessary front matter parameters by default).
+
+For example, if you create your `about` section page and enter `hugo new about/description.md`, the directory structure will become like:
+
+
+```
+content
+└ about
+ ├ _index.md
+ └ description.md
+```
+
+The regular pages can be customized by tweaking the [front matter variables]({{< ref "features/contents/front_matter" >}}).
diff --git a/example/content/features/contents/post_image.md b/example/content/features/contents/post_image.md
new file mode 100644
index 0000000000000000000000000000000000000000..3795179f0ae2a562fbbcef6bdf89b42cfbfed0fd
--- /dev/null
+++ b/example/content/features/contents/post_image.md
@@ -0,0 +1,20 @@
++++
+title = "Inserting images"
+date = 2020-03-09T14:06:22+09:00
+tags = [""]
+image = ""
+draft = false
+weight = "5"
+layout = "single"
+mktile = false
++++
+
+Images may be inserted into the page with the usual markdown notation:
+
+
+
+
+It is also possible to insert an image using the HTML `img` tag, which requires additional settings in the `config.toml` depending on the markdown parser used. Refer to the corresponding Hugo documentations for this issue.
+
+By default, the figure width is set to 40% of the main section. To override this, you must set the figure size manually using the `img` HTML tag.
+
diff --git a/example/content/features/contents/post_math.md b/example/content/features/contents/post_math.md
new file mode 100644
index 0000000000000000000000000000000000000000..743320adf434eeb81e5cc8a7bcb2c60e0f2b9451
--- /dev/null
+++ b/example/content/features/contents/post_math.md
@@ -0,0 +1,42 @@
++++
+title = "Inserting mathematical expressions"
+date = 2020-03-09T14:06:22+09:00
+tags = [""]
+image = ""
+draft = false
+weight = "6"
+layout = "single"
+mktile = false
++++
+
+
+
+
+By enabling `math` in the `config.toml`, you can include mathematical expressions powered by [$$\KaTeX$$](https://katex.org/) in your pages:
+
+```toml
+[Params]
+ ...
+ math = true
+ ...
+```
+
+This will be useful especially for pages with scientific contents.
+
+For example, by writing
+
+```
+$$
+-\frac{\hbar^2}{2m}\left(\nabla^2 + V(\boldsymbol{r}) \right)\phi(t,\boldsymbol{r}) = i\hbar \frac{\partial}{\partial t} \phi(t,\boldsymbol{r}),
+$$
+```
+
+it will be rendered as
+
+$$
+-\frac{\hbar^2}{2m}\left(\nabla^2 + V(\boldsymbol{r}) \right)\phi(t,\boldsymbol{r}) = i\hbar \frac{\partial}{\partial t} \phi(t,\boldsymbol{r}) .
+$$
+
+If you want to insert an equation inline, by writing `$E=mc^2$`, you get $E=mc^2$.
+
+
diff --git a/example/content/features/contents/tags_fm.md b/example/content/features/contents/tags_fm.md
new file mode 100644
index 0000000000000000000000000000000000000000..6aafb48b67ca767fbdd3334a922495ed0a94fed3
--- /dev/null
+++ b/example/content/features/contents/tags_fm.md
@@ -0,0 +1,27 @@
++++
+title = "Adding tags to your posts"
+date = 2020-03-09T14:06:22+09:00
+tags = [""]
+image = ""
+draft = false
+weight = "3"
+layout = "single"
+mktile = false
++++
+
+
+
+
+
+In the [front matter]({{< ref "features/contents/front_matter" >}}) of each post, you can set tags which can be used to categorize your pages. In the [postcard listing style]({{< ref "features/list/list_techs" >}}), the tags attached to each post will be placed on each card as colored buttons.
+
+The color for each tag button can be specified by hex color code in the `config.toml` as, for example,
+
+```toml
+[[Params.category_colors]]
+ Information = "#a22041"
+ News = "#2a83a2"
+ Event = "#316745"
+```
+.
+
diff --git a/example/content/features/list/_index.md b/example/content/features/list/_index.md
new file mode 100644
index 0000000000000000000000000000000000000000..7c429f7a583a29008bd91d7dbb5b5b054cdc3fae
--- /dev/null
+++ b/example/content/features/list/_index.md
@@ -0,0 +1,17 @@
++++
+title = "List layout"
+date = 2019-07-21T14:06:22+09:00
+tags = [""]
+image = "img/list1.jpg"
+draft = false
+weight = "2"
+layout = "single"
+mktile = true
++++
+
+The starting point for adding contents to your website is to create a `section`, or a menu content. After creating a section, you can start creating pages and subsections within the section. A `section page` serves as a cushion page to list the contents that belong to that section. This page, for example, is the section page for the `List layout` section.
+
+You can also add date-dependent contents such as conferences, seminars, festivals, etc. An independent page will be devoted to the description of this `post-type` contents, as it requires special treatment.
+
+{{< textlist >}}
+
diff --git a/example/content/features/list/list_techs.md b/example/content/features/list/list_techs.md
new file mode 100644
index 0000000000000000000000000000000000000000..736eb05fd72e7591490fd6a1f3eef4ffdec23f0e
--- /dev/null
+++ b/example/content/features/list/list_techs.md
@@ -0,0 +1,63 @@
++++
+title = "Listing techniques"
+date = 2020-03-09T14:06:22+09:00
+tags = [""]
+image = ""
+draft = false
+weight = "2"
+layout = "single"
+mktile = false
++++
+
+
+The [Section page]({{< ref "features/list/section_page" >}}) should include a list of links to the pages within the corresponding section. To realize this, we have prepared three methods of listing pages.
+
+
+# Three listing methods
+
+Each method of listing can be used by embedding the corresponding shortcode in the `_index.md` file. See the [official documentation](https://gohugo.io/content-management/shortcodes/) for a general description of shortcodes.
+
+
+## Text lists
+
+
+
+This is the most basic method, where the `title` of each page is listed in the order of their `weight`. This can be generated by embedding the shortcode
+
+```markdown
+{{* textlist */>}}
+```
+
+in the `_index.md`.
+
+
+## Tile lists
+
+
+
+
+
+By setting an image for each page, the link to the page could be arranged in a tile-like format consisting of the image and the title as a caption. This will be useful if you have characteristic images for each page. This can be generated by embedding the shortcode
+
+```markdown
+{{* tilelist */>}}
+```
+
+in the `_index.md`. Note that the image can be specified by adding the link to the image to the `image` variable in the [front matter]({{< ref "features/contents/front_matter" >}}) of each page (i.e. .md file).
+
+
+## Post lists
+
+
+
+
+
+This method displays each page in a card-like format with the date and short preview of the content. You can also set tags to the page by writing them explicitly on the [front matter]({{< ref "features/contents/front_matter" >}}). This method can be used similarly as the previous two by embedding the shortcode
+
+```markdown
+{{* postlist */>}}
+```
+
+in the `_index.md`, but is also intended to be used as [a method of displaying date-dependent contents]({{< ref "features/list/post_type_content" >}}). Note that the usage for the latter is a little different from the description given here.
+
+
diff --git a/example/content/features/list/post_type_content.md b/example/content/features/list/post_type_content.md
new file mode 100644
index 0000000000000000000000000000000000000000..1ea2f3129d041e23e37610c01ac2faa2e5681401
--- /dev/null
+++ b/example/content/features/list/post_type_content.md
@@ -0,0 +1,87 @@
++++
+title = "Posting date-dependent contents"
+date = 2020-03-09T14:06:22+09:00
+tags = [""]
+image = ""
+draft = false
+weight = "3"
+layout = "single"
+mktile = false
++++
+
+If you organize conferences, seminars, festivals, etc., you will most probably want to advertise them to the public. We have prepared a system to display such date-dependent contents.
+
+For instance, you may want to inform people about a weekly meeting. Showing the post about it on the top page will be most effective, but at the same time, it has to disappear as soon as it has ended. Also, you may want to check the page of a particular meeting that had been held years ago. Our method of posting date-dependent contents is realized by
+
+1. selecting future posts and several newest posts to show on the top page,
+
+and
+
+2. preparing a paginated list of all the past posts.
+
+
+## Creating a section devoted to date-dependent content
+
+This method requires special treatment compared to the [regular listing methods]({{< ref "features/list/list_techs" >}}), since by default, the content displayed in the accordion menu is identical to the content of the section page. For date-dependent contents, the section page may be a list of all the pages, but it will be too long to post in the accordion menu. Thus, we override the default structure, and make them as different pages.
+
+The first step is to create a section named `post`.
+
+**Currently, `post` is the only section name that could be used for this feature.**
+
+You should not create an `_index.md` in the section. Instead, set in the `config.toml`:
+
+```toml
+[[Languages.en.menu.main]]
+ name = "News"
+ url = "/post"
+ weight = 4
+ pre = "open"
+ post = "postcard"
+```
+
+You may customize the `name`, `weight`, `pre`, but note that the `url = "/post"` and `post = "postcard"` are requirements.
+
+
+## Customizing what to show in the accordion menu
+
+
+
+
+
+By setting the `eventEndDate` in the [front matter]({{< ref "/features/contents/front_matter" >}}) for each entry, the site will distinguish which event comes up in the future, and which has already ended.
+
+To make these show up in the accordion menu, create the page `/content/post/postcard.md` and write
+
+
+```markdown
+{{* upcoming_posts title="Upcoming Events" */>}}
+{{* newest_posts title="Newest Posts" number=3 */>}}
+[List of all posts]({{* ref "/post" */>}})
+```
+
+where you can customize
+
+* the labels "Upcoming Events", "Newest Posts", and "List of all posts"
+* the number of newest posts that will be displayed (3 in this example).
+
+In this case, The upcoming events will be posted under the heading "Upcoming Events", and three of the latest entries will be posted under the heading "3 Newest Posts". The comparison of `endEventDate` and the current date will be done upon each build, so by rebuilding Hugo everyday, the posts will be updated on a daily basis.
+
+If the arguments for the shortcodes are not given, the default setting of
+
+```markdown
+upcoming posts: title = "Upcoming"
+newest posts: title = "Newest Posts"
+number of newest posts: 3
+```
+
+will be chosen.
+
+You can also choose not to show the upcoming events, for example, by omitting the first line. For multilingual pages, create the same kind of page for each language.
+
+
+An example can be seen from the top page in the "Demonstration of the postcard style" section. Note that you can also place tags on each entry, which can be set in the [front matter]({{}}). The color settings of the tag buttons can be customized in the `config.toml`. See the ["Adding tags to your posts"]({{< ref "features/contents/tags_fm" >}}) page for details.
+
+The "List of all posts" link will direct you to the default `section` template of the `post` section, which displays all the pages in [postlist]({{< ref "features/list/list_techs" >}}) within the section in chronological order. You can see here that creating an `_index.md` file in the `post` section will override this action, and you will have to create the corresponding page by yourself.
+
+
+
diff --git a/example/content/features/list/section_page.md b/example/content/features/list/section_page.md
new file mode 100644
index 0000000000000000000000000000000000000000..f4fcead782c9e59dccca2261778ebdc020c2037d
--- /dev/null
+++ b/example/content/features/list/section_page.md
@@ -0,0 +1,56 @@
++++
+title = "Create a section"
+date = 2020-03-09T14:06:22+09:00
+tags = [""]
+image = ""
+draft = false
+weight = "1"
+layout = "single"
+mktile = false
++++
+
+In order to create a section, you need to create a corresponding menu entry and a directory under the `content` directory.
+
+## Creating a section
+
+Assuming that the home directory for the site is `/foo/bar`, a new menu entry can be created by adding
+
+```toml
+[[menu.main]]
+ identifier = "section_one"
+ name = "Section One"
+ url = "/section_one"
+ weight = 1
+ pre = "open"
+```
+
+to the `/foo/bar/config.toml` and creating a directory `section_one` under `/foo/bar/content/`. The meaning of each variable is as follows:
+
+* `identifier`: an ID that is used to identify each menu entry (corresponding to the section name)
+* `name`: the name of the menu entry that is displayed in each menu
+* `url`: the permanent link to the section page
+* `weight`: the sequencing index for the menu entry
+* `pre`: setting the corresponding accordion menu to be "open" or "closed" upon access (original variable for our theme)
+
+Refer to the [Hugo official documentation](https://gohugo.io/templates/menu-templates/#site-config-menus) for details on the parameters other than `pre`.
+
+The example above will create a section named `section_one`, displayed as `Section One`, and accessed via `/section_one`. On the top page, the corresponding accordion menu will be placed on the top, and will be open upon access by default.
+
+
+
+
+## Creating the section page
+
+A section page serves as a "cushion page", or a table of contents for the entries that belong to that section. It will typically contain an introduction to that section and a list of links to the pages within the section.
+
+The content of the section page can be written on the markdown file `/foo/bar/content/section_one/_index.md`. It is important that the file is named `_index.md`, so that it can be distinguished from the other regular pages. Upon build, Hugo will parse the markdown content to a static HTML file, which will be displayed as the section page. On the top page, the content of the section page will be displayed in the accordion menu.
+
+See [Lists in the section page]({{< ref "features/list/list_techs" >}}) to learn how to show a list of contents within the section. A description of writing regular entries will be given in the [Edit contents]({{< ref "features/contents" >}}) section.
+
+
+
+## Creating subsections
+
+You may also create a subsection `section_two` within the `section_one` by creating a corresponding subdirectory. It is not necessary to create a submenu entry in the `config.toml` for subsections.
+
+
diff --git a/example/content/greenwich.md b/example/content/greenwich.md
new file mode 100644
index 0000000000000000000000000000000000000000..509efea4e48697b1cc5e1631f120275f5bd8e9e2
--- /dev/null
+++ b/example/content/greenwich.md
@@ -0,0 +1,10 @@
++++
+title = "Royal Observatory Greenwich"
+googlemap_url = "https://www.google.com/maps/embed?pb=!1m18!1m12!1m3!1d4691.037791089049!2d-0.002803868719612036!3d51.4766855086724!2m3!1f0!2f0!3f0!3m2!1i1024!2i768!4f13.1!3m3!1m2!1s0x47d8a82a8ca9dca7%3A0x31abb25f451c8402!2sRoyal%20Observatory%20Greenwich!5e0!3m2!1sen!2sjp!4v1584327192393!5m2!1sen!2sjp"
++++
+
+Bussiness hours: 10:00 AM - 5:00 PM
+Address: Blackheath Ave, Greenwich, London SE10 8XJ, United Kingdom
+tel: XX-XXXX-XXXX
+e-mail: foo@bar.com
+
diff --git a/example/content/individual.md b/example/content/individual.md
new file mode 100644
index 0000000000000000000000000000000000000000..ec3a07cfedb0defd939ba9eb282bb340f2b6d949
--- /dev/null
+++ b/example/content/individual.md
@@ -0,0 +1,6 @@
++++
+title = "Hugo"
++++
+
+[Twitter](https://twitter.com/GoHugoIO)
+[GitHub](https://github.com/gohugoio/hugo)
diff --git a/example/content/link/index.md b/example/content/link/index.md
new file mode 100644
index 0000000000000000000000000000000000000000..39ae2dd584f1f5727b94db8941847cbcfb42a9f1
--- /dev/null
+++ b/example/content/link/index.md
@@ -0,0 +1,15 @@
++++
+title = "Links"
++++
+
+# Hugo Official
+
+[Web](https://gohugo.io/)
+[Twitter](https://twitter.com/GoHugoIO)
+[GitHub](https://github.com/gohugoio/hugo)
+
+# Our page
+
+[Demo page](https://www.cns.s.u-tokyo.ac.jp/white_cabinet)
+[Repository (GitLab)](https://gitlab.com)
+[Institute infomation](https://www.cns.s.u-tokyo.ac.jp/en)
diff --git a/example/content/post/post2.md b/example/content/post/post2.md
new file mode 100644
index 0000000000000000000000000000000000000000..b8ae729f6ef4dd601336fe8b7749baaaa6c81985
--- /dev/null
+++ b/example/content/post/post2.md
@@ -0,0 +1,29 @@
++++
+title = "Post2"
+date = 2019-10-11T15:32:38+09:00
+publishDate = 2019-10-11T15:32:38+09:00
+
+categories = ""
+##ex: categories = "event"##
+## for categ. event : remove "#" following 2 columns. ##
+#eventStartDate = 2019-12-11
+#eventEndDate = 2019-12-11
+
+tags = [""]
+##ex: tags = ["Seminar","Conference"]##
+
+image = ""
+
+###banner####
+mkbanner = true
+bannerEndDate = 2025-01-11
+bannerimg = "img/rabbit4.png"
+weight = 1
+
+#For main menu contents
+#mktile false
+
+#For Local
+draft = false
++++
+
diff --git a/example/content/post/post3.md b/example/content/post/post3.md
new file mode 100644
index 0000000000000000000000000000000000000000..6376d516d7029a31baa9e745a73cdc8d25b12576
--- /dev/null
+++ b/example/content/post/post3.md
@@ -0,0 +1,32 @@
++++
+title = "New service is available!"
+date = 2019-12-11T16:31:34+09:00
+publishDate = 2019-12-11T16:31:34+09:00
+
+categories = ""
+##ex: categories = "event"##
+## for categ. event : remove "#" following 2 columns. ##
+#eventStartDate = 2019-12-11
+#eventEndDate = 2019-12-11
+
+tags = ["News"]
+##ex: tags = ["Seminar","Conference"]##
+
+image = ""
+
+###banner####
+mkbanner = true
+bannerEndDate = 2025-01-11
+bannerimg = "img/landscape2.JPG"
+weight = 3
+
+#For main menu contents
+#mktile false
+
+#For Local
+draft = false
++++
+
+We will start the new service.
+
+
diff --git a/example/content/post/post4.md b/example/content/post/post4.md
new file mode 100644
index 0000000000000000000000000000000000000000..7a65c6d06cfac8c7242ada0a495327f10d01a6c0
--- /dev/null
+++ b/example/content/post/post4.md
@@ -0,0 +1,30 @@
++++
+title = "Closed infomation"
+date = 2019-12-01T16:34:34+09:00
+publishDate = 2019-12-01T16:34:34+09:00
+
+categories = ""
+##ex: categories = "event"##
+## for categ. event : remove "#" following 2 columns. ##
+#eventStartDate = 2019-12-11
+#eventEndDate = 2019-12-11
+
+tags = ["Information"]
+##ex: tags = ["Seminar","Conference"]##
+
+image = "/img/2.jpg"
+
+###banner####
+mkbanner = true
+bannerEndDate = 2025-02-25
+bannerimg = "/img/2.jpg"
+weight = 4
+
+#For main menu contents
+#mktile false
+
+#For Local
+draft = false
++++
+
+Our store will be closed on 25th Feburary, 2020 because of the maintenance.
diff --git a/example/content/post/post5.md b/example/content/post/post5.md
new file mode 100644
index 0000000000000000000000000000000000000000..df72c50384b714cb6b35fe7e337517821466438f
--- /dev/null
+++ b/example/content/post/post5.md
@@ -0,0 +1,31 @@
++++
+title = "Special Event"
+date = 2019-11-12T19:09:55+09:00
+publishDate = 2019-11-12T19:09:55+09:00
+
+categories = ""
+##ex: categories = "event"##
+## for categ. event : remove "#" following 2 columns. ##
+eventStartDate = 2020-03-01
+eventEndDate = 2020-03-31
+
+tags = ["Event"]
+##ex: tags = ["Seminar","Conference"]##
+
+#image = ""
+image = "img/landscape.JPG"
+
+###banner####
+mkbanner = true
+bannerEndDate = 2025-04-12
+#bannerimg = "img/landscape.JPG"
+weight = 200
+
+#For main menu contents
+#mktile false
+
+#For Local
+draft = false
++++
+
+Special event coming!
diff --git a/example/content/post/post6.md b/example/content/post/post6.md
new file mode 100644
index 0000000000000000000000000000000000000000..7fd61a66af57d07032d53e647e4ff1ea2a56674c
--- /dev/null
+++ b/example/content/post/post6.md
@@ -0,0 +1,30 @@
++++
+title = "Renewal page!"
+date = 2019-03-25T18:04:30+09:00
+publishDate = 2019-03-25T18:04:30+09:00
+
+categories = ""
+##ex: categories = "event"##
+## for categ. event : remove "#" following 2 columns. ##
+#eventStartDate = 2020-03-25
+#eventEndDate = 2020-03-25
+
+tags = ["Information","News"]
+##ex: tags = ["Seminar","Conference"]##
+
+image = ""
+
+###banner####
+mkbanner = false
+bannerEndDate = 2020-04-25
+bannerimg = ""
+weight = 300
+
+#For main menu contents
+#mktile false
+
+#For Local
+draft = false
++++
+
+Our home page is renewal
diff --git a/example/content/postcard.md b/example/content/postcard.md
new file mode 100644
index 0000000000000000000000000000000000000000..e26a59580251ccdcccc1a3a3290466a169e7708d
--- /dev/null
+++ b/example/content/postcard.md
@@ -0,0 +1,14 @@
++++
+title = "List of Posts"
+date = 2019-08-02T10:25:28+09:00
+tags = [""]
+image = "img/2.jpg"
+draft = false
+weight = ""
++++
+
+{{< upcoming_posts title="Upcoming Events" >}}
+
+{{< newest_posts title="Newest Posts" number=3 >}}
+
+[Posts]({{< ref "/post" >}})
diff --git a/example/content/sitemap.md b/example/content/sitemap.md
new file mode 100644
index 0000000000000000000000000000000000000000..09fe9ffa93d39671251b4085f21d7ca7d3c39138
--- /dev/null
+++ b/example/content/sitemap.md
@@ -0,0 +1,12 @@
++++
+title = "Sitemap"
+date = 2019-09-05T19:47:05+09:00
+publishDate = 2019-09-05T19:47:05+09:00
++++
+
+ - [About this theme]({{< ref "about/" >}})
+ - [Features]({{< ref "features/" >}})
+ - [Build your site]({{< ref "features/build/" >}})
+ - [List layout]({{< ref "features/list/" >}})
+ - [Edit contents]({{< ref "features/contents/" >}})
+
diff --git a/example/static/img/2.jpg b/example/static/img/2.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..bccaf8b0e3dbc288a0ed842657f680a74d3477c8
Binary files /dev/null and b/example/static/img/2.jpg differ
diff --git a/example/static/img/4.png b/example/static/img/4.png
new file mode 100644
index 0000000000000000000000000000000000000000..f2f4e35b3db6e4a4cb76f61554b00fbf9da14a4c
Binary files /dev/null and b/example/static/img/4.png differ
diff --git a/example/static/img/build1.jpg b/example/static/img/build1.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..6003649d826268d3af631f75c82ef27e3057b8ed
Binary files /dev/null and b/example/static/img/build1.jpg differ
diff --git a/example/static/img/edit1.jpg b/example/static/img/edit1.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..9ca5ce2f62e5c01e589b736748b7e6b25911ebe8
Binary files /dev/null and b/example/static/img/edit1.jpg differ
diff --git a/example/static/img/hugo_logo.png b/example/static/img/hugo_logo.png
new file mode 100644
index 0000000000000000000000000000000000000000..48acf346c9e87d15ca919141c2b283e7fa8bce4e
Binary files /dev/null and b/example/static/img/hugo_logo.png differ
diff --git a/example/static/img/landscape.JPG b/example/static/img/landscape.JPG
new file mode 100755
index 0000000000000000000000000000000000000000..47e361fa76eb870b8c8f9a643a097b61d957abff
Binary files /dev/null and b/example/static/img/landscape.JPG differ
diff --git a/example/static/img/landscape2.JPG b/example/static/img/landscape2.JPG
new file mode 100755
index 0000000000000000000000000000000000000000..94edca36c61c022763b0df663b2a87dcddc03f6f
Binary files /dev/null and b/example/static/img/landscape2.JPG differ
diff --git a/example/static/img/list1.jpg b/example/static/img/list1.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..9e7676dc05b7477b130ab0de134b1a3bf49dae12
Binary files /dev/null and b/example/static/img/list1.jpg differ
diff --git a/example/static/img/rabbit2.png b/example/static/img/rabbit2.png
new file mode 100644
index 0000000000000000000000000000000000000000..cfb1f9cfa9af3d824fb76e0993ae6c7865ff8614
Binary files /dev/null and b/example/static/img/rabbit2.png differ
diff --git a/example/static/img/rabbit4.png b/example/static/img/rabbit4.png
new file mode 100755
index 0000000000000000000000000000000000000000..453fafc281dadc30a8dfdca46dac6c1545c36cf3
Binary files /dev/null and b/example/static/img/rabbit4.png differ
diff --git a/example/static/img/screenshots/embmap1.png b/example/static/img/screenshots/embmap1.png
new file mode 100755
index 0000000000000000000000000000000000000000..b37d2592c97525c225d3c8f49710353d4ceb5ade
Binary files /dev/null and b/example/static/img/screenshots/embmap1.png differ
diff --git a/example/static/img/screenshots/embmap2.png b/example/static/img/screenshots/embmap2.png
new file mode 100755
index 0000000000000000000000000000000000000000..301fe1ca28e1aacfa734f148c5404f89789d8372
Binary files /dev/null and b/example/static/img/screenshots/embmap2.png differ
diff --git a/example/static/img/screenshots/fmbanner_fig.png b/example/static/img/screenshots/fmbanner_fig.png
new file mode 100644
index 0000000000000000000000000000000000000000..7a221ba8454e849b02d8e3110eaf59ceec0b3e38
Binary files /dev/null and b/example/static/img/screenshots/fmbanner_fig.png differ
diff --git a/example/static/img/screenshots/fmtags_fig.png b/example/static/img/screenshots/fmtags_fig.png
new file mode 100644
index 0000000000000000000000000000000000000000..b16e6ee237cbe97ba32ae270663634486c19c5bb
Binary files /dev/null and b/example/static/img/screenshots/fmtags_fig.png differ
diff --git a/example/static/img/screenshots/fmtitle_fig.png b/example/static/img/screenshots/fmtitle_fig.png
new file mode 100644
index 0000000000000000000000000000000000000000..44b4dff1e32b13d245464d866c34141ce270d12e
Binary files /dev/null and b/example/static/img/screenshots/fmtitle_fig.png differ
diff --git a/example/static/img/screenshots/footer_fig.png b/example/static/img/screenshots/footer_fig.png
new file mode 100644
index 0000000000000000000000000000000000000000..e2b8411dfc8933217c4ce8556455376737fdfe6a
Binary files /dev/null and b/example/static/img/screenshots/footer_fig.png differ
diff --git a/example/static/img/screenshots/infobar_fig.png b/example/static/img/screenshots/infobar_fig.png
new file mode 100644
index 0000000000000000000000000000000000000000..e31a0e89c134d0d0142529a4a8132b74b5dfd598
Binary files /dev/null and b/example/static/img/screenshots/infobar_fig.png differ
diff --git a/example/static/img/screenshots/links_fig.png b/example/static/img/screenshots/links_fig.png
new file mode 100644
index 0000000000000000000000000000000000000000..c0fcebc7f5b936378cd0d2a9fbd21e6b228baf2a
Binary files /dev/null and b/example/static/img/screenshots/links_fig.png differ
diff --git a/example/static/img/screenshots/mainmenu_fig.png b/example/static/img/screenshots/mainmenu_fig.png
new file mode 100644
index 0000000000000000000000000000000000000000..b2b3e0bfc6fd8c86622c9dfe8566bd186b55ec53
Binary files /dev/null and b/example/static/img/screenshots/mainmenu_fig.png differ
diff --git a/example/static/img/screenshots/post_fig.png b/example/static/img/screenshots/post_fig.png
new file mode 100644
index 0000000000000000000000000000000000000000..f7fd464eb2a8cfda5ad9bf33c9bd2c560a2df84b
Binary files /dev/null and b/example/static/img/screenshots/post_fig.png differ
diff --git a/example/static/img/screenshots/postlist_fig.png b/example/static/img/screenshots/postlist_fig.png
new file mode 100644
index 0000000000000000000000000000000000000000..12d72c686c83cfd22c77e283105d51c075e542c4
Binary files /dev/null and b/example/static/img/screenshots/postlist_fig.png differ
diff --git a/example/static/img/screenshots/textlist_fig.png b/example/static/img/screenshots/textlist_fig.png
new file mode 100644
index 0000000000000000000000000000000000000000..c8357744a69173bbc00da431e1cee02adcc69bb9
Binary files /dev/null and b/example/static/img/screenshots/textlist_fig.png differ
diff --git a/example/static/img/screenshots/tilelist_fig.png b/example/static/img/screenshots/tilelist_fig.png
new file mode 100644
index 0000000000000000000000000000000000000000..03fd54f33fe12d5c7b5f9698f1e2862c1213a3be
Binary files /dev/null and b/example/static/img/screenshots/tilelist_fig.png differ
diff --git a/example/static/img/screenshots/topfigures_headermenu_fig.png b/example/static/img/screenshots/topfigures_headermenu_fig.png
new file mode 100644
index 0000000000000000000000000000000000000000..5eee6d6a8f2577f3caed576c0db8a2696677db65
Binary files /dev/null and b/example/static/img/screenshots/topfigures_headermenu_fig.png differ
diff --git a/example/static/img/thumbnail.png b/example/static/img/thumbnail.png
new file mode 100755
index 0000000000000000000000000000000000000000..94793595ad7fb23c09cbaeba321b0126ee690d0d
Binary files /dev/null and b/example/static/img/thumbnail.png differ
diff --git a/example/static/img/topfigure1.jpg b/example/static/img/topfigure1.jpg
new file mode 100755
index 0000000000000000000000000000000000000000..55dd6c0b92c73cc1e273a8a135fef6d4209b8b1d
Binary files /dev/null and b/example/static/img/topfigure1.jpg differ
diff --git a/example/static/img/topfigure2.jpg b/example/static/img/topfigure2.jpg
new file mode 100755
index 0000000000000000000000000000000000000000..4ebf62ca418a450f0f5224ba8515de043f1e1ffa
Binary files /dev/null and b/example/static/img/topfigure2.jpg differ
diff --git a/example/static/img/topfigure3.jpg b/example/static/img/topfigure3.jpg
new file mode 100755
index 0000000000000000000000000000000000000000..0ff7dcb291b2cf32f2f9564c40d566a5ac7ca31b
Binary files /dev/null and b/example/static/img/topfigure3.jpg differ
diff --git a/example/static/img/topfigure4.jpg b/example/static/img/topfigure4.jpg
new file mode 100755
index 0000000000000000000000000000000000000000..4bc15a68191afcaf4aa38dbfc6e7ae7cb99a7ed0
Binary files /dev/null and b/example/static/img/topfigure4.jpg differ
diff --git a/example/static/img/topfigure5.jpg b/example/static/img/topfigure5.jpg
new file mode 100755
index 0000000000000000000000000000000000000000..af9ce73625bcd8865c65870735fa2b0bedfb4ce5
Binary files /dev/null and b/example/static/img/topfigure5.jpg differ
diff --git a/example/static/img/white_cabinet_components.png b/example/static/img/white_cabinet_components.png
new file mode 100755
index 0000000000000000000000000000000000000000..64e129daa46b599aba636e828bb9b2940d45a1a5
Binary files /dev/null and b/example/static/img/white_cabinet_components.png differ
diff --git a/example/themes b/example/themes
new file mode 120000
index 0000000000000000000000000000000000000000..6581736d62382ae8c6af9609548b31b112d5234c
--- /dev/null
+++ b/example/themes
@@ -0,0 +1 @@
+../../
\ No newline at end of file
diff --git a/layouts/_default/list.html b/layouts/_default/list.html
index 6355bbc38b8489a975ff22b37d397f63bee80cf4..8e62925b2a45658d2a220858fef48aceef7395b8 100644
--- a/layouts/_default/list.html
+++ b/layouts/_default/list.html
@@ -1,7 +1,6 @@
{{ define "main" }}
-
@@ -10,10 +9,10 @@
{{ partial "breadcrumb.html" . }}