kitchen-docs

Test Kitchen Documentation

2 years after

Documentation for KitchenCI.

Overview

All documentation is written in Markdown. To preview the documentation in your browser run the following:

bundle install
bundle exec middleman

Then go view the docs at http://localhost:4567 (which redirects to http://localhost:4567/getting-started/). Edits to the documentation source files should cause the middleman server to reload so you can see your changes update live.

NOTE: the middleman stuff was yanked from the (upcoming) http://kitchen.ci website middleman project. An attempt was made to strip any/all styling and theme sources, as well as removal of any references to commercial support offerings. If any of that was left over and it offends you, please feel free to remove it and submit a pull request.

Hosting

All documentation will be hosted on the official Kitchen website (http://kitchen.ci), which is a static site built with Middleman.

The important parts to familiarize yourself with for contributing to the KitchenCI documentation are the markdown renderer and syntax highlighting engines used to power http://kitchen.ci.

Markdown rendering is handled by kramdown. It would be worth your while to briefly review the kramdown documentation as there are some subtle differences (as well as a number of helpful extensions) that deviate from the Markdown standard.

Syntax Highlighting is handled by middleman-syntax, which uses Rouge, which is a ruby-based syntax highlighting engine that is compatible with Pygments templates and supports things like "fenced code blocks" and language-specific syntax highlighting from Markdown.

Metadata

Each page also contains some YAML "frontmatter" that is used to compile the navigation menus (etc) on http://kitchen.ci. The only required metadata property is title.

---
title: "KitchenCI Overview"
---

In addition to these required properties, there are also some optional metadata properties which can be employed:

User Guide / Next Steps

Some portions of the documentation should be read like a guide, prompting you on to the next step in the process. So, when present the "next" property will cause a prompt to appear at the bottom of the documentation page on http://kitchen.ci to guide the reader to the next relevant topic. If this property is missing (or if the corresponding "url" + "text" properties are omitted), no such prompt will appear.

---
title: "KitchenCI Overview"
next:
  url: installing-kitchen
  text: "Installing KitchenCI"
---

Banners

Sometimes it is helpful to alert the reader to changes, warn them of common pitfalls, or make it known that there be dragons. Adding a alert, warning, or danger property to the frontmatter will cause a corresponding blue, yellow, or red banner to be displayed at the top of the content section of the documentation page on http://kitchen.ci.

---
title: "KitchenCI Documentation"
alert: "Added in kitchen version 1.0.x"
---

Style Guide

There are four elements that may be used for "styling" the docs content: in-line code highlighting, code blocks, blockquotes, and a special hack around markdown tables that we'll use for what we call "Pro-Tips".

In-line Code Highlighting

To highlight some code inline with other content, just "qoute" the text using backtick characters (`). See the kramdown documentation for more details.

Fenced Code Blocks

To highlight a block of code, start and finish the block with three or more tilde characters (~). To enable syntax-highlighting, just indicate the code language after the tildes on the first line.

For example, this code:

~~~yaml
---
title: "KitchenCI Overview"
next:
  url: installing-kitchen
  text: "Installing KitchenCI"
---
~~~

...will yield this output:

---
title: "KitchenCI Overview"
next:
  url: installing-kitchen
  text: "Installing KitchenCI"
---

See the kramdown documentation for more information.

Blockquotes

To draw attention to some content with a blockquote, just start the line(s) with a > (right angle bracket / greater than symbol). See the kramdown documentation for more information.

Pro-Tips (Tables)

To draw attention to some content that may be a side-bar or advanced content, just start the line(s) with double pipe characters (||). For example:

|| Pro-Tip
|| This is an advanced topic...

License

The Kitchen Documentation is released under the MIT license.

Related Repositories

test-kitchen

test-kitchen

Test Kitchen is an integration tool for developing and testing infrastructure co ...

kitchen-docker

kitchen-docker

A Test Kitchen Driver for Docker ...

kitchen-vagrant

kitchen-vagrant

Vagrant driver for Kitchen ...

kitchen-ec2

kitchen-ec2

A Test Kitchen Driver for Amazon EC2 ...

kitchen-terraform

kitchen-terraform

Test Kitchen plugins for testing Terraform configurations ...


Top Contributors

fnichol calebhailey LordCope cheeseplus jjasghar webframp svanzoest robbkidd drrk mattray portertech cheesesashimi MarkGibbons tgeerdes greenmanspirit aspyatkin choongsavvii djoos hwork jsallis grafjo arangamani mlafeldt mwrock mkubenka czerasz filler coderanger pikesley StephenKing