Contributing to Docker Documentation

# Contributing to Docker Documentation We value documentation contributions from the Docker community. We'd like to make it as easy as possible for you to work in this repository. Our style guide and instructions on using our page templates and components is available in the [contribution section](https://docs.docker.com/contribute/) on the website. The following guidelines describe the ways in which you can contribute to the Docker documentation at <https://docs.docker.com/>, and how to get started. ## Reporting issues If you encounter a problem with the content, or the site in general, feel free to [submit an issue](https://github.com/docker/docs/issues/new/choose) in our [GitHub issue tracker](https://github.com/docker/docs/issues). You can also use the issue tracker to raise requests on improvements, or suggest new content that you think is missing or that you would like to see. ## Editing content The website is built using [Hugo](https://gohugo.io/). The content is primarily Markdown files in the `/content` directory of this repository (with a few exceptions, see [Content not edited here](#content-not-edited-here)). The structure of the sidebar navigation on the site is defined by the site's section hierarchy in the `contents` directory. The titles of the pages are defined in the front matter of the Markdown files. You can use `title` and `linkTitle` to define the title of the page. `title` is used for the page title, and `linkTitle` is used for the sidebar title. If `linkTitle` is not defined, the `title` is used for both. You must fork this repository to create a pull request to propose changes. For more details, see [Local setup](#local-setup). ### General guidelines Help make reviewing easier 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 use GitHub Actions for testing and creating preview deployments for each pull request. The URL of the preview deployment is added as a comment on the pull request. Check the staging site to verify how your changes look and fix issues, if necessary. ### Local setup You can use Docker (surprise) to build and serve the files locally.

This section provides guidelines for contributing to Docker documentation, including reporting issues, editing content, and setting up a local environment. It emphasizes the use of GitHub issues for problem reporting and improvement suggestions. It also outlines how the website is built with Hugo, and how content is structured using Markdown files in the /content directory. The guidelines encourage contributors to follow best practices for pull requests, such as minimizing the number of touched files and avoiding unnecessary whitespace changes.