If you notice something to improve, the easiest way to do that is to
- Fork this repo
- Set up a branch
- Make the changes (see
/content
) - Submit a PR
So all in all it's just a regular GitHub PR flow.
Alternatively you can open an issue and we'll look into it.
Note that gh-pages
branch and wiki content gets generated based on the main repository content.
The generator converts the wiki content to Gitbook (standalone site). In this case it is pushed to gh-pages
. Use it as follows:
npm install
npm run generate-gitbook
This should generate /gh-pages
. You can serve that directory through some static server (ie. hit serve
at /gh-pages
).
It is possible to deploy the book by hitting npm run deploy-gitbook
. This will update gh-pages
branch.