+
+[NexT](https://theme-next.org) is an elegant and powerful theme for [Hexo](https://hexo.io/). With it, you can build a static blog hosted on [GitHub Pages](https://pages.github.com/) to share your life and communicate with new friends.
+
+A CODE_OF_CONDUCT dictates how conversation during code updates, issue communication, and pull requests should happen within [NexT](https://github.com/theme-next/hexo-theme-next) repository. We expect all users to show respect and courtesy to others through our repositories. Anyone violating these rules will not be reviewed and will be blocked and expelled from our repositories immediately upon discovery.
+
+## Table Of Contents
+
+- [Our Pledge](#our-pledge)
+- [Our Responsibilities](#our-responsibilities)
+- [Our Standards](#our-standards)
+- [Scope](#scope)
+- [Enforcement](#enforcement)
+- [Contacting Maintainers](#contacting-maintainers)
+- [Attribution](#attribution)
+
+## Our Pledge
+
+As contributors and maintainers of this project, we pledge to respect all people who contribute through reporting issues, posting feature requests, updating documentation, submitting pull requests or patches, and other activities.
+
+In the interest of fostering an open and welcoming environment, we are committed to making participation in our community a harassment-free experience for everyone, regardless of level of experience, gender, gender identity and expression, sexual identity and orientation, disability, personal appearance, body size, race, ethnicity, age, religion, or nationality.
+
+## Our Responsibilities
+
+Project maintainers have the right and responsibility to clarify the standards of acceptable behavior and are expected to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, or to block temporarily or permanently any contributor for other behaviors that they deem inappropriate, threatening, offensive, or harmful.
+
+## Our Standards
+
+As a project on GitHub, this project is overed by the [GitHub Community Guidelines](https://help.github.com/articles/github-community-guidelines/). Additionally, as a project hosted on npm, it is covered by [npm Inc's Code of Conduct](https://www.npmjs.com/policies/conduct).
+
+Examples of behavior that contributes to creating a positive environment include:
+
+* Using welcoming and inclusive language.
+* Being respectful of differing viewpoints and experiences.
+* Gracefully accepting constructive feedback.
+* Focusing on what is best for the community.
+* Showing empathy and kindness towards other community members.
+
+Examples of unacceptable behavior by participants include:
+
+* The use of sexualized language or imagery and unwelcome sexual attention or advances
+* Trolling, insulting/derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others’ private information, such as a physical or electronic address, without explicit permission
+* Other conduct which could reasonably be considered inappropriate in a professional setting
+
+## Scope
+
+This Code of Conduct applies both within project spaces and in public spaces when an individual is representing the project or its community.
+
+Depending on the violation, the maintainers may decide that violations of this code of conduct that have happened outside of the scope of the community may deem an individual unwelcome, and take appropriate action to maintain the comfort and safety of its members.
+
+## Enforcement
+
+If you see a Code of Conduct violation, follow these steps:
+
+1. Let the person know that what they did is not appropriate and ask them to stop and/or edit their message(s) or commits. That person should immediately stop the behavior and correct the issue.
+2. If this doesn’t happen, or if you're uncomfortable speaking up, [contact the maintainers](#contacting-maintainers). When reporting, please include any relevant details, links, screenshots, context, or other information that may be used to better understand and resolve the situation.
+3. As soon as available, a maintainer will look into the issue, and take further action.
+
+Once the maintainers get involved, they will follow a documented series of steps and do their best to preserve the well-being of project members.
+
+All complaints will be reviewed and investigated and will result in a response that is deemed necessary and appropriate to the circumstances. The project team is obligated to maintain confidentiality with regard to the reporter of an incident. Further details of specific enforcement policies may be posted separately.
+
+Thesehese are the steps maintainers will take for further enforcement, as needed:
+
+1. Repeat the request to stop.
+2. If the person doubles down, they will have offending messages removed or edited by a maintainers given an official warning. The PR or Issue may be locked.
+3. If the behavior continues or is repeated later, the person will be blocked from participating for 24 hours.
+4. If the behavior continues or is repeated after the temporary block, a long-term (6-12 months) ban will be used.
+
+On top of this, maintainers may remove any offending messages, images, contributions, etc, as they deem necessary. Maintainers reserve full rights to skip any of these steps, at their discretion, if the violation is considered to be a serious and/or immediate threat to the well-being of members of the community. These include any threats, serious physical or verbal attacks, and other such behavior that would be completely unacceptable in any social setting that puts our members at risk.
+
+Project maintainers who do not follow or enforce the Code of Conduct in good faith may face temporary or permanent repercussions as determined by other members of the project's leadership.
+
+## Contacting Maintainers
+
+You may get in touch with the maintainer team through any of the following methods:
+
+* Through Email:
+ * [support@theme-next.org](mailto:support@theme-next.org)
+
+* Through Chat:
+ * [Gitter](https://gitter.im/theme-next)
+ * [Riot](https://riot.im/app/#/room/#NexT:matrix.org)
+ * [Telegram](https://t.me/joinchat/GUNHXA-vZkgSMuimL1VmMw)
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant](https://www.contributor-covenant.org/) and [WeAllJS Code of Conduct](https://wealljs.org/code-of-conduct).
diff --git a/themes/next/.github/CONTRIBUTING.md b/themes/next/.github/CONTRIBUTING.md
new file mode 100644
index 0000000..e3d895c
--- /dev/null
+++ b/themes/next/.github/CONTRIBUTING.md
@@ -0,0 +1,197 @@
+
+
+First of all, thanks for taking your time to contribute and help make our project even better than it is today! The following is a set of guidelines for contributing to [Theme-Next](https://github.com/theme-next) and its libs submodules. These are mostly guidelines, not rules. Use your best judgment, and feel free to propose changes to this document in a pull request.
+
+## Table Of Contents
+
+[How Can I Contribute?](#how-can-i-contribute)
+
+ * [Before Submitting An Issue](#before-submitting-an-issue)
+ * [Read the docs](#read-the-docs)
+ * [Quick debug instructions](quick-debug-instructions)
+ * [Reporting Bugs](#reporting-bugs)
+ * [Reporting Security Bugs](#reporting-security-bugs)
+ * [Suggesting Enhancements](#suggesting-enhancements)
+ * [Submitting a Pull Request](#submitting-a-pull-request)
+ * [Creating Releases](#creating-releases)
+
+[Guides](#guides)
+
+ * [Coding Rules](#coding-rules)
+ * [Coding Standards](#coding-standards)
+ * [Labels Rules](#labels-rules)
+ * [Commit Messages Rules](#commit-messages-rules)
+
+## How Can I Contribute?
+
+### Before Submitting An Issue
+
+#### Read the docs
+
+If you just have a question, you'll get faster results by checking the [FAQs for a list of common questions and problems](https://theme-next.org/docs/faqs) or the [troubleshooting part of «NexT» Documentation Site](https://theme-next.org/docs/troubleshooting).
+
+Also, you can perform a [cursory search](https://github.com/theme-next/hexo-theme-next/search?q=&type=Issues&utf8=%E2%9C%93) to see if the problem has already been reported or solved. You don't want to duplicate effort. You might be able to find the cause of the problem and fix things yourself, or add comments to the existed issue.
+
+#### Quick debug instructions
+
+Before submitting an Issue on GitHub, you can follow the steps below to debug:
+
+* Execute `hexo clean`, clear the browser cache and disable all CDN services (e.g. Cloudflare Rocket Loader)
+* Switch to another theme and check if the bug still exists (e.g. default theme landscape). In other words, prove that this is a NexT issue, not a issue from Hexo.
+* Upgrade theme NexT to the latest version.
+* Upgrade Hexo and Hexo plugins to the latest version.
+* Upgrade Node.js and `npm` to the latest version.
+* Uninstall all non-essential Hexo plugins, or reinstall all plugins using `npm install --save`.
+
+If you get an error message from Hexo or your browser, please search in Google / Stackoverflow / GitHub Issues, or report it to us when submitting a new Issue.
+
+If you find a bug in the source code, most importantly, please check carefully if you can reproduce the problem [in the latest release version of Next](https://github.com/theme-next/hexo-theme-next/releases/latest). Then, you can help us by [Reporting Bugs](#reporting-bugs) or [Suggesting Enhancements](#suggesting-enhancements) to our [Repository](https://github.com/theme-next/hexo-theme-next). Even better, you can [submit a Pull Request](#submitting-a-pull-request) with a fix.
+
+### Reporting Bugs
+
+Before creating bug reports, please check [this list](#before-submitting-an-issue) as you might find out that you don't need to create one. After you've determined the repository your bug is related to, create an issue on that repository and provide the information as many details as possible by filling in [the required template](ISSUE_TEMPLATE.md).
+
+Following these guidelines helps maintainers and the community understand your report :pencil:, reproduce the behavior, and find related reports:
+
+* Use a clear and descriptive title for the issue to identify the problem.
+* Provide more context by answering these questions:
+ * Can you reproduce the problem? Can you reliably reproduce the issue? If not, provide details about how often the problem happens and under which conditions it normally happens.
+ * Did the problem start happening recently or was this always a problem?
+ * If the problem started happening recently, can you reproduce the problem in an older version of Next? What's the most recent version in which the problem doesn't happen? You can download older versions of Next from [the releases page](https://github.com/theme-next/hexo-theme-next/releases).
+ * Which version of Node, Hexo and Next are you using? You can get the exact version by running `node -v`, `hexo version` in your terminal, or copy the contents in site's`package.json`.
+ * Which packages do you have installed? You can get that list by copying the contents in site's`package.json`.
+* Describe the exact steps which reproduce the problem in as many details as possible. When listing steps, don't just say what you did, but explain how you did it, e.g. which command exactly you used. If you're providing snippets in the issue, use [Markdown code blocks](https://help.github.com/articles/creating-and-highlighting-code-blocks/) or [a permanent link to a code snippet](https://help.github.com/articles/creating-a-permanent-link-to-a-code-snippet/), or a [Gist link](https://gist.github.com/).
+* Provide specific examples to demonstrate the steps. Include links to files (screenshots or GIFs) or live demo.
+* Describe the behavior you observed after following the steps and point out what exactly is the problem with that behavior.
+* Explain which behavior you expected to see instead and why.
+
+#### Reporting Security Bugs
+
+If you find a security issue, please act responsibly and report it not in the public issue tracker, but directly to us, so we can fix it before it can be exploited. Please send the related information to security@theme-next.com (desirable with using PGP for e-mail encryption).
+
+We will gladly special thanks to anyone who reports a vulnerability so that we can fix it. If you want to remain anonymous or pseudonymous instead, please let us know that; we will gladly respect your wishes.
+
+### Suggesting Enhancements
+
+Before creating enhancement suggestions, please check [this list](#before-submitting-an-issue) as you might find out that you don't need to create one. After you've determined the repository your enhancement suggestion is related to, create an issue on that repository and provide the information as many details as possible by filling in [the required template](ISSUE_TEMPLATE.md).
+
+Following these guidelines helps maintainers and the community understand your suggestion :pencil: and find related suggestions.
+
+* Use a clear and descriptive title for the issue to identify the suggestion.
+* Describe the current behavior and explain which behavior you expected to see instead and Explain why this enhancement would be useful to most users.
+* Provide specific examples to demonstrate the suggestion. Include links to files (screenshots or GIFs) or live demo.
+
+### Submitting a Pull Request
+
+Before creating a Pull Request (PR), please check [this list](#before-submitting-an-issue) as you might find out that you don't need to create one. After you've determined the repository your pull request is related to, create a pull request on that repository. The detailed document of creating a pull request can be found [here](https://help.github.com/articles/creating-a-pull-request/).
+
+Following these guidelines helps maintainers and the community understand your pull request :pencil::
+
+* Follow our [Coding Rules](#coding-rules) and [commit message conventions](#commit-messages-rules).
+* Use a clear and descriptive title for the issue to identify the pull request. Do not include issue numbers in the PR title.
+* Fill in [the required template](PULL_REQUEST_TEMPLATE.md) as many details as possible.
+* All features or bug fixes must be tested in all schemes. And provide specific examples to demonstrate the pull request. Include links to files (screenshots or GIFs) or live demo.
+
+### Creating Releases
+
+Releases are a great way to ship projects on GitHub to your users.
+
+1. On GitHub, navigate to the main page of the repository. Under your repository name, click **Releases**. Click **Draft a new release**.
+2. Type a version number for your release. Versions are based on [Git tags](https://git-scm.com/book/en/Git-Basics-Tagging). We recommend naming tags that fit within [About Major and Minor NexT versions](https://github.com/theme-next/hexo-theme-next/issues/187).
+3. Select a branch that contains the project you want to release. Usually, you'll want to release against your `master` branch, unless you're releasing beta software.
+4. Type a title and description that describes your release.
+ - Use the version as the title.
+ - The types of changes include **Breaking Changes**, **Updates**, **Features**, and **Bug Fixes**. In the section of Breaking Changes, use multiple secondary headings, and use item list in other sections.
+ - Use the passive tense and subject-less sentences.
+ - All changes must be documented in release notes. If commits happen without pull request (minimal changes), just add this commit ID into release notes. If commits happen within pull request alreay, just add the related pull request ID including all possible commits.
+5. If you'd like to include binary files along with your release, such as compiled programs, drag and drop or select files manually in the binaries box.
+6. If the release is unstable, select **This is a pre-release** to notify users that it's not ready for production. If you're ready to publicize your release, click **Publish release**. Otherwise, click **Save draft** to work on it later.
+
+## Guides
+
+### Coding Rules
+
+This project and everyone participating in it is governed by the [Code of Conduct](CODE_OF_CONDUCT.md) to keep open and inclusive. By participating, you are expected to uphold this code.
+
+### Coding Standards
+
+We use ESLint and Stylint for identifying and reporting on patterns in JavaScript and Stylus, with the goal of making code more consistent and avoiding bugs. These specifications should be followed when coding.
+
+### Labels Rules
+
+We use "labels" in the issue tracker to help classify Pull requests and Issues. Using labels enables maintainers and users to quickly find issues they should look into, either because they experience them, or because it meets their area of expertise.
+
+If you are unsure what a label is about or which labels you should apply to a PR or issue, look no further!
+
+Issues related:
+
+- By types
+ - `Bug`: A detected bug that needs to be confirmed
+ - `Feature Request`: An issue that wants a new feature
+ - `Question`: An issue about questions
+ - `Meta`: Denoting a change of usage conditions
+ - `Support`: An issue labeled as support requests
+ - `Polls`: An issue that initiated a poll
+- By results
+ - `Duplicate`: An issue which had been mentioned
+ - `Irrelevant`: An irrelevant issue for Next
+ - `Invalid`: An issue that cannot be reproduced
+ - `Expected Behavior`: An issue that corresponds to expected behavior
+ - `Need More Info`: Need more information for solving the issue
+ - `Verified`: An issue that has been verified
+ - `Solved`: An issue that has been solved
+ - `Backlog`: An issue that is to be completed and later compensated
+ - `Stale`: This issue has been automatically marked as stale because lack of recent activity
+
+Pull requests related:
+
+- `Breaking Change`: A pull request that makes breaking change
+- `Bug Fix`: A pull request that fixes the related bug
+- `New Feature`: A pull request that provides a new feature
+- `Feature`: A pull request that provides an option or addition to existing feature
+- `i18n`: A pull request that makes new languages translation
+- `Work in Progress`: A pull request that is still working in progress
+- `Skip Release`: A pull request that should be excluded from release note
+
+Both:
+
+- `Roadmap`: An issue / pull request about future development
+- `Help Wanted`: An issue / pull request that needs help
+- `Discussion`: An issue / pull request that needs to be discussed
+- `Improvement`: An issue that needs improvement or a pull request that improves NexT
+- `Performance`: An issue / pull request that improves the performance
+- `Hexo`: An issue / pull request related to Hexo or Hexo plugins
+- `Template Engine`: An issue / pull request related to template engine
+- `CSS`: An issue / pull request related to CSS
+- `Fonts`: An issue / pull request related to fonts
+- `PJAX`: An issue / pull request related to PJAX
+- `3rd Party Plugin`: An issue / pull request related to 3rd party plugins & service
+- `Docs`: An issue / pull request related to instruction document
+- `Configurations`: An issue / pull request related to configurations
+
+### Commit Messages Rules
+
+We have very precise rules over how our git commit messages can be formatted. Each commit message consists of a `type` and a `subject`. This leads to more
+readable messages that are easy to follow when looking through the project history.
+
+- `type` describes the meaning of this commit including but not limited to the following items, and capitalize the first letter.
+ * `Build`: Changes that affect the build system or external dependencies
+ * `Ci`: Changes to our CI configuration files and scripts
+ * `Docs`: Documentation only changes
+ * `Feat`: A new feature
+ * `Fix`: A bug fix
+ * `Perf`: A code change that improves performance
+ * `Refactor`: A code change that neither fixes a bug nor adds a feature
+ * `Style`: Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc)
+ * `Revert`: Revert some existing commits
+ * `Release`: Commit a release for a conventional changelog project
+- The `subject` contains a succinct description of the change, like `Update code highlighting in readme.md`.
+ * No dot (.) at the end.
+ * Use the imperative, present tense: "change" not "changed" nor "changes".
diff --git a/themes/next/.github/ISSUE_TEMPLATE/bug-report.md b/themes/next/.github/ISSUE_TEMPLATE/bug-report.md
new file mode 100644
index 0000000..45be404
--- /dev/null
+++ b/themes/next/.github/ISSUE_TEMPLATE/bug-report.md
@@ -0,0 +1,64 @@
+---
+name: Bug Report
+about: Something isn't working as expected
+title: ''
+labels: Bug
+assignees: ''
+
+---
+
+Please follow this Issue template to provide relevant information, such as source code repositories, blog links, and screenshots, which will help us investigate.
+请按照此 Issue 模版提供相关信息，例如源码仓库、博客链接和屏幕截图，这将有助于我们进行调查。
+
+## Issue Checklist
+
+
+- [ ] I am using [the latest](https://github.com/theme-next/hexo-theme-next/releases/latest) version of NexT.
+- [ ] I have read the relevant documents of [Hexo](https://hexo.io/docs/) and [NexT](https://theme-next.org/docs/).
+- [ ] I have reviewed the latest Roadmap on GitHub and searched for current [issues](https://github.com/theme-next/hexo-theme-next/issues), which does not help me.
+
+***
+
+## Expected behavior
+
+
+## Actual behavior
+
+
+- Links to demo site with this issue: N/A
+- Links to repository or source code of the blog: N/A
+
+
+## Steps to reproduce the behavior
+1. N/A
+2. N/A
+3. N/A
+
+
+## Environment Information
+
+### Node.js and NPM Information
+
+```
+
+```
+
+### Package dependencies Information
+
+```
+
+```
+
+### Hexo Configuration
+
+```yml
+
+```
+
+### NexT Configuration
+
+```yml
+
+```
+
+## Other Information
diff --git a/themes/next/.github/ISSUE_TEMPLATE/feature-request.md b/themes/next/.github/ISSUE_TEMPLATE/feature-request.md
new file mode 100644
index 0000000..23713cf
--- /dev/null
+++ b/themes/next/.github/ISSUE_TEMPLATE/feature-request.md
@@ -0,0 +1,37 @@
+---
+name: Feature Request
+about: Suggest an idea for this project
+title: ''
+labels: Feature Request
+assignees: ''
+
+---
+
+Please follow this Issue template to provide relevant information, such as source code repositories, blog links, and screenshots, which will help us investigate.
+请按照此 Issue 模版提供相关信息，例如源码仓库、博客链接和屏幕截图，这将有助于我们进行调查。
+
+## Issue Checklist
+
+
+- [ ] I am using [the latest](https://github.com/theme-next/hexo-theme-next/releases/latest) version of NexT.
+- [ ] I have read the relevant documents of [Hexo](https://hexo.io/docs/) and [NexT](https://theme-next.org/docs/).
+- [ ] I have reviewed the latest Roadmap on GitHub and searched for current [issues](https://github.com/theme-next/hexo-theme-next/issues), which does not help me.
+
+***
+
+## Expected behavior
+
+
+## Actual behavior
+
+
+- Links to demo site with this feature: N/A
+- Links to repository or source code of the blog: N/A
+
+
+## Steps to reproduce the behavior
+1. N/A
+2. N/A
+3. N/A
+
+## Other Information
diff --git a/themes/next/.github/ISSUE_TEMPLATE/other.md b/themes/next/.github/ISSUE_TEMPLATE/other.md
new file mode 100644
index 0000000..81a5ed4
--- /dev/null
+++ b/themes/next/.github/ISSUE_TEMPLATE/other.md
@@ -0,0 +1,22 @@
+---
+name: Other
+about: Not a question, feature request or bug report
+title: ''
+labels: ''
+assignees: ''
+
+---
+
+Please follow this Issue template to provide relevant information, such as source code repositories, blog links, and screenshots, which will help us investigate.
+请按照此 Issue 模版提供相关信息，例如源码仓库、博客链接和屏幕截图，这将有助于我们进行调查。
+
+## Issue Checklist
+
+
+- [ ] I am using [the latest](https://github.com/theme-next/hexo-theme-next/releases/latest) version of NexT.
+- [ ] I have read the relevant documents of [Hexo](https://hexo.io/docs/) and [NexT](https://theme-next.org/docs/).
+- [ ] I have reviewed the latest Roadmap on GitHub and searched for current [issues](https://github.com/theme-next/hexo-theme-next/issues), which does not help me.
+
+***
+
+## Other Information
diff --git a/themes/next/.github/ISSUE_TEMPLATE/question.md b/themes/next/.github/ISSUE_TEMPLATE/question.md
new file mode 100644
index 0000000..aaf0f09
--- /dev/null
+++ b/themes/next/.github/ISSUE_TEMPLATE/question.md
@@ -0,0 +1,64 @@
+---
+name: Question
+about: I have a question for NexT (e.g. Customize)
+title: ''
+labels: Custom
+assignees: ''
+
+---
+
+Please follow this Issue template to provide relevant information, such as source code repositories, blog links, and screenshots, which will help us investigate.
+请按照此 Issue 模版提供相关信息，例如源码仓库、博客链接和屏幕截图，这将有助于我们进行调查。
+
+## Issue Checklist
+
+
+- [ ] I am using [the latest](https://github.com/theme-next/hexo-theme-next/releases/latest) version of NexT.
+- [ ] I have read the relevant documents of [Hexo](https://hexo.io/docs/) and [NexT](https://theme-next.org/docs/).
+- [ ] I have reviewed the latest Roadmap on GitHub and searched for current [issues](https://github.com/theme-next/hexo-theme-next/issues), which does not help me.
+
+***
+
+## Expected behavior
+
+
+## Actual behavior
+
+
+- Links to demo site with this issue: N/A
+- Links to repository or source code of the blog: N/A
+
+
+## Steps to reproduce the behavior
+1. N/A
+2. N/A
+3. N/A
+
+
+## Environment Information
+
+### Node.js and NPM Information
+
+```
+
+```
+
+### Package dependencies Information
+
+```
+
+```
+
+### Hexo Configuration
+
+```yml
+
+```
+
+### NexT Configuration
+
+```yml
+
+```
+
+## Other Information
diff --git a/themes/next/.github/PULL_REQUEST_TEMPLATE.md b/themes/next/.github/PULL_REQUEST_TEMPLATE.md
new file mode 100644
index 0000000..f1982e0
--- /dev/null
+++ b/themes/next/.github/PULL_REQUEST_TEMPLATE.md
@@ -0,0 +1,46 @@
+
+
+## PR Checklist
+
+
+- [ ] The commit message follows [guidelines for NexT](https://github.com/theme-next/hexo-theme-next/blob/master/.github/CONTRIBUTING.md).
+- [ ] Tests for the changes was maked (for bug fixes / features).
+ - [ ] Muse | Mist have been tested.
+ - [ ] Pisces | Gemini have been tested.
+- [ ] [Docs](https://github.com/theme-next/theme-next.org/tree/source/source/docs) in [NexT website](https://theme-next.org/docs/) have been added / updated (for features).
+
+
+## PR Type
+
+
+- [ ] Bugfix.
+- [ ] Feature.
+- [ ] Code style update (formatting, local variables).
+- [ ] Refactoring (no functional changes, no api changes).
+- [ ] Build & CI related changes.
+- [ ] Documentation.
+- [ ] Translation.
+- [ ] Other... Please describe:
+
+## What is the current behavior?
+
+
+Issue resolved: N/A
+
+## What is the new behavior?
+
+
+- Screenshots with this changes: N/A
+- Link to demo site with this changes: N/A
+
+### How to use?
+In NexT `_config.yml`:
+```yml
+
+```
diff --git a/themes/next/.github/config.yml b/themes/next/.github/config.yml
new file mode 100644
index 0000000..5476d81
--- /dev/null
+++ b/themes/next/.github/config.yml
@@ -0,0 +1,47 @@
+# =============================================================================================== #
+# Configuration for welcome - https://github.com/behaviorbot/welcome
+
+# Comment to be posted to on first time issues
+newIssueWelcomeComment: >
+ Thanks for opening this issue, maintainers will get back to you as soon as possible!
+
+# Comment to be posted to on PRs from first time contributors in your repository
+newPRWelcomeComment: >
+ Thanks so much for opening your first PR here!
+
+# Comment to be posted to on pull requests merged by a first time user
+firstPRMergeComment: >
+ Congrats on merging your first pull request here! :tada: How awesome!
+
+# =============================================================================================== #
+# Configuration for request-info - https://github.com/behaviorbot/request-info
+
+# *OPTIONAL* Label to be added to Issues and Pull Requests with insufficient information given
+requestInfoLabelToAdd: Need More Info
+
+# *OPTIONAL* Add a list of people whose Issues/PRs will not be commented on
+# keys must be GitHub usernames
+requestInfoUserstoExclude:
+ - 1v9
+ - Acris
+ - flashlab
+ - geekrainy
+ - iissnan
+ - ivan-nginx
+ - JiangTJ
+ - LEAFERx
+ - liolok
+ - maple3142
+ - Raincal
+ - sli1989
+ - stevenjoezhang
+ - tsanie
+ - wafer-li
+
+# =============================================================================================== #
+lockThreads:
+ toxicityThreshold: .7
+ numComments: 2
+ setTimeInHours: 72
+ replyComment: >
+ This thread is being locked due to exceeding the toxicity minimums. cc/ @theme-next/next
diff --git a/themes/next/.github/issue-close-app.yml b/themes/next/.github/issue-close-app.yml
new file mode 100644
index 0000000..daa3e1e
--- /dev/null
+++ b/themes/next/.github/issue-close-app.yml
@@ -0,0 +1,16 @@
+# Comment that will be sent if an issue is judged to be closed.
+comment: "This issue has been closed because it does not meet our Issue template. Please read our [guidelines for contributing](https://github.com/theme-next/hexo-theme-next/blob/master/.github/CONTRIBUTING.md#how-can-i-contribute)."
+issueConfigs:
+# There can be several configs for different kind of issues.
+- content:
+ - "Issue Checklist"
+# Optional configuration:
+#
+# whether the keywords are case-insensitive
+# default value is false, which means keywords are case-sensitive
+caseInsensitive: true
+# the label that will be added when the bot close an issue
+# The bot will only add a label if this property is set.
+label: "Invalid"
+# The issue is judged to be legal if it includes all keywords from any of these two configs.
+# Or it will be closed by the app.
diff --git a/themes/next/.github/issue_label_bot.yaml b/themes/next/.github/issue_label_bot.yaml
new file mode 100644
index 0000000..a0d4c94
--- /dev/null
+++ b/themes/next/.github/issue_label_bot.yaml
@@ -0,0 +1,4 @@
+label-alias:
+ bug: 'Bug'
+ feature_request: 'Feature Request'
+ question: 'Question'
diff --git a/themes/next/.github/lock.yml b/themes/next/.github/lock.yml
new file mode 100644
index 0000000..b2564db
--- /dev/null
+++ b/themes/next/.github/lock.yml
@@ -0,0 +1,38 @@
+# Configuration for Lock Threads - https://github.com/dessant/lock-threads
+
+# Number of days of inactivity before a closed issue or pull request is locked
+daysUntilLock: 365
+
+# Skip issues and pull requests created before a given timestamp. Timestamp must
+# follow ISO 8601 (`YYYY-MM-DD`). Set to `false` to disable
+skipCreatedBefore: false
+
+# Issues and pull requests with these labels will be ignored. Set to `[]` to disable
+exemptLabels: []
+
+# Label to add before locking, such as `outdated`. Set to `false` to disable
+lockLabel: false
+
+# Comment to post before locking. Set to `false` to disable
+lockComment: >
+ This thread has been automatically locked since there has not been
+ any recent activity after it was closed. It is possible issue was
+ solved or at least outdated. Feel free to open new for related bugs.
+
+# Assign `resolved` as the reason for locking. Set to `false` to disable
+setLockReason: true
+
+# Limit to only `issues` or `pulls`
+only: issues
+
+# Optionally, specify configuration settings just for `issues` or `pulls`
+# issues:
+# exemptLabels:
+# - help-wanted
+# lockLabel: outdated
+
+# pulls:
+# daysUntilLock: 30
+
+# Repository to extend settings from
+# _extends: repo
diff --git a/themes/next/.github/mergeable.yml b/themes/next/.github/mergeable.yml
new file mode 100644
index 0000000..73e9c42
--- /dev/null
+++ b/themes/next/.github/mergeable.yml
@@ -0,0 +1,29 @@
+# Configuration for Mergeable - https://github.com/jusx/mergeable
+
+version: 2
+mergeable:
+ - when: pull_request.*
+ validate:
+ - do: description
+ no_empty:
+ enabled: false
+
+ - do: title
+ must_exclude:
+ regex: ^\[WIP\]
+
+ - do: label
+ must_include:
+ regex: 'change|feat|imp|fix|doc|i18n'
+ must_exclude:
+ regex: 'wip|work in progress'
+
+ #- do: project
+ # no_empty:
+ # enabled: true
+ # must_include:
+ # regex: 'change|feat|imp|fix|doc|loc'
+
+ - do: milestone
+ no_empty:
+ enabled: true
diff --git a/themes/next/.github/release-drafter.yml b/themes/next/.github/release-drafter.yml
new file mode 100644
index 0000000..a70af9c
--- /dev/null
+++ b/themes/next/.github/release-drafter.yml
@@ -0,0 +1,40 @@
+# Configuration for Release Drafter - https://github.com/toolmantim/release-drafter
+
+name-template: 'v$NEXT_MINOR_VERSION'
+tag-template: 'v$NEXT_MINOR_VERSION'
+categories:
+ - title: '💥 Breaking Changes'
+ label: '💥 Breaking Change'
+
+ - title: '🌟 New Features'
+ label: '🌟 New Feature'
+
+ - title: '⭐ Features'
+ label: '⭐ Feature'
+
+ - title: '🐞 Bug Fixes'
+ label: '🐞 Bug Fix'
+
+ - title: '🛠 Improvements'
+ label: '🛠 Improvement'
+
+ - title: '🌀 External Changes'
+ label: '🔌 3rd Party Plugin'
+
+ - title: '📖 Documentation'
+ label: '📖 Docs'
+
+ - title: '🌍 Localization'
+ label: '🌍 i18n'
+
+change-template: '- $TITLE (#$NUMBER)'
+no-changes-template: '- No changes'
+template: |
+ $CHANGES
+
+ ***
+
+ For full changes, see the [comparison between $PREVIOUS_TAG and v$NEXT_MINOR_VERSION](https://github.com/theme-next/hexo-theme-next/compare/$PREVIOUS_TAG...v$NEXT_MINOR_VERSION)
+
+exclude-labels:
+ - 'Skip Release'
diff --git a/themes/next/.github/stale.yml b/themes/next/.github/stale.yml
new file mode 100644
index 0000000..3af279e
--- /dev/null
+++ b/themes/next/.github/stale.yml
@@ -0,0 +1,26 @@
+# Configuration for probot-stale - https://github.com/probot/stale
+
+# Number of days of inactivity before an Issue or Pull Request becomes stale
+daysUntilStale: 30
+# Number of days of inactivity before a stale Issue or Pull Request is closed
+daysUntilClose: 7
+# Issues or Pull Requests with these labels will never be considered stale. Set to `[]` to disable
+exemptLabels:
+ - Bug
+ - Feature Request
+ - Discussion
+ - Help Wanted
+ - Question
+# Label to use when marking as stale
+staleLabel: stale
+# Comment to post when marking as stale. Set to `false` to disable
+markComment: >
+ This issue has been automatically marked as stale because lack of
+ recent activity. It will be closed if no further activity occurs. Thank you
+ for your contributions. You can also use our [support channels](https://github.com/theme-next/hexo-theme-next#feedback) to get help with the project.
+# Comment to post when removing the stale label. Set to `false` to disable
+unmarkComment: false
+# Comment to post when closing a stale Issue or Pull Request. Set to `false` to disable
+closeComment: false
+# Limit to only `issues` or `pulls`
+only: issues
diff --git a/themes/next/.github/support.yml b/themes/next/.github/support.yml
new file mode 100644
index 0000000..6eb9741
--- /dev/null
+++ b/themes/next/.github/support.yml
@@ -0,0 +1,23 @@
+# Configuration for Support Requests - https://github.com/dessant/support-requests
+
+# Label used to mark issues as support requests
+supportLabel: Support
+
+# Comment to post on issues marked as support requests, `{issue-author}` is an
+# optional placeholder. Set to `false` to disable
+supportComment: >
+ :wave: @{issue-author}, we use the issue tracker exclusively for bug reports
+ and feature requests. However, this issue appears to be a support request.
+ Please use our [support channels](https://github.com/theme-next/hexo-theme-next/tree/master#feedback) to get help with the project.
+
+# Close issues marked as support requests
+close: true
+
+# Lock issues marked as support requests
+lock: false
+
+# Assign `off-topic` as the reason for locking. Set to `false` to disable
+setLockReason: true
+
+# Repository to extend settings from
+# _extends: repo
diff --git a/themes/next/.gitignore b/themes/next/.gitignore
new file mode 100644
index 0000000..996e516
--- /dev/null
+++ b/themes/next/.gitignore
@@ -0,0 +1,15 @@
+.DS_Store
+.idea/
+*.log
+*.iml
+yarn.lock
+package-lock.json
+node_modules/
+
+# Ignore optional external libraries
+source/lib/*
+
+# Track internal libraries & Ignore unused verdors files
+!source/lib/font-awesome/
+!source/lib/anime.min.js
+!source/lib/velocity/
diff --git a/themes/next/.stylintrc b/themes/next/.stylintrc
new file mode 100644
index 0000000..724a26c
--- /dev/null
+++ b/themes/next/.stylintrc
@@ -0,0 +1,45 @@
+{
+ "blocks": false,
+ "brackets": "always",
+ "colons": "always",
+ "colors": "always",
+ "commaSpace": "always",
+ "commentSpace": "always",
+ "cssLiteral": "never",
+ "customProperties": [],
+ "depthLimit": false,
+ "duplicates": true,
+ "efficient": "always",
+ "exclude": [],
+ "extendPref": false,
+ "globalDupe": false,
+ "groupOutputByFile": true,
+ "indentPref": false,
+ "leadingZero": "never",
+ "maxErrors": false,
+ "maxWarnings": false,
+ "mixed": false,
+ "mixins": [],
+ "namingConvention": "lowercase-dash",
+ "namingConventionStrict": false,
+ "none": "never",
+ "noImportant": true,
+ "parenSpace": false,
+ "placeholders": "always",
+ "prefixVarsWithDollar": "always",
+ "quotePref": false,
+ "reporterOptions": {
+ "columns": ["lineData", "severity", "description", "rule"],
+ "columnSplitter": " ",
+ "showHeaders": false,
+ "truncate": true
+ },
+ "semicolons": "always",
+ "sortOrder": "alphabetical",
+ "stackedProperties": false,
+ "trailingWhitespace": "never",
+ "universal": false,
+ "valid": true,
+ "zeroUnits": "never",
+ "zIndexNormalize": false
+}
diff --git a/themes/next/.travis.yml b/themes/next/.travis.yml
new file mode 100644
index 0000000..cdad71c
--- /dev/null
+++ b/themes/next/.travis.yml
@@ -0,0 +1,8 @@
+language: node_js
+
+node_js: node
+
+cache:
+ npm: true
+
+install: npm install
diff --git a/themes/next/LICENSE.md b/themes/next/LICENSE.md
new file mode 100644
index 0000000..03f8993
--- /dev/null
+++ b/themes/next/LICENSE.md
@@ -0,0 +1,63 @@
+#
Detail attribution information for «NexT»
+ is contained in the 'docs/AUTHORS.md' file.
+
+ This program is free software; you can redistribute it and/or modify
+it under the terms of the [GNU Affero General Public License version 3][AGPL3]
+as published by the Free Software Foundation with the addition of the
+following permission added to [Section 15][AGPL3-15] as permitted in [Section 7(a)][AGPL3-7]:
+FOR ANY PART OF THE COVERED WORK IN WHICH THE COPYRIGHT IS OWNED BY «NEXT»,
+«NEXT» DISCLAIMS THE WARRANTY OF NON INFRINGEMENT OF THIRD PARTY RIGHTS.
+
+ This program is distributed in the hope that it will be useful, but
+WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY
+or FITNESS FOR A PARTICULAR PURPOSE.
+See the GNU Affero General Public License for more details.
+You should have received a copy of the GNU Affero General Public License
+along with this program; if not, see: https://www.gnu.org/licenses/agpl.txt
+
+ In accordance with [Section 7(b)][AGPL3-7] of the GNU Affero General Public License:
+
+* a) It is not necessary to specify copyright in each source file of
+ this program because GitHub fully save commits of all modified files
+ with their authors and provides to see for this changes publicly.
+
+* b) For any part of the covered work in which the copyright not specified,
+ except of third party libraries ('[source/lib/*](source/lib)') and '\*custom.\*' files,
+ will mean this part owned by «NexT» in accord with terms in this file.
+
+* c) A covered work must retain «NexT» official website link
+ (https://theme-next.org) in footer section of every website created,
+ modified or manipulated by using «NexT».
+ «NexT» theme configuration must be:
+ ```yml
+ footer:
+ theme:
+ enable: true
+ ```
+ Collaborators, best contributors and all authors specified in the
+ '[docs/AUTHORS.md][AUTHORS]' file of «NexT» repository under the
+ 'https://github.com/theme-next' organization can ignore theme info link
+ requirements.
+
+Anyone can be released from the requirements of the license by purchasing
+a commercial license. Buying such a license is mandatory as soon as you
+develop commercial activities involving the «NexT» software without
+disclosing the source code of your own applications.
+These activities include:
+ 1. Access to private repository with various premium features.
+ 2. Priority support for resolve all possible issues with «NexT».
+ 3. Priority support for implement all possible features to «NexT».
+
+ For more information, please contact «NexT» Organization at this
+address: support@theme-next.org
+
+
+
+## Installation
+
+The simplest way to install is to clone the entire repository:
+
+```sh
+$ cd hexo
+$ git clone https://github.com/theme-next/hexo-theme-next themes/next
+```
+
+Or you can see [detailed installation instructions][docs-installation-url] if you want any other variant.
+
+## Plugins
+
+NexT supports a large number of third-party plugins, which can be easily configured.
+
+For example, if you want to enable `pjax` on your site, just set `pjax` to `true` in NexT config file:
+
+```yml
+# Easily enable fast Ajax navigation on your website.
+# Dependencies: https://github.com/theme-next/theme-next-pjax
+pjax: true
+```
+
+Then visit the «Dependencies» link to get the installation instructions of this module.
+
+### Configure CDN
+
+If you want to specify a CDN link for any plugins, you need to set / update the CDN link.
+
+For example, if you want to use `mediumzoom` and load the plugin via CDN, go to NexT config and see:
+
+```yml
+vendors:
+ # ...
+ # Some contents...
+ # ...
+ mediumzoom: # Set or update mediumzoom CDN URL.
+```
+
+## Update
+
+NexT releases new versions every month. You can update to latest master branch by the following command:
+
+```sh
+$ cd themes/next
+$ git pull
+```
+
+And if you see any error message during update (something like **«Commit your changes or stash them before you can merge»**), recommended to learn [Hexo data files][docs-data-files-url] feature.\
+However, you can bypass update errors by using the `Commit`, `Stash` or `Reset` commands for local changes. See [here](https://stackoverflow.com/a/15745424/5861495) how to do it.
+
+**If you want to update from v5.1.x to the latest version, read [this][docs-update-5-1-x-url].**
+
+## Feedback
+
+* Visit the [Awesome NexT][awesome-next-url] list to share plugins and tutorials with other users.
+* Join our [Telegram][t-chat-url] / [Gitter][gitter-url] / [Riot][riot-url] chats.
+* [Add or improve translation][i18n-url] in few seconds.
+* Report a bug in [GitHub Issues][issues-bug-url].
+* Request a new feature on [GitHub][issues-feat-url].
+* Vote for [popular feature requests][feat-req-vote-url].
+
+## Contributing
+
+We welcome you to join the development of NexT. Please see [contributing document][contributing-document-url]. 🤗
+
+Also, we welcome Issue or PR to our [official-plugins][official-plugins-url].
+
+## Contributors
+
+[![][contributors-image]][contributors-url]
+
+## Thanks
+
+
+ «NexT» send special thanks to these great services that sponsor our core infrastructure:
+
+
+
+
+
+
+
+ GitHub allows us to host the Git repository, Netlify allows us to distribute the documentation.
+
+
+
+
+
+ Crowdin allows us to translate conveniently the documentation.
+
+
+
+
+
+
+
+ Codacy allows us to monitor code quality, Travis CI allows us to run the test suite.
+
+
+[docs-installation-url]: https://github.com/theme-next/hexo-theme-next/blob/master/docs/INSTALLATION.md
+[docs-data-files-url]: https://github.com/theme-next/hexo-theme-next/blob/master/docs/DATA-FILES.md
+[docs-update-5-1-x-url]: https://github.com/theme-next/hexo-theme-next/blob/master/docs/UPDATE-FROM-5.1.X.md
+
+[t-news-url]: https://t.me/theme_next_news
+[t-chat-url]: https://t.me/theme_next
+[gitter-url]: https://gitter.im/theme-next
+[riot-url]: https://riot.im/app/#/room/#theme-next:matrix.org
+[i18n-url]: https://i18n.theme-next.org
+
+[awesome-next-url]: https://github.com/theme-next/awesome-next
+[issues-bug-url]: https://github.com/theme-next/hexo-theme-next/issues/new?assignees=&labels=Bug&template=bug-report.md
+[issues-feat-url]: https://github.com/theme-next/hexo-theme-next/issues/new?assignees=&labels=Feature+Request&template=feature-request.md
+[feat-req-vote-url]: https://github.com/theme-next/hexo-theme-next/issues?q=is%3Aopen+is%3Aissue+label%3A%22Feature+Request%22
+
+[contributing-document-url]: https://github.com/theme-next/hexo-theme-next/blob/master/.github/CONTRIBUTING.md
+[official-plugins-url]: https://github.com/theme-next
+[contributors-image]: https://opencollective.com/theme-next/contributors.svg?width=890
+[contributors-url]: https://github.com/theme-next/hexo-theme-next/graphs/contributors
diff --git a/themes/next/_config.yml b/themes/next/_config.yml
new file mode 100644
index 0000000..61cc72d
--- /dev/null
+++ b/themes/next/_config.yml
@@ -0,0 +1,997 @@
+# ---------------------------------------------------------------
+# Theme Core Configuration Settings
+# See: https://theme-next.org/docs/theme-settings/
+# ---------------------------------------------------------------
+
+# If false, merge configs from `_data/next.yml` into default configuration (rewrite).
+# If true, will fully override default configuration by options from `_data/next.yml` (override). Only for NexT settings.
+# And if true, all config from default NexT `_config.yml` have to be copied into `next.yml`. Use if you know what you are doing.
+# Useful if you want to comment some options from NexT `_config.yml` by `next.yml` without editing default config.
+override: false
+
+# Console reminder if new version released.
+reminder: false
+
+# Allow to cache content generation. Introduced in NexT v6.0.0.
+cache:
+ enable: true
+
+# Remove unnecessary files after hexo generate.
+minify: false
+
+# Define custom file paths.
+# Create your custom files in site directory `source/_data` and uncomment needed files below.
+custom_file_path:
+ #head: source/_data/head.swig
+ #header: source/_data/header.swig
+ #sidebar: source/_data/sidebar.swig
+ #postMeta: source/_data/post-meta.swig
+ #postBodyEnd: source/_data/post-body-end.swig
+ #footer: source/_data/footer.swig
+ #bodyEnd: source/_data/body-end.swig
+ #variable: source/_data/variables.styl
+ #mixin: source/_data/mixins.styl
+ #style: source/_data/styles.styl
+
+
+# ---------------------------------------------------------------
+# Site Information Settings
+# See: https://theme-next.org/docs/getting-started/
+# ---------------------------------------------------------------
+
+favicon:
+ small: /images/favicon-16x16-next.png
+ medium: /images/favicon-32x32-next.png
+ apple_touch_icon: /images/apple-touch-icon-next.png
+ safari_pinned_tab: /images/logo.svg
+ #android_manifest: /images/manifest.json
+ #ms_browserconfig: /images/browserconfig.xml
+
+# Show multilingual switcher in footer.
+language_switcher: false
+
+footer:
+ # Specify the date when the site was setup. If not defined, current year will be used.
+ #since: 2015
+
+ # Icon between year and copyright info.
+ icon:
+ # Icon name in Font Awesome. See: https://fontawesome.com/icons
+ name: fa fa-heart
+ # If you want to animate the icon, set it to true.
+ animated: false
+ # Change the color of icon, using Hex Code.
+ color: "#ff0000"
+
+ # If not defined, `author` from Hexo `_config.yml` will be used.
+ copyright:
+
+ # Powered by Hexo & NexT
+ powered: true
+
+ # Beian ICP and gongan information for Chinese users. See: https://beian.miit.gov.cn, http://www.beian.gov.cn
+ beian:
+ enable: false
+ icp:
+ # The digit in the num of gongan beian.
+ gongan_id:
+ # The full num of gongan beian.
+ gongan_num:
+ # The icon for gongan beian. See: http://www.beian.gov.cn/portal/download
+ gongan_icon_url:
+
+# Creative Commons 4.0 International License.
+# See: https://creativecommons.org/share-your-work/licensing-types-examples
+# Available values of license: by | by-nc | by-nc-nd | by-nc-sa | by-nd | by-sa | zero
+# You can set a language value if you prefer a translated version of CC license, e.g. deed.zh
+# CC licenses are available in 39 languages, you can find the specific and correct abbreviation you need on https://creativecommons.org
+creative_commons:
+ license: by-nc-sa
+ sidebar: false
+ post: false
+ language:
+
+
+# ---------------------------------------------------------------
+# Scheme Settings
+# ---------------------------------------------------------------
+
+# Schemes
+scheme: Muse
+#scheme: Mist
+#scheme: Pisces
+#scheme: Gemini
+
+# Dark Mode
+darkmode: false
+
+
+# ---------------------------------------------------------------
+# Menu Settings
+# ---------------------------------------------------------------
+
+# Usage: `Key: /link/ || icon`
+# Key is the name of menu item. If the translation for this item is available, the translated text will be loaded, otherwise the Key name will be used. Key is case-senstive.
+# Value before `||` delimiter is the target link, value after `||` delimiter is the name of Font Awesome icon.
+# When running the site in a subdirectory (e.g. yoursite.com/blog), remove the leading slash from link value (/archives -> archives).
+# External url should start with http:// or https://
+menu:
+ home: / || fa fa-home
+ #about: /about/ || fa fa-user
+ #tags: /tags/ || fa fa-tags
+ #categories: /categories/ || fa fa-th
+ archives: /archives/ || fa fa-archive
+ #schedule: /schedule/ || fa fa-calendar
+ #sitemap: /sitemap.xml || fa fa-sitemap
+ #commonweal: /404/ || fa fa-heartbeat
+
+# Enable / Disable menu icons / item badges.
+menu_settings:
+ icons: true
+ badges: false
+
+
+# ---------------------------------------------------------------
+# Sidebar Settings
+# See: https://theme-next.org/docs/theme-settings/sidebar
+# ---------------------------------------------------------------
+
+sidebar:
+ # Sidebar Position.
+ position: left
+ #position: right
+
+ # Manual define the sidebar width. If commented, will be default for:
+ # Muse | Mist: 320
+ # Pisces | Gemini: 240
+ #width: 300
+
+ # Sidebar Display (only for Muse | Mist), available values:
+ # - post expand on posts automatically. Default.
+ # - always expand for all pages automatically.
+ # - hide expand only when click on the sidebar toggle icon.
+ # - remove totally remove sidebar including sidebar toggle.
+ display: post
+
+ # Sidebar padding in pixels.
+ padding: 18
+ # Sidebar offset from top menubar in pixels (only for Pisces | Gemini).
+ offset: 12
+ # Enable sidebar on narrow view (only for Muse | Mist).
+ onmobile: false
+
+# Sidebar Avatar
+avatar:
+ # Replace the default image and set the url here.
+ url: #/images/avatar.gif
+ # If true, the avatar will be dispalyed in circle.
+ rounded: false
+ # If true, the avatar will be rotated with the cursor.
+ rotated: false
+
+# Posts / Categories / Tags in sidebar.
+site_state: true
+
+# Social Links
+# Usage: `Key: permalink || icon`
+# Key is the link label showing to end users.
+# Value before `||` delimiter is the target permalink, value after `||` delimiter is the name of Font Awesome icon.
+social:
+ #GitHub: https://github.com/yourname || fab fa-github
+ #E-Mail: mailto:yourname@gmail.com || fa fa-envelope
+ #Weibo: https://weibo.com/yourname || fab fa-weibo
+ #Google: https://plus.google.com/yourname || fab fa-google
+ #Twitter: https://twitter.com/yourname || fab fa-twitter
+ #FB Page: https://www.facebook.com/yourname || fab fa-facebook
+ #StackOverflow: https://stackoverflow.com/yourname || fab fa-stack-overflow
+ #YouTube: https://youtube.com/yourname || fab fa-youtube
+ #Instagram: https://instagram.com/yourname || fab fa-instagram
+ #Skype: skype:yourname?call|chat || fab fa-skype
+
+social_icons:
+ enable: true
+ icons_only: false
+ transition: false
+
+# Blog rolls
+links_settings:
+ icon: fa fa-link
+ title: Links
+ # Available values: block | inline
+ layout: block
+
+links:
+ #Title: http://yoursite.com
+
+# Table of Contents in the Sidebar
+# Front-matter variable (unsupport wrap expand_all).
+toc:
+ enable: true
+ # Automatically add list number to toc.
+ number: true
+ # If true, all words will placed on next lines if header width longer then sidebar width.
+ wrap: false
+ # If true, all level of TOC in a post will be displayed, rather than the activated part of it.
+ expand_all: false
+ # Maximum heading depth of generated toc.
+ max_depth: 6
+
+# A button to open designated chat widget in sidebar.
+# Firstly, you need enable the chat service you want to activate its sidebar button.
+chat:
+ enable: false
+ #service: chatra
+ #service: tidio
+ icon: fa fa-comment # Icon name in Font Awesome, set false to disable icon.
+ text: Chat # Button text, change it as you wish.
+
+
+# ---------------------------------------------------------------
+# Post Settings
+# See: https://theme-next.org/docs/theme-settings/posts
+# ---------------------------------------------------------------
+
+# Automatically excerpt description in homepage as preamble text.
+excerpt_description: true
+
+# Read more button
+# If true, the read more button will be displayed in excerpt section.
+read_more_btn: true
+
+# Post meta display settings
+post_meta:
+ item_text: true
+ created_at: true
+ updated_at:
+ enable: true
+ another_day: true
+ categories: true
+
+# Post wordcount display settings
+# Dependencies: https://github.com/theme-next/hexo-symbols-count-time
+symbols_count_time:
+ separated_meta: true
+ item_text_post: true
+ item_text_total: false
+
+# Use icon instead of the symbol # to indicate the tag at the bottom of the post
+tag_icon: false
+
+# Reward (Donate)
+# Front-matter variable (unsupport animation).
+reward_settings:
+ # If true, reward will be displayed in every article by default.
+ enable: false
+ animation: false
+ #comment: Donate comment here.
+
+reward:
+ #wechatpay: /images/wechatpay.png
+ #alipay: /images/alipay.png
+ #paypal: /images/paypal.png
+ #bitcoin: /images/bitcoin.png
+
+# Subscribe through Telegram Channel, Twitter, etc.
+# Usage: `Key: permalink || icon` (Font Awesome)
+follow_me:
+ #Twitter: https://twitter.com/username || fab fa-twitter
+ #Telegram: https://t.me/channel_name || fab fa-telegram
+ #WeChat: /images/wechat_channel.jpg || fab fa-weixin
+ #RSS: /atom.xml || fa fa-rss
+
+# Related popular posts
+# Dependencies: https://github.com/tea3/hexo-related-popular-posts
+related_posts:
+ enable: false
+ title: # Custom header, leave empty to use the default one
+ display_in_home: false
+ params:
+ maxCount: 5
+ #PPMixingRate: 0.0
+ #isDate: false
+ #isImage: false
+ #isExcerpt: false
+
+# Post edit
+# Dependencies: https://github.com/hexojs/hexo-deployer-git
+post_edit:
+ enable: false
+ url: https://github.com/user-name/repo-name/tree/branch-name/subdirectory-name # Link for view source
+ #url: https://github.com/user-name/repo-name/edit/branch-name/subdirectory-name # Link for fork & edit
+
+# Show previous post and next post in post footer if exists
+# Available values: left | right | false
+post_navigation: left
+
+
+# ---------------------------------------------------------------
+# Custom Page Settings
+# See: https://theme-next.org/docs/theme-settings/custom-pages
+# ---------------------------------------------------------------
+
+# TagCloud settings for tags page.
+tagcloud:
+ # All values below are same as default, change them by yourself.
+ min: 12 # Minimun font size in px
+ max: 30 # Maxium font size in px
+ start: "#ccc" # Start color (hex, rgba, hsla or color keywords)
+ end: "#111" # End color (hex, rgba, hsla or color keywords)
+ amount: 200 # Amount of tags, change it if you have more than 200 tags
+
+# Google Calendar
+# Share your recent schedule to others via calendar page.
+calendar:
+ calendar_id: # Your Google account E-Mail
+ api_key:
+ orderBy: startTime
+ offsetMax: 24 # Time Range
+ offsetMin: 4 # Time Range
+ showDeleted: false
+ singleEvents: true
+ maxResults: 250
+
+
+# ---------------------------------------------------------------
+# Misc Theme Settings
+# ---------------------------------------------------------------
+
+# Set the text alignment in posts / pages.
+text_align:
+ # Available values: start | end | left | right | center | justify | justify-all | match-parent
+ desktop: justify
+ mobile: justify
+
+# Reduce padding / margin indents on devices with narrow width.
+mobile_layout_economy: false
+
+# Android Chrome header panel color ($brand-bg / $headband-bg => $black-deep).
+android_chrome_color: "#222"
+
+# Custom Logo (Do not support scheme Mist)
+custom_logo: #/uploads/custom-logo.jpg
+
+codeblock:
+ # Code Highlight theme
+ # Available values: normal | night | night eighties | night blue | night bright | solarized | solarized dark | galactic
+ # See: https://github.com/chriskempson/tomorrow-theme
+ highlight_theme: normal
+ # Add copy button on codeblock
+ copy_button:
+ enable: false
+ # Show text copy result.
+ show_result: false
+ # Available values: default | flat | mac
+ style:
+
+back2top:
+ enable: true
+ # Back to top in sidebar.
+ sidebar: false
+ # Scroll percent label in b2t button.
+ scrollpercent: false
+
+# Reading progress bar
+reading_progress:
+ enable: false
+ # Available values: top | bottom
+ position: top
+ color: "#37c6c0"
+ height: 3px
+
+# Bookmark Support
+bookmark:
+ enable: false
+ # Customize the color of the bookmark.
+ color: "#222"
+ # If auto, save the reading progress when closing the page or clicking the bookmark-icon.
+ # If manual, only save it by clicking the bookmark-icon.
+ save: auto
+
+# `Follow me on GitHub` banner in the top-right corner.
+github_banner:
+ enable: false
+ permalink: https://github.com/yourname
+ title: Follow me on GitHub
+
+
+# ---------------------------------------------------------------
+# Font Settings
+# See: https://theme-next.org/docs/theme-settings/#Fonts-Customization
+# ---------------------------------------------------------------
+# Find fonts on Google Fonts (https://www.google.com/fonts)
+# All fonts set here will have the following styles:
+# light | light italic | normal | normal italic | bold | bold italic
+# Be aware that setting too much fonts will cause site running slowly
+# ---------------------------------------------------------------
+# To avoid space between header and sidebar in scheme Pisces / Gemini, Web Safe fonts are recommended for `global` (and `title`):
+# Arial | Tahoma | Helvetica | Times New Roman | Courier New | Verdana | Georgia | Palatino | Garamond | Comic Sans MS | Trebuchet MS
+# ---------------------------------------------------------------
+
+font:
+ enable: false
+
+ # Uri of fonts host, e.g. https://fonts.googleapis.com (Default).
+ host:
+
+ # Font options:
+ # `external: true` will load this font family from `host` above.
+ # `family: Times New Roman`. Without any quotes.
+ # `size: x.x`. Use `em` as unit. Default: 1 (16px)
+
+ # Global font settings used for all elements inside .
+ global:
+ external: true
+ family: Lato
+ size:
+
+ # Font settings for site title (.site-title).
+ title:
+ external: true
+ family:
+ size:
+
+ # Font settings for headlines (
to
).
+ headings:
+ external: true
+ family:
+ size:
+
+ # Font settings for posts (.post-body).
+ posts:
+ external: true
+ family:
+
+ # Font settings for and code blocks.
+ codes:
+ external: true
+ family:
+
+
+# ---------------------------------------------------------------
+# SEO Settings
+# ---------------------------------------------------------------
+
+# Disable Baidu transformation on mobile devices.
+disable_baidu_transformation: false
+
+# If true, site-subtitle will be added to index page.
+# Remember to set up your site-subtitle in Hexo `_config.yml` (e.g. subtitle: Subtitle)
+index_with_subtitle: false
+
+# Automatically add external URL with Base64 encrypt & decrypt.
+exturl: false
+
+# Google Webmaster tools verification.
+# See: https://www.google.com/webmasters
+google_site_verification:
+
+# Bing Webmaster tools verification.
+# See: https://www.bing.com/webmaster
+bing_site_verification:
+
+# Yandex Webmaster tools verification.
+# See: https://webmaster.yandex.ru
+yandex_site_verification:
+
+# Baidu Webmaster tools verification.
+# See: https://ziyuan.baidu.com/site
+baidu_site_verification:
+
+# Enable baidu push so that the blog will push the url to baidu automatically which is very helpful for SEO.
+baidu_push: false
+
+
+# ---------------------------------------------------------------
+# Third Party Plugins & Services Settings
+# See: https://theme-next.org/docs/third-party-services/
+# More plugins: https://github.com/theme-next/awesome-next
+# You may need to install dependencies or set CDN URLs in `vendors`
+# There are two different CDN providers by default:
+# - jsDelivr (cdn.jsdelivr.net), works everywhere even in China
+# - CDNJS (cdnjs.cloudflare.com), provided by cloudflare
+# ---------------------------------------------------------------
+
+# Math Formulas Render Support
+math:
+ # Default (true) will load mathjax / katex script on demand.
+ # That is it only render those page which has `mathjax: true` in Front-matter.
+ # If you set it to false, it will load mathjax / katex srcipt EVERY PAGE.
+ per_page: true
+
+ # hexo-renderer-pandoc (or hexo-renderer-kramed) required for full MathJax support.
+ mathjax:
+ enable: false
+ # See: https://mhchem.github.io/MathJax-mhchem/
+ mhchem: false
+
+ # hexo-renderer-markdown-it-plus (or hexo-renderer-markdown-it with markdown-it-katex plugin) required for full Katex support.
+ katex:
+ enable: false
+ # See: https://github.com/KaTeX/KaTeX/tree/master/contrib/copy-tex
+ copy_tex: false
+
+# Easily enable fast Ajax navigation on your website.
+# Dependencies: https://github.com/theme-next/theme-next-pjax
+pjax: false
+
+# FancyBox is a tool that offers a nice and elegant way to add zooming functionality for images.
+# For more information: https://fancyapps.com/fancybox
+fancybox: false
+
+# A JavaScript library for zooming images like Medium.
+# Do not enable both `fancybox` and `mediumzoom`.
+# For more information: https://github.com/francoischalifour/medium-zoom
+mediumzoom: false
+
+# Vanilla JavaScript plugin for lazyloading images.
+# For more information: https://github.com/ApoorvSaxena/lozad.js
+lazyload: false
+
+# Pangu Support
+# For more information: https://github.com/vinta/pangu.js
+pangu: false
+
+# Quicklink Support
+# Do not enable both `pjax` and `quicklink`.
+# For more information: https://github.com/GoogleChromeLabs/quicklink
+# Front-matter (unsupport home archive).
+quicklink:
+ enable: false
+
+ # Home page and archive page can be controlled through home and archive options below.
+ # This configuration item is independent of `enable`.
+ home: false
+ archive: false
+
+ # Default (true) will initialize quicklink after the load event fires.
+ delay: true
+ # Custom a time in milliseconds by which the browser must execute prefetching.
+ timeout: 3000
+ # Default (true) will enable fetch() or falls back to XHR.
+ priority: true
+
+ # For more flexibility you can add some patterns (RegExp, Function, or Array) to ignores.
+ # See: https://github.com/GoogleChromeLabs/quicklink#custom-ignore-patterns
+ ignores:
+
+
+# ---------------------------------------------------------------
+# Comments Settings
+# See: https://theme-next.org/docs/third-party-services/comments
+# ---------------------------------------------------------------
+
+# Multiple Comment System Support
+comments:
+ # Available values: tabs | buttons
+ style: tabs
+ # Choose a comment system to be displayed by default.
+ # Available values: changyan | disqus | disqusjs | gitalk | livere | valine
+ active:
+ # Setting `true` means remembering the comment system selected by the visitor.
+ storage: true
+ # Lazyload all comment systems.
+ lazyload: false
+ # Modify texts or order for any navs, here are some examples.
+ nav:
+ #disqus:
+ # text: Load Disqus
+ # order: -1
+ #gitalk:
+ # order: -2
+
+# Disqus
+disqus:
+ enable: false
+ shortname:
+ count: true
+ #post_meta_order: 0
+
+# DisqusJS
+# Alternative Disqus - Render comment component using Disqus API.
+# Demo: https://suka.js.org/DisqusJS/
+# For more information: https://github.com/SukkaW/DisqusJS
+disqusjs:
+ enable: false
+ # API Endpoint of Disqus API (https://disqus.com/api/).
+ # Leave api empty if you are able to connect to Disqus API. Otherwise you need a reverse proxy for it.
+ # For example:
+ # api: https://disqus.skk.moe/disqus/
+ api:
+ apikey: # Register new application from https://disqus.com/api/applications/
+ shortname: # See: https://disqus.com/admin/settings/general/
+
+# Changyan
+changyan:
+ enable: false
+ appid:
+ appkey:
+ #post_meta_order: 0
+
+# Valine
+# For more information: https://valine.js.org, https://github.com/xCss/Valine
+valine:
+ enable: false
+ appid: # Your leancloud application appid
+ appkey: # Your leancloud application appkey
+ notify: false # Mail notifier
+ verify: false # Verification code
+ placeholder: Just go go # Comment box placeholder
+ avatar: mm # Gravatar style
+ guest_info: nick,mail,link # Custom comment header
+ pageSize: 10 # Pagination size
+ language: # Language, available values: en, zh-cn
+ visitor: false # Article reading statistic
+ comment_count: true # If false, comment count will only be displayed in post page, not in home page
+ recordIP: false # Whether to record the commenter IP
+ serverURLs: # When the custom domain name is enabled, fill it in here (it will be detected automatically by default, no need to fill in)
+ #post_meta_order: 0
+
+# LiveRe comments system
+# You can get your uid from https://livere.com/insight/myCode (General web site)
+livere_uid: #
+
+# Gitalk
+# For more information: https://gitalk.github.io, https://github.com/gitalk/gitalk
+gitalk:
+ enable: false
+ github_id: # GitHub repo owner
+ repo: # Repository name to store issues
+ client_id: # GitHub Application Client ID
+ client_secret: # GitHub Application Client Secret
+ admin_user: # GitHub repo owner and collaborators, only these guys can initialize gitHub issues
+ distraction_free_mode: true # Facebook-like distraction free mode
+ # Gitalk's display language depends on user's browser or system environment
+ # If you want everyone visiting your site to see a uniform language, you can set a force language value
+ # Available values: en | es-ES | fr | ru | zh-CN | zh-TW
+ language:
+
+
+# ---------------------------------------------------------------
+# Post Widgets & Content Sharing Services
+# See: https://theme-next.org/docs/third-party-services/post-widgets
+# ---------------------------------------------------------------
+
+# Star rating support to each article.
+# To get your ID visit https://widgetpack.com
+rating:
+ enable: false
+ id: #
+ color: fc6423
+
+# AddThis Share. See: https://www.addthis.com
+# Go to https://www.addthis.com/dashboard to customize your tools.
+add_this_id:
+
+
+# ---------------------------------------------------------------
+# Statistics and Analytics
+# See: https://theme-next.org/docs/third-party-services/statistics-and-analytics
+# ---------------------------------------------------------------
+
+# Google Analytics
+google_analytics:
+ tracking_id: #
+ # By default, NexT will load an external gtag.js script on your site.
+ # If you only need the pageview feature, set the following option to true to get a better performance.
+ only_pageview: false
+
+# Baidu Analytics
+baidu_analytics: #
+
+# Growingio Analytics
+growingio_analytics: #
+
+# CNZZ count
+cnzz_siteid:
+
+# Show number of visitors of each article.
+# You can visit https://leancloud.cn to get AppID and AppKey.
+# AppID and AppKey are recommended to be the same as valine's for counter compatibility.
+# Do not enable both `valine.visitor` and `leancloud_visitors`.
+leancloud_visitors:
+ enable: false
+ app_id: #
+ app_key: #
+ # Required for apps from CN region
+ server_url: #
+ # Dependencies: https://github.com/theme-next/hexo-leancloud-counter-security
+ # If you don't care about security in leancloud counter and just want to use it directly
+ # (without hexo-leancloud-counter-security plugin), set `security` to `false`.
+ security: true
+
+# Another tool to show number of visitors to each article.
+# Visit https://console.firebase.google.com/u/0/ to get apiKey and projectId.
+# Visit https://firebase.google.com/docs/firestore/ to get more information about firestore.
+firestore:
+ enable: false
+ collection: articles # Required, a string collection name to access firestore database
+ apiKey: # Required
+ projectId: # Required
+
+# Show Views / Visitors of the website / page with busuanzi.
+# Get more information on http://ibruce.info/2015/04/04/busuanzi
+busuanzi_count:
+ enable: false
+ total_visitors: true
+ total_visitors_icon: fa fa-user
+ total_views: true
+ total_views_icon: fa fa-eye
+ post_views: true
+ post_views_icon: fa fa-eye
+
+
+# ---------------------------------------------------------------
+# Search Services
+# See: https://theme-next.org/docs/third-party-services/search-services
+# ---------------------------------------------------------------
+
+# Algolia Search
+# For more information: https://www.algolia.com
+algolia_search:
+ enable: false
+ hits:
+ per_page: 10
+ labels:
+ input_placeholder: Search for Posts
+ hits_empty: "We didn't find any results for the search: ${query}"
+ hits_stats: "${hits} results found in ${time} ms"
+
+# Local Search
+# Dependencies: https://github.com/theme-next/hexo-generator-searchdb
+local_search:
+ enable: false
+ # If auto, trigger search by changing input.
+ # If manual, trigger search by pressing enter key or search button.
+ trigger: auto
+ # Show top n results per article, show all results by setting to -1
+ top_n_per_article: 1
+ # Unescape html strings to the readable one.
+ unescape: false
+ # Preload the search data when the page loads.
+ preload: false
+
+# Swiftype Search API Key
+swiftype_key:
+
+
+# ---------------------------------------------------------------
+# Chat Services
+# See: https://theme-next.org/docs/third-party-services/chat-services
+# ---------------------------------------------------------------
+
+# Chatra Support
+# See: https://chatra.io
+# Dashboard: https://app.chatra.io/settings/general
+chatra:
+ enable: false
+ async: true
+ id: # Visit Dashboard to get your ChatraID
+ #embed: # Unfinished experimental feature for developers. See: https://chatra.io/help/api/#injectto
+
+# Tidio Support
+# See: https://www.tidiochat.com
+# Dashboard: https://www.tidiochat.com/panel/dashboard
+tidio:
+ enable: false
+ key: # Public Key, get it from dashboard. See: https://www.tidiochat.com/panel/settings/developer
+
+
+# ---------------------------------------------------------------
+# Tags Settings
+# See: https://theme-next.org/docs/tag-plugins/
+# ---------------------------------------------------------------
+
+# Note tag (bs-callout)
+note:
+ # Note tag style values:
+ # - simple bs-callout old alert style. Default.
+ # - modern bs-callout new (v2-v3) alert style.
+ # - flat flat callout style with background, like on Mozilla or StackOverflow.
+ # - disabled disable all CSS styles import of note tag.
+ style: simple
+ icons: false
+ # Offset lighter of background in % for modern and flat styles (modern: -12 | 12; flat: -18 | 6).
+ # Offset also applied to label tag variables. This option can work with disabled note tag.
+ light_bg_offset: 0
+
+# Tabs tag
+tabs:
+ transition:
+ tabs: false
+ labels: true
+
+# PDF tag
+# NexT will try to load pdf files natively, if failed, pdf.js will be used.
+# So, you have to install the dependency of pdf.js if you want to use pdf tag and make it available to all browsers.
+# See: https://github.com/theme-next/theme-next-pdf
+pdf:
+ enable: false
+ # Default height
+ height: 500px
+
+# Mermaid tag
+mermaid:
+ enable: false
+ # Available themes: default | dark | forest | neutral
+ theme: forest
+
+
+# ---------------------------------------------------------------
+# Animation Settings
+# ---------------------------------------------------------------
+
+# Use velocity to animate everything.
+# For more information: http://velocityjs.org
+motion:
+ enable: true
+ async: false
+ transition:
+ # Transition variants:
+ # fadeIn | flipXIn | flipYIn | flipBounceXIn | flipBounceYIn
+ # swoopIn | whirlIn | shrinkIn | expandIn
+ # bounceIn | bounceUpIn | bounceDownIn | bounceLeftIn | bounceRightIn
+ # slideUpIn | slideDownIn | slideLeftIn | slideRightIn
+ # slideUpBigIn | slideDownBigIn | slideLeftBigIn | slideRightBigIn
+ # perspectiveUpIn | perspectiveDownIn | perspectiveLeftIn | perspectiveRightIn
+ post_block: fadeIn
+ post_header: slideDownIn
+ post_body: slideDownIn
+ coll_header: slideLeftIn
+ # Only for Pisces | Gemini.
+ sidebar: slideUpIn
+
+# Progress bar in the top during page loading.
+# Dependencies: https://github.com/theme-next/theme-next-pace
+# For more information: https://github.com/HubSpot/pace
+pace:
+ enable: false
+ # Themes list:
+ # big-counter | bounce | barber-shop | center-atom | center-circle | center-radar | center-simple
+ # corner-indicator | fill-left | flat-top | flash | loading-bar | mac-osx | material | minimal
+ theme: minimal
+
+# JavaScript 3D library.
+# Dependencies: https://github.com/theme-next/theme-next-three
+three:
+ enable: false
+ three_waves: false
+ canvas_lines: false
+ canvas_sphere: false
+
+# Canvas-ribbon
+# Dependencies: https://github.com/theme-next/theme-next-canvas-ribbon
+# For more information: https://github.com/zproo/canvas-ribbon
+canvas_ribbon:
+ enable: false
+ size: 300 # The width of the ribbon
+ alpha: 0.6 # The transparency of the ribbon
+ zIndex: -1 # The display level of the ribbon
+
+
+#! ---------------------------------------------------------------
+#! DO NOT EDIT THE FOLLOWING SETTINGS
+#! UNLESS YOU KNOW WHAT YOU ARE DOING
+#! See: https://theme-next.org/docs/advanced-settings
+#! ---------------------------------------------------------------
+
+# Script Vendors. Set a CDN address for the vendor you want to customize.
+# Be aware that you would better use the same version as internal ones to avoid potential problems.
+# Remember to use the https protocol of CDN files when you enable https on your site.
+vendors:
+ # Internal path prefix.
+ _internal: lib
+
+ # Internal version: 3.1.0
+ # anime: //cdn.jsdelivr.net/npm/animejs@3.1.0/lib/anime.min.js
+ anime:
+
+ # Internal version: 5.13.0
+ # fontawesome: //cdn.jsdelivr.net/npm/@fortawesome/fontawesome-free@5/css/all.min.css
+ # fontawesome: //cdnjs.cloudflare.com/ajax/libs/font-awesome/5.13.0/css/all.min.css
+ fontawesome:
+
+ # MathJax
+ # mathjax: //cdn.jsdelivr.net/npm/mathjax@3/es5/tex-mml-chtml.js
+ mathjax:
+
+ # KaTeX
+ # katex: //cdn.jsdelivr.net/npm/katex@0/dist/katex.min.css
+ # katex: //cdnjs.cloudflare.com/ajax/libs/KaTeX/0.11.1/katex.min.css
+ # copy_tex_js: //cdn.jsdelivr.net/npm/katex@0/dist/contrib/copy-tex.min.js
+ # copy_tex_css: //cdn.jsdelivr.net/npm/katex@0/dist/contrib/copy-tex.min.css
+ katex:
+ copy_tex_js:
+ copy_tex_css:
+
+ # Internal version: 0.2.8
+ # pjax: //cdn.jsdelivr.net/gh/theme-next/theme-next-pjax@0/pjax.min.js
+ pjax:
+
+ # FancyBox
+ # jquery: //cdn.jsdelivr.net/npm/jquery@3/dist/jquery.min.js
+ # fancybox: //cdn.jsdelivr.net/gh/fancyapps/fancybox@3/dist/jquery.fancybox.min.js
+ # fancybox_css: //cdn.jsdelivr.net/gh/fancyapps/fancybox@3/dist/jquery.fancybox.min.css
+ jquery:
+ fancybox:
+ fancybox_css:
+
+ # Medium-zoom
+ # mediumzoom: //cdn.jsdelivr.net/npm/medium-zoom@1/dist/medium-zoom.min.js
+ mediumzoom:
+
+ # Lazyload
+ # lazyload: //cdn.jsdelivr.net/npm/lozad@1/dist/lozad.min.js
+ # lazyload: //cdnjs.cloudflare.com/ajax/libs/lozad.js/1.14.0/lozad.min.js
+ lazyload:
+
+ # Pangu
+ # pangu: //cdn.jsdelivr.net/npm/pangu@4/dist/browser/pangu.min.js
+ # pangu: //cdnjs.cloudflare.com/ajax/libs/pangu/4.0.7/pangu.min.js
+ pangu:
+
+ # Quicklink
+ # quicklink: //cdn.jsdelivr.net/npm/quicklink@1/dist/quicklink.umd.js
+ quicklink:
+
+ # DisqusJS
+ # disqusjs_js: //cdn.jsdelivr.net/npm/disqusjs@1/dist/disqus.js
+ # disqusjs_css: //cdn.jsdelivr.net/npm/disqusjs@1/dist/disqusjs.css
+ disqusjs_js:
+ disqusjs_css:
+
+ # Valine
+ # valine: //cdn.jsdelivr.net/npm/valine@1/dist/Valine.min.js
+ # valine: //cdnjs.cloudflare.com/ajax/libs/valine/1.3.10/Valine.min.js
+ valine:
+
+ # Gitalk
+ # gitalk_js: //cdn.jsdelivr.net/npm/gitalk@1/dist/gitalk.min.js
+ # gitalk_css: //cdn.jsdelivr.net/npm/gitalk@1/dist/gitalk.min.css
+ gitalk_js:
+ gitalk_css:
+
+ # Algolia Search
+ # algolia_search: //cdn.jsdelivr.net/npm/algoliasearch@4/dist/algoliasearch-lite.umd.js
+ # instant_search: //cdn.jsdelivr.net/npm/instantsearch.js@4/dist/instantsearch.production.min.js
+ algolia_search:
+ instant_search:
+
+ # Mermaid
+ # mermaid: //cdn.jsdelivr.net/npm/mermaid@8/dist/mermaid.min.js
+ # mermaid: //cdnjs.cloudflare.com/ajax/libs/mermaid/8.4.8/mermaid.min.js
+ mermaid:
+
+ # Internal version: 1.2.1
+ # velocity: //cdn.jsdelivr.net/npm/velocity-animate@1/velocity.min.js
+ # velocity: //cdnjs.cloudflare.com/ajax/libs/velocity/1.2.1/velocity.min.js
+ # velocity_ui: //cdn.jsdelivr.net/npm/velocity-animate@1/velocity.ui.min.js
+ # velocity_ui: //cdnjs.cloudflare.com/ajax/libs/velocity/1.2.1/velocity.ui.min.js
+ velocity:
+ velocity_ui:
+
+ # Internal version: 1.0.2
+ # pace: //cdn.jsdelivr.net/npm/pace-js@1/pace.min.js
+ # pace: //cdnjs.cloudflare.com/ajax/libs/pace/1.0.2/pace.min.js
+ # pace_css: //cdn.jsdelivr.net/npm/pace-js@1/themes/blue/pace-theme-minimal.css
+ # pace_css: //cdnjs.cloudflare.com/ajax/libs/pace/1.0.2/themes/blue/pace-theme-minimal.min.css
+ pace:
+ pace_css:
+
+ # Internal version: 1.0.0
+ # three: //cdn.jsdelivr.net/gh/theme-next/theme-next-three@1/three.min.js
+ # three_waves: //cdn.jsdelivr.net/gh/theme-next/theme-next-three@1/three-waves.min.js
+ # canvas_lines: //cdn.jsdelivr.net/gh/theme-next/theme-next-three@1/canvas_lines.min.js
+ # canvas_sphere: //cdn.jsdelivr.net/gh/theme-next/theme-next-three@1/canvas_sphere.min.js
+ three:
+ three_waves:
+ canvas_lines:
+ canvas_sphere:
+
+ # Internal version: 1.0.0
+ # canvas_ribbon: //cdn.jsdelivr.net/gh/theme-next/theme-next-canvas-ribbon@1/canvas-ribbon.js
+ canvas_ribbon:
+
+# Assets
+css: css
+js: js
+images: images
diff --git a/themes/next/crowdin.yml b/themes/next/crowdin.yml
new file mode 100644
index 0000000..be97306
--- /dev/null
+++ b/themes/next/crowdin.yml
@@ -0,0 +1,9 @@
+files:
+ - source: /languages/en.yml
+ translation: /languages/%two_letters_code%.%file_extension%
+ languages_mapping:
+ two_letters_code:
+ zh-CN: zh-CN
+ zh-TW: zh-TW
+ zh-HK: zh-HK
+ pt-BR: pt-BR
diff --git a/themes/next/docs/AGPL3.md b/themes/next/docs/AGPL3.md
new file mode 100644
index 0000000..2dcf18c
--- /dev/null
+++ b/themes/next/docs/AGPL3.md
@@ -0,0 +1,649 @@
+#
Everyone is permitted to copy and distribute verbatim copies
+of this license document, but changing it is not allowed.
+
+##
Preamble
+
+The GNU Affero General Public License is a free, copyleft license for
+software and other kinds of works, specifically designed to ensure
+cooperation with the community in the case of network server software.
+
+The licenses for most software and other practical works are designed
+to take away your freedom to share and change the works. By contrast,
+our General Public Licenses are intended to guarantee your freedom to
+share and change all versions of a program--to make sure it remains free
+software for all its users.
+
+When we speak of free software, we are referring to freedom, not
+price. Our General Public Licenses are designed to make sure that you
+have the freedom to distribute copies of free software (and charge for
+them if you wish), that you receive source code or can get it if you
+want it, that you can change the software or use pieces of it in new
+free programs, and that you know you can do these things.
+
+Developers that use our General Public Licenses protect your rights
+with two steps: **(1)** assert copyright on the software, and **(2)** offer
+you this License which gives you legal permission to copy, distribute
+and/or modify the software.
+
+A secondary benefit of defending all users' freedom is that
+improvements made in alternate versions of the program, if they
+receive widespread use, become available for other developers to
+incorporate. Many developers of free software are heartened and
+encouraged by the resulting cooperation. However, in the case of
+software used on network servers, this result may fail to come about.
+The GNU General Public License permits making a modified version and
+letting the public access it on a server without ever releasing its
+source code to the public.
+
+The GNU Affero General Public License is designed specifically to
+ensure that, in such cases, the modified source code becomes available
+to the community. It requires the operator of a network server to
+provide the source code of the modified version running there to the
+users of that server. Therefore, public use of a modified version, on
+a publicly accessible server, gives the public access to the source
+code of the modified version.
+
+An older license, called the Affero General Public License and
+published by Affero, was designed to accomplish similar goals. This is
+a different license, not a version of the Affero GPL, but Affero has
+released a new version of the Affero GPL which permits relicensing under
+this license.
+
+The precise terms and conditions for copying, distribution and
+modification follow.
+
+##
TERMS AND CONDITIONS
+
+### 0. Definitions
+
+“This License” refers to version 3 of the GNU Affero General Public License.
+
+“Copyright” also means copyright-like laws that apply to other kinds of
+works, such as semiconductor masks.
+
+“The Program” refers to any copyrightable work licensed under this
+License. Each licensee is addressed as “you”. “Licensees” and
+“recipients” may be individuals or organizations.
+
+To “modify” a work means to copy from or adapt all or part of the work
+in a fashion requiring copyright permission, other than the making of an
+exact copy. The resulting work is called a “modified version” of the
+earlier work or a work “based on” the earlier work.
+
+A “covered work” means either the unmodified Program or a work based
+on the Program.
+
+To “propagate” a work means to do anything with it that, without
+permission, would make you directly or secondarily liable for
+infringement under applicable copyright law, except executing it on a
+computer or modifying a private copy. Propagation includes copying,
+distribution (with or without modification), making available to the
+public, and in some countries other activities as well.
+
+To “convey” a work means any kind of propagation that enables other
+parties to make or receive copies. Mere interaction with a user through
+a computer network, with no transfer of a copy, is not conveying.
+
+An interactive user interface displays “Appropriate Legal Notices”
+to the extent that it includes a convenient and prominently visible
+feature that **(1)** displays an appropriate copyright notice, and **(2)**
+tells the user that there is no warranty for the work (except to the
+extent that warranties are provided), that licensees may convey the
+work under this License, and how to view a copy of this License. If
+the interface presents a list of user commands or options, such as a
+menu, a prominent item in the list meets this criterion.
+
+### 1. Source Code
+
+The “source code” for a work means the preferred form of the work
+for making modifications to it. “Object code” means any non-source
+form of a work.
+
+A “Standard Interface” means an interface that either is an official
+standard defined by a recognized standards body, or, in the case of
+interfaces specified for a particular programming language, one that
+is widely used among developers working in that language.
+
+The “System Libraries” of an executable work include anything, other
+than the work as a whole, that **(a)** is included in the normal form of
+packaging a Major Component, but which is not part of that Major
+Component, and **(b)** serves only to enable use of the work with that
+Major Component, or to implement a Standard Interface for which an
+implementation is available to the public in source code form. A
+“Major Component”, in this context, means a major essential component
+(kernel, window system, and so on) of the specific operating system
+(if any) on which the executable work runs, or a compiler used to
+produce the work, or an object code interpreter used to run it.
+
+The “Corresponding Source” for a work in object code form means all
+the source code needed to generate, install, and (for an executable
+work) run the object code and to modify the work, including scripts to
+control those activities. However, it does not include the work's
+System Libraries, or general-purpose tools or generally available free
+programs which are used unmodified in performing those activities but
+which are not part of the work. For example, Corresponding Source
+includes interface definition files associated with source files for
+the work, and the source code for shared libraries and dynamically
+linked subprograms that the work is specifically designed to require,
+such as by intimate data communication or control flow between those
+subprograms and other parts of the work.
+
+The Corresponding Source need not include anything that users
+can regenerate automatically from other parts of the Corresponding
+Source.
+
+The Corresponding Source for a work in source code form is that
+same work.
+
+### 2. Basic Permissions
+
+All rights granted under this License are granted for the term of
+copyright on the Program, and are irrevocable provided the stated
+conditions are met. This License explicitly affirms your unlimited
+permission to run the unmodified Program. The output from running a
+covered work is covered by this License only if the output, given its
+content, constitutes a covered work. This License acknowledges your
+rights of fair use or other equivalent, as provided by copyright law.
+
+You may make, run and propagate covered works that you do not
+convey, without conditions so long as your license otherwise remains
+in force. You may convey covered works to others for the sole purpose
+of having them make modifications exclusively for you, or provide you
+with facilities for running those works, provided that you comply with
+the terms of this License in conveying all material for which you do
+not control copyright. Those thus making or running the covered works
+for you must do so exclusively on your behalf, under your direction
+and control, on terms that prohibit them from making any copies of
+your copyrighted material outside their relationship with you.
+
+Conveying under any other circumstances is permitted solely under
+the conditions stated below. Sublicensing is not allowed; section 10
+makes it unnecessary.
+
+### 3. Protecting Users' Legal Rights From Anti-Circumvention Law
+
+No covered work shall be deemed part of an effective technological
+measure under any applicable law fulfilling obligations under article
+11 of the WIPO copyright treaty adopted on 20 December 1996, or
+similar laws prohibiting or restricting circumvention of such
+measures.
+
+When you convey a covered work, you waive any legal power to forbid
+circumvention of technological measures to the extent such circumvention
+is effected by exercising rights under this License with respect to
+the covered work, and you disclaim any intention to limit operation or
+modification of the work as a means of enforcing, against the work's
+users, your or third parties' legal rights to forbid circumvention of
+technological measures.
+
+### 4. Conveying Verbatim Copies
+
+You may convey verbatim copies of the Program's source code as you
+receive it, in any medium, provided that you conspicuously and
+appropriately publish on each copy an appropriate copyright notice;
+keep intact all notices stating that this License and any
+non-permissive terms added in accord with section 7 apply to the code;
+keep intact all notices of the absence of any warranty; and give all
+recipients a copy of this License along with the Program.
+
+You may charge any price or no price for each copy that you convey,
+and you may offer support or warranty protection for a fee.
+
+### 5. Conveying Modified Source Versions
+
+You may convey a work based on the Program, or the modifications to
+produce it from the Program, in the form of source code under the
+terms of section 4, provided that you also meet all of these conditions:
+
+* **a)** The work must carry prominent notices stating that you modified
+it, and giving a relevant date.
+* **b)** The work must carry prominent notices stating that it is
+released under this License and any conditions added under section 7.
+This requirement modifies the requirement in section 4 to
+“keep intact all notices”.
+* **c)** You must license the entire work, as a whole, under this
+License to anyone who comes into possession of a copy. This
+License will therefore apply, along with any applicable section 7
+additional terms, to the whole of the work, and all its parts,
+regardless of how they are packaged. This License gives no
+permission to license the work in any other way, but it does not
+invalidate such permission if you have separately received it.
+* **d)** If the work has interactive user interfaces, each must display
+Appropriate Legal Notices; however, if the Program has interactive
+interfaces that do not display Appropriate Legal Notices, your
+work need not make them do so.
+
+A compilation of a covered work with other separate and independent
+works, which are not by their nature extensions of the covered work,
+and which are not combined with it such as to form a larger program,
+in or on a volume of a storage or distribution medium, is called an
+“aggregate” if the compilation and its resulting copyright are not
+used to limit the access or legal rights of the compilation's users
+beyond what the individual works permit. Inclusion of a covered work
+in an aggregate does not cause this License to apply to the other
+parts of the aggregate.
+
+### 6. Conveying Non-Source Forms
+
+You may convey a covered work in object code form under the terms
+of sections 4 and 5, provided that you also convey the
+machine-readable Corresponding Source under the terms of this License,
+in one of these ways:
+
+* **a)** Convey the object code in, or embodied in, a physical product
+(including a physical distribution medium), accompanied by the
+Corresponding Source fixed on a durable physical medium
+customarily used for software interchange.
+* **b)** Convey the object code in, or embodied in, a physical product
+(including a physical distribution medium), accompanied by a
+written offer, valid for at least three years and valid for as
+long as you offer spare parts or customer support for that product
+model, to give anyone who possesses the object code either **(1)** a
+copy of the Corresponding Source for all the software in the
+product that is covered by this License, on a durable physical
+medium customarily used for software interchange, for a price no
+more than your reasonable cost of physically performing this
+conveying of source, or **(2)** access to copy the
+Corresponding Source from a network server at no charge.
+* **c)** Convey individual copies of the object code with a copy of the
+written offer to provide the Corresponding Source. This
+alternative is allowed only occasionally and noncommercially, and
+only if you received the object code with such an offer, in accord
+with subsection 6b.
+* **d)** Convey the object code by offering access from a designated
+place (gratis or for a charge), and offer equivalent access to the
+Corresponding Source in the same way through the same place at no
+further charge. You need not require recipients to copy the
+Corresponding Source along with the object code. If the place to
+copy the object code is a network server, the Corresponding Source
+may be on a different server (operated by you or a third party)
+that supports equivalent copying facilities, provided you maintain
+clear directions next to the object code saying where to find the
+Corresponding Source. Regardless of what server hosts the
+Corresponding Source, you remain obligated to ensure that it is
+available for as long as needed to satisfy these requirements.
+* **e)** Convey the object code using peer-to-peer transmission, provided
+you inform other peers where the object code and Corresponding
+Source of the work are being offered to the general public at no
+charge under subsection 6d.
+
+A separable portion of the object code, whose source code is excluded
+from the Corresponding Source as a System Library, need not be
+included in conveying the object code work.
+
+A “User Product” is either **(1)** a “consumer product”, which means any
+tangible personal property which is normally used for personal, family,
+or household purposes, or **(2)** anything designed or sold for incorporation
+into a dwelling. In determining whether a product is a consumer product,
+doubtful cases shall be resolved in favor of coverage. For a particular
+product received by a particular user, “normally used” refers to a
+typical or common use of that class of product, regardless of the status
+of the particular user or of the way in which the particular user
+actually uses, or expects or is expected to use, the product. A product
+is a consumer product regardless of whether the product has substantial
+commercial, industrial or non-consumer uses, unless such uses represent
+the only significant mode of use of the product.
+
+“Installation Information” for a User Product means any methods,
+procedures, authorization keys, or other information required to install
+and execute modified versions of a covered work in that User Product from
+a modified version of its Corresponding Source. The information must
+suffice to ensure that the continued functioning of the modified object
+code is in no case prevented or interfered with solely because
+modification has been made.
+
+If you convey an object code work under this section in, or with, or
+specifically for use in, a User Product, and the conveying occurs as
+part of a transaction in which the right of possession and use of the
+User Product is transferred to the recipient in perpetuity or for a
+fixed term (regardless of how the transaction is characterized), the
+Corresponding Source conveyed under this section must be accompanied
+by the Installation Information. But this requirement does not apply
+if neither you nor any third party retains the ability to install
+modified object code on the User Product (for example, the work has
+been installed in ROM).
+
+The requirement to provide Installation Information does not include a
+requirement to continue to provide support service, warranty, or updates
+for a work that has been modified or installed by the recipient, or for
+the User Product in which it has been modified or installed. Access to a
+network may be denied when the modification itself materially and
+adversely affects the operation of the network or violates the rules and
+protocols for communication across the network.
+
+Corresponding Source conveyed, and Installation Information provided,
+in accord with this section must be in a format that is publicly
+documented (and with an implementation available to the public in
+source code form), and must require no special password or key for
+unpacking, reading or copying.
+
+### 7. Additional Terms
+
+“Additional permissions” are terms that supplement the terms of this
+License by making exceptions from one or more of its conditions.
+Additional permissions that are applicable to the entire Program shall
+be treated as though they were included in this License, to the extent
+that they are valid under applicable law. If additional permissions
+apply only to part of the Program, that part may be used separately
+under those permissions, but the entire Program remains governed by
+this License without regard to the additional permissions.
+
+When you convey a copy of a covered work, you may at your option
+remove any additional permissions from that copy, or from any part of
+it. (Additional permissions may be written to require their own
+removal in certain cases when you modify the work.) You may place
+additional permissions on material, added by you to a covered work,
+for which you have or can give appropriate copyright permission.
+
+Notwithstanding any other provision of this License, for material you
+add to a covered work, you may (if authorized by the copyright holders of
+that material) supplement the terms of this License with terms:
+
+* **a)** Disclaiming warranty or limiting liability differently from the
+terms of sections 15 and 16 of this License; or
+* **b)** Requiring preservation of specified reasonable legal notices or
+author attributions in that material or in the Appropriate Legal
+Notices displayed by works containing it; or
+* **c)** Prohibiting misrepresentation of the origin of that material, or
+requiring that modified versions of such material be marked in
+reasonable ways as different from the original version; or
+* **d)** Limiting the use for publicity purposes of names of licensors or
+authors of the material; or
+* **e)** Declining to grant rights under trademark law for use of some
+trade names, trademarks, or service marks; or
+* **f)** Requiring indemnification of licensors and authors of that
+material by anyone who conveys the material (or modified versions of
+it) with contractual assumptions of liability to the recipient, for
+any liability that these contractual assumptions directly impose on
+those licensors and authors.
+
+All other non-permissive additional terms are considered “further
+restrictions” within the meaning of section 10. If the Program as you
+received it, or any part of it, contains a notice stating that it is
+governed by this License along with a term that is a further
+restriction, you may remove that term. If a license document contains
+a further restriction but permits relicensing or conveying under this
+License, you may add to a covered work material governed by the terms
+of that license document, provided that the further restriction does
+not survive such relicensing or conveying.
+
+If you add terms to a covered work in accord with this section, you
+must place, in the relevant source files, a statement of the
+additional terms that apply to those files, or a notice indicating
+where to find the applicable terms.
+
+Additional terms, permissive or non-permissive, may be stated in the
+form of a separately written license, or stated as exceptions;
+the above requirements apply either way.
+
+### 8. Termination
+
+You may not propagate or modify a covered work except as expressly
+provided under this License. Any attempt otherwise to propagate or
+modify it is void, and will automatically terminate your rights under
+this License (including any patent licenses granted under the third
+paragraph of section 11).
+
+However, if you cease all violation of this License, then your
+license from a particular copyright holder is reinstated **(a)**
+provisionally, unless and until the copyright holder explicitly and
+finally terminates your license, and **(b)** permanently, if the copyright
+holder fails to notify you of the violation by some reasonable means
+prior to 60 days after the cessation.
+
+Moreover, your license from a particular copyright holder is
+reinstated permanently if the copyright holder notifies you of the
+violation by some reasonable means, this is the first time you have
+received notice of violation of this License (for any work) from that
+copyright holder, and you cure the violation prior to 30 days after
+your receipt of the notice.
+
+Termination of your rights under this section does not terminate the
+licenses of parties who have received copies or rights from you under
+this License. If your rights have been terminated and not permanently
+reinstated, you do not qualify to receive new licenses for the same
+material under section 10.
+
+### 9. Acceptance Not Required for Having Copies
+
+You are not required to accept this License in order to receive or
+run a copy of the Program. Ancillary propagation of a covered work
+occurring solely as a consequence of using peer-to-peer transmission
+to receive a copy likewise does not require acceptance. However,
+nothing other than this License grants you permission to propagate or
+modify any covered work. These actions infringe copyright if you do
+not accept this License. Therefore, by modifying or propagating a
+covered work, you indicate your acceptance of this License to do so.
+
+### 10. Automatic Licensing of Downstream Recipients
+
+Each time you convey a covered work, the recipient automatically
+receives a license from the original licensors, to run, modify and
+propagate that work, subject to this License. You are not responsible
+for enforcing compliance by third parties with this License.
+
+An “entity transaction” is a transaction transferring control of an
+organization, or substantially all assets of one, or subdividing an
+organization, or merging organizations. If propagation of a covered
+work results from an entity transaction, each party to that
+transaction who receives a copy of the work also receives whatever
+licenses to the work the party's predecessor in interest had or could
+give under the previous paragraph, plus a right to possession of the
+Corresponding Source of the work from the predecessor in interest, if
+the predecessor has it or can get it with reasonable efforts.
+
+You may not impose any further restrictions on the exercise of the
+rights granted or affirmed under this License. For example, you may
+not impose a license fee, royalty, or other charge for exercise of
+rights granted under this License, and you may not initiate litigation
+(including a cross-claim or counterclaim in a lawsuit) alleging that
+any patent claim is infringed by making, using, selling, offering for
+sale, or importing the Program or any portion of it.
+
+### 11. Patents
+
+A “contributor” is a copyright holder who authorizes use under this
+License of the Program or a work on which the Program is based. The
+work thus licensed is called the contributor's “contributor version”.
+
+A contributor's “essential patent claims” are all patent claims
+owned or controlled by the contributor, whether already acquired or
+hereafter acquired, that would be infringed by some manner, permitted
+by this License, of making, using, or selling its contributor version,
+but do not include claims that would be infringed only as a
+consequence of further modification of the contributor version. For
+purposes of this definition, “control” includes the right to grant
+patent sublicenses in a manner consistent with the requirements of
+this License.
+
+Each contributor grants you a non-exclusive, worldwide, royalty-free
+patent license under the contributor's essential patent claims, to
+make, use, sell, offer for sale, import and otherwise run, modify and
+propagate the contents of its contributor version.
+
+In the following three paragraphs, a “patent license” is any express
+agreement or commitment, however denominated, not to enforce a patent
+(such as an express permission to practice a patent or covenant not to
+sue for patent infringement). To “grant” such a patent license to a
+party means to make such an agreement or commitment not to enforce a
+patent against the party.
+
+If you convey a covered work, knowingly relying on a patent license,
+and the Corresponding Source of the work is not available for anyone
+to copy, free of charge and under the terms of this License, through a
+publicly available network server or other readily accessible means,
+then you must either **(1)** cause the Corresponding Source to be so
+available, or **(2)** arrange to deprive yourself of the benefit of the
+patent license for this particular work, or **(3)** arrange, in a manner
+consistent with the requirements of this License, to extend the patent
+license to downstream recipients. “Knowingly relying” means you have
+actual knowledge that, but for the patent license, your conveying the
+covered work in a country, or your recipient's use of the covered work
+in a country, would infringe one or more identifiable patents in that
+country that you have reason to believe are valid.
+
+If, pursuant to or in connection with a single transaction or
+arrangement, you convey, or propagate by procuring conveyance of, a
+covered work, and grant a patent license to some of the parties
+receiving the covered work authorizing them to use, propagate, modify
+or convey a specific copy of the covered work, then the patent license
+you grant is automatically extended to all recipients of the covered
+work and works based on it.
+
+A patent license is “discriminatory” if it does not include within
+the scope of its coverage, prohibits the exercise of, or is
+conditioned on the non-exercise of one or more of the rights that are
+specifically granted under this License. You may not convey a covered
+work if you are a party to an arrangement with a third party that is
+in the business of distributing software, under which you make payment
+to the third party based on the extent of your activity of conveying
+the work, and under which the third party grants, to any of the
+parties who would receive the covered work from you, a discriminatory
+patent license **(a)** in connection with copies of the covered work
+conveyed by you (or copies made from those copies), or **(b)** primarily
+for and in connection with specific products or compilations that
+contain the covered work, unless you entered into that arrangement,
+or that patent license was granted, prior to 28 March 2007.
+
+Nothing in this License shall be construed as excluding or limiting
+any implied license or other defenses to infringement that may
+otherwise be available to you under applicable patent law.
+
+### 12. No Surrender of Others' Freedom
+
+If conditions are imposed on you (whether by court order, agreement or
+otherwise) that contradict the conditions of this License, they do not
+excuse you from the conditions of this License. If you cannot convey a
+covered work so as to satisfy simultaneously your obligations under this
+License and any other pertinent obligations, then as a consequence you may
+not convey it at all. For example, if you agree to terms that obligate you
+to collect a royalty for further conveying from those to whom you convey
+the Program, the only way you could satisfy both those terms and this
+License would be to refrain entirely from conveying the Program.
+
+### 13. Remote Network Interaction; Use with the GNU General Public License
+
+Notwithstanding any other provision of this License, if you modify the
+Program, your modified version must prominently offer all users
+interacting with it remotely through a computer network (if your version
+supports such interaction) an opportunity to receive the Corresponding
+Source of your version by providing access to the Corresponding Source
+from a network server at no charge, through some standard or customary
+means of facilitating copying of software. This Corresponding Source
+shall include the Corresponding Source for any work covered by version 3
+of the GNU General Public License that is incorporated pursuant to the
+following paragraph.
+
+Notwithstanding any other provision of this License, you have
+permission to link or combine any covered work with a work licensed
+under version 3 of the GNU General Public License into a single
+combined work, and to convey the resulting work. The terms of this
+License will continue to apply to the part which is the covered work,
+but the work with which it is combined will remain governed by version
+3 of the GNU General Public License.
+
+### 14. Revised Versions of this License
+
+The Free Software Foundation may publish revised and/or new versions of
+the GNU Affero General Public License from time to time. Such new versions
+will be similar in spirit to the present version, but may differ in detail to
+address new problems or concerns.
+
+Each version is given a distinguishing version number. If the
+Program specifies that a certain numbered version of the GNU Affero General
+Public License “or any later version” applies to it, you have the
+option of following the terms and conditions either of that numbered
+version or of any later version published by the Free Software
+Foundation. If the Program does not specify a version number of the
+GNU Affero General Public License, you may choose any version ever published
+by the Free Software Foundation.
+
+If the Program specifies that a proxy can decide which future
+versions of the GNU Affero General Public License can be used, that proxy's
+public statement of acceptance of a version permanently authorizes you
+to choose that version for the Program.
+
+Later license versions may give you additional or different
+permissions. However, no additional obligations are imposed on any
+author or copyright holder as a result of your choosing to follow a
+later version.
+
+### 15. Disclaimer of Warranty
+
+THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY
+APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT
+HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM “AS IS” WITHOUT WARRANTY
+OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO,
+THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
+PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM
+IS WITH YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF
+ALL NECESSARY SERVICING, REPAIR OR CORRECTION.
+
+### 16. Limitation of Liability
+
+IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING
+WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MODIFIES AND/OR CONVEYS
+THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY
+GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE
+USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF
+DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD
+PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS),
+EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF
+SUCH DAMAGES.
+
+### 17. Interpretation of Sections 15 and 16
+
+If the disclaimer of warranty and limitation of liability provided
+above cannot be given local legal effect according to their terms,
+reviewing courts shall apply local law that most closely approximates
+an absolute waiver of all civil liability in connection with the
+Program, unless a warranty or assumption of liability accompanies a
+copy of the Program in return for a fee.
+
+##
END OF TERMS AND CONDITIONS
+
+###
How to Apply These Terms to Your New Programs
+
+If you develop a new program, and you want it to be of the greatest
+possible use to the public, the best way to achieve this is to make it
+free software which everyone can redistribute and change under these terms.
+
+To do so, attach the following notices to the program. It is safest
+to attach them to the start of each source file to most effectively
+state the exclusion of warranty; and each file should have at least
+the “copyright” line and a pointer to where the full notice is found.
+
+
+ Copyright (C)
+
+ This program is free software: you can redistribute it and/or modify
+ it under the terms of the GNU Affero General Public License as published by
+ the Free Software Foundation, either version 3 of the License, or
+ (at your option) any later version.
+
+ This program is distributed in the hope that it will be useful,
+ but WITHOUT ANY WARRANTY; without even the implied warranty of
+ MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
+ GNU Affero General Public License for more details.
+
+ You should have received a copy of the GNU Affero General Public License
+ along with this program. If not, see .
+
+Also add information on how to contact you by electronic and paper mail.
+
+If your software can interact with users remotely through a computer
+network, you should also make sure that it provides a way for users to
+get its source. For example, if your program is a web application, its
+interface could display a “Source” link that leads users to an archive
+of the code. There are many ways you could offer source, and different
+solutions will be better for different programs; see section 13 for the
+specific requirements.
+
+You should also get your employer (if you work as a programmer) or school,
+if any, to sign a “copyright disclaimer” for the program, if necessary.
+For more information on this, and how to apply and follow the GNU AGPL, see
+<>.
\ No newline at end of file
diff --git a/themes/next/docs/ALGOLIA-SEARCH.md b/themes/next/docs/ALGOLIA-SEARCH.md
new file mode 100644
index 0000000..bdc8ab6
--- /dev/null
+++ b/themes/next/docs/ALGOLIA-SEARCH.md
@@ -0,0 +1,82 @@
+
Algolia Search
+
+NexT provides Algolia search plugin for index your hexo website content. To use this feature, make sure that the version of NexT you are using is after the v5.1.0 release. What you should note here is that only turn on `enable` of `algolia_search` in `next/_config.yml` cannot let you use the algolia search correctly, you need to install corresponding [Hexo Algolia](https://github.com/oncletom/hexo-algolia) plugin to seach your website with Algolia. Follow the steps described below to complete the installation of Algolia search.
+
+1. Register at [Algolia](https://www.algolia.com/), you can log in directly using GitHub or Google Account. Upon Customer’s initial sign-up for an Account, Customer will have a free, fourteen (14) day evaluation period (the “Evaluation Period”) for the Algolia Services commencing on the Effective Date, subject to the limitations on Algolia’s website. After that, Algolia offers a free, branded version for up to 10k records and 100k operations per month.
+
+1. If a tutorial pops up, you can skip it. Go straight to create an `Index` which will be used later.
+
+ 
+
+1. Go to the `API Keys` page and find your credentials. You will need the `Application ID` and the `Search-only API key` in the following sections. The `Admin API key` need to keep confidential. Never store your Admin API Key as apiKey in the` _config.yml` file: it would give full control of your Algolia index to others and you don't want to face the consequences.
+
+ 
+
+1. In your site's `_config.yml`, add the following configuration and replace the `applicationID` & `apiKey` & `indexName` with corresponding fields obtained at Algolia.
+
+ ```yml
+ algolia:
+ applicationID: 'Application ID'
+ apiKey: 'Search-only API key'
+ indexName: 'indexName'
+ chunkSize: 5000
+ ```
+
+1. In the `API Keys` page, click the `All API Keys` button to switch to the corresponding tab. Then click the `New API Key` button to activate a pop-up box where you can setup authorizations and restrictions with a great level of precision. Enter `addObject`, `deleteObject`, `listIndexes`, `deleteIndex` features in ACL permissions that will be allowed for the given API key. And then click the `Create` button. Copy this newly created key to the clipboard, we call it a `High-privilege API key`.
+
+ 
+ 
+
+1. Algolia requires users to upload their search index data either manually or via provided APIs. Install and configure [Hexo Algolia](https://github.com/oncletom/hexo-algolia) in your Hexo directory. This plugin will index your site and upload selected data to Algolia.
+
+ ```
+ $ cd hexo
+ $ npm install hexo-algolia
+ ```
+
+1. Run the following command to upload index data, keep a weather eye out the output of the command.
+
+ ```
+ $ export HEXO_ALGOLIA_INDEXING_KEY=High-privilege API key # Use Git Bash
+ # set HEXO_ALGOLIA_INDEXING_KEY=High-privilege API key # Use Windows command line
+ $ hexo clean
+ $ hexo algolia
+ ```
+
+ 
+
+1. In `next/_config.yml`, turn on `enable` of `algolia_search`. At the same time, you need to **turn off other search plugins** like Local Search. You can also adjust the text in `labels` according to your needs.
+
+ ```yml
+ # Algolia Search
+ algolia_search:
+ enable: true
+ hits:
+ per_page: 10
+ labels:
+ input_placeholder: Search for Posts
+ hits_empty: "We didn't find any results for the search: ${query}"
+ hits_stats: "${hits} results found in ${time} ms"
+ ```
+
+1. If you want to use a different version from CDN, please follow the instructions below.
+
+ You need to **set vendors** in NexT `_config.yml` file:
+ ```yml
+ vendors:
+ ...
+ # Algolia Search
+ # algolia_search: //cdn.jsdelivr.net/npm/algoliasearch@4/dist/algoliasearch-lite.umd.js
+ # instant_search: //cdn.jsdelivr.net/npm/instantsearch.js@4/dist/instantsearch.production.min.js
+ algolia_search: //cdn.jsdelivr.net/npm/algoliasearch@4/dist/algoliasearch-lite.umd.js
+ instant_search: //cdn.jsdelivr.net/npm/instantsearch.js@4/dist/instantsearch.production.min.js
+ ...
+ ```
+
+
Known Issues
+
+1. The latest version of the [Hexo-Algolia](https://github.com/oncletom/hexo-algolia) plugin removes the content indexing feature, given Algolia's free account limitation.
+
+1. The [Hexo-Algoliasearch](https://github.com/LouisBarranqueiro/hexo-algoliasearch) plugin provides content indexing functionality, but requires the replacement of keywords in the NEXT theme. The same problem exists with `Record Too Big` for Algolia's free account.
+ - Replace all `applicationID` in `source/js/algolia-search.js` with `appId`
+ - Replace all `applicationID` in `layout/_partials/head/head.swig` with `appId`
diff --git a/themes/next/docs/AUTHORS.md b/themes/next/docs/AUTHORS.md
new file mode 100644
index 0000000..078740a
--- /dev/null
+++ b/themes/next/docs/AUTHORS.md
@@ -0,0 +1,87 @@
+#
«NexT» Authors
+
+NexT theme was initially developed by:
+
+- **IIssNaN**: [NexT](https://github.com/iissnan/hexo-theme-next) (2014 - 2017)
+
+With collaborators from initially repository:
+
+- **Ivan.Nginx**: [DIFF highlight](https://github.com/iissnan/hexo-theme-next/pull/1079),
+ [HyperComments](https://github.com/iissnan/hexo-theme-next/pull/1155),
+ [`{% note %}` tag](https://github.com/iissnan/hexo-theme-next/pull/1160),
+ [`seo` option](https://github.com/iissnan/hexo-theme-next/pull/1311),
+ [`{% button %}` tag](https://github.com/iissnan/hexo-theme-next/pull/1328),
+ [VK API](https://github.com/iissnan/hexo-theme-next/pull/1381),
+ [WordCount plugin support](https://github.com/iissnan/hexo-theme-next/pull/1381),
+ [Yandex verification option](https://github.com/iissnan/hexo-theme-next/pull/1381),
+ [`{% exturl %}` tag](https://github.com/iissnan/hexo-theme-next/pull/1438),
+ [`b2t` option](https://github.com/iissnan/hexo-theme-next/pull/1438),
+ [`scrollpercent` option](https://github.com/iissnan/hexo-theme-next/pull/1438),
+ [`save_scroll` option](https://github.com/iissnan/hexo-theme-next/pull/1574),
+ [Star rating](https://github.com/iissnan/hexo-theme-next/pull/1649),
+ [`mobile_layout_economy` option](https://github.com/iissnan/hexo-theme-next/pull/1697),
+ [`{% tabs %}` tag](https://github.com/iissnan/hexo-theme-next/pull/1697),
+ [`{% label %}` tag](https://github.com/iissnan/hexo-theme-next/pull/1697),
+ [**`Gemini`** scheme](https://github.com/iissnan/hexo-theme-next/pull/1697),
+ [Menu & Sidebar icons in 1 line](https://github.com/iissnan/hexo-theme-next/pull/1830),
+ [Sidebar scrollable](https://github.com/iissnan/hexo-theme-next/pull/1898),
+ [Responsive favicons](https://github.com/iissnan/hexo-theme-next/pull/1898)
+ and many other [PR's with fixes and enhancements](https://github.com/iissnan/hexo-theme-next/pulls?utf8=%E2%9C%93&q=is%3Apr%20author%3Aivan-nginx)
+- **Acris**: [Many PR's with fixes and updates](https://github.com/iissnan/hexo-theme-next/pulls?utf8=%E2%9C%93&q=is%3Apr%20author%3AAcris)
+
+And best contributors from initially repository:
+
+- **Rainy**: [Gentie comments](https://github.com/iissnan/hexo-theme-next/pull/1301),
+ [Han](https://github.com/iissnan/hexo-theme-next/pull/1598)
+ and many [PR's with fixes and optimizations](https://github.com/iissnan/hexo-theme-next/pulls?utf8=%E2%9C%93&q=is%3Apr%20author%3Ageekrainy)
+- **Jeff**: [Local search](https://github.com/iissnan/hexo-theme-next/pull/694)
+ and many [PR's with fixes and improvements](https://github.com/iissnan/hexo-theme-next/pulls?utf8=%E2%9C%93&q=is%3Apr%20author%3Aflashlab)
+- **Haocen**: [Footer enhancements](https://github.com/iissnan/hexo-theme-next/pull/1886)
+ and some other [PR's with improvements](https://github.com/iissnan/hexo-theme-next/pulls?utf8=%E2%9C%93&q=is%3Apr%20author%3AHaocen)
+- **uchuhimo**: [Greatest enhancements for local search](https://github.com/iissnan/hexo-theme-next/pulls?utf8=%E2%9C%93&q=is%3Apr%20author%3Auchuhimo)
+- **Kei**: [Change static file setting to support subdirectory](https://github.com/iissnan/hexo-theme-next/pull/4)
+- **Jolyon**: [Swiftype](https://github.com/iissnan/hexo-theme-next/pull/84)
+- **xirong**: [404 page](https://github.com/iissnan/hexo-theme-next/pull/126)
+- **PinkyJie**: [Fix Swiftype](https://github.com/iissnan/hexo-theme-next/pull/132)
+- **Tim Kuijsten**: [Split javascript into separate files](https://github.com/iissnan/hexo-theme-next/pull/152)
+- **iamwent**: [Friendly links](https://github.com/iissnan/hexo-theme-next/pull/250)
+- **arao lin**: [Option to lazyload images](https://github.com/iissnan/hexo-theme-next/pull/269)
+- **Konstantin Pavlov**: [Microdata, opengraph and other semantic features](https://github.com/iissnan/hexo-theme-next/pull/276)
+- **Gary**: [FastClick](https://github.com/iissnan/hexo-theme-next/pull/324)
+- **Octavian**: [Baidu site vertification](https://github.com/iissnan/hexo-theme-next/pull/367)
+- **Henry Chang**: [Facebook SDK](https://github.com/iissnan/hexo-theme-next/pull/410)
+- **XiaMo**: [LeanCloud visitors](https://github.com/iissnan/hexo-theme-next/pull/439)
+- **iblogc**: [Fix UA in Duoshuo](https://github.com/iissnan/hexo-theme-next/pull/489)
+- **Vincent**: [Automatic headline ID's](https://github.com/iissnan/hexo-theme-next/pull/588)
+- **cissoid**: [Tencent analytics](https://github.com/iissnan/hexo-theme-next/pull/603)
+- **CosmoX**: [AddThis](https://github.com/iissnan/hexo-theme-next/pull/660)
+- **Jason Guo**: [Reward for post](https://github.com/iissnan/hexo-theme-next/pull/687)
+- **Jerry Bendy**: [CNZZ counter](https://github.com/iissnan/hexo-theme-next/pull/712)
+- **Hui Wang**: [Wechat subscriber](https://github.com/iissnan/hexo-theme-next/pull/788)
+- **PoonChiTim**: [Busuanzi counter](https://github.com/iissnan/hexo-theme-next/pull/809)
+- **hydai**: [Facebook comments](https://github.com/iissnan/hexo-theme-next/pull/925)
+- **OAwan**: [`canonical` option](https://github.com/iissnan/hexo-theme-next/pull/931)
+- **Jim Zenn**: [Google Calendar](https://github.com/iissnan/hexo-theme-next/pull/1167)
+- **Abner Chou**: [Disqus improvements](https://github.com/iissnan/hexo-theme-next/pull/1173)
+- **Igor Fesenko**: [Application Insights](https://github.com/iissnan/hexo-theme-next/pull/1257)
+- **jinfang**: [Youyan comments](https://github.com/iissnan/hexo-theme-next/pull/1324)
+- **AlynxZhou**: [`canvas_nest` option](https://github.com/iissnan/hexo-theme-next/pull/1327)
+- **aleon**: [Tencent MTA](https://github.com/iissnan/hexo-theme-next/pull/1408)
+- **asmoker**: [LiveRe comments](https://github.com/iissnan/hexo-theme-next/pull/1415)
+- **Jacksgong**: [Copyright on posts](https://github.com/iissnan/hexo-theme-next/pull/1497)
+- **zhaiqianfeng**: [Changyan comments](https://github.com/iissnan/hexo-theme-next/pull/1514)
+- **zproo**: [`canvas_ribbon` option](https://github.com/iissnan/hexo-theme-next/pull/1565)
+- **jjandxa**: [`three_waves`](https://github.com/iissnan/hexo-theme-next/pull/1534),
+ [`canvas_lines` and `canvas_sphere`](https://github.com/iissnan/hexo-theme-next/pull/1595) options
+- **shenzekun**: [Load bar at the top](https://github.com/iissnan/hexo-theme-next/pull/1689)
+- **elkan1788**: [Upgrade jiathis share](https://github.com/iissnan/hexo-theme-next/pull/1796)
+- **xCss**: [Valine comment system support](https://github.com/iissnan/hexo-theme-next/pull/1811)
+- **Julian Xhokaxhiu**: [`override` option](https://github.com/iissnan/hexo-theme-next/pull/1861)
+- **LEAFERx**: [NeedMoreShare2](https://github.com/iissnan/hexo-theme-next/pull/1913)
+- **aimingoo & LEAFERx**: [Gitment supported with Mint](https://github.com/iissnan/hexo-theme-next/pull/1919)
+- **LeviDing**: [Fix the bug of Gitment](https://github.com/iissnan/hexo-theme-next/pull/1944)
+- **maple3142**: [Firestore visitor counter](https://github.com/iissnan/hexo-theme-next/pull/1978)
+
+It lives on as an open source project with many contributors, a self updating list is [here](https://github.com/theme-next/hexo-theme-next/graphs/contributors).
+
+P.S. If you did some useful pulls/commits in original repository and you are not in the list, let us know and you will be added here.
diff --git a/themes/next/docs/DATA-FILES.md b/themes/next/docs/DATA-FILES.md
new file mode 100644
index 0000000..1760c77
--- /dev/null
+++ b/themes/next/docs/DATA-FILES.md
@@ -0,0 +1,61 @@
+
Data Files
+
+Currently, it is not smooth to update NexT theme from pulling or downloading new releases. It is quite often running into conflict status when updating NexT theme via `git pull`, or need to merge configurations manually when upgrading to new releases.
+
+At present, NexT encourages users to store some options in site's `/_config.yml` and other options in theme's `/themes/next/_config.yml`. This approach is applicable, but has some drawbacks:
+1. Configurations are splitted into two pieces
+2. Users may be confused which place should be for options
+
+In order to resolve this issue, NexT provides the following two solutions.
+
+
Option 1: Hexo-Way
+
+With this way, all your configurations locate in main Hexo config file (`/_config.yml`), you don't need to touch `/themes/next/_config.yml` or create any new files. But you must preserve double spaces indents within `theme_config` option.
+
+If there are any new options in new releases, you just need to copy those options from `/themes/next/_config.yml`, paste into `/_config.yml` and set their values to whatever you want.
+
+### Usage
+
+1. Please confirm that the `/source/_data/next.yml` file does not exist (delete it if exists).
+2. Copy needed NexT theme options from theme's `/themes/next/_config.yml` into `/_config.yml`, then\
+ 2.1. Move all this settings to the right with two spaces (in Visual Studio Code: select all strings, CTRL + ]).\
+ 2.2. Add `theme_config:` parameter above all this settings.
+
+### Useful links
+
+* [Hexo Configuration](https://hexo.io/docs/configuration.html)
+* [Hexo Pull #757](https://github.com/hexojs/hexo/pull/757)
+
+
Option 2: NexT-Way
+
+With this way, you can put all your configurations into one place (`/source/_data/next.yml`), you don't need to touch `/themes/next/_config.yml`.
+But option may not accurately procces all hexo external libraries with their additional options (for example, `hexo-server` module options may be readed only in default hexo config).
+
+If there are any new options in new releases, you just need to copy those options from `/themes/next/_config.yml`, paste into `/source/_data/next.yml` and set their values to whatever you want.
+
+This method relies on Hexo [Data files](https://hexo.io/docs/data-files.html). Because Data files is introduced in Hexo 3, so you need upgrade Hexo to 3.0 (or above) to use this feature.
+
+### Usage
+
+1. Please ensure you are using Hexo 3 (or above).
+2. Create an file named `next.yml` in site's `/source/_data` directory (create `_data` directory if it does not exist).
+
+
And after that steps there are 2 variants, need to choose only one of them and resume next steps.
+
+* **Variant 1: `override: false` (default)**:
+
+ 1. Check your `override` option in default NexT config, it must set on `false`.\
+ In `next.yml` it must not be defined or set on `false` too.
+ 2. Copy needed options from both site's `/_config.yml` and theme's `/themes/next/_config.yml` into `/source/_data/next.yml`.
+
+* **Variant 2: `override: true`**:
+
+ 1. In `next.yml` set `override` option on `true`.
+ 2. Copy **all** NexT theme options from theme's `/themes/next/_config.yml` into `/source/_data/next.yml`.
+
+3. Then, in main site's `/_config.yml` need to define `theme: next` option (and if needed, `source_dir: source`).
+4. Use standard parameters to start server, generate or deploy (`hexo clean && hexo g -d && hexo s`).
+
+### Useful links
+
+* [NexT Issue #328](https://github.com/iissnan/hexo-theme-next/issues/328)
diff --git a/themes/next/docs/INSTALLATION.md b/themes/next/docs/INSTALLATION.md
new file mode 100644
index 0000000..769d62a
--- /dev/null
+++ b/themes/next/docs/INSTALLATION.md
@@ -0,0 +1,121 @@
+
Installation
+
+
Step 1 → Go to Hexo dir
+
+Change dir to **Hexo root** directory. There must be `node_modules`, `source`, `themes` and other directories:
+
+```sh
+$ cd hexo
+$ ls
+_config.yml node_modules package.json public scaffolds source themes
+```
+
+
Step 2 → Get NexT
+
+
Download theme from GitHub.
+There are 3 options to do it, need to choose only one of them.
+
+### Option 1: Download [latest release version][releases-latest-url]
+
+ At most cases **stable**. Recommended for beginners.
+
+ * Install with [curl & tar & wget][curl-tar-wget-url]:
+
+ ```sh
+ $ mkdir themes/next
+ $ curl -s https://api.github.com/repos/theme-next/hexo-theme-next/releases/latest | grep tarball_url | cut -d '"' -f 4 | wget -i - -O- | tar -zx -C themes/next --strip-components=1
+ ```
+ This variant will give to you **only latest release version** (without `.git` directory inside).\
+ So, there is impossible to update this version with `git` later.\
+ Instead you always can use separate configuration (e.g. [data-files][docs-data-files-url]) and download new version inside old directory (or create new directory and redefine `theme` in Hexo config), without losing your old configuration.
+
+### Option 2: Download [tagged release version][releases-url]
+
+ In rare cases useful, but not recommended.\
+ You must define version. Replace `v6.0.0` with any version from [tags list][tags-url].
+
+ * Variant 1: Install with [curl & tar][curl-tar-url]:
+
+ ```sh
+ $ mkdir themes/next
+ $ curl -L https://api.github.com/repos/theme-next/hexo-theme-next/tarball/v6.0.0 | tar -zxv -C themes/next --strip-components=1
+ ```
+ Same as above under `curl & tar & wget` variant, but will download **only concrete version**.
+
+ * Variant 2: Install with [git][git-url]:
+
+ ```sh
+ $ git clone --branch v6.0.0 https://github.com/theme-next/hexo-theme-next themes/next
+ ```
+ This variant will give to you the **defined release version** (with `.git` directory inside).\
+ And in any time you can switch to any tagged release, but with limit to defined version.
+
+### Option 3: Download [latest master branch][download-latest-url]
+
+ May be **unstable**, but includes latest features. Recommended for advanced users and for developers.
+
+ * Variant 1: Install with [curl & tar][curl-tar-url]:
+
+ ```sh
+ $ mkdir themes/next
+ $ curl -L https://api.github.com/repos/theme-next/hexo-theme-next/tarball | tar -zxv -C themes/next --strip-components=1
+ ```
+ Same as above under `curl & tar & wget` variant, but will download **only latest master branch version**.\
+ At some cases useful for developers.
+
+ * Variant 2: Install with [git][git-url]:
+
+ ```sh
+ $ git clone https://github.com/theme-next/hexo-theme-next themes/next
+ ```
+
+ This variant will give to you the **whole repository** (with `.git` directory inside).\
+ And in any time you can [update current version with git][update-with-git-url] and switch to any tagged release or on latest master or any other branch.\
+ At most cases useful as for users and for developers.
+
+ Get tags list:
+
+ ```sh
+ $ cd themes/next
+ $ git tag -l
+ …
+ v6.0.0
+ v6.0.1
+ v6.0.2
+ ```
+
+ For example, you want to switch on `v6.0.1` [tagged release version][tags-url]. Input the following command:
+
+ ```sh
+ $ git checkout tags/v6.0.1
+ Note: checking out 'tags/v6.0.1'.
+ …
+ HEAD is now at da9cdd2... Release v6.0.1
+ ```
+
+ And if you want to switch back on [master branch][commits-url], input this command:
+
+ ```sh
+ $ git checkout master
+ ```
+
+
+
+NexT provides two render engines for displaying Math Equations.
+
+If you choose to use this feature, you don't need to manually import any JS or CSS. You just need to choose a render engine and turn on `enable` for it (located in `next/_config.yml`).
+
+Notice: only turning on `enable` **cannot let you see the displayed equations correctly**, you need to install the **corresponding Hexo Renderer** to fully support the display of Math Equations. The corresponding Hexo Renderer per engine will be provided below.
+
+
Provided Render Engine
+
+For now, NexT provides two Render Engines: [MathJax](https://www.mathjax.org/) and [Katex](https://khan.github.io/KaTeX/).
+
+### MathJax
+
+If you use MathJax to render Math Equations, you need to use one of them: [hexo-renderer-pandoc](https://github.com/wzpan/hexo-renderer-pandoc) or [hexo-renderer-kramed](https://github.com/sun11/hexo-renderer-kramed) (Not recommended) as the renderer for Markdown.
+
+Firstly, you need to uninstall the original renderer `hexo-renderer-marked`, and install **one of the renderer above**:
+
+```sh
+npm uninstall hexo-renderer-marked
+npm install hexo-renderer-pandoc # or hexo-renderer-kramed
+```
+
+Secondly, in `next/_config.yml`, turn on `enable` of `mathjax`.
+
+```yml
+math:
+ ...
+ mathjax:
+ enable: true
+```
+
+Finally, run standard Hexo generate, deploy process or start the server:
+
+```sh
+hexo clean && hexo g -d
+# or hexo clean && hexo s
+```
+
+#### Numbering and referring equations in MathJax
+
+In the new version of NexT, we have added feature to automatically number equations and to refer to equations. We briefly describe how to use this feature below.
+
+In general, to make the automatic equation numbering work, you have to wrap your LaTeX equations in `equation` environment. Using the plain old style (i.e., wrap an equation with two dollar signs in each side) will not work. How to refer to an equation? Just give a `\label{}` tag and then in your later text, use `\ref{}` or `\eqref{}` to refer it. Using `\eqref{}` is preferred since if you use `\ref{}`, there are no parentheses around the equation number. Below are some of the common scenarios for equation numbering.
+
+For simple equations, use the following form to give a tag,
+
+```latex
+$$\begin{equation}\label{eq1}
+e=mc^2
+\end{equation}$$
+```
+
+Then, you can refer to this equation in your text easily by using something like
+
+```
+the famous matter-energy equation $\eqref{eq1}$ proposed by Einstein ...
+```
+
+For multi-line equations, inside the `equation` environment, you can use the `aligned` environment to split it into multiple lines:
+
+```latex
+$$\begin{equation}\label{eq2}
+\begin{aligned}
+a &= b + c \\
+ &= d + e + f + g \\
+ &= h + i
+\end{aligned}
+\end{equation}$$
+```
+
+We can use `align` environment to align multiple equations. Each of these equations will get its own numbers.
+
+```
+$$\begin{align}
+a &= b + c \label{eq3} \\
+x &= yz \label{eq4}\\
+l &= m - n \label{eq5}
+\end{align}$$
+```
+
+In the `align` environment, if you do not want to number one or some equations, just [use `\nonumber`](https://tex.stackexchange.com/questions/17528/show-equation-number-only-once-in-align-environment) right behind these equations. Like the following:
+
+```latex
+$$\begin{align}
+-4 + 5x &= 2+y \nonumber \\
+ w+2 &= -1+w \\
+ ab &= cb
+\end{align}$$
+```
+
+Sometimes, you want to use more “exotic” style to refer your equation. You can use `\tag{}` to achieve this. For example:
+
+```latex
+$$x+1\over\sqrt{1-x^2} \tag{i}\label{eq_tag}$$
+```
+
+For more information, you can visit the [official MathJax documentation on equation numbering](https://docs.mathjax.org/en/latest/input/tex/eqnumbers.html). You can also visit this [post](https://theme-next.org/docs/third-party-services/math-equations) for more details.
+
+### Katex
+
+The Katex engine is a **much faster** math render engine compared to MathJax. And it could survive without JavaScript.
+
+But, what Katex supports is not as full as MathJax. You could check it from the Useful Links below.
+
+If you use Katex to render Math Equations, you need to use **only one of those renderer**: [hexo-renderer-markdown-it-plus](https://github.com/CHENXCHEN/hexo-renderer-markdown-it-plus) or [hexo-renderer-markdown-it](https://github.com/hexojs/hexo-renderer-markdown-it).
+
+Firstly, you need to uninstall the original renderer `hexo-renderer-marked`, and **install one of selected above**.
+
+```sh
+npm uninstall hexo-renderer-marked
+npm install hexo-renderer-markdown-it-plus
+# or hexo-renderer-markdown-it
+```
+
+Secondly, in `next/_config.yml`, turn on `enable` option of `katex`.
+
+```yml
+math:
+ ...
+ katex:
+ enable: true
+```
+
+Finally, run the standard Hexo generate, deploy process or start the server:
+
+```sh
+hexo clean && hexo g -d
+# or hexo clean && hexo s
+```
+
+#### If you use hexo-renderer-markdown-it
+
+If you use `hexo-renderer-markdown-it`，you also need to add `markdown-it-katex` as its plugin：
+
+```
+npm install markdown-it-katex
+```
+
+And then in `hexo/_config.yml` you need to add `markdown-it-katex` as a plugin for `hexo-renderer-markdown-it`:
+
+```yml
+# config of hexo-renderer-markdown-it
+markdown:
+ render:
+ html: true
+ xhtmlOut: false
+ breaks: true
+ linkify: true
+ typographer: true
+ quotes: '“”‘’'
+ plugins:
+ - markdown-it-katex
+```
+
+#### Known Bugs
+
+1. Firstly, please check [Common Issues](https://github.com/Khan/KaTeX#common-issues) of Katex.
+2. Displayed Math (i.e. `$$...$$`) needs to started with new clear line.\
+ In other words: you must not have any characters (except of whitespaces) **before the opening `$$` and after the ending `$$`** ([comment #32](https://github.com/theme-next/hexo-theme-next/pull/32#issuecomment-357489509)).
+3. Don't support Unicode ([comment #32](https://github.com/theme-next/hexo-theme-next/pull/32#issuecomment-357489509)).
+4. Inline Math (..`$...$`) must not have white spaces **after the opening `$` and before the ending `$`** ([comment #32](https://github.com/theme-next/hexo-theme-next/pull/32#issuecomment-357489509)).
+5. If you use math in Heading (i.e. `## Heading`).\
+ Then in corresponding TOC item it will show the related LaTex code 3 times ([comment #32](https://github.com/theme-next/hexo-theme-next/pull/32#issuecomment-359018694)).
+6. If you use math in your post's title, it will not be rendered ([comment #32](https://github.com/theme-next/hexo-theme-next/pull/32#issuecomment-359142879)).
+
+We currently use Katex 0.11.1, some of those bugs might be caused by the outdated version of Katex we use.
+
+But, as what is described in the beginning, the render of Math Equations relies on Hexo Renderer. Currently, Katex-related renderers only support Katex version until 0.11.1.
+
+We will continuously monitor the updates of corresponding renderers, if there is a renderer which supports newer version of Katex, we will update the Katex we use.
+
+### Useful Links
+
+* [Speed test between Katex and MathJax](https://www.intmath.com/cg5/katex-mathjax-comparison.php)
+* [Function support by Katex](https://khan.github.io/KaTeX/function-support.html)
+
+
Configuration Specifications
+
+ATTENTION! When you edit those configs, **don't change indentation!**
+
+Currently, all NexT config use **2 spaces indents**.
+
+If your content of config is put just directly after the config name, then a space is needed between the colon and the config content (i.e. `enable: true`)
+
+```yml
+# Math Formulas Render Support
+math:
+ # Default (true) will load mathjax / katex script on demand.
+ # That is it only render those page which has `mathjax: true` in Front-matter.
+ # If you set it to false, it will load mathjax / katex srcipt EVERY PAGE.
+ per_page: true
+
+ # hexo-renderer-pandoc (or hexo-renderer-kramed) required for full MathJax support.
+ mathjax:
+ enable: true
+ # See: https://mhchem.github.io/MathJax-mhchem/
+ mhchem: false
+
+ # hexo-renderer-markdown-it-plus (or hexo-renderer-markdown-it with markdown-it-katex plugin) required for full Katex support.
+ katex:
+ enable: false
+ # See: https://github.com/KaTeX/KaTeX/tree/master/contrib/copy-tex
+ copy_tex: false
+```
+
+### `per_page`
+
+`true` or `false`, default is `true`.
+
+This option is to control whether to render Math Equations every page.
+
+The behavior of default (`true`) is to render Math Equations **on demand**.
+
+It will only render those posts which have `mathjax: true` in their Front-matter.
+
+For example:
+
+```md
+
+---
+title: 'Will Render Math'
+mathjax: true
+---
+....
+```
+
+```md
+
+---
+title: 'Not Render Math'
+mathjax: false
+---
+....
+```
+
+```md
+
+---
+title: 'Not Render Math Either'
+---
+....
+```
+
+When you set it to `false`, the math will be rendered on **EVERY PAGE**.
diff --git a/themes/next/docs/UPDATE-FROM-5.1.X.md b/themes/next/docs/UPDATE-FROM-5.1.X.md
new file mode 100644
index 0000000..72201a7
--- /dev/null
+++ b/themes/next/docs/UPDATE-FROM-5.1.X.md
@@ -0,0 +1,29 @@
+
Update from NexT v5.1.x
+
+NexT version 5 works fine with Hexo 3, but for frequent users, you maybe need to upgrade version 5 to 7 to get features and supports in new [Theme-Next](https://github.com/theme-next/hexo-theme-next) repository.
+
+There are no hard breaking changes between 5.1.x and the latest version. It's change major version to 7 because:
+
+1. Main repo was rebased from [iissnan's](https://github.com/iissnan/hexo-theme-next) profile to [theme-next](https://github.com/theme-next) organization.
+2. Most libraries under the `next/source/lib` directory was moved out to [external repos under NexT organization](https://github.com/theme-next).
+3. 3rd-party plugin [`hexo-wordcount`](https://github.com/willin/hexo-wordcount) was replaced by [`hexo-symbols-count-time`](https://github.com/theme-next/hexo-symbols-count-time) because `hexo-symbols-count-time` no have any external Node.js dependencies, no have [language filter](https://github.com/willin/hexo-wordcount/issues/7) which causes better performance on speed at site generation.
+
+So, we suggest to update from version 5 to version 7 in this way:
+
+1. You don't touch old `next` dir and just do some copies of NexT files:\
+ 1.1. `_config.yml` or `next.yml` (if you used [data-files](DATA-FILES.md)).\
+ 1.2. Custom CSS styles what placed in `next/source/css/_custom/*` and `next/source/css/_variables/*` directories.\
+ 1.3. Custom layout styles what placed in `next/layout/_custom/*`.\
+ 1.4. Any another possible custom additions which can be finded by compare tools between repos.
+2. Clone new repo to any another directory instead of `next`. For example, in `next-reloaded` directory: `git clone https://github.com/theme-next/hexo-theme-next themes/next-reloaded`. So, you don't touch your old NexT 5.1.x directory and can work with new `next-reloaded` dir.
+3. Go to Hexo main config and set theme parameter: `theme: next-reloaded`. So, your `next-reloaded` directory must loading with your generation. If you may see any bugs or you simply not like this version, you anytime can switch for 5.1.x version back.
+4. Update language configuration (For Chinese)
+
+ Since v6.0.3, `zh-Hans` has been renamed to `zh-CN`: https://github.com/theme-next/hexo-theme-next/releases/tag/v6.0.3
+
+ Users upgrading to v6.0.3 and later need to explicitly modify the `language` configuration in the Hexo main config file `_config.yml`, otherwise the language display is incorrect.
+5. Update Hexo and Hexo plugin
+
+ If after completing the above steps, an error occurs when executing `hexo s` or` hexo g`, it means that there may be a conflict between the old version of Hexo / Hexo plugin and the new version of the theme NexT. We recommend upgrading Hexo to versions 4.0 and higher and upgrading Hexo plugins to the latest version. You can run `npm outdated` to see all the upgradeable plugins.
+
+And how to enable 3rd-party libraries see [here](https://github.com/theme-next/hexo-theme-next/blob/master/docs/INSTALLATION.md#plugins).
diff --git a/themes/next/docs/ru/DATA-FILES.md b/themes/next/docs/ru/DATA-FILES.md
new file mode 100644
index 0000000..c8c9cc3
--- /dev/null
+++ b/themes/next/docs/ru/DATA-FILES.md
@@ -0,0 +1,61 @@
+
Дата Файлы
+
+Обновление темы NexT через пулы проходит не слишком гладко. Часто происходит конфликтная ситуация при обновлении по команде `git pull`, хотя её и можно обойти, если смерджить настройки в файле конфигурации вручную.
+
+На данный момент, пользователи хранят одни настройки в корневом `_config.yml` (Hexo), а другие настройки в конфиге темы `_config.yml` (NexT). И всё вроде бы ничего, но имеются некоторые недостатки:
+1. Конфигурация разделяется на две части.
+2. Пользователи могут запутаться, в каком файле какие должны быть настройки.
+
+Во избежании проблемы, NexT предлагает два варианта.
+
+
Способ 1: Hexo-Путь
+
+Используя этот способ, вся конфигурация будет раположена в корневом конфиге hexo (`/_config.yml`), благодаря чему нет необходимости изменять оригинальный конфиг темы (`/themes/next/_config.yml`) или создавать какие-либо новые файлы. Но в этом случае необходимо сохранять двойные отступы внутри `theme_config` параметра.
+
+Если в новых версиях появятся какие-то новые настройки, нужно просто скопировать эти настройки из оригинального `next/_config.yml` в редактируемый `/_config.yml` и настроить по своему усмотрению.
+
+### Использование
+
+1. Проверяем на существование `/source/_data/next.yml` файл (удаляем, если существует).
+2. Копируем необходимые опции из конфига темы NexT `/themes/next/_config.yml` в `/_config.yml`, затем\
+ 2.1. Сдвигаем все опции вправо на 2 пробела (в Visual Studio Code: выделяем все строки, CTRL + ]).\
+ 2.2. Добавляем `theme_config:` параметр перед всеми этими настройками.
+
+### Полезные ссылки
+
+* [Конфигурация Hexo](https://hexo.io/ru/docs/configuration.html)
+* [Hexo Pull #757](https://github.com/hexojs/hexo/pull/757)
+
+
Способ 2: NexT-Путь
+
+Используя этот способ, вся конфигурация будет храниться в одном файле (`/source/_data/next.yml`), благодаря чему нет необходимости изменять оригинальный конфиг темы (`/themes/next/_config.yml`).
+Но с этим способом могут не корректно обрабатываться все внешние библиотеки hexo при использовании их дополнительных опций (например, опции модуля `hexo-server` могут быть считаны только из стандартного конфига hexo).
+
+Если в новых версиях появятся какие-то новые настройки, нужно просто скопировать эти настройки из оригинального `/themes/next/_config.yml` во внешний `_data/next.yml` и настроить по своему усмотрению.
+
+Этот метод опирается на Hexo [дата-файлов](https://hexo.io/docs/data-files.html). И т.к. дата-файлы были представлены в Hexo 3, необходимо обновиться до Hexo 3.0 (или выше) для использования этой возможности.
+
+### Использование
+
+1. Убеждаемся, что Hexo версии 3 (или выше).
+2. Создаём файл под именем `next.yml` в корневой директории сайта — `/source/_data` (создаём директорию `_data`, если отсутствует).
+
+
И после этих шагов есть 2 варианта, нужно выбрать только 1 из них и продолжить следующие шаги.
+
+* **Вариант 1: `override: false` (по-умолчанию)**:
+
+ 1. Проверяем опцию `override` в стандартном конфиге NexT'а, должно быть установлено в `false`.\
+ В файле `next.yml` эта опция не должна быть вписана вовсе или вписана и установлена в `false`.
+ 2. Копируем настройки из конфига темы NexT (`_config.yml`) и из корневого конфига сайта (`_config.yml`) в файл `/source/_data/next.yml`.
+
+* **Вариант 2: `override: true`**:
+
+ 1. В файле `next.yml` ставим опцию `override` в `true`.
+ 2. Копируем **все** опции из оригинального конфига NexT'а `/themes/next/_config.yml` в `/source/_data/next.yml`.
+
+3. Затем, в корневом конфиге сайта `/_config.yml` необходимо установить опцию `theme: next` (и если требуется, `source_dir: source`).
+4. Используем станадартные параметры для запускаь генерации или развёртывания (`hexo clean && hexo g -d && hexo s`).
+
+### Полезные ссылки
+
+* [NexT Issue #328](https://github.com/iissnan/hexo-theme-next/issues/328)
diff --git a/themes/next/docs/ru/INSTALLATION.md b/themes/next/docs/ru/INSTALLATION.md
new file mode 100644
index 0000000..5384527
--- /dev/null
+++ b/themes/next/docs/ru/INSTALLATION.md
@@ -0,0 +1,121 @@
+
Установка
+
+
Шаг 1 → Идём в директорию Hexo
+
+Меняем каталог на **корневой hexo**. Там должны находиться `node_modules`, `source`, `themes` и другие папки:
+
+```sh
+$ cd hexo
+$ ls
+_config.yml node_modules package.json public scaffolds source themes
+```
+
+
Шаг 2 → Скачиваем NexT
+
+
Скачиваем тему с GitHub.
+Имеются 3 способа как зделать это, нужно выбрать только 1 из них.
+
+### Способ 1: Скачиваем [последнюю версию релиза][releases-latest-url]
+
+ В большинстве случаев **стабильна**. Рекомендуется для начинающих пользователей.
+
+ * Установка с помощью [curl & tar & wget][curl-tar-wget-url]:
+
+ ```sh
+ $ mkdir themes/next
+ $ curl -s https://api.github.com/repos/theme-next/hexo-theme-next/releases/latest | grep tarball_url | cut -d '"' -f 4 | wget -i - -O- | tar -zx -C themes/next --strip-components=1
+ ```
+ Этим способом Вы скачаете **только последнюю версию релиза** (без директории `.git` внутри).\
+ Поэтому, в дальнейшем будет невозможно обновить эту версию через `git`.\
+ Зато всегда можно использовать отдельную конфигурацию (т.е. [дата-файлы][docs-data-files-url]) и скачивать новую версию перезаписывая старую (или создать новый каталог и переопределить параметр `theme` в конфиге Hexo), без потери старой конфигурации.
+
+### Способ 2: Скачиваем [указанную версию релиза][releases-url]
+
+ В редких случаях полезно, но не рекомендуется.\
+ Необходимо указать версию. Замените `v6.0.0` на любую версию из [списка тэгов][tags-url].
+
+ * Вариант 1: Установка с помощью [curl & tar][curl-tar-url]:
+
+ ```sh
+ $ mkdir themes/next
+ $ curl -L https://api.github.com/repos/theme-next/hexo-theme-next/tarball/v6.0.0 | tar -zxv -C themes/next --strip-components=1
+ ```
+ То же, что и описано выше в способе `curl & tar & wget`, но скачает **только конкретную версию**.
+
+ * Вариант 2: Установка с помощью [git][git-url]:
+
+ ```sh
+ $ git clone --branch v6.0.0 https://github.com/theme-next/hexo-theme-next themes/next
+ ```
+ Этот вариант скачает **указанную версию релиза** (включая директорию `.git` внутри).\
+ И в любой момент Вы можете переключиться на любую весию тэга, но с лимитом до указанной версии.
+
+### Способ 3: Скачиваем [последнюю мастер-ветку][download-latest-url]
+
+ Иногда может быть **нестабильна**, но включает самые последние нововведения. Рекомендуется для продвинутых пользователей и для разработчиков.
+
+ * Вариант 1: Установка с помощью [curl & tar][curl-tar-url]:
+
+ ```sh
+ $ mkdir themes/next
+ $ curl -L https://api.github.com/repos/theme-next/hexo-theme-next/tarball | tar -zxv -C themes/next --strip-components=1
+ ```
+ То же, что и описано выше в варианте `curl & tar & wget`, но скачает **только последнюю мастер-ветку**.\
+ В некоторых случаях полезно для разработчиков.
+
+ * Вариант 2: Установка с помощью [git][git-url]:
+
+ ```sh
+ $ git clone https://github.com/theme-next/hexo-theme-next themes/next
+ ```
+
+ Этот вариант скачает **весь репозиторий** (включая директорию `.git` внутри).\
+ И в любой момент Вы можете [обновить текущую версию через git][update-with-git-url] и переключиться на любую версию тэга или на последнюю мастер или любую другую ветку.\
+ В большинстве случаев полезно как для пользователей, так и для разработчиков.
+
+ Смотрим список тэгов:
+
+ ```sh
+ $ cd themes/next
+ $ git tag -l
+ …
+ v6.0.0
+ v6.0.1
+ v6.0.2
+ ```
+
+ Например, Вы хотите переключиться на [версию релиза][tags-url] `v6.0.1`. Вводим следующую команду:
+
+ ```sh
+ $ git checkout tags/v6.0.1
+ Note: checking out 'tags/v6.0.1'.
+ …
+ HEAD is now at da9cdd2... Release v6.0.1
+ ```
+
+ И если вы хотите переключиться обратно на [мастер-ветку][commits-url], вводим следующее:
+
+ ```sh
+ $ git checkout master
+ ```
+
+
+
+## Установка
+
+Простейший вариант установки — склонировать весь репозиторий:
+
+```sh
+$ cd hexo
+$ git clone https://github.com/theme-next/hexo-theme-next themes/next
+```
+
+Или предлагаю почитать [детальные инструкции по установке][docs-installation-url], если вариант выше не устраивает.
+
+## Плагины
+
+В конфиге NexT'а теперь можно найти зависимости на каждый модуль, который был вынесен во внешние репозитории, которые могут быть найдены по [ссылке основной организации][official-plugins-url].
+
+Например, Вы хотите использовать `pjax` для своего сайта. Открываем конфиг NexT'а и находим:
+
+```yml
+# Easily enable fast Ajax navigation on your website.
+# Dependencies: https://github.com/theme-next/theme-next-pjax
+pjax: true
+```
+
+Затем включаем параметр `pjax` и переходим по ссылке «Dependencies» с дальнейшеми инструкциями по установке этого модуля.
+
+## Обновление
+
+NexT выпускает новые версии каждый месяц. Можно обновить до последней мастер-ветки следующей командой:
+
+```sh
+$ cd themes/next
+$ git pull
+```
+
+А если всплывают ошибки во время обновления (что-то наподобии **«Commit your changes or stash them before you can merge»**), рекомендуется ознакомиться с особенностью хранения [дата-файлов в Hexo][docs-data-files-url].\
+Как бы то ни было, можно обойти ошибки при обновлении если «Закомитить», «Стэшнуть» или «Откатить» локальные изменения. Смотрим [здесь](https://stackoverflow.com/a/15745424/5861495) как это сделать.
+
+**Если нужно обновиться с версии v5.1.x на последней версиями, читаем [здесь][docs-update-5-1-x-url].**
+
+## Обратная связь
+
+* Посетите [Awesome NexT][awesome-next-url] список.
+* Вступить в наши [Telegram][t-chat-url] / [Gitter][gitter-url] / [Riot][riot-url] чаты.
+* [Добавить или улучшить перевод][i18n-url] за несколько секунд.
+* Сообщить об ошибке в разделе [GitHub Issues][issues-bug-url].
+* Запросить новую возможность на [GitHub][issues-feat-url].
+* Голосовать за [популярные запросы возможностей][feat-req-vote-url].
+
+## Содействие
+
+[![][contributors-image]][contributors-url]
+
+Приветсвуется любое содействие, не стесняйтесь сообщать «Баги», брать «Форки» и вливать «Пулы».
+
+## Благодарности
+
+
+ «NexT» выражает особую благодарность этим замечательным сервисам, которые спонсируют нашу основную инфраструктуру:
+
+
+
+
+
+
+ GitHub позволяет нам хостить Git-репозиторий, Netlify позволяет нам деплоить документацию.
+
+
+
+
+ Crowdin позволяет нам удобно переводить документацию.
+
+
+
+
+
+
+ Codacy позволяет нам контролировать качество кода, Travis CI позволяет нам запускать набор тестов.
+
+
+Между версией 5.1.x и последней версиями нет жёстких изменений. Версия сменилась на мажорную 7 по следующим причинам:
+1. Основной репозиторий перебазировался из профиля [iissnan'а](https://github.com/iissnan/hexo-theme-next) в [theme-next](https://github.com/theme-next) организацию.
+2. Большинство библиотек в `next/source/lib` директории были вынесены в [отдельные репозитории под организацией NexT](https://github.com/theme-next).
+3. 3rd-party плагин [`hexo-wordcount`](https://github.com/willin/hexo-wordcount) был заменён на [`hexo-symbols-count-time`](https://github.com/theme-next/hexo-symbols-count-time) т.к. `hexo-symbols-count-time` не имеет никаких сторонних Node.js зависимостей, не имеет [языкового фильтра](https://github.com/willin/hexo-wordcount/issues/7) что обеспечивает улучшенную производительность при генерации сайта.
+
+Поэтому, я предлагаю обновиться с версии 5 на версию 7 следующим способом:
+
+1. Вы не трогаете старую директорию `next`, а всего-лишь делаете резервные копии файлов NexT:\
+ 1.1. `config.yml` или `next.yml` (если Вы использовали [дата-файлы](DATA-FILES.md)).\
+ 1.2. Пользовательских CSS-стилей, которые расположены в `next/source/css/_custom/*` и `next/source/css/_variables/*` директориях.\
+ 1.3. Пользовательских layout-стилей, которые расположены в `next/layout/_custom/*`.\
+ 1.4. Любые другие всевозможные пользовательские изменения, которые могут быть найдены любым инструментом для сравнения файлов.
+2. Склонировать новый репозиторий в любую другую директорию, отличную от `next`. Например, в директорию `next-reloaded`: `git clone https://github.com/theme-next/hexo-theme-next themes/next-reloaded`. Итак, нет необходимости трогать старую NexT 5.1.x директорию и можно работать с новой `next-reloaded`.
+3. Открываем главную Hexo-конфигурацию и устанавливаем параметр темы: `theme: next-reloaded`. Так Ваша директория `next-reloaded` должна грузиться при генерации. Если Вы будете наблюдать какие-либо баги или Вам попросту не нравится эта новая версия, в любой момент Вы можете использовать старую 5.1.x.
+
+А как активировать 3rd-party библиотеки, смотрим здесь [здесь](https://github.com/theme-next/hexo-theme-next/blob/master/docs/ru/INSTALLATION.md#%D0%9F%D0%BB%D0%B0%D0%B3%D0%B8%D0%BD%D1%8B).
diff --git a/themes/next/docs/zh-CN/ALGOLIA-SEARCH.md b/themes/next/docs/zh-CN/ALGOLIA-SEARCH.md
new file mode 100644
index 0000000..660584a
--- /dev/null
+++ b/themes/next/docs/zh-CN/ALGOLIA-SEARCH.md
@@ -0,0 +1,80 @@
+
+{%- endif %}
diff --git a/themes/next/layout/_partials/page/breadcrumb.swig b/themes/next/layout/_partials/page/breadcrumb.swig
new file mode 100644
index 0000000..267617f
--- /dev/null
+++ b/themes/next/layout/_partials/page/breadcrumb.swig
@@ -0,0 +1,27 @@
+{%- set paths = page.path.split('/') %}
+{%- set count = paths.length %}
+{%- if count > 2 %}
+ {%- set current = 0 %}
+ {%- set link = '' %}
+
+ {%- for path in paths %}
+ {%- set current = current + 1 %}
+ {%- if path != 'index.html' %}
+ {%- if current == count - 1 and paths[count - 1] == 'index.html' %}
+
{{ path | upper }}
+ {% else %}
+ {%- if link == '' %}
+ {%- set link = '/' + path %}
+ {% else %}
+ {%- set link = link + '/' + path %}
+ {%- endif %}
+ {%- if path.includes('.html') %}
+
e x T
+
+
+ 
+
+
+
+ 
+ }})
+ {%- endfor %}
+
+ {%- endif %}
+
+ {%- if is_index %}
+ {%- if post.description and theme.excerpt_description %}
+  }})
+ {%- endif %}
+ {%- if theme.footer.beian.gongan_id and theme.footer.beian.gongan_num %}
+ {{- next_url('http://www.beian.gov.cn/portal/registerSystemInfo?recordcode=' + theme.footer.beian.gongan_id, theme.footer.beian.gongan_num + ' ') }}
+ {%- endif %}
+
+{%- endif %}
+
+
+ {% set copyright_year = date(null, 'YYYY') %}
+ © {% if theme.footer.since and theme.footer.since != copyright_year %}{{ theme.footer.since }} – {% endif %}
+ {{ copyright_year }}
+
+
+
+
+
+ {%- if config.symbols_count_time.total_symbols %}
+
+
+ {%- if theme.symbols_count_time.item_text_total %}
+
+ {%- endif %}
+ {{ symbolsCountTotal(site) }}
+ {%- endif %}
+
+ {%- if config.symbols_count_time.total_time %}
+
+
+ {%- if theme.symbols_count_time.item_text_total %}
+
+ {%- endif %}
+ {{ symbolsTimeTotal(site, config.symbols_count_time.awl, config.symbols_count_time.wpm, __('symbols_count_time.time_minutes')) }}
+ {%- endif %}
+
+
+{%- if theme.footer.powered %}
+
+ {%- set next_site = 'https://theme-next.org' %}
+ {%- if theme.scheme !== 'Gemini' %}
+ {%- set next_site = 'https://' + theme.scheme | lower + '.theme-next.org' %}
+ {%- endif %}
+ {{- __('footer.powered', next_url('https://hexo.io', 'Hexo', {class: 'theme-link'}) + ' & ' + next_url(next_site, 'NexT.' + theme.scheme, {class: 'theme-link'})) }}
+
+{%- endif %}
+
+{%- if theme.add_this_id %}
+
+
+
+{%- endif %}
+
+{{- next_inject('footer') }}
diff --git a/themes/next/layout/_partials/head/head-unique.swig b/themes/next/layout/_partials/head/head-unique.swig
new file mode 100644
index 0000000..85af72a
--- /dev/null
+++ b/themes/next/layout/_partials/head/head-unique.swig
@@ -0,0 +1,14 @@
+{{ open_graph() }}
+
+{{ canonical() }}
+
+{# Exports some front-matter variables to Front-End #}
+
diff --git a/themes/next/layout/_partials/head/head.swig b/themes/next/layout/_partials/head/head.swig
new file mode 100644
index 0000000..23ac59b
--- /dev/null
+++ b/themes/next/layout/_partials/head/head.swig
@@ -0,0 +1,61 @@
+
+
+
+
+
+{%- if theme.favicon.apple_touch_icon %}
+
+{%- endif %}
+{%- if theme.favicon.medium %}
+
+{%- endif %}
+{%- if theme.favicon.small %}
+
+{%- endif %}
+{%- if theme.favicon.safari_pinned_tab %}
+
+{%- endif %}
+{%- if theme.favicon.android_manifest %}
+
+{%- endif %}
+{%- if theme.favicon.ms_browserconfig %}
+
+{%- endif %}
+
+{%- if theme.disable_baidu_transformation %}
+
+
+{%- endif %}
+{%- if theme.google_site_verification %}
+
+{%- endif %}
+{%- if theme.bing_site_verification %}
+
+{%- endif %}
+{%- if theme.yandex_site_verification %}
+
+{%- endif %}
+{%- if theme.baidu_site_verification %}
+
+{%- endif %}
+
+
+
+{{ next_font() }}
+
+{%- set font_awesome_uri = theme.vendors.fontawesome or next_vendors('font-awesome/css/all.min.css') %}
+
+
+{%- if theme.fancybox %}
+ {%- set fancybox_css_uri = theme.vendors.fancybox_css or next_vendors('//cdn.jsdelivr.net/gh/fancyapps/fancybox@3/dist/jquery.fancybox.min.css') %}
+
+{%- endif %}
+
+{%- if theme.pace.enable %}
+ {%- set pace_css_uri = theme.vendors.pace_css or next_vendors('pace/pace-theme-' + theme.pace.theme + '.min.css') %}
+ {%- set pace_js_uri = theme.vendors.pace or next_vendors('pace/pace.min.js') %}
+
+
+{%- endif %}
+
+{{ next_config() }}
diff --git a/themes/next/layout/_partials/header/brand.swig b/themes/next/layout/_partials/header/brand.swig
new file mode 100644
index 0000000..290960f
--- /dev/null
+++ b/themes/next/layout/_partials/header/brand.swig
@@ -0,0 +1,41 @@
+
+
+
+
+
+
+
+
+
+
+ {%- if theme.custom_logo and theme.scheme === 'Muse' %}
+
+
+ 
+
+
+ {%- endif %}
+
+
+
+ 
+ {%- endif %}
+
+ {%- if popular_post.excerpt and popular_post.excerpt != '' %}
+  }})
+ {%- endif %}
+
+ {{ description }}
+
+
+{%- if theme.site_state %}
+
+
+
+{%- endif %}
+
+{%- if theme.chat.enable and theme.chat.service !== '' %}
+
+{%- endif %}
+
+{%- if theme.social %}
+
+{%- endif %}
+
+{%- if theme.creative_commons.license and theme.creative_commons.sidebar %}
+
+ {%- set ccImage = ' + ')
' %}
+ {{ next_url(ccURL, ccImage, {class: 'cc-opacity'}) }}
+
+{%- endif %}
+
+{# Blogroll #}
+{%- if theme.links %}
+
+
+ {%- if theme.links_settings.icon %}{%- endif %}
+ {{ theme.links_settings.title }}
+
+