@@ -48,6 +48,39 @@ Or you can just serve the documentation without building it using:
4848mkdocs serve
4949```
5050
51+ Your site will be updated ** live** when you change your files (provided that
52+ you used ` pip install -e . ` , beware of a common pitfall of using ` pip install `
53+ without ` -e ` , in that case the API reference won't change unless you do a new
54+ ` pip install ` ).
55+
56+ To build multi-version documentation, we use
57+ [ mike] ( https://github.com/jimporter/mike ) . If you want to see how the
58+ multi-version sites looks like locally, you can use:
59+
60+ ``` sh
61+ mike deploy my-version
62+ mike set-default my-version
63+ mike serve
64+ ```
65+
66+ ` mike ` works in mysterious ways. Some basic information:
67+
68+ * ` mike deploy ` will do a ` mike build ` and write the results to your ** local**
69+ ` gh-pages ` branch. ` my-version ` is an arbitrary name for the local version
70+ you want to preview.
71+ * ` mike set-default ` is needed so when you serve the documentation, it goes to
72+ your newly produced documentation by default.
73+ * ` mike serve ` will serve the contents of your ** local** ` gh-pages ` branch. Be
74+ aware that, unlike ` mkdocs serve ` , changes to the sources won't be shown
75+ live, as the ` mike deploy ` step is needed to refresh them.
76+
77+ Be careful not to use ` --push ` with ` mike deploy ` , otherwise it will push your
78+ local ` gh-pages ` branch to the ` origin ` remote.
79+
80+ That said, if you want to test the actual website in ** your fork** , you can
81+ always use ` mike deploy --push --remote your-fork-remote ` , and then access the
82+ GitHub pages produced for your fork.
83+
5184Releasing
5285=========
5386
0 commit comments