From 24cb97b393205e4cc85e04af60e2319e27bfcc7a Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Philipp=20Ku=CC=88bler?= <philipp@sourceboat.com>
Date: Thu, 12 Oct 2017 22:11:15 +0200
Subject: [PATCH] change metalsmith docs to small fiction

---
 .../build/api/api.html                        | 107 +-------
 .../build/api/metadata.html                   | 118 ---------
 .../build/documentation/matching.html         | 126 ---------
 .../build/documentation/works.html            | 250 ------------------
 .../technical-documentation/build/index.html  | 106 +-------
 .../build/install/index.html                  | 101 -------
 .../build/plugins/add.html                    |  99 -------
 .../build/plugins/write.html                  | 129 ---------
 .../build/started/install.html                |  48 +---
 .../build/started/intro.html                  | 127 ---------
 .../build/started/metadata.html               | 123 ---------
 .../build/started/plugins.html                |  75 +-----
 .../build/started/trouble.html                |  62 +----
 .../technical-documentation/src/api/api.md    |  65 +----
 .../src/api/metadata.md                       |  35 ---
 .../src/documentation/matching.md             |  49 ----
 .../src/documentation/works.md                | 195 --------------
 examples/technical-documentation/src/index.md |  76 +-----
 .../src/install/index.md                      |  16 --
 .../src/plugins/add.md                        |  13 -
 .../src/plugins/write.md                      |  45 ----
 .../src/started/install.md                    |   9 +-
 .../src/started/intro.md                      |  36 ---
 .../src/started/metadata.md                   |  42 ---
 .../src/started/plugins.md                    |  40 +--
 .../src/started/trouble.md                    |  16 +-
 26 files changed, 48 insertions(+), 2060 deletions(-)
 delete mode 100644 examples/technical-documentation/build/api/metadata.html
 delete mode 100644 examples/technical-documentation/build/documentation/matching.html
 delete mode 100644 examples/technical-documentation/build/documentation/works.html
 delete mode 100644 examples/technical-documentation/build/install/index.html
 delete mode 100644 examples/technical-documentation/build/plugins/add.html
 delete mode 100644 examples/technical-documentation/build/plugins/write.html
 delete mode 100644 examples/technical-documentation/build/started/intro.html
 delete mode 100644 examples/technical-documentation/build/started/metadata.html
 delete mode 100644 examples/technical-documentation/src/api/metadata.md
 delete mode 100644 examples/technical-documentation/src/documentation/matching.md
 delete mode 100644 examples/technical-documentation/src/documentation/works.md
 delete mode 100644 examples/technical-documentation/src/install/index.md
 delete mode 100644 examples/technical-documentation/src/plugins/add.md
 delete mode 100644 examples/technical-documentation/src/plugins/write.md
 delete mode 100644 examples/technical-documentation/src/started/intro.md
 delete mode 100644 examples/technical-documentation/src/started/metadata.md
diff --git a/examples/technical-documentation/build/api/api.html b/examples/technical-documentation/build/api/api.html
index 3b7bff19..2e5efb34 100644
--- a/examples/technical-documentation/build/api/api.html
+++ b/examples/technical-documentation/build/api/api.html
@@ -2,7 +2,7 @@
 <html>
 <head>
 	<meta charset="utf-8">
-	<title>Metalsmith</title>
+	<title>API</title>
 	<link href="http://fonts.googleapis.com/css?family=Roboto:400,300|Arvo:400" rel="stylesheet" type="text/css">
 	<link rel="stylesheet" href="https://cdnjs.cloudflare.com/ajax/libs/highlight.js/9.12.0/styles/default.min.css">
 	<link rel="stylesheet" type="text/css" href="../media/style.css">
@@ -24,40 +24,7 @@ <h2>Navigation</h2>
 					API
 					<ul>
 											<li>
-							<a href="../api/api.html">Metalsmith</a>
-						</li>
-											<li>
-							<a href="../api/metadata.html">Metadata</a>
-						</li>
-										</ul>
-				</li>
-							<li>
-					Documentation
-					<ul>
-											<li>
-							<a href="../documentation/matching.html">Matching</a>
-						</li>
-											<li>
-							<a href="../documentation/works.html">How does it work</a>
-						</li>
-										</ul>
-				</li>
-							<li>
-					Installation
-					<ul>
-											<li>
-							<a href="../install/index.html">Installation</a>
-						</li>
-										</ul>
-				</li>
-							<li>
-					Plugins
-					<ul>
-											<li>
-							<a href="../plugins/add.html">The Community Plugins</a>
-						</li>
-											<li>
-							<a href="../plugins/write.html">Writing A Plugin</a>
+							<a href="../api/api.html">API</a>
 						</li>
 										</ul>
 				</li>
@@ -66,12 +33,6 @@ <h2>Navigation</h2>
 					<ul>
 											<li>
 							<a href="../started/install.html">Installation</a>
-						</li>
-											<li>
-							<a href="../started/intro.html">Introduction</a>
-						</li>
-											<li>
-							<a href="../started/metadata.html">Metadata & debugging</a>
 						</li>
 											<li>
 							<a href="../started/plugins.html">Plugins</a>
@@ -85,70 +46,22 @@ <h2>Navigation</h2>
 		</aside>
 		<article>
 								<ol class="toc">
-			<li><a href="#new-metalsmith-dir-">new Metalsmith(dir)</a>
+			<li><a href="#new-client-">new Client()</a>
 				</li>
     		<li><a href="#-use-plugin-">.use(plugin)</a>
 				</li>
-    		<li><a href="#-build-fn-">.build(fn)</a>
-				</li>
-    		<li><a href="#-source-path-">.source(path)</a>
-				</li>
-    		<li><a href="#-destination-path-">.destination(path)</a>
-				</li>
-    		<li><a href="#-concurrency-max-">.concurrency(max)</a>
-				</li>
-    		<li><a href="#-clean-boolean-">.clean(boolean)</a>
-				</li>
-    		<li><a href="#-frontmatter-boolean-">.frontmatter(boolean)</a>
-				</li>
-    		<li><a href="#-ignore-path-">.ignore(path)</a>
-				</li>
-    		<li><a href="#-metadata-json-">.metadata(json)</a>
-				</li>
-    		<li><a href="#-path-paths-">.path(paths...)</a>
-				</li>
-    		<li><a href="#-run-files-fn-">.run(files, fn)</a>
+    		<li><a href="#-connect-path-">.connect(path)</a>
 				</li>
     	</ol>
 	
 			
 			<h1 id="api"><a class="anchor" href="#api"><span></span></a>API</h1>
-<p>Checkout the <a href="https://github.com/metalsmith/metalsmith/tree/master/examples/project-scaffolder">project scaffolder</a> or <a href="https://github.com/metalsmith/metalsmith/tree/master/examples/build-tool">build tool</a> examples to see a real example of the Javascript API in use.</p>
-<h3 id="new-metalsmith-dir-"><a class="anchor" href="#new-metalsmith-dir-"><span></span></a>new Metalsmith(dir)</h3>
-<p>Create a new <code>Metalsmith</code> instance for a working <code>dir</code>.</p>
-<h3 id="-use-plugin-"><a class="anchor" href="#-use-plugin-"><span></span></a>.use(plugin)</h3>
-<p>Add the given <code>plugin</code> function to the middleware stack. Metalsmith uses
-<a href="https://github.com/segmentio/ware">ware</a> to support middleware, so plugins
-should follow the same pattern of taking arguments of <code>(files, metalsmith, callback)</code>,
-modifying the <code>files</code> or <code>metalsmith.metadata()</code> argument by reference, and then
-calling <code>callback</code> to trigger the next step.</p>
-<h3 id="-build-fn-"><a class="anchor" href="#-build-fn-"><span></span></a>.build(fn)</h3>
-<p>Build with the given settings and a callback having signature <code>fn(err, files)</code>.</p>
-<h3 id="-source-path-"><a class="anchor" href="#-source-path-"><span></span></a>.source(path)</h3>
-<p>Set the relative <code>path</code> to the source directory, or get the full one if no <code>path</code> is provided. The source directory defaults to <code>./src</code>.</p>
-<h3 id="-destination-path-"><a class="anchor" href="#-destination-path-"><span></span></a>.destination(path)</h3>
-<p>Set the relative <code>path</code> to the destination directory, or get the full one if no <code>path</code> is provided. The destination directory defaults to <code>./build</code>.</p>
-<h3 id="-concurrency-max-"><a class="anchor" href="#-concurrency-max-"><span></span></a>.concurrency(max)</h3>
-<p>Set the maximum number of files to open at once when reading or writing.  Defaults to <code>Infinity</code>.  To avoid having too many files open at once (<code>EMFILE</code> errors), set the concurrency to something lower than <code>ulimit -n</code>.</p>
-<h3 id="-clean-boolean-"><a class="anchor" href="#-clean-boolean-"><span></span></a>.clean(boolean)</h3>
-<p>Set whether to remove the destination directory before writing to it, or get the current setting. Defaults to <code>true</code>.</p>
-<h3 id="-frontmatter-boolean-"><a class="anchor" href="#-frontmatter-boolean-"><span></span></a>.frontmatter(boolean)</h3>
-<p>Set whether to parse YAML frontmatter. Defaults to <code>true</code>.</p>
-<h3 id="-ignore-path-"><a class="anchor" href="#-ignore-path-"><span></span></a>.ignore(path)</h3>
-<p>Ignore files/paths from being loaded into Metalsmith.</p>
-<p><code>path</code> can be a string, a function, or an array of strings and/or functions.
-Strings use the glob syntax from
-<a href="https://github.com/isaacs/minimatch">minimatch</a> to match files and directories
-to ignore. Functions are called with the full path to the file as their first
-argument, and the <code>lstat</code> object returned by Node&apos;s <code>fs.lstat</code> function as their
-second argument, and must return either <code>true</code> to ignore the file, or <code>false</code> to
-keep it.</p>
-<h3 id="-metadata-json-"><a class="anchor" href="#-metadata-json-"><span></span></a>.metadata(json)</h3>
-<p>Get the global metadata. This is useful for plugins that want to set global-level metadata that can be applied to all files.</p>
-<h3 id="-path-paths-"><a class="anchor" href="#-path-paths-"><span></span></a>.path(paths...)</h3>
-<p>Resolve any amount of <code>paths...</code> relative to the working directory. This is useful for plugins who want to read extra assets from another directory, for example <code>./layouts</code>.</p>
-<h3 id="-run-files-fn-"><a class="anchor" href="#-run-files-fn-"><span></span></a>.run(files, fn)</h3>
-<p>Run all of the middleware functions on a dictionary of <code>files</code> and callback with <code>fn(err, files)</code>, where <code>files</code> is the altered dictionary.</p>
+<h2 id="new-client-"><a class="anchor" href="#new-client-"><span></span></a>new Client()</h2>
+<p>Create a new <code>Client</code> instance.</p>
+<h2 id="-use-plugin-"><a class="anchor" href="#-use-plugin-"><span></span></a>.use(plugin)</h2>
+<p>Add the given <code>plugin</code> function to the middleware stack.</p>
+<h2 id="-connect-path-"><a class="anchor" href="#-connect-path-"><span></span></a>.connect(path)</h2>
+<p>Set the <code>path</code> to the destination socket.</p>
 
 		</article>
 		<div class="clear"></div>
diff --git a/examples/technical-documentation/build/api/metadata.html b/examples/technical-documentation/build/api/metadata.html
deleted file mode 100644
index 2d70ee13..00000000
--- a/examples/technical-documentation/build/api/metadata.html
+++ /dev/null
@@ -1,118 +0,0 @@
-<!DOCTYPE html>
-<html>
-<head>
-	<meta charset="utf-8">
-	<title>Metadata</title>
-	<link href="http://fonts.googleapis.com/css?family=Roboto:400,300|Arvo:400" rel="stylesheet" type="text/css">
-	<link rel="stylesheet" href="https://cdnjs.cloudflare.com/ajax/libs/highlight.js/9.12.0/styles/default.min.css">
-	<link rel="stylesheet" type="text/css" href="../media/style.css">
-</head>
-<body>
-	<header>
-		<div class="container">
-			Version: 1.0.0
-		</div>
-	</header>
-
-		
-	<div class="container content">
-		<aside>
-			<h2>Navigation</h2>
-			<ul>
-				<li><a href="../index.html">Startseite</a></li>
-							<li>
-					API
-					<ul>
-											<li>
-							<a href="../api/api.html">Metalsmith</a>
-						</li>
-											<li>
-							<a href="../api/metadata.html">Metadata</a>
-						</li>
-										</ul>
-				</li>
-							<li>
-					Documentation
-					<ul>
-											<li>
-							<a href="../documentation/matching.html">Matching</a>
-						</li>
-											<li>
-							<a href="../documentation/works.html">How does it work</a>
-						</li>
-										</ul>
-				</li>
-							<li>
-					Installation
-					<ul>
-											<li>
-							<a href="../install/index.html">Installation</a>
-						</li>
-										</ul>
-				</li>
-							<li>
-					Plugins
-					<ul>
-											<li>
-							<a href="../plugins/add.html">The Community Plugins</a>
-						</li>
-											<li>
-							<a href="../plugins/write.html">Writing A Plugin</a>
-						</li>
-										</ul>
-				</li>
-							<li>
-					Getting Started
-					<ul>
-											<li>
-							<a href="../started/install.html">Installation</a>
-						</li>
-											<li>
-							<a href="../started/intro.html">Introduction</a>
-						</li>
-											<li>
-							<a href="../started/metadata.html">Metadata & debugging</a>
-						</li>
-											<li>
-							<a href="../started/plugins.html">Plugins</a>
-						</li>
-											<li>
-							<a href="../started/trouble.html">Troubleshooting</a>
-						</li>
-										</ul>
-				</li>
-						</ul>
-		</aside>
-		<article>
-			
-			<h1 id="metadata-api"><a class="anchor" href="#metadata-api"><span></span></a>Metadata API</h1>
-<p>Add metadata to your files to access these build features. By default, Metalsmith uses a few different metadata fields:</p>
-<ul>
-<li><code>contents</code> - The body content of the file, not including any <a href="https://middlemanapp.com/basics/frontmatter/">YAML frontmatter</a>.</li>
-<li><code>mode</code> - The numeric version of the <a href="http://en.wikipedia.org/wiki/Modes_%28Unix%29">file&apos;s mode</a>.</li>
-</ul>
-<p>You can add your own metadata in two ways:</p>
-<ul>
-<li>Using <a href="https://middlemanapp.com/basics/frontmatter/">YAML frontmatter</a> at the top of any file.</li>
-<li>Enabling <a href="https://github.com/segmentio/metalsmith/blob/master/Readme.md#plugins">a plugin</a> that adds metadata programmatically.</li>
-</ul>
-<h3 id="mode"><a class="anchor" href="#mode"><span></span></a>mode</h3>
-<p>Set the mode of the file. For example,</p>
-<pre><code class="lang-bash">$ cat cleanup.sh
-
---
-mode: 0764
---
-
-rm -rf .
-</code></pre>
-<p>would be built with mode <code>-rwxrw-r--</code>, i.e. user-executable.</p>
-
-		</article>
-		<div class="clear"></div>
-		<footer>
-			<p>Generated with Metalsmith &mdash; <a href="http://www.metalsmith.io/">http://www.metalsmith.io/</a></p>
-		</footer>
-	</div>
-</body>
-</html>
\ No newline at end of file
diff --git a/examples/technical-documentation/build/documentation/matching.html b/examples/technical-documentation/build/documentation/matching.html
deleted file mode 100644
index 015265df..00000000
--- a/examples/technical-documentation/build/documentation/matching.html
+++ /dev/null
@@ -1,126 +0,0 @@
-<!DOCTYPE html>
-<html>
-<head>
-	<meta charset="utf-8">
-	<title>Matching</title>
-	<link href="http://fonts.googleapis.com/css?family=Roboto:400,300|Arvo:400" rel="stylesheet" type="text/css">
-	<link rel="stylesheet" href="https://cdnjs.cloudflare.com/ajax/libs/highlight.js/9.12.0/styles/default.min.css">
-	<link rel="stylesheet" type="text/css" href="../media/style.css">
-</head>
-<body>
-	<header>
-		<div class="container">
-			Version: 1.0.0
-		</div>
-	</header>
-
-		
-	<div class="container content">
-		<aside>
-			<h2>Navigation</h2>
-			<ul>
-				<li><a href="../index.html">Startseite</a></li>
-							<li>
-					API
-					<ul>
-											<li>
-							<a href="../api/api.html">Metalsmith</a>
-						</li>
-											<li>
-							<a href="../api/metadata.html">Metadata</a>
-						</li>
-										</ul>
-				</li>
-							<li>
-					Documentation
-					<ul>
-											<li>
-							<a href="../documentation/matching.html">Matching</a>
-						</li>
-											<li>
-							<a href="../documentation/works.html">How does it work</a>
-						</li>
-										</ul>
-				</li>
-							<li>
-					Installation
-					<ul>
-											<li>
-							<a href="../install/index.html">Installation</a>
-						</li>
-										</ul>
-				</li>
-							<li>
-					Plugins
-					<ul>
-											<li>
-							<a href="../plugins/add.html">The Community Plugins</a>
-						</li>
-											<li>
-							<a href="../plugins/write.html">Writing A Plugin</a>
-						</li>
-										</ul>
-				</li>
-							<li>
-					Getting Started
-					<ul>
-											<li>
-							<a href="../started/install.html">Installation</a>
-						</li>
-											<li>
-							<a href="../started/intro.html">Introduction</a>
-						</li>
-											<li>
-							<a href="../started/metadata.html">Metadata & debugging</a>
-						</li>
-											<li>
-							<a href="../started/plugins.html">Plugins</a>
-						</li>
-											<li>
-							<a href="../started/trouble.html">Troubleshooting</a>
-						</li>
-										</ul>
-				</li>
-						</ul>
-		</aside>
-		<article>
-			
-			<h1 id="matching"><a class="anchor" href="#matching"><span></span></a>Matching</h1>
-<p>Even though we touched on the topic already, we did not tackle it explicitly. We mentioned that plugins usually run through all files presented to <code>metalsmith</code>. This happens in a loop like this:</p>
-<pre><code class="lang-JavaScript">Object.keys(files).forEach(function(file){
-  //
-  // here would be your code
-  //
-});
-</code></pre>
-<p>The question now is, how does for instance a markdown-engine know, which files to transpile? The answer is easy. Per default, <code>metalsmith-markdown</code> is checking if <code>file</code> has a <code>.md</code> or <code>.markdown</code> extension. Remember, <code>file</code> is a JavaScript object that has its full filename (including its path) as a value.
-If the check is not true it jumps over it, otherwise it is passing the file to the engine. After processing it, <code>metalsmith-markdown</code> replaces the <code>.md</code> extension with an <code>.html</code> and the next plugin can now check against the new filename and so on.</p>
-<p>A process such as this is called check for pattern matching. Many <code>metalsmith</code>-plugins employ such matching. Either they check against internally set requirements or patterns or they offer an explicit option to check against user defined matches, like we have already seen in the <code>writemetadata</code>-plugin:</p>
-<pre><code class="lang-JavaScript">.use(writemetadata({            // write the JS object
-  pattern: [&apos;**/*&apos;],            // for each file into .json
-  ignorekeys: [&apos;next&apos;, &apos;previous&apos;],
-  bufferencoding: &apos;utf8&apos;        // also put &apos;content&apos; into .json
-}))
-</code></pre>
-<p>Pattern matching is normally based on <a href="https://github.com/isaacs/node-glob">glob</a> pattern. Many plugins employ either own functions or rely on <a href="https://www.npmjs.com/package/minimatch"><code>minimatch</code></a> or <a href="https://www.npmjs.com/package/multimatch"><code>multimatch</code></a>.</p>
-<pre><code class="lang-JavaScript">var multimatch = require(&apos;multimatch&apos;);
-
-[...]
-
-  // Checks whether files should be processed
-  // length is zero if no matching pattern was found
-  if (multimatch(file, opts.pattern).length) {
-
-    // process file
-
-  }
-</code></pre>
-
-		</article>
-		<div class="clear"></div>
-		<footer>
-			<p>Generated with Metalsmith &mdash; <a href="http://www.metalsmith.io/">http://www.metalsmith.io/</a></p>
-		</footer>
-	</div>
-</body>
-</html>
\ No newline at end of file
diff --git a/examples/technical-documentation/build/documentation/works.html b/examples/technical-documentation/build/documentation/works.html
deleted file mode 100644
index 44954492..00000000
--- a/examples/technical-documentation/build/documentation/works.html
+++ /dev/null
@@ -1,250 +0,0 @@
-<!DOCTYPE html>
-<html>
-<head>
-	<meta charset="utf-8">
-	<title>How does it work</title>
-	<link href="http://fonts.googleapis.com/css?family=Roboto:400,300|Arvo:400" rel="stylesheet" type="text/css">
-	<link rel="stylesheet" href="https://cdnjs.cloudflare.com/ajax/libs/highlight.js/9.12.0/styles/default.min.css">
-	<link rel="stylesheet" type="text/css" href="../media/style.css">
-</head>
-<body>
-	<header>
-		<div class="container">
-			Version: 1.0.0
-		</div>
-	</header>
-
-		
-	<div class="container content">
-		<aside>
-			<h2>Navigation</h2>
-			<ul>
-				<li><a href="../index.html">Startseite</a></li>
-							<li>
-					API
-					<ul>
-											<li>
-							<a href="../api/api.html">Metalsmith</a>
-						</li>
-											<li>
-							<a href="../api/metadata.html">Metadata</a>
-						</li>
-										</ul>
-				</li>
-							<li>
-					Documentation
-					<ul>
-											<li>
-							<a href="../documentation/matching.html">Matching</a>
-						</li>
-											<li>
-							<a href="../documentation/works.html">How does it work</a>
-						</li>
-										</ul>
-				</li>
-							<li>
-					Installation
-					<ul>
-											<li>
-							<a href="../install/index.html">Installation</a>
-						</li>
-										</ul>
-				</li>
-							<li>
-					Plugins
-					<ul>
-											<li>
-							<a href="../plugins/add.html">The Community Plugins</a>
-						</li>
-											<li>
-							<a href="../plugins/write.html">Writing A Plugin</a>
-						</li>
-										</ul>
-				</li>
-							<li>
-					Getting Started
-					<ul>
-											<li>
-							<a href="../started/install.html">Installation</a>
-						</li>
-											<li>
-							<a href="../started/intro.html">Introduction</a>
-						</li>
-											<li>
-							<a href="../started/metadata.html">Metadata & debugging</a>
-						</li>
-											<li>
-							<a href="../started/plugins.html">Plugins</a>
-						</li>
-											<li>
-							<a href="../started/trouble.html">Troubleshooting</a>
-						</li>
-										</ul>
-				</li>
-						</ul>
-		</aside>
-		<article>
-								<ol class="toc">
-			<li><a href="#more-details">More details</a>
-				</li>
-    		<li><a href="#further-information">Further information</a>
-				</li>
-    	</ol>
-	
-			
-			<h1 id="how-does-it-work"><a class="anchor" href="#how-does-it-work"><span></span></a>How does it work</h1>
-<h2 id="more-details"><a class="anchor" href="#more-details"><span></span></a>More details</h2>
-<p>Metalsmith works in three simple steps:</p>
-<ol>
-<li>Read all the files in a source directory and transform them into a JavaScript object of JavaScript objects.</li>
-<li>Invoke a series of plugins that manipulate these objects.</li>
-<li>According to the information contained in the resulting objects write them as files into a destination directory</li>
-</ol>
-<p>Every file in the source directory is transformed into a JavaScript Object. For instance,</p>
-<p><code>my-file.md:</code></p>
-<pre><code class="lang-Markdown">---
-title: A Catchy Title
-draft: false
----
-
-An unfinished article...
-</code></pre>
-<p>becomes</p>
-<pre><code class="lang-JavaScript">{
-  &apos;relative_to_sourcepath/my-file.md&apos;: {
-    title: &apos;A Catchy Title&apos;,
-    draft: false,
-    contents: &apos;An unfinished article...&apos;,
-    mode: &apos;0664&apos;,
-    stats: {
-      /* keys with information on the file */
-    }    
-  }
-}
-</code></pre>
-<p>where the content of the file is always put into the property value of <strong><code>contents</code></strong>. For illustration purposes only we display the value of <strong><code>contents</code></strong> as a string. Technically, however, the property value of <strong><code>contents</code></strong> is realised as a <code>new Buffer(&apos;...&apos;)</code> object, in order to also handle straight binary data well. <strong><code>mode</code></strong> contains the permission the file has and <strong><code>stats</code></strong> has more technical information on the file such as <code>size</code> or <code>birthtime</code>. Furthermore, the file is also parsed for YAML-front-matter information, which will then also be put into the JS Object. Thus, we finally have an JavaScript object of JavaScript objects. This encompassing JavaScript object is usally called <strong><code>files</code></strong> since it contains all the JavaScript objects that represent the files.</p>
-<pre><code class="lang-JavaScript">{
-  &quot;relative_to_sourcepath/file1.md&quot;: {
-    title: &apos;A Catchy Title&apos;,
-    draft: false,
-    contents: &apos;An unfinished article...&apos;,
-    mode: &apos;0664&apos;,
-    stats: {
-      /* keys with information on the file */
-    }    
-  },
-  &quot;relative_to_sourcepath/file2.md&quot;: {
-    title: &apos;An Even Better Title&apos;,
-    draft: false,
-    contents: &apos;One more unfinished article...&apos;,
-    mode: &apos;0664&apos;,
-    stats: {
-      /* keys with information on the file */
-    }    
-  }
-}
-</code></pre>
-<p>The plugins can manipulate the JavaScript objects representing the original files however they want, and writing one is super simple. Here&apos;s the code for the <strong><code>drafts()</code></strong> plugin from above. You can also find the code in the <a href="https://github.com/segmentio/metalsmith-drafts">github repository for <code>metalsmith-drafts</code></a>. The code just runs through the JS object <strong><code>files</code></strong> and deletes all contained JavaScript objects that have a property value of <strong><code>true</code></strong> for the property <strong><code>draft</code></strong>:</p>
-<pre><code class="lang-JavaScript">/**
- * Expose `plugin`.
- */
-module.exports = plugin;
-
-/**
- * Metalsmith plugin to hide drafts from the output.
- *
- * @return {Function}
- */
-
-function plugin() {
-  return function(files, metalsmith, done){
-    setImmediate(done);
-    Object.keys(files).forEach(function(file){
-      var data = files[file];
-      if (data.draft) delete files[file];
-    });
-  };
-}
-</code></pre>
-<p>Of course plugins can get a lot more complicated too. That&apos;s what makes Metalsmith powerful; the plugins can do anything you want and the community has written a large amount of plugins already.</p>
-<p><i><b>Note:</b> The order the plugins are invoked is the order they are in the build script or the metalsmith.json file for cli implementations.  This is important for using a plugin that requires a plugins output to work.</i></p>
-<p>If you are still struggling with the concept we like to recommend you the <a href="https://github.com/Waxolunist/metalsmith-writemetadata"><strong><code>writemetadata()</code></strong></a> plugin. It is a metalsmith plugin that writes the <strong><code>{property: property value}</code></strong> pairs excerpted from the JavaScript objects representing the files to the filesystem as .json files. You can then view the .json files to find out how files are represented internally in Metalsmith.</p>
-<pre><code class="lang-JavaScript">Metalsmith(__dirname)            
-  .source(&apos;sourcepath&apos;)      
-  .destination(&apos;destpath&apos;)   
-  .use(markdown())          
-  .use(layouts({
-    engine: &apos;handlebars&apos;
-  }))
-  .use(writemetadata({            // write the JS object
-    pattern: [&apos;**/*&apos;],            // for each file into .json
-    ignorekeys: [&apos;next&apos;, &apos;previous&apos;],
-    bufferencoding: &apos;utf8&apos;        // also put &apos;content&apos; into .json
-  }))
-  .build(function(err) {         
-    if (err) throw err;          
-  });
-</code></pre>
-<p>We believe, that understanding the internal representation of files as JavaScript objects is really key to fully grasp the concept of Metalsmith. To see this, we look at what happens in the second example chain above:</p>
-<p>So, within the Markdown chain above after applying <strong><code>.use(markdown())</code></strong> the initial representation of the <code>my-file.md</code> becomes <code>my-file.html</code>...</p>
-<pre><code class="lang-JavaScript">{
-  &apos;relative_to_sourcepath/my-file.html&apos;: {
-    title: &apos;A Catchy Title&apos;,
-    draft: false,
-    contents: &apos;&lt;p&gt;An unfinished article...&lt;/p&gt;&apos;,
-    ...
-  }
-}
-</code></pre>
-<p>end after applying <strong><code>.use(permalinks())</code></strong> it becomes:</p>
-<pre><code class="lang-JavaScript">{
-  &apos;relative_to_sourcepath/my-file/index.html&apos;: {
-    title: &apos;A Catchy Title&apos;,
-    draft: false,
-    contents: &apos;&lt;p&gt;An unfinished article...&lt;/p&gt;&apos;,
-    path: &apos;myfile&apos;,
-    ...
-  }
-}
-</code></pre>
-<p>Note, that <code>permalinks()</code> is also adding a <code>path</code>--property by default.</p>
-<p>Assuming somewhere amongst the source files we have defined a very simple standard handlebars layout file...</p>
-<p><code>layout.html</code></p>
-<p>{% raw %}</p>
-<pre><code class="lang-Handlebars">&lt;!doctype html&gt;
-&lt;html&gt;
-&lt;head&gt;
-  &lt;title&gt;{{title}}&lt;/title&gt;
-&lt;/head&gt;
-&lt;body&gt;
-  {{{contents}}}
-&lt;/body&gt;
-&lt;/html&gt;
-</code></pre>
-<p>{% endraw %}</p>
-<p>... after applying <strong><code>.use(layouts())</code></strong> in our Metalsmith chain our JavaScript object becomes:</p>
-<pre><code class="lang-JavaScript">{
-  &apos;relative_to_sourcepath/my-file/index.html&apos;: {
-    title: &apos;A Catchy Title&apos;,
-    draft: false,
-    contents: &apos;&lt;!doctype html&gt;&lt;html&gt;&lt;head&gt;
-               &lt;title&gt;A Catchy Title&lt;/title&gt;&lt;/head&gt;&lt;body&gt;
-               &lt;p&gt;An unfinished article...&lt;/p&gt;
-               &lt;/body&gt;&lt;/html&gt;&apos;,
-    path: &apos;myfile&apos;,
-    ...      
-  }
-}
-</code></pre>
-<p>Finally when the <strong><code>.build(function(err))</code></strong> is performed our JavaScript object is written to <code>relative_to_destpath/myfile/index.html</code>. So you see, how the chain works. It&apos;s rather straight forward, isn&apos;t it?</p>
-<h2 id="further-information"><a class="anchor" href="#further-information"><span></span></a>Further information</h2>
-<p>Yes, we know. The documentation can be improved. If you want to help, give us a shout. But in the meantime have a look at the <a href="https://github.com/metalsmith/awesome-metalsmith">Awesome Metalsmith list</a>. There you will find references to a number of excellent tutorials, examples and use cases.</p>
-
-		</article>
-		<div class="clear"></div>
-		<footer>
-			<p>Generated with Metalsmith &mdash; <a href="http://www.metalsmith.io/">http://www.metalsmith.io/</a></p>
-		</footer>
-	</div>
-</body>
-</html>
\ No newline at end of file
diff --git a/examples/technical-documentation/build/index.html b/examples/technical-documentation/build/index.html
index 77da9456..9656d48e 100644
--- a/examples/technical-documentation/build/index.html
+++ b/examples/technical-documentation/build/index.html
@@ -2,7 +2,7 @@
 <html>
 <head>
 	<meta charset="utf-8">
-	<title>Metalsmith</title>
+	<title>Fancy Documentation</title>
 	<link href="http://fonts.googleapis.com/css?family=Roboto:400,300|Arvo:400" rel="stylesheet" type="text/css">
 	<link rel="stylesheet" href="https://cdnjs.cloudflare.com/ajax/libs/highlight.js/9.12.0/styles/default.min.css">
 	<link rel="stylesheet" type="text/css" href="media/style.css">
@@ -24,40 +24,7 @@ <h2>Navigation</h2>
 					API
 					<ul>
 											<li>
-							<a href="api/api.html">Metalsmith</a>
-						</li>
-											<li>
-							<a href="api/metadata.html">Metadata</a>
-						</li>
-										</ul>
-				</li>
-							<li>
-					Documentation
-					<ul>
-											<li>
-							<a href="documentation/matching.html">Matching</a>
-						</li>
-											<li>
-							<a href="documentation/works.html">How does it work</a>
-						</li>
-										</ul>
-				</li>
-							<li>
-					Installation
-					<ul>
-											<li>
-							<a href="install/index.html">Installation</a>
-						</li>
-										</ul>
-				</li>
-							<li>
-					Plugins
-					<ul>
-											<li>
-							<a href="plugins/add.html">The Community Plugins</a>
-						</li>
-											<li>
-							<a href="plugins/write.html">Writing A Plugin</a>
+							<a href="api/api.html">API</a>
 						</li>
 										</ul>
 				</li>
@@ -66,12 +33,6 @@ <h2>Navigation</h2>
 					<ul>
 											<li>
 							<a href="started/install.html">Installation</a>
-						</li>
-											<li>
-							<a href="started/intro.html">Introduction</a>
-						</li>
-											<li>
-							<a href="started/metadata.html">Metadata & debugging</a>
 						</li>
 											<li>
 							<a href="started/plugins.html">Plugins</a>
@@ -85,74 +46,15 @@ <h2>Navigation</h2>
 		</aside>
 		<article>
 								<ol class="toc">
-			<li><a href="#a-little-secret">A Little Secret</a>
-				</li>
-    		<li><a href="#license">License</a>
+			<li><a href="#license">License</a>
 				</li>
     	</ol>
 	
 			
 			<h1 id="welcome"><a class="anchor" href="#welcome"><span></span></a>Welcome</h1>
-<p>You want to build a website or blog with a static site generator. Well, here is our elevator pitch. It&apos;s as easy as that:</p>
-<pre><code class="lang-JavaScript">var Metalsmith  = require(&apos;metalsmith&apos;);
-var collections = require(&apos;metalsmith-collections&apos;);
-var layouts     = require(&apos;metalsmith-layouts&apos;);
-var markdown    = require(&apos;metalsmith-markdown&apos;);
-var permalinks  = require(&apos;metalsmith-permalinks&apos;);
-
-
-Metalsmith(__dirname)         // __dirname defined by node.js:
-                              // name of current working directory
-  .metadata({                 // add any variable you want
-                              // use them in layout-files
-    sitename: &quot;My Static Site &amp; Blog&quot;,
-    siteurl: &quot;http://example.com/&quot;,
-    description: &quot;It&apos;s about saying &#xBB;Hello&#xAB; to the world.&quot;,
-    generatorname: &quot;Metalsmith&quot;,
-    generatorurl: &quot;http://metalsmith.io/&quot;
-  })
-  .source(&apos;./src&apos;)            // source directory
-  .destination(&apos;./build&apos;)     // destination directory
-  .clean(true)                // clean destination before
-  .use(collections({          // group all blog posts by internally
-    posts: &apos;posts/*.md&apos;       // adding key &apos;collections&apos;:&apos;posts&apos;
-  }))                         // use `collections.posts` in layouts
-  .use(markdown())            // transpile all md into html
-  .use(permalinks({           // change URLs to permalink URLs
-    relative: false           // put css only in /css
-  }))
-  .use(layouts({              // wrap layouts around html
-    engine: &apos;handlebars&apos;,     // use the layout engine you like
-  }))
-  .build(function(err) {      // build process
-    if (err) throw err;       // error handling is required
-  });
-</code></pre>
-<p>You want to try yourself, if it is really this easy. Have a go:</p>
-<pre><code class="lang-bash">$ git clone https://github.com/metalsmith/metalsmith.git
-$ cd metalsmith/examples/static-site
-$ make
-</code></pre>
-<h2 id="a-little-secret"><a class="anchor" href="#a-little-secret"><span></span></a>A Little Secret</h2>
-<p>We keep referring to Metalsmith as a &quot;static site generator&quot;, but it&apos;s a lot more than that. Since everything is a plugin, the core library is actually just an abstraction for manipulating a directory of files.</p>
-<p>Which means you could just as easily use it to make...</p>
-<pre><code>&lt;ul class=&quot;Example-list&quot;&gt;
-{% for example in examples %}
-  &lt;li class=&quot;Example&quot;&gt;
-    &lt;h1 class=&quot;Example-title&quot;&gt;{{ example.name }}&lt;/h1&gt;
-    &lt;ol class=&quot;Example-step-list&quot;&gt;
-    {% for step in example.steps %}
-      &lt;li class=&quot;Example-step ss-{{ step.icon }}&quot;&gt;{{ step.text }}&lt;/li&gt;
-    {% endfor %}
-    &lt;/ol&gt;
-  &lt;/li&gt;
-{% endfor %}
-&lt;/ul&gt;
-</code></pre><p>The plugins are all reusable. That PDF generator plugin for eBooks? Use it to generate PDFs for each of your blog posts too!</p>
-<p>Check out <a href="https://github.com/segmentio/metalsmith/tree/master/examples">the code examples</a> to get an idea for what&apos;s possible.</p>
+<p>Fancy documentation from gitlab docs.</p>
 <h2 id="license"><a class="anchor" href="#license"><span></span></a>License</h2>
 <p>The MIT License (MIT)</p>
-<p>Copyright &#xA9; 2014, Segment.io \<a href="mailto:friends@segment.io\">friends@segment.io\</a></p>
 <p>Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the &quot;Software&quot;), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:</p>
 <p>The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.</p>
 <p>THE SOFTWARE IS PROVIDED &quot;AS IS&quot;, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.</p>
diff --git a/examples/technical-documentation/build/install/index.html b/examples/technical-documentation/build/install/index.html
deleted file mode 100644
index 33f6094c..00000000
--- a/examples/technical-documentation/build/install/index.html
+++ /dev/null
@@ -1,101 +0,0 @@
-<!DOCTYPE html>
-<html>
-<head>
-	<meta charset="utf-8">
-	<title>Installation</title>
-	<link href="http://fonts.googleapis.com/css?family=Roboto:400,300|Arvo:400" rel="stylesheet" type="text/css">
-	<link rel="stylesheet" href="https://cdnjs.cloudflare.com/ajax/libs/highlight.js/9.12.0/styles/default.min.css">
-	<link rel="stylesheet" type="text/css" href="../media/style.css">
-</head>
-<body>
-	<header>
-		<div class="container">
-			Version: 1.0.0
-		</div>
-	</header>
-
-		
-	<div class="container content">
-		<aside>
-			<h2>Navigation</h2>
-			<ul>
-				<li><a href="../index.html">Startseite</a></li>
-							<li>
-					API
-					<ul>
-											<li>
-							<a href="../api/api.html">Metalsmith</a>
-						</li>
-											<li>
-							<a href="../api/metadata.html">Metadata</a>
-						</li>
-										</ul>
-				</li>
-							<li>
-					Documentation
-					<ul>
-											<li>
-							<a href="../documentation/matching.html">Matching</a>
-						</li>
-											<li>
-							<a href="../documentation/works.html">How does it work</a>
-						</li>
-										</ul>
-				</li>
-							<li>
-					Installation
-					<ul>
-											<li>
-							<a href="../install/index.html">Installation</a>
-						</li>
-										</ul>
-				</li>
-							<li>
-					Plugins
-					<ul>
-											<li>
-							<a href="../plugins/add.html">The Community Plugins</a>
-						</li>
-											<li>
-							<a href="../plugins/write.html">Writing A Plugin</a>
-						</li>
-										</ul>
-				</li>
-							<li>
-					Getting Started
-					<ul>
-											<li>
-							<a href="../started/install.html">Installation</a>
-						</li>
-											<li>
-							<a href="../started/intro.html">Introduction</a>
-						</li>
-											<li>
-							<a href="../started/metadata.html">Metadata & debugging</a>
-						</li>
-											<li>
-							<a href="../started/plugins.html">Plugins</a>
-						</li>
-											<li>
-							<a href="../started/trouble.html">Troubleshooting</a>
-						</li>
-										</ul>
-				</li>
-						</ul>
-		</aside>
-		<article>
-			
-			<h1 id="install-it"><a class="anchor" href="#install-it"><span></span></a>Install it</h1>
-<p>Metalsmith and its plugins can be installed with npm:</p>
-<pre><code class="lang-bash">$ npm install metalsmith
-</code></pre>
-<p>The package exposes both a <a href="https://github.com/segmentio/metalsmith#api">JavaScript API</a>, and <a href="https://github.com/segmentio/metalsmith#cli">CLI</a> in case you&apos;re used to that type of workflow from other static site generators. To see how they&apos;re used check out the <a href="https://github.com/segmentio/metalsmith/tree/master/examples">examples</a>.</p>
-
-		</article>
-		<div class="clear"></div>
-		<footer>
-			<p>Generated with Metalsmith &mdash; <a href="http://www.metalsmith.io/">http://www.metalsmith.io/</a></p>
-		</footer>
-	</div>
-</body>
-</html>
\ No newline at end of file
diff --git a/examples/technical-documentation/build/plugins/add.html b/examples/technical-documentation/build/plugins/add.html
deleted file mode 100644
index 1471f21c..00000000
--- a/examples/technical-documentation/build/plugins/add.html
+++ /dev/null
@@ -1,99 +0,0 @@
-<!DOCTYPE html>
-<html>
-<head>
-	<meta charset="utf-8">
-	<title>The Community Plugins</title>
-	<link href="http://fonts.googleapis.com/css?family=Roboto:400,300|Arvo:400" rel="stylesheet" type="text/css">
-	<link rel="stylesheet" href="https://cdnjs.cloudflare.com/ajax/libs/highlight.js/9.12.0/styles/default.min.css">
-	<link rel="stylesheet" type="text/css" href="../media/style.css">
-</head>
-<body>
-	<header>
-		<div class="container">
-			Version: 1.0.0
-		</div>
-	</header>
-
-		
-	<div class="container content">
-		<aside>
-			<h2>Navigation</h2>
-			<ul>
-				<li><a href="../index.html">Startseite</a></li>
-							<li>
-					API
-					<ul>
-											<li>
-							<a href="../api/api.html">Metalsmith</a>
-						</li>
-											<li>
-							<a href="../api/metadata.html">Metadata</a>
-						</li>
-										</ul>
-				</li>
-							<li>
-					Documentation
-					<ul>
-											<li>
-							<a href="../documentation/matching.html">Matching</a>
-						</li>
-											<li>
-							<a href="../documentation/works.html">How does it work</a>
-						</li>
-										</ul>
-				</li>
-							<li>
-					Installation
-					<ul>
-											<li>
-							<a href="../install/index.html">Installation</a>
-						</li>
-										</ul>
-				</li>
-							<li>
-					Plugins
-					<ul>
-											<li>
-							<a href="../plugins/add.html">The Community Plugins</a>
-						</li>
-											<li>
-							<a href="../plugins/write.html">Writing A Plugin</a>
-						</li>
-										</ul>
-				</li>
-							<li>
-					Getting Started
-					<ul>
-											<li>
-							<a href="../started/install.html">Installation</a>
-						</li>
-											<li>
-							<a href="../started/intro.html">Introduction</a>
-						</li>
-											<li>
-							<a href="../started/metadata.html">Metadata & debugging</a>
-						</li>
-											<li>
-							<a href="../started/plugins.html">Plugins</a>
-						</li>
-											<li>
-							<a href="../started/trouble.html">Troubleshooting</a>
-						</li>
-										</ul>
-				</li>
-						</ul>
-		</aside>
-		<article>
-			
-			<h1 id="the-community-plugins"><a class="anchor" href="#the-community-plugins"><span></span></a>The Community Plugins</h1>
-<p>The core Metalsmith library doesn&apos;t bundle any plugins by default.</p>
-<p>If you write your own plugin, submit a pull request to the <a href="https://github.com/segmentio/metalsmith.io/tree/master/src/plugins.json">metalsmith.io</a> repository and it will show up here!</p>
-
-		</article>
-		<div class="clear"></div>
-		<footer>
-			<p>Generated with Metalsmith &mdash; <a href="http://www.metalsmith.io/">http://www.metalsmith.io/</a></p>
-		</footer>
-	</div>
-</body>
-</html>
\ No newline at end of file
diff --git a/examples/technical-documentation/build/plugins/write.html b/examples/technical-documentation/build/plugins/write.html
deleted file mode 100644
index 4e669269..00000000
--- a/examples/technical-documentation/build/plugins/write.html
+++ /dev/null
@@ -1,129 +0,0 @@
-<!DOCTYPE html>
-<html>
-<head>
-	<meta charset="utf-8">
-	<title>Writing A Plugin</title>
-	<link href="http://fonts.googleapis.com/css?family=Roboto:400,300|Arvo:400" rel="stylesheet" type="text/css">
-	<link rel="stylesheet" href="https://cdnjs.cloudflare.com/ajax/libs/highlight.js/9.12.0/styles/default.min.css">
-	<link rel="stylesheet" type="text/css" href="../media/style.css">
-</head>
-<body>
-	<header>
-		<div class="container">
-			Version: 1.0.0
-		</div>
-	</header>
-
-		
-	<div class="container content">
-		<aside>
-			<h2>Navigation</h2>
-			<ul>
-				<li><a href="../index.html">Startseite</a></li>
-							<li>
-					API
-					<ul>
-											<li>
-							<a href="../api/api.html">Metalsmith</a>
-						</li>
-											<li>
-							<a href="../api/metadata.html">Metadata</a>
-						</li>
-										</ul>
-				</li>
-							<li>
-					Documentation
-					<ul>
-											<li>
-							<a href="../documentation/matching.html">Matching</a>
-						</li>
-											<li>
-							<a href="../documentation/works.html">How does it work</a>
-						</li>
-										</ul>
-				</li>
-							<li>
-					Installation
-					<ul>
-											<li>
-							<a href="../install/index.html">Installation</a>
-						</li>
-										</ul>
-				</li>
-							<li>
-					Plugins
-					<ul>
-											<li>
-							<a href="../plugins/add.html">The Community Plugins</a>
-						</li>
-											<li>
-							<a href="../plugins/write.html">Writing A Plugin</a>
-						</li>
-										</ul>
-				</li>
-							<li>
-					Getting Started
-					<ul>
-											<li>
-							<a href="../started/install.html">Installation</a>
-						</li>
-											<li>
-							<a href="../started/intro.html">Introduction</a>
-						</li>
-											<li>
-							<a href="../started/metadata.html">Metadata & debugging</a>
-						</li>
-											<li>
-							<a href="../started/plugins.html">Plugins</a>
-						</li>
-											<li>
-							<a href="../started/trouble.html">Troubleshooting</a>
-						</li>
-										</ul>
-				</li>
-						</ul>
-		</aside>
-		<article>
-			
-			<h1 id="writing-a-plugin"><a class="anchor" href="#writing-a-plugin"><span></span></a>Writing A Plugin</h1>
-<p>Writing a plugin is not difficult as you have seen above with the <code>metalsmith-drafts</code> plugin. In order to achieve more complicated tasks you will most likely find and can use <code>npm</code>-packages. Look at how others have done it. Here is an example using <code>debug</code> (which we appreciate if you use it) and <code>multimatch</code>:</p>
-<p><code>metalsmith-myplugin</code>:</p>
-<pre><code class="lang-JavaScript">// we would like you to use debug
-var debug = require(&apos;debug&apos;)(&apos;metalsmith-myplugin&apos;);
-var multimatch = require(&apos;multimatch&apos;);
-
-
-// Expose `plugin`.
-module.exports = plugin;
-
-
-function plugin(opts){
-  opts.pattern = opts.pattern || [];
-
-  return function (files, metalsmith, done){
-
-    setImmediate(done);
-    Object.keys(files).forEach(function(file){
-      if(multimatch(file, opts.pattern).length) {
-        debug(&apos;myplugin working on: %s&apos;, file);
-
-        //
-        // here would be your code
-        //
-
-      }
-
-    });
-
-  };
-}
-</code></pre>
-
-		</article>
-		<div class="clear"></div>
-		<footer>
-			<p>Generated with Metalsmith &mdash; <a href="http://www.metalsmith.io/">http://www.metalsmith.io/</a></p>
-		</footer>
-	</div>
-</body>
-</html>
\ No newline at end of file
diff --git a/examples/technical-documentation/build/started/install.html b/examples/technical-documentation/build/started/install.html
index 33f6094c..22c45240 100644
--- a/examples/technical-documentation/build/started/install.html
+++ b/examples/technical-documentation/build/started/install.html
@@ -24,40 +24,7 @@ <h2>Navigation</h2>
 					API
 					<ul>
 											<li>
-							<a href="../api/api.html">Metalsmith</a>
-						</li>
-											<li>
-							<a href="../api/metadata.html">Metadata</a>
-						</li>
-										</ul>
-				</li>
-							<li>
-					Documentation
-					<ul>
-											<li>
-							<a href="../documentation/matching.html">Matching</a>
-						</li>
-											<li>
-							<a href="../documentation/works.html">How does it work</a>
-						</li>
-										</ul>
-				</li>
-							<li>
-					Installation
-					<ul>
-											<li>
-							<a href="../install/index.html">Installation</a>
-						</li>
-										</ul>
-				</li>
-							<li>
-					Plugins
-					<ul>
-											<li>
-							<a href="../plugins/add.html">The Community Plugins</a>
-						</li>
-											<li>
-							<a href="../plugins/write.html">Writing A Plugin</a>
+							<a href="../api/api.html">API</a>
 						</li>
 										</ul>
 				</li>
@@ -66,12 +33,6 @@ <h2>Navigation</h2>
 					<ul>
 											<li>
 							<a href="../started/install.html">Installation</a>
-						</li>
-											<li>
-							<a href="../started/intro.html">Introduction</a>
-						</li>
-											<li>
-							<a href="../started/metadata.html">Metadata & debugging</a>
 						</li>
 											<li>
 							<a href="../started/plugins.html">Plugins</a>
@@ -85,11 +46,10 @@ <h2>Navigation</h2>
 		</aside>
 		<article>
 			
-			<h1 id="install-it"><a class="anchor" href="#install-it"><span></span></a>Install it</h1>
-<p>Metalsmith and its plugins can be installed with npm:</p>
-<pre><code class="lang-bash">$ npm install metalsmith
+			<h1 id="install"><a class="anchor" href="#install"><span></span></a>Install</h1>
+<p>Client and its plugins can be installed with npm:</p>
+<pre><code class="lang-bash">$ npm install XXXX
 </code></pre>
-<p>The package exposes both a <a href="https://github.com/segmentio/metalsmith#api">JavaScript API</a>, and <a href="https://github.com/segmentio/metalsmith#cli">CLI</a> in case you&apos;re used to that type of workflow from other static site generators. To see how they&apos;re used check out the <a href="https://github.com/segmentio/metalsmith/tree/master/examples">examples</a>.</p>
 
 		</article>
 		<div class="clear"></div>
diff --git a/examples/technical-documentation/build/started/intro.html b/examples/technical-documentation/build/started/intro.html
deleted file mode 100644
index 576cdd05..00000000
--- a/examples/technical-documentation/build/started/intro.html
+++ /dev/null
@@ -1,127 +0,0 @@
-<!DOCTYPE html>
-<html>
-<head>
-	<meta charset="utf-8">
-	<title>Introduction</title>
-	<link href="http://fonts.googleapis.com/css?family=Roboto:400,300|Arvo:400" rel="stylesheet" type="text/css">
-	<link rel="stylesheet" href="https://cdnjs.cloudflare.com/ajax/libs/highlight.js/9.12.0/styles/default.min.css">
-	<link rel="stylesheet" type="text/css" href="../media/style.css">
-</head>
-<body>
-	<header>
-		<div class="container">
-			Version: 1.0.0
-		</div>
-	</header>
-
-		
-	<div class="container content">
-		<aside>
-			<h2>Navigation</h2>
-			<ul>
-				<li><a href="../index.html">Startseite</a></li>
-							<li>
-					API
-					<ul>
-											<li>
-							<a href="../api/api.html">Metalsmith</a>
-						</li>
-											<li>
-							<a href="../api/metadata.html">Metadata</a>
-						</li>
-										</ul>
-				</li>
-							<li>
-					Documentation
-					<ul>
-											<li>
-							<a href="../documentation/matching.html">Matching</a>
-						</li>
-											<li>
-							<a href="../documentation/works.html">How does it work</a>
-						</li>
-										</ul>
-				</li>
-							<li>
-					Installation
-					<ul>
-											<li>
-							<a href="../install/index.html">Installation</a>
-						</li>
-										</ul>
-				</li>
-							<li>
-					Plugins
-					<ul>
-											<li>
-							<a href="../plugins/add.html">The Community Plugins</a>
-						</li>
-											<li>
-							<a href="../plugins/write.html">Writing A Plugin</a>
-						</li>
-										</ul>
-				</li>
-							<li>
-					Getting Started
-					<ul>
-											<li>
-							<a href="../started/install.html">Installation</a>
-						</li>
-											<li>
-							<a href="../started/intro.html">Introduction</a>
-						</li>
-											<li>
-							<a href="../started/metadata.html">Metadata & debugging</a>
-						</li>
-											<li>
-							<a href="../started/plugins.html">Plugins</a>
-						</li>
-											<li>
-							<a href="../started/trouble.html">Troubleshooting</a>
-						</li>
-										</ul>
-				</li>
-						</ul>
-		</aside>
-		<article>
-								<ol class="toc">
-			<li><a href="#why-is-metalsmith-a-pluggable-static-site-generator-">Why is Metalsmith a pluggable static site generator?</a>
-				</li>
-    		<li><a href="#why-is-metalsmith-extremely-simple-">Why is Metalsmith extremely simple?</a>
-				</li>
-    	</ol>
-	
-			
-			<h1 id="introduction"><a class="anchor" href="#introduction"><span></span></a>Introduction</h1>
-<p>Metalsmith is an extremely simple, pluggable static site generator. So let us explain why:</p>
-<h2 id="why-is-metalsmith-a-pluggable-static-site-generator-"><a class="anchor" href="#why-is-metalsmith-a-pluggable-static-site-generator-"><span></span></a>Why is Metalsmith a <em>pluggable static site generator</em>?</h2>
-<p>The task of a static site generator is to produce static build files that can be deployed to a web server. These files are built from source files. Basically for a static site generator this means:</p>
-<ol>
-<li>from a source directory read the source files and extract their information</li>
-<li>manipulate the information</li>
-<li>write the manipulated information to files into a destination directory</li>
-</ol>
-<p>Metalsmith is built on this reasoning. It takes the information from the source files from a source directory and it writes the manipulated information to files into a destination directory. All manipulations, however, it exclusively leaves to plugins.</p>
-<p>Manipulations can be anything: translating templates, transpiling code, replacing variables, wrapping layouts around content, grouping files, moving files and so on. This is why we say <em>&#xBB;Everything is a Plugin&#xAB;</em>. And of course, several manipulations can be applied one after another. Obviously, in this case the sequence matters.</p>
-<h2 id="why-is-metalsmith-extremely-simple-"><a class="anchor" href="#why-is-metalsmith-extremely-simple-"><span></span></a>Why is Metalsmith <em>extremely simple</em>?</h2>
-<ol>
-<li><p>When all manipulations are performed by plugins, the only thing Metalsmith has to do in its core is to provide for an underlying logic of actually how manipulations are dealt with and for a defined interface for the plugins. To achieve this, we only needed around 400 lines of code --- have a <a href="https://github.com/metalsmith/metalsmith/blob/master/lib/index.js">look at the source yourself</a>. We believe this is rather simple.</p>
-</li>
-<li><p>For manipulations Metalsmith uses a very clever, but extremely simple idea. All source files are initially converted into JavaScript objects with the usual <strong><code>{property: property value}</code></strong> pairs. These <strong><code>{property: property value}</code></strong> pairs contain information on the original file itself (such as its <strong><code>birthtime</code></strong> or <strong><code>path</code></strong>) and on its <strong><code>content</code></strong>. The JavaScript object for each file is then supplemented with all variables either specified in the front-matter of the file or elsewhere. The manipulations performed by the plugins are now nothing else then modifications applied to the JavaScript objects either by changing the properties or the property values.</p>
-</li>
-<li><p>Breaking down Metalsmith into a core and many plugins has several advantages. It reduces complexity. It gives the user the freedom to use exactly only those plugins he or she needs. Furthermore, it distributes the honor and the burden of maintaining the Metalsmith core and its plugins onto the Metalsmith community. With this approach we hope to keep the Metalsmith environment pretty up-to-date.</p>
-</li>
-<li><p>Writing plugins itself is also rather simple. The plugin-interface is easy to understand and most plugins are also rather short.</p>
-</li>
-<li><p>Every site needs JavaScript anyway. Just like the popular task runners <a href="http://gulpjs.com/">gulp</a> or <a href="http://gruntjs.com/">grunt</a> Metalsmith is programmed in JavaScript. So, you do not have to rely on a further language such as Ruby, Python or Go. This also helps to keep your workflow simple.</p>
-</li>
-</ol>
-
-		</article>
-		<div class="clear"></div>
-		<footer>
-			<p>Generated with Metalsmith &mdash; <a href="http://www.metalsmith.io/">http://www.metalsmith.io/</a></p>
-		</footer>
-	</div>
-</body>
-</html>
\ No newline at end of file
diff --git a/examples/technical-documentation/build/started/metadata.html b/examples/technical-documentation/build/started/metadata.html
deleted file mode 100644
index e09024e4..00000000
--- a/examples/technical-documentation/build/started/metadata.html
+++ /dev/null
@@ -1,123 +0,0 @@
-<!DOCTYPE html>
-<html>
-<head>
-	<meta charset="utf-8">
-	<title>Metadata & debugging</title>
-	<link href="http://fonts.googleapis.com/css?family=Roboto:400,300|Arvo:400" rel="stylesheet" type="text/css">
-	<link rel="stylesheet" href="https://cdnjs.cloudflare.com/ajax/libs/highlight.js/9.12.0/styles/default.min.css">
-	<link rel="stylesheet" type="text/css" href="../media/style.css">
-</head>
-<body>
-	<header>
-		<div class="container">
-			Version: 1.0.0
-		</div>
-	</header>
-
-		
-	<div class="container content">
-		<aside>
-			<h2>Navigation</h2>
-			<ul>
-				<li><a href="../index.html">Startseite</a></li>
-							<li>
-					API
-					<ul>
-											<li>
-							<a href="../api/api.html">Metalsmith</a>
-						</li>
-											<li>
-							<a href="../api/metadata.html">Metadata</a>
-						</li>
-										</ul>
-				</li>
-							<li>
-					Documentation
-					<ul>
-											<li>
-							<a href="../documentation/matching.html">Matching</a>
-						</li>
-											<li>
-							<a href="../documentation/works.html">How does it work</a>
-						</li>
-										</ul>
-				</li>
-							<li>
-					Installation
-					<ul>
-											<li>
-							<a href="../install/index.html">Installation</a>
-						</li>
-										</ul>
-				</li>
-							<li>
-					Plugins
-					<ul>
-											<li>
-							<a href="../plugins/add.html">The Community Plugins</a>
-						</li>
-											<li>
-							<a href="../plugins/write.html">Writing A Plugin</a>
-						</li>
-										</ul>
-				</li>
-							<li>
-					Getting Started
-					<ul>
-											<li>
-							<a href="../started/install.html">Installation</a>
-						</li>
-											<li>
-							<a href="../started/intro.html">Introduction</a>
-						</li>
-											<li>
-							<a href="../started/metadata.html">Metadata & debugging</a>
-						</li>
-											<li>
-							<a href="../started/plugins.html">Plugins</a>
-						</li>
-											<li>
-							<a href="../started/trouble.html">Troubleshooting</a>
-						</li>
-										</ul>
-				</li>
-						</ul>
-		</aside>
-		<article>
-			
-			<h1 id="metadata-debugging"><a class="anchor" href="#metadata-debugging"><span></span></a>Metadata &amp; debugging</h1>
-<p>For Metalsmith we have stated that everything is a plugin. That is true, but in addition the Metalsmith core also provides for a <strong><code>metadata()</code></strong> function. You can specify arbitrary <strong><code>{property: property value}</code></strong> pairs and these information will be globally accessible from each plugin.</p>
-<pre><code class="lang-JavaScript">var debug = require(&apos;metalsmith-debug&apos;);
-
-...
-
-Metalsmith(__dirname)            
-  .source(&apos;sourcepath&apos;)      
-  .destination(&apos;destpath&apos;)   
-  .clean(false)
-  .metadata({
-      author: &apos;John Doe&apos;,
-      site: &apos;http://example.com&apos;
-  })
-  .use(markdown())
-  .use(layouts({
-    engine: &apos;handlebars&apos;
-  }))
-  .use(debug())             // displays debug info on the console
-  .build(function(err) {         
-    if (err) throw err;
-  });
-</code></pre>
-<p>As you have seen in the code above, we have also introduced a plugin named <a href="https://github.com/mahnunchik/metalsmith-debug"><strong><code>metalsmith-debug</code></strong></a>. For this plugin to actually show debug information you need to define an environment variable <code>DEBUG</code> and set it to:</p>
-<pre><code class="lang-bash">$ DEBUG=metalsmith:*
-</code></pre>
-<p>The source and destination path, the metadata and all files are then logged to the console.</p>
-
-		</article>
-		<div class="clear"></div>
-		<footer>
-			<p>Generated with Metalsmith &mdash; <a href="http://www.metalsmith.io/">http://www.metalsmith.io/</a></p>
-		</footer>
-	</div>
-</body>
-</html>
\ No newline at end of file
diff --git a/examples/technical-documentation/build/started/plugins.html b/examples/technical-documentation/build/started/plugins.html
index a07e2bfa..4512e0a0 100644
--- a/examples/technical-documentation/build/started/plugins.html
+++ b/examples/technical-documentation/build/started/plugins.html
@@ -24,40 +24,7 @@ <h2>Navigation</h2>
 					API
 					<ul>
 											<li>
-							<a href="../api/api.html">Metalsmith</a>
-						</li>
-											<li>
-							<a href="../api/metadata.html">Metadata</a>
-						</li>
-										</ul>
-				</li>
-							<li>
-					Documentation
-					<ul>
-											<li>
-							<a href="../documentation/matching.html">Matching</a>
-						</li>
-											<li>
-							<a href="../documentation/works.html">How does it work</a>
-						</li>
-										</ul>
-				</li>
-							<li>
-					Installation
-					<ul>
-											<li>
-							<a href="../install/index.html">Installation</a>
-						</li>
-										</ul>
-				</li>
-							<li>
-					Plugins
-					<ul>
-											<li>
-							<a href="../plugins/add.html">The Community Plugins</a>
-						</li>
-											<li>
-							<a href="../plugins/write.html">Writing A Plugin</a>
+							<a href="../api/api.html">API</a>
 						</li>
 										</ul>
 				</li>
@@ -66,12 +33,6 @@ <h2>Navigation</h2>
 					<ul>
 											<li>
 							<a href="../started/install.html">Installation</a>
-						</li>
-											<li>
-							<a href="../started/intro.html">Introduction</a>
-						</li>
-											<li>
-							<a href="../started/metadata.html">Metadata & debugging</a>
 						</li>
 											<li>
 							<a href="../started/plugins.html">Plugins</a>
@@ -85,37 +46,15 @@ <h2>Navigation</h2>
 		</aside>
 		<article>
 			
-			<h1 id="everything-is-a-plugin-a-first-example"><a class="anchor" href="#everything-is-a-plugin-a-first-example"><span></span></a>Everything is a Plugin - A first example</h1>
-<p>All of the logic in Metalsmith is handled by plugins. You simply chain them together. Here&apos;s what the simplest blog looks like. It uses only two plugins, <strong><code>markdown()</code></strong> and <strong><code>layouts()</code></strong>...</p>
-<pre><code class="lang-js">Metalsmith(__dirname)          // instantiate Metalsmith in the cwd
-  .source(&apos;sourcepath&apos;)        // specify source directory
-  .destination(&apos;destpath&apos;)     // specify destination directory
-  .use(markdown())             // transpile markdown into html
-  .use(layouts({               // wrap a handlebars-layout
-    engine: &apos;handlebars&apos;       // around transpiled html-files
-  }))    
-  .build(function(err) {       // this is the actual build process
-    if (err) throw err;    // throwing errors is required
-  });
-</code></pre>
-<p>... and by the way, if you do not want your destination directory to be cleaned before a new build, just add <b><code>.clean(false)</code></b>. But what if you want to get fancier by hiding your unfinished drafts and using permalinks? Just add plugins...</p>
-<pre><code class="lang-js">Metalsmith(__dirname)
-  .source(&apos;sourcepath&apos;)      
-  .destination(&apos;destpath&apos;)
-  .clean(false)                  // do not clean destination
-                                 // directory before new build   
-  .use(drafts())                 // only files that are NOT drafts
-  .use(markdown())
-  .use(permalinks())             // make a permalink output path
-  .use(layouts({
-    engine: &apos;handlebars&apos;
+			<h1 id="plugin"><a class="anchor" href="#plugin"><span></span></a>Plugin</h1>
+<p>All of the logic in the Client is handled by plugins. You simply chain them together.</p>
+<pre><code class="lang-js">Client()
+  .use(ssh({
+    port: &apos;22&apos;
   }))
-  .build(function(err) {    
-    if (err) throw err;
-  });
+  .connect(&apos;/var/socket&apos;)
 </code></pre>
 <p>...it&apos;s as easy as that!</p>
-<p>A small comment. Instead of <a href="http://handlebarsjs.com/">Handlebars</a> you can also use other templating languages such as <a href="http://jade-lang.com/">Jade/Pug</a>.</p>
 
 		</article>
 		<div class="clear"></div>
diff --git a/examples/technical-documentation/build/started/trouble.html b/examples/technical-documentation/build/started/trouble.html
index dadf0d51..4f6be5c1 100644
--- a/examples/technical-documentation/build/started/trouble.html
+++ b/examples/technical-documentation/build/started/trouble.html
@@ -24,40 +24,7 @@ <h2>Navigation</h2>
 					API
 					<ul>
 											<li>
-							<a href="../api/api.html">Metalsmith</a>
-						</li>
-											<li>
-							<a href="../api/metadata.html">Metadata</a>
-						</li>
-										</ul>
-				</li>
-							<li>
-					Documentation
-					<ul>
-											<li>
-							<a href="../documentation/matching.html">Matching</a>
-						</li>
-											<li>
-							<a href="../documentation/works.html">How does it work</a>
-						</li>
-										</ul>
-				</li>
-							<li>
-					Installation
-					<ul>
-											<li>
-							<a href="../install/index.html">Installation</a>
-						</li>
-										</ul>
-				</li>
-							<li>
-					Plugins
-					<ul>
-											<li>
-							<a href="../plugins/add.html">The Community Plugins</a>
-						</li>
-											<li>
-							<a href="../plugins/write.html">Writing A Plugin</a>
+							<a href="../api/api.html">API</a>
 						</li>
 										</ul>
 				</li>
@@ -66,12 +33,6 @@ <h2>Navigation</h2>
 					<ul>
 											<li>
 							<a href="../started/install.html">Installation</a>
-						</li>
-											<li>
-							<a href="../started/intro.html">Introduction</a>
-						</li>
-											<li>
-							<a href="../started/metadata.html">Metadata & debugging</a>
 						</li>
 											<li>
 							<a href="../started/plugins.html">Plugins</a>
@@ -89,8 +50,6 @@ <h2>Navigation</h2>
 									<ol class="toc">
 			<li><a href="#using-node-js-0-10-x">Using node.js 0.10.x</a>
 				</li>
-    		<li><a href="#using-node-js-0-12-x">Using node.js 0.12.x</a>
-				</li>
     	</ol>
 	
 				</li>
@@ -99,24 +58,9 @@ <h2>Navigation</h2>
 			
 			<h1 id="troubleshooting"><a class="anchor" href="#troubleshooting"><span></span></a>Troubleshooting</h1>
 <h2 id="node-version-requirements"><a class="anchor" href="#node-version-requirements"><span></span></a>Node Version Requirements</h2>
-<p>Metalsmith v2.0 and above uses <a href="https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Generator">generators</a> which has some considerations for <code>node.js 0.12.x</code> and below.</p>
+<p>Client v2.0 and above uses <code>node.js 0.12.x</code> and below.</p>
 <h3 id="using-node-js-0-10-x"><a class="anchor" href="#using-node-js-0-10-x"><span></span></a>Using node.js 0.10.x</h3>
-<p>You have two options:</p>
-<ol>
-<li>Upgrade to latest stable version of <code>node.js</code> (&gt;= <code>0.12.x</code> &#x2014; see &quot;<em>Using <code>node.js 0.12.x</code></em>&quot; section below)</li>
-<li>Use Metalsmith v1.7. Put <code>&quot;metalsmith&quot;: &quot;^1.7.0&quot;</code> in your <code>package.json</code> and <code>npm install</code> that version.</li>
-</ol>
-<h3 id="using-node-js-0-12-x"><a class="anchor" href="#using-node-js-0-12-x"><span></span></a>Using node.js 0.12.x</h3>
-<p>You have three options:</p>
-<ol>
-<li>Run <code>node.js</code> with <code>--harmony_generators</code> flag set.<ol>
-<li><code>node --harmony_generators my_script.js</code></li>
-<li>Using <code>package.json</code>: <code>&quot;scripts&quot;: {&quot;start&quot;: &quot;node --harmony_generators my_script.js&quot;}</code>. Run with <code>npm run</code></li>
-</ol>
-</li>
-<li><code>npm install</code> <a href="https://www.npmjs.com/package/harmonize">harmonize</a> and require before Metalsmith is used. e.g. <code>require(&quot;harmonize&quot;)([&quot;harmony-generators&quot;]);</code></li>
-<li>Use Metalsmith v1.7. Put <code>&quot;metalsmith&quot;: &quot;^1.7.0&quot;</code> in your <code>package.json</code> and <code>npm install</code> that version.</li>
-</ol>
+<p>Upgrade to latest stable version of <code>node.js</code> (&gt;= <code>0.12.x</code> &#x2014; see &quot;<em>Using <code>node.js 0.12.x</code></em>&quot; section below)</p>
 
 		</article>
 		<div class="clear"></div>
diff --git a/examples/technical-documentation/src/api/api.md b/examples/technical-documentation/src/api/api.md
index 64e27f5f..5a29ed93 100644
--- a/examples/technical-documentation/src/api/api.md
+++ b/examples/technical-documentation/src/api/api.md
@@ -1,6 +1,5 @@
 ---
-title: "Metalsmith"
-description: "An extremely simple, pluggable static site generator."
+title: "API"
 autotoc: true
 view: layout.twig
 collection: "API"
@@ -8,64 +7,14 @@ collection: "API"
 
 # API
 
-Checkout the [project scaffolder](https://github.com/metalsmith/metalsmith/tree/master/examples/project-scaffolder) or [build tool](https://github.com/metalsmith/metalsmith/tree/master/examples/build-tool) examples to see a real example of the Javascript API in use.
+## new Client()
 
-### new Metalsmith(dir)
+Create a new `Client` instance.
 
-Create a new `Metalsmith` instance for a working `dir`.
+## .use(plugin)
 
-### .use(plugin)
+Add the given `plugin` function to the middleware stack.
 
-Add the given `plugin` function to the middleware stack. Metalsmith uses
-[ware](https://github.com/segmentio/ware) to support middleware, so plugins
-should follow the same pattern of taking arguments of `(files, metalsmith, callback)`,
-modifying the `files` or `metalsmith.metadata()` argument by reference, and then
-calling `callback` to trigger the next step.
+## .connect(path)
 
-### .build(fn)
-
-Build with the given settings and a callback having signature `fn(err, files)`.
-
-### .source(path)
-
-Set the relative `path` to the source directory, or get the full one if no `path` is provided. The source directory defaults to `./src`.
-
-### .destination(path)
-
-Set the relative `path` to the destination directory, or get the full one if no `path` is provided. The destination directory defaults to `./build`.
-
-### .concurrency(max)
-
-Set the maximum number of files to open at once when reading or writing.  Defaults to `Infinity`.  To avoid having too many files open at once (`EMFILE` errors), set the concurrency to something lower than `ulimit -n`.
-
-### .clean(boolean)
-
-Set whether to remove the destination directory before writing to it, or get the current setting. Defaults to `true`.
-
-### .frontmatter(boolean)
-
-Set whether to parse YAML frontmatter. Defaults to `true`.
-
-### .ignore(path)
-
-Ignore files/paths from being loaded into Metalsmith.
-
-`path` can be a string, a function, or an array of strings and/or functions.
-Strings use the glob syntax from
-[minimatch](https://github.com/isaacs/minimatch) to match files and directories
-to ignore. Functions are called with the full path to the file as their first
-argument, and the `lstat` object returned by Node's `fs.lstat` function as their
-second argument, and must return either `true` to ignore the file, or `false` to
-keep it.
-
-### .metadata(json)
-
-Get the global metadata. This is useful for plugins that want to set global-level metadata that can be applied to all files.
-
-### .path(paths...)
-
-Resolve any amount of `paths...` relative to the working directory. This is useful for plugins who want to read extra assets from another directory, for example `./layouts`.
-
-### .run(files, fn)
-
-Run all of the middleware functions on a dictionary of `files` and callback with `fn(err, files)`, where `files` is the altered dictionary.
\ No newline at end of file
+Set the `path` to the destination socket.
diff --git a/examples/technical-documentation/src/api/metadata.md b/examples/technical-documentation/src/api/metadata.md
deleted file mode 100644
index 7c6a17af..00000000
--- a/examples/technical-documentation/src/api/metadata.md
+++ /dev/null
@@ -1,35 +0,0 @@
----
-title: "Metadata"
-description: "An extremely simple, pluggable static site generator."
-autotoc: false
-view: layout.twig
-collection: "API"
----
-
-# Metadata API
-
-Add metadata to your files to access these build features. By default, Metalsmith uses a few different metadata fields:
-
-- `contents` - The body content of the file, not including any [YAML frontmatter](https://middlemanapp.com/basics/frontmatter/).
-- `mode` - The numeric version of the [file's mode](http://en.wikipedia.org/wiki/Modes_%28Unix%29).
-
-You can add your own metadata in two ways:
-
-- Using [YAML frontmatter](https://middlemanapp.com/basics/frontmatter/) at the top of any file.
-- Enabling [a plugin](https://github.com/segmentio/metalsmith/blob/master/Readme.md#plugins) that adds metadata programmatically.
-
-### mode
-
-Set the mode of the file. For example,
-
-```bash
-$ cat cleanup.sh
-
---
-mode: 0764
---
-
-rm -rf .
-```
-
-would be built with mode `-rwxrw-r--`, i.e. user-executable.
diff --git a/examples/technical-documentation/src/documentation/matching.md b/examples/technical-documentation/src/documentation/matching.md
deleted file mode 100644
index 48519440..00000000
--- a/examples/technical-documentation/src/documentation/matching.md
+++ /dev/null
@@ -1,49 +0,0 @@
----
-title: "Matching"
-description: "An extremely simple, pluggable static site generator."
-autotoc: true
-view: layout.twig
-collection: "Documentation"
----
-
-# Matching
-
-Even though we touched on the topic already, we did not tackle it explicitly. We mentioned that plugins usually run through all files presented to `metalsmith`. This happens in a loop like this:
-
-```JavaScript
-Object.keys(files).forEach(function(file){
-  //
-  // here would be your code
-  //
-});
-```
-
-The question now is, how does for instance a markdown-engine know, which files to transpile? The answer is easy. Per default, `metalsmith-markdown` is checking if `file` has a `.md` or `.markdown` extension. Remember, `file` is a JavaScript object that has its full filename (including its path) as a value.
-If the check is not true it jumps over it, otherwise it is passing the file to the engine. After processing it, `metalsmith-markdown` replaces the `.md` extension with an `.html` and the next plugin can now check against the new filename and so on.
-
-A process such as this is called check for pattern matching. Many `metalsmith`-plugins employ such matching. Either they check against internally set requirements or patterns or they offer an explicit option to check against user defined matches, like we have already seen in the `writemetadata`-plugin:
-
-```JavaScript
-.use(writemetadata({            // write the JS object
-  pattern: ['**/*'],            // for each file into .json
-  ignorekeys: ['next', 'previous'],
-  bufferencoding: 'utf8'        // also put 'content' into .json
-}))
-```
-
-Pattern matching is normally based on [glob](https://github.com/isaacs/node-glob) pattern. Many plugins employ either own functions or rely on [`minimatch`](https://www.npmjs.com/package/minimatch) or [`multimatch`](https://www.npmjs.com/package/multimatch).
-
-
-```JavaScript
-var multimatch = require('multimatch');
-
-[...]
-
-  // Checks whether files should be processed
-  // length is zero if no matching pattern was found
-  if (multimatch(file, opts.pattern).length) {
-
-    // process file
-
-  }
-```
\ No newline at end of file
diff --git a/examples/technical-documentation/src/documentation/works.md b/examples/technical-documentation/src/documentation/works.md
deleted file mode 100644
index ac8175be..00000000
--- a/examples/technical-documentation/src/documentation/works.md
+++ /dev/null
@@ -1,195 +0,0 @@
----
-title: "How does it work"
-description: "An extremely simple, pluggable static site generator."
-autotoc: true
-view: layout.twig
-collection: "Documentation"
----
-
-# How does it work
-
-## More details
-
-Metalsmith works in three simple steps:
-
-  1. Read all the files in a source directory and transform them into a JavaScript object of JavaScript objects.
-  2. Invoke a series of plugins that manipulate these objects.
-  3. According to the information contained in the resulting objects write them as files into a destination directory
-
-Every file in the source directory is transformed into a JavaScript Object. For instance,
-
-`my-file.md:`
-
-```Markdown
----
-title: A Catchy Title
-draft: false
----
-
-An unfinished article...
-```
-
-becomes
-
-```JavaScript
-{
-  'relative_to_sourcepath/my-file.md': {
-    title: 'A Catchy Title',
-    draft: false,
-    contents: 'An unfinished article...',
-    mode: '0664',
-    stats: {
-      /* keys with information on the file */
-    }    
-  }
-}
-```
-
-where the content of the file is always put into the property value of **`contents`**. For illustration purposes only we display the value of **`contents`** as a string. Technically, however, the property value of **`contents`** is realised as a `new Buffer('...')` object, in order to also handle straight binary data well. **`mode`** contains the permission the file has and **`stats`** has more technical information on the file such as `size` or `birthtime`. Furthermore, the file is also parsed for YAML-front-matter information, which will then also be put into the JS Object. Thus, we finally have an JavaScript object of JavaScript objects. This encompassing JavaScript object is usally called **`files`** since it contains all the JavaScript objects that represent the files.
-
-```JavaScript
-{
-  "relative_to_sourcepath/file1.md": {
-    title: 'A Catchy Title',
-    draft: false,
-    contents: 'An unfinished article...',
-    mode: '0664',
-    stats: {
-      /* keys with information on the file */
-    }    
-  },
-  "relative_to_sourcepath/file2.md": {
-    title: 'An Even Better Title',
-    draft: false,
-    contents: 'One more unfinished article...',
-    mode: '0664',
-    stats: {
-      /* keys with information on the file */
-    }    
-  }
-}
-```
-
-The plugins can manipulate the JavaScript objects representing the original files however they want, and writing one is super simple. Here's the code for the **`drafts()`** plugin from above. You can also find the code in the [github repository for `metalsmith-drafts`](https://github.com/segmentio/metalsmith-drafts). The code just runs through the JS object **`files`** and deletes all contained JavaScript objects that have a property value of **`true`** for the property **`draft`**:
-
-```JavaScript
-/**
- * Expose `plugin`.
- */
-module.exports = plugin;
-
-/**
- * Metalsmith plugin to hide drafts from the output.
- *
- * @return {Function}
- */
-
-function plugin() {
-  return function(files, metalsmith, done){
-    setImmediate(done);
-    Object.keys(files).forEach(function(file){
-      var data = files[file];
-      if (data.draft) delete files[file];
-    });
-  };
-}
-```
-
-Of course plugins can get a lot more complicated too. That's what makes Metalsmith powerful; the plugins can do anything you want and the community has written a large amount of plugins already.
-
-<i><b>Note:</b> The order the plugins are invoked is the order they are in the build script or the metalsmith.json file for cli implementations.  This is important for using a plugin that requires a plugins output to work.</i>
-
-If you are still struggling with the concept we like to recommend you the [**`writemetadata()`**](https://github.com/Waxolunist/metalsmith-writemetadata) plugin. It is a metalsmith plugin that writes the **`{property: property value}`** pairs excerpted from the JavaScript objects representing the files to the filesystem as .json files. You can then view the .json files to find out how files are represented internally in Metalsmith.
-
-```JavaScript
-Metalsmith(__dirname)            
-  .source('sourcepath')      
-  .destination('destpath')   
-  .use(markdown())          
-  .use(layouts({
-    engine: 'handlebars'
-  }))
-  .use(writemetadata({            // write the JS object
-    pattern: ['**/*'],            // for each file into .json
-    ignorekeys: ['next', 'previous'],
-    bufferencoding: 'utf8'        // also put 'content' into .json
-  }))
-  .build(function(err) {         
-    if (err) throw err;          
-  });
-```
-
-We believe, that understanding the internal representation of files as JavaScript objects is really key to fully grasp the concept of Metalsmith. To see this, we look at what happens in the second example chain above:
-
-So, within the Markdown chain above after applying **`.use(markdown())`** the initial representation of the `my-file.md` becomes `my-file.html`...
-
-```JavaScript
-{
-  'relative_to_sourcepath/my-file.html': {
-    title: 'A Catchy Title',
-    draft: false,
-    contents: '<p>An unfinished article...</p>',
-    ...
-  }
-}
-
-```
-
-end after applying **`.use(permalinks())`** it becomes:
-
-```JavaScript
-{
-  'relative_to_sourcepath/my-file/index.html': {
-    title: 'A Catchy Title',
-    draft: false,
-    contents: '<p>An unfinished article...</p>',
-    path: 'myfile',
-    ...
-  }
-}
-
-```
-
-Note, that `permalinks()` is also adding a `path`--property by default.
-
-Assuming somewhere amongst the source files we have defined a very simple standard handlebars layout file...
-
-`layout.html`
-
-{% raw %}
-```Handlebars
-<!doctype html>
-<html>
-<head>
-  <title>{{title}}</title>
-</head>
-<body>
-  {{{contents}}}
-</body>
-</html>
-```
-{% endraw %}
-
-... after applying **`.use(layouts())`** in our Metalsmith chain our JavaScript object becomes:
-
-```JavaScript
-{
-  'relative_to_sourcepath/my-file/index.html': {
-    title: 'A Catchy Title',
-    draft: false,
-    contents: '<!doctype html><html><head>
-               <title>A Catchy Title</title></head><body>
-               <p>An unfinished article...</p>
-               </body></html>',
-    path: 'myfile',
-    ...      
-  }
-}
-
-```
-
-Finally when the **`.build(function(err))`** is performed our JavaScript object is written to `relative_to_destpath/myfile/index.html`. So you see, how the chain works. It's rather straight forward, isn't it?
-
-## Further information
-
-Yes, we know. The documentation can be improved. If you want to help, give us a shout. But in the meantime have a look at the [Awesome Metalsmith list](https://github.com/metalsmith/awesome-metalsmith). There you will find references to a number of excellent tutorials, examples and use cases.
\ No newline at end of file
diff --git a/examples/technical-documentation/src/index.md b/examples/technical-documentation/src/index.md
index 1756b1c4..af83713c 100644
--- a/examples/technical-documentation/src/index.md
+++ b/examples/technical-documentation/src/index.md
@@ -1,89 +1,17 @@
 ---
-title: "Metalsmith"
-description: "An extremely simple, pluggable static site generator."
+title: "Fancy Documentation"
 autotoc: true
 view: layout.twig
 ---
 
 # Welcome
 
-You want to build a website or blog with a static site generator. Well, here is our elevator pitch. It's as easy as that:
-
-```JavaScript
-var Metalsmith  = require('metalsmith');
-var collections = require('metalsmith-collections');
-var layouts     = require('metalsmith-layouts');
-var markdown    = require('metalsmith-markdown');
-var permalinks  = require('metalsmith-permalinks');
-
-
-Metalsmith(__dirname)         // __dirname defined by node.js:
-                              // name of current working directory
-  .metadata({                 // add any variable you want
-                              // use them in layout-files
-    sitename: "My Static Site & Blog",
-    siteurl: "http://example.com/",
-    description: "It's about saying »Hello« to the world.",
-    generatorname: "Metalsmith",
-    generatorurl: "http://metalsmith.io/"
-  })
-  .source('./src')            // source directory
-  .destination('./build')     // destination directory
-  .clean(true)                // clean destination before
-  .use(collections({          // group all blog posts by internally
-    posts: 'posts/*.md'       // adding key 'collections':'posts'
-  }))                         // use `collections.posts` in layouts
-  .use(markdown())            // transpile all md into html
-  .use(permalinks({           // change URLs to permalink URLs
-    relative: false           // put css only in /css
-  }))
-  .use(layouts({              // wrap layouts around html
-    engine: 'handlebars',     // use the layout engine you like
-  }))
-  .build(function(err) {      // build process
-    if (err) throw err;       // error handling is required
-  });
-```
-
-You want to try yourself, if it is really this easy. Have a go:
-
-```bash
-$ git clone https://github.com/metalsmith/metalsmith.git
-$ cd metalsmith/examples/static-site
-$ make
-```
-
-## A Little Secret
-
-We keep referring to Metalsmith as a "static site generator", but it's a lot more than that. Since everything is a plugin, the core library is actually just an abstraction for manipulating a directory of files.
-
-Which means you could just as easily use it to make...
-
-```
-<ul class="Example-list">
-{% for example in examples %}
-  <li class="Example">
-    <h1 class="Example-title">{{ example.name }}</h1>
-    <ol class="Example-step-list">
-    {% for step in example.steps %}
-      <li class="Example-step ss-{{ step.icon }}">{{ step.text }}</li>
-    {% endfor %}
-    </ol>
-  </li>
-{% endfor %}
-</ul>
-```
-
-The plugins are all reusable. That PDF generator plugin for eBooks? Use it to generate PDFs for each of your blog posts too!
-
-Check out [the code examples](https://github.com/segmentio/metalsmith/tree/master/examples) to get an idea for what's possible.
+Fancy documentation from gitlab docs.
 
 ## License
 
 The MIT License (MIT)
 
-Copyright &copy; 2014, Segment.io \<friends@segment.io\>
-
 Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
 
 The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
diff --git a/examples/technical-documentation/src/install/index.md b/examples/technical-documentation/src/install/index.md
deleted file mode 100644
index cc9dbc0d..00000000
--- a/examples/technical-documentation/src/install/index.md
+++ /dev/null
@@ -1,16 +0,0 @@
----
-autotoc: true
-view: layout.twig
-title: Installation
-collection: Installation
----
-
-# Install it
-
-Metalsmith and its plugins can be installed with npm:
-
-```bash
-$ npm install metalsmith
-```
-
-The package exposes both a [JavaScript API](https://github.com/segmentio/metalsmith#api), and [CLI](https://github.com/segmentio/metalsmith#cli) in case you're used to that type of workflow from other static site generators. To see how they're used check out the [examples](https://github.com/segmentio/metalsmith/tree/master/examples).
diff --git a/examples/technical-documentation/src/plugins/add.md b/examples/technical-documentation/src/plugins/add.md
deleted file mode 100644
index dd913f94..00000000
--- a/examples/technical-documentation/src/plugins/add.md
+++ /dev/null
@@ -1,13 +0,0 @@
----
-title: "The Community Plugins"
-description: "An extremely simple, pluggable static site generator."
-autotoc: true
-view: layout.twig
-collection: "Plugins"
----
-
-# The Community Plugins
-
-The core Metalsmith library doesn't bundle any plugins by default.
-
-If you write your own plugin, submit a pull request to the [metalsmith.io](https://github.com/segmentio/metalsmith.io/tree/master/src/plugins.json) repository and it will show up here!
\ No newline at end of file
diff --git a/examples/technical-documentation/src/plugins/write.md b/examples/technical-documentation/src/plugins/write.md
deleted file mode 100644
index 7d19fc82..00000000
--- a/examples/technical-documentation/src/plugins/write.md
+++ /dev/null
@@ -1,45 +0,0 @@
----
-title: "Writing A Plugin"
-description: "An extremely simple, pluggable static site generator."
-autotoc: true
-view: layout.twig
-collection: "Plugins"
----
-
-# Writing A Plugin
-
-Writing a plugin is not difficult as you have seen above with the `metalsmith-drafts` plugin. In order to achieve more complicated tasks you will most likely find and can use `npm`-packages. Look at how others have done it. Here is an example using `debug` (which we appreciate if you use it) and `multimatch`:
-
-`metalsmith-myplugin`:
-
-```JavaScript
-// we would like you to use debug
-var debug = require('debug')('metalsmith-myplugin');
-var multimatch = require('multimatch');
-
-
-// Expose `plugin`.
-module.exports = plugin;
-
-
-function plugin(opts){
-  opts.pattern = opts.pattern || [];
-
-  return function (files, metalsmith, done){
-
-    setImmediate(done);
-    Object.keys(files).forEach(function(file){
-      if(multimatch(file, opts.pattern).length) {
-        debug('myplugin working on: %s', file);
-
-        //
-        // here would be your code
-        //
-
-      }
-
-    });
-
-  };
-}
-```
diff --git a/examples/technical-documentation/src/started/install.md b/examples/technical-documentation/src/started/install.md
index 3c08beb1..de1375ea 100644
--- a/examples/technical-documentation/src/started/install.md
+++ b/examples/technical-documentation/src/started/install.md
@@ -1,17 +1,14 @@
 ---
 title: "Installation"
-description: "An extremely simple, pluggable static site generator."
 autotoc: true
 view: layout.twig
 collection: "Getting Started"
 ---
 
-# Install it
+# Install
 
-Metalsmith and its plugins can be installed with npm:
+Client and its plugins can be installed with npm:
 
 ```bash
-$ npm install metalsmith
+$ npm install XXXX
 ```
-
-The package exposes both a [JavaScript API](https://github.com/segmentio/metalsmith#api), and [CLI](https://github.com/segmentio/metalsmith#cli) in case you're used to that type of workflow from other static site generators. To see how they're used check out the [examples](https://github.com/segmentio/metalsmith/tree/master/examples).
\ No newline at end of file
diff --git a/examples/technical-documentation/src/started/intro.md b/examples/technical-documentation/src/started/intro.md
deleted file mode 100644
index 9a2ef6a8..00000000
--- a/examples/technical-documentation/src/started/intro.md
+++ /dev/null
@@ -1,36 +0,0 @@
----
-title: "Introduction"
-description: "An extremely simple, pluggable static site generator."
-autotoc: true
-view: layout.twig
-collection: "Getting Started"
----
-
-# Introduction
-
-Metalsmith is an extremely simple, pluggable static site generator. So let us explain why:
-
-## Why is Metalsmith a *pluggable static site generator*?
-
-The task of a static site generator is to produce static build files that can be deployed to a web server. These files are built from source files. Basically for a static site generator this means:
-
-1. from a source directory read the source files and extract their information
-2. manipulate the information
-3. write the manipulated information to files into a destination directory
-
-Metalsmith is built on this reasoning. It takes the information from the source files from a source directory and it writes the manipulated information to files into a destination directory. All manipulations, however, it exclusively leaves to plugins.
-
-Manipulations can be anything: translating templates, transpiling code, replacing variables, wrapping layouts around content, grouping files, moving files and so on. This is why we say *»Everything is a Plugin«*. And of course, several manipulations can be applied one after another. Obviously, in this case the sequence matters.
-
-
-## Why is Metalsmith *extremely simple*?
-
-1. When all manipulations are performed by plugins, the only thing Metalsmith has to do in its core is to provide for an underlying logic of actually how manipulations are dealt with and for a defined interface for the plugins. To achieve this, we only needed around 400 lines of code --- have a [look at the source yourself](https://github.com/metalsmith/metalsmith/blob/master/lib/index.js). We believe this is rather simple.
-
-2. For manipulations Metalsmith uses a very clever, but extremely simple idea. All source files are initially converted into JavaScript objects with the usual **`{property: property value}`** pairs. These **`{property: property value}`** pairs contain information on the original file itself (such as its **`birthtime`** or **`path`**) and on its **`content`**. The JavaScript object for each file is then supplemented with all variables either specified in the front-matter of the file or elsewhere. The manipulations performed by the plugins are now nothing else then modifications applied to the JavaScript objects either by changing the properties or the property values.
-
-3. Breaking down Metalsmith into a core and many plugins has several advantages. It reduces complexity. It gives the user the freedom to use exactly only those plugins he or she needs. Furthermore, it distributes the honor and the burden of maintaining the Metalsmith core and its plugins onto the Metalsmith community. With this approach we hope to keep the Metalsmith environment pretty up-to-date.
-
-4. Writing plugins itself is also rather simple. The plugin-interface is easy to understand and most plugins are also rather short.
-
-5. Every site needs JavaScript anyway. Just like the popular task runners [gulp](http://gulpjs.com/) or [grunt](http://gruntjs.com/) Metalsmith is programmed in JavaScript. So, you do not have to rely on a further language such as Ruby, Python or Go. This also helps to keep your workflow simple.
\ No newline at end of file
diff --git a/examples/technical-documentation/src/started/metadata.md b/examples/technical-documentation/src/started/metadata.md
deleted file mode 100644
index 3376e7ad..00000000
--- a/examples/technical-documentation/src/started/metadata.md
+++ /dev/null
@@ -1,42 +0,0 @@
----
-title: "Metadata & debugging"
-description: "An extremely simple, pluggable static site generator."
-autotoc: true
-view: layout.twig
-collection: "Getting Started"
----
-
-# Metadata & debugging
-
-For Metalsmith we have stated that everything is a plugin. That is true, but in addition the Metalsmith core also provides for a **`metadata()`** function. You can specify arbitrary **`{property: property value}`** pairs and these information will be globally accessible from each plugin.
-
-```JavaScript
-var debug = require('metalsmith-debug');
-
-...
-
-Metalsmith(__dirname)            
-  .source('sourcepath')      
-  .destination('destpath')   
-  .clean(false)
-  .metadata({
-      author: 'John Doe',
-      site: 'http://example.com'
-  })
-  .use(markdown())
-  .use(layouts({
-    engine: 'handlebars'
-  }))
-  .use(debug())             // displays debug info on the console
-  .build(function(err) {         
-    if (err) throw err;
-  });
-```
-
-As you have seen in the code above, we have also introduced a plugin named [**`metalsmith-debug`**](https://github.com/mahnunchik/metalsmith-debug). For this plugin to actually show debug information you need to define an environment variable `DEBUG` and set it to:
-
-```bash
-$ DEBUG=metalsmith:*
-```
-
-The source and destination path, the metadata and all files are then logged to the console.
\ No newline at end of file
diff --git a/examples/technical-documentation/src/started/plugins.md b/examples/technical-documentation/src/started/plugins.md
index e27e2dee..b70543b1 100644
--- a/examples/technical-documentation/src/started/plugins.md
+++ b/examples/technical-documentation/src/started/plugins.md
@@ -1,48 +1,20 @@
 ---
 title: "Plugins"
-description: "An extremely simple, pluggable static site generator."
 autotoc: true
 view: layout.twig
 collection: "Getting Started"
 ---
 
-# Everything is a Plugin - A first example
+# Plugin
 
-All of the logic in Metalsmith is handled by plugins. You simply chain them together. Here's what the simplest blog looks like. It uses only two plugins, **`markdown()`** and **`layouts()`**...
+All of the logic in the Client is handled by plugins. You simply chain them together.
 
 ```js
-Metalsmith(__dirname)          // instantiate Metalsmith in the cwd
-  .source('sourcepath')        // specify source directory
-  .destination('destpath')     // specify destination directory
-  .use(markdown())             // transpile markdown into html
-  .use(layouts({               // wrap a handlebars-layout
-    engine: 'handlebars'       // around transpiled html-files
-  }))    
-  .build(function(err) {       // this is the actual build process
-    if (err) throw err;    // throwing errors is required
-  });
-```
-
-
-... and by the way, if you do not want your destination directory to be cleaned before a new build, just add <b>`.clean(false)`</b>. But what if you want to get fancier by hiding your unfinished drafts and using permalinks? Just add plugins...
-
-```js
-Metalsmith(__dirname)
-  .source('sourcepath')      
-  .destination('destpath')
-  .clean(false)                  // do not clean destination
-                                 // directory before new build   
-  .use(drafts())                 // only files that are NOT drafts
-  .use(markdown())
-  .use(permalinks())             // make a permalink output path
-  .use(layouts({
-    engine: 'handlebars'
+Client()
+  .use(ssh({
+    port: '22'
   }))
-  .build(function(err) {    
-    if (err) throw err;
-  });
+  .connect('/var/socket')
 ```
 
 ...it's as easy as that!
-
-A small comment. Instead of [Handlebars](http://handlebarsjs.com/) you can also use other templating languages such as [Jade/Pug](http://jade-lang.com/).
diff --git a/examples/technical-documentation/src/started/trouble.md b/examples/technical-documentation/src/started/trouble.md
index f60907f5..47ffd21a 100644
--- a/examples/technical-documentation/src/started/trouble.md
+++ b/examples/technical-documentation/src/started/trouble.md
@@ -1,6 +1,5 @@
 ---
 title: "Troubleshooting"
-description: "An extremely simple, pluggable static site generator."
 autotoc: true
 view: layout.twig
 collection: "Getting Started"
@@ -9,19 +8,8 @@ collection: "Getting Started"
 # Troubleshooting
 
 ## Node Version Requirements
-Metalsmith v2.0 and above uses [generators](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Generator) which has some considerations for `node.js 0.12.x` and below.
+Client v2.0 and above uses `node.js 0.12.x` and below.
 
 ### Using node.js 0.10.x
-You have two options:
 
-1. Upgrade to latest stable version of `node.js` (>= `0.12.x` — see "*Using `node.js 0.12.x`*" section below)
-2. Use Metalsmith v1.7. Put `"metalsmith": "^1.7.0"` in your `package.json` and `npm install` that version.
-
-### Using node.js 0.12.x
-You have three options:
-
-1. Run `node.js` with `--harmony_generators` flag set.
-    1. `node --harmony_generators my_script.js`
-    2. Using `package.json`: `"scripts": {"start": "node --harmony_generators my_script.js"}`. Run with `npm run`
-2. `npm install` [harmonize](https://www.npmjs.com/package/harmonize) and require before Metalsmith is used. e.g. `require("harmonize")(["harmony-generators"]);`
-3. Use Metalsmith v1.7. Put `"metalsmith": "^1.7.0"` in your `package.json` and `npm install` that version.
\ No newline at end of file
+Upgrade to latest stable version of `node.js` (>= `0.12.x` — see "*Using `node.js 0.12.x`*" section below)
