Contributing to the Docs
Last updated
Was this helpful?
Latest Release
Last updated
Was this helpful?
Our docs are centralized inside the docs/ folder of our GitHub repository for garden. These files are synced to GitBook, our documentation publishing tool, which composes them into what users see when they navigate to .
We have an additional class of documentation, which lives as README.md files inside each of our examples inside examples/. These files are not synced to GitBook and are intended to be discovered by our more technical users.
Our ../../gitbook.yaml file determines link redirects and the basic structure of our documentation “tree”. You can find more documentation on this file .
*The README.md file at the top of the docs/ folder and the reference/* files are all auto-generated and should never be touched directly. Refer to for details.
There's a few things you'll need to make your first contribution to the docs:
A local copy of the garden Git repository downloaded to your machine. You can find instructions in GitHub's official documentation for .
Garden's developer tools installed. Our documentation explains how to install Garden's developer tools
Some basic knowledge of Git. If one or more users are contributing to the docs at the same time you are, it is likely you will need to resolve merge conflicts on the CLI or in your visual Git tool. GitHub has or you can use a simple, visual Git tool like available for macOS and Windows. a. In case of emergencies, refer to . b. For new learners, the can teach you Git.
Some form of Markdown linter. A linter enforces standards and consistency in your Markdown writing. The industry standard is . A .
Create a branch to hold your work, change any files you wish to change, save them, then commit them to your branch. Try and keep your branches focused around a specific theme. Your commits will need to be prepended with a keyword that follows the Conventional Commits specification, e.g. docs: added docs contributor page. See our documentation for a list of Conventional Commit keywords.
Before pushing your changes, run npm run build to refresh the Table of Contents contained at ../docs/README.md with any additions or changes you've made.
If you've moved or renamed files, refer to .
Now push your changes to our remote Git repository hosted on GitHub, then and request a review from and/or . View our contributing guidelines for more.
When moving or renaming files, special care must be taken to ensure any existing internal and external links continue to work.
First, use git mv when moving files. git mv is a convenience function that ensures Git can track the renaming as a file rename rather than a file deletion and a new file creation.
We also need to change any existing redirects inside ../gitbook.yaml to point to our new location:
For every file you've renamed or moved, make sure to add a new redirect in ../gitbook.yaml pointing from its old location to its new location unless you're sure no one externally has linked to it.
Do not change absolute URLs within the same pull request. Absolute URLs are links beginning with https:.
Instead, change all the relative URLs inside docs/, submit your PR, then make a new PR to update these absolute URLs. This is to avoid broken links.
Finally, run npm run build to regenerate the Table of Contents.
Use absolute URLs when you need to point to any docs from outside the docs/ folder. This is often the case when you're working in TypeScript (.ts) files. Here's an example from our ../../core/src/graph/actions.ts file that includes a URL intended for users of garden:
This URL would need to be changed or a redirect link set if the configuration-overview file were to move.
To create a new section, create a folder and add a README.md file with the contents title and order e.g.
Our docs are written in the CommonMark specification of Markdown with additional “blocks” provided by GitBook, our documentation publisher.
You'll notice YAML “front-matter” at the top of each docs page: this tells GitBook how to present our page visually and order it in any given section.
The YAML front-matter looks like this:
Markdown normally expects the first heading of any page to be a top-level, usually the title of the page, e.g. # Contributing to the Docs. However, when we specify the title of the page in the front-matter, start the page without the top-level and begin at the second-level heading, ##, as GitBook will automatically pull in the title for you.
Second, update any internal and external links to point to your moved or renamed file, then update ../gitbook.yaml to redirect visitors to your new location. To illustrate this, here's a visual example of moving our to a new Getting Started section.
The second line, quick-start: getting-started/quickstart.md means any users visiting will automatically redirect to .
You'll also need to find and replace all instances of links within the garden repository to your file. An editor like Visual Studio Code will have a .
The order should correspond to its position from top to bottom in the sidebar on and the title should be the title of the section as it appears in the sidebar. We like to use a floral-themed emoji to demarcate new sections .
We use the and blocks from GitBook.
GitBook supports a of headings.
