docsify-cli
docsify-cli copied to clipboard
🖌 docsify cli tool - A magical documentation generator.
Command and Log: ``` $ npm i -g docsify-cli /root/.nvm/versions/node/v14.15.1/bin/docsify -> /root/.nvm/versions/node/v14.15.1/lib/node_modules/docsify-cli/bin/docsify > [email protected] postinstall /root/.nvm/versions/node/v14.15.1/lib/node_modules/docsify-cli/node_modules/docsify > opencollective-postinstall sh: 1: opencollective-postinstall: Permission denied npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@~2.3.1...
Github pages serve user sites one level down: ``` https://davestewart.github.io/vuex-pathify ``` It would be useful to be able to simulate this: ```bash docsify serve docs --path vuex-pathify ``` ``` localhost:3000/vuex-pathify...
## changes * Add a japanese document in `docs/jp/` .
Repeatedly call response.end()
I am using docsify-cli, and run from docker, and route to the docker server from separate server using reverse proxy. I found livereload is injected to index as follow. ``...
## Before this PR Using a `base-path` in `$docsify` config makes `doscify serve .` unusable for local development - all requests just return 404. ```js window.$docsify = { name: 'my-project',...
When I create documentations with docsify, I like to include the coverpage, sidebar and navbar features to take advantage of these amazing resources. So, I decided to automate this process...
# Goal The goal of this PR is to allow to serve several static paths to be able to seperate easily the HTML elements of docsify (css, index.html, so on)...
Would it be worth sticking this in the `packages` folder of the main repo, so it is easier to modify at the same time as other files in the main...