...
 
Commits (2)
......@@ -5,6 +5,11 @@ theme.sidebar.display: hide
---
# About Rohan Sakhale
Mr. Rohan Sakhale is a **Software Mentor** and **Engineer**. He has over **7 years** of experience in I.T. Industry. His experience in several dimension of technologies has always helped him perceive from idea to product. If not coding on any project, occasionally he spends time with students helping them with their project or teaching something new i.e. industry oriented to them.
"Given the right set of raw materials, it can be developed into a finished saleable product."
He has worked with two Top 500 fortune companies namely **[Saba Software](https://www.saba.com)** & **[Diebold Nixdorf](http://www.dieboldnixdorf.com/en-us)**, wherein he was awarded several times for his contributions. Presently with passion of being an entrepreneur, he works with his own startup "**[Sai Ashirwad Informatia](https://about.saiashirwad.com)**" who visions for two main things, firstly to solve business problems with technology and secondly bridge the gap between students and industry.
Known for being **Software Mentor** by passion and **Engineer** by expertise with over **10+years** in Web Development as Freelancer & **7+ years** of Industrial Development experience. Thanks for several dimension from Prof. Rajesh Patkar (my Guru) his perception has always help me perceive from idea to product in effective, efficient & cost saving manner.
If not coding on any project, occasionally you will find me spending time with students spreading practical knowledge on latest technology trends or code practices.
I worked with two Top 500 fortune companies **[Saba Software](https://www.saba.com)** & **[Diebold Nixdorf](http://www.dieboldnixdorf.com/en-us)**, wherein was awarded several times for contributions. Presently I contribute to a very Dynamic startup **[Indigital Technologies LLP](https://indigitalit.com)** developing innovative patent-pending products that has the capability of disrupting the global market with Technology. Parallely, you will find me contributing to my own startup "**[Sai Ashirwad Informatia](https://about.saiashirwad.com)**" delivering client services, infrastructure support & training.
[#PHP](/tags/php) [#Java](/tags/java) [#JavaScript](/tags/javascript) #Laravel #Vue #CI #GitLab #ProjectManagement #TestAutomation #Trainer #AndroidExpert #Vue #Flutter #SonarQube #CodeQuality
\ No newline at end of file
This diff is collapsed.
<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="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>
......
<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="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>
......@@ -154,57 +157,51 @@ We use "labels" in the issue tracker to help classify Pull requests and Issues.
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`
Issues related:
- By types
- `Bug`: A detected bug that needs to be confirmed
- `Improvement Need`: An issue that needs improvement
- `Feature Request`: An issue that wants a new feature
- `Non English`: Requires the attention of a multi-lingual maintainer
- `Discussion`: An issue that needs to be discussed
- `Question`: An issue about questions
- `Meta`: Denoting a change of usage conditions
- `Polls`: An issue that initiated a poll
- By contents
- `Roadmap`: An issue about future development
- `Hexo`: An issue related to Hexo
- `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
- `Fonts`: An issue related to fonts
- `PJAX`: An issue related to PJAX
- `Custom`: An issue related to custom things
- `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
- `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
- `Probably Solved`: An issue that has been resolved maybe
- `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
- `Locked`: This issue has been automatically locked since there has not been any recent activity after it was closed
Pull requests related:
- `Breaking Change`: A pull request that makes breaking change
- `External Change`: A pull request that makes update for external change
- `Bug Fix`: A pull request that fixes the related bug
- `Docs`: A pull request that Instruction document has been added
- `New Feature`: A pull request that provides a new feature
- `Feature`: A pull request that provides an option or addition to existing feature
- `Improvement`: A pull request that improves NexT
- `i18n`: A pull request that makes new languages translation
- `Performance`: A pull request that improves the performance
- `Discussion`: A pull request that needs to be discussed
- `Work in Progress`: A pull request that is still working in progress
- `Skip Release`: A pull request that should be excluded from release note
- `v6.x`: A pull request that bug fixes and some improvements, related to old NexT version 6
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
<a name="commit-messages-rules"></a>
......
<!-- 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) -->
---
name: Bug Report
about: Create a report to help us improve.
about: Something isn't working as expected
title: ''
labels: Bug
assignees: ''
---
<!-- ATTENTION!
IF YOU DON'T FILL OUT THE FOLLOWING INFORMATION WE MIGHT CLOSE YOUR ISSUE WITHOUT INVESTIGATING.
如果你不填充下面的内容,我们可能会直接关闭你的 issue。
Please check if your Issue fulfills the following requirements. If you refuse to fill out the following information in accordance with the template, we may close your issue without conducting an investigation.
请务必确认您在提交此 Issue 前已经查看并完成了下列检查单中的所有事项。如果您拒绝根据模板填写以下信息,我们可能会在不进行调查的情况下关闭您的 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!
-->
## Issue Checklist <!-- 我确认我已经查看了 -->
<!-- Change [ ] to [x] to select, not [ x] or [x ] (将 [ ] 换成 [x] 来选择,而非 [ x] 或者 [x ]) -->
### 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.
- [ ] I am using [the latest](https://github.com/theme-next/hexo-theme-next/releases/latest) version of NexT.
- [ ] I have executed `hexo clean`, cleared the browser cache and disabled all CDN services (e.g. Cloudflare Rocket Loader), this issue still exists.
- [ ] I have confirmed that this issue only appears in theme NexT, but cannot be reproduced in other themes (e.g. default theme landscape). In other words, prove that this is a NexT issue, not a issue from Hexo.
- [ ] I have already viewed [NexT Documentation Site](http://theme-next.org/docs/) and [Hexo Docs page](https://hexo.io/docs/), especially [Troubleshooting](https://hexo.io/docs/troubleshooting.html) part.
- [ ] I have already viewed the latest Roadmap on GitHub and searched for current [issues](https://github.com/theme-next/hexo-theme-next/issues?utf8=%E2%9C%93&q=is%3Aissue), which does not help me.
***
### Expected behavior <!-- 预期行为 -->
## Expected behavior <!-- 预期行为 -->
## Actual behavior <!-- 实际行为 -->
<!-- Please provide at least one of the following information (请至少提供以下的一项信息) -->
### Actual behavior <!-- 实际行为 -->
- Links to demo site with this issue: N/A
- Links to repository or source code of the blog: N/A
### Steps to reproduce the behavior <!-- 重现步骤 -->
## 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
## Environment Information
### Node.js and NPM Information
<!-- Paste output from `node -v && npm -v` (粘贴 `node -v && npm -v` 输出的信息) -->
......@@ -44,49 +46,21 @@ If you want to fast resolve your issue, WRITE IT IN ENGLISH, please. Not all con
```
### Package dependencies Information
<!-- Paste output from `cat package.json` (粘贴 `cat package.json` 输出的信息) -->
```
```
### Hexo Information
#### Hexo version
<!-- Paste output from `hexo -v` (粘贴 `hexo -v` 输出的信息) -->
<!-- Paste output from `npm ls --depth 0` (粘贴 `npm ls --depth 0` 输出的信息) -->
```
```
#### Hexo Configuration
<!-- Paste configuration from Hexo `_config.yml` (从 Hexo `_config.yml` 中粘贴信息) -->
### 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` 中修改过的部分) -->
### NexT Configuration
<!-- Paste ONLY CHANGED CONFIGURATION from NexT `_config.yml` (只粘贴 NexT 主题配置文件 `_config.yml` 中修改过的部分) -->
```yml
```
### Other Information <!-- (Like Browser, System, Screenshots) -->
## Other Information <!-- (Like Browser, System, Screenshots) -->
---
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 -->
---
name: Feature Request
about: Suggest an idea for this project.
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。
Please check if your Issue fulfills the following requirements. If you refuse to fill out the following information in accordance with the template, we may close your issue without conducting an investigation.
请务必确认您在提交此 Issue 前已经查看并完成了下列检查单中的所有事项。如果您拒绝根据模板填写以下信息,我们可能会在不进行调查的情况下关闭您的 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!
-->
## Issue Checklist <!-- 我确认我已经查看了 -->
<!-- Change [ ] to [x] to select, not [ x] or [x ] (将 [ ] 换成 [x] 来选择,而非 [ x] 或者 [x ]) -->
### 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.
- [ ] I am using [the latest](https://github.com/theme-next/hexo-theme-next/releases/latest) version of NexT.
- [ ] I have already viewed [NexT Documentation Site](http://theme-next.org/docs/) and [Hexo Docs page](https://hexo.io/docs/), especially [Troubleshooting](https://hexo.io/docs/troubleshooting.html) part.
- [ ] I have already viewed the latest Roadmap on GitHub and searched for current [issues](https://github.com/theme-next/hexo-theme-next/issues?utf8=%E2%9C%93&q=is%3Aissue), which does not help me.
***
### Expected behavior <!-- 预期行为 -->
## Expected behavior <!-- 预期行为 -->
## Actual behavior <!-- 实际行为 -->
<!-- Please provide at least one of the following information (请至少提供以下的一项信息) -->
### Actual behavior <!-- 实际行为 -->
- Links to demo site with this feature: N/A
- Links to repository or source code of the blog: N/A
### Steps to reproduce the behavior <!-- 重现步骤 -->
## 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
---
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 -->
---
name: Other
about: Not a question, feature request or bug report
title: ''
labels: ''
assignees: ''
---
Please check if your Issue fulfills the following requirements. If you refuse to fill out the following information in accordance with the template, we may close your issue without conducting an investigation.
请务必确认您在提交此 Issue 前已经查看并完成了下列检查单中的所有事项。如果您拒绝根据模板填写以下信息,我们可能会在不进行调查的情况下关闭您的 Issue。
## Issue Checklist <!-- 我确认我已经查看了 -->
<!-- Change [ ] to [x] to select, not [ x] or [x ] (将 [ ] 换成 [x] 来选择,而非 [ x] 或者 [x ]) -->
- [ ] I am using [the latest](https://github.com/theme-next/hexo-theme-next/releases/latest) version of NexT.
- [ ] I have already viewed [NexT Documentation Site](http://theme-next.org/docs/) and [Hexo Docs page](https://hexo.io/docs/), especially [Troubleshooting](https://hexo.io/docs/troubleshooting.html) part.
- [ ] I have already viewed the latest Roadmap on GitHub and searched for current [issues](https://github.com/theme-next/hexo-theme-next/issues?utf8=%E2%9C%93&q=is%3Aissue), which does not help me.
***
---
name: Question
about: I have a question for NexT (e.g. Customize)
title: ''
labels: Custom
assignees: ''
---
Please check if your Issue fulfills the following requirements. If you refuse to fill out the following information in accordance with the template, we may close your issue without conducting an investigation.
请务必确认您在提交此 Issue 前已经查看并完成了下列检查单中的所有事项。如果您拒绝根据模板填写以下信息,我们可能会在不进行调查的情况下关闭您的 Issue。
## Issue Checklist <!-- 我确认我已经查看了 -->
<!-- Change [ ] to [x] to select, not [ x] or [x ] (将 [ ] 换成 [x] 来选择,而非 [ x] 或者 [x ]) -->
- [ ] I am using [the latest](https://github.com/theme-next/hexo-theme-next/releases/latest) version of NexT.
- [ ] I have executed `hexo clean`, cleared the browser cache and disabled all CDN services (e.g. Cloudflare Rocket Loader), this issue still exists.
- [ ] I have confirmed that this issue only appears in theme NexT, but cannot be reproduced in other themes (e.g. default theme landscape). In other words, prove that this is a NexT issue, not a issue from Hexo.
- [ ] I have already viewed [NexT Documentation Site](http://theme-next.org/docs/) and [Hexo Docs page](https://hexo.io/docs/), especially [Troubleshooting](https://hexo.io/docs/troubleshooting.html) part.
- [ ] I have already viewed the latest Roadmap on GitHub and searched for current [issues](https://github.com/theme-next/hexo-theme-next/issues?utf8=%E2%9C%93&q=is%3Aissue), 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 -->
......@@ -7,16 +7,18 @@
4. We use ESLint and Stylint for identifying and reporting on patterns in JavaScript and Stylus. Please execute the following commands:
```sh
cd path/to/theme-next
npm install
npm run test
npm run test lint:stylus
```
And make sure that this PR does not cause more warning messages.
5. Please check if your PR fulfills the following requirements.
-->
## PR Checklist
**Please check if your PR fulfills the following requirements:**
<!-- Change [ ] to [X] to select -->
## PR Checklist <!-- 我确认我已经查看了 -->
<!-- Change [ ] to [x] to select, not [ x] or [x ] (将 [ ] 换成 [x] 来选择,而非 [ x] 或者 [x ]) -->
- [ ] 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).
......@@ -26,7 +28,7 @@ And make sure that this PR does not cause more warning messages.
<!-- 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?**
<!-- What kind of change does this PR introduce? -->
- [ ] Bugfix.
- [ ] Feature.
......@@ -38,12 +40,12 @@ And make sure that this PR does not cause more warning messages.
- [ ] Other... Please describe:
## What is the current behavior?
<!-- Please describe the current behavior that you are modifying, or link to a relevant issue. -->
<!-- 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... -->
<!-- Description about this pull, in several words -->
- Screenshots with this changes: N/A
- Link to demo site with this changes: N/A
......@@ -51,7 +53,7 @@ Issue resolved: N/A
### How to use?
In NexT `_config.yml`:
```yml
...
```
## Does this PR introduce a breaking change?
......
......@@ -8,11 +8,10 @@ daysUntilLock: 365
skipCreatedBefore: false
# Issues and pull requests with these labels will be ignored. Set to `[]` to disable
exemptLabels:
- backlog
exemptLabels: []
# Label to add before locking, such as `outdated`. Set to `false` to disable
lockLabel: 🔒 Locked
lockLabel: false
# Comment to post before locking. Set to `false` to disable
lockComment: >
......
......@@ -6,20 +6,20 @@ categories:
- title: '💥 Breaking Changes'
label: '💥 Breaking Change'
- title: '🌀 External Changes'
label: '🌀 External Change'
- title: '🌟 New Features'
label: '🌟 New Feature'
- title: ' Features'
label: ' Feature'
- title: '🐞 Bug Fixes'
label: '🐞 Bug Fix'
- title: '🛠 Improvements'
label: '🛠 Improvement'
- title: '🐞 Bug Fixes'
label: '🐞 Bug Fix'
- title: '🌀 External Changes'
label: '🔌 3rd Party Plugin'
- title: '📖 Documentation'
label: '📖 Docs'
......
......@@ -8,7 +8,7 @@ daysUntilClose: 7
exemptLabels:
- bug
- feature request
- improvement need
- improvement
- wait for answer
- need verify
- question
......
......@@ -14,6 +14,6 @@ source/lib/font-awesome/less/
source/lib/font-awesome/scss/
!source/lib/font-awesome/
!source/lib/jquery/
!source/lib/anime.min.js
!source/lib/velocity/
language: node_js
#node_js: node
node_js: lts/*
node_js: node
cache:
directories:
- node_modules
npm: true
install: npm install
before_script:
- npm install -g gulp
addons:
browserstack:
username: "ivannginx1"
access_key:
secure: "NutOhdgtUdBUXMPZhy8X1F1Jq+tan1LeNOV0FArBt15SNlxtNArqhiyTi4XnG9MPruX4306aGF2RBrKso+OiGNRdGtRGngH613Q0GWNtlC/boMqnI7fHqLIyCs6S12y2uA8PK4Ifxg9bZ0VtCTYYbMy+p1KvBM//L12vmtfdnby8z5Qvex3tB3dLoPOR50CKkINHJVDLm+iVRFrdz4/83oDsulZSRRGIaxu5taDWPIcp3fYZtre2Nc+RXcsyFDyjN7U0Hvr5tKBbloJxXEQEBv2xLkMOtp85nmCPD06s1Il8Wus1ux3raVsfUyaW5FpNX37Jeb5e00RQUM1wgU5m75H6qiGwDvQswbugJG0i/a2nNfsgVmbrSZdMnkHcx2Uxmrw4ejyEP5NSrJSBi05Ck1fQ4UsZ4Qkdf1fd04SI0LpLWt43eoNO/7rHKsQoP4LCX9gxKUuC075NEBLODyJ529RYfA6dKKwwH6o0ZbOgASmCoAWaM65g4+FHRnJcKL/Kj9ZWklQtRa7/ynlHaA65jefFS2lB8Ut6d3rXDDBih9mIrwV1uUaEH96xgAN42bgU/vY6FGzNkDOYZqj4YfsepDM0wbOsslFie7JZq7iFjsYvrXqLvYUMk37AZwQ2Sb6uH4tIT4Qw/4oZfDzA1En3/8HdZJ28nKW/lzjwMSqheIY="
This diff is collapsed.
This diff is collapsed.
......@@ -12,7 +12,7 @@ NexT provides Algolia search plugin for index your hexo website content. To use
```
$ cd hexo
$ npm install --save hexo-algolia
$ npm install hexo-algolia
```
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.
......
This diff is collapsed.
......@@ -8,8 +8,6 @@ At present, NexT encourages users to store some options in site's `/_config.yml`
In order to resolve this issue, NexT will take advantage of 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.
If you prefer Hexo 2.x, you can still use the old approach for configurations. NexT is still compatible with Hexo 2.x (but errors are possible).
<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.
......
......@@ -3,15 +3,16 @@
<h2 align="center">Step 1 &rarr; 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
```
```sh
$ cd hexo
$ ls
_config.yml node_modules package.json public scaffolds source themes
```
<h2 align="center">Step 2 &rarr; Get NexT</h2>
<p align="center">Download theme from GitHub.</br>
<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]
......
......@@ -105,7 +105,7 @@ Please note the difference between **site config file** and **theme config file*
- Open cmd then switch to **root path of site**, type commands to install `hexo-leancloud-counter-security` plugin:
```
npm install hexo-leancloud-counter-security --save
npm install hexo-leancloud-counter-security
```
- Open **site config file** `_config.yml`, add those config:
......
......@@ -2,35 +2,29 @@
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 turn on `enable` of `math` and choose a render engine for it (located in `next/_config.yml`):
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`).
```yml
math:
enable: true
```
Notice: only turning on `enable` of `math` **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.
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/) (default is MathJax).
For now, NexT provides two Render Engines: [MathJax](https://www.mathjax.org/) and [Katex](https://khan.github.io/KaTeX/).
### MathJax (default)
### MathJax
If you use MathJax to render Math Equations, you need to use **only one of them**: [hexo-renderer-pandoc](https://github.com/wzpan/hexo-renderer-pandoc) or [hexo-renderer-kramed](https://github.com/sun11/hexo-renderer-kramed).
Firstly, you need to uninstall the original renderer `hexo-renderer-marked`, and install one of the renderer above:
```sh
npm un hexo-renderer-marked --save
npm i hexo-renderer-pandoc --save # or hexo-renderer-kramed
npm uninstall hexo-renderer-marked
npm install hexo-renderer-pandoc # or hexo-renderer-kramed
```
Secondly, in `next/_config.yml`, turn on `enable` of `math` and choose `mathjax` as engine.
Secondly, in `next/_config.yml`, turn on `enable` of `mathjax`.
```yml
math:
enable: true
...
mathjax:
enable: true
......@@ -114,16 +108,15 @@ If you use Katex to render Math Equations, you need to use **only one of those r
Firstly, you need to uninstall the original renderer `hexo-renderer-marked`, and **install one of selected above**.
```sh
npm un hexo-renderer-marked --save
npm i hexo-renderer-markdown-it-plus --save
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 `math` and choose `katex` as render engine.
Secondly, in `next/_config.yml`, turn on `enable` option of `katex`.
```yml
math:
enable: true
...
katex:
enable: true
......@@ -141,7 +134,7 @@ hexo clean && hexo g -d
If you use `hexo-renderer-markdown-it`,you also need to add `markdown-it-katex` as its plugin:
```
npm i markdown-it-katex --save
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`:
......@@ -171,9 +164,9 @@ markdown:
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.7.1, some of those bugs might be caused by the outdated version of Katex we use.
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.7.1.
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.
......@@ -193,8 +186,6 @@ If your content of config is put just directly after the config name, then a spa
```yml
# Math Formulas Render Support
math:
enable: true
# 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.
......@@ -213,12 +204,6 @@ math:
copy_tex: false
```
### `enable`
`true` or `false`, default is `false`.
`true` to turn on render of Math Equations, `false` to turn off it.
### `per_page`
`true` or `false`, default is `true`.
......
<h1 align="center">Update from NexT v5.1.x</h1>
There are no hard breaking changes between 5.1.x and 6.0.x versions. It's change major version to 6 because:
There are no hard breaking changes between 5.1.x and the latest version. It's change major version to 6 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).
......@@ -13,7 +13,7 @@ So, i suggest to update from version 5 to version 6 in this way:
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 v6.x 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.
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)
......
......@@ -8,8 +8,6 @@
Во избежании проблемы, NexT использует преимущество Hexo [дата-файлов](https://hexo.io/docs/data-files.html). И т.к. дата-файлы были представлены в Hexo 3, необходимо обновиться до Hexo 3.0 (или выше) для использования этой возможности.
Если же Вы предпочитаете Hexo 2.x, то можно использовать старый способ для конфигураций. NexT всё ещё совместим с Hexo 2.x (но возможны ошибки).
<h2 align="center">Способ 1: Hexo-Путь</h2>
Используя этот способ, вся конфигурация будет раположена в корневом конфиге hexo (`/_config.yml`), благодаря чему нет необходимости изменять оригинальный конфиг темы (`/themes/next/_config.yml`) или создавать какие-либо новые файлы. Но в этом случае необходимо сохранять двойные отступы внутри `theme_config` параметра.
......
......@@ -3,15 +3,16 @@
<h2 align="center">Шаг 1 &rarr; Идём в директорию Hexo</h2>
Меняем каталог на **корневой hexo**. Там должны находиться `node_modules`, `source`, `themes` и другие папки:
```sh
$ cd hexo
$ ls
_config.yml node_modules package.json public scaffolds source themes
```
```sh
$ cd hexo
$ ls
_config.yml node_modules package.json public scaffolds source themes
```
<h2 align="center">Шаг 2 &rarr; Скачиваем NexT</h2>
<p align="center">Скачиваем тему с GitHub.</br>
<p align="center">Скачиваем тему с GitHub.<br>
Имеются <b>3 способа</b> как зделать это, нужно <b>выбрать только 1</b> из них.</p>
### Способ 1: Скачиваем [последнюю версию релиза][releases-latest-url]
......
This diff is collapsed.
<h1 align="center">Обновление из-под NexT v5.1.x</h1>
Между версиями 5.1.x и 6.0.x нет жёстких изменений. Версия сменилась на мажорную 6 по следующим причинам:
Между версией 5.1.x и последней версиями нет жёстких изменений. Версия сменилась на мажорную 6 по следующим причинам:
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` не имеет никаких сторонних nodejs зависимостей, не имеет [языкового фильтра](https://github.com/willin/hexo-wordcount/issues/7) что обеспечивает улучшенную производительность при генерации сайта.
......@@ -13,7 +12,7 @@
1.2. Пользовательских CSS-стилей, которые расположены в `next/source/css/_custom/*` и `next/source/css/_variables/*` директориях.\
1.3. Пользовательских layout-стилей, которые расположены в `next/layout/_custom/*`.\
1.4. Любые другие всевозможные пользовательские изменения, которые могут быть найдены любым инструментом для сравнения файлов.
2. Склонировать новый v6.x репозиторий в любую другую директорию, отличную от `next`. Например, в директорию `next-reloaded`: `git clone https://github.com/theme-next/hexo-theme-next themes/next-reloaded`. Итак, нет необходимости трогать старую NexT 5.1.x директорию и можно работать с новой `next-reloaded`.
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).
......@@ -10,7 +10,7 @@ NexT 内部提供 Algolia 的搜索功能,要使用此功能请确保所使用
```
$ cd hexo
$ npm install --save hexo-algolia
$ npm install hexo-algolia
```
1.`API Keys` 页面找到需要使用的一些配置的值,包括 `ApplicationID``Search-Only API Key`。注意,`Admin API Key` 需要保密保存,不要外泄。
......
<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="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>
......
<div align="right">语言:
<a title="英语" href="../../.github/CONTRIBUTING.md">:us:</a>
:cn:
<a title="俄语" href="../ru/CONTRIBUTING.md">:ru:</a></div>
<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>
......@@ -151,57 +153,51 @@
如果您不确定某个标签的含义,或者不知道将哪些标签应用于 PR 或 issue,千万别错过这个。
Issues 的标签:使用 `类型`+`内容`+`结果` 的组合
Issue 的标签:
- 类型
- `Bug`: 检测到需要进行确认的 Bug
- `Improvement Need`: 需要改进的 Issue
- `Feature Request`: 提出了新功能请求的 Issue
- `Non English`: 需要多语言维护者参与的 Issue
- `Discussion`: 需要进行讨论的 Issue
- `Question`: 提出疑问的 Issue
- `Meta`: 表明使用条款变更的 Issue
- `Polls`: 发起投票的 Issue
- 内容
- `Roadmap`: 与 NexT 主题发展相关的 Issue
- `Hexo`: 与 Hexo 相关的 Issue
- `3rd Party Service`: 与第三方服务相关的 Issue
- `Docs`: 需要添加文档说明的 Issue
- `Configurations`: 与 NexT 主题设置相关的 Issue
- `CSS`: 与 NexT 主题 CSS 文件相关的 Issue
- `Fonts`: 与 NexT 主题字体相关的 Issue
- `PJAX`: 与 NexT 主题 PJAX 相关的 Issue
- `Custom`: 与 NexT 主题个性化相关的 Issue
- `Support`: 被标记为支持请求的 Issue
- `Polls`: 发起投票的 Issue
- 结果
- `Duplicate`: 重复提及的 Issue
- `Irrelevant`: 与 NexT 主题无关的 Issue
- `Invalid`: 无法复现的 Issue
- `Expected Behavior`: 与预期行为相符的 Issue
- `Need More Info`: 需要更多信息的 Issue
- `Need Verify`: 需要开发人员或用户确认 Bug 或解决方法的 Issue
- `Can't Reproduce`: 无法复现的 Issue
- `Verified`: 已经被确认的 Issue
- `Help Wanted`: 需要帮助的 Issue
- `Probably Solved`: 可能已经解决的 Issue
- `Solved`: 已经解决的 Issue
- `Backlog`: 待解决的 Issue
- `Stale`: 由于长期无人回应被封存的 Issue
- `Locked`: 关闭后长期没有新动态的 Issue
Pull requests 的标签:
- `Breaking Change`: 产生重大变动的 Pull request
- `External Change`: 针对外部变动进行更新的 Pull request
- `Bug Fix`: 修复相关 Bug 的 Pull request
- `Docs`: 添加了文档说明的 Pull request
- `New Feature`: 添加了新功能的 Pull request
- `Feature`: 为现有功能提供选项或加成的 Pull request
- `Improvement`: 改进了 NexT 主题的 Pull request
- `i18n`: 更新了翻译的 Pull request
- `Performance`: 提高了 NexT 主题性能的 Pull request
- `Discussion`: 需要进行讨论的 Pull request
- `Work in Progress`: 仍在进行改动和完善的 Pull request
- `Skip Release`: 无需在 Release Note 中展现的 Pull request
- `v6.x`: 与 NexT v6.x 旧版相关的用于修复和改进的 Pull request
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
<a name="commit-messages-rules"></a>
......
......@@ -8,8 +8,6 @@
为了解决这一问题,NexT 将利用 Hexo 的[数据文件](https://hexo.io/docs/data-files.html)特性。因为数据文件是在 Hexo 3 中被引入,所以你需要更新至 Hexo 3.0 以后的版本来使用这一特性。
如果你仍然希望使用 Hexo 2.x,你依旧可以按老的方式进行配置。NexT 仍然兼容 Hexo 2.x(但可能会出现错误)。
<h2 align="center">选择 1:Hexo 方式</h2>
使用这一方式,你的全部配置都将置于 Hexo 站点配置文件(`/_config.yml`),并且不需要修改 `/themes/next/_config.yml`,或者创建什么其他的文件。但是所有的主题选项必须放置在 `theme_config` 后,并全部增加两个空格的缩进。
......
......@@ -3,15 +3,16 @@
<h2 align="center">步骤 1 &rarr; 进入 Hexo 目录</h2>
进入 **Hexo 根**目录。这一目录中应当有 `node_modules``source``themes` 等若干子目录:
```sh
$ cd hexo
$ ls
_config.yml node_modules package.json public scaffolds source themes
```
```sh
$ cd hexo
$ ls
_config.yml node_modules package.json public scaffolds source themes
```
<h2 align="center">步骤 2 &rarr; 获取 NexT</h2>
<p align="center">从 GitHub 下载主题。</br>
<p align="center">从 GitHub 下载主题。<br>
为了下载这一主题,共有 <b>3 种选项</b>可选。你需要选择其中<b>唯一一个方式</b></p>
### 选项 1:下载[最新 release 版本][releases-latest-url]
......
......@@ -115,7 +115,7 @@ leancloud_visitors:
- 打开 cmd 并切换至**博客根目录**,键入以下命令以安装 `hexo-leancloud-counter-security` 插件:
```
npm install hexo-leancloud-counter-security --save
npm install hexo-leancloud-counter-security
```
- 打开**博客配置文件** `_config.yml`,新增以下配置:
......
<h1 align="center">数学公式</h1>
NexT 内部提供数学公式渲染的引擎,这样你就不需要自己手动在模板中引入 JS 或者 CSS;
只需要`next/_config.yml``math``enable` 选项改为 `true`,并选择对应的渲染引擎即可:
只需要选择对应的渲染引擎,并在 `next/_config.yml` 中将其 `enable` 选项改为 `true` 即可。
```yml
math:
enable: true
```
需要注意的是,仅仅将 `math``enable` 打开**并不能让你看到数学公式**,你还需要**使用对应的 Hexo 渲染器(Renderer)** 才能真正在博客页面中显示出数学公式。引擎对应使用的 Hexo 渲染器会在引擎相关的部分介绍。
需要注意的是,仅仅将 `enable` 打开**并不能让你看到数学公式**,你还需要**使用对应的 Hexo 渲染器(Renderer)** 才能真正在博客页面中显示出数学公式。引擎对应使用的 Hexo 渲染器会在引擎相关的部分介绍。
<h2 align="center">提供的渲染引擎</h2>
目前,NexT 提供两种数学公式渲染引擎,分别为 [MathJax](https://www.mathjax.org/)[Katex](https://khan.github.io/KaTeX/),默认为 MathJax
目前,NexT 提供两种数学公式渲染引擎,分别为 [MathJax](https://www.mathjax.org/)[Katex](https://khan.github.io/KaTeX/)
### MathJax(默认)
### MathJax
如果你选择使用 MathJax 进行数学公式渲染,你需要使用 [hexo-renderer-pandoc](https://github.com/wzpan/hexo-renderer-pandoc) 或者 [hexo-renderer-kramed](https://github.com/sun11/hexo-renderer-kramed) 这两个渲染器的其中一个。
首先,卸载原有的渲染器 `hexo-renderer-marked`,并安装这两种渲染器的**其中一个**
```sh
npm un hexo-renderer-marked --save
npm i hexo-renderer-pandoc --save # 或者 hexo-renderer-kramed
npm uninstall hexo-renderer-marked
npm install hexo-renderer-pandoc # 或者 hexo-renderer-kramed
```
然后在 `next/_config.yml` 中将 `math``enable` 打开,并选择 `mathjax` 作为渲染引擎
然后在 `next/_config.yml` 中将 `mathjax``enable` 打开
```yml
math:
enable: true
...
mathjax:
enable: true
......@@ -114,17 +108,15 @@ Katex 渲染引擎相对于 MathJax 来说**大大提高了速度**,而且在
首先,卸载原有的渲染器 `hexo-renderer-marked`,并安装这两种渲染器的**其中一个**:
```sh
npm un hexo-renderer-marked --save
npm i hexo-renderer-markdown-it-plus --save
npm uninstall hexo-renderer-marked
npm install hexo-renderer-markdown-it-plus
# 或者 hexo-renderer-markdown-it
```
然后在 `next/_config.yml` 中将 `math` 的 `enable` 打开,并选择 `katex` 作为渲染引擎。
然后在 `next/_config.yml` 中将 `katex` 的 `enable` 打开。
```yml
math: