From d55b750abcd04a5dfc71890835f36c9df55495b9 Mon Sep 17 00:00:00 2001
From: kahboom <rachelyordan@gmail.com>
Date: Wed, 24 Oct 2018 15:19:07 +0100
Subject: [PATCH 01/42] Rebuilding

---
 static/images/favicon-02.png                  | Bin 1218 -> 1217 bytes
 static/images/favicon.png                     | Bin 1024 -> 1023 bytes
 static/images/grant.png                       | Bin 58918 -> 58915 bytes
 static/images/landing_page.png                | Bin 51698 -> 51695 bytes
 static/images/login.png                       | Bin 23760 -> 23759 bytes
 static/images/orig/grant.png                  | Bin 68813 -> 68811 bytes
 static/images/orig/landing_page.png           | Bin 99759 -> 99758 bytes
 static/images/orig/login.png                  | Bin 23760 -> 23759 bytes
 static/images/orig/security_exception.png     | Bin 81924 -> 81922 bytes
 static/images/red-hat-02.png                  | Bin 5391 -> 5390 bytes
 static/images/screenshot-dashboard.png        | Bin 41848 -> 41847 bytes
 static/images/screenshot-integration-list.png | Bin 38737 -> 38736 bytes
 static/images/security_exception.png          | Bin 76992 -> 76990 bytes
 static/images/zenhub-columns.png              | Bin 167067 -> 167064 bytes
 14 files changed, 0 insertions(+), 0 deletions(-)

diff --git a/static/images/favicon-02.png b/static/images/favicon-02.png
index 7aec1194d317f187e30437d8a50fe27c88db5314..f1ecade669739691a590458c143dbb87c87b0d78 100644
GIT binary patch
delta 13
UcmX@ad61K(Gr-S%BkNuk03jR%e*gdg

delta 14
VcmX@ed5Dv>Gr-TCcO%PQ762q_1dIRx

diff --git a/static/images/favicon.png b/static/images/favicon.png
index ebff58a1c4c2e7c0e196bcb2ecb7754975a63f65..748fa226a31122b5296d44cac566bf46232454df 100644
GIT binary patch
delta 13
UcmZqR_|MML8Q|x>k@Yt-03gQ%wEzGB

delta 14
Vcmey*-oU}y8Q|y6yOHHLGXNzF1i}CS

diff --git a/static/images/grant.png b/static/images/grant.png
index 5f8dd64c2212c93492b6209e8c32a93c8c63d7df..e7afdeacdd8081511a9a1d4a97af272d60e46132 100644
GIT binary patch
delta 24
gcmZ2>hI#QBW|qzXKlhESI-55eZ9Xf%>9U$I0DylAF#rGn

delta 30
lcmZ2{hI!c;X4cLCKX=}ZEIOMRc{dwuJ}VET{$5fO1^}?53snFB

diff --git a/static/images/landing_page.png b/static/images/landing_page.png
index 1aa76794cf6ea561d283a42756288853f907162b..4641a3b53d29c236e5e0b1ec633e6ddb94c9f891 100644
GIT binary patch
delta 25
hcmew~nfd)>W|qzXKlhESKN&awXJj+k%x3mxG60N?3X1>$

delta 30
lcmaDqnfcRXX4cLCKX=}ZEI%0;c{l%MWHSL$%w}&U0|2jv3a<bF

diff --git a/static/images/login.png b/static/images/login.png
index ff03c1bd644a194fb7d1ee096cbb7dfd7548d939..fffaa63cc3f93979b1b35cb280feee3b4b5f5f6c 100644
GIT binary patch
delta 15
WcmcbxlkxmcMwZS1KlhESr(*y%vj$@T

delta 16
XcmX@Vlkvh%M%K;%KX=}ZET>}tJAMXm

diff --git a/static/images/orig/grant.png b/static/images/orig/grant.png
index 57cb8a5c6c9533942c9ec45deffb3bce4a478802..a3c8db2e8e34d3a99ca22f040f7983b651758f2c 100644
GIT binary patch
delta 20
ccmX>*ljZbG7M9KcKlhESPenGr7J2j?09#E7e*gdg

delta 23
fcmX>-ljZD87S_%HKX=}ZEKfxkc{jfldGs9sY-9<T

diff --git a/static/images/orig/landing_page.png b/static/images/orig/landing_page.png
index eaf7adfc6c581c2a158e7abfff1485965850d270..5ac76d259eb12ce3042a77215f2bc2d4d25b8b34 100644
GIT binary patch
delta 18
ZcmZ4A&9<(ajiocd&%Kd#D=XuwRscU-24VmJ

delta 19
acmZ42&9=UqjkPnt&z-lCWh)Egs#X9)wgzqh

diff --git a/static/images/orig/login.png b/static/images/orig/login.png
index ff03c1bd644a194fb7d1ee096cbb7dfd7548d939..fffaa63cc3f93979b1b35cb280feee3b4b5f5f6c 100644
GIT binary patch
delta 15
WcmcbxlkxmcMwZS1KlhESr(*y%vj$@T

delta 16
XcmX@Vlkvh%M%K;%KX=}ZET>}tJAMXm

diff --git a/static/images/orig/security_exception.png b/static/images/orig/security_exception.png
index a4c0c665cce8a928e8960f69284a1820f2ad960e..8912f9d17f976c6cb53b22599a237c40e87fd518 100644
GIT binary patch
delta 20
bcmZo^U~Ot(W$6s?bKl6ylCzmB=htNbM(+oo

delta 23
ecmZo_U~Oq&W$g^`bLZX2!ji+tyO|^B*JS`yt_QdP

diff --git a/static/images/red-hat-02.png b/static/images/red-hat-02.png
index 234fa416d30af7c84d5187e3e371ef28f5e85e1a..62ea0c9b33da552d6dd608b81bd9768cf6010855 100644
GIT binary patch
delta 13
UcmeCz>eFKB4DfT`$jT)O03Fo>xc~qF

delta 14
VcmeCv>epiJ4DfU3-N?cv3IHJg1I7RV

diff --git a/static/images/screenshot-dashboard.png b/static/images/screenshot-dashboard.png
index fd03a26e33a89e51488802b8ea8cb27065cf4955..bc30779986b3d03b816af61e5861cfb4a2349922 100644
GIT binary patch
delta 15
WcmexyjOqI^CYH_sKlhES#ft$u-Uhw^

delta 16
Xcmex<jOoWQCf3dXKX=}ZEX9ifK@|qe

diff --git a/static/images/screenshot-integration-list.png b/static/images/screenshot-integration-list.png
index bc4d9ef49f8d54f5340c25cda719f44d0f551b9a..f52748ea7d45398a63fc4e77d41cdf2b4ee43f44 100644
GIT binary patch
delta 15
Wcmcb(j_JZWCYH_sKlhESKGOj;4+aeY

delta 16
Xcmcbxj_Kk$Cf3dXKX=}ZEI!i#ImiYY

diff --git a/static/images/security_exception.png b/static/images/security_exception.png
index c9aea0393cc3d121c26cc3b94f77587e0268b0e4..f29b7533e99e83532b4b93d6eba0980db54a45ef 100644
GIT binary patch
delta 20
ccmX?blV#sc7M9KcKlhESF*i0R-G~bT0AYd&Gynhq

delta 23
fcmdmYljXoo7S_%HKX=}ZEHO72c{eBAhzkJ#bU_JC

diff --git a/static/images/zenhub-columns.png b/static/images/zenhub-columns.png
index 02b6c4f3b5831a16f592a7211d6b8ed2c025d092..0ff41c2d71126d580bda1eb6761b663c47185aa7 100644
GIT binary patch
delta 33
pcmbO|lWWFIE|$&!Klet~R#wKXtW2}HwlCyjTCKU=*M!M00sy*73U&Yh

delta 38
scmbO+lWX=&F4oQfKX=|nmR1(Vtt?Elxfpr3&*x%VtqG*POql#40Nz~+m;e9(


From d6968ba7bec2e2b2f4ebd187adbab44241586200 Mon Sep 17 00:00:00 2001
From: kahboom <rachelyordan@gmail.com>
Date: Mon, 12 Nov 2018 11:55:43 +0000
Subject: [PATCH 02/42] Set up dirs for Dev Handbook

---
 content/docs/_index.md             | 4 ++--
 content/docs/cli/_index.md         | 8 ++++++++
 content/docs/development/_index.md | 8 ++++++++
 3 files changed, 18 insertions(+), 2 deletions(-)
 create mode 100644 content/docs/cli/_index.md
 create mode 100644 content/docs/development/_index.md

diff --git a/content/docs/_index.md b/content/docs/_index.md
index 940539bf..81d7af5c 100644
--- a/content/docs/_index.md
+++ b/content/docs/_index.md
@@ -1,8 +1,8 @@
 ---
 draft: false
-title: "Docs"
+title: "Developer Handbook"
 description: "Documentation and guides for using and/or contributing to the Syndesis project."
 sidebar: "sidenav"
 ---
 
-Here you will find documentation and guides for using and/or contributing to the Syndesis project.
+This handbook contain all information required for installing, running and developing Syndesis from a developer's point of view.
diff --git a/content/docs/cli/_index.md b/content/docs/cli/_index.md
new file mode 100644
index 00000000..da63e3ce
--- /dev/null
+++ b/content/docs/cli/_index.md
@@ -0,0 +1,8 @@
+---
+draft: false
+title: "CLI"
+description: "CLI test."
+sidebar: "sidenav"
+---
+
+CLI stuff
\ No newline at end of file
diff --git a/content/docs/development/_index.md b/content/docs/development/_index.md
new file mode 100644
index 00000000..ffcb596b
--- /dev/null
+++ b/content/docs/development/_index.md
@@ -0,0 +1,8 @@
+---
+draft: false
+title: "Development"
+description: "Development test."
+sidebar: "sidenav"
+---
+
+Development stuff.

From c2821d55bc0f89f5920f70b1230fa99b5cfc871f Mon Sep 17 00:00:00 2001
From: kahboom <rachelyordan@gmail.com>
Date: Mon, 12 Nov 2018 11:57:17 +0000
Subject: [PATCH 03/42] Move to individual files, not directories

---
 content/docs/{cli/_index.md => cli.md}                 | 0
 content/docs/{development/_index.md => development.md} | 0
 2 files changed, 0 insertions(+), 0 deletions(-)
 rename content/docs/{cli/_index.md => cli.md} (100%)
 rename content/docs/{development/_index.md => development.md} (100%)

diff --git a/content/docs/cli/_index.md b/content/docs/cli.md
similarity index 100%
rename from content/docs/cli/_index.md
rename to content/docs/cli.md
diff --git a/content/docs/development/_index.md b/content/docs/development.md
similarity index 100%
rename from content/docs/development/_index.md
rename to content/docs/development.md

From 8231da65484da3631c277f5b9a5279e808276c82 Mon Sep 17 00:00:00 2001
From: kahboom <rachelyordan@gmail.com>
Date: Mon, 12 Nov 2018 12:07:15 +0000
Subject: [PATCH 04/42] Add sidebar and top nav for docs

---
 content/docs/_index.md      | 11 ++++++++++-
 content/docs/cli.md         |  7 +++++++
 content/docs/development.md |  7 +++++++
 3 files changed, 24 insertions(+), 1 deletion(-)

diff --git a/content/docs/_index.md b/content/docs/_index.md
index 81d7af5c..31a9dd1e 100644
--- a/content/docs/_index.md
+++ b/content/docs/_index.md
@@ -1,8 +1,17 @@
 ---
 draft: false
-title: "Developer Handbook"
+title: "Developer Docs"
 description: "Documentation and guides for using and/or contributing to the Syndesis project."
 sidebar: "sidenav"
+
+menu:
+  sidenav:
+    name: "Docs"
+    pre: "<i class='fa fa-fw fa-group'></i>"
+    weight: -180
+  topnav:
+    name: "docs"
+    weight: -120
 ---
 
 This handbook contain all information required for installing, running and developing Syndesis from a developer's point of view.
diff --git a/content/docs/cli.md b/content/docs/cli.md
index da63e3ce..075127e4 100644
--- a/content/docs/cli.md
+++ b/content/docs/cli.md
@@ -3,6 +3,13 @@ draft: false
 title: "CLI"
 description: "CLI test."
 sidebar: "sidenav"
+menu:
+  sidenav:
+    name: CLI
+    weight: -400
+    parent: Docs
+toc: true
+weight: 10
 ---
 
 CLI stuff
\ No newline at end of file
diff --git a/content/docs/development.md b/content/docs/development.md
index ffcb596b..11081b05 100644
--- a/content/docs/development.md
+++ b/content/docs/development.md
@@ -3,6 +3,13 @@ draft: false
 title: "Development"
 description: "Development test."
 sidebar: "sidenav"
+menu:
+  sidenav:
+    name: Development
+    weight: -400
+    parent: Docs
+toc: true
+weight: 20
 ---
 
 Development stuff.

From add6bd309d52a3a9c93a1778cbc0a4a3d68271d8 Mon Sep 17 00:00:00 2001
From: kahboom <rachelyordan@gmail.com>
Date: Mon, 12 Nov 2018 12:09:53 +0000
Subject: [PATCH 05/42] Rename from Docs to Developer Docs, for clarity

---
 content/docs/_index.md      | 2 +-
 content/docs/cli.md         | 2 +-
 content/docs/development.md | 2 +-
 3 files changed, 3 insertions(+), 3 deletions(-)

diff --git a/content/docs/_index.md b/content/docs/_index.md
index 31a9dd1e..8c66f46f 100644
--- a/content/docs/_index.md
+++ b/content/docs/_index.md
@@ -6,7 +6,7 @@ sidebar: "sidenav"
 
 menu:
   sidenav:
-    name: "Docs"
+    name: "Developer Docs"
     pre: "<i class='fa fa-fw fa-group'></i>"
     weight: -180
   topnav:
diff --git a/content/docs/cli.md b/content/docs/cli.md
index 075127e4..864b4cf4 100644
--- a/content/docs/cli.md
+++ b/content/docs/cli.md
@@ -7,7 +7,7 @@ menu:
   sidenav:
     name: CLI
     weight: -400
-    parent: Docs
+    parent: Developer Docs
 toc: true
 weight: 10
 ---
diff --git a/content/docs/development.md b/content/docs/development.md
index 11081b05..9016a28f 100644
--- a/content/docs/development.md
+++ b/content/docs/development.md
@@ -7,7 +7,7 @@ menu:
   sidenav:
     name: Development
     weight: -400
-    parent: Docs
+    parent: Developer Docs
 toc: true
 weight: 20
 ---

From 792d4ec9f66bc3e3be5b393077f619c77136d6f6 Mon Sep 17 00:00:00 2001
From: kahboom <rachelyordan@gmail.com>
Date: Mon, 12 Nov 2018 16:11:23 +0000
Subject: [PATCH 06/42] Update to use proper archetype and SCSS specifically
 for docs

---
 content/docs/_index.md                        |   1 +
 content/docs/cli.md                           | 185 +++++++++++++++++-
 .../layouts/docs/{list.html => single.html}   |   6 +-
 themes/syndesis/scss/_blog.scss               |   3 +-
 themes/syndesis/scss/_docs.scss               |  11 ++
 themes/syndesis/scss/_sidenav.scss            |   2 +-
 6 files changed, 201 insertions(+), 7 deletions(-)
 rename themes/syndesis/layouts/docs/{list.html => single.html} (80%)

diff --git a/content/docs/_index.md b/content/docs/_index.md
index 8c66f46f..dbb47a7c 100644
--- a/content/docs/_index.md
+++ b/content/docs/_index.md
@@ -3,6 +3,7 @@ draft: false
 title: "Developer Docs"
 description: "Documentation and guides for using and/or contributing to the Syndesis project."
 sidebar: "sidenav"
+kind: doc
 
 menu:
   sidenav:
diff --git a/content/docs/cli.md b/content/docs/cli.md
index 864b4cf4..eca08cac 100644
--- a/content/docs/cli.md
+++ b/content/docs/cli.md
@@ -12,4 +12,187 @@ toc: true
 weight: 10
 ---
 
-CLI stuff
\ No newline at end of file
+
+# Buildtool "syndesis"
+
+Syndesis uses a single tool for controlling various aspects of the build and developer related tasks.
+This script can be found in `$SYNDESIS_DIR/tools/bin` and is called `syndesis`.
+It requires bash and can be used on any Unix or macOS.
+
+To have this script handy all the time it is recommended to either put this `bin/` directory into the path or add a symlink from `syndesis` into a directory which is already on your execution path.
+
+The script can be used for various tasks which are selected by a so-called command_ which is the first argument to the script.
+
+Just type `syndesis -h` to get an overview of the commands available:
+
+_Usage message_
+```
+Usage: syndesis <command> [... options ...]
+
+with the following commands
+
+   build            Build Syndesis
+   dev              Developer tools
+   doc              Generate Syndesis Developer Handbook (SDH)
+   minishift        Initialize and manage a Minishift developer environment
+   system-test      Run system tests
+
+"build" is the default command if no command is specified.
+```
+
+
+There are a handful of global options which can be used:
+
+<table>
+<thead>
+<tr>
+<th>Testing</th>
+<th>Two</th>
+<th>Three</th>
+</tr>
+</thead>
+
+<tbody>
+<tr>
+<td><code>--help</code></td>
+<td>right-aligned</td>
+<td>$1600</td>
+</tr>
+
+<tr>
+<td><code>--rebase</code></td>
+<td>centered</td>
+<td>$12</td>
+</tr>
+
+<tr>
+<td><code>--verbose</code></td>
+<td>are neat</td>
+<td>$1</td>
+</tr>
+</tbody>
+</table>
+
+| Tables        | Are           | Cool  |
+| ------------- |:-------------:| -----:|
+| `--help`      | right-aligned | $1600 |
+| `--rebase`      | centered      |   $12 |
+| `--verbose` | are neat      |    $1 |
+
+|===
+| `--help`
+| `-h`
+| Print usage information. If a command is given print out commands specific options
+
+| `--rebase`
+| `-r`
+| Rebase your project directory before building to integrate upstream changes to your local repository. See <<syndesis-rebase,below>> for details how this works.
+
+| `--verbose`
+|
+| Set verbose mode, which is useful mostly only for debugging the script itself.
+|===
+
+Rebase to upstream
+To easily rebase on changes which have been merged upstream to master, you can use the option `--rebase` (short: `-r`).
+This command assumes that you have forked the Syndesis GitHub repositories and you have "origin" and "upstream" remotes like
+
+```
+$ git remote -v
+origin    git@github.com:rhuss/syndesis.git (fetch)
+origin    git@github.com:rhuss/syndesis.git (push)
+upstream  https://github.com/syndesisio/syndesis (fetch)
+upstream  https://github.com/syndesisio/syndesis (push)
+```
+
+With this in place, a `--rebase` performs the following steps:
+
+* Refresh upstream remote: `git fetch upstream master`
+* Try a `git rebase upstream/master` which rebases your current local working branch.
+* If this fails because you have uncommitted work:
+  - A `git stash` is performed
+  - The rebase is retried and should succeed
+  - `git stash pop` brings back your changes. Stashing can fail with conflicts which you would have to resolve on your own.
+
+Development Modes
+
+The Syndesis application consists of a set of Docker images OpenShift resources descriptors for installing Syndesis.
+For development, https://www.openshift.org/minishift/[minishift] is used, and most of the commands assume that you have minishift installed locally and executable directly from your path.
+Minishift can be downloaded and installed from https://github.com/minishift/minishift/releases
+
+For development OpenShift S2I builds and image streams are used.
+This mode works also when running with a real OpenShift cluster and is not restricted to Minishift usage.
+The advantage is that a build automatically triggers a redeployment, so you don't have to kill any pods manually.
+
+Commands
+All other options are specific to each command.
+You get a list of those options with `syndesis <cmd> -h`.
+These options are described in detail in the next sections.
+
+The following commands are available:
+
+[cols="3,15",options="header"]
+|===
+| Command
+| Description
+
+| <<syndesis-build,**build**>>
+| Used for building Syndesis and its various modules.
+
+| <<syndesis-ui,**ui**>>
+| Start the UI for local development _(not implemented yet)_
+
+| <<syndesis-minishift,**minishift**>>
+| Start and install Syndesis on Minishift
+
+| <<syndesis-install,**install**>>
+| Install Syndesis in a running cluster (other than Minishift)
+
+| <<syndesis-system-test,**system-test**>>
+| Run System test against an OpenShift cluster
+
+| <<syndesis-dev,**dev**>>
+| Utility commands useful during development
+
+| <<syndesis-doc,**doc**>>
+| Generating and publish this documentation
+
+| <<syndesis-doc,**release**>>
+| Release Syndesis' Maven and NPM artefacts _(not implemented yet)_
+|===
+
+If no command is given, `build` is the default.
+Remember a command must be the first argument, but there are additional possibilities to specify commands:
+
+* You can use the form `--command` anywhere as an option, too. E.g. using  `--minishift` is the same as specifying "minishift" as the first argument.
+* A `--mode command` can be used, too (e.g. `--mode sytem-test`)
+
+The next sections describe the commands in detail.
+To add a new command, just drop a script file into `$SYNDESIS_DIR/tools/bin/commands` directory with following structure:
+
+```
+#!/bin/bash
+
+yourscriptname::description() {
+    echo "Describe the command"
+}
+
+yourscriptname::usage() {
+    cat <<EOT
+    Describe the usage of the command
+EOT
+}
+
+yourscriptname::run() {
+    Do your stuff
+}
+```
+
+include::cmd_build.adoc[]
+include::cmd_ui.adoc[]
+include::cmd_minishift.adoc[]
+include::cmd_system_test.adoc[]
+include::cmd_dev.adoc[]
+include::cmd_doc.adoc[]
+include::cmd_release.adoc[]
+include::cmd_install.adoc[]
diff --git a/themes/syndesis/layouts/docs/list.html b/themes/syndesis/layouts/docs/single.html
similarity index 80%
rename from themes/syndesis/layouts/docs/list.html
rename to themes/syndesis/layouts/docs/single.html
index e0fba605..a48677f8 100644
--- a/themes/syndesis/layouts/docs/list.html
+++ b/themes/syndesis/layouts/docs/single.html
@@ -1,6 +1,6 @@
 {{ define "main"}}
 <div itemscope
-    class="article">
+    class="doc">
   {{ template "_internal/schema.html" .}}
   <div class="hero">
     <h1 itemprop="headline">{{.Title}}</h1>
@@ -8,8 +8,8 @@ <h1 itemprop="headline">{{.Title}}</h1>
     <blockquote itemprop="description">{{ .Description }}</blockquote>
     {{ end }}
   </div>
-  <div itemprop="articleBody"
-      class="articleBody">
+  <div itemprop="docBody"
+      class="docBody">
     {{ .Content | safeHTML }}
   </div>
 </div>
diff --git a/themes/syndesis/scss/_blog.scss b/themes/syndesis/scss/_blog.scss
index 7776fc77..dabb197e 100644
--- a/themes/syndesis/scss/_blog.scss
+++ b/themes/syndesis/scss/_blog.scss
@@ -1,4 +1,4 @@
-@import 'colors';
+@import "colors";
 
 ////////////////////////////////////////////////////////////////////////////////
 // BLOG
@@ -36,4 +36,3 @@
     }
   }
 }
-
diff --git a/themes/syndesis/scss/_docs.scss b/themes/syndesis/scss/_docs.scss
index c7c75e5a..78a367b9 100644
--- a/themes/syndesis/scss/_docs.scss
+++ b/themes/syndesis/scss/_docs.scss
@@ -4,3 +4,14 @@
 
 @import 'colors';
 @import 'navbar';
+
+.docs {
+    table {
+        display: table;
+        empty-cells: hide;
+        overflow: auto;
+        width: 100%;
+      }
+}
+
+
diff --git a/themes/syndesis/scss/_sidenav.scss b/themes/syndesis/scss/_sidenav.scss
index 55f8ed4b..c777cb49 100644
--- a/themes/syndesis/scss/_sidenav.scss
+++ b/themes/syndesis/scss/_sidenav.scss
@@ -68,7 +68,7 @@
 ul.sidebar-menu {
   padding: 0;
   margin: -2px 0 0;
-  background-color: #eeeeee;
+  //background-color: #eeeeee;
 
   li {
 

From 92e6ba7fec67a11f00a18fcefa770c1ed38115f7 Mon Sep 17 00:00:00 2001
From: kahboom <rachelyordan@gmail.com>
Date: Mon, 12 Nov 2018 16:27:26 +0000
Subject: [PATCH 07/42] fix #63 table styling

---
 content/docs/cli.md                | 32 +--------------------
 themes/syndesis/scss/_docs.scss    | 12 ++------
 themes/syndesis/scss/syndesis.scss | 45 ++++++++++++++++++++++++++++++
 3 files changed, 48 insertions(+), 41 deletions(-)

diff --git a/content/docs/cli.md b/content/docs/cli.md
index eca08cac..6a7d788e 100644
--- a/content/docs/cli.md
+++ b/content/docs/cli.md
@@ -43,38 +43,8 @@ with the following commands
 
 There are a handful of global options which can be used:
 
-<table>
-<thead>
-<tr>
-<th>Testing</th>
-<th>Two</th>
-<th>Three</th>
-</tr>
-</thead>
-
-<tbody>
-<tr>
-<td><code>--help</code></td>
-<td>right-aligned</td>
-<td>$1600</td>
-</tr>
-
-<tr>
-<td><code>--rebase</code></td>
-<td>centered</td>
-<td>$12</td>
-</tr>
-
-<tr>
-<td><code>--verbose</code></td>
-<td>are neat</td>
-<td>$1</td>
-</tr>
-</tbody>
-</table>
-
 | Tables        | Are           | Cool  |
-| ------------- |:-------------:| -----:|
+| ------------- |-------------| -----|
 | `--help`      | right-aligned | $1600 |
 | `--rebase`      | centered      |   $12 |
 | `--verbose` | are neat      |    $1 |
diff --git a/themes/syndesis/scss/_docs.scss b/themes/syndesis/scss/_docs.scss
index 78a367b9..7f93d999 100644
--- a/themes/syndesis/scss/_docs.scss
+++ b/themes/syndesis/scss/_docs.scss
@@ -2,16 +2,8 @@
 // DOCS
 ////////////////////////////////////////////////////////////////////////////////
 
-@import 'colors';
-@import 'navbar';
+@import "colors";
+@import "navbar";
 
 .docs {
-    table {
-        display: table;
-        empty-cells: hide;
-        overflow: auto;
-        width: 100%;
-      }
 }
-
-
diff --git a/themes/syndesis/scss/syndesis.scss b/themes/syndesis/scss/syndesis.scss
index fe23b81c..187c8784 100644
--- a/themes/syndesis/scss/syndesis.scss
+++ b/themes/syndesis/scss/syndesis.scss
@@ -40,6 +40,51 @@ html, body {
       width: calc(100% - 214px - 314px);
     }
   }
+
+  table {
+    display: block;
+    //display: table;
+    border-collapse: collapse;
+    //border-collapse: separate;
+    border-color: grey;
+    border-spacing: 2px;
+    empty-cells: hide;
+    line-height: 1.5;
+    overflow: auto;
+    width: 100%;
+
+    thead {
+      display: table-header-group;
+      vertical-align: middle;
+      border-color: inherit;
+    }
+
+    tbody {
+      display: table-row-group;
+      vertical-align: middle;
+      border-color: inherit;
+    }
+
+    th {
+      font-weight: 600;
+    }
+
+    tr {
+      background-color: #fff;
+      border-top: 1px solid #c6cbd1;
+      display: table-row;
+    }
+
+    tr:nth-child(2n) {
+      background-color: #f6f8fa;
+    }
+
+    td,
+    th {
+      border: 1px solid #dfe2e5;
+      padding: 6px 13px;
+    }
+  }
 }
 
 :target::before {

From db35090d3ee76568e863fd8fd6811bd43874a5a6 Mon Sep 17 00:00:00 2001
From: kahboom <rachelyordan@gmail.com>
Date: Mon, 12 Nov 2018 16:30:19 +0000
Subject: [PATCH 08/42] Make tables adjust to full width of screen

---
 themes/syndesis/scss/syndesis.scss | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/themes/syndesis/scss/syndesis.scss b/themes/syndesis/scss/syndesis.scss
index 187c8784..325ef225 100644
--- a/themes/syndesis/scss/syndesis.scss
+++ b/themes/syndesis/scss/syndesis.scss
@@ -42,8 +42,8 @@ html, body {
   }
 
   table {
-    display: block;
-    //display: table;
+    //display: block;
+    display: table;
     border-collapse: collapse;
     //border-collapse: separate;
     border-color: grey;

From 505eb834d0949e33aada0d44a3c92581c95e1540 Mon Sep 17 00:00:00 2001
From: kahboom <rachelyordan@gmail.com>
Date: Mon, 12 Nov 2018 16:41:10 +0000
Subject: [PATCH 09/42] Fix issue where empty table headers are not hidden

---
 content/docs/cli.md                |  2 +-
 themes/syndesis/scss/syndesis.scss | 48 +++++++++++++++++++-----------
 2 files changed, 32 insertions(+), 18 deletions(-)

diff --git a/content/docs/cli.md b/content/docs/cli.md
index 6a7d788e..c51868e1 100644
--- a/content/docs/cli.md
+++ b/content/docs/cli.md
@@ -43,7 +43,7 @@ with the following commands
 
 There are a handful of global options which can be used:
 
-| Tables        | Are           | Cool  |
+||||
 | ------------- |-------------| -----|
 | `--help`      | right-aligned | $1600 |
 | `--rebase`      | centered      |   $12 |
diff --git a/themes/syndesis/scss/syndesis.scss b/themes/syndesis/scss/syndesis.scss
index 325ef225..e114172b 100644
--- a/themes/syndesis/scss/syndesis.scss
+++ b/themes/syndesis/scss/syndesis.scss
@@ -1,19 +1,20 @@
-@import './bootstrap/_variables';
-@import '../../../node_modules/bootstrap/scss/bootstrap';
-
-@import 'blog';
-@import 'colors';
-@import 'docs';
-@import 'footer';
-@import 'github-corner';
-@import 'home';
-@import 'icons';
-@import 'navbar';
-@import 'sidenav';
-@import 'toc';
-@import 'highlighting';
-
-html, body {
+@import "./bootstrap/_variables";
+@import "../../../node_modules/bootstrap/scss/bootstrap";
+
+@import "blog";
+@import "colors";
+@import "docs";
+@import "footer";
+@import "github-corner";
+@import "home";
+@import "icons";
+@import "navbar";
+@import "sidenav";
+@import "toc";
+@import "highlighting";
+
+html,
+body {
   height: 100%;
   width: 100%;
 }
@@ -57,6 +58,12 @@ html, body {
       display: table-header-group;
       vertical-align: middle;
       border-color: inherit;
+
+      th, tr {
+        :empty {
+          display: none;
+        }
+      }
     }
 
     tbody {
@@ -66,10 +73,18 @@ html, body {
     }
 
     th {
+      :empty {
+        display: none;
+      }
+
       font-weight: 600;
     }
 
     tr {
+      :empty {
+        display: none;
+      }
+
       background-color: #fff;
       border-top: 1px solid #c6cbd1;
       display: table-row;
@@ -94,4 +109,3 @@ html, body {
   height: 100px;
   visibility: hidden;
 }
-

From f6f8d21de926ed51431c15a5748f672c38125783 Mon Sep 17 00:00:00 2001
From: kahboom <rachelyordan@gmail.com>
Date: Mon, 12 Nov 2018 16:45:40 +0000
Subject: [PATCH 10/42] Update table content

---
 content/docs/cli.md | 22 +++++-----------------
 1 file changed, 5 insertions(+), 17 deletions(-)

diff --git a/content/docs/cli.md b/content/docs/cli.md
index c51868e1..d6f6137c 100644
--- a/content/docs/cli.md
+++ b/content/docs/cli.md
@@ -44,26 +44,14 @@ with the following commands
 There are a handful of global options which can be used:
 
 ||||
-| ------------- |-------------| -----|
-| `--help`      | right-aligned | $1600 |
-| `--rebase`      | centered      |   $12 |
-| `--verbose` | are neat      |    $1 |
+| ------------- |--------| ------|
+| `--help`      | `-h`   | Print usage information. If a command is given print out commands specific options. |
+| `--rebase`    | `-r`   | Rebase your project directory before building to integrate upstream changes to your local repository. See below for details how this works. |
+| `--verbose`   | &nbsp; | Set verbose mode, which is useful mostly only for debugging the script itself. |
 
-|===
-| `--help`
-| `-h`
-| Print usage information. If a command is given print out commands specific options
-
-| `--rebase`
-| `-r`
-| Rebase your project directory before building to integrate upstream changes to your local repository. See <<syndesis-rebase,below>> for details how this works.
 
-| `--verbose`
-|
-| Set verbose mode, which is useful mostly only for debugging the script itself.
-|===
+_Rebase to upstream_
 
-Rebase to upstream
 To easily rebase on changes which have been merged upstream to master, you can use the option `--rebase` (short: `-r`).
 This command assumes that you have forked the Syndesis GitHub repositories and you have "origin" and "upstream" remotes like
 

From fd7b4957fa52ab424e80e75cbdd13fe88021b93e Mon Sep 17 00:00:00 2001
From: kahboom <rachelyordan@gmail.com>
Date: Tue, 13 Nov 2018 11:48:12 +0000
Subject: [PATCH 11/42] Icon adj

---
 content/docs/_index.md             |  2 +-
 content/docs/cli.md                | 23 +++++++++++++----------
 themes/syndesis/scss/syndesis.scss |  1 +
 3 files changed, 15 insertions(+), 11 deletions(-)

diff --git a/content/docs/_index.md b/content/docs/_index.md
index dbb47a7c..e3e3b6bd 100644
--- a/content/docs/_index.md
+++ b/content/docs/_index.md
@@ -8,7 +8,7 @@ kind: doc
 menu:
   sidenav:
     name: "Developer Docs"
-    pre: "<i class='fa fa-fw fa-group'></i>"
+    pre: "<i class='fa fa-fw fa-book'></i>"
     weight: -180
   topnav:
     name: "docs"
diff --git a/content/docs/cli.md b/content/docs/cli.md
index d6f6137c..9f25277b 100644
--- a/content/docs/cli.md
+++ b/content/docs/cli.md
@@ -72,7 +72,7 @@ With this in place, a `--rebase` performs the following steps:
   - The rebase is retried and should succeed
   - `git stash pop` brings back your changes. Stashing can fail with conflicts which you would have to resolve on your own.
 
-Development Modes
+_Development Modes_
 
 The Syndesis application consists of a set of Docker images OpenShift resources descriptors for installing Syndesis.
 For development, https://www.openshift.org/minishift/[minishift] is used, and most of the commands assume that you have minishift installed locally and executable directly from your path.
@@ -82,13 +82,24 @@ For development OpenShift S2I builds and image streams are used.
 This mode works also when running with a real OpenShift cluster and is not restricted to Minishift usage.
 The advantage is that a build automatically triggers a redeployment, so you don't have to kill any pods manually.
 
-Commands
+_Commands_
 All other options are specific to each command.
 You get a list of those options with `syndesis <cmd> -h`.
 These options are described in detail in the next sections.
 
 The following commands are available:
 
+|Command      | Description|
+| ----------- | -----------|
+| build       | Used for building Syndesis and its various modules.   |
+| ui          ||
+| minishift   ||
+| install     ||
+| system-test ||
+| dev||
+| doc||
+| release||
+
 [cols="3,15",options="header"]
 |===
 | Command
@@ -146,11 +157,3 @@ yourscriptname::run() {
 }
 ```
 
-include::cmd_build.adoc[]
-include::cmd_ui.adoc[]
-include::cmd_minishift.adoc[]
-include::cmd_system_test.adoc[]
-include::cmd_dev.adoc[]
-include::cmd_doc.adoc[]
-include::cmd_release.adoc[]
-include::cmd_install.adoc[]
diff --git a/themes/syndesis/scss/syndesis.scss b/themes/syndesis/scss/syndesis.scss
index e114172b..805116c5 100644
--- a/themes/syndesis/scss/syndesis.scss
+++ b/themes/syndesis/scss/syndesis.scss
@@ -51,6 +51,7 @@ body {
     border-spacing: 2px;
     empty-cells: hide;
     line-height: 1.5;
+    margin-bottom: 1.5rem;
     overflow: auto;
     width: 100%;
 

From 8ea6411709c08b4efed9d8cd2d7ab0d2f6944b70 Mon Sep 17 00:00:00 2001
From: kahboom <rachelyordan@gmail.com>
Date: Tue, 13 Nov 2018 11:51:06 +0000
Subject: [PATCH 12/42] Adj weight menus for list ordering, top and side nav

---
 content/community.md   | 2 +-
 content/docs/_index.md | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/content/community.md b/content/community.md
index d976ee98..77ee6cbf 100644
--- a/content/community.md
+++ b/content/community.md
@@ -8,7 +8,7 @@ menu:
   sidenav:
     name: "Community"
     pre: "<i class='fa fa-fw fa-group'></i>"
-    weight: -180
+    weight: -80
   topnav:
     name: "community"
     weight: -120
diff --git a/content/docs/_index.md b/content/docs/_index.md
index e3e3b6bd..17d7e28f 100644
--- a/content/docs/_index.md
+++ b/content/docs/_index.md
@@ -12,7 +12,7 @@ menu:
     weight: -180
   topnav:
     name: "docs"
-    weight: -120
+    weight: -180
 ---
 
 This handbook contain all information required for installing, running and developing Syndesis from a developer's point of view.

From a57e40c6a200a35c3d3ca39e1dbbb67c9605af0a Mon Sep 17 00:00:00 2001
From: kahboom <rachelyordan@gmail.com>
Date: Tue, 13 Nov 2018 12:10:22 +0000
Subject: [PATCH 13/42] Fix commands table

---
 content/docs/cli.md | 46 ++++++++-------------------------------------
 1 file changed, 8 insertions(+), 38 deletions(-)

diff --git a/content/docs/cli.md b/content/docs/cli.md
index 9f25277b..6d8b2ff2 100644
--- a/content/docs/cli.md
+++ b/content/docs/cli.md
@@ -91,44 +91,14 @@ The following commands are available:
 
 |Command      | Description|
 | ----------- | -----------|
-| build       | Used for building Syndesis and its various modules.   |
-| ui          ||
-| minishift   ||
-| install     ||
-| system-test ||
-| dev||
-| doc||
-| release||
-
-[cols="3,15",options="header"]
-|===
-| Command
-| Description
-
-| <<syndesis-build,**build**>>
-| Used for building Syndesis and its various modules.
-
-| <<syndesis-ui,**ui**>>
-| Start the UI for local development _(not implemented yet)_
-
-| <<syndesis-minishift,**minishift**>>
-| Start and install Syndesis on Minishift
-
-| <<syndesis-install,**install**>>
-| Install Syndesis in a running cluster (other than Minishift)
-
-| <<syndesis-system-test,**system-test**>>
-| Run System test against an OpenShift cluster
-
-| <<syndesis-dev,**dev**>>
-| Utility commands useful during development
-
-| <<syndesis-doc,**doc**>>
-| Generating and publish this documentation
-
-| <<syndesis-doc,**release**>>
-| Release Syndesis' Maven and NPM artefacts _(not implemented yet)_
-|===
+| build       | Used for building Syndesis and its various modules   |
+| ui          | Start the UI for local development _(not implemented yet)_ |
+| minishift   | Start and install Syndesis on Minishift |
+| install     | Install Syndesis in a running cluster (other than Minishift) |
+| system-test | Run System test against an OpenShift cluster |
+| dev         | Utility commands useful during development |
+| doc         | Generating and publish this documentation |
+| release     | Release Syndesis' Maven and NPM artifacts _(not implemented yet)_ |
 
 If no command is given, `build` is the default.
 Remember a command must be the first argument, but there are additional possibilities to specify commands:

From 174c2d7c1c9fb5d3503d93e0c138331413763114 Mon Sep 17 00:00:00 2001
From: kahboom <rachelyordan@gmail.com>
Date: Tue, 13 Nov 2018 13:29:28 +0000
Subject: [PATCH 14/42] Fix pre styling

---
 content/docs/cli.md             | 18 ++++++++++--------
 themes/syndesis/scss/_docs.scss | 14 ++++++++++++++
 2 files changed, 24 insertions(+), 8 deletions(-)

diff --git a/content/docs/cli.md b/content/docs/cli.md
index 6d8b2ff2..a5420c10 100644
--- a/content/docs/cli.md
+++ b/content/docs/cli.md
@@ -1,7 +1,7 @@
 ---
 draft: false
-title: "CLI"
-description: "CLI test."
+title: "Syndesis CLI"
+description: "Buildtool \"syndesis\""
 sidebar: "sidenav"
 menu:
   sidenav:
@@ -13,8 +13,6 @@ weight: 10
 ---
 
 
-# Buildtool "syndesis"
-
 Syndesis uses a single tool for controlling various aspects of the build and developer related tasks.
 This script can be found in `$SYNDESIS_DIR/tools/bin` and is called `syndesis`.
 It requires bash and can be used on any Unix or macOS.
@@ -25,7 +23,8 @@ The script can be used for various tasks which are selected by a so-called comma
 
 Just type `syndesis -h` to get an overview of the commands available:
 
-_Usage message_
+
+<i class="title">Usage Message</i>
 ```
 Usage: syndesis <command> [... options ...]
 
@@ -50,7 +49,7 @@ There are a handful of global options which can be used:
 | `--verbose`   | &nbsp; | Set verbose mode, which is useful mostly only for debugging the script itself. |
 
 
-_Rebase to upstream_
+<i class="title">Rebase to Upstream</i>
 
 To easily rebase on changes which have been merged upstream to master, you can use the option `--rebase` (short: `-r`).
 This command assumes that you have forked the Syndesis GitHub repositories and you have "origin" and "upstream" remotes like
@@ -72,7 +71,8 @@ With this in place, a `--rebase` performs the following steps:
   - The rebase is retried and should succeed
   - `git stash pop` brings back your changes. Stashing can fail with conflicts which you would have to resolve on your own.
 
-_Development Modes_
+
+<i class="title">Development Modes</i>
 
 The Syndesis application consists of a set of Docker images OpenShift resources descriptors for installing Syndesis.
 For development, https://www.openshift.org/minishift/[minishift] is used, and most of the commands assume that you have minishift installed locally and executable directly from your path.
@@ -82,7 +82,9 @@ For development OpenShift S2I builds and image streams are used.
 This mode works also when running with a real OpenShift cluster and is not restricted to Minishift usage.
 The advantage is that a build automatically triggers a redeployment, so you don't have to kill any pods manually.
 
-_Commands_
+
+<i class="title">Commands</i>
+
 All other options are specific to each command.
 You get a list of those options with `syndesis <cmd> -h`.
 These options are described in detail in the next sections.
diff --git a/themes/syndesis/scss/_docs.scss b/themes/syndesis/scss/_docs.scss
index 7f93d999..585ec583 100644
--- a/themes/syndesis/scss/_docs.scss
+++ b/themes/syndesis/scss/_docs.scss
@@ -4,6 +4,20 @@
 
 @import "colors";
 @import "navbar";
+@import "./bootstrap/_variables";
+@import "../../../node_modules/bootstrap/scss/bootstrap";
+
+@import "colors";
+@import "highlighting";
 
 .docs {
+  p i {
+    &.title {
+      color: $pf-blue;
+    }
+  }
+
+  pre {
+    background: #f7f7f8;
+  }
 }

From c00586aa3ff8ed330f7b6d15531e60c857d0f06e Mon Sep 17 00:00:00 2001
From: kahboom <rachelyordan@gmail.com>
Date: Tue, 13 Nov 2018 13:30:45 +0000
Subject: [PATCH 15/42] Update italic title

---
 themes/syndesis/scss/_docs.scss | 1 +
 1 file changed, 1 insertion(+)

diff --git a/themes/syndesis/scss/_docs.scss b/themes/syndesis/scss/_docs.scss
index 585ec583..69b2962f 100644
--- a/themes/syndesis/scss/_docs.scss
+++ b/themes/syndesis/scss/_docs.scss
@@ -14,6 +14,7 @@
   p i {
     &.title {
       color: $pf-blue;
+      font-size: 1.1em;
     }
   }
 

From 41e4aad6154b8f701586119614a833dcd107e55e Mon Sep 17 00:00:00 2001
From: kahboom <rachelyordan@gmail.com>
Date: Tue, 13 Nov 2018 14:28:11 +0000
Subject: [PATCH 16/42] Darken code blocks for Docs section

---
 themes/syndesis/scss/_docs.scss | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/themes/syndesis/scss/_docs.scss b/themes/syndesis/scss/_docs.scss
index 69b2962f..fa867547 100644
--- a/themes/syndesis/scss/_docs.scss
+++ b/themes/syndesis/scss/_docs.scss
@@ -19,6 +19,6 @@
   }
 
   pre {
-    background: #f7f7f8;
+    background: #f7f7f8 !important;
   }
 }

From e0074684ddac1e6c8257c3f1d5f655f9e86c242c Mon Sep 17 00:00:00 2001
From: kahboom <rachelyordan@gmail.com>
Date: Tue, 13 Nov 2018 14:58:19 +0000
Subject: [PATCH 17/42] Add remaining content for CLI page

---
 content/docs/cli.md | 945 ++++++++++++++++++++++++++++++++++++++++++++
 1 file changed, 945 insertions(+)

diff --git a/content/docs/cli.md b/content/docs/cli.md
index a5420c10..b5a44e0f 100644
--- a/content/docs/cli.md
+++ b/content/docs/cli.md
@@ -129,3 +129,948 @@ yourscriptname::run() {
 }
 ```
 
+## syndesis build
+
+The primary goal of `syndesis build` is to build Syndesis.
+
+It is mainly a wrapper around Maven and Go but adds some convenience functionality for common developer workflows.
+
+### Usage
+
+Usage: syndesis build [... options ...]
+
+Options for build:
+
+    -b  --backend                  Build only backend modules (core, extension, integration,
+                                   connectors, server, meta)
+        --all-images               Build all modules with images: ui, server, meta, s2i, operator
+        --app-images               Build only application modules with Docker images
+                                   (ui, server, meta, s2i)
+                                   and create images
+        --infra-images             Build only infrastructure modules with Docker images
+                                   (operator) and create images
+    -m  --module <m1>,<m2>, ..     Build modules
+                                   Modules: ui, server, connector, s2i, meta, integration,
+                                   extension, common, operator
+    -d  --dependencies             Build also all project the specified module depends on
+        --skip-tests               Skip unit and system test execution
+        --skip-checks              Disable all checks
+    -f  --flash                    Skip checks and tests execution (fastest mode)
+    -i  --image                    Build Docker images, too
+                                   (for those modules creating images)
+        --docker                   Use a plain Docker build for creating images.
+                                   Used by CI for pushing to Docker Hub
+    -p  --project <project>        Specifies the project/namespace to create images in
+    -e  --ensure                   If building the operator, run 'dep ensure' before building.
+                                   Otherwise ignored.
+    -l  --local                    If building the operator, use a locally installed go
+                                   Otherwise run the Go build from a container
+                                   (either local or Minishift's Docker daemon)
+        --clean-cache              Used for the operator build to remove the local dependency cache.
+    -c  --clean                    Run clean builds (mvn clean)
+        --resume <m1>              Resume build from maven module (mvn -rf m1)
+        --batch-mode               Run mvn in batch mode
+        --camel-snapshot <version> Run a build with a specific Camel snapshot.
+                                   If no argument is given the
+                                   environment variable CAMEL_SNAPSHOT_VERSION is used or an error thrown.
+----
+
+### Modules
+A plain `build` command without any options performs a plain `mvn install` for all Java and UI modules.
+Plus it also builds the infrastructure operator via Go (see <<below,syndesis-build-operator>> for details)
+
+This compiles all Java and Javascript artefacts and also runs all tests and code checks for the application modules.
+
+You restrict the build to certain modules, which are divided into two categories: _application modules_ which are the modules building up Syndesis.
+And _infrastructure modules_ which help in managing the application itself.
+
+You can individually select specific modules by using the `--module` (short: `-m`) option with a comma-separated list of modules, but there
+are also option to combine modules
+
+
+The following modules are available:
+
+|===
+| Module | Description | `--all-images` | `--backend` | `--app-images` | `--infra-images`
+
+| **server**
+| Main backend providing a REST API for the user interface
+| ✔︎
+| ✔︎
+| ✔︎
+|
+
+| **ui**
+| The SPA user interface application
+| ✔︎
+|
+| ✔︎
+|
+
+| **meta**
+| Meta data and verifier used for verifying connections and providing connector metadata
+| ✔︎
+| ✔︎
+| ✔︎
+|
+
+| **connector**
+| All connectors used by Syndesis out of the box
+|
+| ✔︎
+|
+|
+
+| **integration**
+| Support libraries for running integrations
+|
+| ✔︎
+|
+|
+
+| **extension**
+| Tools for developing and running Syndesis custom extensions
+|
+| ✔︎
+|
+|
+
+| **common**
+| Common modules containing common code
+|
+| ✔︎
+|
+|
+
+| **s2i**
+| S2I base image used for building the runtime images
+| ✔︎
+|
+| ✔︎
+|
+
+| **operator**
+| Infrastructure operator for managing the application
+| ✔︎
+|
+|
+| ✔︎
+
+All option ending with `-images` will also build the corresponding Docker image.
+
+When you build individual modules you you can provide the option `--image` (short: `-i`) to create also the Docker image in the build, when the module is associated with a Docker image.
+
+By default images are build via S2I against a running Minishift.
+This is the recommended way for developing as this automatically will trigger a redeployment after the build.
+However, for certain scenarios like when used in a CI system or when doing the release, the image creation can be done against are Docker daemon when the `--docker` is given.
+For this to work you must have access to Docker daemon, which you can verify with `docker ps`.
+
+When the option `--dependencies` (short: `-d`) is given in addition to `--modules`, also all Maven modules which the specified modules depend on are build, too.
+
+### Tuning
+By default, all checks like license or code quality checks are performed.
+Also, all unit and local integration tests are run.
+A full build eats up quite some time, but you should always run at full blast before submitting a pull request.
+
+However, to speed up the turnaround, several speed-up options are available.
+The following table shows these options, and also how long a full clean build over all modules takes: (but without building images)
+
+|===
+|Option
+|Description
+|Time
+
+| _none_
+| Default mode with all checks and tests
+|
+
+| `--skip-tests`
+| Skip all unit and local integration tests
+|
+
+| `--skip-checks`
+| Skip sanity checks like for correct license headers and
+|
+
+
+| `--flash`
+| Fastest mode with skipping all checks and tests and with even some other aggressive optimizations
+|
+
+| `--camel-snapshot <version>`
+| Sometimes it's needed to use a Camel snapshot version for building. This snapshot most be available in you local Maven repo (`~/.m2`) Use this option with the Camel version. Alternatively, you can also set the environment variable `CAMEL_SNAPSHOT` to the corresponding version.
+|===
+
+### Infrastructure Operator
+
+`syndesis build` can also build the infrastructure operator, which is a golang program.
+
+You can build the operator by running `syndesis build -m operator` or
+as part of a module collection like `--all-images` or `--infra-images`
+
+There are three modes, how the operator can be created:
+
+* Running you go compiler locally
+* Compiling in a local Docker daemon which allows volume mounts with the localhost
+* Compiling in Minishift Docker daemon, which was made accessible via `eval $(minishift docker-env)`
+
+See below for the details.
+
+.Load dependencies
+
+In any case, before you compile first you should use the option `--ensure` (short: `-e`) to setup the dependency tree.
+This will download all source dependency and cache them locally.
+To get rid of this cache, use the option `--clean-cache`.
+This might be necessary when `go dep` 's cache gets into a weird state.
+
+If you compile for the first time, then `--ensure` will be added automatically.
+
+.Compiling locally
+
+This is the fastest way for compiling the operator.
+Use the option `--local` (short: `-l`) for selecting the local compile mode.
+
+It is also the recommended way when you are working on the operator.
+You project setup needs to fit however: The main project directory must be reachable as `$GOPATH/src/github.com/syndesisio/syndesis`.
+You can either move your project directory to this location or work with a symlink:
+
+----
+cd ~/Development/syndesis
+mkdir -p $GOPATH/src/github.com/syndesisio
+cd ..
+mv syndesis $GOPATH/src/github.com/syndesisio/
+ln -s $GOPATH/src/github.com/syndesisio/ syndesis
+----
+
+By default this compiles into for your native architecture (amd64, darwin).
+When you use this mode with `--image` (short: `-i`) on macOS then go will be used as cross compiler so that the generated bimary can be used in a Linux image.
+
+.Compiling with a local Docker daemon
+
+This is the default mode and is used also when doing the release.
+It use a builder image `syndesis/godev` which is created from the `tools/image` directory and fetched from Docker Hub.
+
+For this mode to work your Docker daemon must support volume mounts to the system from where you are calling `syndesis`.
+This is the case on Linux for locally installed Docker daemon and for Mac with _Docker for Mac_.
+It is *not* the case for Minishift which runs in a disconnected VM.
+But see below how you still can use Minishift for building.
+
+`dep ensure` and `go build` will be run from this `syndesis/godev` image, but with your local directory mounted into the container so that the fetched dependencies can be cached in the local directories `dep-cache` and `vendor` so that the can be reused for the next run.
+Also the binary will be stored in your local directory, but this will alway be a Linux (`amd64`) binary.
+
+.Compiling with Minishift
+
+As Minishift is running in a remote VM you cannot bind a volume to your localhost. Therefor when running in Minishift mode the source code will be rsynced to a directory in the Minishift VM (`rsync` will be installed in the Minishift VM on the first run).
+
+The build with `syndesis/godev` will then be started with a volume mount to the copied directory in the VM.
+After the build the generated binary is copied back with `rsync` to your local directory.
+
+The Minishift mode is automatically detected and selected if `DOCKER_CERTS` contains a path to `.minishift`.
+You enable the Minishift Docker daemon for your local CLI with `eval $(minishift docker-env)`
+
+Some simple benchmark reveals the following timings (in minutes) :
+
+|===
+| Context | Local | Local Docker (macOS) | Minishift Docker
+
+| Cold (no build cache)
+| 0:40
+| 10:09
+| 1:36
+
+| Hot (with dep cache)
+| 0:08
+| 2:47
+| 0:13
+|===
+
+The fastest mode is obviously the local mode, followed surprisingly by Minishift.
+The local mode is probably slow because of how the macOS daemon mounts ts volumes (which can probably be optimized)
+
+### Examples
+
+Some common usage examples for `syndesis build` are
+
+```
+# Build all images (app and infrastructure) with S2I
+syndesis build --all-images
+
+# Create all application images and re-deploy Syndesis in the
+# Openshift cluster, but do it as fast as possible. Don't build
+# any golang code
+syndesis build --app-images --flash
+
+# Create the infrastructure operator by running go locally
+# and calling `dep ensure before`
+syndesis build -m operator --local --ensure
+
+# Use a Camel snapshot for a clean build, build all modules
+syndesis build --clean --camel-snapshot 2.21.0-SNAPSHOT
+```
+
+
+## syndesis ui
+
+"syndesis ui" is not implemented yet
+****
+This is just a placeholder, still in the planning phased.
+Nevertheless we already start to document the feature for an "UX first" approach.
+****
+
+### Usage
+
+---
+
+## syndesis minishift
+
+With `syndesis minishift` you can adequately manage a https://www.openshift.org/minishift/[minishift] installation for hosting Syndesis.
+This command is especially useful for a simple and self-contained development workflow.
+
+`syndesis minishift` requires that you have a current minishift in your path.
+You can download it directly from https://github.com/minishift/minishift/releases[GitHub].
+
+### Usage
+
+```
+--install                 Install templates to a running Minishift.
+-p  --project             Install into this project.
+                          Delete this project if it already exists.
+                          By default, install into the current project (without deleting)
+-c  --context             Install into this context. Default is 'minishift'
+--reset                   Reset and initialize the minishift installation by
+                          'minishift delete && minishift start'.
+--full-reset              Full reset and initialie by
+                          'minishift stop && rm -rf ~/.minishift/* && minishift start'
+--memory <mem>            How much memory to use when doing a reset. Default: 4912
+--cpus <nr cpus>          How many CPUs to use when doing a reset. Default: 2
+--disk-size <size>        How many disk space to use when doing a reset. Default: 20GB
+--vm-driver <driver>      Which virtual machine driver to use (depends on OS)
+--show-logs               Show minishift logs during startup
+--openshift-version <ver> Set OpenShift version to use when reseting (default: v3.9.0)
+--tag <tag>               Syndesis version/tag to install. If not given, then the latest
+                          version from master is installed
+--local                   Use the local resource files instead of fetching them from GitHub
+-o  --open                Open Syndesis in the browser
+-y  --yes                 Assume 'yes' automatically when asking for deleting
+                          a given project.
+--memory-server <mem>     Memory limit to set for syndesis-server. Specify as "800Mi"
+--memory-meta <mem>       Memory limit to set for syndesis-meta. Specify as "512Mi"
+--test-support            Allow test support endpoint for syndesis-server
+--man                     Open HTML documentation in the Syndesis Developer Handbook
+```
+
+### Installing Syndesis
+
+You can easily install Syndesis with the option `--install`.
+This option triggers the creation of all relevant OpenShift resources objects in the currently connected OpenShift project.
+
+If you want to use a different project, then use `--project` (short: `-p`) to specify this project.
+
+WARNING: Any existing project will be deleted first when specified with `--project`. This option is also an easy and quick way to recreate a Syndesis installation.
+
+### Resetting Minishift
+
+The quickest way to get a fresh Syndesis setup is to use `--project` which will install Syndesis into a clean, new project.
+
+However, you can also recreate the whole Minishift installation with `--reset`. This will delete the Minishift VM (`minishift delete`) and create a new one (`minishift start`).
+It doesn't harm if the Minishift VM does not exist so that you can use `--reset` also on a fresh Minishift installation.
+
+If you want to get a real clean installation use `--full-reset` which deletes the `~/.minishift` directory which holds downloaded artefacts like the ISO image for the Minishift VM.
+Using `--full-reset` forces Minishift to re-download all those files.
+
+There are several options which influence the re-creation of the VM:
+
+
+| Option
+| Description
+| Default
+
+|`--memory`
+| Memory to use for the Minishift VM.
+| 4 GB
+
+|`--cpus`
+| Number of CPUs used for the Minishift VM.
+| 2
+
+|`--disk-size`
+| Disk space used for Minishift.
+| 20 GB
+
+|`--show-logs`
+| Whether to show OpenShift logs during startup.
+| false
+
+|`--vm-driver`
+| Which virtual machine driver to use. For OS X this can be 'virtualbox', 'xhyve' or 'vmwarefusion' (if insalled).
+|
+
+|`--openshift-version`
+| OpenShift version to use
+| 3.7.1
+
+
+### Example
+
+This short example performs the following actions:
+
+* Stops and deletes a running Minishift VM (if existent)
+* Removes `~/.minishift` (if existent)
+* Install Syndesis in OpenShift modes (S2I builds & image streams) in project `syndesis`
+* Open Syndesis UI in the default browser
+
+```
+# Complete fresh installation in project "syndesis"
+syndesis minishift --full-reset --install --project syndesis
+
+# Open Syndesis in default browser
+syndesis minishift -o
+```
+
+
+## syndesis system-test
+
+The `system-test` command is for running a full blown system test of Syndesis by installing it in one of multiple projects which are managed in a pool.
+
+
+### Usage
+
+```
+Usage: syndesis system-test [... options ...]
+
+Options for system-test:
+    --project <project>       The test project to use
+    --token <token>           Token for connecting to the server
+    --server <url>            OpenShift server url to use for the tests.
+                              If not given, use the currently connected server
+    --pool <project>          If no project is given, use a pooling mechanism.
+                              This pool has to be created before with --create-pool
+    --test-id <id>            Id to identify the test run
+    --create-pool <prefix>    Create project pool for system-tests with
+                              all projects with the given prefix
+    --list-pool               Show all locks for the pool
+    --release-project <t-id>  Release project for given test id (or all if no test id is given)
+```
+
+### How it works
+
+NOTE: This section needs a more detailed explanation how the systems tests are working in detail.
+
+
+
+## syndesis dev
+
+Dev commands are useful helpers for developing Syndesis
+
+### Usage
+
+```
+Usage: syndesis dev [... options ...]
+
+Options for dev:
+    --debug <name>            Setup a port forwarding to <name> pod (default: server)
+```
+
+This command enable port-forwarding of port 5005 from a specific pod (by default: "server") to port 5005 on the localhost.
+You then can point your Java IDE to port 5005 on localhost for connecting for remote debugging.
+As argument to `--debug` "server", "meta" and "atlasmap" can be used, which are our Java based services.
+
+
+## syndesis doc
+
+This command is used to generated and manage this documentation which you are currently reading.
+
+
+### Usage
+
+```
+Usage: syndesis doc [... options ...]
+
+Options for doc:
+-d  --directory <dir>         Top-level dir holding doc source and output directory. Default: "doc/sdh"
+-i  --input <file>            Input file to use. Default: "index.adoc"
+    --out <dir>               Directory to generate files (default: "output")
+    --html                    Generate HTML pages
+    --pdf <out>               Generate PDF and write it to <out> (default: "sdh.pdf")
+    --epub <out>              Generate Epub and write it to <out> (default: "sdh.epub")
+    --gh-pages <msg>          Create everything into the gh-pages branch and commit with <msg>
+-o  --open                    Open HTML documentation in default browser after doc generation
+-l  --local                   Use locally installed commands instead of Docker image
+```
+
+`syndesis doc` uses by default a Docker container to create the documentation.
+Therefore a Docker daemon must be accessible, and it must allow https://docs.docker.com/engine/admin/volumes/bind-mounts/[bind volume mounts] to the local `doc/sdh` directory.
+Bind mounts are possible for Linux Docker daemons and for "Docker for Mac".
+But it is not the case for the Minishift exposed Docker daemon, as this daemon is running isolated in a VM.
+
+You can always run `asciidoctor` locally with the `--local` (short: `-l`) options. See the https://asciidoctor.org/#installation[Asciidoctor manual] for more information how to install Asciidoctor.
+
+
+### Output
+
+Input and output has the same defaults but can be changed with the following options
+
+[cols="4,3,15"]
+|===
+|`--input <file>`
+|`-i <file>`
+| Input document in Asciidoc format which is by default `$SYNDESIS_DIR/doc/sdh/index.adoc`
+
+
+| `--output <dir>`
+| `-o <dir>`
+| Output directory, default is `$SYNDESIS_DIR/doc/sdh/output`
+|===
+
+By default `syndesis doc` creates the documentation in HTML format, but more formats are supported:
+
+[cols="3,15"]
+|===
+| `--html`
+| Create HTML documentation in the output directory
+
+|`--pdf <name>`
+| Create PDF documentation. `<name>` is optional, but when given, then this specifies the file name generated in the output directory. By default `sdh.pdf` is used.
+
+|`--epub <name>`
+| Create the documentation in Epub format. `<name>` is optional, but when given, then this specifies the file name generated in the output directory. By default `sdh.epub` is used.
+|===
+
+
+## syndesis release
+
+Use `syndesis release` for performing a release of Syndesis.
+A Syndesis release consists of:
+
+* Maven artefacts of the backend and runtime services
+* Docker images pushed to Docker Hub
+* A set of OpenShift templates referencing these images
+
+This chapter describes how you can efficiently perform a release and
+how to troubleshoot if something goes wrong.
+This documentation might also be interesting to you even when you do not perform a release on your own, as it might help you to understand how the various Syndesis artefacts fit together.
+
+
+### Usage
+
+
+Perform a release
+
+This command performs a release but does *no* automated rollback when something fails.
+Please refer to the manual at https://docs.syndesis.io for more details and what needs
+to be cleaned up in case of a failure.
+
+```
+Usage: syndesis release [... options ...]
+
+Options for release:
+-n  --dry-run                 Dry run, which performs the whole build but does no tagging,
+                              artefact upload or pushing Docker images
+    --release-version <ver>   Version to release (e.g. "1.2.1"). This is a mandatory argument.
+    --snapshot-release        Snapshot release which can be created on a daily basis.
+                              A timestamped version will be created automatically, and no Maven artefacts
+                              are pushed to maven central. No moving tag will be moved, too.
+    --dev-version <version>   Next development version. If not given, set to
+                              "<major>.<minor>-SNAPSHOT" as calculated from
+                              --release-version (e.g. "1.2-SNAPSHOT")
+    --settings <file>         Path to a custom settings.xml to use for the release.
+                              This file must contain all the credentials to be used for Sonatype.
+                              By default ~/.m2/settings.xml is used.
+    --local-maven-repo <dir>  Local dir for holding the local Maven repo cache.
+                              If not given, then a new
+                              temporary directory will be used
+                              (and removed after the release)
+    --docker-user <user>      Docker user for Docker Hub
+    --docker-password <pwd>   Docker password for Docker Hub
+    --no-git-push             Don't push the release tag (and symbolic major.minor tag)
+    --git-remote              Name of the git remote to push to. If not given, its trying to be pushed
+                              to the git remote to which the currently checked out branch is attached to.
+                              Works only when on a branch, not when checked out directly.
+
+    --log <log-file>          Write full log to <log-file>, only print progress to screen
+    --man                     Open HTML documentation in the Syndesis Developer Handbook
+```
+
+A lot of output is produced during a release.
+If you are only interested to see the major steps only, then you
+can use `--log` to redirect the output to a specific log file.
+This log file will contain all output (and if you add `--verbose` you see even more output), but on the console you will only see the current step that is actually performed.
+
+.Example
+An example run for a dry run for `1.3.1` release on the current branch look like:
+
+```
+./tools/bin/syndesis release           \ <1>
+    --release-version 1.3.1            \ <2>
+    --local-maven-repo /tmp/clean-repo \ <3>
+    --log /tmp/build.log               \ <4>
+    --dry-run                            <5>
+```
+
+<1> Always run `syndesis` from the repo and branch you want to release.
+<2> The release version is mandatory and must be in the format `<major>.<minor>.<patch>`.
+<3> Use a clean local Maven repository to avoid side effects
+<4> Redirect the full output to `/tmp/build.log` but still print the main steps to the console.
+<5> Make only a dry run, without pushing any artefacts out nor checking in any changed files.
+
+### Preparations
+
+To perform a release, certain preconditions need to be given.
+
+First of all, you need to have access to the various systems to which release artefacts are uploaded:
+
+* You need to be logged in to https://hub.docker.com/[Docker Hub] and your account needs to have write access to the https://hub.docker.com/u/syndesis/[syndesis] Docker Hub organisation.
+* You have `gpg` to have installed and set up a gpg-agent for being able to sign Maven artefacts during deployment in a non-interactive mode.
+* You need to have access to the "syndesis" account on (http://oss.sonatype.org/)[oss.sonatype.org] for being able to publish Maven artefacts.
+This credential needs to be added to either your `~/.m2/settings.xml` or you can use an settings file with the `--settings-xml` option.
+The credential needs to be added to the server with the id `oss-sonatype-staging`.
+
+You have to perform the release from a locally checked out Syndesis repository, which can be either checkout from a branch like `1.2.x` for a patch release or directly from `master`.
+It is highly recommended to run the release directly from a freshly checked out directory:
+
+```
+# Go to a temporary directory
+cd /tmp
+
+# Clone repository afresh, but only use the last history entry (--depth=1)
+git clone --depth=1 https://github.com/syndesisio/syndesis.git
+
+# Jump into the directory
+cd syndesis
+
+# Switch to the target branch if needed (or stay on master)
+git fetch --depth 1 origin 1.2.x:1.2.x
+git checkout 1.2.x
+
+# Call Syndesis from the checked out clone
+./tools/bin/syndesis release --release-version 1.2.8 .....
+
+# Push to origin after a successful release.
+# This automatically done if --no-git-push is given
+git push 1.2.8
+git push -f 1.2
+
+# Remove the temporary clone again
+cd ..
+rm -rf syndesis
+```
+
+Please note that you should always call `syndesis` out of the branch for which the release is for.
+If there is an issue due to bugs in the release script itself, please fix them on the branch with the usual developer process (i.e. opening a PR request).
+`syndesis release` must always work for the branch where this script is, too.
+
+### Release steps
+
+A release consist of several different steps, which can be grouped into two groups:
+
+* *Build steps* are performed to build the release and create the artefacts.
+Also during the build Maven artefacts are uploaded to the staging area for publishing to Maven central
+* *Persist steps* are then used for releasing objects, pushing Docker images to Docker Hub, committing and tagging in Git (but only when the build steps have been performed successfully).
+
+#### Build steps
+
+* Check whether the current local Git clone is _clean_, i.e. that is does not have any modified files.
+The script will abort if this is the case.
+* Update the versions of all `pom.xml` files below `app/` to the version given with `--release-version`.
+If no `--release-version` is given, then the script aborts.
+* Run an `mvn clean install` to verify that the build is not broken and all tests succeed.
+* Re-generate the OpenShift templates in `install` so that the image streams included in these templates refer to Docker images with the new version.
+* Now run an `mvn -Prelease clean deploy` to deploy all artefacts to a new staging repository on oss.sonatype.org, the platform for release artefacts on Maven central.
+The staging repository on this Sonatype Nexus is validated and closed.
+* If `--docker-user` and `--docker-password` is given, then a `docker login` is performed.
+Otherwise, it is assumed that the user is already logged in.
+* The Docker images are created with `mvn -Prelease,image package` in the `server`, `meta`, `ui` and `s2i` modules.
+
+If the option `--dry-run` (short: `-n`) is provided, the script drops the staging repository at Sonatype and stops.
+You should examine the generated files and before starting a real build, reset the repository (`git reset --hard`).
+
+The builds are using a clean local Maven repository, which otherwise is usually taken from `~/.m2/repository`.
+This new local cache should ensure that we have a completely fresh build without interference from previous builds store in the local Maven cache in the home directory.
+You can provide such a directory with `--local-maven-repo` which will be taken directly (so it's good if you have to perform multiple runs like with `--dry-run`).
+If not provided, a new temporary directory is created and also _deleted_ after the release run.
+
+#### Persist steps
+
+* Push Docker images to Docker Hub.
+In addition to the images that carry the full release version as the tag, also a tag for the _minor version_ is attached and pushed.
+E.g. when the release version is `1.2.8`, then the minor version is `1.2`.
+If this minor version tag already exists on Docker Hub, its moved to the newly created version.
+* The staging repository on Sonatype is released.
+It will take a bit, but the artefact should then be downloadable from https://search.maven.org/[Maven central] soon after.
+* Commit all modified local files to the local Git repo.
+* Create a Git tag for the release version (e.g. `git tag 1.2.8`).
+
+The next steps are for creating templates for the minor version:
+
+* In `install` create new templates which contain image streams that reference images with the minor version (e.g. `syndesis/syndesis-server:1.3` for a release version of 1.3.8).
+* Commit those generated templates
+* Tag it with the minor version (e.g. `1.2`), overwriting an already existing minor version tag
+
+Next, we are switching back to the next development version of the pom.xml files.
+This version can be given with `--dev-version`, but by default, it is calculated automatically as `<minor.version>-SNAPSHOT` (e.g. `1.2-SNAPSHOT`).
+This new version is then committed to the local git repository.
+
+Finally, the tags just created on the local Git repo is pushed to the remote repository.
+You can omit this with the option `--no-git-push`.
+If to so, the last step can also be performed manually afterwards with:
+
+```
+git push 1.2.8
+git push -f 1.2 <1>
+```
+<1> Using `-f` as the minor tag needs to be moved.
+
+Please be careful to *not* push the master branch upstream (i.e. do *not* a plain `git push`).
+We only want to have the tag with all the release preparation steps, not on the branch so that pull requests can be still be easily rebased with out conflict because of the temporary version changes.
+
+### Minor Version Templates
+
+What is now the thing with this _minor version_?
+Why is the needed and how does it work?
+
+Syndesis follows a https://semver.org/[semantic versioning] approach.
+So, patch level releases (i.e. all releases which only change the last digit in 1.2.8) are fully compatible with all other patch level versions.
+In order to allow easy bug fix upgrades, we also create a tag which contains only the version parts up to the minor version (e.g. 1.2).
+These tags *always* points to the latest full version of its minor version.
+If, e.g. 1.2.8 is the latest 1.2.x version, then the tag 1.2 point to this 1.2.8 version.
+Corresponding to these Docker image variants, there exist two OpenShift templates variants:
+
+* One set of templates directly references the Docker images which its full version, e.g. `syndesis/syndesis-ui:1.2.8`.
+Applying such a template will keep your application at precisely this patch-level.
+You would have to update your templates and recreate your applications if you want to upgrade.
+* The other set of templates references images only via its minor version, e.g. `syndesis/syndesis-ui:1.2`.
+Using these templates has the advantage that application created from these templates automatically benefit from patch releases.
+The templates contain an image change trigger which will redeploy the application if the images change.
+So when we release the next patch level release, moving the minor version tag to this patch level release, then the application gets automatically redeployed, and it will pick up the new image.
+
+These two sets of templates can be reached directly from GitHub as the git tags correspond to the Docker tags (i.e. a `1.2.8` tag and a `1.2` tag which will be moved forward).
+
+### Snapshot Release
+
+With the option `--snapshot-release` a lightweight snapshot release for the images and templates can be created.
+The tag/version is calculated automatically by picking up the latest release number (e.g. 1.3.5), increasing the patch-level by
+ one and adding a daily timestamp (e.g. 1.3.6-20180419).
+According to  https://semver.org/[Semantic Versioning 2.0] this is considered to be a version larger than 1.3.5 but https://semver.org/#spec-item-11[smaller] than 1.3.6.
+
+This tag can be referenced to in `syndesis install` and `syndesis minishift`.
+
+In detail, a snapshot release differs from a normal release as it:
+
+* ... doesn't release artefacts on Maven central, but pushes Docker images and creates a Git tag for referencing the proper templates.
+* ... skips all checks and tests when building to maximise the likelihood that the release succeeds. The rationale here is to better have untested daily snapshot release than no snapshot release because of test failure (which in many cases are not because of errors, but of failure in the infrastructure)
+* ... force pushes the snapshot tag on GitHub so that multiple releases per day are allowed
+
+.Example
+
+```
+syndesis release \
+     --snapshot-release \                   <1>
+     --local-maven-repo /tmp/clean-repo \   <2>
+     --git-remote origin \                  <3>
+     --docker-user "${DOCKER_USER}" \       <4>
+     --docker-password "${DOCKER_PASSWORD}"
+```
+
+<1> Enable snapshot release with a version in the format 1.3.5-20180419
+<2> Point to an empty repository to avoid side effects when building
+<3> Push to the origin repository
+<4> Docker credentials required for pushing to Docker Hub
+
+A daily Jenkins job with this configuration run on https://ci.fabric8.io for creating a daily snapshots.
+
+### Troubleshooting
+
+When you run the `syndesis release` command and when it should not succeed, you might have to perform some cleanup steps yourself
+(there is now automatic rollback).
+However, care has been taken to move all persistent changes to the end of the release flow, so if something breaks early, you only need to clean up locally.
+If the process fails before the step _=== Pushing Docker images_ you only need to:
+
+* Reset your local git repo with `git reset --hard`
+* Potentially remove the create staging repository on `http://oss.sonatype.org/` (but it doesn't harm if it is not cleaned up immediately).
+
+After pushing the Docker images, it should be improbable that things go wrong.
+But these things should take care of if this should be the case:
+
+* Remove Docker Hub tags for the pushed images, which is best done on the Docker Hub Web UI
+* Revert your local git commits to the point before the release. If you did this on a fresh checked out repo (as recommended), you just could delete the whole clone.
+
+
+## syndesis install
+
+With `syndesis install` you can install Syndesis to an arbitrary OpenShift cluster.
+If you want to install to https://www.openshift.org/minishift/[Minishift] the <<syndesis-minishift,syndesis minishift>> command is recommended as it supports some additional features specific to Minishift.
+
+### Usage
+
+```
+-s  --setup               Install CRDs clusterwide. Use --grant if you want a specific user to be
+                          able to install Syndesis. You have to run this option once as
+                          cluster admin.
+-u  --grant <user>        Add permissions for the given user so that user can install
+                          the operator in her projects. Must be run as cluster admin.
+    --cluster             Add the permission for all projects in the cluster
+                          (only when used together with --grant)
+-p  --project             Install into this project. Delete this project
+                          if it already exists. By default, install into the current project
+                          (without deleting)
+    --operator-only       Only install the operator but no resource
+    --route               Route to use. If not given, the route is trying to be detected
+                          from the currently connected cluster.
+    --console             The URL to the OpenShift console
+    --tag <tag>           Syndesis version/tag to install. If not given, then the latest
+                          version from master is installed
+    --dev                 Prepare for development of Syndesis so that S2I builds of
+                          Syndesis images are picked up properly (implies --watch)
+    --force               Override an existing "Syndesis" if present
+-w  --watch               Wait until cluster is up
+    --local               install from local Git repo when using. By default the
+                          resource descriptor is downloaded from GitHub remotely.
+-o  --open                Open Syndesis in browser when installation is ready (implies --watch)
+-y  --yes                 Assume 'yes' automatically when asking for deleting
+                          a given project.
+    --memory-server <mem> Memory limit to set for syndesis-server. Specify as "800Mi"
+    --memory-meta <mem>   Memory limit to set for syndesis-meta. Specify as "512Mi"
+    --test-support        Allow test support endpoint for syndesis-server
+
+You have to run `--setup --grant <user>` as a cluster-admin before you can
+install Fuse Online as a user.
+```
+
+The deployment happens to the currently connected OpenShift cluster.
+So it's mandatory that you have logged into the cluster with `oc login` before.
+You can check the status with `oc status`.
+
+The installation process consists of two steps:
+
+* An initial setup which has to be performed as _cluster admin_ which is a one-off action which needs to be done only once.
+* Installation of Syndesis into a specific project by the _app admin_, a regular user of OpenShiftm which can be performed as many times as required.
+
+### Initial Setup
+
+In the initial setup, you have to register the custom resource definition (CRD) to allow to deploy `Syndesis` resources.
+This step has to be performed by the admin.
+
+Also, if you want to allow an OpenShift user to install Syndesis on her own, then you have to grant specific permissions to her.
+
+To perform this setup step, which needs to be performed only once per cluster, you have to run `syndesis` **while being connected as a cluster admin**.
+For `minishift` use `oc login -u system:admin` if you have the `admin-user` addon enabled.
+
+```
+syndesis install --setup
+```
+
+This will install only the CRD. In addition to grant a user _developer_ the proper permission to create a `Syndesis` resource, you should add `--grant <user>`:
+
+```
+syndesis install --setup --grant <user>
+```
+
+This call adds permissions to read and write `Syndesis` resource objects for the current project.
+If you would instead want to allow the user managing `Syndesis` resources in the whole cluster, you should add a
+`--cluster`.
+This cluster-wide access is especially required when you plan to use the `--project` option to use a new project or recreate the existing one, as in this case the role association to this project gets lost.
+
+### Installing Syndesis
+
+After the CRDs a registered, you can easily install Syndesis directly with
+
+```
+syndesis install
+```
+
+Depending on whether you have granted the current user access this step has to be done either as admin or as a regular user.
+
+.Example for Minishift
+
+```
+# Enable the admin user on Minishift
+minishift addons enable admin-user
+
+# Create a minishift instance
+minishift start --memory 4192
+
+# Switch to admin
+oc login -u system:admin
+
+# Register CRD and grant permissions to "developer"
+syndesis --setup --grant developer --cluster
+
+# Switch to account developer
+oc login -u developer
+
+# Install Syndesis
+syndesis install
+```
+
+
+A route name can be given with `--route`.
+This step can be omitted as the operator can autodetect the route.
+If you provide the route manually, you need to check your OpenShift installation.
+Typically the route name is the name of your OpenShift project followed by the cluster's hostname.
+E.g. a route `--route proj186023.6a63.fuse-ignite.openshiftapps.com` is specific to the Fuse Ignite test cluster `6a63.fuse-ignite.openshiftapps.com` and for the project `proj186023`.
+However, you don't have to provide the route name.
+
+If you want to have a link to the OpenShift console to read the Pod logs, you have to add the `--console` option with the full URL to the console.
+Unfortunately, this cannot be autodetected.
+If not given, no link appears.
+
+By default, this commands installs Syndesis in the currently connected project, but you can specify an alternative project with `--project <project>`.
+If this project already exists, it gets deleted unconditionally before the deployment, so be careful when using this option.
+By default, you are asked whether you want to delete the project for recreation.
+You can switch off the security question with the option `--yes` (short: `-y`).
+
+WARNING: Don't use `syndesis install --project $(oc project -q) --yes`. You'll shoot yourself into the foot. Ask the author if you want to know more details.
+
+If you want to wait until everything is running (including fetching of the Docker images), you can specify `--watch` (short: `-w`) which blocks the script until everything is set up.
+
+You can also automatically open Syndesis in the browser after the installation with `--open` (short: `-o`)
+
+### Development mode
+
+As with <<syndesis-minishift,syndesis minishift>> you can also use this command to set up a development platform for Syndesis.
+_Development platform_ here means that you can create Docker images on your own with <<syndesis-build,syndesis build>> and can use them with an automatic redeployment after the build.
+
+You can switch on this mode with the option `--dev`.
+When the operator has deployed the application, the application imagestreams refer to Docker images pushed to Docker Hub.
+To change the imagestream references to the images built with `syndesis build --all-images`, these imagestreams needs to be patched after the initial images have been fetched from Docker Hub.
+If you use the `--dev` option, then this update is done automatically.
+
+### Selecting the version
+
+With the option `--tag` you can select a specific version of Syndesis to install.
+By default, the currently checked out checked out branch is used.
+
+.Example
+
+```
+syndesis install --route syndesis.192.168.64.12.nip.io --tag 1.4
+```
+
+This example installs the latest Syndesis version of the 1.4 branch to the local cluster.
+
+You can see a list of available tags with `git tag`.
+Tags prefixed with `fuse-ignite` are suited for the Fuse Online cluster as those templates do not contain images streams themselves but refer to the image streams installed on this cluster.
+
+### Quick installation
+
+WARNING: The following scripts are not yet updated and probably don't work as expected. Please stay tuned.
+
+If you only want to install Syndesis without developing for, there is even an easier without checking out Syndesis into a local Git repository.
+
+You can directly use the standalone installation script https://raw.githubusercontent.com/syndesisio/syndesis/master/tools/bin/install-syndesis[syndesis-install] for installing Syndesis.
+Just download this https://raw.githubusercontent.com/syndesisio/syndesis/master/tools/bin/install-syndesis[script], save it as "syndesis-install" and then call it with
+
+```
+bash install-syndesis --route $(oc project -q).6a63.fuse-ignite.openshiftapps.com --open
+```
+
+Or, if you feel fancy (and trust us), then you can directly install the latest version of Syndesis by deleting and recreating the current project with a single line:
+
+```
+bash <(curl -sL https://bit.ly/syndesis-install) -p $(oc project -q) -r $(oc project -q).6a63.fuse-ignite.openshiftapps.com -o
+```
+
+All you need is to have `bash`, `curl` and `oc` installed and you need to be connected to an OpenShift cluster.
+
+Use `install-syndesis --help` for a list of options (which is a subset of `syndesis install` described above)
+

From bc6c5e269d75cd0cc0ab47908cd59b283d34c7fc Mon Sep 17 00:00:00 2001
From: kahboom <rachelyordan@gmail.com>
Date: Tue, 13 Nov 2018 16:24:01 +0000
Subject: [PATCH 18/42] Add modules table

---
 content/docs/cli.md | 14 +++++++++++++-
 1 file changed, 13 insertions(+), 1 deletion(-)

diff --git a/content/docs/cli.md b/content/docs/cli.md
index b5a44e0f..1b29ee93 100644
--- a/content/docs/cli.md
+++ b/content/docs/cli.md
@@ -190,6 +190,18 @@ are also option to combine modules
 
 The following modules are available:
 
+| Module      | Description | `--all-images` | `--backend` | `--app-images` | `--infra-images` |
+| ----------- | ----------- | -------------- | ----------- | -------------- | ---------------- |
+| server      |  |  |  |  |  |
+| ui          |  |  |  |  |  |
+| meta        |  |  |  |  |  |
+| connector   |  |  |  |  |  |
+| integration |  |  |  |  |  |
+| extension   |  |  |  |  |  |
+| common      |  |  |  |  |  |
+| s21         |  |  |  |  |  |
+| operator    |  |  |  |  |  |
+
 |===
 | Module | Description | `--all-images` | `--backend` | `--app-images` | `--infra-images`
 
@@ -316,7 +328,7 @@ There are three modes, how the operator can be created:
 
 See below for the details.
 
-.Load dependencies
+<i class="title">Load Dependencies</i>
 
 In any case, before you compile first you should use the option `--ensure` (short: `-e`) to setup the dependency tree.
 This will download all source dependency and cache them locally.

From d95e5f8f9642ab91366d6f1e8fa7e7299dd2ed30 Mon Sep 17 00:00:00 2001
From: kahboom <rachelyordan@gmail.com>
Date: Tue, 13 Nov 2018 16:26:19 +0000
Subject: [PATCH 19/42] Fix table

---
 content/docs/cli.md | 83 +++++----------------------------------------
 1 file changed, 9 insertions(+), 74 deletions(-)

diff --git a/content/docs/cli.md b/content/docs/cli.md
index 1b29ee93..93bcec5f 100644
--- a/content/docs/cli.md
+++ b/content/docs/cli.md
@@ -192,81 +192,16 @@ The following modules are available:
 
 | Module      | Description | `--all-images` | `--backend` | `--app-images` | `--infra-images` |
 | ----------- | ----------- | -------------- | ----------- | -------------- | ---------------- |
-| server      |  |  |  |  |  |
-| ui          |  |  |  |  |  |
-| meta        |  |  |  |  |  |
-| connector   |  |  |  |  |  |
-| integration |  |  |  |  |  |
-| extension   |  |  |  |  |  |
-| common      |  |  |  |  |  |
-| s21         |  |  |  |  |  |
-| operator    |  |  |  |  |  |
+| server      | Main backend providing a REST API for the user interface | ✔︎ | ✔︎ | ✔︎ |  |
+| ui          | The SPA user interface application | ✔︎ |  | ✔︎ |  |
+| meta        | Meta data and verifier used for verifying connections and providing connector metadata | ✔︎ | ✔︎ | ✔︎ |  |
+| connector   | All connectors used by Syndesis out of the box |  | ✔︎ |  |  |
+| integration | Support libraries for running integrations |  | ✔︎ |  |  |
+| extension   | Tools for developing and running Syndesis custom extensions |  | ✔︎ |  |  |
+| common      | Common modules containing common code |  | ✔︎ |  |  |
+| s21         | S2I base image used for building the runtime images | ✔︎ |  | ✔︎ |  |
+| operator    | Infrastructure operator for managing the application | ✔︎ |  |  | ✔︎ |
 
-|===
-| Module | Description | `--all-images` | `--backend` | `--app-images` | `--infra-images`
-
-| **server**
-| Main backend providing a REST API for the user interface
-| ✔︎
-| ✔︎
-| ✔︎
-|
-
-| **ui**
-| The SPA user interface application
-| ✔︎
-|
-| ✔︎
-|
-
-| **meta**
-| Meta data and verifier used for verifying connections and providing connector metadata
-| ✔︎
-| ✔︎
-| ✔︎
-|
-
-| **connector**
-| All connectors used by Syndesis out of the box
-|
-| ✔︎
-|
-|
-
-| **integration**
-| Support libraries for running integrations
-|
-| ✔︎
-|
-|
-
-| **extension**
-| Tools for developing and running Syndesis custom extensions
-|
-| ✔︎
-|
-|
-
-| **common**
-| Common modules containing common code
-|
-| ✔︎
-|
-|
-
-| **s2i**
-| S2I base image used for building the runtime images
-| ✔︎
-|
-| ✔︎
-|
-
-| **operator**
-| Infrastructure operator for managing the application
-| ✔︎
-|
-|
-| ✔︎
 
 All option ending with `-images` will also build the corresponding Docker image.
 

From 7025d693438fdbf552d3f9a160db5d861b0aeb8f Mon Sep 17 00:00:00 2001
From: kahboom <rachelyordan@gmail.com>
Date: Tue, 13 Nov 2018 16:27:45 +0000
Subject: [PATCH 20/42] Fix table, though eventually should only hide empty
 cells in thead

---
 content/docs/cli.md | 18 +++++++++---------
 1 file changed, 9 insertions(+), 9 deletions(-)

diff --git a/content/docs/cli.md b/content/docs/cli.md
index 93bcec5f..2065a333 100644
--- a/content/docs/cli.md
+++ b/content/docs/cli.md
@@ -192,15 +192,15 @@ The following modules are available:
 
 | Module      | Description | `--all-images` | `--backend` | `--app-images` | `--infra-images` |
 | ----------- | ----------- | -------------- | ----------- | -------------- | ---------------- |
-| server      | Main backend providing a REST API for the user interface | ✔︎ | ✔︎ | ✔︎ |  |
-| ui          | The SPA user interface application | ✔︎ |  | ✔︎ |  |
-| meta        | Meta data and verifier used for verifying connections and providing connector metadata | ✔︎ | ✔︎ | ✔︎ |  |
-| connector   | All connectors used by Syndesis out of the box |  | ✔︎ |  |  |
-| integration | Support libraries for running integrations |  | ✔︎ |  |  |
-| extension   | Tools for developing and running Syndesis custom extensions |  | ✔︎ |  |  |
-| common      | Common modules containing common code |  | ✔︎ |  |  |
-| s21         | S2I base image used for building the runtime images | ✔︎ |  | ✔︎ |  |
-| operator    | Infrastructure operator for managing the application | ✔︎ |  |  | ✔︎ |
+| server      | Main backend providing a REST API for the user interface | ✔︎ | ✔︎ | ✔︎ | &nbsp; |
+| ui          | The SPA user interface application | ✔︎ | &nbsp; | ✔︎ | &nbsp; |
+| meta        | Meta data and verifier used for verifying connections and providing connector metadata | ✔︎ | ✔︎ | ✔︎ | &nbsp; |
+| connector   | All connectors used by Syndesis out of the box | &nbsp; | ✔︎ | &nbsp; | &nbsp; |
+| integration | Support libraries for running integrations | &nbsp; | ✔︎ | &nbsp; | &nbsp; |
+| extension   | Tools for developing and running Syndesis custom extensions | &nbsp; | ✔︎ | &nbsp; | &nbsp; |
+| common      | Common modules containing common code | &nbsp; | ✔︎ | &nbsp; | &nbsp; |
+| s21         | S2I base image used for building the runtime images | ✔︎ | &nbsp; | ✔︎ | &nbsp; |
+| operator    | Infrastructure operator for managing the application | ✔︎ | &nbsp; | &nbsp; | ✔︎ |
 
 
 All option ending with `-images` will also build the corresponding Docker image.

From ab143be676e748d6d3d1d65862f0bd06e4c70248 Mon Sep 17 00:00:00 2001
From: kahboom <rachelyordan@gmail.com>
Date: Wed, 14 Nov 2018 12:50:36 +0000
Subject: [PATCH 21/42] Reformat minishift, ui, build to md

---
 content/docs/cli.md             | 496 ++++++++++++++++----------------
 themes/syndesis/scss/_docs.scss |   7 +
 2 files changed, 260 insertions(+), 243 deletions(-)

diff --git a/content/docs/cli.md b/content/docs/cli.md
index 2065a333..4e259cb8 100644
--- a/content/docs/cli.md
+++ b/content/docs/cli.md
@@ -133,212 +133,225 @@ yourscriptname::run() {
 
 The primary goal of `syndesis build` is to build Syndesis.
 
-It is mainly a wrapper around Maven and Go but adds some convenience functionality for common developer workflows.
+It is mainly a wrapper around Maven and Go but adds some convenience
+functionality for common developer workflows.
 
 ### Usage
 
-Usage: syndesis build [... options ...]
-
-Options for build:
-
-    -b  --backend                  Build only backend modules (core, extension, integration,
-                                   connectors, server, meta)
-        --all-images               Build all modules with images: ui, server, meta, s2i, operator
-        --app-images               Build only application modules with Docker images
-                                   (ui, server, meta, s2i)
-                                   and create images
-        --infra-images             Build only infrastructure modules with Docker images
-                                   (operator) and create images
-    -m  --module <m1>,<m2>, ..     Build modules
-                                   Modules: ui, server, connector, s2i, meta, integration,
-                                   extension, common, operator
-    -d  --dependencies             Build also all project the specified module depends on
-        --skip-tests               Skip unit and system test execution
-        --skip-checks              Disable all checks
-    -f  --flash                    Skip checks and tests execution (fastest mode)
-    -i  --image                    Build Docker images, too
-                                   (for those modules creating images)
-        --docker                   Use a plain Docker build for creating images.
-                                   Used by CI for pushing to Docker Hub
-    -p  --project <project>        Specifies the project/namespace to create images in
-    -e  --ensure                   If building the operator, run 'dep ensure' before building.
-                                   Otherwise ignored.
-    -l  --local                    If building the operator, use a locally installed go
-                                   Otherwise run the Go build from a container
-                                   (either local or Minishift's Docker daemon)
-        --clean-cache              Used for the operator build to remove the local dependency cache.
-    -c  --clean                    Run clean builds (mvn clean)
-        --resume <m1>              Resume build from maven module (mvn -rf m1)
-        --batch-mode               Run mvn in batch mode
-        --camel-snapshot <version> Run a build with a specific Camel snapshot.
-                                   If no argument is given the
-                                   environment variable CAMEL_SNAPSHOT_VERSION is used or an error thrown.
-----
+    Usage: syndesis build [... options ...]
+    
+    Options for build:
+        -b  --backend                  Build only backend modules (core, extension, integration,
+                                       connectors, server, meta)
+            --all-images               Build all modules with images: ui, server, meta, s2i, operator
+            --app-images               Build only application modules with Docker images
+                                       (ui, server, meta, s2i)
+                                       and create images
+            --infra-images             Build only infrastructure modules with Docker images
+                                       (operator) and create images
+        -m  --module <m1>,<m2>, ..     Build modules
+                                       Modules: ui, server, connector, s2i, meta, integration,
+                                       extension, common, operator
+        -d  --dependencies             Build also all project the specified module depends on
+            --skip-tests               Skip unit and system test execution
+            --skip-checks              Disable all checks
+        -f  --flash                    Skip checks and tests execution (fastest mode)
+        -i  --image                    Build Docker images, too
+                                       (for those modules creating images)
+            --docker                   Use a plain Docker build for creating images.
+                                       Used by CI for pushing to Docker Hub
+        -p  --project <project>        Specifies the project/namespace to create images in
+        -e  --ensure                   If building the operator, run 'dep ensure' before building.
+                                       Otherwise ignored.
+        -l  --local                    If building the operator, use a locally installed go
+                                       Otherwise run the Go build from a container
+                                       (either local or Minishift's Docker daemon)
+            --clean-cache              Used for the operator build to remove the local dependency cache.
+        -c  --clean                    Run clean builds (mvn clean)
+            --resume <m1>              Resume build from maven module (mvn -rf m1)
+            --batch-mode               Run mvn in batch mode
+            --camel-snapshot <version> Run a build with a specific Camel snapshot.
+                                       If no argument is given the
+                                       environment variable CAMEL_SNAPSHOT_VERSION is used or an error thrown.
 
 ### Modules
-A plain `build` command without any options performs a plain `mvn install` for all Java and UI modules.
-Plus it also builds the infrastructure operator via Go (see <<below,syndesis-build-operator>> for details)
 
-This compiles all Java and Javascript artefacts and also runs all tests and code checks for the application modules.
+A plain `build` command without any options performs a plain `mvn
+install` for all Java and UI modules. Plus it also builds the
+infrastructure operator via Go (see [syndesis-build-operator](#below)
+for details)
 
-You restrict the build to certain modules, which are divided into two categories: _application modules_ which are the modules building up Syndesis.
-And _infrastructure modules_ which help in managing the application itself.
+This compiles all Java and Javascript artefacts and also runs all tests
+and code checks for the application modules.
 
-You can individually select specific modules by using the `--module` (short: `-m`) option with a comma-separated list of modules, but there
-are also option to combine modules
-
-
-The following modules are available:
-
-| Module      | Description | `--all-images` | `--backend` | `--app-images` | `--infra-images` |
-| ----------- | ----------- | -------------- | ----------- | -------------- | ---------------- |
-| server      | Main backend providing a REST API for the user interface | ✔︎ | ✔︎ | ✔︎ | &nbsp; |
-| ui          | The SPA user interface application | ✔︎ | &nbsp; | ✔︎ | &nbsp; |
-| meta        | Meta data and verifier used for verifying connections and providing connector metadata | ✔︎ | ✔︎ | ✔︎ | &nbsp; |
-| connector   | All connectors used by Syndesis out of the box | &nbsp; | ✔︎ | &nbsp; | &nbsp; |
-| integration | Support libraries for running integrations | &nbsp; | ✔︎ | &nbsp; | &nbsp; |
-| extension   | Tools for developing and running Syndesis custom extensions | &nbsp; | ✔︎ | &nbsp; | &nbsp; |
-| common      | Common modules containing common code | &nbsp; | ✔︎ | &nbsp; | &nbsp; |
-| s21         | S2I base image used for building the runtime images | ✔︎ | &nbsp; | ✔︎ | &nbsp; |
-| operator    | Infrastructure operator for managing the application | ✔︎ | &nbsp; | &nbsp; | ✔︎ |
-
-
-All option ending with `-images` will also build the corresponding Docker image.
+You restrict the build to certain modules, which are divided into two
+categories: *application modules* which are the modules building up
+Syndesis. And *infrastructure modules* which help in managing the
+application itself.
 
-When you build individual modules you you can provide the option `--image` (short: `-i`) to create also the Docker image in the build, when the module is associated with a Docker image.
-
-By default images are build via S2I against a running Minishift.
-This is the recommended way for developing as this automatically will trigger a redeployment after the build.
-However, for certain scenarios like when used in a CI system or when doing the release, the image creation can be done against are Docker daemon when the `--docker` is given.
-For this to work you must have access to Docker daemon, which you can verify with `docker ps`.
+You can individually select specific modules by using the `--module`
+(short: `-m`) option with a comma-separated list of modules, but there
+are also option to combine modules
 
-When the option `--dependencies` (short: `-d`) is given in addition to `--modules`, also all Maven modules which the specified modules depend on are build, too.
+The following modules are
+available:
+
+| Module          | Description                                                                            | `--all-images` | `--backend` | `--app-images` | `--infra-images` |
+| --------------- | -------------------------------------------------------------------------------------- | -------------- | ----------- | -------------- | ---------------- |
+| **server**      | Main backend providing a REST API for the user interface                               | ✔︎             | ✔︎          | ✔︎             |                  |
+| **ui**          | The SPA user interface application                                                     | ✔︎             |             | ✔︎             |                  |
+| **meta**        | Meta data and verifier used for verifying connections and providing connector metadata | ✔︎             | ✔︎          | ✔︎             |                  |
+| **connector**   | All connectors used by Syndesis out of the box                                         |                | ✔︎          |                |                  |
+| **integration** | Support libraries for running integrations                                             |                | ✔︎          |                |                  |
+| **extension**   | Tools for developing and running Syndesis custom extensions                            |                | ✔︎          |                |                  |
+| **common**      | Common modules containing common code                                                  |                | ✔︎          |                |                  |
+| **s2i**         | S2I base image used for building the runtime images                                    | ✔︎             |             | ✔︎             |                  |
+| **operator**    | Infrastructure operator for managing the application                                   | ✔︎             |             |                | ✔︎               |
+
+All option ending with `-images` will also build the corresponding
+Docker image.
+
+When you build individual modules you you can provide the option
+`--image` (short: `-i`) to create also the Docker image in the build,
+when the module is associated with a Docker image.
+
+By default images are build via S2I against a running Minishift. This is
+the recommended way for developing as this automatically will trigger a
+redeployment after the build. However, for certain scenarios like when
+used in a CI system or when doing the release, the image creation can be
+done against are Docker daemon when the `--docker` is given. For this to
+work you must have access to Docker daemon, which you can verify with
+`docker ps`.
+
+When the option `--dependencies` (short: `-d`) is given in addition to
+`--modules`, also all Maven modules which the specified modules depend
+on are build, too.
 
 ### Tuning
-By default, all checks like license or code quality checks are performed.
-Also, all unit and local integration tests are run.
-A full build eats up quite some time, but you should always run at full blast before submitting a pull request.
-
-However, to speed up the turnaround, several speed-up options are available.
-The following table shows these options, and also how long a full clean build over all modules takes: (but without building images)
-
-|===
-|Option
-|Description
-|Time
-
-| _none_
-| Default mode with all checks and tests
-|
 
-| `--skip-tests`
-| Skip all unit and local integration tests
-|
+By default, all checks like license or code quality checks are
+performed. Also, all unit and local integration tests are run. A full
+build eats up quite some time, but you should always run at full blast
+before submitting a pull request.
 
-| `--skip-checks`
-| Skip sanity checks like for correct license headers and
-|
+However, to speed up the turnaround, several speed-up options are
+available. The following table shows these options, and also how long a
+full clean build over all modules takes: (but without building
+images)
 
-
-| `--flash`
-| Fastest mode with skipping all checks and tests and with even some other aggressive optimizations
-|
-
-| `--camel-snapshot <version>`
-| Sometimes it's needed to use a Camel snapshot version for building. This snapshot most be available in you local Maven repo (`~/.m2`) Use this option with the Camel version. Alternatively, you can also set the environment variable `CAMEL_SNAPSHOT` to the corresponding version.
-|===
+| Option          | Description                                                                                       | Time |
+| --------------- | ------------------------------------------------------------------------------------------------- | ---- |
+| *none*          | Default mode with all checks and tests                                                            |      |
+| `--skip-tests`  | Skip all unit and local integration tests                                                         |      |
+| `--skip-checks` | Skip sanity checks like for correct license headers and                                           |      |
+| `--flash`       | Fastest mode with skipping all checks and tests and with even some other aggressive optimizations |      |
 
 ### Infrastructure Operator
 
-`syndesis build` can also build the infrastructure operator, which is a golang program.
+`syndesis build` can also build the infrastructure operator, which is a
+golang program.
 
-You can build the operator by running `syndesis build -m operator` or
-as part of a module collection like `--all-images` or `--infra-images`
+You can build the operator by running `syndesis build -m operator` or as
+part of a module collection like `--all-images` or `--infra-images`
 
 There are three modes, how the operator can be created:
 
-* Running you go compiler locally
-* Compiling in a local Docker daemon which allows volume mounts with the localhost
-* Compiling in Minishift Docker daemon, which was made accessible via `eval $(minishift docker-env)`
+  - Running you go compiler locally
+
+  - Compiling in a local Docker daemon which allows volume mounts with
+    the localhost
+
+  - Compiling in Minishift Docker daemon, which was made accessible via
+    `eval $(minishift docker-env)`
 
 See below for the details.
 
-<i class="title">Load Dependencies</i>
+**Load dependencies.**
 
-In any case, before you compile first you should use the option `--ensure` (short: `-e`) to setup the dependency tree.
-This will download all source dependency and cache them locally.
-To get rid of this cache, use the option `--clean-cache`.
-This might be necessary when `go dep` 's cache gets into a weird state.
+In any case, before you compile first you should use the option
+`--ensure` (short: `-e`) to setup the dependency tree. This will
+download all source dependency and cache them locally. To get rid of
+this cache, use the option `--clean-cache`. This might be necessary when
+`go dep` 's cache gets into a weird state.
 
-If you compile for the first time, then `--ensure` will be added automatically.
+If you compile for the first time, then `--ensure` will be added
+automatically.
 
-.Compiling locally
+**Compiling locally.**
 
-This is the fastest way for compiling the operator.
-Use the option `--local` (short: `-l`) for selecting the local compile mode.
+This is the fastest way for compiling the operator. Use the option
+`--local` (short: `-l`) for selecting the local compile mode.
 
-It is also the recommended way when you are working on the operator.
-You project setup needs to fit however: The main project directory must be reachable as `$GOPATH/src/github.com/syndesisio/syndesis`.
-You can either move your project directory to this location or work with a symlink:
+It is also the recommended way when you are working on the operator. You
+project setup needs to fit however: The main project directory must be
+reachable as `$GOPATH/src/github.com/syndesisio/syndesis`. You can
+either move your project directory to this location or work with a
+symlink:
 
-----
+``` shell
 cd ~/Development/syndesis
 mkdir -p $GOPATH/src/github.com/syndesisio
 cd ..
 mv syndesis $GOPATH/src/github.com/syndesisio/
 ln -s $GOPATH/src/github.com/syndesisio/ syndesis
-----
-
-By default this compiles into for your native architecture (amd64, darwin).
-When you use this mode with `--image` (short: `-i`) on macOS then go will be used as cross compiler so that the generated bimary can be used in a Linux image.
+```
 
-.Compiling with a local Docker daemon
+By default this compiles into for your native architecture (amd64,
+darwin). When you use this mode with `--image` (short: `-i`) on macOS
+then go will be used as cross compiler so that the generated bimary can
+be used in a Linux image.
 
-This is the default mode and is used also when doing the release.
-It use a builder image `syndesis/godev` which is created from the `tools/image` directory and fetched from Docker Hub.
+**Compiling with a local Docker daemon.**
 
-For this mode to work your Docker daemon must support volume mounts to the system from where you are calling `syndesis`.
-This is the case on Linux for locally installed Docker daemon and for Mac with _Docker for Mac_.
-It is *not* the case for Minishift which runs in a disconnected VM.
-But see below how you still can use Minishift for building.
+This is the default mode and is used also when doing the release. It use
+a builder image `syndesis/godev` which is created from the `tools/image`
+directory and fetched from Docker Hub.
 
-`dep ensure` and `go build` will be run from this `syndesis/godev` image, but with your local directory mounted into the container so that the fetched dependencies can be cached in the local directories `dep-cache` and `vendor` so that the can be reused for the next run.
-Also the binary will be stored in your local directory, but this will alway be a Linux (`amd64`) binary.
+For this mode to work your Docker daemon must support volume mounts to
+the system from where you are calling `syndesis`. This is the case on
+Linux for locally installed Docker daemon and for Mac with *Docker for
+Mac*. It is **not** the case for Minishift which runs in a disconnected
+VM. But see below how you still can use Minishift for building.
 
-.Compiling with Minishift
+`dep ensure` and `go build` will be run from this `syndesis/godev`
+image, but with your local directory mounted into the container so that
+the fetched dependencies can be cached in the local directories
+`dep-cache` and `vendor` so that the can be reused for the next run.
+Also the binary will be stored in your local directory, but this will
+alway be a Linux (`amd64`) binary.
 
-As Minishift is running in a remote VM you cannot bind a volume to your localhost. Therefor when running in Minishift mode the source code will be rsynced to a directory in the Minishift VM (`rsync` will be installed in the Minishift VM on the first run).
+**Compiling with Minishift.**
 
-The build with `syndesis/godev` will then be started with a volume mount to the copied directory in the VM.
-After the build the generated binary is copied back with `rsync` to your local directory.
+As Minishift is running in a remote VM you cannot bind a volume to your
+localhost. Therefor when running in Minishift mode the source code will
+be rsynced to a directory in the Minishift VM (`rsync` will be installed
+in the Minishift VM on the first run).
 
-The Minishift mode is automatically detected and selected if `DOCKER_CERTS` contains a path to `.minishift`.
-You enable the Minishift Docker daemon for your local CLI with `eval $(minishift docker-env)`
+The build with `syndesis/godev` will then be started with a volume mount
+to the copied directory in the VM. After the build the generated binary
+is copied back with `rsync` to your local directory.
 
-Some simple benchmark reveals the following timings (in minutes) :
+The Minishift mode is automatically detected and selected if
+`DOCKER_CERTS` contains a path to `.minishift`. You enable the Minishift
+Docker daemon for your local CLI with `eval $(minishift docker-env)`
 
-|===
-| Context | Local | Local Docker (macOS) | Minishift Docker
+Some simple benchmark reveals the following timings (in minutes)
+:
 
-| Cold (no build cache)
-| 0:40
-| 10:09
-| 1:36
+| Context               | Local | Local Docker (macOS) | Minishift Docker |
+| --------------------- | ----- | -------------------- | ---------------- |
+| Cold (no build cache) | 0:40  | 10:09                | 1:36             |
+| Hot (with dep cache)  | 0:08  | 2:47                 | 0:13             |
 
-| Hot (with dep cache)
-| 0:08
-| 2:47
-| 0:13
-|===
-
-The fastest mode is obviously the local mode, followed surprisingly by Minishift.
-The local mode is probably slow because of how the macOS daemon mounts ts volumes (which can probably be optimized)
+The fastest mode is obviously the local mode, followed surprisingly by
+Minishift. The local mode is probably slow because of how the macOS
+daemon mounts ts volumes (which can probably be optimized)
 
 ### Examples
 
 Some common usage examples for `syndesis build` are
 
-```
+``` shell
 # Build all images (app and infrastructure) with S2I
 syndesis build --all-images
 
@@ -348,7 +361,7 @@ syndesis build --all-images
 syndesis build --app-images --flash
 
 # Create the infrastructure operator by running go locally
-# and calling `dep ensure before`
+# and calling dep ensure before
 syndesis build -m operator --local --ensure
 
 # Use a Camel snapshot for a clean build, build all modules
@@ -356,6 +369,7 @@ syndesis build --clean --camel-snapshot 2.21.0-SNAPSHOT
 ```
 
 
+
 ## syndesis ui
 
 "syndesis ui" is not implemented yet
@@ -370,109 +384,106 @@ Nevertheless we already start to document the feature for an "UX first" approach
 
 ## syndesis minishift
 
-With `syndesis minishift` you can adequately manage a https://www.openshift.org/minishift/[minishift] installation for hosting Syndesis.
-This command is especially useful for a simple and self-contained development workflow.
+With `syndesis minishift` you can adequately manage a
+[minishift](https://www.openshift.org/minishift/) installation for
+hosting Syndesis. This command is especially useful for a simple and
+self-contained development workflow.
 
-`syndesis minishift` requires that you have a current minishift in your path.
-You can download it directly from https://github.com/minishift/minishift/releases[GitHub].
+`syndesis minishift` requires that you have a current minishift in your
+path. You can download it directly from
+[GitHub](https://github.com/minishift/minishift/releases).
 
 ### Usage
 
-```
---install                 Install templates to a running Minishift.
--p  --project             Install into this project.
-                          Delete this project if it already exists.
-                          By default, install into the current project (without deleting)
--c  --context             Install into this context. Default is 'minishift'
---reset                   Reset and initialize the minishift installation by
-                          'minishift delete && minishift start'.
---full-reset              Full reset and initialie by
-                          'minishift stop && rm -rf ~/.minishift/* && minishift start'
---memory <mem>            How much memory to use when doing a reset. Default: 4912
---cpus <nr cpus>          How many CPUs to use when doing a reset. Default: 2
---disk-size <size>        How many disk space to use when doing a reset. Default: 20GB
---vm-driver <driver>      Which virtual machine driver to use (depends on OS)
---show-logs               Show minishift logs during startup
---openshift-version <ver> Set OpenShift version to use when reseting (default: v3.9.0)
---tag <tag>               Syndesis version/tag to install. If not given, then the latest
-                          version from master is installed
---local                   Use the local resource files instead of fetching them from GitHub
--o  --open                Open Syndesis in the browser
--y  --yes                 Assume 'yes' automatically when asking for deleting
-                          a given project.
---memory-server <mem>     Memory limit to set for syndesis-server. Specify as "800Mi"
---memory-meta <mem>       Memory limit to set for syndesis-meta. Specify as "512Mi"
---test-support            Allow test support endpoint for syndesis-server
---man                     Open HTML documentation in the Syndesis Developer Handbook
-```
+    --install                 Install templates to a running Minishift.
+    -p  --project             Install into this project.
+                              Delete this project if it already exists.
+                              By default, install into the current project (without deleting)
+    -c  --context             Install into this context. Default is 'minishift'
+    --reset                   Reset and initialize the minishift installation by
+                              'minishift delete && minishift start'.
+    --full-reset              Full reset and initialie by
+                              'minishift stop && rm -rf ~/.minishift/* && minishift start'
+    --memory <mem>            How much memory to use when doing a reset. Default: 4912
+    --cpus <nr cpus>          How many CPUs to use when doing a reset. Default: 2
+    --disk-size <size>        How many disk space to use when doing a reset. Default: 20GB
+    --vm-driver <driver>      Which virtual machine driver to use (depends on OS)
+    --show-logs               Show minishift logs during startup
+    --openshift-version <ver> Set OpenShift version to use when reseting (default: v3.9.0)
+    --tag <tag>               Syndesis version/tag to install. If not given, then the latest
+                              version from master is installed
+    --local                   Use the local resource files instead of fetching them from GitHub
+    -o  --open                Open Syndesis in the browser
+    -y  --yes                 Assume 'yes' automatically when asking for deleting
+                              a given project.
+    --memory-server <mem>     Memory limit to set for syndesis-server. Specify as "800Mi"
+    --memory-meta <mem>       Memory limit to set for syndesis-meta. Specify as "512Mi"
+    --test-support            Allow test support endpoint for syndesis-server
+    --man                     Open HTML documentation in the Syndesis Developer Handbook
 
 ### Installing Syndesis
 
-You can easily install Syndesis with the option `--install`.
-This option triggers the creation of all relevant OpenShift resources objects in the currently connected OpenShift project.
+You can easily install Syndesis with the option `--install`. This option
+triggers the creation of all relevant OpenShift resources objects in the
+currently connected OpenShift project.
 
-If you want to use a different project, then use `--project` (short: `-p`) to specify this project.
+If you want to use a different project, then use `--project` (short:
+`-p`) to specify this project.
 
-WARNING: Any existing project will be deleted first when specified with `--project`. This option is also an easy and quick way to recreate a Syndesis installation.
+> **Warning**
+> 
+> Any existing project will be deleted first when specified with
+> `--project`. This option is also an easy and quick way to recreate a
+> Syndesis installation.
 
 ### Resetting Minishift
 
-The quickest way to get a fresh Syndesis setup is to use `--project` which will install Syndesis into a clean, new project.
-
-However, you can also recreate the whole Minishift installation with `--reset`. This will delete the Minishift VM (`minishift delete`) and create a new one (`minishift start`).
-It doesn't harm if the Minishift VM does not exist so that you can use `--reset` also on a fresh Minishift installation.
-
-If you want to get a real clean installation use `--full-reset` which deletes the `~/.minishift` directory which holds downloaded artefacts like the ISO image for the Minishift VM.
-Using `--full-reset` forces Minishift to re-download all those files.
-
-There are several options which influence the re-creation of the VM:
-
+The quickest way to get a fresh Syndesis setup is to use `--project`
+which will install Syndesis into a clean, new project.
 
-| Option
-| Description
-| Default
+However, you can also recreate the whole Minishift installation with
+`--reset`. This will delete the Minishift VM (`minishift delete`) and
+create a new one (`minishift start`). It doesn’t harm if the Minishift
+VM does not exist so that you can use `--reset` also on a fresh
+Minishift installation.
 
-|`--memory`
-| Memory to use for the Minishift VM.
-| 4 GB
+If you want to get a real clean installation use `--full-reset` which
+deletes the `~/.minishift` directory which holds downloaded artefacts
+like the ISO image for the Minishift VM. Using `--full-reset` forces
+Minishift to re-download all those files.
 
-|`--cpus`
-| Number of CPUs used for the Minishift VM.
-| 2
+There are several options which influence the re-creation of the
+VM:
 
-|`--disk-size`
-| Disk space used for Minishift.
-| 20 GB
+| Option                | Description                                                                                                      | Default |
+| --------------------- | ---------------------------------------------------------------------------------------------------------------- | ------- |
+| `--memory`            | Memory to use for the Minishift VM.                                                                              | 4 GB    |
+| `--cpus`              | Number of CPUs used for the Minishift VM.                                                                        | 2       |
+| `--disk-size`         | Disk space used for Minishift.                                                                                   | 20 GB   |
+| `--show-logs`         | Whether to show OpenShift logs during startup.                                                                   | false   |
+| `--vm-driver`         | Which virtual machine driver to use. For OS X this can be 'virtualbox', 'xhyve' or 'vmwarefusion' (if insalled). |         |
+| `--openshift-version` | OpenShift version to use                                                                                         | 3.7.1   |
 
-|`--show-logs`
-| Whether to show OpenShift logs during startup.
-| false
+### Example
 
-|`--vm-driver`
-| Which virtual machine driver to use. For OS X this can be 'virtualbox', 'xhyve' or 'vmwarefusion' (if insalled).
-|
+This short example performs the following actions:
 
-|`--openshift-version`
-| OpenShift version to use
-| 3.7.1
+  - Stops and deletes a running Minishift VM (if existent)
 
+  - Removes `~/.minishift` (if existent)
 
-### Example
+  - Install Syndesis in OpenShift modes (S2I builds & image streams) in
+    project `syndesis`
 
-This short example performs the following actions:
+  - Open Syndesis UI in the default browser
 
-* Stops and deletes a running Minishift VM (if existent)
-* Removes `~/.minishift` (if existent)
-* Install Syndesis in OpenShift modes (S2I builds & image streams) in project `syndesis`
-* Open Syndesis UI in the default browser
+<!-- end list -->
 
-```
-# Complete fresh installation in project "syndesis"
-syndesis minishift --full-reset --install --project syndesis
-
-# Open Syndesis in default browser
-syndesis minishift -o
-```
+    # Complete fresh installation in project "syndesis"
+    syndesis minishift --full-reset --install --project syndesis
+    
+    # Open Syndesis in default browser
+    syndesis minishift -o
 
 
 ## syndesis system-test
@@ -511,17 +522,16 @@ Dev commands are useful helpers for developing Syndesis
 
 ### Usage
 
-```
-Usage: syndesis dev [... options ...]
-
-Options for dev:
-    --debug <name>            Setup a port forwarding to <name> pod (default: server)
-```
-
-This command enable port-forwarding of port 5005 from a specific pod (by default: "server") to port 5005 on the localhost.
-You then can point your Java IDE to port 5005 on localhost for connecting for remote debugging.
-As argument to `--debug` "server", "meta" and "atlasmap" can be used, which are our Java based services.
+    Usage: syndesis dev [... options ...]
+    
+    Options for dev:
+        --debug <name>            Setup a port forwarding to <name> pod (default: server)
 
+This command enable port-forwarding of port 5005 from a specific pod (by
+default: "server") to port 5005 on the localhost. You then can point
+your Java IDE to port 5005 on localhost for connecting for remote
+debugging. As argument to `--debug` "server", "meta" and "atlasmap" can
+be used, which are our Java based services.
 
 ## syndesis doc
 
diff --git a/themes/syndesis/scss/_docs.scss b/themes/syndesis/scss/_docs.scss
index fa867547..49582018 100644
--- a/themes/syndesis/scss/_docs.scss
+++ b/themes/syndesis/scss/_docs.scss
@@ -11,6 +11,13 @@
 @import "highlighting";
 
 .docs {
+    h2 {
+        font-size: 1.75rem;
+    }
+
+    h3 {
+        font-size: 1.3rem;
+    }
   p i {
     &.title {
       color: $pf-blue;

From ae0a5938fb36285f6688e0dbba7ecbc426370640 Mon Sep 17 00:00:00 2001
From: kahboom <rachelyordan@gmail.com>
Date: Wed, 14 Nov 2018 12:54:29 +0000
Subject: [PATCH 22/42] Reformat syndesis dev for md

---
 content/docs/cli.md | 1 +
 1 file changed, 1 insertion(+)

diff --git a/content/docs/cli.md b/content/docs/cli.md
index 4e259cb8..45b19110 100644
--- a/content/docs/cli.md
+++ b/content/docs/cli.md
@@ -533,6 +533,7 @@ your Java IDE to port 5005 on localhost for connecting for remote
 debugging. As argument to `--debug` "server", "meta" and "atlasmap" can
 be used, which are our Java based services.
 
+
 ## syndesis doc
 
 This command is used to generated and manage this documentation which you are currently reading.

From 1e71ba5d3d83caa7857cc9123a62832dfcc7868a Mon Sep 17 00:00:00 2001
From: kahboom <rachelyordan@gmail.com>
Date: Wed, 14 Nov 2018 12:55:19 +0000
Subject: [PATCH 23/42] Reformat syndesis_doc for md

---
 content/docs/cli.md | 91 +++++++++++++++++++++------------------------
 1 file changed, 43 insertions(+), 48 deletions(-)

diff --git a/content/docs/cli.md b/content/docs/cli.md
index 45b19110..e8b8a918 100644
--- a/content/docs/cli.md
+++ b/content/docs/cli.md
@@ -536,63 +536,58 @@ be used, which are our Java based services.
 
 ## syndesis doc
 
-This command is used to generated and manage this documentation which you are currently reading.
-
+This command is used to generated and manage this documentation which
+you are currently reading.
 
 ### Usage
 
-```
-Usage: syndesis doc [... options ...]
-
-Options for doc:
--d  --directory <dir>         Top-level dir holding doc source and output directory. Default: "doc/sdh"
--i  --input <file>            Input file to use. Default: "index.adoc"
-    --out <dir>               Directory to generate files (default: "output")
-    --html                    Generate HTML pages
-    --pdf <out>               Generate PDF and write it to <out> (default: "sdh.pdf")
-    --epub <out>              Generate Epub and write it to <out> (default: "sdh.epub")
-    --gh-pages <msg>          Create everything into the gh-pages branch and commit with <msg>
--o  --open                    Open HTML documentation in default browser after doc generation
--l  --local                   Use locally installed commands instead of Docker image
-```
-
-`syndesis doc` uses by default a Docker container to create the documentation.
-Therefore a Docker daemon must be accessible, and it must allow https://docs.docker.com/engine/admin/volumes/bind-mounts/[bind volume mounts] to the local `doc/sdh` directory.
-Bind mounts are possible for Linux Docker daemons and for "Docker for Mac".
-But it is not the case for the Minishift exposed Docker daemon, as this daemon is running isolated in a VM.
-
-You can always run `asciidoctor` locally with the `--local` (short: `-l`) options. See the https://asciidoctor.org/#installation[Asciidoctor manual] for more information how to install Asciidoctor.
-
+    Usage: syndesis doc [... options ...]
+    
+    Options for doc:
+    -d  --directory <dir>         Top-level dir holding doc source and output directory. Default: "doc/sdh"
+    -i  --input <file>            Input file to use. Default: "index.adoc"
+        --out <dir>               Directory to generate files (default: "output")
+        --html                    Generate HTML pages
+        --pdf <out>               Generate PDF and write it to <out> (default: "sdh.pdf")
+        --epub <out>              Generate Epub and write it to <out> (default: "sdh.epub")
+        --gh-pages <msg>          Create everything into the gh-pages branch and commit with <msg>
+    -o  --open                    Open HTML documentation in default browser after doc generation
+    -l  --local                   Use locally installed commands instead of Docker image
+
+`syndesis doc` uses by default a Docker container to create the
+documentation. Therefore a Docker daemon must be accessible, and it must
+allow [bind volume
+mounts](https://docs.docker.com/engine/admin/volumes/bind-mounts/) to
+the local `doc/sdh` directory. Bind mounts are possible for Linux Docker
+daemons and for "Docker for Mac". But it is not the case for the
+Minishift exposed Docker daemon, as this daemon is running isolated in a
+VM.
+
+You can always run `asciidoctor` locally with the `--local` (short:
+`-l`) options. See the [Asciidoctor
+manual](https://asciidoctor.org/#installation) for more information how
+to install Asciidoctor.
 
 ### Output
 
-Input and output has the same defaults but can be changed with the following options
-
-[cols="4,3,15"]
-|===
-|`--input <file>`
-|`-i <file>`
-| Input document in Asciidoc format which is by default `$SYNDESIS_DIR/doc/sdh/index.adoc`
-
-
-| `--output <dir>`
-| `-o <dir>`
-| Output directory, default is `$SYNDESIS_DIR/doc/sdh/output`
-|===
-
-By default `syndesis doc` creates the documentation in HTML format, but more formats are supported:
+Input and output has the same defaults but can be changed with the
+following
+options
 
-[cols="3,15"]
-|===
-| `--html`
-| Create HTML documentation in the output directory
+|                  |             |                                                                                          |
+| ---------------- | ----------- | ---------------------------------------------------------------------------------------- |
+| `--input <file>` | `-i <file>` | Input document in Asciidoc format which is by default `$SYNDESIS_DIR/doc/sdh/index.adoc` |
+| `--output <dir>` | `-o <dir>`  | Output directory, default is `$SYNDESIS_DIR/doc/sdh/output`                              |
 
-|`--pdf <name>`
-| Create PDF documentation. `<name>` is optional, but when given, then this specifies the file name generated in the output directory. By default `sdh.pdf` is used.
+By default `syndesis doc` creates the documentation in HTML format, but
+more formats are
+supported:
 
-|`--epub <name>`
-| Create the documentation in Epub format. `<name>` is optional, but when given, then this specifies the file name generated in the output directory. By default `sdh.epub` is used.
-|===
+|                 |                                                                                                                                                                                    |
+| --------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `--html`        | Create HTML documentation in the output directory                                                                                                                                  |
+| `--pdf <name>`  | Create PDF documentation. `<name>` is optional, but when given, then this specifies the file name generated in the output directory. By default `sdh.pdf` is used.                 |
+| `--epub <name>` | Create the documentation in Epub format. `<name>` is optional, but when given, then this specifies the file name generated in the output directory. By default `sdh.epub` is used. |
 
 
 ## syndesis release

From f5eefbd73792bfa66a02fc1ef6791806e23a5151 Mon Sep 17 00:00:00 2001
From: kahboom <rachelyordan@gmail.com>
Date: Wed, 14 Nov 2018 12:57:00 +0000
Subject: [PATCH 24/42] Reformat syndesis_release for md

---
 content/docs/cli.md | 456 +++++++++++++++++++++++++++-----------------
 1 file changed, 282 insertions(+), 174 deletions(-)

diff --git a/content/docs/cli.md b/content/docs/cli.md
index e8b8a918..5f1da639 100644
--- a/content/docs/cli.md
+++ b/content/docs/cli.md
@@ -592,96 +592,119 @@ supported:
 
 ## syndesis release
 
-Use `syndesis release` for performing a release of Syndesis.
-A Syndesis release consists of:
+Use `syndesis release` for performing a release of Syndesis. A Syndesis
+release consists of:
 
-* Maven artefacts of the backend and runtime services
-* Docker images pushed to Docker Hub
-* A set of OpenShift templates referencing these images
+  - Maven artefacts of the backend and runtime services
 
-This chapter describes how you can efficiently perform a release and
-how to troubleshoot if something goes wrong.
-This documentation might also be interesting to you even when you do not perform a release on your own, as it might help you to understand how the various Syndesis artefacts fit together.
+  - Docker images pushed to Docker Hub
 
+  - A set of OpenShift templates referencing these images
 
-### Usage
-
+This chapter describes how you can efficiently perform a release and how
+to troubleshoot if something goes wrong. This documentation might also
+be interesting to you even when you do not perform a release on your
+own, as it might help you to understand how the various Syndesis
+artefacts fit together.
 
-Perform a release
-
-This command performs a release but does *no* automated rollback when something fails.
-Please refer to the manual at https://docs.syndesis.io for more details and what needs
-to be cleaned up in case of a failure.
+### Usage
 
-```
-Usage: syndesis release [... options ...]
-
-Options for release:
--n  --dry-run                 Dry run, which performs the whole build but does no tagging,
-                              artefact upload or pushing Docker images
-    --release-version <ver>   Version to release (e.g. "1.2.1"). This is a mandatory argument.
-    --snapshot-release        Snapshot release which can be created on a daily basis.
-                              A timestamped version will be created automatically, and no Maven artefacts
-                              are pushed to maven central. No moving tag will be moved, too.
-    --dev-version <version>   Next development version. If not given, set to
-                              "<major>.<minor>-SNAPSHOT" as calculated from
-                              --release-version (e.g. "1.2-SNAPSHOT")
-    --settings <file>         Path to a custom settings.xml to use for the release.
-                              This file must contain all the credentials to be used for Sonatype.
-                              By default ~/.m2/settings.xml is used.
-    --local-maven-repo <dir>  Local dir for holding the local Maven repo cache.
-                              If not given, then a new
-                              temporary directory will be used
-                              (and removed after the release)
-    --docker-user <user>      Docker user for Docker Hub
-    --docker-password <pwd>   Docker password for Docker Hub
-    --no-git-push             Don't push the release tag (and symbolic major.minor tag)
-    --git-remote              Name of the git remote to push to. If not given, its trying to be pushed
-                              to the git remote to which the currently checked out branch is attached to.
-                              Works only when on a branch, not when checked out directly.
-
-    --log <log-file>          Write full log to <log-file>, only print progress to screen
-    --man                     Open HTML documentation in the Syndesis Developer Handbook
+    Perform a release
+    
+    This command performs a release but does no automated rollback when something fails.
+    Please refer to the manual at https://docs.syndesis.io for more details and what needs
+    to be cleaned up in case of a failure.
+    
+    Usage: syndesis release [... options ...]
+    
+    Options for release:
+    -n  --dry-run                 Dry run, which performs the whole build but does no tagging,
+                                  artefact upload or pushing Docker images
+        --release-version <ver>   Version to release (e.g. "1.2.1"). This is a mandatory argument.
+        --snapshot-release        Snapshot release which can be created on a daily basis.
+                                  A timestamped version will be created automatically, and no Maven artefacts
+                                  are pushed to maven central. No moving tag will be moved, too.
+        --dev-version <version>   Next development version. If not given, set to
+                                  "<major>.<minor>-SNAPSHOT" as calculated from
+                                  --release-version (e.g. "1.2-SNAPSHOT")
+        --settings <file>         Path to a custom settings.xml to use for the release.
+                                  This file must contain all the credentials to be used for Sonatype.
+                                  By default ~/.m2/settings.xml is used.
+        --local-maven-repo <dir>  Local dir for holding the local Maven repo cache.
+                                  If not given, then a new
+                                  temporary directory will be used
+                                  (and removed after the release)
+        --docker-user <user>      Docker user for Docker Hub
+        --docker-password <pwd>   Docker password for Docker Hub
+        --no-git-push             Don't push the release tag (and symbolic major.minor tag)
+        --git-remote              Name of the git remote to push to. If not given, its trying to be pushed
+                                  to the git remote to which the currently checked out branch is attached to.
+                                  Works only when on a branch, not when checked out directly.
+    
+        --log <log-file>          Write full log to <log-file>, only print progress to screen
+        --man                     Open HTML documentation in the Syndesis Developer Handbook
+
+A lot of output is produced during a release. If you are only interested
+to see the major steps only, then you can use `--log` to redirect the
+output to a specific log file. This log file will contain all output
+(and if you add `--verbose` you see even more output), but on the
+console you will only see the current step that is actually performed.
+
+**Example**
+
+An example run for a dry run for `1.3.1` release on the current branch
+look like:
+
+``` bash
+./tools/bin/syndesis release           \ 
+    --release-version 1.3.1            \ 
+    --local-maven-repo /tmp/clean-repo \ 
+    --log /tmp/build.log               \ 
+    --dry-run                            
 ```
 
-A lot of output is produced during a release.
-If you are only interested to see the major steps only, then you
-can use `--log` to redirect the output to a specific log file.
-This log file will contain all output (and if you add `--verbose` you see even more output), but on the console you will only see the current step that is actually performed.
+  - Always run `syndesis` from the repo and branch you want to release.
 
-.Example
-An example run for a dry run for `1.3.1` release on the current branch look like:
+  - The release version is mandatory and must be in the format
+    `<major>.<minor>.<patch>`.
 
-```
-./tools/bin/syndesis release           \ <1>
-    --release-version 1.3.1            \ <2>
-    --local-maven-repo /tmp/clean-repo \ <3>
-    --log /tmp/build.log               \ <4>
-    --dry-run                            <5>
-```
+  - Use a clean local Maven repository to avoid side effects
 
-<1> Always run `syndesis` from the repo and branch you want to release.
-<2> The release version is mandatory and must be in the format `<major>.<minor>.<patch>`.
-<3> Use a clean local Maven repository to avoid side effects
-<4> Redirect the full output to `/tmp/build.log` but still print the main steps to the console.
-<5> Make only a dry run, without pushing any artefacts out nor checking in any changed files.
+  - Redirect the full output to `/tmp/build.log` but still print the
+    main steps to the console.
+
+  - Make only a dry run, without pushing any artefacts out nor checking
+    in any changed files.
 
 ### Preparations
 
 To perform a release, certain preconditions need to be given.
 
-First of all, you need to have access to the various systems to which release artefacts are uploaded:
+First of all, you need to have access to the various systems to which
+release artefacts are uploaded:
 
-* You need to be logged in to https://hub.docker.com/[Docker Hub] and your account needs to have write access to the https://hub.docker.com/u/syndesis/[syndesis] Docker Hub organisation.
-* You have `gpg` to have installed and set up a gpg-agent for being able to sign Maven artefacts during deployment in a non-interactive mode.
-* You need to have access to the "syndesis" account on (http://oss.sonatype.org/)[oss.sonatype.org] for being able to publish Maven artefacts.
-This credential needs to be added to either your `~/.m2/settings.xml` or you can use an settings file with the `--settings-xml` option.
-The credential needs to be added to the server with the id `oss-sonatype-staging`.
+  - You need to be logged in to [Docker Hub](https://hub.docker.com/)
+    and your account needs to have write access to the
+    [syndesis](https://hub.docker.com/u/syndesis/) Docker Hub
+    organisation.
 
-You have to perform the release from a locally checked out Syndesis repository, which can be either checkout from a branch like `1.2.x` for a patch release or directly from `master`.
-It is highly recommended to run the release directly from a freshly checked out directory:
+  - You have `gpg` to have installed and set up a gpg-agent for being
+    able to sign Maven artefacts during deployment in a non-interactive
+    mode.
 
-```
+  - You need to have access to the "syndesis" account on
+    ([oss.sonatype.org](http://oss.sonatype.org/\)) for being able to
+    publish Maven artefacts. This credential needs to be added to either
+    your `~/.m2/settings.xml` or you can use an settings file with the
+    `--settings-xml` option. The credential needs to be added to the
+    server with the id `oss-sonatype-staging`.
+
+You have to perform the release from a locally checked out Syndesis
+repository, which can be either checkout from a branch like `1.2.x` for
+a patch release or directly from `master`. It is highly recommended to
+run the release directly from a freshly checked out directory:
+
+``` bash
 # Go to a temporary directory
 cd /tmp
 
@@ -708,144 +731,229 @@ cd ..
 rm -rf syndesis
 ```
 
-Please note that you should always call `syndesis` out of the branch for which the release is for.
-If there is an issue due to bugs in the release script itself, please fix them on the branch with the usual developer process (i.e. opening a PR request).
-`syndesis release` must always work for the branch where this script is, too.
+Please note that you should always call `syndesis` out of the branch for
+which the release is for. If there is an issue due to bugs in the
+release script itself, please fix them on the branch with the usual
+developer process (i.e. opening a PR request). `syndesis release` must
+always work for the branch where this script is, too.
 
 ### Release steps
 
-A release consist of several different steps, which can be grouped into two groups:
-
-* *Build steps* are performed to build the release and create the artefacts.
-Also during the build Maven artefacts are uploaded to the staging area for publishing to Maven central
-* *Persist steps* are then used for releasing objects, pushing Docker images to Docker Hub, committing and tagging in Git (but only when the build steps have been performed successfully).
-
-#### Build steps
-
-* Check whether the current local Git clone is _clean_, i.e. that is does not have any modified files.
-The script will abort if this is the case.
-* Update the versions of all `pom.xml` files below `app/` to the version given with `--release-version`.
-If no `--release-version` is given, then the script aborts.
-* Run an `mvn clean install` to verify that the build is not broken and all tests succeed.
-* Re-generate the OpenShift templates in `install` so that the image streams included in these templates refer to Docker images with the new version.
-* Now run an `mvn -Prelease clean deploy` to deploy all artefacts to a new staging repository on oss.sonatype.org, the platform for release artefacts on Maven central.
-The staging repository on this Sonatype Nexus is validated and closed.
-* If `--docker-user` and `--docker-password` is given, then a `docker login` is performed.
-Otherwise, it is assumed that the user is already logged in.
-* The Docker images are created with `mvn -Prelease,image package` in the `server`, `meta`, `ui` and `s2i` modules.
-
-If the option `--dry-run` (short: `-n`) is provided, the script drops the staging repository at Sonatype and stops.
-You should examine the generated files and before starting a real build, reset the repository (`git reset --hard`).
-
-The builds are using a clean local Maven repository, which otherwise is usually taken from `~/.m2/repository`.
-This new local cache should ensure that we have a completely fresh build without interference from previous builds store in the local Maven cache in the home directory.
-You can provide such a directory with `--local-maven-repo` which will be taken directly (so it's good if you have to perform multiple runs like with `--dry-run`).
-If not provided, a new temporary directory is created and also _deleted_ after the release run.
-
-#### Persist steps
-
-* Push Docker images to Docker Hub.
-In addition to the images that carry the full release version as the tag, also a tag for the _minor version_ is attached and pushed.
-E.g. when the release version is `1.2.8`, then the minor version is `1.2`.
-If this minor version tag already exists on Docker Hub, its moved to the newly created version.
-* The staging repository on Sonatype is released.
-It will take a bit, but the artefact should then be downloadable from https://search.maven.org/[Maven central] soon after.
-* Commit all modified local files to the local Git repo.
-* Create a Git tag for the release version (e.g. `git tag 1.2.8`).
+A release consist of several different steps, which can be grouped into
+two groups:
+
+  - **Build steps** are performed to build the release and create the
+    artefacts. Also during the build Maven artefacts are uploaded to the
+    staging area for publishing to Maven central
+
+  - **Persist steps** are then used for releasing objects, pushing
+    Docker images to Docker Hub, committing and tagging in Git (but only
+    when the build steps have been performed successfully).
+
+**Build steps**
+
+  - Check whether the current local Git clone is *clean*, i.e. that is
+    does not have any modified files. The script will abort if this is
+    the case.
+
+  - Update the versions of all `pom.xml` files below `app/` to the
+    version given with `--release-version`. If no `--release-version` is
+    given, then the script aborts.
+
+  - Run an `mvn clean install` to verify that the build is not broken
+    and all tests succeed.
+
+  - Re-generate the OpenShift templates in `install` so that the image
+    streams included in these templates refer to Docker images with the
+    new version.
+
+  - Now run an `mvn -Prelease clean deploy` to deploy all artefacts to a
+    new staging repository on oss.sonatype.org, the platform for release
+    artefacts on Maven central. The staging repository on this Sonatype
+    Nexus is validated and closed.
+
+  - If `--docker-user` and `--docker-password` is given, then a `docker
+    login` is performed. Otherwise, it is assumed that the user is
+    already logged in.
+
+  - The Docker images are created with `mvn -Prelease,image package` in
+    the `server`, `meta`, `ui` and `s2i` modules.
+
+If the option `--dry-run` (short: `-n`) is provided, the script drops
+the staging repository at Sonatype and stops. You should examine the
+generated files and before starting a real build, reset the repository
+(`git reset --hard`).
+
+The builds are using a clean local Maven repository, which otherwise is
+usually taken from `~/.m2/repository`. This new local cache should
+ensure that we have a completely fresh build without interference from
+previous builds store in the local Maven cache in the home directory.
+You can provide such a directory with `--local-maven-repo` which will be
+taken directly (so it’s good if you have to perform multiple runs like
+with `--dry-run`). If not provided, a new temporary directory is created
+and also *deleted* after the release run.
+
+**Persist steps**
+
+  - Push Docker images to Docker Hub. In addition to the images that
+    carry the full release version as the tag, also a tag for the *minor
+    version* is attached and pushed. E.g. when the release version is
+    `1.2.8`, then the minor version is `1.2`. If this minor version tag
+    already exists on Docker Hub, its moved to the newly created
+    version.
+
+  - The staging repository on Sonatype is released. It will take a bit,
+    but the artefact should then be downloadable from [Maven
+    central](https://search.maven.org/) soon after.
+
+  - Commit all modified local files to the local Git repo.
+
+  - Create a Git tag for the release version (e.g. `git tag 1.2.8`).
 
 The next steps are for creating templates for the minor version:
 
-* In `install` create new templates which contain image streams that reference images with the minor version (e.g. `syndesis/syndesis-server:1.3` for a release version of 1.3.8).
-* Commit those generated templates
-* Tag it with the minor version (e.g. `1.2`), overwriting an already existing minor version tag
+  - In `install` create new templates which contain image streams that
+    reference images with the minor version (e.g.
+    `syndesis/syndesis-server:1.3` for a release version of 1.3.8).
 
-Next, we are switching back to the next development version of the pom.xml files.
-This version can be given with `--dev-version`, but by default, it is calculated automatically as `<minor.version>-SNAPSHOT` (e.g. `1.2-SNAPSHOT`).
-This new version is then committed to the local git repository.
+  - Commit those generated templates
 
-Finally, the tags just created on the local Git repo is pushed to the remote repository.
-You can omit this with the option `--no-git-push`.
-If to so, the last step can also be performed manually afterwards with:
+  - Tag it with the minor version (e.g. `1.2`), overwriting an already
+    existing minor version tag
 
-```
-git push 1.2.8
-git push -f 1.2 <1>
-```
-<1> Using `-f` as the minor tag needs to be moved.
+Next, we are switching back to the next development version of the
+pom.xml files. This version can be given with `--dev-version`, but by
+default, it is calculated automatically as `<minor.version>-SNAPSHOT`
+(e.g. `1.2-SNAPSHOT`). This new version is then committed to the local
+git repository.
 
-Please be careful to *not* push the master branch upstream (i.e. do *not* a plain `git push`).
-We only want to have the tag with all the release preparation steps, not on the branch so that pull requests can be still be easily rebased with out conflict because of the temporary version changes.
+Finally, the tags just created on the local Git repo is pushed to the
+remote repository. You can omit this with the option `--no-git-push`. If
+to so, the last step can also be performed manually afterwards with:
 
-### Minor Version Templates
+``` bash
+git push 1.2.8
+git push -f 1.2 
+```
 
-What is now the thing with this _minor version_?
-Why is the needed and how does it work?
+  - Using `-f` as the minor tag needs to be moved.
 
-Syndesis follows a https://semver.org/[semantic versioning] approach.
-So, patch level releases (i.e. all releases which only change the last digit in 1.2.8) are fully compatible with all other patch level versions.
-In order to allow easy bug fix upgrades, we also create a tag which contains only the version parts up to the minor version (e.g. 1.2).
-These tags *always* points to the latest full version of its minor version.
-If, e.g. 1.2.8 is the latest 1.2.x version, then the tag 1.2 point to this 1.2.8 version.
-Corresponding to these Docker image variants, there exist two OpenShift templates variants:
+Please be careful to **not** push the master branch upstream (i.e. do
+**not** a plain `git push`). We only want to have the tag with all the
+release preparation steps, not on the branch so that pull requests can
+be still be easily rebased with out conflict because of the temporary
+version changes.
 
-* One set of templates directly references the Docker images which its full version, e.g. `syndesis/syndesis-ui:1.2.8`.
-Applying such a template will keep your application at precisely this patch-level.
-You would have to update your templates and recreate your applications if you want to upgrade.
-* The other set of templates references images only via its minor version, e.g. `syndesis/syndesis-ui:1.2`.
-Using these templates has the advantage that application created from these templates automatically benefit from patch releases.
-The templates contain an image change trigger which will redeploy the application if the images change.
-So when we release the next patch level release, moving the minor version tag to this patch level release, then the application gets automatically redeployed, and it will pick up the new image.
+### Minor Version Templates
 
-These two sets of templates can be reached directly from GitHub as the git tags correspond to the Docker tags (i.e. a `1.2.8` tag and a `1.2` tag which will be moved forward).
+What is now the thing with this *minor version*? Why is the needed and
+how does it work?
+
+Syndesis follows a [semantic versioning](https://semver.org/) approach.
+So, patch level releases (i.e. all releases which only change the last
+digit in 1.2.8) are fully compatible with all other patch level
+versions. In order to allow easy bug fix upgrades, we also create a tag
+which contains only the version parts up to the minor version (e.g.
+1.2). These tags **always** points to the latest full version of its
+minor version. If, e.g. 1.2.8 is the latest 1.2.x version, then the tag
+1.2 point to this 1.2.8 version. Corresponding to these Docker image
+variants, there exist two OpenShift templates variants:
+
+  - One set of templates directly references the Docker images which its
+    full version, e.g. `syndesis/syndesis-ui:1.2.8`. Applying such a
+    template will keep your application at precisely this patch-level.
+    You would have to update your templates and recreate your
+    applications if you want to upgrade.
+
+  - The other set of templates references images only via its minor
+    version, e.g. `syndesis/syndesis-ui:1.2`. Using these templates has
+    the advantage that application created from these templates
+    automatically benefit from patch releases. The templates contain an
+    image change trigger which will redeploy the application if the
+    images change. So when we release the next patch level release,
+    moving the minor version tag to this patch level release, then the
+    application gets automatically redeployed, and it will pick up the
+    new image.
+
+These two sets of templates can be reached directly from GitHub as the
+git tags correspond to the Docker tags (i.e. a `1.2.8` tag and a `1.2`
+tag which will be moved forward).
 
 ### Snapshot Release
 
-With the option `--snapshot-release` a lightweight snapshot release for the images and templates can be created.
-The tag/version is calculated automatically by picking up the latest release number (e.g. 1.3.5), increasing the patch-level by
- one and adding a daily timestamp (e.g. 1.3.6-20180419).
-According to  https://semver.org/[Semantic Versioning 2.0] this is considered to be a version larger than 1.3.5 but https://semver.org/#spec-item-11[smaller] than 1.3.6.
+With the option `--snapshot-release` a lightweight snapshot release for
+the images and templates can be created. The tag/version is calculated
+automatically by picking up the latest release number (e.g. 1.3.5),
+increasing the patch-level by one and adding a daily timestamp (e.g.
+1.3.6-20180419). According to [Semantic
+Versioning 2.0](https://semver.org/) this is considered to be a version
+larger than 1.3.5 but [smaller](https://semver.org/#spec-item-11) than
+1.3.6.
 
-This tag can be referenced to in `syndesis install` and `syndesis minishift`.
+This tag can be referenced to in `syndesis install` and `syndesis
+minishift`.
 
 In detail, a snapshot release differs from a normal release as it:
 
-* ... doesn't release artefacts on Maven central, but pushes Docker images and creates a Git tag for referencing the proper templates.
-* ... skips all checks and tests when building to maximise the likelihood that the release succeeds. The rationale here is to better have untested daily snapshot release than no snapshot release because of test failure (which in many cases are not because of errors, but of failure in the infrastructure)
-* ... force pushes the snapshot tag on GitHub so that multiple releases per day are allowed
+  - …​ doesn’t release artefacts on Maven central, but pushes Docker
+    images and creates a Git tag for referencing the proper templates.
 
-.Example
+  - …​ skips all checks and tests when building to maximise the
+    likelihood that the release succeeds. The rationale here is to
+    better have untested daily snapshot release than no snapshot release
+    because of test failure (which in many cases are not because of
+    errors, but of failure in the infrastructure)
 
-```
+  - …​ force pushes the snapshot tag on GitHub so that multiple releases
+    per day are allowed
+
+**Example**
+
+``` bash
 syndesis release \
-     --snapshot-release \                   <1>
-     --local-maven-repo /tmp/clean-repo \   <2>
-     --git-remote origin \                  <3>
-     --docker-user "${DOCKER_USER}" \       <4>
+     --snapshot-release \                   
+     --local-maven-repo /tmp/clean-repo \   
+     --git-remote origin \                  
+     --docker-user "${DOCKER_USER}" \       
      --docker-password "${DOCKER_PASSWORD}"
 ```
 
-<1> Enable snapshot release with a version in the format 1.3.5-20180419
-<2> Point to an empty repository to avoid side effects when building
-<3> Push to the origin repository
-<4> Docker credentials required for pushing to Docker Hub
+  - Enable snapshot release with a version in the format 1.3.5-20180419
 
-A daily Jenkins job with this configuration run on https://ci.fabric8.io for creating a daily snapshots.
+  - Point to an empty repository to avoid side effects when building
+
+  - Push to the origin repository
+
+  - Docker credentials required for pushing to Docker Hub
+
+A daily Jenkins job with this configuration run on
+<https://ci.fabric8.io> for creating a daily snapshots.
 
 ### Troubleshooting
 
-When you run the `syndesis release` command and when it should not succeed, you might have to perform some cleanup steps yourself
-(there is now automatic rollback).
-However, care has been taken to move all persistent changes to the end of the release flow, so if something breaks early, you only need to clean up locally.
-If the process fails before the step _=== Pushing Docker images_ you only need to:
+When you run the `syndesis release` command and when it should not
+succeed, you might have to perform some cleanup steps yourself (there is
+now automatic rollback). However, care has been taken to move all
+persistent changes to the end of the release flow, so if something
+breaks early, you only need to clean up locally. If the process fails
+before the step *=== Pushing Docker images* you only need to:
+
+  - Reset your local git repo with `git reset --hard`
+
+  - Potentially remove the create staging repository on
+    `http://oss.sonatype.org/` (but it doesn’t harm if it is not cleaned
+    up immediately).
+
+After pushing the Docker images, it should be improbable that things go
+wrong. But these things should take care of if this should be the case:
 
-* Reset your local git repo with `git reset --hard`
-* Potentially remove the create staging repository on `http://oss.sonatype.org/` (but it doesn't harm if it is not cleaned up immediately).
+  - Remove Docker Hub tags for the pushed images, which is best done on
+    the Docker Hub Web UI
 
-After pushing the Docker images, it should be improbable that things go wrong.
-But these things should take care of if this should be the case:
+  - Revert your local git commits to the point before the release. If
+    you did this on a fresh checked out repo (as recommended), you just
+    could delete the whole clone.
 
-* Remove Docker Hub tags for the pushed images, which is best done on the Docker Hub Web UI
-* Revert your local git commits to the point before the release. If you did this on a fresh checked out repo (as recommended), you just could delete the whole clone.
 
 
 ## syndesis install

From 632e72909e2660d3a6d1e5e5bf6bfb0079afd52e Mon Sep 17 00:00:00 2001
From: kahboom <rachelyordan@gmail.com>
Date: Wed, 14 Nov 2018 12:58:16 +0000
Subject: [PATCH 25/42] Reformat syndesis_install for md

---
 content/docs/cli.md | 250 ++++++++++++++++++++++++++------------------
 1 file changed, 151 insertions(+), 99 deletions(-)

diff --git a/content/docs/cli.md b/content/docs/cli.md
index 5f1da639..981e84e8 100644
--- a/content/docs/cli.md
+++ b/content/docs/cli.md
@@ -958,92 +958,109 @@ wrong. But these things should take care of if this should be the case:
 
 ## syndesis install
 
-With `syndesis install` you can install Syndesis to an arbitrary OpenShift cluster.
-If you want to install to https://www.openshift.org/minishift/[Minishift] the <<syndesis-minishift,syndesis minishift>> command is recommended as it supports some additional features specific to Minishift.
+With `syndesis install` you can install Syndesis to an arbitrary
+OpenShift cluster. If you want to install to
+[Minishift](https://www.openshift.org/minishift/) the [syndesis
+minishift](#syndesis-minishift) command is recommended as it supports
+some additional features specific to
+    Minishift.
 
 ### Usage
 
-```
--s  --setup               Install CRDs clusterwide. Use --grant if you want a specific user to be
-                          able to install Syndesis. You have to run this option once as
-                          cluster admin.
--u  --grant <user>        Add permissions for the given user so that user can install
-                          the operator in her projects. Must be run as cluster admin.
-    --cluster             Add the permission for all projects in the cluster
-                          (only when used together with --grant)
--p  --project             Install into this project. Delete this project
-                          if it already exists. By default, install into the current project
-                          (without deleting)
-    --operator-only       Only install the operator but no resource
-    --route               Route to use. If not given, the route is trying to be detected
-                          from the currently connected cluster.
-    --console             The URL to the OpenShift console
-    --tag <tag>           Syndesis version/tag to install. If not given, then the latest
-                          version from master is installed
-    --dev                 Prepare for development of Syndesis so that S2I builds of
-                          Syndesis images are picked up properly (implies --watch)
-    --force               Override an existing "Syndesis" if present
--w  --watch               Wait until cluster is up
-    --local               install from local Git repo when using. By default the
-                          resource descriptor is downloaded from GitHub remotely.
--o  --open                Open Syndesis in browser when installation is ready (implies --watch)
--y  --yes                 Assume 'yes' automatically when asking for deleting
-                          a given project.
-    --memory-server <mem> Memory limit to set for syndesis-server. Specify as "800Mi"
-    --memory-meta <mem>   Memory limit to set for syndesis-meta. Specify as "512Mi"
-    --test-support        Allow test support endpoint for syndesis-server
-
-You have to run `--setup --grant <user>` as a cluster-admin before you can
-install Fuse Online as a user.
-```
+    -s  --setup               Install CRDs clusterwide. Use --grant if you want a specific user to be
+                              able to install Syndesis. You have to run this option once as
+                              cluster admin.
+    -u  --grant <user>        Add permissions for the given user so that user can install
+                              the operator in her projects. Must be run as cluster admin.
+        --cluster             Add the permission for all projects in the cluster
+                              (only when used together with --grant)
+    -p  --project             Install into this project. Delete this project
+                              if it already exists. By default, install into the current project
+                              (without deleting)
+        --operator-only       Only install the operator but no resource
+        --route               Route to use. If not given, the route is trying to be detected
+                              from the currently connected cluster.
+        --console             The URL to the OpenShift console
+        --tag <tag>           Syndesis version/tag to install. If not given, then the latest
+                              version from master is installed
+        --dev                 Prepare for development of Syndesis so that S2I builds of
+                              Syndesis images are picked up properly (implies --watch)
+        --force               Override an existing "Syndesis" if present
+    -w  --watch               Wait until cluster is up
+        --local               install from local Git repo when using. By default the
+                              resource descriptor is downloaded from GitHub remotely.
+    -o  --open                Open Syndesis in browser when installation is ready (implies --watch)
+    -y  --yes                 Assume 'yes' automatically when asking for deleting
+                              a given project.
+        --memory-server <mem> Memory limit to set for syndesis-server. Specify as "800Mi"
+        --memory-meta <mem>   Memory limit to set for syndesis-meta. Specify as "512Mi"
+        --test-support        Allow test support endpoint for syndesis-server
+    
+    You have to run --setup --grant <user> as a cluster-admin before you can
+    install Fuse Online as a user.
 
-The deployment happens to the currently connected OpenShift cluster.
-So it's mandatory that you have logged into the cluster with `oc login` before.
-You can check the status with `oc status`.
+The deployment happens to the currently connected OpenShift cluster. So
+it’s mandatory that you have logged into the cluster with `oc login`
+before. You can check the status with `oc status`.
 
 The installation process consists of two steps:
 
-* An initial setup which has to be performed as _cluster admin_ which is a one-off action which needs to be done only once.
-* Installation of Syndesis into a specific project by the _app admin_, a regular user of OpenShiftm which can be performed as many times as required.
+  - An initial setup which has to be performed as *cluster admin* which
+    is a one-off action which needs to be done only once.
+
+  - Installation of Syndesis into a specific project by the *app admin*,
+    a regular user of OpenShiftm which can be performed as many times as
+    required.
 
 ### Initial Setup
 
-In the initial setup, you have to register the custom resource definition (CRD) to allow to deploy `Syndesis` resources.
-This step has to be performed by the admin.
+In the initial setup, you have to register the custom resource
+definition (CRD) to allow to deploy `Syndesis` resources. This step has
+to be performed by the admin.
 
-Also, if you want to allow an OpenShift user to install Syndesis on her own, then you have to grant specific permissions to her.
+Also, if you want to allow an OpenShift user to install Syndesis on her
+own, then you have to grant specific permissions to her.
 
-To perform this setup step, which needs to be performed only once per cluster, you have to run `syndesis` **while being connected as a cluster admin**.
-For `minishift` use `oc login -u system:admin` if you have the `admin-user` addon enabled.
+To perform this setup step, which needs to be performed only once per
+cluster, you have to run `syndesis` **while being connected as a cluster
+admin**. For `minishift` use `oc login -u system:admin` if you have the
+`admin-user` addon enabled.
 
-```
+``` bash
 syndesis install --setup
 ```
 
-This will install only the CRD. In addition to grant a user _developer_ the proper permission to create a `Syndesis` resource, you should add `--grant <user>`:
+This will install only the CRD. In addition to grant a user *developer*
+the proper permission to create a `Syndesis` resource, you should add
+`--grant <user>`:
 
-```
+``` bash
 syndesis install --setup --grant <user>
 ```
 
-This call adds permissions to read and write `Syndesis` resource objects for the current project.
-If you would instead want to allow the user managing `Syndesis` resources in the whole cluster, you should add a
-`--cluster`.
-This cluster-wide access is especially required when you plan to use the `--project` option to use a new project or recreate the existing one, as in this case the role association to this project gets lost.
+This call adds permissions to read and write `Syndesis` resource objects
+for the current project. If you would instead want to allow the user
+managing `Syndesis` resources in the whole cluster, you should add a
+`--cluster`. This cluster-wide access is especially required when you
+plan to use the `--project` option to use a new project or recreate the
+existing one, as in this case the role association to this project gets
+lost.
 
 ### Installing Syndesis
 
-After the CRDs a registered, you can easily install Syndesis directly with
+After the CRDs a registered, you can easily install Syndesis directly
+with
 
-```
+``` bash
 syndesis install
 ```
 
-Depending on whether you have granted the current user access this step has to be done either as admin or as a regular user.
+Depending on whether you have granted the current user access this step
+has to be done either as admin or as a regular user.
 
-.Example for Minishift
+**Example for Minishift.**
 
-```
+``` bash
 # Enable the admin user on Minishift
 minishift addons enable admin-user
 
@@ -1063,75 +1080,110 @@ oc login -u developer
 syndesis install
 ```
 
+A route name can be given with `--route`. This step can be omitted as
+the operator can autodetect the route. If you provide the route
+manually, you need to check your OpenShift installation. Typically the
+route name is the name of your OpenShift project followed by the
+cluster’s hostname. E.g. a route `--route
+proj186023.6a63.fuse-ignite.openshiftapps.com` is specific to the Fuse
+Ignite test cluster `6a63.fuse-ignite.openshiftapps.com` and for the
+project `proj186023`. However, you don’t have to provide the route name.
+
+If you want to have a link to the OpenShift console to read the Pod
+logs, you have to add the `--console` option with the full URL to the
+console. Unfortunately, this cannot be autodetected. If not given, no
+link appears.
+
+By default, this commands installs Syndesis in the currently connected
+project, but you can specify an alternative project with `--project
+<project>`. If this project already exists, it gets deleted
+unconditionally before the deployment, so be careful when using this
+option. By default, you are asked whether you want to delete the project
+for recreation. You can switch off the security question with the option
+`--yes` (short: `-y`).
 
-A route name can be given with `--route`.
-This step can be omitted as the operator can autodetect the route.
-If you provide the route manually, you need to check your OpenShift installation.
-Typically the route name is the name of your OpenShift project followed by the cluster's hostname.
-E.g. a route `--route proj186023.6a63.fuse-ignite.openshiftapps.com` is specific to the Fuse Ignite test cluster `6a63.fuse-ignite.openshiftapps.com` and for the project `proj186023`.
-However, you don't have to provide the route name.
-
-If you want to have a link to the OpenShift console to read the Pod logs, you have to add the `--console` option with the full URL to the console.
-Unfortunately, this cannot be autodetected.
-If not given, no link appears.
-
-By default, this commands installs Syndesis in the currently connected project, but you can specify an alternative project with `--project <project>`.
-If this project already exists, it gets deleted unconditionally before the deployment, so be careful when using this option.
-By default, you are asked whether you want to delete the project for recreation.
-You can switch off the security question with the option `--yes` (short: `-y`).
-
-WARNING: Don't use `syndesis install --project $(oc project -q) --yes`. You'll shoot yourself into the foot. Ask the author if you want to know more details.
+> **Warning**
+> 
+> Don’t use `syndesis install --project $(oc project -q) --yes`. You’ll
+> shoot yourself into the foot. Ask the author if you want to know more
+> details.
 
-If you want to wait until everything is running (including fetching of the Docker images), you can specify `--watch` (short: `-w`) which blocks the script until everything is set up.
+If you want to wait until everything is running (including fetching of
+the Docker images), you can specify `--watch` (short: `-w`) which blocks
+the script until everything is set up.
 
-You can also automatically open Syndesis in the browser after the installation with `--open` (short: `-o`)
+You can also automatically open Syndesis in the browser after the
+installation with `--open` (short: `-o`)
 
 ### Development mode
 
-As with <<syndesis-minishift,syndesis minishift>> you can also use this command to set up a development platform for Syndesis.
-_Development platform_ here means that you can create Docker images on your own with <<syndesis-build,syndesis build>> and can use them with an automatic redeployment after the build.
+As with [syndesis minishift](#syndesis-minishift) you can also use this
+command to set up a development platform for Syndesis. *Development
+platform* here means that you can create Docker images on your own with
+[syndesis build](#syndesis-build) and can use them with an automatic
+redeployment after the build.
 
-You can switch on this mode with the option `--dev`.
-When the operator has deployed the application, the application imagestreams refer to Docker images pushed to Docker Hub.
-To change the imagestream references to the images built with `syndesis build --all-images`, these imagestreams needs to be patched after the initial images have been fetched from Docker Hub.
-If you use the `--dev` option, then this update is done automatically.
+You can switch on this mode with the option `--dev`. When the operator
+has deployed the application, the application imagestreams refer to
+Docker images pushed to Docker Hub. To change the imagestream references
+to the images built with `syndesis build --all-images`, these
+imagestreams needs to be patched after the initial images have been
+fetched from Docker Hub. If you use the `--dev` option, then this update
+is done automatically.
 
 ### Selecting the version
 
-With the option `--tag` you can select a specific version of Syndesis to install.
-By default, the currently checked out checked out branch is used.
+With the option `--tag` you can select a specific version of Syndesis to
+install. By default, the currently checked out checked out branch is
+used.
 
-.Example
+**Example.**
 
-```
+``` bash
 syndesis install --route syndesis.192.168.64.12.nip.io --tag 1.4
 ```
 
-This example installs the latest Syndesis version of the 1.4 branch to the local cluster.
+This example installs the latest Syndesis version of the 1.4 branch to
+the local cluster.
 
-You can see a list of available tags with `git tag`.
-Tags prefixed with `fuse-ignite` are suited for the Fuse Online cluster as those templates do not contain images streams themselves but refer to the image streams installed on this cluster.
+You can see a list of available tags with `git tag`. Tags prefixed with
+`fuse-ignite` are suited for the Fuse Online cluster as those templates
+do not contain images streams themselves but refer to the image streams
+installed on this cluster.
 
 ### Quick installation
 
-WARNING: The following scripts are not yet updated and probably don't work as expected. Please stay tuned.
+> **Warning**
+> 
+> The following scripts are not yet updated and probably don’t work as
+> expected. Please stay tuned.
 
-If you only want to install Syndesis without developing for, there is even an easier without checking out Syndesis into a local Git repository.
+If you only want to install Syndesis without developing for, there is
+even an easier without checking out Syndesis into a local Git
+repository.
 
-You can directly use the standalone installation script https://raw.githubusercontent.com/syndesisio/syndesis/master/tools/bin/install-syndesis[syndesis-install] for installing Syndesis.
-Just download this https://raw.githubusercontent.com/syndesisio/syndesis/master/tools/bin/install-syndesis[script], save it as "syndesis-install" and then call it with
+You can directly use the standalone installation script
+[syndesis-install](https://raw.githubusercontent.com/syndesisio/syndesis/master/tools/bin/install-syndesis)
+for installing Syndesis. Just download this
+[script](https://raw.githubusercontent.com/syndesisio/syndesis/master/tools/bin/install-syndesis),
+save it as "syndesis-install" and then call it
+with
 
-```
+``` bash
 bash install-syndesis --route $(oc project -q).6a63.fuse-ignite.openshiftapps.com --open
 ```
 
-Or, if you feel fancy (and trust us), then you can directly install the latest version of Syndesis by deleting and recreating the current project with a single line:
+Or, if you feel fancy (and trust us), then you can directly install the
+latest version of Syndesis by deleting and recreating the current
+project with a single
+line:
 
-```
+``` bash
 bash <(curl -sL https://bit.ly/syndesis-install) -p $(oc project -q) -r $(oc project -q).6a63.fuse-ignite.openshiftapps.com -o
 ```
 
-All you need is to have `bash`, `curl` and `oc` installed and you need to be connected to an OpenShift cluster.
-
-Use `install-syndesis --help` for a list of options (which is a subset of `syndesis install` described above)
+All you need is to have `bash`, `curl` and `oc` installed and you need
+to be connected to an OpenShift cluster.
 
+Use `install-syndesis --help` for a list of options (which is a subset
+of `syndesis install` described above)

From 43016450dacadf5b7bf4c236520c3dbf978c3c36 Mon Sep 17 00:00:00 2001
From: kahboom <rachelyordan@gmail.com>
Date: Wed, 14 Nov 2018 13:02:53 +0000
Subject: [PATCH 26/42] Styling changes for h3

---
 content/docs/cli.md             |  8 ++++----
 themes/syndesis/scss/_docs.scss | 19 ++++++++-----------
 2 files changed, 12 insertions(+), 15 deletions(-)

diff --git a/content/docs/cli.md b/content/docs/cli.md
index 981e84e8..5d80babd 100644
--- a/content/docs/cli.md
+++ b/content/docs/cli.md
@@ -24,7 +24,7 @@ The script can be used for various tasks which are selected by a so-called comma
 Just type `syndesis -h` to get an overview of the commands available:
 
 
-<i class="title">Usage Message</i>
+### Usage Message
 ```
 Usage: syndesis <command> [... options ...]
 
@@ -49,7 +49,7 @@ There are a handful of global options which can be used:
 | `--verbose`   | &nbsp; | Set verbose mode, which is useful mostly only for debugging the script itself. |
 
 
-<i class="title">Rebase to Upstream</i>
+### Rebase to Upstream
 
 To easily rebase on changes which have been merged upstream to master, you can use the option `--rebase` (short: `-r`).
 This command assumes that you have forked the Syndesis GitHub repositories and you have "origin" and "upstream" remotes like
@@ -72,7 +72,7 @@ With this in place, a `--rebase` performs the following steps:
   - `git stash pop` brings back your changes. Stashing can fail with conflicts which you would have to resolve on your own.
 
 
-<i class="title">Development Modes</i>
+### Development Modes
 
 The Syndesis application consists of a set of Docker images OpenShift resources descriptors for installing Syndesis.
 For development, https://www.openshift.org/minishift/[minishift] is used, and most of the commands assume that you have minishift installed locally and executable directly from your path.
@@ -83,7 +83,7 @@ This mode works also when running with a real OpenShift cluster and is not restr
 The advantage is that a build automatically triggers a redeployment, so you don't have to kill any pods manually.
 
 
-<i class="title">Commands</i>
+### Commands
 
 All other options are specific to each command.
 You get a list of those options with `syndesis <cmd> -h`.
diff --git a/themes/syndesis/scss/_docs.scss b/themes/syndesis/scss/_docs.scss
index 49582018..f6afb4c7 100644
--- a/themes/syndesis/scss/_docs.scss
+++ b/themes/syndesis/scss/_docs.scss
@@ -11,18 +11,15 @@
 @import "highlighting";
 
 .docs {
-    h2 {
-        font-size: 1.75rem;
-    }
+  h2 {
+    font-size: 1.75rem;
+  }
 
-    h3 {
-        font-size: 1.3rem;
-    }
-  p i {
-    &.title {
-      color: $pf-blue;
-      font-size: 1.1em;
-    }
+  h3 {
+    color: $pf-blue;
+    font-size: 1.1em;
+    font-style: italic;
+    padding: 25px 0 10px;
   }
 
   pre {

From 5a3df0a5c93529ad341354445e206dc42b6d69aa Mon Sep 17 00:00:00 2001
From: kahboom <rachelyordan@gmail.com>
Date: Wed, 14 Nov 2018 13:06:34 +0000
Subject: [PATCH 27/42] Adj padding for header tags

---
 themes/syndesis/scss/_docs.scss | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/themes/syndesis/scss/_docs.scss b/themes/syndesis/scss/_docs.scss
index f6afb4c7..e61a852b 100644
--- a/themes/syndesis/scss/_docs.scss
+++ b/themes/syndesis/scss/_docs.scss
@@ -13,13 +13,14 @@
 .docs {
   h2 {
     font-size: 1.75rem;
+    padding: 35px 0 10px;
   }
 
   h3 {
     color: $pf-blue;
     font-size: 1.1em;
     font-style: italic;
-    padding: 25px 0 10px;
+    padding: 15px 0 10px;
   }
 
   pre {

From fbadfe26d0401099cb292694d2b4aa59bb26f3c4 Mon Sep 17 00:00:00 2001
From: kahboom <rachelyordan@gmail.com>
Date: Wed, 14 Nov 2018 13:07:42 +0000
Subject: [PATCH 28/42] Only hide empty cells in thead

---
 themes/syndesis/scss/syndesis.scss | 8 --------
 1 file changed, 8 deletions(-)

diff --git a/themes/syndesis/scss/syndesis.scss b/themes/syndesis/scss/syndesis.scss
index 805116c5..231b1ff4 100644
--- a/themes/syndesis/scss/syndesis.scss
+++ b/themes/syndesis/scss/syndesis.scss
@@ -74,18 +74,10 @@ body {
     }
 
     th {
-      :empty {
-        display: none;
-      }
-
       font-weight: 600;
     }
 
     tr {
-      :empty {
-        display: none;
-      }
-
       background-color: #fff;
       border-top: 1px solid #c6cbd1;
       display: table-row;

From 6b376541687abe5326a13c4b20dd8a3977d5966b Mon Sep 17 00:00:00 2001
From: kahboom <rachelyordan@gmail.com>
Date: Wed, 14 Nov 2018 13:10:34 +0000
Subject: [PATCH 29/42] Fix first h2

---
 content/docs/cli.md             | 2 +-
 themes/syndesis/scss/_docs.scss | 4 ++++
 2 files changed, 5 insertions(+), 1 deletion(-)

diff --git a/content/docs/cli.md b/content/docs/cli.md
index 5d80babd..dd49e3a2 100644
--- a/content/docs/cli.md
+++ b/content/docs/cli.md
@@ -1,7 +1,6 @@
 ---
 draft: false
 title: "Syndesis CLI"
-description: "Buildtool \"syndesis\""
 sidebar: "sidenav"
 menu:
   sidenav:
@@ -12,6 +11,7 @@ toc: true
 weight: 10
 ---
 
+## Buildtool "syndesis"
 
 Syndesis uses a single tool for controlling various aspects of the build and developer related tasks.
 This script can be found in `$SYNDESIS_DIR/tools/bin` and is called `syndesis`.
diff --git a/themes/syndesis/scss/_docs.scss b/themes/syndesis/scss/_docs.scss
index e61a852b..7ed48e1d 100644
--- a/themes/syndesis/scss/_docs.scss
+++ b/themes/syndesis/scss/_docs.scss
@@ -14,6 +14,10 @@
   h2 {
     font-size: 1.75rem;
     padding: 35px 0 10px;
+
+    &:first-of-type {
+        padding: 15px 0;
+    }
   }
 
   h3 {

From e7c0e2bdf84d3941cd1c6ceec20351f17fb51479 Mon Sep 17 00:00:00 2001
From: kahboom <rachelyordan@gmail.com>
Date: Wed, 14 Nov 2018 13:15:28 +0000
Subject: [PATCH 30/42] Minor changes

---
 content/docs/cli.md             | 20 ++++++++++----------
 themes/syndesis/scss/_docs.scss |  3 +--
 2 files changed, 11 insertions(+), 12 deletions(-)

diff --git a/content/docs/cli.md b/content/docs/cli.md
index dd49e3a2..72ad703a 100644
--- a/content/docs/cli.md
+++ b/content/docs/cli.md
@@ -266,7 +266,7 @@ There are three modes, how the operator can be created:
 
 See below for the details.
 
-**Load dependencies.**
+**Load dependencies**
 
 In any case, before you compile first you should use the option
 `--ensure` (short: `-e`) to setup the dependency tree. This will
@@ -277,7 +277,7 @@ this cache, use the option `--clean-cache`. This might be necessary when
 If you compile for the first time, then `--ensure` will be added
 automatically.
 
-**Compiling locally.**
+**Compiling locally**
 
 This is the fastest way for compiling the operator. Use the option
 `--local` (short: `-l`) for selecting the local compile mode.
@@ -301,7 +301,7 @@ darwin). When you use this mode with `--image` (short: `-i`) on macOS
 then go will be used as cross compiler so that the generated bimary can
 be used in a Linux image.
 
-**Compiling with a local Docker daemon.**
+**Compiling with a local Docker daemon**
 
 This is the default mode and is used also when doing the release. It use
 a builder image `syndesis/godev` which is created from the `tools/image`
@@ -320,7 +320,7 @@ the fetched dependencies can be cached in the local directories
 Also the binary will be stored in your local directory, but this will
 alway be a Linux (`amd64`) binary.
 
-**Compiling with Minishift.**
+**Compiling with Minishift**
 
 As Minishift is running in a remote VM you cannot bind a volume to your
 localhost. Therefor when running in Minishift mode the source code will
@@ -793,7 +793,7 @@ taken directly (so it’s good if you have to perform multiple runs like
 with `--dry-run`). If not provided, a new temporary directory is created
 and also *deleted* after the release run.
 
-**Persist steps**
+**Persist Steps**
 
   - Push Docker images to Docker Hub. In addition to the images that
     carry the full release version as the tag, also a tag for the *minor
@@ -1058,7 +1058,7 @@ syndesis install
 Depending on whether you have granted the current user access this step
 has to be done either as admin or as a regular user.
 
-**Example for Minishift.**
+**Example for Minishift**
 
 ``` bash
 # Enable the admin user on Minishift
@@ -1115,7 +1115,7 @@ the script until everything is set up.
 You can also automatically open Syndesis in the browser after the
 installation with `--open` (short: `-o`)
 
-### Development mode
+### Development Mode
 
 As with [syndesis minishift](#syndesis-minishift) you can also use this
 command to set up a development platform for Syndesis. *Development
@@ -1131,13 +1131,13 @@ imagestreams needs to be patched after the initial images have been
 fetched from Docker Hub. If you use the `--dev` option, then this update
 is done automatically.
 
-### Selecting the version
+### Selecting the Version
 
 With the option `--tag` you can select a specific version of Syndesis to
 install. By default, the currently checked out checked out branch is
 used.
 
-**Example.**
+**Example**
 
 ``` bash
 syndesis install --route syndesis.192.168.64.12.nip.io --tag 1.4
@@ -1151,7 +1151,7 @@ You can see a list of available tags with `git tag`. Tags prefixed with
 do not contain images streams themselves but refer to the image streams
 installed on this cluster.
 
-### Quick installation
+### Quick Installation
 
 > **Warning**
 > 
diff --git a/themes/syndesis/scss/_docs.scss b/themes/syndesis/scss/_docs.scss
index 7ed48e1d..e51ebe69 100644
--- a/themes/syndesis/scss/_docs.scss
+++ b/themes/syndesis/scss/_docs.scss
@@ -22,8 +22,7 @@
 
   h3 {
     color: $pf-blue;
-    font-size: 1.1em;
-    font-style: italic;
+    font-size: 1.3em;
     padding: 15px 0 10px;
   }
 

From e0a04ddf7c1d661004dfb625167ecd4a9cc325d0 Mon Sep 17 00:00:00 2001
From: kahboom <rachelyordan@gmail.com>
Date: Wed, 14 Nov 2018 14:19:47 +0000
Subject: [PATCH 31/42] Fix headers in main SCSS file

---
 themes/syndesis/scss/syndesis.scss | 22 +++++++++++++++++++++-
 1 file changed, 21 insertions(+), 1 deletion(-)

diff --git a/themes/syndesis/scss/syndesis.scss b/themes/syndesis/scss/syndesis.scss
index 231b1ff4..4d0e9ca8 100644
--- a/themes/syndesis/scss/syndesis.scss
+++ b/themes/syndesis/scss/syndesis.scss
@@ -40,6 +40,25 @@ body {
     @include media-breakpoint-up(lg) {
       width: calc(100% - 214px - 314px);
     }
+
+    h2 {
+      font-size: 1.75rem;
+      padding: 35px 0 10px;
+
+      &:first-of-type {
+        padding: 15px 0;
+      }
+    }
+
+    h3 {
+      color: $pf-blue;
+      font-size: 1.3em;
+      padding: 15px 0 10px;
+    }
+
+    pre {
+      background: #f7f7f8 !important;
+    }
   }
 
   table {
@@ -60,7 +79,8 @@ body {
       vertical-align: middle;
       border-color: inherit;
 
-      th, tr {
+      th,
+      tr {
         :empty {
           display: none;
         }

From 672a0795d1f9870031405a81f42d5a4efbb259fc Mon Sep 17 00:00:00 2001
From: kahboom <rachelyordan@gmail.com>
Date: Wed, 14 Nov 2018 16:28:44 +0000
Subject: [PATCH 32/42] Minor changes

---
 config.yml             | 2 +-
 content/docs/_index.md | 2 +-
 content/docs/cli.md    | 1 +
 3 files changed, 3 insertions(+), 2 deletions(-)

diff --git a/config.yml b/config.yml
index db8b6f63..ba453c7a 100644
--- a/config.yml
+++ b/config.yml
@@ -1,5 +1,5 @@
 baseURL: "https://syndesis.io/"
-languageCode: "en-gb"
+languageCode: "en-us"
 title: "Syndesis"
 theme: "syndesis"
 canonifyURLs: true
diff --git a/content/docs/_index.md b/content/docs/_index.md
index 17d7e28f..7b2c9609 100644
--- a/content/docs/_index.md
+++ b/content/docs/_index.md
@@ -3,7 +3,7 @@ draft: false
 title: "Developer Docs"
 description: "Documentation and guides for using and/or contributing to the Syndesis project."
 sidebar: "sidenav"
-kind: doc
+kind: docs
 
 menu:
   sidenav:
diff --git a/content/docs/cli.md b/content/docs/cli.md
index 72ad703a..7920c0e1 100644
--- a/content/docs/cli.md
+++ b/content/docs/cli.md
@@ -1,6 +1,7 @@
 ---
 draft: false
 title: "Syndesis CLI"
+description: "blah"
 sidebar: "sidenav"
 menu:
   sidenav:

From 58dc44cfc786c6eb7a8aea4df4aeced85ac22520 Mon Sep 17 00:00:00 2001
From: kahboom <rachelyordan@gmail.com>
Date: Wed, 14 Nov 2018 16:35:12 +0000
Subject: [PATCH 33/42] Move index

---
 config.yml                          | 2 +-
 content/{docs/_index.md => docs.md} | 0
 content/docs/cli.md                 | 3 +--
 3 files changed, 2 insertions(+), 3 deletions(-)
 rename content/{docs/_index.md => docs.md} (100%)

diff --git a/config.yml b/config.yml
index ba453c7a..db8b6f63 100644
--- a/config.yml
+++ b/config.yml
@@ -1,5 +1,5 @@
 baseURL: "https://syndesis.io/"
-languageCode: "en-us"
+languageCode: "en-gb"
 title: "Syndesis"
 theme: "syndesis"
 canonifyURLs: true
diff --git a/content/docs/_index.md b/content/docs.md
similarity index 100%
rename from content/docs/_index.md
rename to content/docs.md
diff --git a/content/docs/cli.md b/content/docs/cli.md
index 7920c0e1..ad82118b 100644
--- a/content/docs/cli.md
+++ b/content/docs/cli.md
@@ -1,7 +1,6 @@
 ---
 draft: false
 title: "Syndesis CLI"
-description: "blah"
 sidebar: "sidenav"
 menu:
   sidenav:
@@ -182,7 +181,7 @@ install` for all Java and UI modules. Plus it also builds the
 infrastructure operator via Go (see [syndesis-build-operator](#below)
 for details)
 
-This compiles all Java and Javascript artefacts and also runs all tests
+This compiles all Java and Javascript artifacts and also runs all tests
 and code checks for the application modules.
 
 You restrict the build to certain modules, which are divided into two

From 8877fba5c5da745a2cce680f82ba70764a1d8df3 Mon Sep 17 00:00:00 2001
From: kahboom <rachelyordan@gmail.com>
Date: Wed, 14 Nov 2018 16:38:46 +0000
Subject: [PATCH 34/42] Use docs SCSS for headers

---
 themes/syndesis/scss/_docs.scss | 26 ++++++++++++++------------
 1 file changed, 14 insertions(+), 12 deletions(-)

diff --git a/themes/syndesis/scss/_docs.scss b/themes/syndesis/scss/_docs.scss
index e51ebe69..f5c0dcf4 100644
--- a/themes/syndesis/scss/_docs.scss
+++ b/themes/syndesis/scss/_docs.scss
@@ -11,22 +11,24 @@
 @import "highlighting";
 
 .docs {
-  h2 {
-    font-size: 1.75rem;
-    padding: 35px 0 10px;
+  .docBody {
+    h2 {
+      font-size: 1.75rem;
+      padding: 35px 0 10px;
 
-    &:first-of-type {
+      &:first-of-type {
         padding: 15px 0;
+      }
     }
-  }
 
-  h3 {
-    color: $pf-blue;
-    font-size: 1.3em;
-    padding: 15px 0 10px;
-  }
+    h3 {
+      color: $pf-blue;
+      font-size: 1.3em;
+      padding: 15px 0 10px;
+    }
 
-  pre {
-    background: #f7f7f8 !important;
+    pre {
+      background: #f7f7f8 !important;
+    }
   }
 }

From 9c0ab19dd6dc1fc46fea91056bce15b680ba33e2 Mon Sep 17 00:00:00 2001
From: kahboom <rachelyordan@gmail.com>
Date: Thu, 15 Nov 2018 13:49:21 +0000
Subject: [PATCH 35/42] Note to use sidebar to navigate

---
 content/docs.md | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/content/docs.md b/content/docs.md
index 7b2c9609..a1e8174f 100644
--- a/content/docs.md
+++ b/content/docs.md
@@ -16,3 +16,5 @@ menu:
 ---
 
 This handbook contain all information required for installing, running and developing Syndesis from a developer's point of view.
+
+Please use the links in the sidebar on the left to navigate the Developer Docs.
\ No newline at end of file

From 4e0914482d51787ab3f293a1b30afeac5b3e1497 Mon Sep 17 00:00:00 2001
From: kahboom <rachelyordan@gmail.com>
Date: Thu, 15 Nov 2018 14:16:56 +0000
Subject: [PATCH 36/42] Add Development section, Maven Groups

---
 content/docs/development.md                   |  72 +++++++++++++++++-
 static/images/syndesis-group-dependencies.png | Bin 0 -> 17736 bytes
 2 files changed, 70 insertions(+), 2 deletions(-)
 create mode 100644 static/images/syndesis-group-dependencies.png

diff --git a/content/docs/development.md b/content/docs/development.md
index 9016a28f..e1cf6948 100644
--- a/content/docs/development.md
+++ b/content/docs/development.md
@@ -1,7 +1,6 @@
 ---
 draft: false
 title: "Development"
-description: "Development test."
 sidebar: "sidenav"
 menu:
   sidenav:
@@ -12,4 +11,73 @@ toc: true
 weight: 20
 ---
 
-Development stuff.
+# Maven Groups
+
+Syndesis uses [Maven](http://maven.apache.org/) as build tool. Maven
+groups are used to separate the various Syndesis parts.
+
+In details Syndesis consists of the following
+groups:
+
+| Group           | Maven                     | Docker Image               | Description                                                     |
+| --------------- | ------------------------- | -------------------------- | --------------------------------------------------------------- |
+| **common**      | `io.syndesis.common`      |                            | Syndesis shared common module                                   |
+| **connector**   | `io.syndesis.connector`   |                            | Supported camel connectors                                      |
+| **rest**        | `io.syndesis.rest`        | `syndesis/syndesis-server` | REST backend for managing integrations. This is the main sever. |
+| **integration** | `io.syndesis.integration` |                            | Library used in the the integration runtimes                    |
+| **s2i**         | `io.syndesis.s2i`         | `syndesis/syndesis-s2i`    | S2I base image for building integrations                        |
+| **ui**          | `io.syndesis.ui`          | `syndesis/syndesis-ui`     | User interface SPA, talking to the REST backend                 |
+| **meta**        | `io.syndesis.meta`        | `syndesis/syndesis-meta`   | Service for connector meta-data and verification of connections |
+| **extension**   | `io.syndesis.extension`   |                            | Library and API for developing Syndesis extensions              |
+| **test**        | `io.syndesis.test`        |                            | System tests for testing the whole applications                 |
+
+**Group dependencies.**
+
+![](images/syndesis-group-dependencies.png)
+
+## Naming Conventions
+
+The following conventions are used for naming directories, modules and
+Java packages.
+
+> **Important**
+> 
+> These conventions are mandatory and should be also checked for when
+> doing pull request reviews.
+
+  - Each directory directly below `app/` is specific for a certain Maven
+    group. E.g. the directory `app/extension` is reserved for all Maven
+    modules belonging to the Maven group `io.syndesis.extension`. The
+    directory name is reflected as the last name part.
+
+  - All names (groups, modules, package) are using the **singular**
+    form. E.g. its a `io.syndesis.connector`, *not*
+    `io.syndesis.connectors`.
+
+  - Each Maven module is prefixed with the last part of the group name.
+    E.g. the directory `app/integration/api` holds a Maven module for
+    the the Maven group `io.syndesis.integration`, and the module’s
+    artefactId is `integration-api`.
+
+  - A module’s directory name is directly reflected as the last part of
+    the Maven module name. If the Maven module name consists of multiple
+    parts (e.g. artifact `integration-project-generator`), then the
+    corresponding directory is also a concatenated word (like in
+    `integration/project-generator`). Multipart names should be the
+    exception, though.
+
+  - There should be only one level deep modules, so each Maven group
+    directory holds all Maven modules flat.
+
+  - Each module has a **single** top-level package, reflecting the Maven
+    module name. E.g. for the Maven module `common-util` in group
+    `io.syndesis.common` has a single top-level package
+    `io.syndesis.common.util` This top-level package should reflect the
+    artefact name, with dashes replaced by dots.
+
+> **Note**
+> 
+> Not every module has been already transformed to this scheme. This
+> will happen step-by-step. But for new groups and modules this scheme
+> has to be followed.
+
diff --git a/static/images/syndesis-group-dependencies.png b/static/images/syndesis-group-dependencies.png
new file mode 100644
index 0000000000000000000000000000000000000000..b0c8d25cce92318f0132b1542481e164acb7e97e
GIT binary patch
literal 17736
zcmZs@by!qi^gb#o4I(X4(o#c*q>>^fT|-JYLxX^zba#t%r_|7(zyMOxT|-GXNZsw{
z_r3RipXc5`ba>9}v(G*|)_T{w-Zi1`m1J?To?|_D@Bmltt(5A62PpC2p9aQ5a3y~@
zF$;V!yGU!hd~k5|v^6t#c_3?MZw51VF*AK(;`zeT#l=yGgTv9**xtp}&KB~)!49AE
z6$R+Q*Gpa7<^R6^;DJYmkII1356-78dVj>rexeA{m&kq7coHJ;lK0_gZ+=NkI;2yz
zrZ~eD)h{~!{omJ)bD1-#l-?XHnn8B4?mua&`g0HyV>+@fQo1AqaWT&d&{)5AzNz@`
zK7>QNSA|;hH+|w~3R!nk-r0yqgSJCTQ*~FTqVyN$WOKBy?oaMH=X@hEeK}PprVrjx
zHhlj$d@0c2Wc_om^g>;4`TUaqj@9`3jknCwH~sp<zp-`8Ph&{LlN%isonIVfu&z3B
ze<Duv;&^+X$LifCBKi(WI!Dojg82SYBr@RXemws8O|@Xt$F>&V#=w$VMrrM>u*k1-
zLMzoF6Yo01875I>4r`^t9H^!q%>RCu9*5;FkFOjz*rBtfZxuxIJQ<BqZimMzUK*mi
zbkNrS+RK?akZ^)pf(%ETwTCvqpYfXJYY@5gR<Q3>{F~u{n2{~@`Q`MQSIsz9aK}}Q
zo?PKd4zw`tQto6DIcPGZ_{wGe{YR8Vy-m1<<AU~s2a@mQq~54|%<i>fLp3!1-XG`_
z{UqNoduwOX&#1_x=&%01ul6NJYOaiRo}9E*K4C$z;lte5-CcdZabgZB_8(&Ue|jqs
zfU)@gJ^C$8wm*$=ZgK8C-rgP4DoiBVN5>{>^F)`!FnDjK!FAHNa#QD8XV}^~Sc*2*
zLyf%TAwj4Vk~a1&JuPXd6fHjdEj>YOIQT9EN>31KiivDexjxA+lVBMfh-5t*Z!114
zsUvn$hNxE*3|fMV(brg*xZ_?EvtjBI6>8}L5HqVHjP>!J7qq0Z<rm>+m3P8c3^r!z
z_oY&hK0j}fiUtSj0@{S|)aU;ikfvbVF{jiWAN;%sfl5J85s6JsdiM7ADk>^EIyz=%
zX8QV+u>lA(Hh7Ai^i6DO-#7E^f}p}$7qzEUTKZRY=MQ38trvoR{`?sc5pi?#k+=EJ
zA8T6F^zw#IJ%x|TT4JwA5l{ZzYbUr@a7v0T(D@j)2Zf7qb90M{Q4K!vVH8q$h)!Cb
zj8CZWg7kZNh!(7lpPmCpi4guCb4BbfJ3HIbZHveFFgZDyQ1BUb94T6ND((L?>|tEV
zW`JcA)Y^O=+34!(%E`$YG42{?a^w`NV(189hH=e>{d+4gp9qHZhQ=dh$>S!8McUZ#
z+ez%os-u{e3eGKd0=VUuuL$W?2k<{bnmx4m-pMe#A_48dIwTC^iLHo|vI@QwBue+7
z9<TLz^cW8@@f)P7`E)o!8oBEJ--k)X?p(tye3KC$9s-5M?L;C4g2Z_;Km+bp+u2(1
zM_ekDXL9%j>`1DjRLgnEbF;hiGrG&3^%;WBZ_HARpxzK3cQR}99sSAfRD**9Q=x3l
z_jaQCXzF`Qqh&qkO{MC(Ix5a@!<$)^lkKf-cOB^tLzKKle)o575C|O}^<w^g3y-;i
z<x(5vINX^jK|0)gtNm+PnVrwy)3S=8t|)$f{bu)ut6{&mP$-E6<bd9RT$ucx=PtTY
z{P#@L_r&svv{k<8yQ9G9UJkOQokfFsA3I7ackS3#iOaj*MC$0T0!`lS`_ned;%IH~
zO+{m2H;1V<{W&)~VVC_+tCu-+vEi;TPtU>UJmy<)XK(ujAtKU-&i<0IqcyJSyWjG|
zLc(~J#eIL5?y)2#J~p|2uPAxfdoC9*GdFh;C>ea<uy|9clqnRT=vCi-+^-<pYn%)*
zTjr_%EZlWIITZddhpz#y+x&GP`J&EhY-78y*XOWvM>bl9Qi$kk>E2fvS@RTDen0GW
z^Vcuy=Auwb^mgChJ=uaCugv;cm%G8Th{w25JGc19uVkFx^|I`Z$i&32{f5Q1{u;g4
zcq--{<arKnA1+8!?8;_r5%af&*dtJ}I*=%WX$}X!^PO#X(H63*Y$POoP$k%Pj^_`E
z8XHOX3i9ZchTUv-AV){!uCn`6mF@}(?`<~iBB5Rt=%{G3HD)IWy;=na{GhmjQivkI
z+n?F(^^jy&zuCnP*h(uuG6tQ!Zt{BrD6t<G@j;{@UlFKG*dbSU*N4sa)I#GcKk$}_
zFzVd)2#nX1#m&}is$6vE4D_0*sUI^bX&G_Vxh+m2@;ANSFYEiB3>Hd32Ixs!S{PL1
zpF3a*l75<`6^w4;W_3(DZ2y$}LpwN1lk%Q>mxJTrV=AJ%dJvUvtAal{Q$IRW_%?!p
zRBUcmmx;lS|F9)!4%)PXkErvze?ptw9VagU&1cnIC^Hys$+6%Nj5ui+>}@N>(!_^1
zQfvl<3z+{J2@4zFnZny&q_j1g*dED#Yin3*8T9?+5G)o7VLCti!9ugQqGA#z^7#CY
zDeBQZeije6So^*2HMQTbac6@B*PWIiT<4Cd_hDha?U$1k!QkXrD^)m!_bv$h6>I;E
zmV9`&P&v0?vFSHUoz>gI*|W#q5Gii|(;`bGD=JgCLbzUO+N@-F{Lb$nx-z?Lx;+5V
zEd>9wgU6=F?=bT1jx$Oo>f>7r#Q4PR5oEaA%+%NSOVxrlOuseldQy*L`O;`GH~I-m
z-f0$Te#=dIFO_$rT4B^Bht`zJ-^%|PO*E^xo6khuRBLOQx6T}1gCPZ6d-~3I^cqjm
z3sDe_izUeCcl~hzViQ$Hb{XxzCtMfYisl~oZy+y&z9PE${`-(d0t+7keHU^(LI}Sk
zcK6&0h0?mKC9DS_x+`O)b?n)ap$WmDIR{*@Us4$vXJr&#^9nSjoX)Wwl7i5Z0$V1H
zG#Sy$6FHTF*!M|$ZdrZ#Dg(OVl~6{mzWMLw%9nVp>v01`#vK3JFa4hna2qWQAAU(z
z)$oh9r2rTsF{4Ubd;`*_@C1tE+FugLoXOHv&7Y$1=Xjn4_VXll_CJOacYgTXsH_nX
z54O11POk0WDe93*MqllFm1m}(uP4$P{?S^Ig6!)${5+ATyB5p#5g!TZ`S4a=kL(+K
z6LYU5T4OA1wy2o$o4HDRk=b~i=5s3%E$i|g{!?lESof=qR%NT(09?`CW@>9Mg^>zv
zj{OM&_@#C0Y<DSdD`QameJp<a(JXEn4G)g>hv>mEHV-Yn^0yku{=q>-1qI-9a1td9
z_b+Gn*7f<<$ji3QKXe6%P28VV7Pb*^-Maq3qpm;yP&=E+0U^C8Q6VoP99Qu4d^PHC
zw&!`&`trKa&F=57q9ymumWEL_+$-}&hmnf?itM>Iby-$bVt80s*a-X2-rn4tA3rBH
z=jejPE4N>%INrIty3E3lC2zfVKTe4s`&-Fm(tnghRNN{1?%kDWYejm!w)>{^o+mLe
zQ3{>k^?IXRB)YEoo{K|NsB?Of{FQyD(y%-3?J?pNK1WM#lx7|atTSP7cvzM=*Dr)X
z#qeW38M309>b@6YW?`|%z0|yWb_R)@SW{UsBzLdi`0+gAzIRi0?{|vdN)h@v+MmaK
zYWn($5k~I?cJ9-+|F{|@4HvI|V5~J5G;-ey&U*HDFItjUl<}Kc$v5KSFzD9P_wX$;
zqe=6SJO}Y5va|H!{Jmu&;XkPCM&pATbFR?i9qM`4rN&;7^RfloU9yXUkL2Quz^<Qo
zyECPG9{u0X)Y6hoF;Z+-htBetp0AjZ8@r|c_8R+LmzgnYgyTTq6wSe#w_URorY;Rp
zXZ`zloTKH4n@jyrTHQrp>SwU|I@{7G@r!oi%kt}*XECKG(?0Sy`%TyGrD6-h?)g@Q
zLtdWxU516!!~J}le^u~`aK|yNH~yaONMRMI>#3(%9vD0?<AR@2&1AM+`)@{A6HGHy
zEG5*$7kW5I+ZCbIS$8t{xwE`n)zyf!=X|)g+h5HCch<C-jeONOa<NY@s`HiCBW-)g
z;Vtiw2mIR?U+lAD7Cw&brSY&71?ML)x9fedYCZdPOSgN+Bc_Y2F$lAw5yW|vegxiG
zAuF$4uW6GPSq<sPBj41Izp*iAESHR4PPC^zUj1gQzDbnsNzs@p6hG*w-_N4pmJ<3k
z1!0EY4?7X7l)G-7^7>mYDrrt$qjg8?m!h<h(ZG1{O!q3a-076CNK#hIL3)j=P<#wi
zf4jT&ig7o@cS^xI8qpm*GGuhU)x?~lf8-XAJA+^K*~xxm#!0C5j805%D|lH~;`EVY
zE_nc_TD2(SLecFEub!Ce7xY;9Tb9!&Qd%<}1D%0w4HdUuQ<S4sBP}>r1-|-~71H6u
zncu_Q>6T3L!+kr@Ri1?0;q)~2H5cM!+N8D0AXjCUpRkn~vOxH(1QhFQ3tVJ}<#hsc
zplGwAmu9*G@~ZD6bE$s{G42**Y_lpXwu<n+8W>DR<eO*CJfAWl<f<a3GHg(klCAW(
zG8cKIHQ@JcDUg&e)c2{p<HNK|l%A#v%-e$1*$`-n#vhF6l5vrE_sSt=5_bjv90tL-
zm!o*>Sgp*zAkI+_QZ|Nkq>-wH*2hs~m(Nv{H%aC`#A$!75mE+Cr<1k+HI=Op*Eb%*
zx1YQhShTN6MW=yrvADe3n7cwZzsd-Ii%(fh#NJsW72#_MSs9FeNvg9&`4*{~UZFLW
zcC!kv?jR*J$vj{QOEOZ+krn5i0`o5ctxfGB4*T5|3bie!f5GM#+kVvx*S&j`AsjmW
zZj?Yl?sO}d1XX<buqHBx0xL$8m<Rwwjp0<Vy|f>#a7NL4MN5tn?7j`#3Z8UycDuG$
zdBV{07g@1M2dgXTM;`p96zvw$&31pmCb(UZl*2%jECt?##q~>Y2uJeho|6Ds2x6k7
zrjU);NxPMWZ@5ElmN6VOOK<_rbZ162KMZE2WXD6&AH;@xcY1_2q_df<HR{|iO;g3w
zQ(iZo+{?<RkZnkEYg*Lz$dTTT<TxdByHtdr6LAY35huPwT2EX_;9sOv!A(Ot0tN#$
zEzJY4;#P!KzoYs#WvHkW<gfp(RC|N3+H%JT>tiv_$=UiK!+>IZ{Bvlz|A;MA$w1Xv
zjlq40<x*#=)Mj1e0N4U)Kk}E4L*z(%-XP;7*R%UJ3Ja`85du6EOGQB;On*AqsPQQc
z2<Z55*7U=8@lXv=m~Pyj!UZ*(ato#G^(ESiYg+Hr`e~~kGuupb3C67ow8D0AW|=rZ
zG*Vg&Ax)si{mQ8F-+tyEo{IG&>LJh#37`x8RPf3QzHdFaO>j>D7gPhMYx`m4kaS*0
zd(2hT7Xd>)&)%(GK10r)L?7>PHF>TC8jR^UA-7-z!^Co+R6*l68x1}#e#mhzE9+fL
zu_W6mO7D~%4-<Q`FXll3eHw!jGVVRMDcd{py4Up`)NUUsh(qw(g)RPK$*t+<hoIBK
z<RH9?#op>754QM;;lc}z+=|2elLW?_`m(>5t>R{-1REQ<ra>U4k(kExBj9Cn4VHAq
z6RQAWHc7@ud~(T=p96!*#0?`N!^bVGT3%DfhCf>IOj_xtrh33DhI%4|h!K6qXTttS
z*Hx(+XMw6k<-B)06xzO%945~hw_YuE-rQd9k;Q1$qvRUWS@u1@^Ep|8F-Euz=OTXy
zXm;6TSCe1IjvY$EV4R&A$15*%V8Sydo)#%WADG&ADJUAd6RorX3}wyLi{Ge(&lz4h
ze|MxeKS2#mPm+(88cvizs)l~xI3uV1!C)aK0{LkhC39N2S^)OPF0;H2RUs3M4@~IH
z{>wuwBc`hc+gBlEq-&nl(#iw*hMTmi4*(u%4%mAXEw>R&^3AkF2l0LX(SV5`J3(q;
zl>ZvrW-ASh&om_2UMP@C_2+aWCts9N-zWjJ>>f=((_Hv=S;Ejf7@sW@+Qr@On2Z$X
zdqyLj#K2?bKT6P222Wq#U_WVAs#PX4`5p=_z}Vvh3nQ)M)8&Ak&heF<MK@p&9MnLF
z=H0feC1y>lGZT!A#)Vm<*z=w18SF{pa|Z0tq-D!GdKy*TyOXZZ=3}AtmN0+HntUyL
z6<|@BSBsw0PRPn1)=4mwNk|)PcPyLGpT{81f{6^1Mcju<fSX9V_SBG(KWt?2kb9k?
z`T_e;{uxC~9TW!aY+zrm?Hp=-o)Wrw!8j><r|+p`c$e}wb?D38{m<Awq0lmn$)wfx
zVAap0GIEOGt);|kUqb6u>DDh7Mti^W6Cz-JiM$@qu_eEABe{vB|K>8J1nAn>@SPBV
zBfU;;$EVqejrdw~3YEf&mG{(O^h@TqM#0unZTZN<5k9{iniM0RpcSnPElte@^N?C<
z>kLMtSN|Dd_T`X=lbhEdF|BvNn$=x5I?0Hs@<Exn9eN=n`KvHrOO>!f>3~u6;Mn47
zC3$*MH8PPeM8y=5ehtsqv#og2@HuuvhDo3bgr!OUde+#YEV}&7^lD6tbDdL{7Op*z
zmLzJ%Y`7E37oGHgt?g=#jikxH@vFTM?C2R7dV(%TN$8KFaa%&#se|&=I)%Ez09ve;
zhnFQijH3jfq`N*95>ZPB7{|FRx%fjfWWcnTkwTu*vn_T;IU6}4g(~Gfu<wi{ez1r`
zQ(miJeDiog*Wi=1?L}xRp`qG&T-<&-$-=f1G{WA8pSV{0w5IO~k4|G8n}CBG;};zY
zIIzEDE`tPn3&e&2<EB&O5f9iNd(@G{zW99jeSiNx!I8mQmyoo|=%=D^vyXfDfn6vR
zrY&GOhSP+HPWl&yZ*eN$o&Vbicb5(2sp3260TU6<{@}BVceQ7i8(IKbJ^p~AOo_eI
zk~S&8NgzO{AZ(1BNHU8p?O^>hxXgT6Rn|SQH5L7;`_-7{&uJygfKW>tQt2F3<DKra
zl*`R<GQz2y&;vuLo;Q+rDv|{EGbIPj*hF}2c=ZbyCKt1<k}-aexF>}?8YyhEENW-H
zz)BdcC1iV}<gL2(BDPIVc@N)%(!G=~ZE7c^SB9cm`B84^BMvOWG?Z11WKPf6L!f3f
zqp*S_e$DNuufQNN1ky!u=riLj#f!R<{SA6XK2_p?_s*+=F`t&7wdAu}#sc!ucg?%@
zBAjAn_qBJezn(l-`+*7&iO!Y@=!{u%^IaGk52~89stxMJ;_5OH@drRsA#J2dFE+mO
zcL&6>A(JF3{$!Y##bZ2&1;!025+aCi7fHE<$BI%kbF_RRJa8pcX$ph-*y5ltc@yJ6
zH+dSZ{S1wWcE(^-st;?l3)dX}P>&lE<=fZYwFHD;8F}ExB9k>q-ZlHCudr8wN!~zc
zI-g#vy{6B6E`uZphZd7JtZ!_P5EBDLuA!+pIWZw8^fTKi1ZwlI_wW~5a<89}j@b;^
zMiO#SmGs4Y+-4kfSX|xoxN%{qU*<hRXv3t-=VDS)QetCcv$F6!G_<tj$Eob~ulZ)J
z*=(3^_p7QUn*a8pa<GjqW_CuE!Yh*QV@4cG8fB91Bp6dLk+X1^kEyBY$B!b*r~}yM
z$x?eLkx7H=Pjs}i^>2|S3U`o&(fH(2MYj}Y&EE#MlE+;}Jh20hVS(3|!9hU}4XRp}
z`ID06*9Exv<_fB{|GUeC6Th5_*bBX@A<@`K-UA~P$`~Wx%#VS@!p05{3k#S*4OYqN
zarBsx>CUW~OxXUDKQ56E=B6MH<GCe`Ioy*FM4}HVpFtrCBbe=!{XsTG8PM(lfs@2P
zQdK{s`vOjz8yb)QhcmlIhV5~M&giTrW4}wljZx=;8(DWQuR<a#wcP|GN1PQQwR-%d
z$&+$3n2FYmTAr5NhM3PDCqDiXY7)HEsCvKFCZW%ayEyTwL?cUps<5yK!@SRxh9>=J
zGJUgJvvXVl+|-oI6kVz=XBtdS724!AH)S_ldv)AwqI5;Oa5f-Uv9?ps)t0jd4<SNT
zdsdVL^|*@%=baZFPNY<^f}C|)-fE^1=9L{LJLdGO;u&%}9y?x>8}^KB@-^>E<ncij
zE{@k5Kl`JLs>V~C1O=GGB#`u_NpRLen;tWaOhaVpMB@uIEJI5P#vuI5)H*YnBvGhK
zvY2>wLau_mPMjxQYNP|dY5r9yl4+`cxJ$_G&v^ESUdF}AC2D8r;eJ}Rvhsn+SoxHw
zPwU4=fqNgmrp#9OT-Wc-8gmdeY;I!C(S;9*+^!DzpiN)wj$N$uW(2H`1?~xM<U-<Y
zZJXzWMXJn$3+(3V$qCL)nh%Dw=L}jU+r|BXx3Alu9X$UY@ww}QI$dz4-hv~2Uo=QK
z`rh{7;_vX>?3pYDOD4BNw*Gzl>DIz#CqCUR?dsW5@+y*mTd`*8J#mDf8WX%<B1hWq
zcs+qr8VVJjcTBgD*R_vl@=F<;UcCML<4rg-{P5UX{2Pib!QIYGa!cBrnDVc452H&&
zB`kV{rwz{lV~P5H*BLL`?e6cP)wjpqD{Sd;+|{CN_w-`XF0SbfyZW}65!af|c@%S5
z89aUoJA{`wQwO6*geYta%(@~DHdEqG8{*VAy+u`@8Mv5ONh@`hx@R{A9?70ACD$NJ
zhL|@@R)Ygdy^G?Z-a)@KKbk2{?mF`H@m*zc{E>-0Y|q-AsSJLR+3e!uKA_bk?mfNm
zeRXUPm)h$>hon||`ZAkeP8LG+?EOAA$qt+)ru*)$J@qwYq$ECZqFwA(^@3@)S>Pf6
zPCJKLUtmSUh;U3egn!YVJ666{me*_xx_Gb}GMogqS+!)v%;Et?){hfqK1L<yfL%7r
z%Yfz6Z7ep*8&YUXop5c}RQ)CqpV*T-n+Z~U#fry<zLw)DzK_r^s9mTXd6wI*6<?5M
zyuTrPdKS5l{pg<m=US%5-vfCa*gD7Yrr88vKKEi#3>3s9MMmYV;oc|RXQZZdr0+=6
z?GNm59ek1YqFxo3rs;<>9JFni@S8Rz%Nw)3>XWL4WpOOOq5G-pg4j~j^iqq;e196Y
zcviddfB{qnD6e`xjJhNe+J%8HY!i}RrZ?qFEI^(kg-ko?IevpDa;mZDL}c7ZY4!)3
zL-aCQ<*@zm>b@(-n0Li5F!pTJUM(joE1FGgN9fk`78xd}K3i`$*TDagL=A?LLcSqL
zGE}hdr}u9i56*8|f}ARD;yaQyz1tpGPInT3;|z!n%hKwW+7%wXH6pqFGJaU+k5!XT
z9Z$`aby!TKhV}c1eR3o`G?-e_3B`n!J!S3*+xU2vjHfYn9}4fRj1IN8>#>Pl|LW5E
zi&KS8clY<gm{lB`u>M|H6mOAQ;p;WEuj$05uv5k|vTPC&_%Q2<?CVrsn|%xK_J$qt
z2M?_GTD&U6bE*_B?2o|d5{r_9v&ItBPXT1`%#bI$+B*ClF<e(8R{kyROHE(aZjI+<
z_|*a**wcAl_UPxeiTsBoJUv@C!m6EO#Wk8r5UAK@2h-gpa7w3S79)S?{ohmhXC|D<
zM%1FBekyBDthC8W{|qLv6z=BhyTD2fX~_7CzpQ)<v9CDnpZ$`=GwKZAU7Q>0sTZE_
zVO&#_g6Q*X*tC_?s<BN-LPS<T;0sHT8hM&};+9b}@A$65qq*;+;(cSIfT6FUtSB-d
za`1BAYwX4_KAGj4$f-!2eCM=MeEwTquf&+}G5UZYkB<PCrcN@xOy`M45^!ZUWW1wX
zp>ckY_733+0!=F5VRKw$mB->@3E>{}Q^nsf+K!`lg7{2_xQhs2`H{NccHhzCJn>Vd
z@}lYkyb+$PyvDZr^Rn1iQL4B|f;fytm0}QWr`AJXMvk1ktw_jrhHFnWUcK-sC?$;@
z5Tt}|4eZvqZ0wv5>J_X%&lNeHkKLK9Gt4dTIZi=bc)7CcGRF>VaoL)ax)VqP`XyDo
zII-@T7p+$K;%BRKKJ2(xDWAPzowFv+sLuEd{VaP@kn_I$@m({O1c2r@wRtX(fL*Fr
zO|3E;n>eN>_^U`92rb8*R^!UUsN~C|)5>-?vZ@Li(`0crw`l7_?K!d0C&#wrSu?{S
zt12{k8yf`$sOB>D@(kw*<dgwMmiOrUM<Qsc>c*47UpkGE=(}nH_Tjn>#+&_TAl>Bg
zgcx#AF*V!t?C6&GPFGl9P>=ehTc=^5yc9$_4&o^EwwDX;Tii(GAfSUP_ZYVpBK>hE
zViQ-H@~fzbzi#*03R7C=zRX^B>P3_}0>=&s$%p7*!6vdQmW3M8l}&0Vv}vanTwTsI
zC+P8c^K`yRl3<U);qcJVP=GA5abDg`Xc$JPTI?Fc{xFvo*~?!x%RPS|T-0}b3{&wX
zLY*4Lmxop0_p!q5ms%15io2G#3M&FgwmL40h?uxjJ0v=~ca5~5w(aW*<<YK<%mGP_
z#+c3O&^q-?*kF;sIMtu0d?2yMtf|blpT>MFKjaGcWFTdEyOE;btwHdVF)0!gok?7r
z8jq?h=w*Js&&Rg&NY{eh?Pj^L4*}=jIo8|F$H}enTtm{zDk@0UWoHiV>Tj;Dq})H7
ze&(n|KCCy*6{c$fv3i-4$`e!`lxT`wR6${~cdX}~sl{2oX0vT_;Zr|xe8lM3^*3x}
zTC@LqyQU@~72gCY?~A`<#881zXME-wR4ouo(}cc=j;H@cw6B|>Am%Y`#JpV0%E7^*
zraM|ss6@rW?Rk-K6n?>e6n~Yb;!q?yPGfxx2*Qnf+Aj5{i*uVGYdRxB1L;F8#B|%H
z92f)a7fbj<xPiWnIjtxK$|Tl7ssxc7D@)TzdH=arf;bFQ?y+BSqp3eKfN$t}r;rhN
zB!0g)P>RQsFQ*i9c(t7YmRj^vY<x5OL`kY52{l*JOu16!TpGmdY4fHk1*VHvduOP&
zB)&FiiJwZ|_kIczIjOj!)B1yfSI3CYD`k~S((&{C;2y=%4DBSAzK;FkjSMj&3s<M<
zoOw9XQKllT<pTx#J?m(0MFCeE*r`9gWFsoXMi&=qe@%r6>j0`}qS`jmmPS7#7F(t+
z?BDSQT-*j8PBopA+NXzlpGXbmeHX6m{JqCN3;DjE`K^B_1)({hZC6w6{*wj&nmi{}
z#rHGQ6Dt_sp3d-*0bpiI`nZ_puwK|*mJq!fv*awj-FGPcz<dDszSJ!DvR5;3^24}S
z-xKpB27UpW5OK!Dfcv!|N=1Rk)!ZgS2;<47Qdk{oAPPs+;s-#89tny}<-FfJeq7)r
zSy3|HQmcZEq37-^9~{7>hAN;+LZH7){6fX%4e?QpkbfG9Y7G0cL~>ZCw5n`Jxc0^-
zu+$#y*mA9TfY1bl*ZQgo>4KT2W*UEPDAez!2?QAvN3+^Qo$4x`h>*M)d~ga-8>GvO
zxVFDMe?N1)Tjge!GTea<AMrbGG==94>WAUerq)>?Y~^^$FdZH|Gc;QNvh-wZlG9>_
z<|zZmg9~Ipv6+?J;{z5NX_f<-qWaJA<15&&MX2bLKEFl&>S2mD`qO{t_2m&Pb1Kh?
z%ZTPXw|;BmSJc3Yw`DFL{<?zwki^u~pNgVWpTztFONJr_8>69?J^;;&4C+0S*tgU-
zM$=g)PhR(F&=toRr^`*#FbnW)Zyy8t+TI^Lx8$GOR$h7h&Q$M#w8sy+RbIMk`gd{E
zlL^8Wi8!&p%i=+p_@D>XsYKc-vk+&R1yB^uzfgS1Y;5NHLLFvY9J3ufEo-FXvG>^O
zd+GNXNBU>rN91d0S}Ge(LZ<=83JP4%tMHrkp8~P+j4QIDoCCoa6KNx2+TKLC$v4<C
z^G)YAV0#w)HXcYCe5Vwe;vA_3%g4!N{qdf<J%F!&y9WDHh^>_$Id+-CmOx_cHoAl^
z<c$5d@5cpxGV_-2^8X?^Y-L)@7xQG%wYDlo!K!4%Mn$XRY=;t^?_R*<US7WWL;moo
z{y#sN(sd~zQ6Ipi3F79O7~3_dR2U1o<Z|@D;jF(34AVCzkO`cUj0!gfy*oGw>Syep
zCmq=ymAU<o+pDb2ww^s>0FhdX)RnS&0f07<)lMt+W%PiLt)W}5lg<abBT-*XXkf6J
z`%0KL*$eRxkVtvEqphLMsGld~&ku5a$}IALh<@V%+-iWcxWCdw-a0LytSDpuJ`B%S
z1CB)aTD@N5>Xa3*nfWFAfL1ey>?<NoMnm3z#0j9A$Ye{llXFp_r*ASszKf$YXECYH
z@z&JQg~&5$-EL#OqqQtshB_xWEW_Sl&hxrK(DoFAKB_AIy#C@T8n=0d?TqXaEoB=`
z!&$W<=<`&3t~UC>v0+SxJ;qbBJwzT^!zdrI8Bm=679G*t@h}RChxYx`hJv9J*k-SW
zF*r0(Suvl&?+#-o{@lp3&<qlCK-|9e>Q44>srbu%E|g0qY7d<z+m4smdSr?S>LGy}
z)s}L1Nu%WpdmVH45+?UAM=(HD0l9i?iVIAe<`Kb1l4RCZFjm6@gf`EpCmFS=n`dX-
zr>fQuqywDG8YBeeZMD!O`HCCqyWL8z?lO<<o=&!;6FpM^=p@m<_18j$))fqCJ}(Vo
z!R^QI$_f&F*Gbt>AvK&`%pX##Ed4{z_f-o;)Xj7unQW|hx5eK=KvL!L3uhOAHLmen
z8YO!CEVV1+o_G}Vu_p({*$l_bh-{>qyaP;iwX)x($u0-mi|tRzx?`|DTNUm%kY}5_
zk2Ow8OV`Caw2hWH6O4_Yog@OJpz=NrwAnU&V*}k(Fzi%!bM!?WOFW_=-^yuxwhGtO
zh_^g|NK0VX0j`p{r$;*Imsfwhd<w5JA+fXypx)OGEY__ib1<eKwxqS6a*l<o+vq|l
zkJkJAvqj)h6^kXS(<E27`wChdN$GsoceWoojUQX4ed~WISq8_PM^ZNRZ!}FHDdU->
z6T6TS>95r`UJj$I5oi{fp0`c_Khy?O&h_D^KI}I{I$Yv|NQ}JQ(k3pcRH#t<2q%2?
z4>$=TtlP{A6(?!DwK%j<ApwKkWjruoVpXC=>D)}>Q7Rh^l%MT$KGeYVISKvVl|@QW
z<I3ag&weKT(Es=_XIvR_+F?C-mYwkKVOPpoTX?d=hEtkUJPL<m`e>ruD;Yl6E+hi^
z=h*ZuC0{{8hY4B1-AjcE*509I(!^IBaep-Q)cbdZ5|4jj$08C&a6SB?GipiC+Z?Q_
z(3&yYP^};6^HmWqn9Z-4rH@bDe6pI)?C(Pz`_x<aaE4UKnZMUZEof++msw*Cg~RA&
z!H!2RMNd)G(Cm{T29y;*xD5v$g#JNNOgYD~T-(lQK6@Vl?b7DHKG_wlo1Te?4zGVc
z;BXmk-+}#)XBaJtJ#&y9>@{e-Es9c_b^CA#XSx0M_c;}n^?a_#rfS4L%IZ%Pz2<vc
z8LO$RijMeU6+VN0mM_le{k$A1nY|m{f63N4W!%Z`=h|?m`vHDU#8n;&RSb*8c1OrF
zicpn5n*Lt)iVkqUB5ks0j@Ye_a?ABi?3j3iv@*E(=9f9$e4*1^J+so~W98)SuQZt8
z9c-@3LK;xu!Vx_0trHRl9S}#6vsubz_bfeb0rj81Klql{KE&B?{PTi5qAqG^lW*JF
z&XtqhOn$Qx2fjQ|B>4R~Hpr<2)-_Nc=P@O#bJh&`;#2z#$IsS(SiM%@XW=jR=q`Mr
z)zhe@KL2Ngr|%rvV71uL@glBPopBwo;dfO`Q?&~Y&|)S|GLwm#dL_Xdj2Q{jeES|*
zEjz_$hc1BeB)uSc);MsbzdakJw3&PU?)D?|<>fAAvvxf*id|a6B}p*-472!t?r3%M
zKb)?UK9{k}sa9`guq*K4OjJxFKHd(a(hTNPeK+C9RBl>sd*YXfFiVL1p~T2`sdKq!
z>TUIcckO@6%;c!4QwML7`cM@f-xK}Py>egmmV*2Mreko3{*AUCOy(SW@LBZE-du1o
z#=1#?%<o>=jfuib0E&9-0P>ZVmIf*_z{|P1x;`$RH0o5kQ8znwhgF~`Agv>zzeUAT
zD-2XCMUFvgfoy<nA@6G8e+kQSChguTDEvYo5FmTLr=_Jun5U}-GA$9NPvidjc!m!)
z{x6}Ld=7Z@n+h}-8Fx}&2qt5U4FLTBb{`!b75TVOZV80EFE0k9Z0zgD(9pbt0bHvd
z68iv5WZc$K?7hAl`9D_fo1hvJ>*5Fx7gu^OcjwcBo`HeV7i&dgu2dN_z8EEd=;E3P
z{stohJFRGwU819J<jWdH#s7~Q&1woQ`_GU6BU5weSY?o?W7IyVTG2^CW&q=4^%v{*
zkzSXiJTh+oDAqG39FgzaM@CU(@l@&$(L*53>tncoF-46G(3<vmYoPV)lq3||lXe8$
zDyugx@P4YwYPSn|^OuD*p87NnDyp!)dTX>LIv^7HpqIEBKgVjq?Oae9;}3Kql^Aef
zBuuH0)-R@jrcivJbv*I+vOX^3bg)5W?{;cf*b5jLYd4Qzj+wmOMcs6S{O3pH(PL`r
zU!<ayfg?R;+TP$G0Q;g0FwSunDxW74+7X5u6y-NEIr}q&zY7%8seRvW20}qPkXYxX
zG9#=t_NM31B8U)9G&-}_ysq<5d06jZYJ8xa)IWwy{9>Noiaj^ndu^2;+I%j`fdnu|
zGtae8s)B6C0?1QT<0s_SNrxccn_2MT{C2t!K6v8^3Gkcmk?VD%NL>oJ2jV9U5aJZs
zL|4e?B+U!28tfQM%Bz8Vidfs>(Ivy0_rlyjeP#KNwI{4KS{ThDt9Ngk&-Z5QZRWC_
z(TRFVDFgS~3O@!bQCcs|HQ5YT;5CU|0&$NNB(&B7u?tXISjJzOy<w0X<jxv@3Y(as
z_Ba`Ye?~hySXvtDHbbubXs$X+Haw>CaY4-1$$vR8`f#z&4~H9HihSt#a=thBCR5m5
zLI((=zOH?X`2W%Mk<=TurZqdRe4qYZs5}fLNFMihlwIcw&7Ym7fiRB$h@=wQ=ebum
z^9cQXXRe_kevEEr#_*4LTL!X(okhdiz6?wRLF?mFloCcS<;N|PM3rQG-U(wLnQoF#
z9&UE#qFpCmt(^S&l)CWO<<Y>GR-kjsh7X=y%14XeAb<F4_`lJ3g9jIV+<_0LS3No&
z1R2?vFzcrPE1`czdaWm>Mn(OA==XPQ4yNCuLO#8@{J1|)^-)QA3CmPaaK71Y?)d`b
zpykBGIlZ)QO(BhUcCn3v;+I~-6Jy~RdfWT0+<aw`m6w;Fxwrrm#ff1!LRnsB>rM!3
zJ^lTCXy}KHb<N#HdsocUEc=DB(vsh26oyJLN`rcp;_>E!80?O&;8$6{w(l?QE)P#j
z3Q@OQ{zpu=RNLA+$@5DM5B{7qrsCicNTd<`6LO4A$j7Q>P385qKaHh9*3|D4P`9gG
zShV}LcH*x%%k*seT@8rt@2?s7oL%)a*S@WojCxeVrgNNOe~Kl-!W{ZzlcUY!e$o5d
znwJ{0%0@LU2D|pp|04w)2U0*VLVnmnn<py}8mO{*r%6CAKVNckm@a;c{e0Nz6M0=#
z7=)UE{d&Q*e&5#2CZF~DLyK*iDVw9p+llQ;w~LuGczbkY=Ah`4i>Gk<I9ipV0HYmB
z{nkW2*u><%taDxUHkQSEEu+z`wnJpR5~WaWyW@)9E%LWBMU3>O>)ojuf1BH>Wx^rT
z^7<bkthdj(Ry!LTalH^4`k8^^?e}8Pi@<D2O0k<m#oONGU??zB?_7gT;;^a9nsi!o
zJoCF-)8cJ@bmLZy8dYNYiS1mo#mcLi!9544U7R-?QX)Vcjx!6bub-5YOV_)p<Y<Rp
zj7VO1dfz*Ded)Dd6v<oKu-+4NXTYZDscbh`YV&DUD_q5GfbZ^l?apuaK7@mGH2XaV
zD<-^$oyvV_>-y#$c@NxR=~gI$`F`xK%RtSipsVg@)=SoNfrxqZ3_Q!Z`n{XI6M+d^
zuak6vd;U8Iuvh6|a)m&B0QmajECE1tf*2Vm4%-OkM)gEo-VyJhed(^3n&;@1xOk5H
z!G3Ra?|h>Qr~SP6qSp@U0%T{>6PJABQ)M<0vDGPcAzzJ$my#a*Hz9hjMMgJ}r(T^f
zd-cFc*wg&i4BJ}pre|xdUR9JAFv>f@Fm1e81XB$aU_Q{R>YdVxOG98&&VTHY%0edh
z>NXH*{`b$O+tj?L&7ORq{1Q1_=7Y8*<#g)!v3={7%5NLx5FDi6|FV*l=KX#KwFf&B
zbvSW5e<q;st$-%cs1ryIXIh1yk)ve#Kf0Edy2M^8E>rk-wD*UPj~%GIcUQo<?-~kd
zF5DFKLcq>#e<v^xUCfVRqf!8^^;2@=8O%zyK=<&j&CM*ohxZy<7ro8Wq{*=lO8xmW
z^N<p<MYa`=Vc88Y7-pLRNQya$FiN7$Hcc4Rv4-uDaqIc2r6J6+g&Ie+Hgp8TOz}am
zrU<zygH;6o=7u*80QDia&L*D~4DtabF_>}Fvn+8%Dk0cF36_n`hKZq;0!>)&fjwSg
z2XMMx8ZR4!?8wkh`D_9;v8DT_o-GTe-J~=d9C)I!0~DR^KR6(B+fRNS$6D0s_Dgb*
z!(j!LM#efM{TsGALQP(!8BW>7bRz#4TIzpFN0V3pjRma^c}X<+U%+&d4xI}lbzjVF
zn_|y1!TKaCK!C!UzEjQ&2TI4lEx<m03l%}poGP&f3}NDl8SQ#@asm`U<n=5OWxCTm
z@g8O*nRip80JVN?1~LcVYa0<L<^X~XZVttQXrQ=U{Ow|HGY<%&<BYfUoHk&DeDGy@
z7Qyx=R9M}#y9#|tm}}h)x@Sh?>Uz2|s`N{~3|X0^5M-0<o>ncHr$PNw_}g-p8RHGG
z-lmT7#C=L{kOY~~e>Su^!9N>mZP#HiQ{ywS8iW#VVaNnaEq++}fXw9E1x_maBWlHG
z|3{O_=?@jK_KN}no|6bI!oF^o>a6FU_dF{*4?%9Pl>4d~Fnz_tIeW`_>dScOgWB09
z58+QZ=Crpc5xV5|xfXdmu50y0uH<eNQ0o1)Xma!XkHl@xvC#!nQiFuy7yC+#u+(qq
zXZIj-jwNE<%1PAKdlP4V6Bk{uWV(0lk0XjvASNdB-|~SdvA=@X_9^^1wm{I_55-l@
zIyTHH!n+yL*+Rp}KVmdf?xh)oN9wsCB$8WlTw4awLXBe~E$>>xE$`%7-F<^fDHfR$
zL_`NHD>5`2KOXx3@|?SvT7fnLQ6Y*{XF0Sw0-jSK{do8=PuN%IEiWA;D0R@I@Z$Ni
z%asE^q7qunXguqJmKLb;1Tn|buWwl%?l59vV*h>s+Zu;ClfLY9YOKsU1_B5P6edO^
z8yv^U;unnVP0;tWR$&aa9wZy<X)_UYBzL7KdMKU7EUNLnvcuXdi`C(&u9l~<*hxSQ
zEVlpDBg#askqSy&fvcshug~6c_X!o>LE!4wq#%q6m#E~Q#D;*9qQV4#Q?~hnzCrEg
z5!ta`#pdnrFI|hT*2cPC8}AJ}n&sJ0{f@&H>1jpzRmH-iO;CXjUiAktNI7pqE`hRU
zivi)u``(kvX4rm-eY7*4(tI+L&0>XL(WXc4Yv~8Hrb1aJ(;}sEQL#u@$Ls^3KVxe!
z@IiLzqx3b33jQzyi}1O$t8N9W(y)CIS<?qP10)_nAZgd`gqx$u&r7~+G7AVa{%~rW
z=?OBqSmiHumT)_JUeS2}#A-~qVeE-z$d|yvydr9Cy|7JY0UgU%RrAEdSH%g-G&Lj;
zhc`&;RS^ToOB$uRBEa_NAC_^@n+{|g8nCGy0o7J5nKa2Gi#Lr<M&Z~N`H_G8a0H`4
zj1P=6$z1rKQT!}+)k{<$-=N2Z$2`${P|<C&Gvx3?uf^rWj&0@QX-4lCU$uPlm<@G;
z{1FLp6%ZvPm&XEe2*RxI1NPPrQ-kp+AV)b#+24{I%2fhd#pgicw>4>*lrFI5P>^PX
zjY~KDp`76Zc15U&&RhtT5zCx3f&)h78c?o+AJ4qcrSgL<_#xjUNb?$n3omIxH8zQW
z<>*LGpYM6-$Ha+^q}^0`4`SLnnhH!pJHDiF?{-a%?|>o1?wte)24Jgel70pOz1=cT
zm$Q^#srnOU8Flv>5nzh&@w9>Nl-mWuF|EpC!z%oho8^s5ZaRV?{v^a;DlSttM*gRV
zy9gQ(zElm{-0VmEDpP-|w*`;Bv|Tw`WzU2LoTRiPsP`^Gux~c`z~1numOqfuMTp~c
zXy&vw2SyWjAir4ssw`AM{?!Lcwcj%ARSKI&EsTmkp}PMVGn_!cwHbxW-oKU7XTL{L
zS_Q}EX7OR{4jw=uJHI9yLHdZ3jE#i?U(>=iTFxZ@t)lzsW6G3n5?@2?-XtLrGg>XR
ze@di_FZQW}>M;bEjqn7Gm;KqF(9q)V7q8fNNtD^Xt24yMBN&G8GPqsr!L-vA>*h@!
zxz0(EWf1%lKy!FH%mRt1LUm)UOQ49A7u&=q;bRNQEp1?_3yQQY=@U*8>iTiB28Fzo
z1FYv8+s=`y!$Z=<>U4xFY3EVjiFP`WMGASbh^EMV=U*E596qQUMdTvR$;<ZB&0Y~~
zWg`K#aCJgBawNa33ut65ly&;`i>g<II0w-8=6-$d5R*2>(z{$?qtGjQY$R`%_!`OG
z#lnn<@%h99P?8!#(H0E{L9SLCZ;TwP2}#g{9_rb)L1GkTKh_u35QIQ`<PgtNLCE{N
z8;f`pEcmiUs^?R;V?io|dM>~Uf}Q2V&O);=s+Rb#=YN`&M+RU)m#wtMe6pSS<Aqg`
zzqnRH*-xL;BF78d*<Q4>#tukz8jGwnJi=pvzMVk2c0G!o<MMPr-8(GU4%L7*UI0ox
zmrDIcDFb0v5e(!X1z577r>7VY$AZ%2zGkgWq8|b(6ncMrO%6(Cb5wZ|Kn*sL`7##4
z5Wo`OF8^GF9k7uGzqhxyOO2(|Y|Ar%V4<@mO=9Db{1Bqd8`Ox6iHAUQUPb>C4(Gli
zCh9zkk6+)gJDwc}Z=JGcn-*OT2t1N-_LTdoWEGDCu}~;h(VdGl2<3oU=a{@0=ak3`
zJ*}Q&mr|PXr+#S(Sh|ilwREgfIz9CyDca=ArkI#a%Y(0*)k(b#qafG>gpT4IDI!Vy
zo!(o!ek(7L6W82x3zuiW){hfWD<f4E91RZHIz8ENCmlE2zg_UN&(h6Wm;G`$H9|hr
zBT1h<U0wWm8ViC~y=8Jt+T<@K!a85qH*jTT!d&z6|0QY|%bG9byBSU%=|q+rgbyNc
z)H{XI>c@{%(-GY{LpHxhx{gV&oU6C4GMCU4mp`S9+&>zFnGF1f74e;Ktx&BB)F8VF
zL!jKaGT(x~oM7k$`D`BPYAAwCP4$!x2?6{59}6$_Of?E%Ud#&kfo9jZ&xY|SoG7LW
z!7t2neTqS9wY#J8P3Nn-o`jc3yrjS-@r@JB{u?vrp%Catj8=wuiXPG#vDNSEKvXHS
zSF?0$N2Z#xLX?ymOE!qc-<(#Eh7b2}rP47ly;jxCu0HWFeft^pV&q|U;B{cJy}uKl
z6hwxBttPVT+et{2XirbKW9ieSDL2Qsaf+ukUb^a09UvJ7b{<f=n)~+1(vr%VVusuD
zY>9MT^V|$lelmgGl+e`FM*ISx2dni_V4rD{h<65}yXgc2*7?ooPoRp<+uD_}Le}_p
zLZ|YXjp+bZYnrj6j$)v1Kp6{8wyQ;cL#HLR7@`vnxBa1kqJSG5E;WYcq>bH&z%e8@
zph-ytDTuIS;TN#t8Bf!^cE#r+gRjwXD{yUjnXB?AO@9tXP67|Xqu)9mok9bP)lC9Z
zhdml}XpD<93Y6|70$k!aPcKW7VrFaWi-<Y`^sW5yt)(EuC5#8!vqh-=LeT)A;Zn2)
z7&7O4rpx0;#hr*`AJ+zqHjQ9VPHhPE55DdR(8T}a^<h*fQP0Sedk*Rk;a7=9A3!3N
zP+?$FDUHV`ut_aF=Lz6DHIJ}7q#$u!Lv#^sJu?`9wZ*F8#SHzTkpe8)8hem}vK1GW
z))`sqj#3h-7kbZm%46mEF46#cSnSDVA(P?!$=Aa<l%3a`3mEd(34v0E{Vd}?g|v)>
znsNKX!179}R`M#d(HLQ)6|htT0dE6X^V8Q=-$QhyATX+X`bWjaL|m@t|56Rj2X-Ox
zmT$W!+{1>dSTHfhMsZ1v5E3(-^mUXO&mHhp(@Qw$crxDHSQq^m$EV`t=@a-jij?20
z_p9x{wtv52n0_Bg&DqF5?Lk8$Tr#${B*H1bDb2We9dXD9jgASeq6wE=Vh;Keu}U^s
zOSbS>uV?7U9NNfC!vVoj4IjLhMbeV}5$SQuN_lm}=S%@HHaT(Uxj$1|k-JG1wwRc)
z!vqO~?is~Jfh)xoVW1QKX0a6SfJOA^`}>?SD)D3c5Sqdc;y(z6Ulgip)?<MGDB^ue
z%}C#!KmdP>_A1&cmsCbCl4r~prDb^#1>zkf;%C_xd?~QdN9af8#rN7GP1@CE(#=t<
zT8wDw@SgV{ABlM(VuitF{7go#83Re6n*I*Iy9B`z;3W^7)H;euTC*e=^oj@xSeog^
z4jY~^$xg{<Q`eXtAzb_wY4y2;f5nL>u8w;Ai>-1EANo{rmE^|PFFgC$mf(qqq5Gln
z<tpgl2R}-^ddw_QjKtsrZBFqOO*Kc7*l^P#Z`xm;W$Y}0w{bTeWsUpsZg?L3zudKr
z-hJc{cp>xBsdfH2UPWhF$PV+3!=ri-x0)>*k5L+uJShr@_;nZ?nD+!gHfFzneT98_
z6@8th{}rfF9aqwW%`M=b=`;7A*{bUaACGj9*;3%31ambFc&xPNG)M4ozIY^KqP|%z
z^qe1ZsO;3)h<%>?+&|vi<!sV4I2EXz#8w(U=TLxRUqaXQX|iWhhZM#L%h@P=?U>^W
zzqI?VCx>D6&!>!>&oahMTV9!M&7-Z>x(i*K<@n38UQ3nkEzgH&4mrMU_i+&;?RZ#b
zY*i3-_*C;1JsqeM<CX^H79F2~^pE(1Xqz-E+WSv*AMRMMobiiQC^J>ko@p{YYDZ&G
zqw?%Ll=L}SwncH9jT$QcVJLX3!*<=#rT?g`3VoFIo5Q!Kz*NXltgHkNYMkv|Fo|Q`
z-*wkn(QPu}ekGY3z(qdPS@nWz{50<z<tZd;tz&K~m5+}E1hloVQ07vi{qh?Ky{XOI
zE5;{jnwREJ#mF1~5szWxf68szS7`w+`Jn2MLrjf=IX0X=@vx}D((g#mcV6qIA0?J=
z1LuChUj<=M#><Kns$<?#O$xezS$~MJMK<}IXaXU8719S3jsS{)Bu+dHA#D-@_1JY-
z68q&1PbrQ~gF4m@OXp$G902B?Lcet)CyA6628ydyV_8A4G(SHNs)lQ7YWn;8feK+k
zFrkl&8b}<KF8AKLpGH(Wy#lxcLL<!&;=7tZfB=l_{Vp%S2b3A<0f*B&{grj-mke6t
zO}Ie8K}JS)b#?Vg%hmNPb1COFpjabHia@kg9?~b$I3fTlivXS><yiXY<RI4FObCDb
z?zzri>_Wzr*A<zpQ?fELJ-xk;fYQ^*t+V}+4-Q3ezy+vZ%As-l*~8%7|GOr}Qj&l=
z4(yayh>6*l7EZ(<AH2)wMp9A|g+to_o%`HOq~Rg?89CJP7C1;Cpaybi$<AO<Ve+!T
z9~3y71Ci(@oH5zW?kR$pgoLDSWoh(6tbA`PgV)2$nWGXQ0wCMW=nT@XU!tvg_n9w(
z%|H&!6<Y!nKU~YYtk<SFBD~&dRJwYKB=PIa^JHNQ;*4I9VEx#Ubqb3CPw4$0{#nJp
zp-7+Xu<j(h**AS9Z*Su`a!lfxnuO)`SDNp}rk&$C*{q=2T^?5K@x@@wCa%Y8p1RKs
zO#z@PkxIE-K{W8?hlT&88huKPPciM0@pY^yB>oMxz#B)GVY%v7M#`fZiBTM2^HFiV
zownJ<PIQroSIu6E<F(|uSL|0TcL4w9&Aj@r0zB9~yqR~&m*i{RPmYD7^+p4GC((rx
z)srn!rhnVPHlCG*g^n(_tW2SC3@|moHCfeyBUD55UzO;PFvk-rk#9CyrLt64=`ts=
zRk!_#8B+%7qK-!GZ9d+@uSDZAZyESO5$p}%>eLDZFLtf22L-aCD6ZZgEG{_1+-mDv
z>;C_#U;bbyDE{xOL9DOy+5Ae$-W=M4yY9S)&ZDuGDgi>v=vtmbbZ1wjrGRnA@17M0
z^Jsf=u&IQ_XZUN(P^K`7+(7a$dfwehmMLCzAqmIVnc4HnsLy-xjFI&X2h9#kZW-<;
z8-A{T#;e=zK#dUiwSk39=r>FS_6Ma`=Ma6N-X8mr+Zn(*kGwa0ie=Q5WH&d714uJG
z>W_ziBghDK=N4z39>e}Cd{%F2Y*0++XJBypZ&qF0VH#Q%C}c~1)V@=DlEFeBFIUoE
zjDLG`d$buvxnoqk^5gHBgF^bo?7uP5#n|l4GIaH1`S$lrMNvimcM$0%?J81IzBSK6
z-P}ao_D^||pyiaH=oWnW>-lED0NSLwdY(bMuj9qO5txtQC(<U@Inq2CnZf@EyT+MX
zD^D=NfIg03(6Z?TKm?qS?+6V;Kckr%&*iA{@-sv%9wr+8JN*UfgU9+%nT<_Zqg+g+
z^^xFzuV6|7AIBg5_qhN0tpNI5^(;_=3$7GTB2=A{$iZ$z<m<wU1p$`@X0N8vpIu`;
z`@e1TuOc@TA+0*Ar|v}M^<P6x*eHf5xV9?CG6Xm@Q15H`?^go;SN{;WE_u~vDMlqJ
z7%FXYevG_g;D3)Z{Qv0D?mXEI1A(cKf?yMTbr#w4*f>Jkcmg*BhVcSu+8G%cWn^T6
zjydL0_fg%|K{l$L4Gh*CFeLxi4tjI~7lS3sAKP5;cL(<!?sqFTZJJaUDKydhY*X^o
z`SbhP<*s>&oImvSv0j1xj>W)p8-AsFy6Bm5KjV}uy`fpK$*4kXoqTy?^+DOISFc{w
z_XdVXWW|ZZg%2`;Yq0bmNA9QtTUzq>S1DL0>>P`iU;i^|6fTnLFM1&kJQ{_;(-pW_
I$|<1<04Xm9ssI20

literal 0
HcmV?d00001


From dfecbdd665ae20972ad0498cf5e42e1bc6e6b629 Mon Sep 17 00:00:00 2001
From: kahboom <rachelyordan@gmail.com>
Date: Thu, 15 Nov 2018 14:17:48 +0000
Subject: [PATCH 37/42] Add Issue Labels

---
 content/docs/development.md | 172 ++++++++++++++++++++++++++++++++++++
 1 file changed, 172 insertions(+)

diff --git a/content/docs/development.md b/content/docs/development.md
index e1cf6948..e91424df 100644
--- a/content/docs/development.md
+++ b/content/docs/development.md
@@ -81,3 +81,175 @@ Java packages.
 > will happen step-by-step. But for new groups and modules this scheme
 > has to be followed.
 
+
+# Issue Labels
+
+We use GitHub labels to categorize epics, issues and tasks. They are the
+foundation of our process, so please use labels for issues.
+
+> **Caution**
+> 
+> Labels are living entities. This document describes the current status
+> and might be slightly outdated. Please send a PR to adopt this section
+> if the label structure changes. Also feel free to discuss the label
+> structure anytime. It’s essential that labels describe our process,
+> not that we have to adapt our process for these labels.
+
+Labels are grouped. Each label consists of two parts: A **Group** and a
+**Name** which are separated by a slash (`/`). For example, the label
+`module/ui` is used to mark issue which is relevant to the Syndesis UI
+module.
+
+The following label groups are available. There must be only at most one
+label from the "Exclusive"
+groups.
+
+| Group       | Description                                                                                                                        | Excl. |
+| ----------- | ---------------------------------------------------------------------------------------------------------------------------------- | ----- |
+| **cat/**    | Misc categories which can be added freely                                                                                          |       |
+| **prio/**   | Priority of the issue. Only one `prio/` label must be added per issue. `prio/p0` is of highest priority, `prio/p2` the lowest one. | ✔︎    |
+| **ext/**    | Reference to external projects                                                                                                     |       |
+| **source/** | Where did the issue originate from (stakeholders)? i.e. `source/qe` indicates that QE raised this issue.                           |       |
+| **group/**  | Internal Syndesis modules                                                                                                          |       |
+| **source/** | Which external group has created the issue                                                                                         |       |
+| **notif/**  | Notification label which can be added and removed to ping certain subteams                                                         |       |
+| **pr/**     | Labels which are only relevant for pull request and which have also some semantics for the bot managing pull requests              |       |
+| **size/**   | Tee shirt size for issues. Sizing is a subjective assessment and should be done relative to other issues.                          | ✔︎    |
+| **status/** | Status of an issue or PR.                                                                                                          |       |
+
+Each label group serves a particular purpose, and for each issue and PR,
+it should be considered whether a label from a group applies.
+
+## Groups
+
+Labels from this group reference our application groups like "rest",
+"ui" or "connector". Each sub-team is responsible for one or more group,
+and every group has an 'owning' team. That does not mean that members of
+other teams are not allowed to work on such groups. Contrary, this is
+even encouraged. But its just there so that teams can filter on issues
+and PRs which are relevant to them.
+
+An issue can carry many group labels. Especially Epics will carry more
+than such label as they touch more than one group (otherwise it wouldn’t
+be an epic).
+
+For Java code, a "group" roughly corresponds to a directory directly
+below
+`app/`
+
+| Group                 | Description                                                     |
+| --------------------- | --------------------------------------------------------------- |
+| **group/common**      | Syndesis shared common module                                   |
+| **group/connector**   | Supported camel connectors                                      |
+| **group/extension**   | Tools for developing Syndesis extensions                        |
+| **group/install**     | Installing Syndesis (templates, scripts)                        |
+| **group/integration** | Library used in the the integration runtimes                    |
+| **group/meta**        | Service for connector meta-data and verification of connections |
+| **group/operator**    | Infrastructure operator related                                 |
+| **group/s2i**         | S2I base image for building integrations                        |
+| **group/server**      | REST backend for managing integrations                          |
+| **group/ui**          | User interface SPA, talking to the REST backend                 |
+| **group/uxd**         | User experience (UX) designs                                    |
+
+## Categories
+
+Labels from the `cat/` group are labels which can always be applied and
+which does not fit in another category. Currently we have these
+categories:
+
+| Category           | Description                                                                    |
+| ------------------ | ------------------------------------------------------------------------------ |
+| **cat/bug**        | A bug which needs fixing.                                                      |
+| **cat/build**      | For issues which have relevance for the build system.                          |
+| **cat/design**     | A concrete UX design. Use this for PRs containing UX designs.                  |
+| **cat/discussion** | This issues requires a discussion.                                             |
+| **cat/feature**    | PR label for a new feature                                                     |
+| **cat/process**    | Development process related issues carry this label.                           |
+| **cat/question**   | For issues holding a question.                                                 |
+| **cat/research**   | Label used for issues which describe some research work                        |
+| **cat/starter**    | An issue which is easy to solve and can be used for ramping up new developers. |
+| **cat/techdebt**   | Label for issues identifying technical debt.                                   |
+| **cat/techdoc**    | Technical developer information (likes this handbook ;-) related issues.       |
+| **cat/user-story** | A user story, which might not be an epic                                       |
+
+## Pull Requests
+
+This category of labels is all about pull requests. All of them have a
+meaning for the [pure-bot](https://github.com/syndesisio/pure-bot) bot
+which watches a pull request and performs certain action. These actions
+also involve monitoring and creating labels.
+
+The following labels are
+involved:
+
+| Notification            | Description                                                                                                                                                                                                                                                                                                                                                                                       |
+| ----------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| **pr/approved**         | This label will be automatically applied to a PR as soon as the PR has been approved at the end of a review. It is an indicator for [pure-bot](https://github.com/syndesisio/pure-bot) to automatically merge the pull request if it passes all required tests. You should not set this label manually for approving a PR but using the GitHub button to do so.                                   |
+| **pr/needs-backport**   | This pull request needs a corresponding backport to the latest patch branch.                                                                                                                                                                                                                                                                                                                      |
+| **pr/review-requested** | In our process it is not mandatory to have a PR review. However, if the author requests a review via the normal GitHub functionality, this label gets applied automatically. When this label is set on a pull-request, then the mandatory status check `pure-bot/review-requested` will only pass if at least a single pull request has been given, so prevents manual merging (without forcing). |
+| **status/wip**          | This is a PR request label which should be used for "Work-in-Progress" kind of PRs which has been submitted for early review. If this label is present on a PR, the PR is not merged, even when it is approved. A dedicated mandatory status check `pure-bot/wip` monitors this labels and prevents merging if this label is present.                                                             |
+| **status/1.4.x**        | This pull request is against the 1.4.x patch branch (analogous labels might appear over time)                                                                                                                                                                                                                                                                                                     |
+
+## Notification
+
+Notification labels from the `notif/` group serve a particular purpose.
+They are used when one team wants to notify another group that a
+specific issue might have them relevance to
+them.
+
+| Notification     | Description                                                                                                                                                                                                                      |
+| ---------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| **notif/doc**    | The issue needs some attention from the docs team. This might because a new feature has been introduced or, more important, an existing feature has changed for which a documentation already exists.                            |
+| **notif/pm**     | The issue needs input from product management.                                                                                                                                                                                   |
+| **notif/triage** | Every new issue gets this label and is considered during a triage session for properly priorisation and categorisation. Remove this label after the triage has happened.                                                         |
+| **notif/uxd**    | This label should be used for issues which needs some attention from the UX team. This might because a new feature has been introduced or, more important, an existing feature has changed for which a UX design already exists. |
+
+It is important to note that these labels also be removed when the
+notification has been received.
+
+For example, when a UI feature like an input form changes. Then the UI
+team attaches a `notif/uxd` label to the PR which introduces this
+change. The UX team, detects with a filter search on this label, that
+there is a new notification. It then decides, whether UX design needs to
+be updated or not. In any case, they are removing the `notif/uxd` label
+and add a `module/uxd` label if this PR indeed requires a UX design
+update. If no update is required, then the label is removed without
+replacement.
+
+## Source
+
+Labels starting with `source/` indicate the origin of an issue. It
+should be applied to help in triaging and priotizing.
+
+| Notification  | Description                      |
+| ------------- | -------------------------------- |
+| **source/qe** | This issue has been raised by QE |
+
+## External references
+
+This label group should be used if an external system is referenced,
+which is not part of the Syndesis mono
+repo.
+
+| External Project | Description                                                                                           |
+| ---------------- | ----------------------------------------------------------------------------------------------------- |
+| **ext/atlasmap** | [atlasmap](https://github.com/atlasmap/atlasmap) data mapper                                          |
+| **ext/qe**       | [syndesis-qe](https://github.com/syndesisio/syndesis-qe) suite                                        |
+| **ext/docs**     | [syndesis-documentation](https://github.com/syndesisio/syndesis-documentation) End user documentation |
+
+For the future, we plan to add more of these external repos into the
+Syndesis mono repo (like documentation or QE). If this happens, then
+labels should be converted to `module/` kind of labels.
+
+## Status
+
+Status labels are unique since they may trigger some automatic actions.
+
+The current status labels
+are:
+
+| Status             | Description                                                                                                                                  |
+| ------------------ | -------------------------------------------------------------------------------------------------------------------------------------------- |
+| **status/blocked** | The current issue is blocked by another issue. Refer to the issue itself to see what is blocking this issued. This label is purely informal. |
+
+

From 8bf837f1cf446b022eac000dcd5b0f14cd7a9fea Mon Sep 17 00:00:00 2001
From: kahboom <rachelyordan@gmail.com>
Date: Thu, 15 Nov 2018 14:18:24 +0000
Subject: [PATCH 38/42] Add Local section

---
 content/docs/development.md | 157 ++++++++++++++++++++++++++++++++++++
 1 file changed, 157 insertions(+)

diff --git a/content/docs/development.md b/content/docs/development.md
index e91424df..cde71129 100644
--- a/content/docs/development.md
+++ b/content/docs/development.md
@@ -253,3 +253,160 @@ are:
 | **status/blocked** | The current issue is blocked by another issue. Refer to the issue itself to see what is blocking this issued. This label is purely informal. |
 
 
+# Local Development
+
+If you’d like to get a local development environment up and running, for
+both the UI and REST API, this is how you’d do it.
+
+**Tips**
+
+  - Build on branch, not master.
+
+  - Callback URL Example:
+    <https://syndesis.192.168.64.29.nip.io/api/v1/credentials/callback>
+
+## Requirements
+
+You can follow these steps if it’s your first time setting up Syndesis,
+or if you want a fresh local installation to replace an existing one.
+Some environment-specific instructions may be available below as well.
+
+1.  Make sure you have installed [node](https://nodejs.org/en/download/)
+    version \>= 6.x.x and [Yarn](https://yarnpkg.com/en/docs/install)
+    version \>= 0.18.1.
+
+2.  Get a developer deployment of Syndesis running in a Minishift
+    environment as described in the [Syndesis
+    Quickstart](https://syndesis.io/quickstart/). Most are specific to
+    your environment, so follow the sections below for a quick setup.
+    The general instructions are:
+    
+      - Install a hypervisor for Minishift.
+    
+      - Install Minishift.
+    
+      - Install the OpenShift CLI.
+    
+      - Make sure it’s in your `$PATH`
+
+**macOS**
+
+If you’ll be using the Homebrew method, you’ll obviously need to have
+Homebrew installed. Then, to install the hypervisor for Minishift and
+Minishift itself:
+
+    $ brew install docker-machine-driver-xhyve
+    $ brew cask install minishift
+
+Finally, to install the OpenShift CLI, we recommend using Homebrew:
+`brew install openshift-cli`
+
+**Linux & Windows**
+
+  - [Install a hypervisor for
+    Minishift](https://docs.openshift.org/latest/minishift/getting-started/installing.html#install-prerequisites).
+    For macOS, we recommend using the Docker xhyve plugin
+    [here](https://docs.openshift.org/latest/minishift/getting-started/setting-up-driver-plugin.html#xhyve-driver-install),
+    which can be installed using Homebrew.
+
+  - [Install
+    Minishift](https://docs.openshift.org/latest/minishift/getting-started/installing.html#installing-instructions).
+    For macOS, we recommend you use the Homebrew method.
+
+Please note that you need to have the `oc` binary available in your
+`PATH`. To do that, see here:
+<https://docs.openshift.org/latest/cli_reference/get_started_cli.html>
+
+## First-Time Setup
+
+The goal here is to download the project to your laptop/PC, and to
+install Minishift, the VM that contains OpenShift.
+
+    $ git pull https://github.com/syndesisio/syndesis.git # or own fork
+    $ cd syndesis
+    $ syndesis minishift --full-reset
+
+## Day-to-Day
+
+This uses an existing Minishift instance.
+
+**NOTE:** If you already followed the First-Time Setup above, you do not
+need to follow this. The Minishift VM will already have been started.
+Simply skip to the
+
+**Get the Latest Changes**
+
+    $ git checkout master
+    $ git pull upstream master
+    $ git checkout <branch>
+    $ git rebase master
+
+**Start of the Day** Make sure Minishift is running.
+
+    $ minishift status
+
+Which should look like:
+
+    Minishift:  Running
+    Profile:    minishift
+    OpenShift:  Running (openshift v3.6.0+c4dd4cf)
+    DiskUsage:  11% of 17.9G
+
+If it isn’t, start it with:
+
+    $ minishift start
+
+**Login into and Set up OpenShift**
+
+This step is required regardless of whether it’s a first-time install or
+not. It logs you in and points OpenShift to use Minishift resources.
+
+    $ oc login -u developer
+    $ eval $(minishift oc-env)
+    $ eval $(minishift docker-env)
+
+The eval’s set a number of environment variables, like change the
+`$PATH` and `$DOCKER_HOST`, so each time you do a Syndesis build it’s
+good to make sure those are invoked.
+
+**End of the Day**
+
+    $ minishift stop
+
+**Start the UI App & Open in the Browser**
+
+    $ yarn start:minishift
+    $ open https://$(oc get routes syndesis --template "{{.spec.host}}")
+
+**Resetting the Database**
+
+This step is optional. This command expects Minishift to be running
+already. It’s the `-i docker` that determines the workflow, for Roland
+it seems to work without that though.
+
+It would clean the database if we increase the schema version, if we
+don’t it remains the same.
+
+    $ syndesis build -m rest -f -i docker -k
+
+Alternatively, you can use the REST API Endpoint:
+/api/v1/test-support/reset-db
+
+**Connecting to the Database**
+
+You can also port forward the DB’s port using `oc port-forward` and then
+connect to the database using a tool like
+[pgadmin](https://www.pgadmin.org/download/) to view the data. First get
+the DB pod’s name either from `oc get pods` or from the OpenShift
+console. Then use the following command:
+
+    $ oc port-forward <db pod name> 5432:5432
+
+Now start pgadmin and add a new DB server, use `localhost` for the
+`host` setting. For the username and password look on the DB pod’s
+`Environment` page in the OpenShift console.
+
+In pgadmin you can see the table by navigating into the tree under
+`Server Groups > Servers > syndesis > Databases > syndesis > Schemas >
+public > Tables > jsondb`. Right click, and then go to `View Data > View
+All Rows`.

From 746aaed46b0fe3c295c23f88bae7d3b73058b616 Mon Sep 17 00:00:00 2001
From: kahboom <rachelyordan@gmail.com>
Date: Thu, 15 Nov 2018 14:19:01 +0000
Subject: [PATCH 39/42] Add UI section

---
 content/docs/development.md | 118 ++++++++++++++++++++++++++++++++++++
 1 file changed, 118 insertions(+)

diff --git a/content/docs/development.md b/content/docs/development.md
index cde71129..c5d30200 100644
--- a/content/docs/development.md
+++ b/content/docs/development.md
@@ -410,3 +410,121 @@ In pgadmin you can see the table by navigating into the tree under
 `Server Groups > Servers > syndesis > Databases > syndesis > Schemas >
 public > Tables > jsondb`. Right click, and then go to `View Data > View
 All Rows`.
+
+
+# UI
+
+After you’ve set up your initial Local Development environment, you’re
+ready to contribute to the UI.
+
+## Install Dependencies
+
+From the project root directory:
+
+    $ cd app/ui
+    $ yarn install
+
+## Start up the App
+
+**Using Minishift resources (recommended):**
+
+    $ yarn start:minishift
+
+The `yarn start:minishift` command works when it can properly detect
+your local development machine’s IP address. A proxy server inside the
+minishift deployment will use that IP address to connect back to the
+development server being run by the yarn command. If detection of the IP
+is failing for you, then set the `SYNDESIS_DEV_LOCAL_IP` env variable to
+your local machine’s IP address before running the yarn `yarn
+start:minishift` command.
+
+## Open in Your Browser
+
+Open the Syndesis UI in your browser from the command line by running:
+
+``` bash
+# on macOS
+$ open https://$(oc get routes syndesis --template "{{.spec.host}}")
+```
+
+``` bash
+# on linux
+$ xdg-open https://$(oc get routes syndesis --template "{{.spec.host}}")
+```
+
+``` bash
+# on windows
+$ start https://$(oc get routes syndesis --template "{{.spec.host}}")
+```
+
+Another option is to run `minishift console`, go into **My Project** and
+click on the URL for the Syndesis app.
+
+To verify that you’re running against the development instance of the UI
+check the title of the browser tab you’ve opened and ensure it says
+`DEVELOPMENT` in in somewhere.
+
+**Not using Minishift resources** In the event that you have issues with
+Minishift. Don’t be surprised if most things don’t load and there isn’t
+any data in the UI. Only use this if you’re totally blocked and need to
+work on something minor/aesthetic in the UI.
+
+    $ yarn start
+
+## Running Tests
+
+To run tests or lint there are two more commands you can run in separate
+terminals.
+
+    $ yarn test
+
+## Running Linter
+
+If you don’t, the CI will, and your PR build will likely fail.
+
+    $ yarn lint
+
+You should be able to access the UI in your browser at
+<http://localhost:4200>
+
+## Code Documentation
+
+We use [Compodoc](https://compodoc.github.io/website/) for
+documentation, or
+[here](https://compodoc.github.io/website/guides/comments.html) to see
+how to format comments. Files get generated automatically in the
+`/documentation` directory. Read the documentation
+\[here\](<https://compodoc.github.io/website/guides/getting-started.html>)
+to see how to properly document features. You can automatically generate
+and run docs using Yarn:
+
+``` bash
+$ yarn compodoc
+```
+
+Or manually with `compodoc -s`, or `compodoc` if you want it to simply
+generate the files in the default `/documentation` directory and run it
+with an HTTP server.
+
+## Technology Stack
+
+Included in this stack are the following technologies:
+
+  - Language: [TypeScript](http://www.typescriptlang.org) (JavaScript
+    with @Types)
+
+  - Framework: [Angular](https://angular.io/)
+
+  - Testing: [Cucumber.js](https://cucumber.io/) (BDD Unit Test
+    Framework), [Karma](https://karma-runner.github.io/1.0/index.html)
+    (Unit Test Runner),
+    [Istanbul](https://github.com/gotwarlost/istanbul) (Code Coverage)
+
+  - Linting: [TsLint](https://github.com/palantir/tslint) (Linting for
+    TypeScript)
+
+  - Logging: WIP
+
+  - Code Analysis: [Codelyzer](https://github.com/mgechev/codelyzer)
+    (TsLint rules for static code analysis of Angular TypeScript
+    projects) / WIP

From ebc2a67b0b21cac2430ad3a923877feac14b64f6 Mon Sep 17 00:00:00 2001
From: kahboom <rachelyordan@gmail.com>
Date: Thu, 15 Nov 2018 14:19:37 +0000
Subject: [PATCH 40/42] Add REST API section

---
 content/docs/development.md | 7 +++++++
 1 file changed, 7 insertions(+)

diff --git a/content/docs/development.md b/content/docs/development.md
index c5d30200..98473fcc 100644
--- a/content/docs/development.md
+++ b/content/docs/development.md
@@ -528,3 +528,10 @@ Included in this stack are the following technologies:
   - Code Analysis: [Codelyzer](https://github.com/mgechev/codelyzer)
     (TsLint rules for static code analysis of Angular TypeScript
     projects) / WIP
+
+
+
+# REST API
+
+After you’ve set up your initial Local Development environment, you’re
+ready to contribute to the REST API.

From 9b86f18635875776197fbccd872d80c15f65f5bc Mon Sep 17 00:00:00 2001
From: kahboom <rachelyordan@gmail.com>
Date: Thu, 15 Nov 2018 14:20:04 +0000
Subject: [PATCH 41/42] Add Troubleshooting section

---
 content/docs/development.md | 55 +++++++++++++++++++++++++++++++++++++
 1 file changed, 55 insertions(+)

diff --git a/content/docs/development.md b/content/docs/development.md
index 98473fcc..2d4f988f 100644
--- a/content/docs/development.md
+++ b/content/docs/development.md
@@ -535,3 +535,58 @@ Included in this stack are the following technologies:
 
 After you’ve set up your initial Local Development environment, you’re
 ready to contribute to the REST API.
+
+
+# Troubleshooting
+
+When things go wrong, you want to try to identify the area that is
+causing problems (UI, REST API, etc). If it’s the UI, look for errors in
+the browser console or the terminal to see if it’s a dependency issue.
+
+## UI Dependency Issues
+
+    $ rm -rf node_modules
+    $ yarn install
+
+## VM Trouble
+
+**Not getting latest API changes**
+
+This is a known issue. This is the workaround for using the latest REST
+image from the Docker stream.
+
+**NOTE**: This deletes your Minishift instance, installs OpenShift
+templates for the pods, and restarts Minishift.
+
+Disclaimer: It’s not 100% clear what `-i` docker for `Syndesis Minishift
+--install` does exactly, but there is no way to invoke those evals
+before you get a running VM, which is what `--full-reset` does. So as a
+rule of thumb, you can have a terminal with those evals and keep it open
+and do all of the Syndesis building from there.
+
+    $ syndesis minishift --full-reset --install -p syndesis -i docker
+
+**syndesis command not found** If you get `'syndesis' command not found`
+then use the full path to the `syndesis` binary instead. This assumes
+you are in the root of the project
+    directory.
+
+    $ ./tools/bin/syndesis minishift --full-reset --install -p syndesis -i docker
+
+**If OpenShift templates have been updated** This should not be the
+first choice, since it changes the IP of the VM, and in general should
+not be necessary for just building and updating the version.
+
+    $ syndesis minishift --full-reset --install
+
+**VM Trouble**
+
+    $ syndesis build
+
+Other things you can try: - `rm -rf ~/.minishift` - Check the OpenShift
+console and look for logs. - Is it a xip or nip problem?
+<http://downoruprightnow.com/status/nip.io>
+
+## Still Having Trouble?
+
+Ask on IRC \#syndesis

From 1738f05182a4e87756584ec5502f869ce790a177 Mon Sep 17 00:00:00 2001
From: kahboom <rachelyordan@gmail.com>
Date: Thu, 15 Nov 2018 14:22:50 +0000
Subject: [PATCH 42/42] Resolve header issues

---
 content/docs/development.md | 51 +++++++++++++++++++------------------
 1 file changed, 26 insertions(+), 25 deletions(-)

diff --git a/content/docs/development.md b/content/docs/development.md
index 2d4f988f..07bddff5 100644
--- a/content/docs/development.md
+++ b/content/docs/development.md
@@ -11,7 +11,7 @@ toc: true
 weight: 20
 ---
 
-# Maven Groups
+## Maven Groups
 
 Syndesis uses [Maven](http://maven.apache.org/) as build tool. Maven
 groups are used to separate the various Syndesis parts.
@@ -35,7 +35,7 @@ groups:
 
 ![](images/syndesis-group-dependencies.png)
 
-## Naming Conventions
+### Naming Conventions
 
 The following conventions are used for naming directories, modules and
 Java packages.
@@ -82,7 +82,7 @@ Java packages.
 > has to be followed.
 
 
-# Issue Labels
+## Issue Labels
 
 We use GitHub labels to categorize epics, issues and tasks. They are the
 foundation of our process, so please use labels for issues.
@@ -120,7 +120,7 @@ groups.
 Each label group serves a particular purpose, and for each issue and PR,
 it should be considered whether a label from a group applies.
 
-## Groups
+### Groups
 
 Labels from this group reference our application groups like "rest",
 "ui" or "connector". Each sub-team is responsible for one or more group,
@@ -151,7 +151,7 @@ below
 | **group/ui**          | User interface SPA, talking to the REST backend                 |
 | **group/uxd**         | User experience (UX) designs                                    |
 
-## Categories
+### Categories
 
 Labels from the `cat/` group are labels which can always be applied and
 which does not fit in another category. Currently we have these
@@ -172,7 +172,7 @@ categories:
 | **cat/techdoc**    | Technical developer information (likes this handbook ;-) related issues.       |
 | **cat/user-story** | A user story, which might not be an epic                                       |
 
-## Pull Requests
+### Pull Requests
 
 This category of labels is all about pull requests. All of them have a
 meaning for the [pure-bot](https://github.com/syndesisio/pure-bot) bot
@@ -190,7 +190,7 @@ involved:
 | **status/wip**          | This is a PR request label which should be used for "Work-in-Progress" kind of PRs which has been submitted for early review. If this label is present on a PR, the PR is not merged, even when it is approved. A dedicated mandatory status check `pure-bot/wip` monitors this labels and prevents merging if this label is present.                                                             |
 | **status/1.4.x**        | This pull request is against the 1.4.x patch branch (analogous labels might appear over time)                                                                                                                                                                                                                                                                                                     |
 
-## Notification
+### Notification
 
 Notification labels from the `notif/` group serve a particular purpose.
 They are used when one team wants to notify another group that a
@@ -241,7 +241,7 @@ For the future, we plan to add more of these external repos into the
 Syndesis mono repo (like documentation or QE). If this happens, then
 labels should be converted to `module/` kind of labels.
 
-## Status
+### Status
 
 Status labels are unique since they may trigger some automatic actions.
 
@@ -253,7 +253,7 @@ are:
 | **status/blocked** | The current issue is blocked by another issue. Refer to the issue itself to see what is blocking this issued. This label is purely informal. |
 
 
-# Local Development
+## Local Development
 
 If you’d like to get a local development environment up and running, for
 both the UI and REST API, this is how you’d do it.
@@ -265,7 +265,7 @@ both the UI and REST API, this is how you’d do it.
   - Callback URL Example:
     <https://syndesis.192.168.64.29.nip.io/api/v1/credentials/callback>
 
-## Requirements
+### Requirements
 
 You can follow these steps if it’s your first time setting up Syndesis,
 or if you want a fresh local installation to replace an existing one.
@@ -317,7 +317,7 @@ Please note that you need to have the `oc` binary available in your
 `PATH`. To do that, see here:
 <https://docs.openshift.org/latest/cli_reference/get_started_cli.html>
 
-## First-Time Setup
+### First-Time Setup
 
 The goal here is to download the project to your laptop/PC, and to
 install Minishift, the VM that contains OpenShift.
@@ -326,7 +326,7 @@ install Minishift, the VM that contains OpenShift.
     $ cd syndesis
     $ syndesis minishift --full-reset
 
-## Day-to-Day
+### Day-to-Day
 
 This uses an existing Minishift instance.
 
@@ -412,19 +412,19 @@ public > Tables > jsondb`. Right click, and then go to `View Data > View
 All Rows`.
 
 
-# UI
+## UI
 
 After you’ve set up your initial Local Development environment, you’re
 ready to contribute to the UI.
 
-## Install Dependencies
+### Install Dependencies
 
 From the project root directory:
 
     $ cd app/ui
     $ yarn install
 
-## Start up the App
+### Start up the App
 
 **Using Minishift resources (recommended):**
 
@@ -438,7 +438,7 @@ is failing for you, then set the `SYNDESIS_DEV_LOCAL_IP` env variable to
 your local machine’s IP address before running the yarn `yarn
 start:minishift` command.
 
-## Open in Your Browser
+### Open in Your Browser
 
 Open the Syndesis UI in your browser from the command line by running:
 
@@ -471,14 +471,14 @@ work on something minor/aesthetic in the UI.
 
     $ yarn start
 
-## Running Tests
+### Running Tests
 
 To run tests or lint there are two more commands you can run in separate
 terminals.
 
     $ yarn test
 
-## Running Linter
+### Running Linter
 
 If you don’t, the CI will, and your PR build will likely fail.
 
@@ -487,7 +487,7 @@ If you don’t, the CI will, and your PR build will likely fail.
 You should be able to access the UI in your browser at
 <http://localhost:4200>
 
-## Code Documentation
+### Code Documentation
 
 We use [Compodoc](https://compodoc.github.io/website/) for
 documentation, or
@@ -506,7 +506,7 @@ Or manually with `compodoc -s`, or `compodoc` if you want it to simply
 generate the files in the default `/documentation` directory and run it
 with an HTTP server.
 
-## Technology Stack
+### Technology Stack
 
 Included in this stack are the following technologies:
 
@@ -531,24 +531,24 @@ Included in this stack are the following technologies:
 
 
 
-# REST API
+## REST API
 
 After you’ve set up your initial Local Development environment, you’re
 ready to contribute to the REST API.
 
 
-# Troubleshooting
+## Troubleshooting
 
 When things go wrong, you want to try to identify the area that is
 causing problems (UI, REST API, etc). If it’s the UI, look for errors in
 the browser console or the terminal to see if it’s a dependency issue.
 
-## UI Dependency Issues
+### UI Dependency Issues
 
     $ rm -rf node_modules
     $ yarn install
 
-## VM Trouble
+### VM Trouble
 
 **Not getting latest API changes**
 
@@ -587,6 +587,7 @@ Other things you can try: - `rm -rf ~/.minishift` - Check the OpenShift
 console and look for logs. - Is it a xip or nip problem?
 <http://downoruprightnow.com/status/nip.io>
 
-## Still Having Trouble?
+
+### Still Having Trouble?
 
 Ask on IRC \#syndesis