Contributing to and reusing The Runbook

The Runbook is open content, and there are clear paths for fixing it, adding to it, and reusing it.

Reporting a mistake

If a guide is wrong, outdated, or unclear, the fastest fix is to flag it directly. Each page has a “was this helpful?” control and an “edit this page” link that takes you to the source on GitHub, and you can open an issue on the repository. You’re also welcome to contact support here and we’ll route it.

Contributing a change

Contributions are welcome by pull request. In short: fork the repository, set it up locally, create a branch, make your change, build it to confirm it’s clean, and open a PR against main. Contributions are reviewed for technical accuracy, writing style, and a clean build. The repository’s contributing guide has the exact steps.

Licensing (important if you want to reuse it)

The Runbook is dual-licensed, and which license applies depends on the file:

• Written content (the guides themselves) is licensed CC BY-NC-ND 4.0. In plain terms: you may share it with attribution, but not commercially and not in modified form. Reposting a guide verbatim, with credit and a link, non-commercially, is fine; selling it or publishing an edited or excerpted version is not, without separate permission.
• Code (the site’s scripts, styles, and templates) is licensed MIT - permissive, reuse freely as long as you keep the notice.

If a file’s license is ever ambiguous, the rule is: .md files are content (CC BY-NC-ND 4.0), everything else is code (MIT).

Want to reuse a guide in a way the license doesn’t obviously cover? Send us a message and a human will reply.