4 min • read

Ambassador Documentation

The documentation in this repository is built with Gatsby, which gives us control and flexibility over the layout.

Contributing

We welcome all contributions! See LICENSE for applicable terms and conditions.

Authoring Documentation

If you're authoring the documentation, just edit the Markdown files. You can use GitHub to preview the Markdown.

Strings like $variable$ are substituted with the values defined in versions.yml.

The doc-links.yml file is the table of contents (TOC) that appears on the left sidebar.

The aes-pages.yml file identifies which pages should be marked as "Ambassador Edge Stack" pages.

Documentation Infrastructure Notes

The docs in this repository can be "vendored" into other repositories using git subtree. Repositories that do this are encouraged to include some kind of convenience tooling to make syncing the docs easier. For example, the following Makefile snippet:

The (private) getambassador.io.git repository contains the Gatsby-based toolchain that compiles the docs into website at https://www.getambassador.io/.

Other repositories that include the docs as a subtree should get in the habit of doing a git subtree pull from their master branch periodically. Documentation for code changes can then be committed right along-side the code changes. When a release is cut, and you are ready to publicize it, simply do a git subtree push.

Adding Release Notes

To add a Release Notes page for a product version, you should:

  1. Add a releaseNotes.yml file to the folder for that version of the product under ambassador-docs/docs. A template for this file can be found here:
  1. Add an entry to the doc-links.yml file to surface the release notes in the table of contents:
  1. If images need to be added, the images should be included in the ambassador-docs/public folder.