Building and checking the quality of documentation
Building and checking the quality of documentation#
This document covers how to build the Plone Documentation and check it for quality.
Installation of Plone 6 Documentation includes pre-requisites and the repository itself.
Vale is a linter for narrative text.
It checks spelling, English grammar, and style guides.
Plone documentation uses a custom spelling dictionary, with accepted and rejected spellings in
Use your operating system's package manager to install Vale.
Vale also has integrations with various IDEs.
Plone documentation uses a file located at the root of the repository,
.vale.ini, to configure Vale.
This file allows overriding rules or changing their severity.
The Plone Documentation Team selected the Microsoft Writing Style Guide for its ease of use—especially for non-native English readers and writers—and attention to non-technical audiences.
More corrections to spellings and Vale's configuration are welcome by submitting a pull request. This is an easy way to become a contributor to Plone.
Install Graphviz for graph visualization.
brew install graphviz
sudo apt-get install graphviz
Clone the Plone Documentation repository, and change your working directory into the cloned project.
Then with a single command using
Makefile, create a Python virtual environment, install project dependencies, pull in Volto documentation as a git submodule, build the docs, and view the results in a web browser by opening
git clone https://github.com/plone/documentation.git cd documentation make html
Available documentation builds#
All build and check documentation commands use the file
To see the most frequently used builds, use the following command.
Else you can open
Makefile to see other build formats, including PDF.
html is the HTML version of the documentation.
/_build/html/index.html in a web browser.
livehtml rebuilds Sphinx documentation on changes, with live-reload in the browser.
Open http://0.0.0.0:8000/ in a web browser.
vale checks for American English spelling, grammar, syntax, and the Microsoft Developer Style Guide.
See American English Spelling, Grammar, and Syntax, and Style Guide for configuration.
See the output on the console for suggestions.