The source files for the Buildkite Documentation.

To contribute, please send a pull request! ❤️

There are two ways to develop and contribute to the Buildkite Documentation—non-containerized and containerized.

You will need both Ruby and Yarn.

See .ruby-version for the current required version. Use/install rbenv to install the correct version of Ruby.

Ensure you have installed Yarn too. If you use macOS, you can do this conveniently with Homebrew.

You will need Docker and Docker Compose. Most desktop installations of Docker include Docker Compose by default. On some platforms (for example, Linux-based ones), you may need to prefix docker commands with sudo or add your user to the docker group.

Clone the Buildkite Docs source locally. To do so, run these commands:

git clone [email protected]:buildkite/docs.git

cd docs

git submodule update --init

After completing the relevant 'Before you start' steps above:

1. Build and run your local Buildkite Docs development server environment.

   For non-containerized development, run the following:

   # Check that you have Xcode Command Line Tools installed - required to build dependencies
   xcode-select -p
   
   # If not, install them
   xcode-select --install
   
   # Install dependencies
   bin/setup
   
   # Start the app
   foreman start

   Note: After stopping the non-containerized server, simply run foreman start to re-start the server again. If, however, the foreman start command fails to run successfully, try re-running the bin/setup command again to update any dependencies before running foreman start again.

   For containerized development, run the following:

   # Start the app on http://localhost:3000/
   docker-compose up --build

2. Open http://localhost:3000 to preview the docs site.

3. After saving your modifications to a page, refresh the relevant page on this site to see your changes.

With the development dependencies installed you can update the CLI docs with the following:

# Set a custom PATH to select a locally built buildkite-agent
PATH="$HOME/Projects/buildkite/agent:$PATH" ./scripts/update-agent-help.sh

GraphQL API documentation is generated from a local version of the Buildkite GraphQL API schema.

This repository is kept up-to-date with production based on a daily scheduled build. The build fetches the latest GraphQL schema, generates the documentation, and publishes a pull request for review.

If you need to fetch the latest schema you can either:

• Manually trigger a build on buildkite/docs-graphql; or
• Run the following in your local environment:

# Fetch latest schema
API_ACCESS_TOKEN=xxx rake graphql:fetch_schema >| data/graphql/schema.graphql

# Generate docs based on latest schema
rake graphql:generate

We spell-check the docs (US English) and run a few automated checks for repeated words, common errors, and markdown and filename inconsistencies.

You can run most of these checks with ./scripts/vale.sh.

If you've added a new valid word that showing up as a spelling error, add it to ./vale/styles/vocab.txt.

Our documentation is based on the principles of common sense, clarity, and brevity.

The writing and Markdown syntax style guides should provide you a general idea and an insight into our language and writing style, as well as the Markdown syntax we use (including custom formatting elements).

Note: By default, search (through Algolia) references the production search index.

The search index is updated once a day by a scheduled build using the config in config/algolia.json.

To test changes to the indexing configuration:

1. Make sure you have an API key in .env like:

   APPLICATION_ID=APP_ID
   API_KEY=YOUR_API_KEY

2. Run bundle exec rake update_test_index.

The navigation is split into the following files:

• nav_graphql.yml: For the GraphQL API content.
• nav.yml: For everything else.

A combined navigation is generated when the application starts.

Otherwise, to update the general navigation:

1. Edit nav.yml with your changes.
2. Restart the application.

We render content keywords in data-content-keywords in the body tag to highlight the focus keywords of each page with content authors.

This helps the content team to quickly inspect to see the types of content we're providing across different channels.

Keywords are added as Frontmatter meta data using the keywords key, e.g.:

keywords: docs, tutorial, pipelines, 2fa

If no keywords are provided it falls back to comma-separated URL path segments.

See LICENSE.md (MIT)