The live docs are published from the
main branch. Therefore, you must create pull requests against the
main branch for all content updates. This includes:
- Conceptual and task-based information
- Restructuring / rewriting
- Doc bug fixing
- Fixing typos, broken links, and any grammar errors
There are two ways to contribute a pull request to the docs repository:
You can select the Edit this page option in the right column of every page on https://docs.docker.com/.
This opens the GitHub editor, which means you don't need to know a lot about Git, or even about Markdown. When you save, Git prompts you to create a fork if you don't already have one, and to create a branch in your fork and submit the pull request.
Fork the docs GitHub repositoryopen_in_new. Suggest changes or add new content on your local branch, and submit a pull request (PR) to the
This is the manual, more advanced version of selecting 'Edit this page' on a published docs page. Initiating a docs change in a PR from your own branch gives you more flexibility, as you can submit changes to multiple pages or files under a single pull request, and even create new topics.
For a demo of the components, tags, Markdown syntax, styles, etc. used in https://docs.docker.com/, see the components section.
Here’s a list of some of the important files:
/_data/toc.yamldefines the left-hand navigation for the docs.
/js/docs.jsdefines most of the docs-specific JS such as the table of contents (ToC) generation and menu syncing.
/css/style.scssdefines the docs-specific style rules.
/_layouts/docs.htmlis the HTML template file, which defines the header and footer, and includes all the JS/CSS that serves the docs content.
Some files and directories are maintained in the upstream repositories. You can find a list of such files in
_config_production.yml. Pull requests against these files will be rejected.
Help us review your PRs more quickly by following these guidelines.
- Try not to touch a large number of files in a single PR if possible.
- Don't change whitespace or line wrapping in parts of a file you aren't editing for other reasons. Make sure your text editor isn't configured to automatically reformat the whole file when saving.
- We highly recommend that you build and test the docs locally before submitting a PR.
- A Netlify test runs for each PR that is against the
mainbranch, and deploys the result of your PR to a staging site. The URL will be available in the Conversation tab. Check the staging site to verify how your changes look and fix issues, if necessary.
Unless the PR author specifically disables it, you can push commits into another contributor's PR. You can do it from the command line by adding and fetching their remote, checking out their branch, and adding commits to it. Even easier, you can add commits from the GitHub web UI, by clicking the pencil icon for a given file in the Files view.
If a PR consists of multiple small addendum commits on top of a more significant
one, the commit will usually be "squash-merged", so that only one commit is
merged into the
main branch. In some scenarios where a squash and merge isn't appropriate, all commits are kept separate when merging.
A Netlify test runs for each PR created against the
main branch and deploys the result of your PR to a staging site. When the site builds successfully, you will see a comment in the Conversation tab in the PR stating Deploy Preview for docsdocker ready!. Click the Browse the preview URL and check the staging site to verify how your changes look and fix issues, if necessary. Reviewers also check the staged site before merging the PR to protect the integrity of the docs site.
On your local machine, clone the docs repository:
$ git clone https://github.com/docker/docs.git $ cd docs
Then, build and run the documentation using Docker Compose:
$ docker compose up -d --build $ docker compose alpha watch
You need Docker Compose to build and run the docs locally. Docker Compose is included with Docker Desktop. If you don't have Docker Desktop installed, follow the instructions to install Docker Compose.
When the container is built and running, visit http://localhost:1313open_in_new in your web browser to view the docs.
watch feature causes your
running container to rebuild itself automatically when you make changes to your
To stop the development container:
- In your terminal, press
<Ctrl+C>to exit the file watch mode of Compose.
- Stop the Compose services with the
docker compose downcommand.
The default configuration for local builds of the documentation disables some features to allow for a shorter build-time. The following options differ between local builds, and builds that are deployed to docs.docker.com:
- search auto-completion, and generation of
- Google Analytics
- page feedback
- minification of stylesheets (
- adjusting "edit this page" links for content in other repositories
If you want to contribute in these areas, you can perform a "production" build
locally. To preview the documentation with deployment features enabled, set the
JEKYLL_ENV environment variable when building the documentation:
JEKYLL_ENV=production docker compose up --build
When the container is built and running, visit http://localhost:4000open_in_new in your web browser to view the docs.
To rebuild the docs after you make changes, repeat the steps above.
We use a command-line tool called valeopen_in_new to check the style and help you find errors in your writing. We highly recommend that you use vale to lint your documentation before you submit your pull request.
You can run vale as a stand-alone tool using the command-line, or you can integrate it with your editor to get real-time feedback on your writing.
To get started, follow the vale installation instructionsopen_in_new for your operating system. To enable the vale integration for your editor, install the relevant plugin:
The vale rules that implement the Docker style guide are included in the Docker docs repository,
.github/vale directory. Vale will automatically apply these rules when invoked in this