diff --git a/source/_posts/en/Configuring-Theme.md b/source/_posts/en/Configuring-Theme.md
new file mode 100644
index 0000000..0d5fc25
--- /dev/null
+++ b/source/_posts/en/Configuring-Theme.md
@@ -0,0 +1,469 @@
+title: Icarus User Guide - Configuring the Theme
+date: 2020-03-01
+thumbnail: /gallery/thumbnails/vector_landscape_2.svg
+categories:
+- Configuration
+tags:
+- Getting Started
+- Icarus User Guide
+language: en
+toc: true
+---
+
+Icarus' default theme configuration file `_config.yml` resides in the `themes/icarus` directory.
+It defines the global layout and style settings of the theme as well as external features such as comment
+plugins and widgets.
+In this post, we will be covering settings that relate to the styling and overall layout of your site.
+We will be covering the mechanisms used by Icarus to configure your site and going through the format and meaning of some configuration
+settings.
+
+
+
+
+
+## Generate and Validate the Configuration
+
+An Icarus theme configuration file is written in [the `YAML` language](https://yaml.org/), and the default configuration file
+`themes/icarus/_config.yml` is generated automatically from a set of [JSON schemas](https://json-schema.org/) when the theme is processed by Hexo and you don't have
+a theme configuration file available at that time.
+That's why you don't see an example file (`_config.yml.example`) under your theme directory and there's no
+need to create `_config.yml` yourself.
+Most of the JSON schema definitions sit in the `themes/icarus/include/schema` directory and the others are
+in the [ppoffice/hexo-component-inferno](https://github.com/ppoffice/hexo-component-inferno) repository.
+You may attach the `--icarus-dont-generate-config` flag to your `hexo` commands to prevent configuration
+generation.
+
+The theme will also validate your configurations using these schemas every time you execute a `hexo` command
+in your site directory.
+If anything goes wrong during the validation, Icarus will print out the exact location of the misconfiguration
+and it's error type. For example, the following messages tell us that the value of `logo` setting should be
+either a string or an object, instead of an integer.
+You could ignore the warnings or append the `--icarus-dont-check-config` flag to your `hexo` commands to skip
+the validation, but it is not recommended to do so.
+
+{% codeblock "hexo log" %}
+INFO === Checking package dependencies ===
+INFO === Checking the configuration file ===
+WARN Configuration file failed one or more checks.
+WARN Icarus may still run, but you will encounter unexcepted results.
+WARN Here is some information for you to correct the configuration file.
+WARN [
+ {
+ keyword: 'type',
+ dataPath: '.logo',
+ schemaPath: '#/properties/logo/type',
+ params: { type: 'string,object' },
+ message: 'should be string,object'
+ }
+]
+{% endcodeblock %}
+
+Additionally, Icarus will try to use the migration scripts to upgrade your configuration to the newest version.
+These scripts are in the `themes/icarus/include/migration` directory.
+You may disable the upgrade by append the `--icarus-dont-upgrade-config` flag to your `hexo` commands.
+Finally, Icarus will also check the Node.js package dependencies and remind you to install them if you haven't.
+
+## Additional Configuration Files and Priority
+
+Apart from the default theme configuration file at `themes/icarus/_config.yml`, Icarus also look at configurations
+from the following sources:
+
+- `themes/icarus/_config.post.yml` and `themes/icarus/_config.page.yml`
+- Post/page's [front-matter](https://hexo.io/docs/front-matter.html)
+- Site `_config.yml` in the root directory
+
+`_config.post.yml` and `_config.page.yml` follows the same format and definitions of the default theme configuration
+file.
+You may put post-specific configurations in `_config.post.yml`, and these configurations will override the default
+theme configurations.
+For example, you can apply a two-column layout for all posts by moving all widgets to the left side of the page while keeping a three-column layout in other pages:
+
+{% codeblock themes/icarus/_config.yml lang:yaml %}
+widgets:
+ -
+ type: recent_posts
+ position: left
+ -
+ type: categories
+ position: right
+ -
+ type: tags
+ position: right
+{% endcodeblock %}
+
+{% codeblock themes/icarus/_config.post.yml lang:yaml %}
+widgets:
+ -
+ type: recent_posts
+ position: left
+ -
+ type: categories
+ position: left
+ -
+ type: tags
+ position: left
+{% endcodeblock %}
+
+Similarly, `_config.page.yml` overrides the default theme configurations and only applies to all Hexo pages.
+Additionally, if you wish to override theme configurations for a certain post/page, you can put them in the
+front-matter of that post/page.
+For example, if you can change the highlight.js theme of the code blocks by adding the setting in the post's
+front-matter like this:
+
+{% codeblock source/_post/some-post.md lang:yaml %}
+title: My first post
+date: '2015-01-01 00:00:01'
+article:
+ highlight:
+ theme: atom-one-dark
+---
+# Some Post
+{% endcodeblock %}
+
+The above setting in the front-matter will always override the same setting in the `_config.post.yml` and
+`_config.yml`.
+This feature can be very useful for displaying customized/optimized pages to a specific audience.
+For example, you can enable faster CDNs or a localized comment service based on the country and language of the
+page viewers.
+However, it should be noted that the post or page attributes defined by Hexo in the front-matter will not
+override the theme configuration files. Examples are:
+
+- `title`
+- `date`
+- `updated`
+- `comments` (not `comment`)
+- `layout`
+- `source`
+- `photos`
+- `excerpt`
+
+Finally, the site configuration file `_config.yml` in the root directory will be override by all other
+configuration files for the settings used by the theme.
+For instance, `title` in the `themes/icarus/_config.yml` will override `title` in the `_config.yml`, but
+`new_post_name` will not since it is not used by Icarus.
+
+In conclusion, the scopes of the configuration files and their priorities are
+
+
+
+
A certain post/page
+
+
+
+
+
front-matter overrides
+
themes/icarus/_config.post.yml or themes/icarus/_config.page.yml overrides
+
themes/icarus/_config.yml overrides
+
_config.yml
+
+
+
+
+
All posts/pages
+
+
+
+
+
themes/icarus/_config.post.yml or themes/icarus/_config.page.yml overrides
+
themes/icarus/_config.yml overrides
+
_config.yml
+
+
+
+
+
All HTML pages
+
+
+
+
+
themes/icarus/_config.yml overrides
+
_config.yml
+
+
+
+
+
+
+
+## Theme Configuration Walkthrough
+
+### Configuration version
+
+{% codeblock themes/icarus/_config.yml lang:yaml %}
+version: 3.0.0
+{% endcodeblock %}
+
+This version code is related to and but not always the same as the theme version code.
+It is used when Icarus upgrade the configuration file via migration scripts.
+You should not change it by yourself.
+
+### Theme variant
+
+{% codeblock themes/icarus/_config.yml lang:yaml %}
+variant: default
+{% endcodeblock %}
+
+Choose a skin for Icarus.
+"default" and "cyberpunk" are supported currently.
+You can take a look at the Cyberpunk variant {% post_link demo/Cyberpunk "here" %}.
+
+### Logo
+
+{% codeblock themes/icarus/_config.yml lang:yaml %}
+logo: /img/logo.svg
+{% endcodeblock %}
+
+Set the logo of your site which will display on the navigation bar and the footer.
+The value of the `logo` setting can either be a path/URL to your logo image, or it can be the following if
+you want text instead of an image as the logo
+
+{% codeblock themes/icarus/_config.yml lang:yaml %}
+logo:
+ text: My Beautiful Site
+{% endcodeblock %}
+
+### Favicon
+
+{% codeblock themes/icarus/_config.yml lang:yaml %}
+head:
+ favicon: /img/favicon.svg
+{% endcodeblock %}
+
+You may specify the path or URL to your site's favicon in the `head` section.
+
+### Open Graph
+
+{% codeblock themes/icarus/_config.yml lang:yaml >folded %}
+head:
+ open_graph:
+ # Page title (og:title) (optional)
+ # You should leave this blank for most of the time
+ title:
+ # Page type (og:type) (optional)
+ # You should leave this blank for most of the time
+ type: blog
+ # Page URL (og:url) (optional)
+ # You should leave this blank for most of the time
+ url:
+ # Page cover (og:image) (optional)
+ # You should leave this blank for most of the time
+ image:
+ # Site name (og:site_name) (optional)
+ # You should leave this blank for most of the time
+ site_name:
+ # Page author (article:author) (optional)
+ # You should leave this blank for most of the time
+ author:
+ # Page description (og:description) (optional)
+ # You should leave this blank for most of the time
+ description:
+ # Twitter card type (twitter:card)
+ twitter_card:
+ # Twitter ID (twitter:creator)
+ twitter_id:
+ # Twitter Site (twitter:site)
+ twitter_site:
+ # Google+ profile link (deprecated)
+ google_plus:
+ # Facebook admin ID
+ fb_admins:
+ # Facebook App ID
+ fb_app_id:
+{% endcodeblock %}
+
+You may set the Open Graph settings in the `head` section.
+You should leave some of the settings blank in the theme configuration file and only set those settings
+in the front-matter of your post when needed.
+Please refer to [Hexo documentation](https://hexo.io/docs/helpers.html#open-graph) for details of each setting.
+
+### Google Structured Data
+
+{% codeblock themes/icarus/_config.yml lang:yaml >folded %}
+head:
+ structured_data:
+ # Page title (optional)
+ # You should leave this blank for most of the time
+ title:
+ # Page description (optional)
+ # You should leave this blank for most of the time
+ description:
+ # Page URL (optional)
+ # You should leave this blank for most of the time
+ url:
+ # Page author (article:author) (optional)
+ # You should leave this blank for most of the time
+ author:
+ # Page images (optional)
+ # You should leave this blank for most of the time
+ image:
+{% endcodeblock %}
+
+You may set the Google Structured Data settings in the `head` section.
+You should leave most of the settings blank in the theme configuration file and only set those settings
+in the front-matter of your post when needed.
+Please refer to [Search for Developers](https://developers.google.com/search/docs/guides/intro-structured-data) for details of
+each setting.
+
+### Page Metadata
+
+{% codeblock themes/icarus/_config.yml lang:yaml %}
+head:
+ meta:
+ - 'name=theme-color;content=#123456'
+ - 'name=generator;content="Hexo 4.2.0"'
+{% endcodeblock %}
+
+You can add custom HTML `` tags to all pages in the `meta` setting of the `head` section.
+Each meta tag should appear as an item of the `meta` array.
+The fields of the tag should be in the `=` format and they are separated by `;`.
+
+### RSS
+
+{% codeblock themes/icarus/_config.yml lang:yaml %}
+head:
+ rss: /path/to/atom.xml
+{% endcodeblock %}
+
+You can add an RSS link in the page head via this setting.
+
+### Navigation Bar
+
+{% codeblock themes/icarus/_config.yml lang:yaml %}
+navbar:
+ # Naviagtion menu items
+ menu:
+ Home: /
+ Archives: /archives
+ Categories: /categories
+ Tags: /tags
+ About: /about
+ # Links to be shown on the right of the navigation bar
+ links:
+ GitHub: 'https://github.com'
+ Download on GitHub:
+ icon: fab fa-github
+ url: 'https://github.com/ppoffice/hexo-theme-icarus'
+{% endcodeblock %}
+
+The `navbar` section defines the links showing in the navigation bar.
+You may add arbitrary links to the navigation menu by adding `: ` to the `menu` setting.
+If you wish to add links on the right side of the navigation bar, please add `: ` to the `links` setting.
+You can even use a FontAwesome icon instead of pure text as link with the following format:
+
+{% codeblock "Link format" lang:yaml %}
+:
+ icon:
+ url:
+{% endcodeblock %}
+
+### Footer
+
+{% codeblock themes/icarus/_config.yml lang:yaml %}
+footer:
+ links:
+ Creative Commons:
+ icon: fab fa-creative-commons
+ url: 'https://creativecommons.org/'
+ Attribution 4.0 International:
+ icon: fab fa-creative-commons-by
+ url: 'https://creativecommons.org/licenses/by/4.0/'
+ Download on GitHub:
+ icon: fab fa-github
+ url: 'https://github.com/ppoffice/hexo-theme-icarus'
+{% endcodeblock %}
+
+You may add arbitrary links to the page footer in the `links` setting of the `footer` section.
+The format of the links is the same as `links` in the `navbar` section.
+
+### Code Highlight
+
+{% codeblock themes/icarus/_config.yml lang:yaml %}
+article:
+ highlight:
+ # Code highlight themes
+ # https://github.com/highlightjs/highlight.js/tree/master/src/styles
+ theme: atom-one-light
+ # Show copy code button
+ clipboard: true
+ # Default folding status of the code blocks. Can be "", "folded", "unfolded"
+ fold: unfolded
+{% endcodeblock %}
+
+If you have already enabled code highlighting in Hexo, you may customize the code blocks with `highlight` settings in the `article`
+section.
+You can choose a theme from all themes listed in [highlight.js/src/styles](https://github.com/highlightjs/highlight.js/tree/9.18.1/src/styles)
+and put the file name without the `.css` extension in the `theme` setting.
+You may also turn the "copy" button on or off by setting `clipboard` to `true` or `false`.
+Finally, if you wish to fold or unfold all code blocks, please set the `fold` setting to `folded` or `unfolded`.
+The folding feature can also be disabled if you leave the `fold` setting empty.
+Moreover, you can fold individual code blocks in the markdown file using the following syntax:
+
+
+```
+{% codeblock "optional file name" lang:code_language_name >folded %}
+...code block content...
+{% endcodeblock %}
+```
+
+### Thumbnail
+
+You can add thumbnail images to your posts in two steps.
+First, make sure the thumbnail is enabled in the theme's configuration file:
+
+{% codeblock themes/icarus/_config.yml lang:yaml %}
+article:
+ thumbnail: true
+{% endcodeblock %}
+
+Then, provide an URL or path to the image file in the front-matter of your post:
+
+{% codeblock post.md lang:yaml %}
+title: Getting Started with Icarus
+thumbnail: /gallery/thumbnails/desert.jpg
+---
+Post content...
+{% endcodeblock %}
+
+The image path you put in the front-matter needs to be the absolute path or URL to the image,
+or relative path to the source directory of your website.
+For example, if you want to use the `/source/gallery/image.jpg` as a thumbnail, you will need to put
+`/gallery/image.jpg` in the front-matter.
+
+### Read Time
+
+{% codeblock themes/icarus/_config.yml lang:yaml %}
+article:
+ readtime: true
+{% endcodeblock %}
+
+You can show the word counter and estimated time on top of your article by setting `readtime` to `true`
+in the `article` section.
+
+### Sidebar
+
+{% codeblock themes/icarus/_config.yml lang:yaml %}
+sidebar:
+ left:
+ sticky: false
+ right:
+ sticky: true
+{% endcodeblock %}
+
+Sometimes you may want your sidebar's position to stay fixed when your page scrolls.
+This can be done via the `sticky` settings in the `sidebar` section.
+
+
+## Other Configuration Settings
+
+Please refer to the [Icarus User Guide](/hexo-theme-icarus/tags/Icarus-User-Guide/) series if you are interested
+in configurating third-party plugins, widgets, and CDN providers of Icarus.
+
+
+
+Something wrong with this article? Click here to submit your revision.
+
+
+
+Vector Landscape Vectors by Vecteezy
diff --git a/source/_posts/FAQ.md b/source/_posts/en/FAQ.md
similarity index 58%
rename from source/_posts/FAQ.md
rename to source/_posts/en/FAQ.md
index bbd6226..5aaef90 100644
--- a/source/_posts/FAQ.md
+++ b/source/_posts/en/FAQ.md
@@ -1,6 +1,6 @@
title: FAQ
-date: 2018-10-19
-thumbnail: /gallery/thumbnails/sculpture.jpg
+date: 2020-02-01
+thumbnail: /gallery/thumbnails/vector_landscape_3.svg
---
### How do I put text instead of an image as my site's logo?
@@ -51,4 +51,4 @@ comments: false
Partially yes. Please refer to [Issues#234](https://github.com/ppoffice/hexo-theme-icarus/issues/234)
-Christopher Czermak
\ No newline at end of file
+Vector Landscape Vectors by Vecteezy
\ No newline at end of file
diff --git a/source/_posts/en/Getting-Started.md b/source/_posts/en/Getting-Started.md
index 8723250..5e9b4d0 100644
--- a/source/_posts/en/Getting-Started.md
+++ b/source/_posts/en/Getting-Started.md
@@ -1,12 +1,12 @@
title: Getting Started with Icarus
-date: 2020-01-01
-thumbnail: /gallery/thumbnails/desert.jpg
+date: 2020-04-01
+thumbnail: /gallery/thumbnails/vector_landscape_1.svg
tags:
- Getting Started
- Icarus User Guide
language: en
---
-A simple, delicate, and modern theme for the static site generator Hexo.
+Icarus is a simple, delicate, and modern theme for the static site generator Hexo.
It allows you to set up a single or multiple-column (up to three column) blog with its versatile layout configuration.
Additionally, it offers plentiful plugins and pluggable widgets so that you can enable the features you want in no time.
And with the all-new API designing, Icarus makes the development of this theme painless for developers and users.
@@ -61,4 +61,5 @@ Also, you can refer to the source code of this site for more examples by fetchin
Something wrong with this article? Click here to submit your revision.
-Chandler Chen
+
+Vector Landscape Vectors by Vecteezy
diff --git a/source/_posts/post/Adding-A-Thumbnail-to-Your-Article.md b/source/_posts/post/Adding-A-Thumbnail-to-Your-Article.md
deleted file mode 100644
index 3a9af55..0000000
--- a/source/_posts/post/Adding-A-Thumbnail-to-Your-Article.md
+++ /dev/null
@@ -1,39 +0,0 @@
-title: Adding a Thumbnail to Your Article
-date: 2018-10-18 00:00:01
-categories:
-- Configuration
-- Posts
-tags:
-- Getting Started
----
-You can add thumbnail images to your posts in two steps. First, make sure the thumbnail is enabled in the theme's configuration file:
-
-{% codeblock _config.yml lang:yaml %}
-article:
- thumbnail: true
-{% endcodeblock %}
-
-Then, provide an URL or path to the image file in the front-matter of your post:
-
-{% codeblock post.md lang:yaml %}
-title: Getting Started with Icarus
-thumbnail: /gallery/thumbnails/desert.jpg
----
-Post content...
-{% endcodeblock %}
-
-### About thumbnail image path
-
-The image path you put in the front-matter needs to be the relative path to the source directory of your website. For example, if you want to use the following image as a thumbnail:
-
-```
-/source/gallery/image.jpg
-```
-
-You need to use the following as the image path:
-
-```
-/gallery/image.jpg
-```
-
-Also, it is recommended that you put all the images under a dedicated asset folder that is separated from the `_posts` folder.
\ No newline at end of file
diff --git a/source/_posts/theme/Configuring-Icarus.md b/source/_posts/theme/Configuring-Icarus.md
deleted file mode 100644
index 7d9b264..0000000
--- a/source/_posts/theme/Configuring-Icarus.md
+++ /dev/null
@@ -1,45 +0,0 @@
-title: Configuring Icarus
-date: 2018-10-22 19:23:57
-thumbnail: /gallery/thumbnails/plant.jpg
-categories:
-- Configuration
-- Theme
-tags:
-- Getting Started
----
-
-The configuration of Icarus consists of two parts: theme configuration and post configuration.
-
-
-
-## Theme Configuration
-
-Icarus uses the _config.yml file for global page layout, plugins and widgets settings. It will check and validate the configuration file, points out any misconfigurations, and generates one for you if none exists. You can check the specifications at any time from the `*.spec.js` files inside the `themes/icarus/includes/specs` folder.
-
-A default theme configuration consists of the following parts:
-
-- Site preference and page meta data
-- Top navigation bar links
-- Page footer links
-- Article display settings
-- [Comment](/hexo-theme-icarus/categories/Plugins/Comment/), [share](/hexo-theme-icarus/categories/Plugins/Share/) and [search](/hexo-theme-icarus/categories/Plugins/Search/) plugin settings
-- [Sidebar widget](/hexo-theme-icarus/categories/Widgets/) settings
-- Other display and analytics [plugins](/hexo-theme-icarus/categories/Plugins/General/)
-- CDN settings
-
-Most of the settings are documented in the `_config.yml` file. For more details on configuring plugins, you can refer to the [online documentation](/hexo-theme-icarus/categories/).
-
-## Post Configuration
-
-Apart from the global theme configuration, you can also make customizations in any post. That is, you can override the theme configurations from a post. Let's say you want to show different navigation bar menus in a post. To do this, you only need to put the `navbar` settings in the post's front-matter:
-
-```yaml
-navbar:
- menu:
- Home: /
- Special!: /special
-```
-
-The configurations you set here will be applied only to this post. This feature can be very useful for displaying customized/optimized pages to a specific audience. For example, you can enable faster CDNs or a localized comment service based on the country and language of the page viewers.
-
-Alex Holt
\ No newline at end of file
diff --git a/source/_posts/theme/Polymorphic-Link-Settings.md b/source/_posts/theme/Polymorphic-Link-Settings.md
deleted file mode 100644
index 23c3d1d..0000000
--- a/source/_posts/theme/Polymorphic-Link-Settings.md
+++ /dev/null
@@ -1,41 +0,0 @@
-title: Polymorphic Link Settings
-slug: Polymorphic-Link-Settings
-date: 2018-10-22 19:23:57
-thumbnail: /gallery/thumbnails/flower.jpg
-categories:
-- Configuration
-- Theme
-footer:
- links:
- Creative Commons: 'https://creativecommons.org/'
- Attribution 4.0 International: 'https://creativecommons.org/licenses/by/4.0/'
- Download on GitHub:
- icon: fab fa-github
- url: 'http://github.com/ppoffice/hexo-theme-icarus'
----
-
-You may already notice that Icarus allows you to put icon links on the right of the navigation bar, the bottom of the profile widget, and the right side of the footer with the following format:
-
-
-
-```yml
-footer:
- links:
- 'Creative Commons':
- icon: fab fa-creative-commons
- url: 'https://creativecommons.org/'
- 'Attribution 4.0 International':
- icon: fab fa-creative-commons-by
- url: 'https://creativecommons.org/licenses/by/4.0/'
-```
-
-In the above link format, you need to specify the name of the link (e.g., Creative Commons), as well as the icon class name (e.g., Font Awesome class name) and link URL. However, Icarus also accept pure text links with a link name and URL in the format below:
-
-```yml
-footer:
- links:
- 'Creative Commons': 'https://creativecommons.org/'
- 'Attribution 4.0 International': 'https://creativecommons.org/licenses/by/4.0/'
-```
-
-Evie Shaffer
diff --git a/source/_posts/theme/Sticky-Sidebar.md b/source/_posts/theme/Sticky-Sidebar.md
deleted file mode 100644
index ee6c3af..0000000
--- a/source/_posts/theme/Sticky-Sidebar.md
+++ /dev/null
@@ -1,67 +0,0 @@
-title: Make a Sidebar Sticky When Page Scrolls
-date: 2018-10-16 00:00:00
-categories:
-- Configuration
-- Theme
-sidebar:
- right:
- sticky: true
-widgets:
- -
- type: profile
- position: right
- author: PPOffice
- author_title: Web Developer
- location: Earth, Solar System
- avatar:
- gravatar:
- follow_link: 'http://github.com/ppoffice'
- social_links:
- Github:
- icon: fab fa-github
- url: 'http://github.com/ppoffice'
- Facebook:
- icon: fab fa-facebook
- url: 'http://facebook.com'
- Twitter:
- icon: fab fa-twitter
- url: 'http://twitter.com'
- Dribbble:
- icon: fab fa-dribbble
- url: 'http://dribbble.com'
- RSS:
- icon: fas fa-rss
- url: /
- -
- type: links
- position: right
- links:
- Hexo: 'https://hexo.io'
- Bulma: 'https://bulma.io'
- -
- type: recent_posts
- position: left
- -
- type: archives
- position: left
- -
- type: categories
- position: left
- -
- type: tags
- position: left
----
-Sometimes you may want your sidebar's position to stay fixed when other parts of your page scrolls. This can be done via the `sticky` option of the sidebar in the theme's `_config.yml`. You can set any of the sidebar or even both of them to `sticky`.
-
-```yaml
-sidebar:
- left:
- sticky: false
- right:
- sticky: true
-```
-
-
-
-
This is some really long content.
-
\ No newline at end of file
diff --git a/source/_posts/zh-CN/Configuring-Theme.md b/source/_posts/zh-CN/Configuring-Theme.md
new file mode 100644
index 0000000..8392ffb
--- /dev/null
+++ b/source/_posts/zh-CN/Configuring-Theme.md
@@ -0,0 +1,444 @@
+title: Icarus用户指南 - 主题配置
+date: 2016-01-03
+categories:
+- Configuration
+tags:
+- Getting Started
+- Icarus用户指南
+language: zh-CN
+toc: true
+providers:
+ cdn: loli
+ fontcdn: loli
+ iconcdn: loli
+---
+
+