kopia lustrzana https://github.com/wagtail/wagtail
44933d06c4
Reorganise the 4.2 release notes and changelog to include new sections for documentation and maintenance. This helps to highlight the most relevant changes from the perspective of a developer wanting to know what they can expect from an upgrade, while still recognising less visible contributions. Also update the "committing code" docs to explain the new classification scheme. |
||
|---|---|---|
| .. | ||
| _static | ||
| _templates | ||
| advanced_topics | ||
| contributing | ||
| editor_manual | ||
| extending | ||
| getting_started | ||
| public | ||
| reference | ||
| releases | ||
| topics | ||
| Makefile | ||
| README.md | ||
| autobuild.sh | ||
| conf.py | ||
| favicon.ico | ||
| index.rst | ||
| logo.png | ||
| requirements.txt | ||
| spelling_wordlist.txt | ||
| support.md | ||
README.md
Wagtail docs
These are Sphinx docs, automatically built at https://docs.wagtail.org when the main branch is committed to Github. To build them locally, install Wagtail's development requirements (in the root Wagtail directory):
pip install -e .[testing,docs]
To build the documentation for browsing, from this directory run:
make html
then open _build/html/index.html in a browser.
To rebuild automatically while editing the documentation, from this directory run:
sphinx-autobuild . _build
The online MyST playground at Curvenote or the MyST-Markdown VS Code Extension are helpful tools for working with the MyST syntax.