k6 Documentation

Welcome to the k6 docs! This repo contains the source code of the k6 documentation.

Some key facts:

• Issues and contributions are always welcome!
• The docs are written in Markdown, built with Gatsby, and linted with Prettier and Vale.
• The Contributor's guide has meta-documentation about building locally, using special components and styling, deploying, troubleshooting, and more.
• We have a Code of conduct.

Contributing

Don't feel shy about contributing! All input is welcome. No fix is too trivial.

If something confuses you or feels lacking about the docs, make an issue. If you find something that you think you can fix, please go ahead. You don't need to ask permission.

Markdown files for the documentation are located in src/data/markdown/docs folder. The URL structure is generated based on the folder structure and file names.

For small changes and spelling fixes, the GitHub UI is most convenient. For larger contributions, consider running the project locally to see how the changes look like before making a pull request. You can build locally with Docker, as described in the following section, or you can use node, as described in the Contributor's Guide

The following docs cover the different stages of the writing workflow:

• Build locally. For any large changes, being able to view how the site looks live hugely improves writer comfort and doc quality. To build locally, you'll need node and a node version manager.

• Contributor's reference. The syntax and structure of the page paths, custom style components, program redirects, and so on.

• Troubleshooting. Unfortunately, things can go wrong. Fortunately, most errors usually share the same few fixes.

• Preview and deploy. Each PR has a preview. The main branch has two previews, staging (which deploys on merges) and prod (which deploys with version upgrades).

  Only people with qualified permissions can deploy.

Install and run in Docker

This uses docker-compose and port 8100.

git clone git@github.com:grafana/k6-docs.git
cd k6-docs
cp .env.example .env.development

docker-compose  up -d --build

Note that starting up the Docker takes several minutes, during which the website will not be accessible. Use docker-compose logs -f web to track progress.

Then visit http://localhost:8100

If you want to re-run the --build command, you may get an error about not having access to delete a cache/ folder. Use sudo to delete this manually before retrying.