This repository contains the source content and code for Kong's documentation website. It's built using Jekyll and deployed with Netlify.
Here are some things to know before you get started:
-
We're beginner-friendly. Whether you're a Technical Writer learning about docs-as-code or an engineer practicing your documentation skills, we welcome your involvement. If you'd like to contribute and don't have something in mind already, head on over to Issues. We've added
good first issuelabels on beginner-friendly issues. -
We need more help in some areas. We'd especially love some help with plugin documentation.
-
Some of our docs are generated.
All pull requests for these docs should be opened in the Kong/kong repository. Fork the repository and submit PRs from your fork.
For Gateway Enterprise configuration reference, open an issue on this repo and we'll update the docs.
-
Community is a priority for us. Before submitting an issue or pull request, make sure to review our Contributing Guide.
-
We are currently accepting plugin submissions to our plugin hub from trusted technical partners, on a limited basis. For more information, see the Kong Partners page.
For anything other than minor changes, clone the repository onto your local machine and build locally. Once you've installed all of the tools required, you can use our Makefile to build the docs:
# Install dependencies
make install
# Make sure to update submodules
git submodule update --init --recursive
# Build the site and watch for changes
make runIf you have contributed a plugin, you can add a Kong badge to your plugin README.
Use the following, where you replace test with your plugin name and link-to-docs with a link to the Kong docs for your plugin.
[](link-to-docs)
Here's how the badge looks:
See Issue #908 for more information. Note that we're not currently hosting assets for badges.
This section is for Kong source code maintainers. You don't need to do anything here if you're contributing to this repo!
The PDK docs, Admin API docs, cli.md and configuration.md for each release are generated from the Kong source code.
To generate them, go to the Kong/kong repo and run:
scripts/autodoc <docs-folder> <kong-version>For example:
cd /path/to/kong
scripts/autodoc ../docs.konghq.com 2.4.xThis example assumes that the Kong/docs.konghq.com repo is cloned into the
same directory as the Kong/kong repo, and that you want to generate the docs
for version 2.4.x. Adjust the paths and version as needed.
After everything is generated, review, open a branch with the changes, send a pull request, and review the changes.
You usually want to open a PR against a release/* branch. For example, in the
example above, the branch was release/2.4.
cd docs.konghq.com
git fetch --all
git checkout release/2.4
git checkout -b release/2.4-autodocos
git add -A .
git commit -m "docs(2.4.x) add autodocs"
git pushThen open a pull request against release/2.4.
Tests for this site are written using fetch, cheerio and jest
To run the tests, you must first build the site by running make build before running make smoke.
Many of the tests are smoke tests to check for issues that occurred while adding caching to the site, such as ensuring that the side navigation isn't cached.
To add your own tests, look in the tests directory and use home.test.js as a sample. You specify which URL to visit and then a CSS selector to search for, before asserting that the contents match what you expect.
test("has the 'Welcome to Kong' header", async () => {
const $ = await fetchPage("/")
expect($("#main")).toHaveText("Welcome to Kong Docs");
});We run various quality checks at build time to ensure that the documentation is maintainable.
Some of the checks can be manually marked as approved using labels:
ci:manual-approve:link-validation- mark link checking as successful. Useful when Netlify returns anHTTP 400error and the links are validated manually.
The include-check.sh script checks for any files in the app/_includes folder that depend on a page.* variable (e.g. page.url). This is not compatible with the include_cached gem that we use, and so using page.* in an include will fail the build.
To run the script locally, open a terminal, navigate to the documentation folder, and run
./include-check.sh. If there is no output, everything is successful.
In the following example, we can see that deployment-options-k8s.md uses a page.* variable, and that the include is used in the kong-for-kubernetes.md file:
❯ ./include-check.sh
Page variables must not be used in includes.
Pass them in via include_cached instead
Files that currently use page.*:
File: app/_includes/md/2.5.x/deployment-options-k8s.md
via:
app/enterprise/2.5.x/deployment/installation/kong-for-kubernetes.mdHere are sample contents for those files:
In kong-for-kubernetes.md:
{% include_cached app/_includes/md/2.5.x/deployment-options-k8s.md %}In deployment-options-k8s:
This is an include that uses {{ page.url }}To resolve this, the two files should be updated to pass in the URL when include_cached is called:
In kong-for-kubernetes.md:
{% include_cached app/_includes/md/2.5.x/deployment-options-k8s.md url=page.url %}In deployment-options-k8s:
This is an include that uses {{ include.url }}The include_cached gem uses all passed parameters as the cache lookup key, and this ensures that all required permutations of an include file will be generated.
For guidelines on how to write includes and call them in target topics, see the Kong Docs contributing guidelines.
When raising a pull request, it's useful to indicate what type of review you're looking for from the team. To help with this, we've added three labels that can be applied:
review:copyedit: Request for writer review.review:general: Review for general accuracy and presentation. Does the doc work? Does it output correctly?review:tech: Request for technical review from an SME.
At least one of these labels must be applied to a PR or the build will fail.