Skip to content

quickstart.md

Latest commit

History

History
142 lines (104 loc) · 4.2 KB

quickstart.md

File metadata and controls

142 lines (104 loc) · 4.2 KB
Raw

Quick start

It is recommended to install docsify-cli globally, which helps initializing and previewing the website locally.

npm i docsify-cli -g

Initialize

If you want to write the documentation in the ./docs subdirectory, you can use the init command.

docsify init ./docs

Writing content

After the init is complete, you can see the file list in the ./docs subdirectory.

  • index.html as the entry file
  • README.md as the home page
  • .nojekyll prevents GitHub Pages from ignoring files that begin with an underscore

You can easily update the documentation in ./docs/README.md, and of course you can add more pages.

Preview your site

Run the local server with docsify serve. You can preview your site in your browser on http://localhost:3000.

docsify serve docs

[!TIP] For more use cases of docsify-cli, head over to the docsify-cli documentation.

Manual initialization

Download or create an index.html template using the following markup:

Download Template

<!doctype html><html><head><metacharset="utf-8"><metaname="viewport" content="width=device-width, initial-scale=1, viewport-fit=cover"><!-- Core Theme --><linkrel="stylesheet" href="//cdn.jsdelivr.net/npm/docsify@5/dist/themes/core.min.css"></head><bodyclass="loading"><divid="app"></div><!-- Configuration --><script>window.$docsify={//...};</script><!-- Docsify.js --><scriptsrc="//cdn.jsdelivr.net/npm/docsify@5"></script><!-- Plugins (optional) --><!-- <script src="//cdn.jsdelivr.net/npm/docsify@5/dist/plugins/search.min.js"></script> --></body></html>

Specifying docsify versions

[!TIP] Note that in both of the examples below, docsify URLs will need to be manually updated when a new major version of docsify is released (e.g. v5.x.x => v6.x.x). Check the docsify website periodically to see if a new major version has been released.

Specifying a major version in the URL (@5) will allow your site to receive non-breaking enhancements (i.e. "minor" updates) and bug fixes (i.e. "patch" updates) automatically. This is the recommended way to load docsify resources.

<!-- Core Theme --><linkrel="stylesheet" href="//cdn.jsdelivr.net/npm/docsify@5/dist/themes/core.min.css"><!-- Docsify --><scriptsrc="//cdn.jsdelivr.net/npm/docsify@5"></script>

If you'd like to ensure absolutely no possibility of changes that will break your site (non-major updates can unintentionally introduce breaking changes despite that they aim not to), specify the full version after the @ symbol in the URL. This is the safest way to ensure your site will look and behave the same way regardless of any changes made to future versions of docsify.

<!-- Core Theme --><linkrel="stylesheet" href="//cdn.jsdelivr.net/npm/docsify@5.0.0/themes/core.min.css"><!-- Docsify --><scriptsrc="//cdn.jsdelivr.net/npm/docsify@5.0.0"></script>

JSDelivr supports npm-compatible semver ranges, so you can also use version syntax such as @^5.0.0 for the latest v5 release, @5.0.x for the latest v5.0 patch release (f.e. you will receive 5.0.4 but not 5.1.0), @5.x for the latest v5 minor and patch releases (which is effectively the same as @5 and @^5.0.0), etc.

Manually preview your site

If you have Python installed on your system, you can easily use it to run a static server to preview your site instead of using docsify serve from docsify-cli.

# Python 2cddocs&&python-mSimpleHTTPServer3000
# Python 3cddocs&&python-mhttp.server3000
<script> (function() { const linkElm = document.querySelector('#template a[download="index.html"]'); const codeElm = document.querySelector('#template code'); const html = codeElm?.textContent; linkElm?.setAttribute('href', `data:text/plain,${html}`); })(); </script>