Showing preview only (593K chars total). Download the full file or copy to clipboard to get everything.
Repository: theme-next/hexo-theme-next
Branch: master
Commit: b062274e94d2
Files: 275
Total size: 532.3 KB
Directory structure:
gitextract_z3btu9dz/
├── .editorconfig
├── .eslintrc.json
├── .gitattributes
├── .github/
│ ├── CODE_OF_CONDUCT.md
│ ├── CONTRIBUTING.md
│ ├── ISSUE_TEMPLATE/
│ │ ├── bug-report.md
│ │ ├── feature-request.md
│ │ ├── other.md
│ │ └── question.md
│ ├── PULL_REQUEST_TEMPLATE.md
│ ├── config.yml
│ ├── issue-close-app.yml
│ ├── issue_label_bot.yaml
│ ├── lock.yml
│ ├── mergeable.yml
│ ├── release-drafter.yml
│ ├── stale.yml
│ └── support.yml
├── .gitignore
├── .stylintrc
├── .travis.yml
├── LICENSE.md
├── README.md
├── _config.yml
├── crowdin.yml
├── docs/
│ ├── AGPL3.md
│ ├── ALGOLIA-SEARCH.md
│ ├── AUTHORS.md
│ ├── DATA-FILES.md
│ ├── INSTALLATION.md
│ ├── LEANCLOUD-COUNTER-SECURITY.md
│ ├── LICENSE.txt
│ ├── MATH.md
│ ├── UPDATE-FROM-5.1.X.md
│ ├── ru/
│ │ ├── DATA-FILES.md
│ │ ├── INSTALLATION.md
│ │ ├── README.md
│ │ └── UPDATE-FROM-5.1.X.md
│ └── zh-CN/
│ ├── ALGOLIA-SEARCH.md
│ ├── CODE_OF_CONDUCT.md
│ ├── CONTRIBUTING.md
│ ├── DATA-FILES.md
│ ├── INSTALLATION.md
│ ├── LEANCLOUD-COUNTER-SECURITY.md
│ ├── MATH.md
│ ├── README.md
│ └── UPDATE-FROM-5.1.X.md
├── gulpfile.js
├── languages/
│ ├── ar.yml
│ ├── de.yml
│ ├── en.yml
│ ├── es.yml
│ ├── fa.yml
│ ├── fr.yml
│ ├── hu.yml
│ ├── id.yml
│ ├── it.yml
│ ├── ja.yml
│ ├── ko.yml
│ ├── nl.yml
│ ├── pt-BR.yml
│ ├── pt.yml
│ ├── ru.yml
│ ├── tr.yml
│ ├── uk.yml
│ ├── vi.yml
│ ├── zh-CN.yml
│ ├── zh-HK.yml
│ └── zh-TW.yml
├── layout/
│ ├── _layout.swig
│ ├── _macro/
│ │ ├── post-collapse.swig
│ │ ├── post.swig
│ │ └── sidebar.swig
│ ├── _partials/
│ │ ├── comments.swig
│ │ ├── footer.swig
│ │ ├── head/
│ │ │ ├── head-unique.swig
│ │ │ └── head.swig
│ │ ├── header/
│ │ │ ├── brand.swig
│ │ │ ├── index.swig
│ │ │ ├── menu-item.swig
│ │ │ ├── menu.swig
│ │ │ └── sub-menu.swig
│ │ ├── languages.swig
│ │ ├── page/
│ │ │ ├── breadcrumb.swig
│ │ │ └── page-header.swig
│ │ ├── pagination.swig
│ │ ├── post/
│ │ │ ├── post-copyright.swig
│ │ │ ├── post-followme.swig
│ │ │ ├── post-footer.swig
│ │ │ ├── post-related.swig
│ │ │ └── post-reward.swig
│ │ ├── search/
│ │ │ ├── algolia-search.swig
│ │ │ ├── index.swig
│ │ │ └── localsearch.swig
│ │ ├── sidebar/
│ │ │ └── site-overview.swig
│ │ └── widgets.swig
│ ├── _scripts/
│ │ ├── index.swig
│ │ ├── noscript.swig
│ │ ├── pages/
│ │ │ └── schedule.swig
│ │ ├── pjax.swig
│ │ ├── schemes/
│ │ │ ├── gemini.swig
│ │ │ ├── mist.swig
│ │ │ ├── muse.swig
│ │ │ └── pisces.swig
│ │ ├── three.swig
│ │ └── vendors.swig
│ ├── _third-party/
│ │ ├── analytics/
│ │ │ ├── baidu-analytics.swig
│ │ │ ├── google-analytics.swig
│ │ │ ├── growingio.swig
│ │ │ └── index.swig
│ │ ├── baidu-push.swig
│ │ ├── chat/
│ │ │ ├── chatra.swig
│ │ │ └── tidio.swig
│ │ ├── comments/
│ │ │ ├── changyan.swig
│ │ │ ├── disqus.swig
│ │ │ ├── disqusjs.swig
│ │ │ ├── gitalk.swig
│ │ │ ├── livere.swig
│ │ │ └── valine.swig
│ │ ├── index.swig
│ │ ├── math/
│ │ │ ├── index.swig
│ │ │ ├── katex.swig
│ │ │ └── mathjax.swig
│ │ ├── quicklink.swig
│ │ ├── rating.swig
│ │ ├── search/
│ │ │ ├── algolia-search.swig
│ │ │ ├── localsearch.swig
│ │ │ └── swiftype.swig
│ │ ├── statistics/
│ │ │ ├── busuanzi-counter.swig
│ │ │ ├── cnzz-analytics.swig
│ │ │ ├── firestore.swig
│ │ │ ├── index.swig
│ │ │ └── lean-analytics.swig
│ │ └── tags/
│ │ ├── mermaid.swig
│ │ └── pdf.swig
│ ├── archive.swig
│ ├── category.swig
│ ├── index.swig
│ ├── page.swig
│ ├── post.swig
│ └── tag.swig
├── package.json
├── scripts/
│ ├── events/
│ │ ├── index.js
│ │ └── lib/
│ │ ├── config.js
│ │ ├── injects-point.js
│ │ └── injects.js
│ ├── filters/
│ │ ├── comment/
│ │ │ ├── changyan.js
│ │ │ ├── common.js
│ │ │ ├── default-config.js
│ │ │ ├── disqus.js
│ │ │ ├── disqusjs.js
│ │ │ ├── gitalk.js
│ │ │ ├── livere.js
│ │ │ └── valine.js
│ │ ├── default-injects.js
│ │ ├── front-matter.js
│ │ ├── locals.js
│ │ ├── minify.js
│ │ └── post.js
│ ├── helpers/
│ │ ├── engine.js
│ │ ├── font.js
│ │ ├── next-config.js
│ │ └── next-url.js
│ ├── renderer.js
│ └── tags/
│ ├── button.js
│ ├── caniuse.js
│ ├── center-quote.js
│ ├── group-pictures.js
│ ├── label.js
│ ├── mermaid.js
│ ├── note.js
│ ├── pdf.js
│ ├── tabs.js
│ └── video.js
└── source/
├── css/
│ ├── _colors.styl
│ ├── _common/
│ │ ├── components/
│ │ │ ├── back-to-top-sidebar.styl
│ │ │ ├── back-to-top.styl
│ │ │ ├── components.styl
│ │ │ ├── pages/
│ │ │ │ ├── breadcrumb.styl
│ │ │ │ ├── categories.styl
│ │ │ │ ├── pages.styl
│ │ │ │ ├── schedule.styl
│ │ │ │ └── tag-cloud.styl
│ │ │ ├── post/
│ │ │ │ ├── post-collapse.styl
│ │ │ │ ├── post-copyright.styl
│ │ │ │ ├── post-eof.styl
│ │ │ │ ├── post-expand.styl
│ │ │ │ ├── post-followme.styl
│ │ │ │ ├── post-gallery.styl
│ │ │ │ ├── post-header.styl
│ │ │ │ ├── post-nav.styl
│ │ │ │ ├── post-reward.styl
│ │ │ │ ├── post-rtl.styl
│ │ │ │ ├── post-tags.styl
│ │ │ │ ├── post-widgets.styl
│ │ │ │ └── post.styl
│ │ │ ├── reading-progress.styl
│ │ │ └── third-party/
│ │ │ ├── gitalk.styl
│ │ │ ├── math.styl
│ │ │ ├── related-posts.styl
│ │ │ ├── search.styl
│ │ │ └── third-party.styl
│ │ ├── outline/
│ │ │ ├── footer/
│ │ │ │ └── footer.styl
│ │ │ ├── header/
│ │ │ │ ├── bookmark.styl
│ │ │ │ ├── github-banner.styl
│ │ │ │ ├── header.styl
│ │ │ │ ├── headerband.styl
│ │ │ │ ├── menu.styl
│ │ │ │ ├── site-meta.styl
│ │ │ │ └── site-nav.styl
│ │ │ ├── mobile.styl
│ │ │ ├── outline.styl
│ │ │ └── sidebar/
│ │ │ ├── sidebar-author-links.styl
│ │ │ ├── sidebar-author.styl
│ │ │ ├── sidebar-blogroll.styl
│ │ │ ├── sidebar-button.styl
│ │ │ ├── sidebar-dimmer.styl
│ │ │ ├── sidebar-nav.styl
│ │ │ ├── sidebar-toc.styl
│ │ │ ├── sidebar-toggle.styl
│ │ │ ├── sidebar.styl
│ │ │ └── site-state.styl
│ │ └── scaffolding/
│ │ ├── base.styl
│ │ ├── buttons.styl
│ │ ├── comments.styl
│ │ ├── highlight/
│ │ │ ├── copy-code.styl
│ │ │ ├── diff.styl
│ │ │ ├── highlight.styl
│ │ │ └── theme.styl
│ │ ├── normalize.styl
│ │ ├── pagination.styl
│ │ ├── scaffolding.styl
│ │ ├── tables.styl
│ │ ├── tags/
│ │ │ ├── blockquote-center.styl
│ │ │ ├── group-pictures.styl
│ │ │ ├── label.styl
│ │ │ ├── note.styl
│ │ │ ├── pdf.styl
│ │ │ ├── tabs.styl
│ │ │ └── tags.styl
│ │ └── toggles.styl
│ ├── _mixins.styl
│ ├── _schemes/
│ │ ├── Gemini/
│ │ │ └── index.styl
│ │ ├── Mist/
│ │ │ ├── _header.styl
│ │ │ ├── _layout.styl
│ │ │ ├── _menu.styl
│ │ │ ├── _posts-expand.styl
│ │ │ └── index.styl
│ │ ├── Muse/
│ │ │ ├── _header.styl
│ │ │ ├── _layout.styl
│ │ │ ├── _menu.styl
│ │ │ ├── _sidebar.styl
│ │ │ ├── _sub-menu.styl
│ │ │ └── index.styl
│ │ └── Pisces/
│ │ ├── _header.styl
│ │ ├── _layout.styl
│ │ ├── _menu.styl
│ │ ├── _sidebar.styl
│ │ ├── _sub-menu.styl
│ │ └── index.styl
│ ├── _variables/
│ │ ├── Gemini.styl
│ │ ├── Mist.styl
│ │ ├── Muse.styl
│ │ ├── Pisces.styl
│ │ └── base.styl
│ └── main.styl
├── js/
│ ├── algolia-search.js
│ ├── bookmark.js
│ ├── local-search.js
│ ├── motion.js
│ ├── next-boot.js
│ ├── schemes/
│ │ ├── muse.js
│ │ └── pisces.js
│ └── utils.js
└── lib/
└── anime.min.js
================================================
FILE CONTENTS
================================================
================================================
FILE: .editorconfig
================================================
# editorconfig.org
root = true
[*]
charset = utf-8
end_of_line = lf
insert_final_newline = true
trim_trailing_whitespace = true
indent_style = space
indent_size = 2
================================================
FILE: .eslintrc.json
================================================
{
"extends": "theme-next",
"root": true
}
================================================
FILE: .gitattributes
================================================
source/lib/* linguist-vendored
================================================
FILE: .github/CODE_OF_CONDUCT.md
================================================
<div align="right">
Language:
:us:
<a title="Chinese" href="../docs/zh-CN/CODE_OF_CONDUCT.md">:cn:</a>
<a title="Russian" href="../docs/ru/CODE_OF_CONDUCT.md">:ru:</a>
</div>
# <div align="center"><a title="Go to homepage" href="https://theme-next.org"><img align="center" width="56" height="56" src="https://raw.githubusercontent.com/theme-next/hexo-theme-next/master/source/images/logo.svg?sanitize=true"></a> e x T</div>
[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).
================================================
FILE: .github/CONTRIBUTING.md
================================================
<div align="right">
Language:
:us:
<a title="Chinese" href="../docs/zh-CN/CONTRIBUTING.md">:cn:</a>
<a title="Russian" href="../docs/ru/CONTRIBUTING.md">:ru:</a>
</div>
# <div align="center"><a title="Go to homepage" href="https://theme-next.org"><img align="center" width="56" height="56" src="https://raw.githubusercontent.com/theme-next/hexo-theme-next/master/source/images/logo.svg?sanitize=true"></a> e x T</div>
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".
================================================
FILE: .github/ISSUE_TEMPLATE/bug-report.md
================================================
---
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 <!-- 我确认我已经查看了 -->
<!-- Change [ ] to [x] to select (将 [ ] 换成 [x] 来选择) -->
- [ ] 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 <!-- 实际行为 -->
<!-- Please provide at least one of the following information (请至少提供以下的一项信息) -->
- 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
<!-- Paste output from `node -v && npm -v` (粘贴 `node -v && npm -v` 输出的信息) -->
```
```
### Package dependencies Information
<!-- Paste output from `npm ls --depth 0` (粘贴 `npm ls --depth 0` 输出的信息) -->
```
```
### Hexo Configuration
<!-- Paste configuration from Hexo `_config.yml` (粘贴 Hexo `_config.yml` 中的内容) -->
```yml
```
### NexT Configuration
<!-- Paste ONLY CHANGED CONFIGURATION from NexT `_config.yml` (只粘贴 NexT 主题配置文件 `_config.yml` 中修改过的部分) -->
```yml
```
## Other Information <!-- (Like Browser, System, Screenshots) -->
================================================
FILE: .github/ISSUE_TEMPLATE/feature-request.md
================================================
---
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 <!-- 我确认我已经查看了 -->
<!-- Change [ ] to [x] to select (将 [ ] 换成 [x] 来选择) -->
- [ ] 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 <!-- 实际行为 -->
<!-- Please provide at least one of the following information (请至少提供以下的一项信息) -->
- 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 <!-- Like Browser, System, Screenshots -->
================================================
FILE: .github/ISSUE_TEMPLATE/other.md
================================================
---
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 <!-- 我确认我已经查看了 -->
<!-- Change [ ] to [x] to select (将 [ ] 换成 [x] 来选择) -->
- [ ] 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 <!-- Like Browser, System, Screenshots -->
================================================
FILE: .github/ISSUE_TEMPLATE/question.md
================================================
---
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 <!-- 我确认我已经查看了 -->
<!-- Change [ ] to [x] to select (将 [ ] 换成 [x] 来选择) -->
- [ ] 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 <!-- 实际行为 -->
<!-- Please provide at least one of the following information (请至少提供以下的一项信息) -->
- 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
<!-- Paste output from `node -v && npm -v` (粘贴 `node -v && npm -v` 输出的信息) -->
```
```
### Package dependencies Information
<!-- Paste output from `npm ls --depth 0` (粘贴 `npm ls --depth 0` 输出的信息) -->
```
```
### Hexo Configuration
<!-- Paste configuration from Hexo `_config.yml` (粘贴 Hexo `_config.yml` 中的内容) -->
```yml
```
### NexT Configuration
<!-- Paste ONLY CHANGED CONFIGURATION from NexT `_config.yml` (只粘贴 NexT 主题配置文件 `_config.yml` 中修改过的部分) -->
```yml
```
## Other Information <!-- Like Browser, System, Screenshots -->
================================================
FILE: .github/PULL_REQUEST_TEMPLATE.md
================================================
<!-- ATTENTION!
1. Please write pull request readme in English, thanks!
2. Always remember that NexT includes 4 schemes. And if on one of them works fine after the changes, on another scheme this changes can be broken. Muse and Mist have similar structure, but Pisces is very difference from them. Gemini is a mirror of Pisces with some styles and layouts remakes. So, please make the tests at least on two schemes (Muse or Mist and Pisces or Gemini).
3. In addition, you need to confirm that the changes made by this PR are compatible with PJAX and Dark Mode.
-->
## PR Checklist <!-- 我确认我已经查看了 -->
<!-- Change [ ] to [x] to select (将 [ ] 换成 [x] 来选择) -->
- [ ] 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).
<!-- For adding Docs edit needed file here: https://github.com/theme-next/theme-next.org/tree/source/source/docs and create PR with this changes here: https://github.com/theme-next/theme-next.org/pulls -->
## PR Type
<!-- What kind of change does this PR introduce? -->
- [ ] Bugfix.
- [ ] Feature.
- [ ] Code style update (formatting, local variables).
- [ ] Refactoring (no functional changes, no api changes).
- [ ] Build & CI related changes.
- [ ] Documentation.
- [ ] Translation. <!-- We use Crowdin to manage translations https://i18n.theme-next.org -->
- [ ] Other... Please describe:
## What is the current behavior?
<!-- Please describe the current behavior that you are modifying, or link to a relevant issue -->
Issue resolved: N/A
## What is the new behavior?
<!-- Description about this pull, in several words -->
- Screenshots with this changes: N/A
- Link to demo site with this changes: N/A
### How to use?
In NexT `_config.yml`:
```yml
```
================================================
FILE: .github/config.yml
================================================
# =============================================================================================== #
# 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
================================================
FILE: .github/issue-close-app.yml
================================================
# 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.
================================================
FILE: .github/issue_label_bot.yaml
================================================
label-alias:
bug: 'Bug'
feature_request: 'Feature Request'
question: 'Question'
================================================
FILE: .github/lock.yml
================================================
# 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
================================================
FILE: .github/mergeable.yml
================================================
# 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
================================================
FILE: .github/release-drafter.yml
================================================
# 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'
================================================
FILE: .github/stale.yml
================================================
# 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
================================================
FILE: .github/support.yml
================================================
# 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
================================================
FILE: .gitignore
================================================
.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/
================================================
FILE: .stylintrc
================================================
{
"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
}
================================================
FILE: .travis.yml
================================================
language: node_js
node_js: node
cache:
npm: true
install: npm install
================================================
FILE: LICENSE.md
================================================
# <div align="center">«NexT» – Elegant and powerful theme for Hexo.</div>
<p align="center">Copyright © 2017 «<a href="https://github.com/theme-next/hexo-theme-next">NexT</a>».</p>
<p align="center">Detail attribution information for «NexT»<br>
is contained in the '<a href="docs/AUTHORS.md">docs/AUTHORS.md</a>' file.</p>
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
<p align="center">This license also available in <a href="docs/LICENSE.txt">text format</a>.</p>
[AUTHORS]: docs/AUTHORS.md
[AGPL3]: docs/AGPL3.md
[AGPL3-7]: docs/AGPL3.md/#7-additional-terms
[AGPL3-15]: docs/AGPL3.md/#15-disclaimer-of-warranty
================================================
FILE: README.md
================================================
<div align="right">
Language:
🇺🇸
<a title="Chinese" href="docs/zh-CN/README.md">🇨🇳</a>
<a title="Russian" href="docs/ru/README.md">🇷🇺</a>
</div>
# <div align="center"><a title="NexT website repository" href="https://github.com/theme-next/theme-next.org"><img align="center" width="56" height="56" src="https://raw.githubusercontent.com/theme-next/hexo-theme-next/master/source/images/logo.svg?sanitize=true"></a> e x T</div>
<p align="center">
«NexT» is a high quality elegant <a href="https://hexo.io">Hexo</a> theme. It is crafted from scratch with love.
<br>
<br>
<a href="https://www.npmjs.com/package/hexo-theme-next"><img src="https://img.shields.io/github/package-json/v/theme-next/hexo-theme-next?style=flat-square"></a>
<a href="https://nodejs.org"><img src="https://img.shields.io/badge/node-%3E=10.9.0-green?style=flat-square"></a>
<a href="https://hexo.io"><img src="https://img.shields.io/badge/hexo-%3E=4.0.0-blue?style=flat-square&logo=hexo"></a>
<a href="https://github.com/theme-next/hexo-theme-next/blob/master/LICENSE.md"><img src="https://img.shields.io/badge/license-%20AGPL-orange?style=flat-square&logo=gnu"></a>
<br>
<a href="https://bestpractices.coreinfrastructure.org/projects/2625"><img src="https://img.shields.io/cii/level/2625?style=flat-square" title="Core Infrastructure Initiative Best Practices"></a>
<a href="https://travis-ci.org/theme-next/hexo-theme-next?branch=master"><img src="https://img.shields.io/travis/theme-next/hexo-theme-next/master?style=flat-square&logo=travis%20ci" title="Travis CI [Linux]"></a>
<a href="https://app.codacy.com/manual/theme-next/hexo-theme-next/dashboard"><img src="https://img.shields.io/codacy/grade/72f7fe7609c2438a92069f448e5a341a/master?style=flat-square&logo=codacy" title="Project Grade"></a>
<img src="https://img.shields.io/snyk/vulnerabilities/github/theme-next/hexo-theme-next?style=flat-square" title="Vulnerabilities">
<br>
<img src="https://user-images.githubusercontent.com/16272760/63487983-da41b080-c4df-11e9-951c-64883a8a5e9b.png">
</p>
## Live Preview
<p align="center">
💟 <a href="https://muse.theme-next.org">Muse</a> | 🔯 <a href="https://mist.theme-next.org">Mist</a> | ♓️ <a href="https://pisces.theme-next.org">Pisces</a> | ♊️ <a href="https://theme-next.org">Gemini</a>
<br>
<br>
More «NexT» examples <a href="https://github.com/theme-next/awesome-next#live-preview">here</a>.
</p>
## 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
<p align="center">
«NexT» send special thanks to these great services that sponsor our core infrastructure:
<br>
<br>
<a href="https://github.com"><img align="center" width="100" src="https://github.githubassets.com/images/modules/logos_page/GitHub-Logo.png"></a>
<a href="https://www.netlify.com"><img align="center" width="150" src="https://cdn.netlify.com/15ecf59b59c9d04b88097c6b5d2c7e8a7d1302d0/1b6d6/img/press/logos/full-logo-light.svg"></a>
<br>
<br>
<sub>GitHub allows us to host the Git repository, Netlify allows us to distribute the documentation.</sub>
<br>
<br>
<a href="https://crowdin.com"><img align="center" width="180" src="https://support.crowdin.com/assets/logos/crowdin-logo1-small.png"></a>
<br>
<br>
<sub>Crowdin allows us to translate conveniently the documentation.</sub>
<br>
<br>
<a href="https://codacy.com"><img align="center" width="155" src="https://user-images.githubusercontent.com/16944225/55026017-623f8f00-5002-11e9-88bf-0d6a5884c6c2.png"></a>
<a href="https://travis-ci.com"><img align="center" width="140" src="https://raw.githubusercontent.com/travis-ci/travis-web/master/public/images/logos/TravisCI-Full-Color.png"></a>
<br>
<br>
<sub>Codacy allows us to monitor code quality, Travis CI allows us to run the test suite.</sub>
</p>
[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
================================================
FILE: _config.yml
================================================
# ---------------------------------------------------------------
# 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: <required> # Your Google account E-Mail
api_key: <required>
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 <body>.
global:
external: true
family: Lato
size:
# Font settings for site title (.site-title).
title:
external: true
family:
size:
# Font settings for headlines (<h1> to <h6>).
headings:
external: true
family:
size:
# Font settings for posts (.post-body).
posts:
external: true
family:
# Font settings for <code> 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: # <your_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: # <app_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: # <app_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: # <app_id>
# Growingio Analytics
growingio_analytics: # <project_id>
# 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: # <your app id>
app_key: # <your app key>
# Required for apps from CN region
server_url: # <your 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
================================================
FILE: crowdin.yml
================================================
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
================================================
FILE: docs/AGPL3.md
================================================
# <div align="center">GNU Affero General Public License<div>
<p align="center">Version 3, 19 November 2007 Copyright © 2007 Free Software Foundation, Inc. <http://fsf.org/></p>
<p align="center">Everyone is permitted to copy and distribute verbatim copies
of this license document, but changing it is not allowed.</p>
## <div align="center">Preamble</div>
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.
## <div align="center">TERMS AND CONDITIONS</div>
### 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.
## <div align="center">END OF TERMS AND CONDITIONS</div>
### <div align="center">How to Apply These Terms to Your New Programs</div>
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.
<one line to give the program's name and a brief idea of what it does.>
Copyright (C) <year> <name of author>
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 <http://www.gnu.org/licenses/>.
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
<<http://www.gnu.org/licenses/>>.
================================================
FILE: docs/ALGOLIA-SEARCH.md
================================================
<h1 align="center">Algolia Search</h1>
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
...
```
<h2 align="center">Known Issues</h2>
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`
================================================
FILE: docs/AUTHORS.md
================================================
# <div align="center">«NexT» Authors</div>
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.
================================================
FILE: docs/DATA-FILES.md
================================================
<h1 align="center">Data Files</h1>
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.
<h2 align="center">Option 1: Hexo-Way</h2>
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, <kbd>CTRL</kbd> + <kbd>]</kbd>).\
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)
<h2 align="center">Option 2: NexT-Way</h2>
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).
<p align="center">And after that steps there are <b>2 variants</b>, need to <b>choose only one</b> of them and <b>resume next steps</b>.</p>
* **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)
================================================
FILE: docs/INSTALLATION.md
================================================
<h1 align="center">Installation</h1>
<h2 align="center">Step 1 → Go to Hexo dir</h2>
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
```
<h2 align="center">Step 2 → Get NexT</h2>
<p align="center">Download theme from GitHub.<br>
There are <b>3 options</b> to do it, need to <b>choose only one</b> of them.</p>
### 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
```
<h2 align="center">Step 3 → Set it up</h2>
Set theme in main **Hexo root config** `_config.yml` file:
```yml
theme: next
```
[download-latest-url]: https://github.com/theme-next/hexo-theme-next/archive/master.zip
[releases-latest-url]: https://github.com/theme-next/hexo-theme-next/releases/latest
[releases-url]: https://github.com/theme-next/hexo-theme-next/releases
[tags-url]: https://github.com/theme-next/hexo-theme-next/tags
[commits-url]: https://github.com/theme-next/hexo-theme-next/commits/master
[git-url]: http://lmgtfy.com/?q=linux+git+install
[curl-tar-url]: http://lmgtfy.com/?q=linux+curl+tar+install
[curl-tar-wget-url]: http://lmgtfy.com/?q=linux+curl+tar+wget+install
[update-with-git-url]: https://github.com/theme-next/hexo-theme-next/blob/master/README.md#update
[docs-data-files-url]: https://github.com/theme-next/hexo-theme-next/blob/master/docs/DATA-FILES.md
================================================
FILE: docs/LEANCLOUD-COUNTER-SECURITY.md
================================================
<h1 align="center">Fix LeanCloud Counter Plugin Security Vulnerability</h1>
Before you make the config, please upgrade your NexT version to v6.0.6 or greater.
Please note the difference between **site config file** and **theme config file**
---
# Sign up to LeanCloud and create an app
- Go to LeanCloud website [leancloud.app](https://leancloud.app) and sign up to LeanCloud. Then login.
- Click `1` to enter the console:
- Then click `1` to create an app:
- Type your app name in `1` in the pop up window(eg. "test"), then choose `2`, which means developer's plan, and then click `3` to create the app:
# Create Counter class and enable plugin in NexT
- Click `1` (app name) to enter the app manage page:
- then click `1` to create a class for counter:
- Type `Counter` in the pop up window in `1`, check `2`, then click `3`:
- Click `1` to enter the app setting, then click `2`:
- Paste `App ID` and `App Key` to **theme config file** `_config.yml` like this:
```yml
leancloud_visitors:
enable: true
app_id: # <your app id>
app_key: # <your app key>
# Required for apps from CN region
server_url: # <your server url>
# Dependencies: https://github.com/theme-next/hexo-leancloud-counter-security
security: true
```
- Set domain whitelist: Click `1`, then type your domain into `2` (**protocol, domain and port should be exactly the same**):
# Deploy web engine to avoid your data being changed illegally
- Click `1 -> 2 -> 3` by order
- Click `1`:
- In the pop up window, click `1` to choose type `Hook`, then choose`beforeUpdate` in `2`, choose `Counter` in `3`. Paste code below into `4`, then click `5` to save it:
```javascript
var query = new AV.Query("Counter");
if (request.object.updatedKeys.includes('time')) {
return query.get(request.object.id).then(function (obj) {
if (obj.get("time") > request.object.get("time")) {
throw new AV.Cloud.Error('Invalid update!');
}
return request.object.save();
});
}
```
- Click `1` to deploy after the message in the red rect shows up:
- Click `1` in the pop up：
- Click `1` to close the pop up window after the message in the red rect shows up:
# Set access control for your database
- Open **theme config file** `_config.yml`, set `leancloud_visitors: security` to `true`:
```yml
leancloud_visitors:
enable: true
app_id: # <your app id>
app_key: # <your app key>
# Required for apps from CN region
server_url: # <your server url>
# Dependencies: https://github.com/theme-next/hexo-leancloud-counter-security
security: true
```
- Open cmd then switch to **root path of site**, type commands to install `hexo-leancloud-counter-security` plugin:
```
npm install hexo-leancloud-counter-security
```
- Open **site config file** `_config.yml`, add those config:
```yml
leancloud_counter_security:
enable_sync: true
app_id: <your app id>
app_key: <your app key>
username:
password:
```
- Type command:
```
hexo lc-counter register <username> <password>
```
or
```
hexo lc-counter r <username> <password>
```
Change `<username>` and `<password>` to your own username and password (no need to be the same as leancloud account). They will be used in the hexo deploying.
- Open **site config file** `_config.yml`, change `<username>` and `<password>`to those you set above:
```yml
leancloud_counter_security:
enable_sync: true
app_id: <your app id>
app_key: <your app key>
username: <your username> # will be asked while deploying if be left blank
password: <your password> # recommend to leave it blank for security, will be asked while deploying if be left blank
```
- Add the deployer in the `deploy` of **site config file** `_config.yml`:
```yml
deploy:
- type: git
repo: // your repo
...
- type: leancloud_counter_security_sync
```
- Return to the LeanCloud console. Click `1 -> 2`, check if there is a record added in the `_User` (the img below is using username "admin" for example):
- Click `1 -> 2 -> 3` by order:
- <del>Click `1` (add_fields), then choose `2`:</del> Do as below "create" setting(choose the user you create):
- click `1` (create), then choose `2`, type the username in `3`, then click `4 -> 5`:
Now your page should be similar to this img after finishing the step.
- Click `1` (delete), then choose `2`:
Now the bug is fixed.
---
See detailed version here: https://leaferx.online/2018/03/16/lc-security-en/
================================================
FILE: docs/LICENSE.txt
================================================
«NexT» – Elegant and powerful theme for Hexo.
Copyright © 2017 «NexT» (github.com/theme-next/hexo-theme-next).
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
as published by the Free Software Foundation with the addition of the
following permission added to Section 15 as permitted in Section 7(a):
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) 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/*') 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:
```
footer:
theme:
enable: true
```
Collaborators, best contributors and all authors specified in the
'docs/AUTHORS.md' 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
================================================
FILE: docs/MATH.md
================================================
<h1 align="center">Math Equations</h1>
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.
<h2 align="center">Provided Render Engine</h2>
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)
<h2 align="center">Configuration Specifications</h2>
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
<!-- This post will render the Math Equations -->
---
title: 'Will Render Math'
mathjax: true
---
....
```
```md
<!-- This post will NOT render the Math Equations -->
---
title: 'Not Render Math'
mathjax: false
---
....
```
```md
<!-- This post will NOT render the Math Equations either -->
---
title: 'Not Render Math Either'
---
....
```
When you set it to `false`, the math will be rendered on **EVERY PAGE**.
================================================
FILE: docs/UPDATE-FROM-5.1.X.md
================================================
<h1 align="center">Update from NexT v5.1.x</h1>
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).
================================================
FILE: docs/ru/DATA-FILES.md
================================================
<h1 align="center">Дата Файлы</h1>
Обновление темы NexT через пулы проходит не слишком гладко. Часто происходит конфликтная ситуация при обновлении по команде `git pull`, хотя её и можно обойти, если смерджить настройки в файле конфигурации вручную.
На данный момент, пользователи хранят одни настройки в корневом `_config.yml` (Hexo), а другие настройки в конфиге темы `_config.yml` (NexT). И всё вроде бы ничего, но имеются некоторые недостатки:
1. Конфигурация разделяется на две части.
2. Пользователи могут запутаться, в каком файле какие должны быть настройки.
Во избежании проблемы, NexT предлагает два варианта.
<h2 align="center">Способ 1: Hexo-Путь</h2>
Используя этот способ, вся конфигурация будет раположена в корневом конфиге 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: выделяем все строки, <kbd>CTRL</kbd> + <kbd>]</kbd>).\
2.2. Добавляем `theme_config:` параметр перед всеми этими настройками.
### Полезные ссылки
* [Конфигурация Hexo](https://hexo.io/ru/docs/configuration.html)
* [Hexo Pull #757](https://github.com/hexojs/hexo/pull/757)
<h2 align="center">Способ 2: NexT-Путь</h2>
Используя этот способ, вся конфигурация будет храниться в одном файле (`/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`, если отсутствует).
<p align="center">И после этих шагов есть <b>2 варианта</b>, нужно <b>выбрать только 1</b> из них и <b>продолжить следующие шаги</b>.</p>
* **Вариант 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)
================================================
FILE: docs/ru/INSTALLATION.md
================================================
<h1 align="center">Установка</h1>
<h2 align="center">Шаг 1 → Идём в директорию Hexo</h2>
Меняем каталог на **корневой hexo**. Там должны находиться `node_modules`, `source`, `themes` и другие папки:
```sh
$ cd hexo
$ ls
_config.yml node_modules package.json public scaffolds source themes
```
<h2 align="center">Шаг 2 → Скачиваем NexT</h2>
<p align="center">Скачиваем тему с GitHub.<br>
Имеются <b>3 способа</b> как зделать это, нужно <b>выбрать только 1</b> из них.</p>
### Способ 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
```
<h2 align="center">Шаг 3 → Конфигурируем</h2>
Устанавливаем параметр темы в конфиге `_config.yml` **корневой директории hexo**:
```yml
theme: next
```
[download-latest-url]: https://github.com/theme-next/hexo-theme-next/archive/master.zip
[releases-latest-url]: https://github.com/theme-next/hexo-theme-next/releases/latest
[releases-url]: https://github.com/theme-next/hexo-theme-next/releases
[tags-url]: https://github.com/theme-next/hexo-theme-next/tags
[commits-url]: https://github.com/theme-next/hexo-theme-next/commits/master
[git-url]: http://lmgtfy.com/?q=linux+git+install
[curl-tar-url]: http://lmgtfy.com/?q=linux+curl+tar+install
[curl-tar-wget-url]: http://lmgtfy.com/?q=linux+curl+tar+wget+install
[update-with-git-url]: https://github.com/theme-next/hexo-theme-next/blob/master/docs/ru/README.md#%D0%A3%D1%81%D1%82%D0%B0%D0%BD%D0%BE%D0%B2%D0%BA%D0%B0
[docs-data-files-url]: https://github.com/theme-next/hexo-theme-next/blob/master/docs/ru/DATA-FILES.md
================================================
FILE: docs/ru/README.md
================================================
<div align="right">
Язык:
<a title="Английский" href="../../README.md">🇺🇸</a>
<a title="Китайский" href="../zh-CN/README.md">🇨🇳</a>
🇷🇺
</div>
# <div align="center"><a title="Репозиторий сайта NexT" href="https://github.com/theme-next/theme-next.org"><img align="center" width="56" height="56" src="https://raw.githubusercontent.com/theme-next/hexo-theme-next/master/source/images/logo.svg?sanitize=true"></a> e x T</div>
<p align="center">
«NexT» — элегантная высококачественная тема под <a href="https://hexo.io">Hexo</a>. Сделана с нуля, с любовью.
<br>
<br>
<a href="https://www.npmjs.com/package/hexo-theme-next"><img src="https://img.shields.io/github/package-json/v/theme-next/hexo-theme-next?style=flat-square"></a>
<a href="https://nodejs.org"><img src="https://img.shields.io/badge/node-%3E=10.9.0-green?style=flat-square"></a>
<a href="https://hexo.io"><img src="https://img.shields.io/badge/hexo-%3E=4.0.0-blue?style=flat-square&logo=hexo"></a>
<a href="https://github.com/theme-next/hexo-theme-next/blob/master/LICENSE.md"><img src="https://img.shields.io/badge/license-%20AGPL-orange?style=flat-square&logo=gnu"></a>
<br>
<a href="https://bestpractices.coreinfrastructure.org/projects/2625"><img src="https://img.shields.io/cii/level/2625?style=flat-square" title="Инициатива базовой инфраструктуры: передовой опыт"></a>
<a href="https://travis-ci.org/theme-next/hexo-theme-next?branch=master"><img src="https://img.shields.io/travis/theme-next/hexo-theme-next/master?style=flat-square&logo=travis%20ci" title="Travis CI [Linux]"></a>
<a href="https://app.codacy.com/manual/theme-next/hexo-theme-next/dashboard"><img src="https://img.shields.io/codacy/grade/72f7fe7609c2438a92069f448e5a341a/master?style=flat-square&logo=codacy" title="Оценка проекта"></a>
<img src="https://img.shields.io/snyk/vulnerabilities/github/theme-next/hexo-theme-next?style=flat-square" title="Vulnerabilities">
<br>
<img src="https://user-images.githubusercontent.com/16272760/63487983-da41b080-c4df-11e9-951c-64883a8a5e9b.png">
</p>
## Демо
<p align="center">
💟 <a href="https://muse.theme-next.org">Muse</a> | 🔯 <a href="https://mist.theme-next.org">Mist</a> | ♓️ <a href="https://pisces.theme-next.org">Pisces</a> | ♊️ <a href="https://theme-next.org">Gemini</a>
<br>
<br>
Больше примеров «NexT» <a href="https://github.com/theme-next/awesome-next#live-preview">здесь</a>.
</p>
## Установка
Простейший вариант установки — склонировать весь репозиторий:
```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]
Приветсвуется любое содействие, не стесняйтесь сообщать «Баги», брать «Форки» и вливать «Пулы».
## Благодарности
<p align="center">
«NexT» выражает особую благодарность этим замечательным сервисам, которые спонсируют нашу основную инфраструктуру:
<br>
<br>
<a href="https://github.com"><img align="center" width="100" src="https://github.githubassets.com/images/modules/logos_page/GitHub-Logo.png"></a>
<a href="https://www.netlify.com"><img align="center" width="150" src="https://cdn.netlify.com/15ecf59b59c9d04b88097c6b5d2c7e8a7d1302d0/1b6d6/img/press/logos/full-logo-light.svg"></a>
<br>
<sub>GitHub позволяет нам хостить Git-репозиторий, Netlify позволяет нам деплоить документацию.</sub>
<br>
<br>
<a href="https://crowdin.com"><img align="center" width="180" src="https://support.crowdin.com/assets/logos/crowdin-logo1-small.png"></a>
<br>
<sub>Crowdin позволяет нам удобно переводить документацию.</sub>
<br>
<br>
<a href="https://codacy.com"><img align="center" width="155" src="https://user-images.githubusercontent.com/16944225/55026017-623f8f00-5002-11e9-88bf-0d6a5884c6c2.png"></a>
<a href="https://travis-ci.com"><img align="center" width="140" src="https://raw.githubusercontent.com/travis-ci/travis-web/master/public/images/logos/TravisCI-Full-Color.png"></a>
<br>
<sub>Codacy позволяет нам контролировать качество кода, Travis CI позволяет нам запускать набор тестов.</sub>
</p>
[docs-installation-url]: https://github.com/theme-next/hexo-theme-next/blob/master/docs/ru/INSTALLATION.md
[docs-data-files-url]: https://github.com/theme-next/hexo-theme-next/blob/master/docs/ru/DATA-FILES.md
[docs-update-5-1-x-url]: https://github.com/theme-next/hexo-theme-next/blob/master/docs/ru/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
================================================
FILE: docs/ru/UPDATE-FROM-5.1.X.md
================================================
<h1 align="center">Обновление из-под NexT v5.1.x</h1>
Между версией 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).
================================================
FILE: docs/zh-CN/ALGOLIA-SEARCH.md
================================================
<h1 align="center">Algolia 搜索</h1>
NexT 内部提供 Algolia 的搜索功能，要使用此功能请确保所使用的 NexT 版本在 `v5.1.0` 之后。需要注意的是，仅仅将 `next/_config.yml` 中 `algolia_search` 的 `enable` 打开**并不能让你使用 Algolia 搜索**，你还需要**使用对应的 Hexo-Algolia 插件** 才能真正在博客页面中使用 Algolia 搜索。按照下面介绍的步骤操作即可完成 Algolia 搜索的安装。
1. 前往 [Algolia 注册页面](https://www.algolia.com/)，注册一个新账户。 可以使用 GitHub 或者 Google 账户直接登录，注册后的 14 天内拥有所有功能（包括收费类别的）。之后若未续费会自动降级为免费账户，免费账户 总共有 10,000 条记录，每月有 100,000 的可以操作数。注册完成后，创建一个新的 Index，这个 Index 将在后面使用。
1. 在 `API Keys` 页面找到需要使用的一些配置的值，包括 `Application ID` 和 `Search-Only API Key`。注意，`Admin API Key` 需要保密保存，不要外泄。
1. 编辑 `站点配置文件`，新增以下配置，除了 `chunkSize` 字段，替换成在 Algolia 获取到的值：
```yml
algolia:
applicationID: 'Application ID'
apiKey: 'Search-Only API Key'
indexName: 'indexName'
chunkSize: 5000
```
1. 在 `API Keys` 页面，点击 `All API Keys` 切换到对应的页面中。接着点击 `New API Key` 按钮，来**编辑权限**。在弹出框中找到 ACL ，**输入 addObject、 deleteObject、listIndexes、deleteIndex 权限**，然后点击最下方的 `Create` 按钮。将这个新创建的 API Key 复制到剪贴板，我们称之为 `High-privilege API key`。
1. 在 Index 和 API Key 创建完成后，此时这个 Index 里未包含任何数据。接下来需要安装 [Hexo Algolia](https://github.com/oncletom/hexo-algolia) 扩展，这个扩展的功能是搜集站点的内容并通过 API 发送给 Algolia。前往站点根目录，执行命令安装：
```
$ cd hexo
$ npm install hexo-algolia
```
1. 当配置完成，在站点根目录下执行以下命令来更新上传 Index。请注意观察命令的输出。
```
$ export HEXO_ALGOLIA_INDEXING_KEY=High-privilege API key # 使用 Git Bash
# set HEXO_ALGOLIA_INDEXING_KEY=High-privilege API key # 使用 Windows CMD 命令行
$ hexo clean
$ hexo algolia
```
1. 更改`主题配置文件`，找到 Algolia Search 配置部分，将 `enable` 改为 `true`。同时你需要**关闭**其他搜索插件，如 Local Search 等。你也可以根据需要调整 `labels` 中的文本：
```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. 如果你需要通过 CDN 使用其它版本的 algolia-instant-search ，请根据以下步骤操作。
你需要在`主题配置文件`中的 vendors 字段进行设置：
```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
...
```
<h2 align="center">已知的问题</h2>
1. 考虑到 Algolia 免费账户的限制，目前 [Hexo-Algolia](https://github.com/oncletom/hexo-algolia) 插件最新版本去掉了正文索引功能。
1. [Hexo-Algoliasearch](https://github.com/LouisBarranqueiro/hexo-algoliasearch) 插件提供了正文索引功能，不过需要替换 NEXT 主题中的关键字。对于免费账户，`Record Too Big` 的问题同样存在。
- 替换 `source/js/algolia-search.js` 中所有的 `applicationID` 为 `appId`
- 替换 `layout/_partials/head/head.swig` 中所有的 `applicationID` 为 `appId`
================================================
FILE: docs/zh-CN/CODE_OF_CONDUCT.md
================================================
<div align="right">
语言：
<a title="英语" href="../../.github/CODE_OF_CONDUCT.md">:us:</a>
:cn:
<a title="俄语" href="../ru/CODE_OF_CONDUCT.md">:ru:</a>
</div>
# <div align="center"><a title="Go to homepage" href="https://theme-next.org"><img align="center" width="56" height="56" src="https://raw.githubusercontent.com/theme-next/hexo-theme-next/master/source/images/logo.svg?sanitize=true"></a> e x T</div>
[NexT](https://theme-next.org) 是一个优雅而强大的 [Hexo](https://hexo.io/)主题。在这里，您可以构建一个托管在 [GitHub Pages](https://pages.github.com/) 上的静态博客，分享您的生活，并与新朋友进行交流。
参与者公约用来约束在 [NexT](https://github.com/theme-next/hexo-theme-next) 社区中代码更新、问题交流、请求合并等行为。我们期望所有用户相互尊重，礼貌待人。任何违反这些规则的人都将不会被审核，并会在发现后立即被阻止和驱逐。
## 目录
- [我们的保证](#我们的保证)
- [我们的责任](#我们的责任)
- [我们的标准](#我们的标准)
- [使用范围](#使用范围)
- [强制执行](#强制执行)
- [联系项目维护者](#联系项目维护者)
- [来源](#来源)
## 我们的保证
作为此项目的贡献者和维护者，我们承诺尊重所有做出贡献的用户，这些贡献包括了报告问题、发布功能请求、更新文档、提交合并请求以及其他活动。
为了促进一个开放透明且友好的环境，我们作为贡献者和维护者保证：无论年龄、种族、民族、性别认同和表达（方式）、体型、身体健全与否、经验水平、国籍、个人表现、宗教或性别取向，参与者在我们项目和社区中都免于骚扰。
## 我们的责任
项目维护者有责任为「可接受的行为」标准做出诠释，有权利及责任去删除、编辑、拒绝与本行为标准有所违背的评论（comments）、提交（commits）、代码、wiki 编辑、问题（issues）和其他贡献，以及项目维护者可暂时或永久性的禁止任何他们认为有不适当、威胁、冒犯、有害行为的贡献者。
## 我们的标准
作为 GitHub 上的一个项目，本项目受到 [GitHub 社区准则](https://help.github.com/articles/github-community-guidelines/)的约束。 此外，作为 npm 托管的项目，[npm 公司的行为准则](https://www.npmjs.com/policies/conduct)也涵盖了本项目。
有助于创造正面环境的行为包括但不限于：
* 使用友好和包容性语言
* 尊重不同的观点和经历
* 耐心地接受建设性批评
* 关注对社区最有利的事情
* 友善对待其他社区成员
身为参与者不能接受的行为包括但不限于：
* 使用与性有关的言语或是图像，以及不受欢迎的性骚扰
* 捣乱/煽动/造谣的行为或进行侮辱/贬损的评论，人身攻击及政治攻击
* 公开或私下的骚扰
* 未经许可地发布他人的个人资料，例如住址或是电子地址
* 其他可以被合理地认定为不恰当或者违反职业操守的行为
## 使用范围
当一个人代表该项目或是其社区时，本行为标准适用于其项目社区和公共社区。
根据某人在本社区范围以外发生的违规情况，项目维护者可以认为其不受欢迎，并采取适当措施来保证所有成员的安全性和舒适性。
## 强制执行
如果您看到违反行为准则的行为，请按以下步骤操作：
1. 让这个人知道他所做的并不合适，并要求他停止或编辑他们的提交信息。该人应立即停止行为并纠正问题。
2. 如果该人没有纠正其行为，或者您不方便与其沟通，请[联系项目维护者](#联系项目维护者)。上报时，请尽可能多的提供详细信息，链接，截图，上下文或可用于更好地理解和解决情况的其他信息。
3. 收到上报信息后，项目维护者会查看问题，并采取进一步的措施。
一旦项目维护者参与其中，他们将遵循以下一系列步骤，并尽力保护项目成员的利益。任何维护团队认为有必要且适合的所有投诉都将进行审查及调查，并做出相对应的回应。项目小组有对事件回报者有保密的义务。具体执行的方针近一步细节可能会单独公布。
以下是项目维护者根据需要采取的进一步执法步骤：
1. 再次要求停止违规行为。
2. 如果违规者还是没有回应，将会受到正式的警告，并收到项目维护者的移除或修改消息。同时，相关的问题或合并请求将会被锁定。
3. 如果警告后违规行为继续出现，违规者将会被禁言 24 小时。
4. 如果禁言后违规行为继续出现，违规者将会被处罚长期（6-12个月）禁言。
除此之外，项目维护者可以根据需要删除任何违规的消息，图片，贡献等。如果违规行为被认为是对社区成员的严重或直接威胁，包括任何置社区成员于风险的威胁、身体或言语攻击，项目维护者有充分权利自行决定跳过上述任何步骤。
没有切实地遵守或是执行本行为标准的项目维护人员，可能会因项目领导人或是其他成员的决定，暂时或是永久地取消其参与资格。
## 联系项目维护者
您可以通过以下任何方法与维护人员联系
* 电子邮件:
* [support@theme-next.org](mailto:support@theme-next.org)
* 即时通信:
* [Gitter](https://gitter.im/theme-next)
* [Riot](https://riot.im/app/#/room/#NexT:matrix.org)
* [Telegram](https://t.me/joinchat/GUNHXA-vZkgSMuimL1VmMw)
## 来源
本行为标准改编自[Contributor Covenant](https://www.contributor-covenant.org/) 和 [WeAllJS Code of Conduct](https://wealljs.org/code-of-conduct)。
================================================
FILE: docs/zh-CN/CONTRIBUTING.md
================================================
<div align="right">
语言：
<a title="英语" href="../../.github/CONTRIBUTING.md">:us:</a>
:cn:
<a title="俄语" href="../ru/CONTRIBUTING.md">:ru:</a>
</div>
# <div align="center"><a title="Go to homepage" href="https://theme-next.org"><img align="center" width="56" height="56" src="https://raw.githubusercontent.com/theme-next/hexo-theme-next/master/source/images/logo.svg?sanitize=true"></a> e x T</div>
首先，非常感谢大家抽出宝贵时间来让我们的 NexT 主题越变越好。在这里，我们介绍一下 [NexT 主题及其子模块](https://github.com/theme-next) 的开源贡献指南。不过，我们希望大家不要局限于此，更欢迎大家随时进行补充。
## 目录
[如何为 NexT 做贡献](#如何为-next-做贡献)
* [你需要了解的](#你需要了解的)
* [阅读文档](#阅读文档)
* [快速调试指南](#快速调试指南)
* [反馈 Bug](#反馈-bug)
* [提交漏洞](#提交漏洞)
* [提交功能需求](#提交功能需求)
* [提交合并请求](#提交合并请求)
* [发布版本](#发布版本)
[规范](#规范)
* [行为规范](#行为规范)
* [编码规范](#编码规范)
* [标签规范](#标签规范)
* [提交信息规范](#提交信息规范)
## 如何为 NexT 做贡献
### 你需要了解的
#### 阅读文档
如果你在使用过程中遇到了问题，你可以查阅 [FAQs](https://theme-next.org/docs/faqs) 或者 [NexT 帮助文档](https://theme-next.org/docs/troubleshooting)。
另外，你也可以通过 [这里](https://github.com/theme-next/hexo-theme-next/search?q=&type=Issues&utf8=%E2%9C%93) 进行大致检索，有些问题已经得到解答，你可以自行解决。对于没有解决的 Issue，你也可以继续提问。
#### 快速调试指南
在 GitHub 上提交 Issue 前，请先通过以下方法 debug：
* 执行`hexo clean`，清除浏览器缓存，并禁用 CDN 服务（例如 Cloudflare Rocket Loader）；
* 切换到其它主题并检查 bug 是否仍然存在（例如使用默认主题 landscape）。换言之，证明这是 NexT 主题而非来自 Hexo 的 bug；
* 将 NexT 主题升级到最新版；
* 将 Hexo 和 Hexo 插件升级到最新版；
* 将 Node.js 和 `npm` 升级到最新版；
* 卸载不必要的 Hexo 插件，或重新通过 `npm install --save` 安装插件。
如果你得到了来自 Hexo 或浏览器控制台的报错信息，请在 Google / Stackoverflow / GitHub Issue 中搜寻，或在提交 Issue 时报告给我们。
如果你在使用过程中发现了 Bug，请再次确认 Bug 在 [最新发布版本](https://github.com/theme-next/hexo-theme-next/releases/latest) 中是否重现。如果 Bug 重现，欢迎你到我们的 [主题仓库](https://github.com/theme-next/hexo-theme-next) 中 [反馈 Bug](#reporting-bugs) 或者 [提交功能需求](#提交功能需求)，也更期待您 [提交合并请求](#提交合并请求)。
### 反馈 Bug
反馈 Bug 前，请再次确认您已经查看了 [你需要了解的](#你需要了解的) 内容，避免提交重复的 Issue。确定相关仓库后，创建 Issue 并按照 [模板](../../.github/ISSUE_TEMPLATE.md) 尽可能的详细填写相关信息。
请认真遵守如下指南，这样我们才能更好地理解问题，重现问题和解决问题。
* 在标题中清晰准确地描述你的问题。
* 参照如下问题尽可能多的提供信息：
* Bug 是否能够重现？是一直出现还是偶尔出现？
* Bug 是从什么时候开始发生的？
* 如果 Bug 突然发生，使用 [旧版本主题](https://github.com/theme-next/hexo-theme-next/releases) 是否能够重现 Bug？又是从哪个版本开始出现 Bug？
* 你所使用 Node，Hexo 以及 Next 的版本号多少？你可以运行 `node -v` 和 `hexo version` 获取版本号，或者查看文件 `package.json` 的内容。
* 你使用了哪些插件包？查看文件 `package.json` 的内容即可获取。
* 一步步详细你是如何重现 Bug 的，做了什么，使用了哪些功能等等。如果你需要展示代码段，请使用 [Markdown 代码块](https://help.github.com/articles/creating-and-highlighting-code-blocks/) 或 [Github 预览链接](https://help.github.com/articles/creating-a-permanent-link-to-a-code-snippet/) 或 [Gist 链接](https://gist.github.com/)。
* 提供 Bug 的样例，如图像文件、在线演示网址等等。
* 详细描述通过上述重现过程出现的问题。
* 详细描述你期待的结果。
#### 提交漏洞
如果你发现安全问题，请以负责任的方式行事，即不要在公共 Issue 中提交而是直接向我们反馈，这样我们就可以在漏洞被利用之前对其进行修复。请将相关信息发送到 security@theme-next.com（可接受 PGP 加密邮件）。
我们很乐意对任何提交漏洞的人予以特别感谢以便我们修复它。如果你想保持匿名性或使用笔名替代，请告诉我们。我们将充分尊重你的意愿。
### 提交功能需求
提交功能需求前，请再次确认您已经查看了 [你需要了解的](#你需要了解的) 内容，避免提交重复的 Issue。确定相关仓库后，创建 Issue 并按照 [模板](../../.github/ISSUE_TEMPLATE.md) 尽可能的详细填写相关信息。
请认真遵守如下指南，这样我们才能更好地理解和开发功能需求:pencil:：
* 在标题中清晰准确地描述你的功能需求。
* 详细描述目前所具有的功能和你所期待的功能，并解释为什么需要该功能。
* 提供功能需求的样例，如图像文件、在线演示网址等等。
### 提交合并请求
提交合并请求前，请再次确认您已经查看了 [你需要了解的](#你需要了解的) 内容，避免提交重复的合并请求。确定相关仓库后，创建合并请求。更多详细操作过程可以查看 [帮助文档](https://help.github.com/articles/creating-a-pull-request/)。
请认真遵守如下指南，这样我们才能更好地理解你的合并请求：
* 创建合并请求时，请遵守 [编码规范](#编码规范) 和 [提交信息规范](#提交信息规范)。
* 在标题中清晰准确地描述你的合并请求，不要加入 Issue 编号。
* 按照 [模板](../../.github/PULL_REQUEST_TEMPLATE.md) 尽可能的详细填写相关信息。
* 合并请求需要在所有主题样式中测试通过，并提供所表现功能的样例，如图像文件、在线演示网址等等。
### 发布版本
版本发布是将项目发布给用户的一种很好的方式。
1. 进入 GitHub 项目主页，点击 **Releases** 和 **Draft a new release**。
2. 输入你需要发布的版本号。版本控制是基于 [Git tags](https://git-scm.com/book/en/Git-Basics-Tagging) 工作的，建议按照 [About Major and Minor NexT versions](https://github.com/theme-next/hexo-theme-next/issues/187) 确定版本号。
3. 确定你需要发布的分支。除非发布测试版本，通常情况下选择 `master` 分支。
4. 输入发布版本的标题和说明。
- 标题为版本号。
- 所有内容更改的类型包括了 **Breaking Changes**, **Updates**, **Features** 和 **Bug Fixes**。在描述 Breaking Changes 时，使用二级标题分别陈述，描述其他类型时，使用项目列表陈述。
- 使用被动语态，省略主语。
- 所有的变化都需要记录在版本说明中。对于没有使用 PR 的更改，需要添加相应的 commit 编号。如果使用了 PR 进行合并修改，则直接添加相应的 PR 编号即可。
5. 如果您希望随版本一起发布二进制文件（如编译的程序），请在上传二进制文件对话框中手动拖放或选择文件。
6. 如果版本不稳定，请选择 **This is a pre-release**，以通知用户它尚未完全准备好。如果您准备公布您的版本，请点击 **Publish release**。否则，请单击 **Save draft** 以稍后处理。
## 规范
### 行为规范
为了保证本项目的顺利运作，所有参与人都需要遵守 [行为规范](CODE_OF_CONDUCT.md)。
### 编码规范
我们使用 ESLint 和 Stylint 来识别和报告 JavaScript 和 Stylus 中的模式，目的是使代码更加一致并避免错误。编码时应遵循这些规范。
### 标签规范
为了方便维护人员和用户能够快速找到他们想要查看的问题，我们使用“标签”功能对 Pull requests 和 Issues 进行分类。
如果您不确定某个标签的含义，或者不知道将哪些标签应用于 PR 或 issue，千万别错过这个。
Issue 的标签：
- 类型
- `Bug`: 检测到需要进行确认的 Bug
- `Feature Request`: 提出了新功能请求的 Issue
- `Question`: 提出疑问的 Issue
- `Meta`: 表明使用条款变更的 Issue
- `Support`: 被标记为支持请求的 Issue
- `Polls`: 发起投票的 Issue
- 结果
- `Duplicate`: 重复提及的 Issue
- `Irrelevant`: 与 NexT 主题无关的 Issue
- `Invalid`: 无法复现的 Issue
- `Expected Behavior`: 与预期行为相符的 Issue
- `Need More Info`: 需要更多信息的 Issue
- `Verified`: 已经被确认的 Issue
- `Solved`: 已经解决的 Issue
- `Backlog`: 待解决的 Issue
- `Stale`: 由于长期无人回应被封存的 Issue
Pull Request 的标签：
- `Breaking Change`: 产生重大变动的 Pull Request
- `Bug Fix`: 修复相关 Bug 的 Pull Request
- `New Feature`: 添加了新功能的 Pull Request
- `Feature`: 为现有功能提供选项或加成的 Pull Request
- `i18n`: 更新了翻译的 Pull Request
- `Work in Progress`: 仍在进行改动和完善的 Pull Request
- `Skip Release`: 无需在 Release Note 中展现的 Pull Request
两者兼有：
- `Roadmap`: 与 NexT 主题发展相关的 Issue 或者 Pull Request
- `Help Wanted`: 需要帮助的 Issue 或者 Pull Request
- `Discussion`: 需要进行讨论的 Issue 或者 Pull Request
- `Improvement`: 需要改进的 Issue 或者改进了 NexT 主题的 Pull Request
- `Performance`: 提出性能问题的 Issue 或者提高了 NexT 主题性能的 Pull Request
- `Hexo`: 与 Hexo 和 Hexo 插件相关的 Issue 或者 Pull Request
- `Template Engine`: 与模版引擎相关的 Issue 或者 Pull Request
- `CSS`: 与 NexT 主题 CSS 文件相关的 Issue 或者 Pull Request
- `Fonts`: 与 NexT 主题字体相关的 Issue 或者 Pull Request
- `PJAX`: 与 PJAX 相关的 Issue 或者 Pull Request
- `3rd Party Plugin`: 与第三方插件和服务相关的 Issue 或者 Pull Request
- `Docs`: 与文档说明相关的 Issue 或者 Pull Request
- `Configurations`: 与 NexT 主题设置相关的 Issue 或者 Pull Request
### 提交信息规范
我们对项目的 git 提交信息格式进行统一格式约定，每条提交信息由 `type`+`subject` 组成，这将提升项目日志的可读性。
- `type` 用于表述此次提交信息的意义，首写字母大写，包括但不局限于如下类型：
* `Build`：基础构建系统或依赖库的变化
* `Ci`：CI 构建系统及其脚本变化
* `Docs`：文档内容变化
* `Feat`：新功能
* `Fix`：Bug 修复
* `Perf`：性能优化
* `Refactor`：重构（即不是新增功能，也不是修改 Bug 的代码变动）
* `Style`：格式（不影响代码运行的变动）
* `Revert`：代码回滚
* `Release`：版本发布
- `subject` 用于简要描述修改变更的内容，如 `Update code highlighting in readme.md`。
* 句尾不要使用符号。
* 使用现在时、祈使句语气。
================================================
FILE: docs/zh-CN/DATA-FILES.md
================================================
<h1 align="center">数据文件</h1>
目前，通过 pull 或下载新的 release 版本来更新 NexT 主题的体验并不平滑。当用户使用 `git pull` 更新 NexT 主题时经常需要解决冲突问题，而在手动下载 release 版本时也经常需要手动合并配置。
现在来说，NexT 推荐用户存储部分配置在 Hexo 站点配置文件（`/_config.yml`），而另一部分在主题配置文件（`/themes/next/_config.yml`）。这一方式固然可用，但也有一些缺点：
1. 配置项被分裂为两部分；
2. 用户难以弄清何处存放配置选项。
为了解决这一问题，NexT 提供了以下两种方案。
<h2 align="center">选择 1：Hexo 方式</h2>
使用这一方式，你的全部配置都将置于 Hexo 站点配置文件（`/_config.yml`），并且不需要修改 `/themes/next/_config.yml`，或者创建什么其他的文件。但是所有用到的主题选项必须放置在 `theme_config` 后，并全部增加两个空格的缩进。
如果在新的 release 中新增了选项，那么你只需要从 `/themes/next/_config.yml` 中将他们复制到 `/_config.yml` 中并将它们的值设置为你想要的。
### 用法
1. 请确认不存在 `/source/_data/next.yml` 文件（如果已存在，请删除）
2. 从主题的 `/themes/next/_config.yml` 文件中复制你需要的 NexT 配置项到 `/_config.yml` 中，然后\
2.1. 所有这些配置项右移两个空格（在 Visual Studio Code 中：选中这些文字，<kbd>CTRL</kbd> + <kbd>]</kbd>）。\
2.2. 在这些参数最上方添加一行 `theme_config:`。
### 相关链接
* [Hexo 配置](https://hexo.io/zh-cn/docs/configuration.html)
* [Hexo Pull #757](https://github.com/hexojs/hexo/pull/757)
<h2 align="center">选择 2: NexT 方式</h2>
使用这一方式，你现在可以将你的全部配置置于同一位置（`/source/_data/next.yml`），并且不需要修改 `/themes/next/_config.yml`。
但是可能无法让所有 Hexo 外部库都准确处理它们的附加选项（举个例子，`hexo-server` 模块只会从 Hexo 默认配置文件中读取选项）。
如果在新的 release 中出现了任何新的选项，那么你只需要从 `/themes/next/_config.yml` 中将他们复制到 `/source/_data/next.yml` 中并设置它们的值为你想要的选项。
这一方法依赖于 Hexo 的[数据文件](https://hexo.io/docs/data-files.html)特性。因为数据文件是在 Hexo 3 中被引入，所以你需要更新至 Hexo 3.0 以后的版本来使用这一特性。
### 用法
1. 请确认你的 Hexo 版本为 3.0 或更高。
2. 在你站点的 `/source/_data` 目录创建一个 `next.yml` 文件（如果 `_data` 目录不存在，请创建之）。
<p align="center">以上步骤之后有 <b>两种选择</b>，请<b>任选其一</b>然后<b>继续后面的步骤</b>。</p>
* **选择 1：`override: false`（默认）**：
1. 检查默认 NexT 配置中的 `override` 选项，必须设置为 `false`。\
在 `next.yml` 文件中，也要设置为 `false`，或者不定义此选项。
2. 从站点配置文件（`/_config.yml`）与主题配置文件（`/themes/next/_config.yml`）中复制你需要的选项到 `/source/_data/next.yml` 中。
* **选择 2：`override: true`**：
1. 在 `next.yml` 中设置 `override` 选项为 `true`。
2. 从 `/themes/next/_config.yml` 配置文件中复制**所有**的 NexT 主题选项到 `/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)
================================================
FILE: docs/zh-CN/INSTALLATION.md
================================================
<h1 align="center">安装</h1>
<h2 align="center">步骤 1 → 进入 Hexo 目录</h2>
进入 **Hexo 根**目录。这一目录中应当有 `node_modules`、`source`、`themes` 等若干子目录：
```sh
$ cd hexo
$ ls
_config.yml node_modules package.json public scaffolds source themes
```
<h2 align="center">步骤 2 → 获取 NexT</h2>
<p align="center">从 GitHub 下载主题。<br>
为了下载这一主题，共有 <b>3 种选项</b>可选。你需要选择其中<b>唯一一个方式</b>。</p>
### 选项 1：下载[最新 release 版本][releases-latest-url]
通常情况下请选择 **stable** 版本。推荐不熟悉的用户按此方式进行。
* 使用 [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
```
这种方式将**仅提供最新的 release 版本**（其中不附带 `.git` 目录）。\
因此，将来你将不可能通过 `git` 更新这一方式安装的主题。\
取而代之的，为了能不丢失你的自定义配置，你可以使用独立的配置文件（例如 [数据文件][docs-data-files-url]）并下载最新版本到旧版本的目录中（或者下载到新的主题目录中并修改 Hexo 配置中的主题名）。
### 选项 2：下载 [tag 指向的 release 版本][releases-url]
在少数情况下将有所帮助，但这并非推荐方式。\
你必须指定一个版本：使用 [tags 列表][tags-url]中的任意 tag 替换 `v6.0.0`。
* 方式 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` 方法相同，但只会下载**指定的 release 版本**。
* 方式 2：使用 [git][git-url] 安装：
```sh
$ git clone --branch v6.0.0 https://github.com/theme-next/hexo-theme-next themes/next
```
这一方式将为你下载**指定的 release 版本**（其中包含 `.git` 目录）。\
并且，你可以随时切换到任何已定义的版本号所对应的 tag 的版本。
### 选项 3：下载[最新 master 分支][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` 方法相同，但只会下载**最新 master 分支版本**。\
在有些情况对开发者有所帮助。
* 方式 2：使用 [git][git-url] 安装：
```sh
$ git clone https://github.com/theme-next/hexo-theme-next themes/next
```
这一方式将为你下载**完整仓库**（其中包含 `.git` 目录）。\
你可以随时[使用 git 更新至最新版本][update-with-git-url]并切换至任何有 tag 标记的 release 版本、最新的 master 分支版本、甚至其他分支。\
在绝大多数情况下对用户和开发者友好。
获取 tags 列表：
```sh
$ cd themes/next
$ git tag -l
…
v6.0.0
v6.0.1
v6.0.2
```
例如，假设你想要切换到 `v6.0.1` 这一 [tag 指向的 release 版本][tags-url]。输入如下指令：
```sh
$ git checkout tags/v6.0.1
Note: checking out 'tags/v6.0.1'.
…
HEAD is now at da9cdd2... Release v6.0.1
```
然后，假设你想要切换回 [master 分支][commits-url]，输入如下指令即可：
```sh
$ git checkout master
```
<h2 align="center">步骤 3 → 完成配置</h2>
在 **Hexo 站点配置文件**（`/_config.yml`）中设置你的主题：
```yml
theme: next
```
[download-latest-url]: https://github.com/theme-next/hexo-theme-next/archive/master.zip
[releases-latest-url]: https://github.com/theme-next/hexo-theme-next/releases/latest
[releases-url]: https://github.com/theme-next/hexo-theme-next/releases
[tags-url]: https://github.com/theme-next/hexo-theme-next/tags
[commits-url]: https://github.com/theme-next/hexo-theme-next/commits/master
[git-url]: http://lmgtfy.com/?q=linux+git+install
[curl-tar-url]: http://lmgtfy.com/?q=linux+curl+tar+install
[curl-tar-wget-url]: http://lmgtfy.com/?q=linux+curl+tar+wget+install
[update-with-git-url]: https://github.com/theme-next/hexo-theme-next/blob/master/docs/zh-CN/README.md#update
[docs-data-files-url]: https://github.com/theme-next/hexo-theme-next/blob/master/docs/zh-CN/DATA-FILES.md
================================================
FILE: docs/zh-CN/LEANCLOUD-COUNTER-SECURITY.md
================================================
<h1 align="center">修复 LeanCl
gitextract_z3btu9dz/
├── .editorconfig
├── .eslintrc.json
├── .gitattributes
├── .github/
│ ├── CODE_OF_CONDUCT.md
│ ├── CONTRIBUTING.md
│ ├── ISSUE_TEMPLATE/
│ │ ├── bug-report.md
│ │ ├── feature-request.md
│ │ ├── other.md
│ │ └── question.md
│ ├── PULL_REQUEST_TEMPLATE.md
│ ├── config.yml
│ ├── issue-close-app.yml
│ ├── issue_label_bot.yaml
│ ├── lock.yml
│ ├── mergeable.yml
│ ├── release-drafter.yml
│ ├── stale.yml
│ └── support.yml
├── .gitignore
├── .stylintrc
├── .travis.yml
├── LICENSE.md
├── README.md
├── _config.yml
├── crowdin.yml
├── docs/
│ ├── AGPL3.md
│ ├── ALGOLIA-SEARCH.md
│ ├── AUTHORS.md
│ ├── DATA-FILES.md
│ ├── INSTALLATION.md
│ ├── LEANCLOUD-COUNTER-SECURITY.md
│ ├── LICENSE.txt
│ ├── MATH.md
│ ├── UPDATE-FROM-5.1.X.md
│ ├── ru/
│ │ ├── DATA-FILES.md
│ │ ├── INSTALLATION.md
│ │ ├── README.md
│ │ └── UPDATE-FROM-5.1.X.md
│ └── zh-CN/
│ ├── ALGOLIA-SEARCH.md
│ ├── CODE_OF_CONDUCT.md
│ ├── CONTRIBUTING.md
│ ├── DATA-FILES.md
│ ├── INSTALLATION.md
│ ├── LEANCLOUD-COUNTER-SECURITY.md
│ ├── MATH.md
│ ├── README.md
│ └── UPDATE-FROM-5.1.X.md
├── gulpfile.js
├── languages/
│ ├── ar.yml
│ ├── de.yml
│ ├── en.yml
│ ├── es.yml
│ ├── fa.yml
│ ├── fr.yml
│ ├── hu.yml
│ ├── id.yml
│ ├── it.yml
│ ├── ja.yml
│ ├── ko.yml
│ ├── nl.yml
│ ├── pt-BR.yml
│ ├── pt.yml
│ ├── ru.yml
│ ├── tr.yml
│ ├── uk.yml
│ ├── vi.yml
│ ├── zh-CN.yml
│ ├── zh-HK.yml
│ └── zh-TW.yml
├── layout/
│ ├── _layout.swig
│ ├── _macro/
│ │ ├── post-collapse.swig
│ │ ├── post.swig
│ │ └── sidebar.swig
│ ├── _partials/
│ │ ├── comments.swig
│ │ ├── footer.swig
│ │ ├── head/
│ │ │ ├── head-unique.swig
│ │ │ └── head.swig
│ │ ├── header/
│ │ │ ├── brand.swig
│ │ │ ├── index.swig
│ │ │ ├── menu-item.swig
│ │ │ ├── menu.swig
│ │ │ └── sub-menu.swig
│ │ ├── languages.swig
│ │ ├── page/
│ │ │ ├── breadcrumb.swig
│ │ │ └── page-header.swig
│ │ ├── pagination.swig
│ │ ├── post/
│ │ │ ├── post-copyright.swig
│ │ │ ├── post-followme.swig
│ │ │ ├── post-footer.swig
│ │ │ ├── post-related.swig
│ │ │ └── post-reward.swig
│ │ ├── search/
│ │ │ ├── algolia-search.swig
│ │ │ ├── index.swig
│ │ │ └── localsearch.swig
│ │ ├── sidebar/
│ │ │ └── site-overview.swig
│ │ └── widgets.swig
│ ├── _scripts/
│ │ ├── index.swig
│ │ ├── noscript.swig
│ │ ├── pages/
│ │ │ └── schedule.swig
│ │ ├── pjax.swig
│ │ ├── schemes/
│ │ │ ├── gemini.swig
│ │ │ ├── mist.swig
│ │ │ ├── muse.swig
│ │ │ └── pisces.swig
│ │ ├── three.swig
│ │ └── vendors.swig
│ ├── _third-party/
│ │ ├── analytics/
│ │ │ ├── baidu-analytics.swig
│ │ │ ├── google-analytics.swig
│ │ │ ├── growingio.swig
│ │ │ └── index.swig
│ │ ├── baidu-push.swig
│ │ ├── chat/
│ │ │ ├── chatra.swig
│ │ │ └── tidio.swig
│ │ ├── comments/
│ │ │ ├── changyan.swig
│ │ │ ├── disqus.swig
│ │ │ ├── disqusjs.swig
│ │ │ ├── gitalk.swig
│ │ │ ├── livere.swig
│ │ │ └── valine.swig
│ │ ├── index.swig
│ │ ├── math/
│ │ │ ├── index.swig
│ │ │ ├── katex.swig
│ │ │ └── mathjax.swig
│ │ ├── quicklink.swig
│ │ ├── rating.swig
│ │ ├── search/
│ │ │ ├── algolia-search.swig
│ │ │ ├── localsearch.swig
│ │ │ └── swiftype.swig
│ │ ├── statistics/
│ │ │ ├── busuanzi-counter.swig
│ │ │ ├── cnzz-analytics.swig
│ │ │ ├── firestore.swig
│ │ │ ├── index.swig
│ │ │ └── lean-analytics.swig
│ │ └── tags/
│ │ ├── mermaid.swig
│ │ └── pdf.swig
│ ├── archive.swig
│ ├── category.swig
│ ├── index.swig
│ ├── page.swig
│ ├── post.swig
│ └── tag.swig
├── package.json
├── scripts/
│ ├── events/
│ │ ├── index.js
│ │ └── lib/
│ │ ├── config.js
│ │ ├── injects-point.js
│ │ └── injects.js
│ ├── filters/
│ │ ├── comment/
│ │ │ ├── changyan.js
│ │ │ ├── common.js
│ │ │ ├── default-config.js
│ │ │ ├── disqus.js
│ │ │ ├── disqusjs.js
│ │ │ ├── gitalk.js
│ │ │ ├── livere.js
│ │ │ └── valine.js
│ │ ├── default-injects.js
│ │ ├── front-matter.js
│ │ ├── locals.js
│ │ ├── minify.js
│ │ └── post.js
│ ├── helpers/
│ │ ├── engine.js
│ │ ├── font.js
│ │ ├── next-config.js
│ │ └── next-url.js
│ ├── renderer.js
│ └── tags/
│ ├── button.js
│ ├── caniuse.js
│ ├── center-quote.js
│ ├── group-pictures.js
│ ├── label.js
│ ├── mermaid.js
│ ├── note.js
│ ├── pdf.js
│ ├── tabs.js
│ └── video.js
└── source/
├── css/
│ ├── _colors.styl
│ ├── _common/
│ │ ├── components/
│ │ │ ├── back-to-top-sidebar.styl
│ │ │ ├── back-to-top.styl
│ │ │ ├── components.styl
│ │ │ ├── pages/
│ │ │ │ ├── breadcrumb.styl
│ │ │ │ ├── categories.styl
│ │ │ │ ├── pages.styl
│ │ │ │ ├── schedule.styl
│ │ │ │ └── tag-cloud.styl
│ │ │ ├── post/
│ │ │ │ ├── post-collapse.styl
│ │ │ │ ├── post-copyright.styl
│ │ │ │ ├── post-eof.styl
│ │ │ │ ├── post-expand.styl
│ │ │ │ ├── post-followme.styl
│ │ │ │ ├── post-gallery.styl
│ │ │ │ ├── post-header.styl
│ │ │ │ ├── post-nav.styl
│ │ │ │ ├── post-reward.styl
│ │ │ │ ├── post-rtl.styl
│ │ │ │ ├── post-tags.styl
│ │ │ │ ├── post-widgets.styl
│ │ │ │ └── post.styl
│ │ │ ├── reading-progress.styl
│ │ │ └── third-party/
│ │ │ ├── gitalk.styl
│ │ │ ├── math.styl
│ │ │ ├── related-posts.styl
│ │ │ ├── search.styl
│ │ │ └── third-party.styl
│ │ ├── outline/
│ │ │ ├── footer/
│ │ │ │ └── footer.styl
│ │ │ ├── header/
│ │ │ │ ├── bookmark.styl
│ │ │ │ ├── github-banner.styl
│ │ │ │ ├── header.styl
│ │ │ │ ├── headerband.styl
│ │ │ │ ├── menu.styl
│ │ │ │ ├── site-meta.styl
│ │ │ │ └── site-nav.styl
│ │ │ ├── mobile.styl
│ │ │ ├── outline.styl
│ │ │ └── sidebar/
│ │ │ ├── sidebar-author-links.styl
│ │ │ ├── sidebar-author.styl
│ │ │ ├── sidebar-blogroll.styl
│ │ │ ├── sidebar-button.styl
│ │ │ ├── sidebar-dimmer.styl
│ │ │ ├── sidebar-nav.styl
│ │ │ ├── sidebar-toc.styl
│ │ │ ├── sidebar-toggle.styl
│ │ │ ├── sidebar.styl
│ │ │ └── site-state.styl
│ │ └── scaffolding/
│ │ ├── base.styl
│ │ ├── buttons.styl
│ │ ├── comments.styl
│ │ ├── highlight/
│ │ │ ├── copy-code.styl
│ │ │ ├── diff.styl
│ │ │ ├── highlight.styl
│ │ │ └── theme.styl
│ │ ├── normalize.styl
│ │ ├── pagination.styl
│ │ ├── scaffolding.styl
│ │ ├── tables.styl
│ │ ├── tags/
│ │ │ ├── blockquote-center.styl
│ │ │ ├── group-pictures.styl
│ │ │ ├── label.styl
│ │ │ ├── note.styl
│ │ │ ├── pdf.styl
│ │ │ ├── tabs.styl
│ │ │ └── tags.styl
│ │ └── toggles.styl
│ ├── _mixins.styl
│ ├── _schemes/
│ │ ├── Gemini/
│ │ │ └── index.styl
│ │ ├── Mist/
│ │ │ ├── _header.styl
│ │ │ ├── _layout.styl
│ │ │ ├── _menu.styl
│ │ │ ├── _posts-expand.styl
│ │ │ └── index.styl
│ │ ├── Muse/
│ │ │ ├── _header.styl
│ │ │ ├── _layout.styl
│ │ │ ├── _menu.styl
│ │ │ ├── _sidebar.styl
│ │ │ ├── _sub-menu.styl
│ │ │ └── index.styl
│ │ └── Pisces/
│ │ ├── _header.styl
│ │ ├── _layout.styl
│ │ ├── _menu.styl
│ │ ├── _sidebar.styl
│ │ ├── _sub-menu.styl
│ │ └── index.styl
│ ├── _variables/
│ │ ├── Gemini.styl
│ │ ├── Mist.styl
│ │ ├── Muse.styl
│ │ ├── Pisces.styl
│ │ └── base.styl
│ └── main.styl
├── js/
│ ├── algolia-search.js
│ ├── bookmark.js
│ ├── local-search.js
│ ├── motion.js
│ ├── next-boot.js
│ ├── schemes/
│ │ ├── muse.js
│ │ └── pisces.js
│ └── utils.js
└── lib/
└── anime.min.js
SYMBOL INDEX (87 symbols across 20 files)
FILE: scripts/events/lib/config.js
function isObject (line 3) | function isObject(item) {
function merge (line 7) | function merge(target, source) {
FILE: scripts/events/lib/injects.js
class StylusInject (line 9) | class StylusInject {
method constructor (line 10) | constructor(base_dir) {
method push (line 14) | push(file) {
class ViewInject (line 21) | class ViewInject {
method constructor (line 22) | constructor(base_dir) {
method raw (line 26) | raw(name, raw, ...args) {
method file (line 33) | file(name, file, ...args) {
function initInject (line 44) | function initInject(base_dir) {
FILE: scripts/filters/comment/common.js
function capitalize (line 3) | function capitalize(input) {
method iconText (line 8) | iconText(icon, key, defaultValue) {
FILE: scripts/filters/front-matter.js
function showWarnLog (line 17) | function showWarnLog(source, variable) {
function compatibleBeforeAssign (line 22) | function compatibleBeforeAssign(page) {
function compatibleAfterAssign (line 33) | function compatibleAfterAssign(page) {
FILE: scripts/renderer.js
function njkCompile (line 8) | function njkCompile(data) {
function njkRenderer (line 23) | function njkRenderer(data, locals) {
FILE: scripts/tags/button.js
function postButton (line 9) | function postButton(args) {
FILE: scripts/tags/caniuse.js
function caniUse (line 9) | function caniUse(args) {
FILE: scripts/tags/center-quote.js
function centerQuote (line 9) | function centerQuote(args, content) {
FILE: scripts/tags/group-pictures.js
function groupBy (line 74) | function groupBy(group, data) {
function groupPicture (line 128) | function groupPicture(args, content) {
FILE: scripts/tags/label.js
function postLabel (line 9) | function postLabel(args) {
FILE: scripts/tags/mermaid.js
function mermaid (line 9) | function mermaid(args, content) {
FILE: scripts/tags/note.js
function postNote (line 9) | function postNote(args, content) {
FILE: scripts/tags/pdf.js
function pdf (line 9) | function pdf(args) {
FILE: scripts/tags/tabs.js
function postTabs (line 9) | function postTabs(args, content) {
FILE: scripts/tags/video.js
function postVideo (line 9) | function postVideo(args) {
FILE: source/js/motion.js
function getMistLineSettings (line 45) | function getMistLineSettings(element, translateX) {
function pushImageToSequence (line 56) | function pushImageToSequence() {
FILE: source/js/schemes/muse.js
function updateFooterPosition (line 104) | function updateFooterPosition() {
FILE: source/js/schemes/pisces.js
method checkPositionWithEventLoop (line 44) | checkPositionWithEventLoop() {
FILE: source/js/utils.js
function activateNavByIndex (line 254) | function activateNavByIndex(target) {
function findIndex (line 275) | function findIndex(entries) {
function createIntersectionObserver (line 292) | function createIntersectionObserver(marginTop) {
FILE: source/lib/anime.min.js
function a (line 8) | function a(n,e,r){return Math.min(Math.max(n,e),r)}
function o (line 8) | function o(n,e){return n.indexOf(e)>-1}
function u (line 8) | function u(n,e){return n.apply(null,e)}
function c (line 8) | function c(n){var e=/\(([^)]+)\)/.exec(n);return e?e[1].split(",").map(f...
function s (line 8) | function s(n,e){var r=c(n),o=a(i.und(r[0])?1:r[0],.1,100),u=a(i.und(r[1]...
function f (line 8) | function f(n){return void 0===n&&(n=10),function(e){return Math.round(e*...
function r (line 8) | function r(n,e){return 1-3*e+3*n}
function t (line 8) | function t(n,e){return 3*e-6*n}
function a (line 8) | function a(n){return 3*n}
function o (line 8) | function o(n,e,o){return((r(e,o)*n+t(e,o))*n+a(e))*n}
function u (line 8) | function u(n,e,o){return 3*r(e,o)*n*n+2*t(e,o)*n+a(e)}
function f (line 8) | function f(t){for(var i=0,s=1,f=n-1;s!==f&&c[s]<=t;++s)i+=e;var l=i+(t-c...
function v (line 8) | function v(n,e){if(i.fnc(n))return n;var r=n.split("(")[0],t=h[r],a=c(n)...
function g (line 8) | function g(n){try{return document.querySelectorAll(n)}catch(n){return}}
function m (line 8) | function m(n,e){for(var r=n.length,t=arguments.length>=2?arguments[1]:vo...
function y (line 8) | function y(n){return n.reduce(function(n,e){return n.concat(i.arr(e)?y(e...
function b (line 8) | function b(n){return i.arr(n)?n:(i.str(n)&&(n=g(n)||n),n instanceof Node...
function M (line 8) | function M(n,e){return n.some(function(n){return n===e})}
function x (line 8) | function x(n){var e={};for(var r in n)e[r]=n[r];return e}
function w (line 8) | function w(n,e){var r=x(n);for(var t in n)r[t]=e.hasOwnProperty(t)?e[t]:...
function k (line 8) | function k(n,e){var r=x(n);for(var t in e)r[t]=i.und(n[t])?e[t]:n[t];ret...
function O (line 8) | function O(n){return i.rgb(n)?(r=/rgb\((\d+,\s*[\d]+,\s*[\d]+)\)/g.exec(...
function C (line 8) | function C(n){var e=/[+-]?\d*\.?\d+(?:\.\d+)?(?:[eE][+-]?\d+)?(%|px|pt|e...
function B (line 8) | function B(n,e){return i.fnc(n)?n(e.target,e.id,e.total):n}
function P (line 8) | function P(n,e){return n.getAttribute(e)}
function I (line 8) | function I(n,e,r){if(M([r,"deg","rad","turn"],C(e)))return e;var a=t.CSS...
function T (line 8) | function T(n,e,r){if(e in n.style){var t=e.replace(/([a-z])([A-Z])/g,"$1...
function D (line 8) | function D(n,e){return i.dom(n)&&!i.inp(n)&&(P(n,e)||i.svg(n)&&n[e])?"at...
function E (line 8) | function E(n){if(i.dom(n)){for(var e,r=n.style.transform||"",t=/(\w+)\((...
function F (line 8) | function F(n,e,r,t){var a,u=o(e,"scale")?1:0+(o(a=e,"translate")||"persp...
function N (line 8) | function N(n,e,r,t){switch(D(n,e)){case"transform":return F(n,e,t,r);cas...
function A (line 8) | function A(n,e){var r=/^(\*=|\+=|-=)/.exec(n);if(!r)return n;var t=C(n)|...
function L (line 8) | function L(n,e){if(i.col(n))return O(n);if(/\s/g.test(n))return n;var r=...
function j (line 8) | function j(n,e){return Math.sqrt(Math.pow(e.x-n.x,2)+Math.pow(e.y-n.y,2))}
function S (line 8) | function S(n){for(var e,r=n.points,t=0,a=0;a<r.numberOfItems;a++){var o=...
function q (line 8) | function q(n){if(n.getTotalLength)return n.getTotalLength();switch(n.tag...
function $ (line 8) | function $(n,e){var r=e||{},t=r.el||function(n){for(var e=n.parentNode;i...
function X (line 8) | function X(n,e){function r(r){void 0===r&&(r=0);var t=e+r>=1?e+r:0;retur...
function Y (line 8) | function Y(n,e){var r=/[+-]?\d*\.?\d+(?:\.\d+)?(?:[eE][+-]?\d+)?/g,t=L(i...
function Z (line 8) | function Z(n){return m(n?y(i.arr(n)?n.map(b):b(n)):[],function(n,e,r){re...
function Q (line 8) | function Q(n){var e=Z(n);return e.map(function(n,r){return{target:n,id:r...
function V (line 8) | function V(n,e){var r=x(e);if(/^spring/.test(r.easing)&&(r.duration=s(r....
function z (line 8) | function z(n,e){var r=[],t=e.keyframes;for(var a in t&&(e=k(function(n){...
function H (line 8) | function H(n,e){var r;return n.tweens.map(function(t){var a=function(n,e...
function R (line 8) | function R(n,e){Q(n).forEach(function(n){for(var r in e){var t=B(e[r],n)...
function W (line 8) | function W(n,e){return m(y(n.map(function(n){return e.map(function(e){re...
function J (line 8) | function J(n,e){var r=n.length,t=function(n){return n.timelineOffset?n.t...
function n (line 8) | function n(){U=requestAnimationFrame(e)}
function e (line 8) | function e(e){var r=_.length;if(r){for(var t=0;t<r;){var a=_[t];if(a.pau...
function rn (line 8) | function rn(r){void 0===r&&(r={});var t,o=0,u=0,i=0,c=0,s=null;function ...
function tn (line 8) | function tn(n,e){for(var r=e.length;r--;)M(n,e[r].animatable.target)&&e....
function c (line 8) | function c(n){n.passThrough=!0}
Condensed preview — 275 files, each showing path, character count, and a content snippet. Download the .json file or copy for the full structured content (582K chars).
[
{
"path": ".editorconfig",
"chars": 167,
"preview": "# editorconfig.org\n\nroot = true\n\n[*]\ncharset = utf-8\nend_of_line = lf\ninsert_final_newline = true\ntrim_trailing_whitespa"
},
{
"path": ".eslintrc.json",
"chars": 46,
"preview": "{\n \"extends\": \"theme-next\",\n \"root\": true\n}\n"
},
{
"path": ".gitattributes",
"chars": 31,
"preview": "source/lib/* linguist-vendored\n"
},
{
"path": ".github/CODE_OF_CONDUCT.md",
"chars": 6763,
"preview": "<div align=\"right\">\n Language:\n :us:\n <a title=\"Chinese\" href=\"../docs/zh-CN/CODE_OF_CONDUCT.md\">:cn:</a>\n <a title="
},
{
"path": ".github/CONTRIBUTING.md",
"chars": 14164,
"preview": "<div align=\"right\">\n Language:\n :us:\n <a title=\"Chinese\" href=\"../docs/zh-CN/CONTRIBUTING.md\">:cn:</a>\n <a title=\"Ru"
},
{
"path": ".github/ISSUE_TEMPLATE/bug-report.md",
"chars": 1729,
"preview": "---\nname: Bug Report\nabout: Something isn't working as expected\ntitle: ''\nlabels: Bug\nassignees: ''\n\n---\n\nPlease follow "
},
{
"path": ".github/ISSUE_TEMPLATE/feature-request.md",
"chars": 1211,
"preview": "---\nname: Feature Request\nabout: Suggest an idea for this project\ntitle: ''\nlabels: Feature Request\nassignees: ''\n\n---\n\n"
},
{
"path": ".github/ISSUE_TEMPLATE/other.md",
"chars": 878,
"preview": "---\nname: Other\nabout: Not a question, feature request or bug report\ntitle: ''\nlabels: ''\nassignees: ''\n\n---\n\nPlease fol"
},
{
"path": ".github/ISSUE_TEMPLATE/question.md",
"chars": 1736,
"preview": "---\nname: Question\nabout: I have a question for NexT (e.g. Customize)\ntitle: ''\nlabels: Custom\nassignees: ''\n\n---\n\nPleas"
},
{
"path": ".github/PULL_REQUEST_TEMPLATE.md",
"chars": 2087,
"preview": "<!-- ATTENTION!\n1. Please write pull request readme in English, thanks!\n\n2. Always remember that NexT includes 4 schemes"
},
{
"path": ".github/config.yml",
"chars": 1576,
"preview": "# =============================================================================================== #\n# Configuration for "
},
{
"path": ".github/issue-close-app.yml",
"chars": 827,
"preview": "# Comment that will be sent if an issue is judged to be closed.\ncomment: \"This issue has been closed because it does not"
},
{
"path": ".github/issue_label_bot.yaml",
"chars": 86,
"preview": "label-alias:\n bug: 'Bug'\n feature_request: 'Feature Request'\n question: 'Question'\n"
},
{
"path": ".github/lock.yml",
"chars": 1201,
"preview": "# Configuration for Lock Threads - https://github.com/dessant/lock-threads\n\n# Number of days of inactivity before a clos"
},
{
"path": ".github/mergeable.yml",
"chars": 615,
"preview": "# Configuration for Mergeable - https://github.com/jusx/mergeable\n\nversion: 2\nmergeable:\n - when: pull_request.*\n va"
},
{
"path": ".github/release-drafter.yml",
"chars": 931,
"preview": "# Configuration for Release Drafter - https://github.com/toolmantim/release-drafter\n\nname-template: 'v$NEXT_MINOR_VERSIO"
},
{
"path": ".github/stale.yml",
"chars": 1133,
"preview": "# Configuration for probot-stale - https://github.com/probot/stale\n\n# Number of days of inactivity before an Issue or Pu"
},
{
"path": ".github/support.yml",
"chars": 851,
"preview": "# Configuration for Support Requests - https://github.com/dessant/support-requests\n\n# Label used to mark issues as suppo"
},
{
"path": ".gitignore",
"chars": 253,
"preview": ".DS_Store\n.idea/\n*.log\n*.iml\nyarn.lock\npackage-lock.json\nnode_modules/\n\n# Ignore optional external libraries\nsource/lib/"
},
{
"path": ".stylintrc",
"chars": 1090,
"preview": "{\n \"blocks\": false,\n \"brackets\": \"always\",\n \"colons\": \"always\",\n \"colors\": \"always\",\n \"commaSpace\": \"always\",\n \"co"
},
{
"path": ".travis.yml",
"chars": 75,
"preview": "language: node_js\n\nnode_js: node\n\ncache:\n npm: true\n\ninstall: npm install\n"
},
{
"path": "LICENSE.md",
"chars": 3116,
"preview": "# <div align=\"center\">«NexT» – Elegant and powerful theme for Hexo.</div>\n\n<p align=\"center\">Copyright © 2017 «<a href=\""
},
{
"path": "README.md",
"chars": 7434,
"preview": "<div align=\"right\">\n Language:\n 🇺🇸\n <a title=\"Chinese\" href=\"docs/zh-CN/README.md\">🇨🇳</a>\n <a title=\"Russian\" href=\""
},
{
"path": "_config.yml",
"chars": 33184,
"preview": "# ---------------------------------------------------------------\n# Theme Core Configuration Settings\n# See: https://the"
},
{
"path": "crowdin.yml",
"chars": 232,
"preview": "files:\n - source: /languages/en.yml\n translation: /languages/%two_letters_code%.%file_extension%\n languages_mappi"
},
{
"path": "docs/AGPL3.md",
"chars": 34325,
"preview": "# <div align=\"center\">GNU Affero General Public License<div>\n\n<p align=\"center\">Version 3, 19 November 2007 Copyright © "
},
{
"path": "docs/ALGOLIA-SEARCH.md",
"chars": 5277,
"preview": "<h1 align=\"center\">Algolia Search</h1>\n\nNexT provides Algolia search plugin for index your hexo website content. To use "
},
{
"path": "docs/AUTHORS.md",
"chars": 7555,
"preview": "# <div align=\"center\">«NexT» Authors</div>\n\nNexT theme was initially developed by:\n\n- **IIssNaN**: [NexT](https://github"
},
{
"path": "docs/DATA-FILES.md",
"chars": 3595,
"preview": "<h1 align=\"center\">Data Files</h1>\n\nCurrently, it is not smooth to update NexT theme from pulling or downloading new rel"
},
{
"path": "docs/INSTALLATION.md",
"chars": 4641,
"preview": "<h1 align=\"center\">Installation</h1>\n\n<h2 align=\"center\">Step 1 → Go to Hexo dir</h2>\n\nChange dir to **Hexo root** "
},
{
"path": "docs/LEANCLOUD-COUNTER-SECURITY.md",
"chars": 5975,
"preview": "<h1 align=\"center\">Fix LeanCloud Counter Plugin Security Vulnerability</h1>\n\nBefore you make the config, please upgrade "
},
{
"path": "docs/LICENSE.txt",
"chars": 2702,
"preview": " «NexT» – Elegant and powerful theme for Hexo.\n\n Copyright © 2017 «NexT» (github.com/theme-next/hexo-theme-"
},
{
"path": "docs/MATH.md",
"chars": 8865,
"preview": "<h1 align=\"center\">Math Equations</h1>\n\nNexT provides two render engines for displaying Math Equations.\n\nIf you choose t"
},
{
"path": "docs/UPDATE-FROM-5.1.X.md",
"chars": 3023,
"preview": "<h1 align=\"center\">Update from NexT v5.1.x</h1>\n\nNexT version 5 works fine with Hexo 3, but for frequent users, you mayb"
},
{
"path": "docs/ru/DATA-FILES.md",
"chars": 3900,
"preview": "<h1 align=\"center\">Дата Файлы</h1>\n\nОбновление темы NexT через пулы проходит не слишком гладко. Часто происходит конфлик"
},
{
"path": "docs/ru/INSTALLATION.md",
"chars": 4909,
"preview": "<h1 align=\"center\">Установка</h1>\n\n<h2 align=\"center\">Шаг 1 → Идём в директорию Hexo</h2>\n\nМеняем каталог на **корн"
},
{
"path": "docs/ru/README.md",
"chars": 7216,
"preview": "<div align=\"right\">\n Язык:\n <a title=\"Английский\" href=\"../../README.md\">🇺🇸</a>\n <a title=\"Китайский\" href=\"../zh-CN/"
},
{
"path": "docs/ru/UPDATE-FROM-5.1.X.md",
"chars": 2306,
"preview": "<h1 align=\"center\">Обновление из-под NexT v5.1.x</h1>\n\nМежду версией 5.1.x и последней версиями нет жёстких изменений. В"
},
{
"path": "docs/zh-CN/ALGOLIA-SEARCH.md",
"chars": 3433,
"preview": "<h1 align=\"center\">Algolia 搜索</h1>\n\nNexT 内部提供 Algolia 的搜索功能，要使用此功能请确保所使用的 NexT 版本在 `v5.1.0` 之后。需要注意的是，仅仅将 `next/_config."
},
{
"path": "docs/zh-CN/CODE_OF_CONDUCT.md",
"chars": 2803,
"preview": "<div align=\"right\">\n 语言：\n <a title=\"英语\" href=\"../../.github/CODE_OF_CONDUCT.md\">:us:</a>\n :cn:\n <a title=\"俄语\" href=\""
},
{
"path": "docs/zh-CN/CONTRIBUTING.md",
"chars": 6554,
"preview": "<div align=\"right\">\n 语言：\n <a title=\"英语\" href=\"../../.github/CONTRIBUTING.md\">:us:</a>\n :cn:\n <a title=\"俄语\" href=\"../"
},
{
"path": "docs/zh-CN/DATA-FILES.md",
"chars": 2212,
"preview": "<h1 align=\"center\">数据文件</h1>\n\n目前，通过 pull 或下载新的 release 版本来更新 NexT 主题的体验并不平滑。当用户使用 `git pull` 更新 NexT 主题时经常需要解决冲突问题，而在手动下"
},
{
"path": "docs/zh-CN/INSTALLATION.md",
"chars": 3613,
"preview": "<h1 align=\"center\">安装</h1>\n\n<h2 align=\"center\">步骤 1 → 进入 Hexo 目录</h2>\n\n进入 **Hexo 根**目录。这一目录中应当有 `node_modules`、`sou"
},
{
"path": "docs/zh-CN/LEANCLOUD-COUNTER-SECURITY.md",
"chars": 5494,
"preview": "<h1 align=\"center\">修复 LeanCloud 统计插件安全漏洞</h1>\n\n在配置前，请升级 NexT 至 **v6.0.6** 以上。\n\n在配置过程中请注意**博客配置文件**和**主题配置文件**的区别。\n\n---\n\n"
},
{
"path": "docs/zh-CN/MATH.md",
"chars": 6048,
"preview": "<h1 align=\"center\">数学公式</h1>\n\nNexT 内部提供数学公式渲染的引擎，这样你就不需要自己手动在模板中引入 JS 或者 CSS；\n只需要选择对应的渲染引擎，并在 `next/_config.yml` 中将其 `en"
},
{
"path": "docs/zh-CN/README.md",
"chars": 6367,
"preview": "<div align=\"right\">\n 语言:\n <a title=\"英语\" href=\"../../README.md\">🇺🇸</a>\n 🇨🇳\n <a title=\"俄语\" href=\"../ru/README.md\">🇷🇺</"
},
{
"path": "docs/zh-CN/UPDATE-FROM-5.1.X.md",
"chars": 1903,
"preview": "<h1 align=\"center\">从 NexT v5.1.x 更新</h1>\n\n在使用 Hexo 3 时，NexT V5 版本仍然能够正常运行，但是如果你想获得更多的功能和帮助，还是建议您升级到 NexT V7+ 版本，并移步 [The"
},
{
"path": "gulpfile.js",
"chars": 1220,
"preview": "const fs = require('fs');\nconst path = require('path');\nconst gulp = require('gulp');\nconst eslint = require('gulp-eslin"
},
{
"path": "languages/ar.yml",
"chars": 1765,
"preview": "---\nname: عربي\ntitle:\n archive: الأرشيف\n category: تصنيف\n tag: وسم\n schedule: التقويم\nmenu:\n home: Home\n archives:"
},
{
"path": "languages/de.yml",
"chars": 2001,
"preview": "---\nname: Deutsch\ntitle:\n archive: Archiv\n category: Kategorie\n tag: Schlagwort\n schedule: Zeitplan\nmenu:\n home: St"
},
{
"path": "languages/en.yml",
"chars": 1835,
"preview": "name: English\n\ntitle:\n archive: Archive\n category: Category\n tag: Tag\n schedule: Schedule\n\nmenu:\n home: Home\n arch"
},
{
"path": "languages/es.yml",
"chars": 2020,
"preview": "---\nname: Español\ntitle:\n archive: Archivo\n category: Categoría\n tag: Etiqueta\n schedule: Calendario\nmenu:\n home: I"
},
{
"path": "languages/fa.yml",
"chars": 1861,
"preview": "---\nname: فارسی\ntitle:\n archive: بایگانی\n category: دسته بندی\n tag: برچسب\n schedule: زمان بندی\nmenu:\n home: صفحه اص"
},
{
"path": "languages/fr.yml",
"chars": 1942,
"preview": "---\nname: Français\ntitle:\n archive: Archive\n category: Catégorie\n tag: Mots clés\n schedule: Plannifier\nmenu:\n home:"
},
{
"path": "languages/hu.yml",
"chars": 1821,
"preview": "---\nname: magyar\ntitle:\n archive: Archive\n category: Category\n tag: Tag\n schedule: Ütemterv\nmenu:\n home: Home\n arc"
},
{
"path": "languages/id.yml",
"chars": 1862,
"preview": "---\nname: Bahasa Indonesia\ntitle:\n archive: Arsip\n category: Kategori\n tag: Tag\n schedule: Schedule\nmenu:\n home: Be"
},
{
"path": "languages/it.yml",
"chars": 1860,
"preview": "---\nname: Italiano\ntitle:\n archive: Archivio\n category: Categoria\n tag: Tag\n schedule: Programma\nmenu:\n home: Home\n"
},
{
"path": "languages/ja.yml",
"chars": 1461,
"preview": "---\nname: 日本語\ntitle:\n archive: アーカイブ\n category: カテゴリ\n tag: タグ\n schedule: スケジュール\nmenu:\n home: ホーム\n archives: アーカイブ\n"
},
{
"path": "languages/ko.yml",
"chars": 1676,
"preview": "---\nname: 한국어\ntitle:\n archive: 아카이브\n category: 카테고리\n tag: 태그\n schedule: Schedule\nmenu:\n home: 홈\n archives: 아카이브\n "
},
{
"path": "languages/nl.yml",
"chars": 1905,
"preview": "---\nname: Niederländisch\ntitle:\n archive: Archief\n category: Categorie\n tag: Label\n schedule: Rooster\nmenu:\n home: "
},
{
"path": "languages/pt-BR.yml",
"chars": 1873,
"preview": "---\nname: Português\ntitle:\n archive: Arquivo\n category: Categoria\n tag: Tag\n schedule: Schedule\nmenu:\n home: Home\n "
},
{
"path": "languages/pt.yml",
"chars": 1896,
"preview": "---\nname: Português\ntitle:\n archive: Arquivo\n category: Categoria\n tag: Tag\n schedule: Schedule\nmenu:\n home: Home\n "
},
{
"path": "languages/ru.yml",
"chars": 1900,
"preview": "---\nname: Русский\ntitle:\n archive: Архив\n category: Категория\n tag: Тэг\n schedule: Календарь\nmenu:\n home: Главная\n "
},
{
"path": "languages/tr.yml",
"chars": 1944,
"preview": "---\nname: Türk\ntitle:\n archive: Arşiv\n category: Kategori\n tag: Etiket\n schedule: Program\nmenu:\n home: Ana Sayfa\n "
},
{
"path": "languages/uk.yml",
"chars": 1877,
"preview": "---\nname: Український\ntitle:\n archive: Архів\n category: Категорія\n tag: Тег\n schedule: Календар\nmenu:\n home: Головн"
},
{
"path": "languages/vi.yml",
"chars": 1938,
"preview": "---\nname: Tiếng Việt\ntitle:\n archive: Lưu Trữ\n category: Phân Loại\n tag: Thẻ\n schedule: Danh Mục\nmenu:\n home: Trang"
},
{
"path": "languages/zh-CN.yml",
"chars": 1372,
"preview": "---\nname: 简体中文\ntitle:\n archive: 归档\n category: 分类\n tag: 标签\n schedule: 日程表\nmenu:\n home: 首页\n archives: 归档\n categorie"
},
{
"path": "languages/zh-HK.yml",
"chars": 1378,
"preview": "---\nname: 繁體中文（香港）\ntitle:\n archive: 歸檔\n category: 分類\n tag: 標籤\n schedule: 日程表\nmenu:\n home: 首頁\n archives: 歸檔\n categ"
},
{
"path": "languages/zh-TW.yml",
"chars": 1375,
"preview": "---\nname: 繁體中文\ntitle:\n archive: 歸檔\n category: 分類\n tag: 標籤\n schedule: 時間表\nmenu:\n home: 首頁\n archives: 歸檔\n categorie"
},
{
"path": "layout/_layout.swig",
"chars": 2052,
"preview": "<!DOCTYPE html>\n<html lang=\"{{ config.language }}\">\n<head>\n {{ partial('_partials/head/head.swig', {}, {cache: theme.ca"
},
{
"path": "layout/_macro/post-collapse.swig",
"chars": 1324,
"preview": "{% macro render(posts) %}\n{%- set current_year = '1970' %}\n{%- for post in posts.toArray() %}\n\n {%- set year = date(pos"
},
{
"path": "layout/_macro/post.swig",
"chars": 11306,
"preview": " {##################}\n {### POST BLOCK ###}\n {##################}\n <article itemscope itemtype=\"http://schema.org/Ar"
},
{
"path": "layout/_macro/sidebar.swig",
"chars": 1550,
"preview": "{% macro render(display_toc) %}\n <div class=\"toggle sidebar-toggle\">\n <span class=\"toggle-line toggle-line-first\"></"
},
{
"path": "layout/_partials/comments.swig",
"chars": 3433,
"preview": "{%- if page.comments %}\n {%- if theme.injects.comment.length == 1 %}\n {%- set inject_item = theme.injects.comment[0]"
},
{
"path": "layout/_partials/footer.swig",
"chars": 2740,
"preview": "{%- if theme.footer.beian.enable %}\n <div class=\"beian\">\n {{- next_url('https://beian.miit.gov.cn', theme.footer.bei"
},
{
"path": "layout/_partials/head/head-unique.swig",
"chars": 333,
"preview": "{{ open_graph() }}\n\n{{ canonical() }}\n\n{# Exports some front-matter variables to Front-End #}\n<script id=\"page-configura"
},
{
"path": "layout/_partials/head/head.swig",
"chars": 2688,
"preview": "<meta charset=\"UTF-8\">\n<meta name=\"viewport\" content=\"width=device-width, initial-scale=1, maximum-scale=2\">\n<meta name="
},
{
"path": "layout/_partials/header/brand.swig",
"chars": 1456,
"preview": "<div class=\"site-brand-container\">\n <div class=\"site-nav-toggle\">\n <div class=\"toggle\" aria-label=\"{{ __('accessibil"
},
{
"path": "layout/_partials/header/index.swig",
"chars": 265,
"preview": "{{ partial('_partials/header/brand.swig', {}, {cache: theme.cache.enable}) }}\n\n{{ partial('_partials/header/menu.swig', "
},
{
"path": "layout/_partials/header/menu-item.swig",
"chars": 1064,
"preview": "{% macro render(name, itemName, value) %}\n\n {%- set itemURL = value.split('||')[0] | trim %}\n {%- if not itemURL.start"
},
{
"path": "layout/_partials/header/menu.swig",
"chars": 1194,
"preview": "{% import 'menu-item.swig' as menu_item with context %}\n\n<nav class=\"site-nav\">\n{%- if theme.menu %}\n <ul id=\"menu\" cla"
},
{
"path": "layout/_partials/header/sub-menu.swig",
"chars": 3740,
"preview": "{% import '_partials/header/menu-item.swig' as menu_item with context %}\n\n{%- if theme.menu and is_page() %}\n {# Submen"
},
{
"path": "layout/_partials/languages.swig",
"chars": 571,
"preview": "{%- if theme.language_switcher and languages.length > 1 %}\n <div class=\"languages\">\n <label class=\"lang-select-label"
},
{
"path": "layout/_partials/page/breadcrumb.swig",
"chars": 872,
"preview": "{%- set paths = page.path.split('/') %}\n{%- set count = paths.length %}\n{%- if count > 2 %}\n {%- set current = 0 %}\n {"
},
{
"path": "layout/_partials/page/page-header.swig",
"chars": 336,
"preview": "<header class=\"post-header\">\n\n<h1 class=\"post-title\" itemprop=\"name headline\">\n {{- page.title }}\n {{- post_edit(page."
},
{
"path": "layout/_partials/pagination.swig",
"chars": 383,
"preview": "{%- if page.prev or page.next %}\n <nav class=\"pagination\">\n {{\n paginator({\n prev_text: '<i class=\"fa fa"
},
{
"path": "layout/_partials/post/post-copyright.swig",
"chars": 731,
"preview": "{%- set ccIcon = '<i class=\"fab fa-fw fa-creative-commons\"></i>' %}\n{%- set ccText = theme.creative_commons.license | up"
},
{
"path": "layout/_partials/post/post-followme.swig",
"chars": 610,
"preview": "{%- if theme.follow_me %}\n\n <div class=\"followme\">\n <p>{{ __('follow_me.welcome') }}</p>\n\n <div class=\"social-lis"
},
{
"path": "layout/_partials/post/post-footer.swig",
"chars": 155,
"preview": "{%- if theme.rating.enable %}\n <div class=\"post-widgets\">\n <div class=\"wp_rating\">\n <div id=\"wpac-rating\"></div"
},
{
"path": "layout/_partials/post/post-related.swig",
"chars": 1008,
"preview": "{%- set popular_posts = popular_posts_json(theme.related_posts.params, page) %}\n{%- if popular_posts.json and popular_po"
},
{
"path": "layout/_partials/post/post-reward.swig",
"chars": 775,
"preview": "<div class=\"reward-container\">\n <div>{{ page.reward_settings.comment }}</div>\n <button onclick=\"var qr = document.getE"
},
{
"path": "layout/_partials/search/algolia-search.swig",
"chars": 401,
"preview": "<div class=\"search-header\">\n <span class=\"search-icon\">\n <i class=\"fa fa-search\"></i>\n </span>\n <div class=\"search"
},
{
"path": "layout/_partials/search/index.swig",
"chars": 363,
"preview": "{%- if theme.algolia_search.enable or theme.local_search.enable %}\n <div class=\"search-pop-overlay\">\n <div class=\"po"
},
{
"path": "layout/_partials/search/localsearch.swig",
"chars": 529,
"preview": "<div class=\"search-header\">\n <span class=\"search-icon\">\n <i class=\"fa fa-search\"></i>\n </span>\n <div class=\"search"
},
{
"path": "layout/_partials/sidebar/site-overview.swig",
"chars": 4737,
"preview": "<div class=\"site-author motion-element\" itemprop=\"author\" itemscope itemtype=\"http://schema.org/Person\">\n {%- if theme."
},
{
"path": "layout/_partials/widgets.swig",
"chars": 1695,
"preview": "{%- if theme.back2top.enable and not theme.back2top.sidebar %}\n <div class=\"back-to-top\">\n <i class=\"fa fa-arrow-up\""
},
{
"path": "layout/_scripts/index.swig",
"chars": 428,
"preview": "{% include 'vendors.swig' %}\n\n{{- next_js('utils.js') }}\n{%- if theme.motion.enable %}\n {{- next_js('motion.js') }}\n{%-"
},
{
"path": "layout/_scripts/noscript.swig",
"chars": 508,
"preview": "<noscript>\n <style>\n .use-motion .brand,\n .use-motion .menu-item,\n .sidebar-inner,\n .use-motion .post-block,\n .use"
},
{
"path": "layout/_scripts/pages/schedule.swig",
"chars": 4718,
"preview": "<script{{ pjax }}>\n(function() {\n // Initialization\n var calendar = {\n orderBy : 'startTime',\n showLocation:"
},
{
"path": "layout/_scripts/pjax.swig",
"chars": 1535,
"preview": "<script>\nvar pjax = new Pjax({\n selectors: [\n 'head title',\n '#page-configurations',\n '.content-wrap',\n '.p"
},
{
"path": "layout/_scripts/schemes/gemini.swig",
"chars": 36,
"preview": "{{- next_js('schemes/pisces.js') }}\n"
},
{
"path": "layout/_scripts/schemes/mist.swig",
"chars": 34,
"preview": "{{- next_js('schemes/muse.js') }}\n"
},
{
"path": "layout/_scripts/schemes/muse.swig",
"chars": 34,
"preview": "{{- next_js('schemes/muse.js') }}\n"
},
{
"path": "layout/_scripts/schemes/pisces.swig",
"chars": 36,
"preview": "{{- next_js('schemes/pisces.js') }}\n"
},
{
"path": "layout/_scripts/three.swig",
"chars": 778,
"preview": "{%- if theme.three.enable %}\n {%- set three_uri = theme.vendors.three or next_vendors('three/three.min.js') %}\n <scrip"
},
{
"path": "layout/_scripts/vendors.swig",
"chars": 2225,
"preview": "{%- set js_vendors = {} %}\n{%- set js_vendors = js_vendors | attr('anime', 'anime.min.js') %}\n\n{%- if theme.pjax %}\n {%"
},
{
"path": "layout/_third-party/analytics/baidu-analytics.swig",
"chars": 353,
"preview": "{%- if theme.baidu_analytics %}\n <script{{ pjax }}>\n var _hmt = _hmt || [];\n (function() {\n var hm = documen"
},
{
"path": "layout/_third-party/analytics/google-analytics.swig",
"chars": 1235,
"preview": "{%- if theme.google_analytics.tracking_id %}\n {%- if not theme.google_analytics.only_pageview %}\n <script async src="
},
{
"path": "layout/_third-party/analytics/growingio.swig",
"chars": 488,
"preview": "{%- if theme.growingio_analytics %}\n <script{{ pjax }}>\n !function(e,t,n,g,i){e[i]=e[i]||function(){(e[i].q=e[i].q||"
},
{
"path": "layout/_third-party/analytics/index.swig",
"chars": 106,
"preview": "{% include 'google-analytics.swig' %}\n{% include 'baidu-analytics.swig' %}\n{% include 'growingio.swig' %}\n"
},
{
"path": "layout/_third-party/baidu-push.swig",
"chars": 1151,
"preview": "{%- if theme.baidu_push %}\n <script{{ pjax }}>\n (function(){\n var canonicalURL, curProtocol;\n //Get the <l"
},
{
"path": "layout/_third-party/chat/chatra.swig",
"chars": 608,
"preview": "{%- if theme.chatra.enable %}\n {%- if theme.chatra.embed %}\n <script>\n window.ChatraSetup = {\n mode : 'fram"
},
{
"path": "layout/_third-party/chat/tidio.swig",
"chars": 109,
"preview": "{%- if theme.tidio.enable %}\n <script src=\"//code.tidio.co/{{ theme.tidio.key }}.js\"></script>\n{%- endif %}\n"
},
{
"path": "layout/_third-party/comments/changyan.swig",
"chars": 1402,
"preview": "{%- if is_home() %}\n <script id=\"cy_cmt_num\" src=\"https://changyan.sohu.com/upload/plugins/plugins.list.count.js?client"
},
{
"path": "layout/_third-party/comments/disqus.swig",
"chars": 1177,
"preview": "{%- if theme.disqus.count %}\n<script>\n function loadCount() {\n var d = document, s = d.createElement('script');\n "
},
{
"path": "layout/_third-party/comments/disqusjs.swig",
"chars": 842,
"preview": "{%- if page.comments %}\n{%- set disqusjs_css_uri = theme.vendors.disqusjs_css or '//cdn.jsdelivr.net/npm/disqusjs@1/dist"
},
{
"path": "layout/_third-party/comments/gitalk.swig",
"chars": 1148,
"preview": "{%- if page.comments %}\n{%- set gitalk_css_uri = theme.vendors.gitalk_css or '//cdn.jsdelivr.net/npm/gitalk@1/dist/gital"
},
{
"path": "layout/_third-party/comments/livere.swig",
"chars": 536,
"preview": "{%- if page.comments %}\n<script>\nNexT.utils.loadComments(document.querySelector('#lv-container'), () => {\n window.liver"
},
{
"path": "layout/_third-party/comments/valine.swig",
"chars": 1124,
"preview": "{%- set valine_uri = theme.vendors.valine or '//unpkg.com/valine/dist/Valine.min.js' %}\n\n<script>\nNexT.utils.loadComment"
},
{
"path": "layout/_third-party/index.swig",
"chars": 437,
"preview": "{% include 'baidu-push.swig' %}\n\n{% include 'rating.swig' %}\n\n{%- if theme.algolia_search.enable %}\n {% include 'search"
},
{
"path": "layout/_third-party/math/index.swig",
"chars": 703,
"preview": "{%- if theme.math.mathjax.enable or theme.math.katex.enable %}\n {%- set is_index_has_math = false %}\n\n {# At home, che"
},
{
"path": "layout/_third-party/math/katex.swig",
"chars": 545,
"preview": "{%- set katex_uri = theme.vendors.katex or '//cdn.jsdelivr.net/npm/katex@0/dist/katex.min.css' %}\n<link rel=\"stylesheet\""
},
{
"path": "layout/_third-party/math/mathjax.swig",
"chars": 1889,
"preview": "{%- set mathjax_uri = theme.vendors.mathjax or '//cdn.jsdelivr.net/npm/mathjax@3/es5/tex-mml-chtml.js' %}\n\n<script>\n if"
},
{
"path": "layout/_third-party/quicklink.swig",
"chars": 657,
"preview": "{%- if page.quicklink.enable %}\n {%- set quicklink_uri = theme.vendors.quicklink or next_vendors('//cdn.jsdelivr.net/np"
},
{
"path": "layout/_third-party/rating.swig",
"chars": 679,
"preview": "{%- if theme.rating.enable %}\n <script{{ pjax }}>\n if (CONFIG.page.isPost) {\n wpac_init = window.wpac_init || [];\n "
},
{
"path": "layout/_third-party/search/algolia-search.swig",
"chars": 444,
"preview": "{%- set algolia_search_uri = theme.vendors.algolia_search or next_vendors('//cdn.jsdelivr.net/npm/algoliasearch@4/dist/a"
},
{
"path": "layout/_third-party/search/localsearch.swig",
"chars": 34,
"preview": "{{- next_js('local-search.js') }}\n"
},
{
"path": "layout/_third-party/search/swiftype.swig",
"chars": 371,
"preview": "<script>\n (function(w,d,t,u,n,s,e){w['SwiftypeObject']=n;w[n]=w[n]||function(){\n (w[n].q=w[n].q||[]).push(arguments)"
},
{
"path": "layout/_third-party/statistics/busuanzi-counter.swig",
"chars": 1182,
"preview": "{%- if theme.busuanzi_count.enable %}\n<div class=\"busuanzi-count\">\n <script{{ pjax }} async src=\"https://busuanzi.ibruc"
},
{
"path": "layout/_third-party/statistics/cnzz-analytics.swig",
"chars": 203,
"preview": "{%- if theme.cnzz_siteid %}\n <div style=\"display: none;\">\n <script{{ pjax }} src=\"//s95.cnzz.com/z_stat.php?id={{ th"
},
{
"path": "layout/_third-party/statistics/firestore.swig",
"chars": 2346,
"preview": "{%- if theme.firestore.enable %}\n <script src=\"https://www.gstatic.com/firebasejs/6.3.3/firebase-app.js\"></script>\n <s"
},
{
"path": "layout/_third-party/statistics/index.swig",
"chars": 141,
"preview": "{% include 'busuanzi-counter.swig' %}\n{% include 'cnzz-analytics.swig' %}\n{% include 'firestore.swig' %}\n{% include 'lea"
},
{
"path": "layout/_third-party/statistics/lean-analytics.swig",
"chars": 3791,
"preview": "{%- if theme.leancloud_visitors.enable and not theme.valine.visitor %}\n<script{{ pjax }}>\n (function() {\n function l"
},
{
"path": "layout/_third-party/tags/mermaid.swig",
"chars": 533,
"preview": "{%- if theme.mermaid.enable %}\n{%- set mermaid_uri = theme.vendors.mermaid or '//cdn.jsdelivr.net/npm/mermaid@8/dist/mer"
},
{
"path": "layout/_third-party/tags/pdf.swig",
"chars": 904,
"preview": "{%- if theme.pdf.enable %}\n{%- set pdf_uri = next_vendors('pdf/web/viewer.html') %}\n<script{{ pjax }}>\ndocument.querySel"
},
{
"path": "layout/archive.swig",
"chars": 1435,
"preview": "{% extends '_layout.swig' %}\n{% import '_macro/post-collapse.swig' as post_template with context %}\n{% import '_macro/si"
},
{
"path": "layout/category.swig",
"chars": 947,
"preview": "{% extends '_layout.swig' %}\n{% import '_macro/post-collapse.swig' as post_template with context %}\n{% import '_macro/si"
},
{
"path": "layout/index.swig",
"chars": 553,
"preview": "{% extends '_layout.swig' %}\n{% import '_macro/sidebar.swig' as sidebar_template with context %}\n\n{% block title %}{{ ti"
},
{
"path": "layout/page.swig",
"chars": 2534,
"preview": "{% extends '_layout.swig' %}\n{% import '_macro/sidebar.swig' as sidebar_template with context %}\n\n{% block title %}\n {%"
},
{
"path": "layout/post.swig",
"chars": 372,
"preview": "{% extends '_layout.swig' %}\n{% import '_macro/sidebar.swig' as sidebar_template with context %}\n\n{% block title %}{{ pa"
},
{
"path": "layout/tag.swig",
"chars": 892,
"preview": "{% extends '_layout.swig' %}\n{% import '_macro/post-collapse.swig' as post_template with context %}\n{% import '_macro/si"
},
{
"path": "package.json",
"chars": 834,
"preview": "{\n \"name\": \"hexo-theme-next\",\n \"version\": \"7.8.0\",\n \"description\": \"Elegant and powerful theme for Hexo.\",\n \"main\": "
},
{
"path": "scripts/events/index.js",
"chars": 1776,
"preview": "/* global hexo */\n\n'use strict';\n\nhexo.on('generateBefore', () => {\n // Merge config.\n require('./lib/config')(hexo);\n"
},
{
"path": "scripts/events/lib/config.js",
"chars": 1646,
"preview": "'use strict';\n\nfunction isObject(item) {\n return item && typeof item === 'object' && !Array.isArray(item);\n}\n\nfunction "
},
{
"path": "scripts/events/lib/injects-point.js",
"chars": 229,
"preview": "'use strict';\n\nmodule.exports = {\n views: [\n 'head',\n 'header',\n 'sidebar',\n 'postMeta',\n 'postBodyEnd',"
},
{
"path": "scripts/events/lib/injects.js",
"chars": 2170,
"preview": "'use strict';\n\nconst fs = require('fs');\nconst path = require('path');\nconst points = require('./injects-point');\nconst "
},
{
"path": "scripts/filters/comment/changyan.js",
"chars": 1479,
"preview": "/* global hexo */\n\n'use strict';\n\nconst path = require('path');\nconst { iconText } = require('./common');\n\n// Add commen"
},
{
"path": "scripts/filters/comment/common.js",
"chars": 659,
"preview": "'use strict';\n\nfunction capitalize(input) {\n return input.toString().charAt(0).toUpperCase() + input.toString().substr("
},
{
"path": "scripts/filters/comment/default-config.js",
"chars": 913,
"preview": "/* global hexo */\n\n'use strict';\n\nconst path = require('path');\n\nhexo.extend.filter.register('theme_inject', injects => "
},
{
"path": "scripts/filters/comment/disqus.js",
"chars": 1253,
"preview": "/* global hexo */\n\n'use strict';\n\nconst path = require('path');\nconst { iconText } = require('./common');\n\n// Add commen"
},
{
"path": "scripts/filters/comment/disqusjs.js",
"chars": 606,
"preview": "/* global hexo */\n\n'use strict';\n\nconst path = require('path');\n\n// Add comment\nhexo.extend.filter.register('theme_injec"
},
{
"path": "scripts/filters/comment/gitalk.js",
"chars": 424,
"preview": "/* global hexo */\n\n'use strict';\n\nconst path = require('path');\n\n// Add comment\nhexo.extend.filter.register('theme_injec"
},
{
"path": "scripts/filters/comment/livere.js",
"chars": 491,
"preview": "/* global hexo */\n\n'use strict';\n\nconst path = require('path');\n\n// Add comment\nhexo.extend.filter.register('theme_injec"
},
{
"path": "scripts/filters/comment/valine.js",
"chars": 1193,
"preview": "/* global hexo */\n\n'use strict';\n\nconst path = require('path');\nconst { iconText } = require('./common');\n\n// Add commen"
},
{
"path": "scripts/filters/default-injects.js",
"chars": 466,
"preview": "/* global hexo */\n\n'use strict';\n\nconst points = require('../events/lib/injects-point');\n\nhexo.extend.filter.register('t"
},
{
"path": "scripts/filters/front-matter.js",
"chars": 1885,
"preview": "/**\n * Modify front-matter.\n *\n * Some keys are included by Hexo, please don't use them.\n * e.g. layout title date updat"
},
{
"path": "scripts/filters/locals.js",
"chars": 1194,
"preview": "/* global hexo */\n\n'use strict';\n\nconst path = require('path');\n\nhexo.extend.filter.register('template_locals', locals ="
},
{
"path": "scripts/filters/minify.js",
"chars": 1318,
"preview": "/* global hexo */\n\n'use strict';\n\nhexo.extend.filter.register('after_generate', () => {\n const theme = hexo.theme.confi"
},
{
"path": "scripts/filters/post.js",
"chars": 988,
"preview": "/* global hexo */\n\n'use strict';\n\nhexo.extend.filter.register('after_post_render', data => {\n const { config } = hexo;\n"
},
{
"path": "scripts/helpers/engine.js",
"chars": 2788,
"preview": "/* global hexo */\n\n'use strict';\n\nconst crypto = require('crypto');\n\nhexo.extend.helper.register('next_inject', function"
},
{
"path": "scripts/helpers/font.js",
"chars": 996,
"preview": "/* global hexo */\n\n'use strict';\n\nhexo.extend.helper.register('next_font', () => {\n const config = hexo.theme.config.fo"
},
{
"path": "scripts/helpers/next-config.js",
"chars": 1279,
"preview": "/* global hexo */\n\n'use strict';\n\nconst url = require('url');\n\n/**\n * Export theme config to js\n */\nhexo.extend.helper.r"
},
{
"path": "scripts/helpers/next-url.js",
"chars": 1563,
"preview": "/* global hexo */\n\n'use strict';\n\nconst { htmlTag } = require('hexo-util');\nconst url = require('url');\n\nhexo.extend.hel"
},
{
"path": "scripts/renderer.js",
"chars": 962,
"preview": "/* global hexo */\n\n'use strict';\n\nconst nunjucks = require('nunjucks');\nconst path = require('path');\n\nfunction njkCompi"
},
{
"path": "scripts/tags/button.js",
"chars": 769,
"preview": "/**\n * button.js | https://theme-next.org/docs/tag-plugins/button\n */\n\n/* global hexo */\n\n'use strict';\n\nfunction postBu"
},
{
"path": "scripts/tags/caniuse.js",
"chars": 627,
"preview": "/**\n * caniuse.js | https://theme-next.org/docs/tag-plugins/caniuse\n */\n\n/* global hexo */\n\n'use strict';\n\nfunction cani"
},
{
"path": "scripts/tags/center-quote.js",
"chars": 516,
"preview": "/**\n * center-quote.js | https://theme-next.org/docs/tag-plugins/\n */\n\n/* global hexo */\n\n'use strict';\n\nfunction center"
},
{
"path": "scripts/tags/group-pictures.js",
"chars": 2822,
"preview": "/**\n * group-pictures.js | https://theme-next.org/docs/tag-plugins/group-pictures\n */\n\n/* global hexo */\n\n'use strict';\n"
},
{
"path": "scripts/tags/label.js",
"chars": 423,
"preview": "/**\n * label.js | https://theme-next.org/docs/tag-plugins/label\n */\n\n/* global hexo */\n\n'use strict';\n\nfunction postLabe"
},
{
"path": "scripts/tags/mermaid.js",
"chars": 336,
"preview": "/**\n * mermaid.js | https://theme-next.org/docs/tag-plugins/mermaid\n */\n\n/* global hexo */\n\n'use strict';\n\nfunction merm"
},
{
"path": "scripts/tags/note.js",
"chars": 420,
"preview": "/**\n * note.js | https://theme-next.org/docs/tag-plugins/note\n */\n\n/* global hexo */\n\n'use strict';\n\nfunction postNote(a"
},
{
"path": "scripts/tags/pdf.js",
"chars": 331,
"preview": "/**\n * pdf.js | https://theme-next.org/docs/tag-plugins/pdf\n */\n\n/* global hexo */\n\n'use strict';\n\nfunction pdf(args) {\n"
},
{
"path": "scripts/tags/tabs.js",
"chars": 2134,
"preview": "/**\n * tabs.js | https://theme-next.org/docs/tag-plugins/tabs\n */\n\n/* global hexo */\n\n'use strict';\n\nfunction postTabs(a"
},
{
"path": "scripts/tags/video.js",
"chars": 337,
"preview": "/**\n * video.js | https://theme-next.org/docs/tag-plugins/video\n */\n\n/* global hexo */\n\n'use strict';\n\nfunction postVide"
},
{
"path": "source/css/_colors.styl",
"chars": 1931,
"preview": ":root {\n --body-bg-color: $body-bg-color;\n --content-bg-color: $content-bg-color;\n --card-bg-color: $card-bg-color;\n "
},
{
"path": "source/css/_common/components/back-to-top-sidebar.styl",
"chars": 325,
"preview": ".back-to-top {\n background: transparent;\n margin: 20px - $sidebar-offset -10px -20px;\n opacity: 0;\n\n if (!hexo-confi"
},
{
"path": "source/css/_common/components/back-to-top.styl",
"chars": 635,
"preview": ".back-to-top {\n background: $b2t-bg-color;\n bottom: $b2t-position-bottom;\n box-sizing: border-box;\n color: $b2t-colo"
},
{
"path": "source/css/_common/components/components.styl",
"chars": 354,
"preview": "if (hexo-config('back2top.enable')) {\n .back-to-top {\n font-size: $b2t-font-size;\n text-align: center;\n the-tr"
},
{
"path": "source/css/_common/components/pages/breadcrumb.styl",
"chars": 305,
"preview": "ul.breadcrumb {\n font-size: $font-size-smallest;\n list-style: none;\n margin: 1em 0;\n padding: 0 2em;\n text-align: c"
},
{
"path": "source/css/_common/components/pages/categories.styl",
"chars": 483,
"preview": ".category-all-page {\n .category-all-title {\n text-align: center;\n }\n\n .category-all {\n margin-top: 20px;\n }\n\n "
},
{
"path": "source/css/_common/components/pages/pages.styl",
"chars": 109,
"preview": "// Page specific styles\n@import 'categories';\n@import 'schedule';\n@import 'breadcrumb';\n@import 'tag-cloud';\n"
},
{
"path": "source/css/_common/components/pages/schedule.styl",
"chars": 1830,
"preview": "@keyframes dot-flash {\n from {\n opacity: 1;\n transform: scale(1);\n }\n\n to {\n opacity: 0;\n transform: scal"
},
{
"path": "source/css/_common/components/pages/tag-cloud.styl",
"chars": 163,
"preview": ".tag-cloud {\n text-align: center;\n\n a {\n display: inline-block;\n margin: 10px;\n\n &:hover {\n color: var(-"
},
{
"path": "source/css/_common/components/post/post-collapse.styl",
"chars": 2187,
"preview": ".posts-collapse {\n margin-left: $posts-collapse-margin;\n position: relative;\n\n +mobile() {\n margin-left: $posts-co"
},
{
"path": "source/css/_common/components/post/post-copyright.styl",
"chars": 147,
"preview": ".post-copyright {\n background: var(--card-bg-color);\n border-left: 3px solid $red;\n list-style: none;\n margin: 2em 0"
},
{
"path": "source/css/_common/components/post/post-eof.styl",
"chars": 207,
"preview": ".post-eof {\n background: $grey-light;\n height: 1px;\n margin: $post-eof-margin-top auto $post-eof-margin-bottom;\n tex"
},
{
"path": "source/css/_common/components/post/post-expand.styl",
"chars": 889,
"preview": ".content {\n padding-top: 40px;\n}\n\n.post-body {\n +desktop() {\n text-align: unquote(hexo-config('text_align.desktop')"
},
{
"path": "source/css/_common/components/post/post-followme.styl",
"chars": 672,
"preview": ".followme {\n align-items: center;\n background: var(--card-bg-color);\n border-left: 3px solid $red;\n color: $grey;\n "
},
{
"path": "source/css/_common/components/post/post-gallery.styl",
"chars": 266,
"preview": ".post-gallery {\n align-items: center;\n display: grid;\n grid-gap: 10px;\n grid-template-columns: 1fr 1fr 1fr;\n margin"
},
{
"path": "source/css/_common/components/post/post-header.styl",
"chars": 1838,
"preview": ".posts-expand .post-header {\n font-size: $font-size-large;\n}\n\n.posts-expand .post-title {\n font-size: $font-size-large"
},
{
"path": "source/css/_common/components/post/post-nav.styl",
"chars": 595,
"preview": ".post-nav {\n border-top: 1px solid $gainsboro;\n display: flex;\n justify-content: space-between;\n margin-top: 15px;\n "
},
{
"path": "source/css/_common/components/post/post-reward.styl",
"chars": 893,
"preview": ".reward-container {\n margin: 20px auto;\n padding: 10px 0;\n text-align: center;\n width: 90%;\n\n button {\n backgrou"
},
{
"path": "source/css/_common/components/post/post-rtl.styl",
"chars": 186,
"preview": ".rtl {\n &.post-body {\n p, a, h1, h2, h3, h4, h5, h6, li, ul, ol {\n direction: rtl;\n font-family: UKIJ Ekra"
},
{
"path": "source/css/_common/components/post/post-tags.styl",
"chars": 188,
"preview": ".post-tags {\n margin-top: 40px;\n text-align: center;\n\n a {\n display: inline-block;\n font-size: $font-size-small"
},
{
"path": "source/css/_common/components/post/post-widgets.styl",
"chars": 326,
"preview": ".post-widgets {\n border-top: 1px solid $gainsboro;\n margin-top: 15px;\n text-align: center;\n}\n\n.wp_rating {\n height: "
},
{
"path": "source/css/_common/components/post/post.styl",
"chars": 1327,
"preview": ".post-body {\n font-family: $font-family-posts;\n word-wrap();\n\n +desktop-large() {\n font-size: $font-size-large;\n "
},
{
"path": "source/css/_common/components/reading-progress.styl",
"chars": 334,
"preview": ".reading-progress-bar {\n background: unquote(hexo-config('reading_progress.color'));\n display: block;\n height: unquot"
},
{
"path": "source/css/_common/components/third-party/gitalk.styl",
"chars": 141,
"preview": ".gt-header a, .gt-comments a, .gt-popup a {\n border-bottom: none;\n}\n\n.gt-container .gt-popup .gt-action.is--active::bef"
},
{
"path": "source/css/_common/components/third-party/math.styl",
"chars": 122,
"preview": "mjx-container[jax=\"CHTML\"][display=\"true\"], .has-jax {\n overflow: auto hidden;\n}\nmjx-container + br {\n display: none;\n"
},
{
"path": "source/css/_common/components/third-party/related-posts.styl",
"chars": 443,
"preview": ".popular-posts-header {\n border-bottom: 1px solid $gainsboro;\n display: block;\n font-size: $font-size-large;\n margin"
}
]
// ... and 75 more files (download for full content)
About this extraction
This page contains the full source code of the theme-next/hexo-theme-next GitHub repository, extracted and formatted as plain text for AI agents and large language models (LLMs). The extraction includes 275 files (532.3 KB), approximately 160.5k tokens, and a symbol index with 87 extracted functions, classes, methods, constants, and types. Use this with OpenClaw, Claude, ChatGPT, Cursor, Windsurf, or any other AI tool that accepts text input. You can copy the full output to your clipboard or download it as a .txt file.
Extracted by GitExtract — free GitHub repo to text converter for AI. Built by Nikandr Surkov.