add doc

2019-04-10 22:28:09 +08:00
1 parent 16ef430a39
commit 792897291b
@@ -0,0 +1,94 @@
+<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).
@@ -0,0 +1,230 @@
+<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)
+  * [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)
+
+<a name="how-can-i-contribute"></a>
+
+## How Can I Contribute?
+
+Main Theme-Next repository was rebased from [iissnan's](https://github.com/iissnan/hexo-theme-next) profile to [Theme-Next](https://github.com/theme-next) organization on GitHub. Most libraries under the `next/source/lib` directory was moved out to [external repos](https://github.com/theme-next) under NexT organization. Version 5 works fine at most cases, but for frequent users, you maybe need to [upgrade version 5 to 6](https://github.com/theme-next/hexo-theme-next/blob/master/docs/UPDATE-FROM-5.1.X.md) to get features and supports in new [Theme-Next](https://github.com/theme-next/hexo-theme-next) repository.
+
+<a name="before-submitting-an-issue"></a>
+
+### Before Submitting An Issue
+
+If you just have a question, you'll get faster results by checking the FAQs for a list of common questions and problems (Work in progress) or the [«NexT» Documentation Site](https://theme-next.org/docs/) (Work in progress).
+
+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.
+
+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.
+
+<a name="reporting-bugs"></a>
+
+### 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.
+
+<a name="reporting-security-bugs"></a>
+
+#### 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.
+
+<a name="suggesting-enhancements"></a>
+
+### 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.
+
+<a name="submitting-a-pull-request"></a>
+
+### 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/).
+
+1. On GitHub, navigate to the original page of the [hexo-theme-next](https://github.com/theme-next/hexo-theme-next). In the top-right corner of the page, click **Fork**.
+2. Under the repository name in your forked repository, click **Clone or download**. In the `Clone with SSH` section, copy the clone URL for the repository. Open Git Bash, and change the current working directory to the location where you want the cloned directory to be made. Type `git clone`, and then paste the URL you copied. Press **Enter**. Your local clone will be created.
+    ```bash
+    $ git clone git@github.com:username/hexo-theme-next.git
+    ```
+3. Navigate into your new cloned repository. Switch branches to the compare branch of the pull request where the original changes were made.
+    ```bash
+    $ cd hexo-theme-next
+    $ git checkout -b patchname
+    ```
+4. After you commit your changes to the head branch of the pull request you can push your changes up to the original pull request directly.
+    ```bash
+    $ git add .
+    $ git commit -m "add commit messamge"
+    $ git push origin patchname
+    ```
+5. Navigate to the original repository you created your fork from. To the right of the Branch menu, click **New pull request**. On the Compare page, confirm that the base fork is the repository you'd like to merge changes into. Use the base branch drop-down menu to select the branch of the upstream repository you'd like to merge changes into. Use the head fork drop-down menu to select your fork, then use the compare branch drop-down menu to select the branch you made your changes in. Click **Create pull request** and type a title and description for your 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.
+
+<a name="creating-releases"></a>
+
+### 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.
+
+<a name="guides"></a>
+
+## Guides
+
+<a name="coding-rules"></a>
+
+### 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.
+
+<a name="coding-standards"></a>
+
+### Coding Standards
+
+To be continued.
+
+<a name="labels-rules"></a>
+
+### 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: `types`+`contents`+`results`
+
+- By types
+    - `Irrelevant`: An irrelevant issue for Next
+    - `Duplicate`: An issue which had been mentioned
+    - `Bug`: A detected bug that needs to be confirmed
+    - `Improvement Need`: An issue that needs to be improvement
+    - `Feature Request`: An issue that wants a new feature
+    - `High Priority`: A detected bugs or misprints with high priority
+    - `Low Priority`: A detected bugs or misprints with low priority
+    - `Non English`: Requires the attention of a multi-lingual maintainer
+    - `Discussion`: An issue that needs to be discussed
+    - `Question`: An issue about questions
+    - `Backlog`: An issue that is to be completed and later compensated
+    - `Meta`: Denoting a change of usage conditions
+- By contents
+    - `Roadmap`: An issue about future development
+    - `Hexo`: An issue related to Hexo
+    - `Scheme [1] - Mist`: An issue related to Scheme Mist
+    - `Scheme [2] - Muse`: An issue related to Scheme Muse
+    - `Scheme [3] - Pisces`: An issue related to Scheme Pisces
+    - `Scheme [4] - Gemini`: An issue related to Scheme Gemini
+    - `3rd Party Service`: An issue related to 3rd party service
+    - `Docs`: Need to add instruction document
+    - `Configurations`: An issue related to configurations
+    - `CSS`: An issue related to CSS
+    - `Custom`: An issue related to custom things
+- By results
+    - `Wontfix`: An issue that will not to be fixed
+    - `Need More Info`: Need more information for solving the issue
+    - `Need Verify`: Need confirmation from the developers or user about the bug or solution
+    - `Can't Reproduce`: An issue that can’t be reproduced
+    - `Verified`: An issue that has been verified
+    - `Help Wanted`: An issue that needs help
+    - `Wait for Answer`: An issue that needs to be answered by the developers or user
+    - `Resolved Maybe`: An issue that has been resolved maybe
+    - `Solved`: An issue that has been solved
+    - `Stale`: This issue has been automatically marked as stale because lack of recent activity
+
+Pull requests related:
+
+- `Breaking Change`: A Pull requests that makes breaking change
+- `Bug Fix`: A Pull requests that fixes the related bug
+- `Docs`: A Pull requests that Instruction document has been added
+- `New Feature`: A Pull requests that provides a new feature
+- `Feature`: A Pull requests that provides an option or addition to existing feature
+- `Improvement`: A Pull requests that improves NexT
+- `i18n`: A Pull requests that makes new languages translation
+- `Performance`: A Pull requests that improves the performance
+- `Discussion`: A Pull requests that needs to be discussed
+- `v6.x`: A Pull requests that bug fixes and some improvements, related to old NexT version 6
+- `v7.x`: A Pull requests that bug fixes and some improvements, related to old NexT version 7
+
+<a name="commit-messages-rules"></a>
+
+### 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".
@@ -0,0 +1,84 @@
+<!-- ATTENTION!
+IF YOU DON'T FILL OUT THE FOLLOWING INFORMATION WE MIGHT CLOSE YOUR ISSUE WITHOUT INVESTIGATING.
+如果你不填充下面的内容，我们可能会直接关闭你的 issue。
+
+If you want to fast resolve your issue, WRITE IT IN ENGLISH, please. Not all contributors/collaborators know Chinese language and Google translate can't always give true translates on issues. Thanks!
+You may delete this recomendations and use template which is placed below.
+-->
+
+### I agree and want to create new issue <!-- (我确认我已经查看了) -->
+
+<!-- Check all with [x] (把 [ ] 换成 [X] 来选择) -->
+- [ ] Yes, I was on [Hexo Docs page](https://hexo.io/docs/), especially on [Templates](https://hexo.io/docs/templates.html), [Variables](https://hexo.io/docs/variables.html), [Helpers](https://hexo.io/docs/helpers.html) and [Troubleshooting](https://hexo.io/docs/troubleshooting.html).
+- [ ] Yes, I was on [NexT Documentation Site](http://theme-next.org/docs/).
+- [ ] And yes, I already searched for current [issues](https://github.com/theme-next/hexo-theme-next/issues?utf8=%E2%9C%93&q=is%3Aissue) and this is not help to me.
+
+***
+
+### Expected behavior <!-- (预期行为) -->
+
+
+### Actual behavior <!-- (实际行为) -->
+
+
+### Steps to reproduce the behavior <!-- (重现步骤) -->
+1. N/A
+2. N/A
+3. N/A
+
+* Link to demo site with this issue: N/A
+* Link(s) to source code or any usefull link(s): N/A
+
+### Node.js and NPM Information
+<!-- Paste output from `node -v && npm -v`  (粘贴 `node -v && npm -v` 输出的信息) -->
+```
+
+```
+
+### Package dependencies Information
+<!-- Paste output from `cat package.json`  (粘贴 `cat package.json` 输出的信息) -->
+```
+
+```
+
+### Hexo Information
+
+#### Hexo version
+<!-- Paste output from `hexo -v`  (粘贴 `hexo -v` 输出的信息) -->
+```
+
+```
+
+#### Hexo Configuration
+<!-- Paste configuration from Hexo `_config.yml`  (从 Hexo `_config.yml` 中粘贴信息) -->
+```yml
+
+```
+
+### NexT Information
+
+**NexT Version:**
+<!-- Check needed with [x] (把 [ ] 换成 [X] 来选择) -->
+
+- [ ] Latest Master branch
+- [ ] Latest Release version
+- [ ] Old version
+
+
+**NexT Scheme:**
+<!-- Check needed with [x] (把 [ ] 换成 [X] 来选择) -->
+
+- [ ] All schemes
+- [ ] Muse
+- [ ] Mist
+- [ ] Pisces
+- [ ] Gemini
+
+
+#### NexT Configuration:
+<!-- Paste ONLY CHANGED CONFIGURATION from NexT `_config.yml` (只粘贴NexT主题配置文件 `_config.yml` 中修改过的部分) -->
+```yml
+
+```
+
+### Other Information <!-- (Like Browser, System, Screenshots) -->
@@ -0,0 +1,92 @@
+---
+name: Bug Report
+about: Create a report to help us improve.
+title: ''
+labels: Bug
+assignees: ''
+
+---
+
+<!-- ATTENTION!
+IF YOU DON'T FILL OUT THE FOLLOWING INFORMATION WE MIGHT CLOSE YOUR ISSUE WITHOUT INVESTIGATING.
+如果你不填充下面的内容，我们可能会直接关闭你的 issue。
+
+If you want to fast resolve your issue, WRITE IT IN ENGLISH, please. Not all contributors / collaborators know Chinese and Google translate can't always translate issues accurately. Thanks!
+-->
+
+### I agree and want to create new issue <!-- 我确认我已经查看了 -->
+
+<!-- Check all with [x] (把 [ ] 换成 [X] 来选择) -->
+- [ ] Yes, I was on [Hexo Docs page](https://hexo.io/docs/), especially on [Templates](https://hexo.io/docs/templates.html), [Variables](https://hexo.io/docs/variables.html), [Helpers](https://hexo.io/docs/helpers.html) and [Troubleshooting](https://hexo.io/docs/troubleshooting.html).
+- [ ] Yes, I was on [NexT Documentation Site](http://theme-next.org/docs/).
+- [ ] And yes, I already searched for current [issues](https://github.com/theme-next/hexo-theme-next/issues?utf8=%E2%9C%93&q=is%3Aissue) and this is not help to me.
+
+***
+
+### Expected behavior <!-- 预期行为 -->
+
+
+### Actual behavior <!-- 实际行为 -->
+
+
+### Steps to reproduce the behavior <!-- 重现步骤 -->
+1. N/A
+2. N/A
+3. N/A
+
+* Link to demo site with this bug: N/A
+* Link(s) to source code or any usefull link(s): N/A
+
+### Node.js and NPM Information
+<!-- Paste output from `node -v && npm -v` (粘贴 `node -v && npm -v` 输出的信息) -->
+```
+
+```
+
+### Package dependencies Information
+<!-- Paste output from `cat package.json` (粘贴 `cat package.json` 输出的信息) -->
+```
+
+```
+
+### Hexo Information
+
+#### Hexo version
+<!-- Paste output from `hexo -v` (粘贴 `hexo -v` 输出的信息) -->
+```
+
+```
+
+#### Hexo Configuration
+<!-- Paste configuration from Hexo `_config.yml` (从 Hexo `_config.yml` 中粘贴信息) -->
+```yml
+
+```
+
+### NexT Information
+
+**NexT Version:**
+<!-- Check needed with [x] (把 [ ] 换成 [X] 来选择) -->
+
+- [ ] Latest Master branch
+- [ ] Latest Release version
+- [ ] Old version
+
+
+**NexT Scheme:**
+<!-- Check needed with [x] (把 [ ] 换成 [X] 来选择) -->
+
+- [ ] All schemes
+- [ ] Muse
+- [ ] Mist
+- [ ] Pisces
+- [ ] Gemini
+
+
+#### NexT Configuration:
+<!-- Paste ONLY CHANGED CONFIGURATION from NexT `_config.yml` (只粘贴NexT主题配置文件 `_config.yml` 中修改过的部分) -->
+```yml
+
+```
+
+### Other Information <!-- (Like Browser, System, Screenshots) -->
@@ -0,0 +1,92 @@
+---
+name: Custom Issue Template
+about: Describe this issue template's purpose here.
+title: ''
+labels: Custom
+assignees: ''
+
+---
+
+<!-- ATTENTION!
+IF YOU DON'T FILL OUT THE FOLLOWING INFORMATION WE MIGHT CLOSE YOUR ISSUE WITHOUT INVESTIGATING.
+如果你不填充下面的内容，我们可能会直接关闭你的 issue。
+
+If you want to fast resolve your issue, WRITE IT IN ENGLISH, please. Not all contributors / collaborators know Chinese and Google translate can't always translate issues accurately. Thanks!
+-->
+
+### I agree and want to create new issue <!-- 我确认我已经查看了 -->
+
+<!-- Check all with [x] (把 [ ] 换成 [X] 来选择) -->
+- [ ] Yes, I was on [Hexo Docs page](https://hexo.io/docs/), especially on [Templates](https://hexo.io/docs/templates.html), [Variables](https://hexo.io/docs/variables.html), [Helpers](https://hexo.io/docs/helpers.html) and [Troubleshooting](https://hexo.io/docs/troubleshooting.html).
+- [ ] Yes, I was on [NexT Documentation Site](http://theme-next.org/docs/).
+- [ ] And yes, I already searched for current [issues](https://github.com/theme-next/hexo-theme-next/issues?utf8=%E2%9C%93&q=is%3Aissue) and this is not help to me.
+
+***
+
+### Expected behavior <!-- 预期行为 -->
+
+
+### Actual behavior <!-- 实际行为 -->
+
+
+### Steps to reproduce the behavior <!-- 重现步骤 -->
+1. N/A
+2. N/A
+3. N/A
+
+* Link to demo site with this issue: N/A
+* Link(s) to source code or any usefull link(s): N/A
+
+### Node.js and NPM Information
+<!-- Paste output from `node -v && npm -v` (粘贴 `node -v && npm -v` 输出的信息) -->
+```
+
+```
+
+### Package dependencies Information
+<!-- Paste output from `cat package.json` (粘贴 `cat package.json` 输出的信息) -->
+```
+
+```
+
+### Hexo Information
+
+#### Hexo version
+<!-- Paste output from `hexo -v` (粘贴 `hexo -v` 输出的信息) -->
+```
+
+```
+
+#### Hexo Configuration
+<!-- Paste configuration from Hexo `_config.yml` (从 Hexo `_config.yml` 中粘贴信息) -->
+```yml
+
+```
+
+### NexT Information
+
+**NexT Version:**
+<!-- Check needed with [x] (把 [ ] 换成 [X] 来选择) -->
+
+- [ ] Latest Master branch
+- [ ] Latest Release version
+- [ ] Old version
+
+
+**NexT Scheme:**
+<!-- Check needed with [x] (把 [ ] 换成 [X] 来选择) -->
+
+- [ ] All schemes
+- [ ] Muse
+- [ ] Mist
+- [ ] Pisces
+- [ ] Gemini
+
+
+#### NexT Configuration:
+<!-- Paste ONLY CHANGED CONFIGURATION from NexT `_config.yml` (只粘贴NexT主题配置文件 `_config.yml` 中修改过的部分) -->
+```yml
+
+```
+
+### Other Information <!-- Like Browser, System, Screenshots -->
@@ -0,0 +1,47 @@
+---
+name: Feature Request
+about: Suggest an idea for this project.
+title: ''
+labels: Feature Request
+assignees: ''
+
+---
+
+<!-- ATTENTION!
+IF YOU DON'T FILL OUT THE FOLLOWING INFORMATION WE MIGHT CLOSE YOUR ISSUE WITHOUT INVESTIGATING.
+如果你不填充下面的内容，我们可能会直接关闭你的 issue。
+
+If you want to fast resolve your issue, WRITE IT IN ENGLISH, please. Not all contributors / collaborators know Chinese and Google translate can't always translate issues accurately. Thanks!
+-->
+
+### I agree and want to create new issue <!-- 我确认我已经查看了 -->
+
+<!-- Check all with [x] (把 [ ] 换成 [X] 来选择) -->
+- [ ] Yes, I was on [Hexo Docs page](https://hexo.io/docs/), especially on [Templates](https://hexo.io/docs/templates.html), [Variables](https://hexo.io/docs/variables.html), [Helpers](https://hexo.io/docs/helpers.html) and [Troubleshooting](https://hexo.io/docs/troubleshooting.html).
+- [ ] Yes, I was on [NexT Documentation Site](http://theme-next.org/docs/).
+- [ ] And yes, I already searched for current [issues](https://github.com/theme-next/hexo-theme-next/issues?utf8=%E2%9C%93&q=is%3Aissue) and this is not help to me.
+
+***
+
+### Expected behavior <!-- 预期行为 -->
+
+
+### Actual behavior <!-- 实际行为 -->
+
+
+### Steps to reproduce the behavior <!-- 重现步骤 -->
+1. N/A
+2. N/A
+3. N/A
+
+* Link to demo site with this feature: N/A
+* Link(s) to source code or any usefull link(s): N/A
+
+**NexT Scheme:**
+<!-- Check needed with [x] (把 [ ] 换成 [X] 来选择) -->
+
+- [ ] All schemes
+- [ ] Muse
+- [ ] Mist
+- [ ] Pisces
+- [ ] Gemini
@@ -0,0 +1,92 @@
+---
+name: Non English
+about: Issue in Chinese or any other language.
+title: ''
+labels: Non English
+assignees: ''
+
+---
+
+<!-- ATTENTION!
+IF YOU DON'T FILL OUT THE FOLLOWING INFORMATION WE MIGHT CLOSE YOUR ISSUE WITHOUT INVESTIGATING.
+如果你不填充下面的内容，我们可能会直接关闭你的 issue。
+
+If you want to fast resolve your issue, WRITE IT IN ENGLISH, please. Not all contributors / collaborators know Chinese and Google translate can't always translate issues accurately. Thanks!
+-->
+
+### I agree and want to create new issue <!-- 我确认我已经查看了 -->
+
+<!-- Check all with [x] (把 [ ] 换成 [X] 来选择) -->
+- [ ] Yes, I was on [Hexo Docs page](https://hexo.io/docs/), especially on [Templates](https://hexo.io/docs/templates.html), [Variables](https://hexo.io/docs/variables.html), [Helpers](https://hexo.io/docs/helpers.html) and [Troubleshooting](https://hexo.io/docs/troubleshooting.html).
+- [ ] Yes, I was on [NexT Documentation Site](http://theme-next.org/docs/).
+- [ ] And yes, I already searched for current [issues](https://github.com/theme-next/hexo-theme-next/issues?utf8=%E2%9C%93&q=is%3Aissue) and this is not help to me.
+
+***
+
+### Expected behavior <!-- 预期行为 -->
+
+
+### Actual behavior <!-- 实际行为 -->
+
+
+### Steps to reproduce the behavior <!-- 重现步骤 -->
+1. N/A
+2. N/A
+3. N/A
+
+* Link to demo site with this issue: N/A
+* Link(s) to source code or any usefull link(s): N/A
+
+### Node.js and NPM Information
+<!-- Paste output from `node -v && npm -v` (粘贴 `node -v && npm -v` 输出的信息) -->
+```
+
+```
+
+### Package dependencies Information
+<!-- Paste output from `cat package.json` (粘贴 `cat package.json` 输出的信息) -->
+```
+
+```
+
+### Hexo Information
+
+#### Hexo version
+<!-- Paste output from `hexo -v` (粘贴 `hexo -v` 输出的信息) -->
+```
+
+```
+
+#### Hexo Configuration
+<!-- Paste configuration from Hexo `_config.yml` (从 Hexo `_config.yml` 中粘贴信息) -->
+```yml
+
+```
+
+### NexT Information
+
+**NexT Version:**
+<!-- Check needed with [x] (把 [ ] 换成 [X] 来选择) -->
+
+- [ ] Latest Master branch
+- [ ] Latest Release version
+- [ ] Old version
+
+
+**NexT Scheme:**
+<!-- Check needed with [x] (把 [ ] 换成 [X] 来选择) -->
+
+- [ ] All schemes
+- [ ] Muse
+- [ ] Mist
+- [ ] Pisces
+- [ ] Gemini
+
+
+#### NexT Configuration:
+<!-- Paste ONLY CHANGED CONFIGURATION from NexT `_config.yml` (只粘贴NexT主题配置文件 `_config.yml` 中修改过的部分) -->
+```yml
+
+```
+
+### Other Information <!-- Like Browser, System, Screenshots -->
@@ -0,0 +1,48 @@
+<!-- ATTENTION!
+1. Please, write pull request readme in English. Not all contributors / collaborators know Chinese and Google translate can't always translate issues accurately. 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).
+-->
+
+## PR Checklist
+**Please check if your PR fulfills the following requirements:**
+<!-- Change [ ] to [X] to select -->
+
+- [ ] The commit message follows [our guidelines](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 in [NexT website](https://theme-next.org/docs/) have been added / updated (for new features).
+
+## 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 related changes.
+- [ ] CI related changes.
+- [ ] Documentation content changes.
+- [ ] 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
+...
+```
+
+## Does this PR introduce a breaking change?
+- [ ] Yes.
+- [ ] No.
@@ -0,0 +1,23 @@
+# Configuration for Auto Assign - https://github.com/kentaro-m/auto-assign
+
+# Set to true to add reviewers to pull requests
+addReviewers: true
+
+# Set to true to add assignees to pull requests
+addAssignees: false
+
+# A list of reviewers to be added to pull requests (GitHub user name)
+reviewers:
+  - 1v9
+  - ivan-nginx
+  - maple3142
+  - sli1989
+  - stevenjoezhang
+
+# A number of reviewers added to the pull request
+# Set 0 to add all the reviewers (default: 0)
+numberOfReviewers: 0
+
+# A list of keywords to be skipped the process that add reviewers if pull requests include it
+skipKeywords:
+  - wip
@@ -0,0 +1,63 @@
+# =============================================================================================== #
+# 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
+
+# =============================================================================================== #
+# Configuration for sentiment-bot - https://github.com/behaviorbot/sentiment-bot
+
+# *Required* toxicity threshold between 0 and .99 with the higher numbers being the most toxic
+# Anything higher than this threshold will be marked as toxic and commented on
+sentimentBotToxicityThreshold: .6
+
+# *Required* Comment to reply with
+sentimentBotReplyComment: >
+  Please be sure to review the [code of conduct](https://github.com/theme-next/hexo-theme-next/blob/master/.github/code-of-conduct.md) and be respectful of other users. cc/ @theme-next/next
+
+# =============================================================================================== #
+lockThreads:
+  toxicityThreshold: .7
+  numComments: 2
+  setTimeInHours: 72
+  replyComment: >
+    This thread is being locked due to exceeding the toxicity minimums. cc/ @theme-next/next
+
+# =============================================================================================== #
+# Configuration for todo-bot - https://github.com/JasonEtco/todo
+todo:
+  label: '🗒 To-Do'
@@ -0,0 +1,8 @@
+# Configuration for ESLint Disable Watcher - https://github.com/koddsson/eslint-disable-probot
+
+# Change this to set the number of comments the watcher should comment on a given PR.
+commentLimit: 10
+# The message the bot will post on any lines containing a eslint disable comment.
+commentMessage: Please don't disable eslint rules :pray:
+# A optional regular expression that will match against the branch name and not comment on it if it matches.
+skipBranchMatching: null
@@ -0,0 +1,39 @@
+# 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:
+  - backlog
+
+# Label to add before locking, such as `outdated`. Set to `false` to disable
+lockLabel: 🔒 Locked
+
+# 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
@@ -0,0 +1,29 @@
+# Configuration for Mergeable - https://github.com/jusx/mergeable
+
+version: 2
+mergeable:
+  - when: pull_request.*
+    validate:
+      - do: description
+        no_empty:
+          enabled: false
+
+      - do: title
+        must_exclude:
+          regex: ^\[WIP\]
+
+      - do: label
+        must_include:
+          regex: 'feat|imp|fix|doc|i18n'
+        must_exclude:
+          regex: 'wip|work in progress'
+
+      - do: project
+        no_empty:
+          enabled: true
+        must_include:
+          regex: 'feat|imp|fix|doc|loc'
+
+      - do: milestone
+        no_empty:
+          enabled: true
@@ -0,0 +1,34 @@
+# 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: 🛠 Improvements
+    label: Improvement
+
+  - title: 🐞 Bug Fixes
+    label: Bug Fix
+
+  - 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 v$PREVIOUS_TAG and v$NEXT_MINOR_VERSION](https://github.com/theme-next/hexo-theme-next/compare/v$PREVIOUS_TAG...v$NEXT_MINOR_VERSION)
@@ -0,0 +1,29 @@
+# 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
+  - improvement need
+  - wait for answer
+  - need verify
+  - question
+  - backlog
+  - docs
+# 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
@@ -0,0 +1,23 @@
+# Configuration for Support Requests - https://github.com/dessant/support-requests
+
+# Label used to mark issues as support requests
+supportLabel: Support
+
+# Comment to post on issues marked as support requests, `{issue-author}` is an
+# optional placeholder. Set to `false` to disable
+supportComment: >
+  :wave: @{issue-author}, we use the issue tracker exclusively for bug reports
+  and feature requests. However, this issue appears to be a support request.
+  Please use our [support channels](https://github.com/theme-next/hexo-theme-next/tree/master#feedback) to get help with the project.
+
+# Close issues marked as support requests
+close: true
+
+# Lock issues marked as support requests
+lock: false
+
+# Assign `off-topic` as the reason for locking. Set to `false` to disable
+setLockReason: true
+
+# Repository to extend settings from
+# _extends: repo
@@ -0,0 +1,5 @@
+# Configuration for top-issue-bot - https://github.com/adamzolyak/gh-vote-bot
+
+labelName: '👍 Top Issue!'
+labelColor: '006b75'
+numberOfIssuesToLabel: 10
@@ -0,0 +1,8 @@
+# Configuration for weekly-digest - https://github.com/apps/weekly-digest
+
+publishDay: sun
+canPublishIssues: true
+canPublishPullRequests: true
+canPublishContributors: true
+canPublishStargazers: true
+canPublishCommits: true