Contents
Development
Hexo welcomes you to join the development of Hexo. This document will help you through the process.
Before You Start
Please follow the coding style:
- Follow Google JavaScript Style Guide.
- Use soft-tabs with a two space indent.
- Don’t put commas first.
Workflow
- Fork the project.
- Clone the repository to your computer and install dependencies.
$ git clone https://github.com/<username>/hexo.git$ cd hexo$ npm install$ git submodule update --init
- Create a feature branch for your change.
$ git checkout -b new_feature
- Start hacking. Don’t forget to run tests.
- Push the branch:
$ git push origin new_feature
- Create a pull request against the
master
branch and describe the change.
Don't change version in package.jsonWhen making changes on Hexo, don’t change version number in
package.json
.
Updating Documentation
The Hexo documentation is open source and you can find the source code on hexojs/site. To update the documentation:
- Fork the project
- Clone the repository to your computer and install dependencies.
$ git clone https://github.com/<username>/site.git$ cd site$ npm install
- Start editing the documentation. You can start the server for live previewing.
$ hexo server
- Push the branch:
- Create a pull request against the
master
branch and describe the change.
Reporting Issues
When you encounter some problems when using Hexo, you can find the solutions in [Troubleshooting] or ask me on GitHub or Google Group. If you can’t find the answer, please report it on GitHub.
- Represent the problem in debug mode.
$ hexo --debug
- Check the version info.
$ hexo version
- Post both debug message and version info on GitHub.