This guide is for administrators of Plone Documentation. It covers automated deployments, hosting, automated testing, previewing, and importing external package documentation into Plone Documentation.
Importing external docs and converting to MyST#
This section describes how to import external projects and convert their docs to MyST.
We did this for
plone.app.dexterity and several other projects.
Create a new branch using the name of the project.
bin/pip install "rst-to-myst[sphinx]"
Clone the project repository to the root of
Delete any non-documentation files from the clone.
Move the documentation files and subfolders to the root of the clone, retaining the documentation structure.
Convert the reStructuredText documentation files to MyST. The example commands below assume that there are files at the root of the clone and in one sub-level of nested directories. For deeper nesting, insert globbing syntax for each sub-level as
bin/rst2myst convert -R project/*.rst bin/rst2myst convert -R project/**/*.rst
Add HTML meta data to the converted files.
cd project ../bin/python ../docs/addMetaData.py
Optionally clean up any MyST syntax.
Commit and push your branch to GitHub and create a pull request.
Importing external docs with submodules#
To add an external package to Plone Documentation, we use git submodules. We did this with Volto documentation. Your package must be available under the Plone GitHub organization.
Inside the repository
plone/documentation, add a git submodule that points to your project.
git submodule add firstname.lastname@example.org:plone/my_package.git submodules/my_package
Add a target
Makefile, then add
docs/my_package to the
deps target, following
volto as a pattern.
You might need to adjust the paths to your package's documentation after it is cloned.
To complete setup, generate a symlink to your project's docs, and build the docs, use a single command.
To make it easier for other contributors to work with your project, update the following files, using
volto as a model.
Add it to the documentation section Editing external package documentation.
Add the symlink
Optionally set a branch to work on in
Commit and push your changes to a remote, and submit a pull request against
Add a project to Netlify#
To add a new site to Netlify to preview built documentation or storybooks, you need to add a new site to Netlify.
Visit Team Overview.
Click Add a new site and select Import an existing project.
Click Deploy with GitHub.
Select plone for the GitHub organization.
Click Configure Netlify on GitHub.
Select the organization to where you want to install Netlify.
Click Select repositories and select the repository that you want to add.
Click Update access.
Netlify sends an email to members of the email group
plone.org, who need to review and approve the request. However the email doesn't specify the repository, and admins will not know what to do. You must send email to that group, including in your request the organization and repository, such as
The admin must login to GitHub as an organization owner, then navigate to the requested repository's Settings. [What else Admin person?]
The admin replies to the requestor, letting them know the request was approved.
From here you need to update your repository to work with Netlify. For an example, see the following files.
Makefile, specifically the
netlifysection. This will become the command used to build docs on Netlify.
requirements-docs.txtspecifies the requirements to build the docs.
netlify.tomlspecifies when to build the docs, specifically only when there are changes to documentation files.
Finally you need to configure your site in Netlify. You may have done some of these steps earlier, but you might need to refine them. The critical pieces are the following.
From the dashboard, select the site to edit it.
Click Site configuration.
One time only, under General > Site details click Change site name. A modal dialog appears. Enter the site name using the pattern
ORGANIZATION_NAME-REPOSITORY_NAME. For example,
plone-components. Click Save.
Under Build & deploy > Continuous deployment, scroll to Build settings, and click Configure, then enter the following values.
make netlify. This is the command you would define in your
_build/html. This is where the
makecommand will output files.
Finally click Save.
Under Build & deploy > Continuous deployment, scroll to Branches and deploy contexts, and click Configure, then enter appropriate values.