website: terminology

website/source/docs/basics/terminology.html.markdown

+---
+layout: "docs"
+---
+
+# Packer Terminology
+
+There are a handful of terms used throughout Packer documentation where
+the meaning may not be immediately obvious if you haven't used Packer before.
+Luckily, there are relatively few. This page documents all the terminology
+required to understand and use Packer. The terminology is in alphabetical
+order for easy referencing.
+
+<a class="term" id="#term-build"></a>
+**Artifacts** are the results of a single [build](#term-build), and are
+usually a set of IDs or files to represent a machine image. Every [builder](#term-builder)
+produces a single artifact. As an example, in the case of the Amazon EC2 builder,
+the artifact is a set of AMI IDs (one per region). For the VMware builder,
+the artifact is a directory of files comprising the created virtual machine.
+
+<a class="term" id="#term-build"></a>
+**Builds** are a single task that eventually produces an image for a single
+platform. Multiple builds run in parallel. Example usage in a sentence: "The Packer build
+produced an AMI to run our web application." Or: "Packer is running the builds
+now for VMware, AWS, and VirtualBox."
+
+<a class="term" id="#term-builder"></a>
+**Builders** are components of Packer that are able to create a machine
+image for a single platform. Builders read in some configuration and use
+that to run and generate a machine image. A builder is invoked as part of a [build](#term-build)
+in order to create the actual resulting images. Example builders include
+VirtualBox, VMware, and Amazon EC2. Builders can be created and added to
+Packer in the form of plugins.
+
+<a class="term" id="#term-command"></a>
+**Commands** are sub-commands for the `packer` program that perform some
+job. An example somecommand is "build", which is invoked as `packer build`.
+Packer ships with a set of commands out of the box in order to define
+its [command-line interface](#). Commands can also be created and added to
+Packer in the form of plugins.
+
+<a class="term" id="#term-provisioner"></a>
+**Provisioners** are components of Packer that install and configure
+software within a running machine prior to that machine being turned
+into a static image. They perform the major work of making the image contain
+useful software. Example provisioners include shell scripts, Chef, Puppet,
+etc.
+
+<a class="term" id="#term-template"></a>
+**Templates** are JSON files which define one or more [builds](#term-build)
+by configuring the various components of Packer. Packer is able to read a
+template and use that information to create multiple machine images in
+parallel.

website/source/docs/installation.html.markdown

+---
+layout: "docs"
+---
+
+# Installing Packer
+
+Coming soon.

website/source/layouts/docs.erb

@@ -8,7 +8,7 @@
 		<meta name="author" content="">
 
 		<!-- Le styles -->
-		<%= stylesheet_link_tag "bootstrap.min" %>
+		<%= stylesheet_link_tag "bootstrap.min", "packer" %>
 		<style type="text/css">
 			body {
 				padding-top: 20px;
@@ -25,10 +25,10 @@
 					<div class="well sidebar-nav" style="padding: 8px 0;">
 						<ul class="nav nav-list">
 							<li><a href="/docs/what-is-packer.html">What is Packer?</a></li>
-							<li><a href="#">Installation</a></li>
+							<li><a href="/docs/installation.html">Installation</a></li>
 
 							<li class="nav-header">Basics</li>
-							<li><a href="#">Terminology</a></li>
+							<li><a href="/docs/basics/terminology.html">Terminology</a></li>
 							<li><a href="#">Command-Line</a></li>
 							<li><a href="#">Templates</a></li>