You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@hop.apache.org by ha...@apache.org on 2021/04/01 08:36:30 UTC
[incubator-hop-docs] branch asf-site updated: HOP-2670 getting
started update, new concepts page
This is an automated email from the ASF dual-hosted git repository.
hansva pushed a commit to branch asf-site
in repository https://gitbox.apache.org/repos/asf/incubator-hop-docs.git
The following commit(s) were added to refs/heads/asf-site by this push:
new e4e468a HOP-2670 getting started update, new concepts page
new ff8e57f Merge pull request #63 from bamaer/HOP-2670
e4e468a is described below
commit e4e468ad8e7c476ce0541fa68ea7c804f416cdec
Author: Bart Maertens <ba...@know.bi>
AuthorDate: Thu Apr 1 07:57:05 2021 +0200
HOP-2670 getting started update, new concepts page
---
.../getting-started-debug-dialog.png | Bin 64600 -> 0 bytes
.../getting-started-debug-pipeline.png | Bin 65943 -> 0 bytes
.../getting-started-debug-results.png | Bin 56897 -> 0 bytes
.../getting-started-execution-results-metrics.png | Bin 26064 -> 0 bytes
.../getting-started/getting-started-hop-gui.png | Bin 11701 -> 0 bytes
.../getting-started/getting-started-new-dialog.png | Bin 69907 -> 0 bytes
.../getting-started-new-pipeline.png | Bin 65121 -> 0 bytes
.../getting-started-new-slave-config.png | Bin 83469 -> 0 bytes
.../getting-started-new-slave-run-config.png | Bin 114389 -> 0 bytes
.../getting-started/getting-started-new-slave.png | Bin 53489 -> 0 bytes
.../getting-started-new-transform.png | Bin 143202 -> 0 bytes
.../getting-started-preview-dialog.png | Bin 55180 -> 0 bytes
.../getting-started-preview-pipeline.png | Bin 47704 -> 0 bytes
.../getting-started-preview-results.png | Bin 52513 -> 0 bytes
.../getting-started-run-configuration-dialog.png | Bin 73108 -> 0 bytes
.../getting-started-run-pipeline-dialog.png | Bin 50272 -> 0 bytes
.../getting-started-run-workflow-logging.png | Bin 230863 -> 0 bytes
.../getting-started-run-workflow-metrics.png | Bin 162969 -> 0 bytes
.../getting-started-save-pipeline.png | Bin 23784 -> 0 bytes
.../getting-started-server-index.png | Bin 17976 -> 0 bytes
...ing-started-server-status-after-run-details.png | Bin 117401 -> 0 bytes
.../getting-started-server-status-after-run.png | Bin 118999 -> 0 bytes
.../getting-started-server-status.png | Bin 108332 -> 0 bytes
.../gs-hop-gui-create-pipeline-1.png | Bin 0 -> 73652 bytes
.../gs-hop-gui-create-pipeline-2.png | Bin 0 -> 42763 bytes
.../gs-hop-gui-create-pipeline-3.png | Bin 0 -> 73652 bytes
.../gs-hop-gui-create-pipeline-4.png | Bin 0 -> 20248 bytes
.../gs-hop-gui-create-pipeline-5.png | Bin 0 -> 7579 bytes
.../gs-hop-gui-create-pipeline-6.png | Bin 0 -> 53887 bytes
.../gs-hop-gui-create-pipeline-7.png | Bin 0 -> 115333 bytes
.../gs-hop-gui-create-pipeline-8.png | Bin 0 -> 115236 bytes
.../gs-hop-gui-create-pipeline-9.png | Bin 0 -> 118494 bytes
...-hop-gui-create-pipeline-add-two-transforms.png | Bin 0 -> 15304 bytes
.../gs-hop-gui-create-pipeline-create-hop.png | Bin 0 -> 14478 bytes
.../gs-hop-gui-create-workflow-1.png | Bin 0 -> 66749 bytes
.../gs-hop-gui-create-workflow-2.png | Bin 0 -> 42763 bytes
.../gs-hop-gui-create-workflow-3.png | Bin 0 -> 66749 bytes
.../gs-hop-gui-create-workflow-4.png | Bin 0 -> 32839 bytes
.../gs-hop-gui-create-workflow-5.png | Bin 0 -> 7579 bytes
.../gs-hop-gui-create-workflow-6.png | Bin 0 -> 45243 bytes
.../gs-hop-gui-create-workflow-7.png | Bin 0 -> 112901 bytes
...hop-gui-create-workflow-add-pipeline-action.png | Bin 0 -> 5049 bytes
.../gs-hop-gui-create-workflow-run.png | Bin 0 -> 19869 bytes
.../gs-hop-gui-create-workflow-save.png | Bin 0 -> 40818 bytes
.../getting-started/gs-hop-gui-overview-1.png | Bin 0 -> 13038 bytes
.../getting-started/gs-hop-gui-overview-2.png | Bin 0 -> 17683 bytes
.../getting-started/gs-hop-gui-run-pipeline-1.png | Bin 0 -> 35199 bytes
.../getting-started/gs-hop-gui-run-pipeline-2.png | Bin 0 -> 45420 bytes
.../getting-started/gs-hop-gui-run-pipeline-3.png | Bin 0 -> 18592 bytes
.../getting-started/gs-hop-gui-run-pipeline-4.png | Bin 0 -> 40551 bytes
.../getting-started/gs-hop-gui-run-pipeline-5.png | Bin 0 -> 6348 bytes
.../getting-started/gs-hop-gui-run-pipeline-6.png | Bin 0 -> 11464 bytes
.../getting-started/gs-hop-gui-run-pipeline-7.png | Bin 0 -> 23269 bytes
hop-user-manual/modules/ROOT/nav.adoc | 10 +-
hop-user-manual/modules/ROOT/pages/concepts.adoc | 62 +--
.../modules/ROOT/pages/getting-started.adoc | 461 ---------------------
.../ROOT/pages/getting-started/hop-concepts.adoc | 22 +
.../getting-started/hop-download-install.adoc | 27 ++
.../pages/getting-started/hop-gui-pipelines.adoc | 103 +++++
.../pages/getting-started/hop-gui-workflows.adoc | 72 ++++
.../ROOT/pages/getting-started/hop-gui.adoc | 43 ++
.../ROOT/pages/getting-started/hop-next-steps.adoc | 16 +
.../ROOT/pages/getting-started/hop-tools.adoc | 95 +++++
.../pages/getting-started/hop-what-is-hop.adoc | 33 ++
.../modules/ROOT/pages/getting-started/index.adoc | 22 +
.../ROOT/pages/snippets/hop-concepts/action.adoc | 1 +
.../pages/snippets/hop-concepts/environment.adoc | 2 +
.../hop-concepts/hop-projects-environments.adoc | 9 +
.../ROOT/pages/snippets/hop-concepts/hop.adoc | 1 +
.../pages/snippets/hop-concepts/item-types.adoc | 22 +
.../pages/snippets/hop-concepts/lazy-loading.adoc | 3 +
.../ROOT/pages/snippets/hop-concepts/metadata.adoc | 1 +
.../ROOT/pages/snippets/hop-concepts/pipeline.adoc | 1 +
.../ROOT/pages/snippets/hop-concepts/project.adoc | 2 +
.../pages/snippets/hop-concepts/transform.adoc | 1 +
.../ROOT/pages/snippets/hop-concepts/workflow.adoc | 1 +
.../ROOT/pages/snippets/hop-tools/hop-conf.adoc | 1 +
.../ROOT/pages/snippets/hop-tools/hop-encrypt.adoc | 3 +
.../ROOT/pages/snippets/hop-tools/hop-gui.adoc | 1 +
.../ROOT/pages/snippets/hop-tools/hop-run.adoc | 1 +
.../ROOT/pages/snippets/hop-tools/hop-search.adoc | 1 +
.../ROOT/pages/snippets/hop-tools/hop-server.adoc | 1 +
.../ROOT/pages/snippets/hop-tools/hop-tools.adoc | 22 +
.../pages/snippets/hop-tools/hop-translator.adoc | 1 +
84 files changed, 523 insertions(+), 518 deletions(-)
diff --git a/hop-user-manual/modules/ROOT/assets/images/getting-started/getting-started-debug-dialog.png b/hop-user-manual/modules/ROOT/assets/images/getting-started/getting-started-debug-dialog.png
deleted file mode 100644
index 8961d69..0000000
Binary files a/hop-user-manual/modules/ROOT/assets/images/getting-started/getting-started-debug-dialog.png and /dev/null differ
diff --git a/hop-user-manual/modules/ROOT/assets/images/getting-started/getting-started-debug-pipeline.png b/hop-user-manual/modules/ROOT/assets/images/getting-started/getting-started-debug-pipeline.png
deleted file mode 100644
index 4765dc2..0000000
Binary files a/hop-user-manual/modules/ROOT/assets/images/getting-started/getting-started-debug-pipeline.png and /dev/null differ
diff --git a/hop-user-manual/modules/ROOT/assets/images/getting-started/getting-started-debug-results.png b/hop-user-manual/modules/ROOT/assets/images/getting-started/getting-started-debug-results.png
deleted file mode 100644
index 192c842..0000000
Binary files a/hop-user-manual/modules/ROOT/assets/images/getting-started/getting-started-debug-results.png and /dev/null differ
diff --git a/hop-user-manual/modules/ROOT/assets/images/getting-started/getting-started-execution-results-metrics.png b/hop-user-manual/modules/ROOT/assets/images/getting-started/getting-started-execution-results-metrics.png
deleted file mode 100644
index 02ac9a2..0000000
Binary files a/hop-user-manual/modules/ROOT/assets/images/getting-started/getting-started-execution-results-metrics.png and /dev/null differ
diff --git a/hop-user-manual/modules/ROOT/assets/images/getting-started/getting-started-hop-gui.png b/hop-user-manual/modules/ROOT/assets/images/getting-started/getting-started-hop-gui.png
deleted file mode 100644
index 2131fa6..0000000
Binary files a/hop-user-manual/modules/ROOT/assets/images/getting-started/getting-started-hop-gui.png and /dev/null differ
diff --git a/hop-user-manual/modules/ROOT/assets/images/getting-started/getting-started-new-dialog.png b/hop-user-manual/modules/ROOT/assets/images/getting-started/getting-started-new-dialog.png
deleted file mode 100644
index bafedbd..0000000
Binary files a/hop-user-manual/modules/ROOT/assets/images/getting-started/getting-started-new-dialog.png and /dev/null differ
diff --git a/hop-user-manual/modules/ROOT/assets/images/getting-started/getting-started-new-pipeline.png b/hop-user-manual/modules/ROOT/assets/images/getting-started/getting-started-new-pipeline.png
deleted file mode 100644
index 355bad1..0000000
Binary files a/hop-user-manual/modules/ROOT/assets/images/getting-started/getting-started-new-pipeline.png and /dev/null differ
diff --git a/hop-user-manual/modules/ROOT/assets/images/getting-started/getting-started-new-slave-config.png b/hop-user-manual/modules/ROOT/assets/images/getting-started/getting-started-new-slave-config.png
deleted file mode 100644
index b4db566..0000000
Binary files a/hop-user-manual/modules/ROOT/assets/images/getting-started/getting-started-new-slave-config.png and /dev/null differ
diff --git a/hop-user-manual/modules/ROOT/assets/images/getting-started/getting-started-new-slave-run-config.png b/hop-user-manual/modules/ROOT/assets/images/getting-started/getting-started-new-slave-run-config.png
deleted file mode 100644
index f6eda64..0000000
Binary files a/hop-user-manual/modules/ROOT/assets/images/getting-started/getting-started-new-slave-run-config.png and /dev/null differ
diff --git a/hop-user-manual/modules/ROOT/assets/images/getting-started/getting-started-new-slave.png b/hop-user-manual/modules/ROOT/assets/images/getting-started/getting-started-new-slave.png
deleted file mode 100644
index 6f1433a..0000000
Binary files a/hop-user-manual/modules/ROOT/assets/images/getting-started/getting-started-new-slave.png and /dev/null differ
diff --git a/hop-user-manual/modules/ROOT/assets/images/getting-started/getting-started-new-transform.png b/hop-user-manual/modules/ROOT/assets/images/getting-started/getting-started-new-transform.png
deleted file mode 100644
index 91db819..0000000
Binary files a/hop-user-manual/modules/ROOT/assets/images/getting-started/getting-started-new-transform.png and /dev/null differ
diff --git a/hop-user-manual/modules/ROOT/assets/images/getting-started/getting-started-preview-dialog.png b/hop-user-manual/modules/ROOT/assets/images/getting-started/getting-started-preview-dialog.png
deleted file mode 100644
index a603322..0000000
Binary files a/hop-user-manual/modules/ROOT/assets/images/getting-started/getting-started-preview-dialog.png and /dev/null differ
diff --git a/hop-user-manual/modules/ROOT/assets/images/getting-started/getting-started-preview-pipeline.png b/hop-user-manual/modules/ROOT/assets/images/getting-started/getting-started-preview-pipeline.png
deleted file mode 100644
index 33f7b86..0000000
Binary files a/hop-user-manual/modules/ROOT/assets/images/getting-started/getting-started-preview-pipeline.png and /dev/null differ
diff --git a/hop-user-manual/modules/ROOT/assets/images/getting-started/getting-started-preview-results.png b/hop-user-manual/modules/ROOT/assets/images/getting-started/getting-started-preview-results.png
deleted file mode 100644
index a057dc9..0000000
Binary files a/hop-user-manual/modules/ROOT/assets/images/getting-started/getting-started-preview-results.png and /dev/null differ
diff --git a/hop-user-manual/modules/ROOT/assets/images/getting-started/getting-started-run-configuration-dialog.png b/hop-user-manual/modules/ROOT/assets/images/getting-started/getting-started-run-configuration-dialog.png
deleted file mode 100644
index 7a489d6..0000000
Binary files a/hop-user-manual/modules/ROOT/assets/images/getting-started/getting-started-run-configuration-dialog.png and /dev/null differ
diff --git a/hop-user-manual/modules/ROOT/assets/images/getting-started/getting-started-run-pipeline-dialog.png b/hop-user-manual/modules/ROOT/assets/images/getting-started/getting-started-run-pipeline-dialog.png
deleted file mode 100644
index 270c1f6..0000000
Binary files a/hop-user-manual/modules/ROOT/assets/images/getting-started/getting-started-run-pipeline-dialog.png and /dev/null differ
diff --git a/hop-user-manual/modules/ROOT/assets/images/getting-started/getting-started-run-workflow-logging.png b/hop-user-manual/modules/ROOT/assets/images/getting-started/getting-started-run-workflow-logging.png
deleted file mode 100644
index 40a7fb3..0000000
Binary files a/hop-user-manual/modules/ROOT/assets/images/getting-started/getting-started-run-workflow-logging.png and /dev/null differ
diff --git a/hop-user-manual/modules/ROOT/assets/images/getting-started/getting-started-run-workflow-metrics.png b/hop-user-manual/modules/ROOT/assets/images/getting-started/getting-started-run-workflow-metrics.png
deleted file mode 100644
index 77fd704..0000000
Binary files a/hop-user-manual/modules/ROOT/assets/images/getting-started/getting-started-run-workflow-metrics.png and /dev/null differ
diff --git a/hop-user-manual/modules/ROOT/assets/images/getting-started/getting-started-save-pipeline.png b/hop-user-manual/modules/ROOT/assets/images/getting-started/getting-started-save-pipeline.png
deleted file mode 100644
index b1359b7..0000000
Binary files a/hop-user-manual/modules/ROOT/assets/images/getting-started/getting-started-save-pipeline.png and /dev/null differ
diff --git a/hop-user-manual/modules/ROOT/assets/images/getting-started/getting-started-server-index.png b/hop-user-manual/modules/ROOT/assets/images/getting-started/getting-started-server-index.png
deleted file mode 100644
index 59d0915..0000000
Binary files a/hop-user-manual/modules/ROOT/assets/images/getting-started/getting-started-server-index.png and /dev/null differ
diff --git a/hop-user-manual/modules/ROOT/assets/images/getting-started/getting-started-server-status-after-run-details.png b/hop-user-manual/modules/ROOT/assets/images/getting-started/getting-started-server-status-after-run-details.png
deleted file mode 100644
index 35b7d3c..0000000
Binary files a/hop-user-manual/modules/ROOT/assets/images/getting-started/getting-started-server-status-after-run-details.png and /dev/null differ
diff --git a/hop-user-manual/modules/ROOT/assets/images/getting-started/getting-started-server-status-after-run.png b/hop-user-manual/modules/ROOT/assets/images/getting-started/getting-started-server-status-after-run.png
deleted file mode 100644
index c005f04..0000000
Binary files a/hop-user-manual/modules/ROOT/assets/images/getting-started/getting-started-server-status-after-run.png and /dev/null differ
diff --git a/hop-user-manual/modules/ROOT/assets/images/getting-started/getting-started-server-status.png b/hop-user-manual/modules/ROOT/assets/images/getting-started/getting-started-server-status.png
deleted file mode 100644
index 6ffee87..0000000
Binary files a/hop-user-manual/modules/ROOT/assets/images/getting-started/getting-started-server-status.png and /dev/null differ
diff --git a/hop-user-manual/modules/ROOT/assets/images/getting-started/gs-hop-gui-create-pipeline-1.png b/hop-user-manual/modules/ROOT/assets/images/getting-started/gs-hop-gui-create-pipeline-1.png
new file mode 100644
index 0000000..7e05ea8
Binary files /dev/null and b/hop-user-manual/modules/ROOT/assets/images/getting-started/gs-hop-gui-create-pipeline-1.png differ
diff --git a/hop-user-manual/modules/ROOT/assets/images/getting-started/gs-hop-gui-create-pipeline-2.png b/hop-user-manual/modules/ROOT/assets/images/getting-started/gs-hop-gui-create-pipeline-2.png
new file mode 100644
index 0000000..19778f0
Binary files /dev/null and b/hop-user-manual/modules/ROOT/assets/images/getting-started/gs-hop-gui-create-pipeline-2.png differ
diff --git a/hop-user-manual/modules/ROOT/assets/images/getting-started/gs-hop-gui-create-pipeline-3.png b/hop-user-manual/modules/ROOT/assets/images/getting-started/gs-hop-gui-create-pipeline-3.png
new file mode 100644
index 0000000..7e05ea8
Binary files /dev/null and b/hop-user-manual/modules/ROOT/assets/images/getting-started/gs-hop-gui-create-pipeline-3.png differ
diff --git a/hop-user-manual/modules/ROOT/assets/images/getting-started/gs-hop-gui-create-pipeline-4.png b/hop-user-manual/modules/ROOT/assets/images/getting-started/gs-hop-gui-create-pipeline-4.png
new file mode 100644
index 0000000..c822dfc
Binary files /dev/null and b/hop-user-manual/modules/ROOT/assets/images/getting-started/gs-hop-gui-create-pipeline-4.png differ
diff --git a/hop-user-manual/modules/ROOT/assets/images/getting-started/gs-hop-gui-create-pipeline-5.png b/hop-user-manual/modules/ROOT/assets/images/getting-started/gs-hop-gui-create-pipeline-5.png
new file mode 100644
index 0000000..c569f11
Binary files /dev/null and b/hop-user-manual/modules/ROOT/assets/images/getting-started/gs-hop-gui-create-pipeline-5.png differ
diff --git a/hop-user-manual/modules/ROOT/assets/images/getting-started/gs-hop-gui-create-pipeline-6.png b/hop-user-manual/modules/ROOT/assets/images/getting-started/gs-hop-gui-create-pipeline-6.png
new file mode 100644
index 0000000..2fe830a
Binary files /dev/null and b/hop-user-manual/modules/ROOT/assets/images/getting-started/gs-hop-gui-create-pipeline-6.png differ
diff --git a/hop-user-manual/modules/ROOT/assets/images/getting-started/gs-hop-gui-create-pipeline-7.png b/hop-user-manual/modules/ROOT/assets/images/getting-started/gs-hop-gui-create-pipeline-7.png
new file mode 100644
index 0000000..3b9fe91
Binary files /dev/null and b/hop-user-manual/modules/ROOT/assets/images/getting-started/gs-hop-gui-create-pipeline-7.png differ
diff --git a/hop-user-manual/modules/ROOT/assets/images/getting-started/gs-hop-gui-create-pipeline-8.png b/hop-user-manual/modules/ROOT/assets/images/getting-started/gs-hop-gui-create-pipeline-8.png
new file mode 100644
index 0000000..01e2af4
Binary files /dev/null and b/hop-user-manual/modules/ROOT/assets/images/getting-started/gs-hop-gui-create-pipeline-8.png differ
diff --git a/hop-user-manual/modules/ROOT/assets/images/getting-started/gs-hop-gui-create-pipeline-9.png b/hop-user-manual/modules/ROOT/assets/images/getting-started/gs-hop-gui-create-pipeline-9.png
new file mode 100644
index 0000000..d2b20cd
Binary files /dev/null and b/hop-user-manual/modules/ROOT/assets/images/getting-started/gs-hop-gui-create-pipeline-9.png differ
diff --git a/hop-user-manual/modules/ROOT/assets/images/getting-started/gs-hop-gui-create-pipeline-add-two-transforms.png b/hop-user-manual/modules/ROOT/assets/images/getting-started/gs-hop-gui-create-pipeline-add-two-transforms.png
new file mode 100644
index 0000000..1a7c063
Binary files /dev/null and b/hop-user-manual/modules/ROOT/assets/images/getting-started/gs-hop-gui-create-pipeline-add-two-transforms.png differ
diff --git a/hop-user-manual/modules/ROOT/assets/images/getting-started/gs-hop-gui-create-pipeline-create-hop.png b/hop-user-manual/modules/ROOT/assets/images/getting-started/gs-hop-gui-create-pipeline-create-hop.png
new file mode 100644
index 0000000..2a69a73
Binary files /dev/null and b/hop-user-manual/modules/ROOT/assets/images/getting-started/gs-hop-gui-create-pipeline-create-hop.png differ
diff --git a/hop-user-manual/modules/ROOT/assets/images/getting-started/gs-hop-gui-create-workflow-1.png b/hop-user-manual/modules/ROOT/assets/images/getting-started/gs-hop-gui-create-workflow-1.png
new file mode 100644
index 0000000..d23edd6
Binary files /dev/null and b/hop-user-manual/modules/ROOT/assets/images/getting-started/gs-hop-gui-create-workflow-1.png differ
diff --git a/hop-user-manual/modules/ROOT/assets/images/getting-started/gs-hop-gui-create-workflow-2.png b/hop-user-manual/modules/ROOT/assets/images/getting-started/gs-hop-gui-create-workflow-2.png
new file mode 100644
index 0000000..19778f0
Binary files /dev/null and b/hop-user-manual/modules/ROOT/assets/images/getting-started/gs-hop-gui-create-workflow-2.png differ
diff --git a/hop-user-manual/modules/ROOT/assets/images/getting-started/gs-hop-gui-create-workflow-3.png b/hop-user-manual/modules/ROOT/assets/images/getting-started/gs-hop-gui-create-workflow-3.png
new file mode 100644
index 0000000..d23edd6
Binary files /dev/null and b/hop-user-manual/modules/ROOT/assets/images/getting-started/gs-hop-gui-create-workflow-3.png differ
diff --git a/hop-user-manual/modules/ROOT/assets/images/getting-started/gs-hop-gui-create-workflow-4.png b/hop-user-manual/modules/ROOT/assets/images/getting-started/gs-hop-gui-create-workflow-4.png
new file mode 100644
index 0000000..0912b8a
Binary files /dev/null and b/hop-user-manual/modules/ROOT/assets/images/getting-started/gs-hop-gui-create-workflow-4.png differ
diff --git a/hop-user-manual/modules/ROOT/assets/images/getting-started/gs-hop-gui-create-workflow-5.png b/hop-user-manual/modules/ROOT/assets/images/getting-started/gs-hop-gui-create-workflow-5.png
new file mode 100644
index 0000000..c569f11
Binary files /dev/null and b/hop-user-manual/modules/ROOT/assets/images/getting-started/gs-hop-gui-create-workflow-5.png differ
diff --git a/hop-user-manual/modules/ROOT/assets/images/getting-started/gs-hop-gui-create-workflow-6.png b/hop-user-manual/modules/ROOT/assets/images/getting-started/gs-hop-gui-create-workflow-6.png
new file mode 100644
index 0000000..48fad7e
Binary files /dev/null and b/hop-user-manual/modules/ROOT/assets/images/getting-started/gs-hop-gui-create-workflow-6.png differ
diff --git a/hop-user-manual/modules/ROOT/assets/images/getting-started/gs-hop-gui-create-workflow-7.png b/hop-user-manual/modules/ROOT/assets/images/getting-started/gs-hop-gui-create-workflow-7.png
new file mode 100644
index 0000000..9f44725
Binary files /dev/null and b/hop-user-manual/modules/ROOT/assets/images/getting-started/gs-hop-gui-create-workflow-7.png differ
diff --git a/hop-user-manual/modules/ROOT/assets/images/getting-started/gs-hop-gui-create-workflow-add-pipeline-action.png b/hop-user-manual/modules/ROOT/assets/images/getting-started/gs-hop-gui-create-workflow-add-pipeline-action.png
new file mode 100644
index 0000000..c38ba08
Binary files /dev/null and b/hop-user-manual/modules/ROOT/assets/images/getting-started/gs-hop-gui-create-workflow-add-pipeline-action.png differ
diff --git a/hop-user-manual/modules/ROOT/assets/images/getting-started/gs-hop-gui-create-workflow-run.png b/hop-user-manual/modules/ROOT/assets/images/getting-started/gs-hop-gui-create-workflow-run.png
new file mode 100644
index 0000000..0e67a73
Binary files /dev/null and b/hop-user-manual/modules/ROOT/assets/images/getting-started/gs-hop-gui-create-workflow-run.png differ
diff --git a/hop-user-manual/modules/ROOT/assets/images/getting-started/gs-hop-gui-create-workflow-save.png b/hop-user-manual/modules/ROOT/assets/images/getting-started/gs-hop-gui-create-workflow-save.png
new file mode 100644
index 0000000..8153b21
Binary files /dev/null and b/hop-user-manual/modules/ROOT/assets/images/getting-started/gs-hop-gui-create-workflow-save.png differ
diff --git a/hop-user-manual/modules/ROOT/assets/images/getting-started/gs-hop-gui-overview-1.png b/hop-user-manual/modules/ROOT/assets/images/getting-started/gs-hop-gui-overview-1.png
new file mode 100644
index 0000000..b873ea8
Binary files /dev/null and b/hop-user-manual/modules/ROOT/assets/images/getting-started/gs-hop-gui-overview-1.png differ
diff --git a/hop-user-manual/modules/ROOT/assets/images/getting-started/gs-hop-gui-overview-2.png b/hop-user-manual/modules/ROOT/assets/images/getting-started/gs-hop-gui-overview-2.png
new file mode 100644
index 0000000..3bcaef6
Binary files /dev/null and b/hop-user-manual/modules/ROOT/assets/images/getting-started/gs-hop-gui-overview-2.png differ
diff --git a/hop-user-manual/modules/ROOT/assets/images/getting-started/gs-hop-gui-run-pipeline-1.png b/hop-user-manual/modules/ROOT/assets/images/getting-started/gs-hop-gui-run-pipeline-1.png
new file mode 100644
index 0000000..c3c72ca
Binary files /dev/null and b/hop-user-manual/modules/ROOT/assets/images/getting-started/gs-hop-gui-run-pipeline-1.png differ
diff --git a/hop-user-manual/modules/ROOT/assets/images/getting-started/gs-hop-gui-run-pipeline-2.png b/hop-user-manual/modules/ROOT/assets/images/getting-started/gs-hop-gui-run-pipeline-2.png
new file mode 100644
index 0000000..2dbdf57
Binary files /dev/null and b/hop-user-manual/modules/ROOT/assets/images/getting-started/gs-hop-gui-run-pipeline-2.png differ
diff --git a/hop-user-manual/modules/ROOT/assets/images/getting-started/gs-hop-gui-run-pipeline-3.png b/hop-user-manual/modules/ROOT/assets/images/getting-started/gs-hop-gui-run-pipeline-3.png
new file mode 100644
index 0000000..63a4fbf
Binary files /dev/null and b/hop-user-manual/modules/ROOT/assets/images/getting-started/gs-hop-gui-run-pipeline-3.png differ
diff --git a/hop-user-manual/modules/ROOT/assets/images/getting-started/gs-hop-gui-run-pipeline-4.png b/hop-user-manual/modules/ROOT/assets/images/getting-started/gs-hop-gui-run-pipeline-4.png
new file mode 100644
index 0000000..c53c1ed
Binary files /dev/null and b/hop-user-manual/modules/ROOT/assets/images/getting-started/gs-hop-gui-run-pipeline-4.png differ
diff --git a/hop-user-manual/modules/ROOT/assets/images/getting-started/gs-hop-gui-run-pipeline-5.png b/hop-user-manual/modules/ROOT/assets/images/getting-started/gs-hop-gui-run-pipeline-5.png
new file mode 100644
index 0000000..915e321
Binary files /dev/null and b/hop-user-manual/modules/ROOT/assets/images/getting-started/gs-hop-gui-run-pipeline-5.png differ
diff --git a/hop-user-manual/modules/ROOT/assets/images/getting-started/gs-hop-gui-run-pipeline-6.png b/hop-user-manual/modules/ROOT/assets/images/getting-started/gs-hop-gui-run-pipeline-6.png
new file mode 100644
index 0000000..2778fd6
Binary files /dev/null and b/hop-user-manual/modules/ROOT/assets/images/getting-started/gs-hop-gui-run-pipeline-6.png differ
diff --git a/hop-user-manual/modules/ROOT/assets/images/getting-started/gs-hop-gui-run-pipeline-7.png b/hop-user-manual/modules/ROOT/assets/images/getting-started/gs-hop-gui-run-pipeline-7.png
new file mode 100644
index 0000000..d57497e
Binary files /dev/null and b/hop-user-manual/modules/ROOT/assets/images/getting-started/gs-hop-gui-run-pipeline-7.png differ
diff --git a/hop-user-manual/modules/ROOT/nav.adoc b/hop-user-manual/modules/ROOT/nav.adoc
index f10bc30..ad94cc7 100644
--- a/hop-user-manual/modules/ROOT/nav.adoc
+++ b/hop-user-manual/modules/ROOT/nav.adoc
@@ -1,4 +1,12 @@
-* xref:getting-started.adoc[Getting Started]
+* xref:getting-started/index.adoc[Getting Started]
+** xref:getting-started/hop-what-is-hop.adoc[What is Hop]
+** xref:getting-started/hop-concepts.adoc[Hop Concepts]
+** xref:getting-started/hop-download-install.adoc[Download & Install]
+** xref:getting-started/hop-tools.adoc[Tools]
+** xref:getting-started/hop-gui.adoc[Hop Gui Overview]
+** xref:getting-started/hop-gui-pipelines.adoc[Pipelines]
+** xref:getting-started/hop-gui-workflows.adoc[Workflows]
+** xref:getting-started/hop-next-steps.adoc[Next Steps]
* xref:concepts.adoc[Concepts]
* xref:hop-gui/index.adoc[Hop Gui]
** xref:hop-gui/file-browser.adoc[File Browser]
diff --git a/hop-user-manual/modules/ROOT/pages/concepts.adoc b/hop-user-manual/modules/ROOT/pages/concepts.adoc
index aaa003e..db0f7e3 100644
--- a/hop-user-manual/modules/ROOT/pages/concepts.adoc
+++ b/hop-user-manual/modules/ROOT/pages/concepts.adoc
@@ -3,69 +3,19 @@
= Concepts
-== Components
+include::snippets/hop-tools/hop-tools.adoc[]
-.Hop Components
-[width="90%", cols="3*", options="header"]
-|=======
-|Name |Description |Since
-|Hop UI |Hop UI is the visual IDE where Workflow and Pipeline developers create, test and run their work before the code is ready to be deployed. |0.1
-|Hop Server |Hop Server is a lightweight web server that allows to run Workflows and Pipelines through a REST api. |0.1
-|Hop CLI |Hop CLI is a command line interface (CLI) for headless execution of Workflows and Pipelines |0.1
-|=======
+include::snippets/hop-concepts/item-types.adoc[]
-== Item types
-
-.Hop Item Types
-[width="90%", cols="3*", options="header"]
-|===
-|Name |Description |Since
-|Workflow |A Workflow is a sequence of operations that are performed sequentially by default (with optional parallel execution). Workflows usually do not operate on the data directly, but perform orchestration tasks. Typical tasks in a Workflow consist of retrieving and archiving data, sending emails, error handling etc. ) |0.1
-|Pipeline |Pipelines are the actual data workers. Operations in a Pipeline read, modify, enrich, clean and write data. Orchestration of Pipelines is done through othere Pipelines and/or Workflows.|0.1
-|Action |An Action is one operation performed in a Workflow. Actions are executed sequentially by default, with parallel execution as a configuration option. An Action returns a true or false exit code, which can be used (or ignored) in the Workflow's execution. |0.1
-|Transform |A Transform is a unit of work performed in a Pipeline. Typical Transform operations are reading data from files, databases, performing lookups or joins, enriching, cleaning data and more. All transforms in a Pipeline are executed in parallel. Transforms process data and move batches of processed data on Hops for processing by subsequent Actions. |0.1
-|Hop |A Hop links Actions in a Workflow or Transforms in a Pipeline. In Workflows, Hops operate based on the exit status of previous Actions, Hops in Pipelines pass data between Transforms. |0.1
-|===
-
-image::concepts/workflow.png[Workflow]
-image::concepts/pipeline.png[Pipeline]
-
-
-== Environment
-
-The link:hop-gui/environments/environments.html[Hop Environment] allows data developers to manage development, acceptance and production environments with their configurations and variables.
-Each environment will remember your opened files, their zoom level and other UI settings.
-
-image::concepts/environments.png[Environment Examples]
+include::snippets/hop-concepts/hop-projects-environments.adoc[]
== Metadata
-The Hop Metadata is the central storage repository for shared metadata like relational database connections, run configurations, servers, git repositories and so on.
-The Metastore uses the following elements:
-
-* *Object types*: Object types have a key, a name and (optionally) a description.
-* *Objects*: Every object type can have any number of objects which are identified their name
-Hop plugins can define their own metadata object types so depending on the installed plugins you can find extra types.
+include::snippets/hop-concepts/metadata.adoc[]
== Various
The following items are an alphabetically ordered list of concepts that are used throughout Hop and will be mentioned at various locations in the Hop tools and documentation.
-.Various Hop Concepts
-[width="90%", cols="2*", options="header"]
-|===
-|Concept | Description
-|Lazy Loading
-| If enabled, all data conversions (character decoding, data conversion, trimming, ...) for the data being read will be postponed as long as possible, effectively reading the data as binary fields. Enabling lazy conversion can significantly decrease the CPU cost of reading data.
-
-
-When to avoid: if the data conversion needs to be performed later in the stream anyway, postponing the conversion may slow things down instead of speeding up.
-
-
-Use cases where Lazy Conversion may speed things up:
-
- - data is read and written to another file without conversion
-
- - data needs to be sorted and doesn't fit in memory. In this case, serialization to disk is faster with lazy conversion because encoding and type conversions are postponed.
- - bulk-loading to database without the need for data conversion. Bulk loading utilities typically read text directly and the generation of this text is faster (this does not apply to Table Output).
-|===
\ No newline at end of file
+Lazy Loading::
+include::snippets/hop-concepts/lazy-loading.adoc[]
\ No newline at end of file
diff --git a/hop-user-manual/modules/ROOT/pages/getting-started.adoc b/hop-user-manual/modules/ROOT/pages/getting-started.adoc
deleted file mode 100644
index 1d8f5fc..0000000
--- a/hop-user-manual/modules/ROOT/pages/getting-started.adoc
+++ /dev/null
@@ -1,461 +0,0 @@
-[[GettingStarted]]
-:imagesdir: ../assets/images
-
-= Getting Started
-
-
-== Getting Started with Hop
-* https://hop.apache.org/download/[Download] a recent Hop build.
-* unzip hop to a local directory
-* change to the hop directory
-
-== Introducing Hop
-Hop is a metadata driven environment where you manage your data processing workflows.
-
-Before anything else, we need to explain Hop's two main concepts:
-
-* **Workflow** is a (by default) sequential process that has a starting point and one or more endpoints.
-Between the start and endpoint, a variety of 'actions' can be performed. These actions can range from executing other workflows or pipelines, archiving files that were processed, sending error messages or success notifications and much more.
-
-* **Pipelines** are more granular items of work. A pipeline is where the actual work is done. Pipelines consist of a chain of transforms that read, process or write data.
-Depending on the execution engine your pipelines run, this can be in batch, streaming or a hybrid mode.
-
-The actions in a workflow and the transforms in a pipeline are connected by 'hops'. Hop are visual links between actions (workflows) and transforms (pipelines).
-
-As you'll discover soon, the process of creating workflows and pipelines is very similar.
-
-However, there are a number of conceptual differences between workflows and pipelines that you have to keep in mind:
-
-* the pipeline engine executes all transforms in a pipeline simultaneously and in parallel. The workflow engine executes all actions in a workflow sequentially by default. When action finishes, the workflow engine checks which action needs to be executed next.
-* hops in a pipeline pass data between transforms. In a workflow, hops can conditionally determine which action the workflow needs to execute next (on success, on failure, unconditionally)
-* because of their sequential nature, workflows have 1 action to start from and 1 or more end actions. Pipelines can start with input from multiple transforms simultaneously.
-
-
-The following tools are at your disposal to work with Hop flows and pipelines:
-
-* the **Hop Gui** is your visual IDE to build, preview, run, test, deploy, ... workflows and pipelines.
-* the **Hop Server** is a lightweight web server that provides a REST api to run workflows and pipelines remotely.
-* **Hop Run** is a command line utility to run workflows and pipelines.
-
-== The Hop GUI
-
-The Hop Gui is your local development environment to build, run, preview and debug (work)flows and pipelines.
-
-Check out this short video to learn how to download, unzip and start the Hop Gui (on Windows).
-
-<!-- [html-validate-disable-next deprecated] -->
-video::RMIOTmZK-YE[youtube, width=75%, height=400px]
-
-=== Start the Hop GUI
-
-On Linux:
-[source,bash]
- ./hop-gui.sh
-
-On Windows:
-[source,bash]
-hop-gui.bat
-
-=== Hop GUI Walkthrough
-
-After starting the Hop Gui, you'll be presented with a window like the one below.
-
-image::getting-started/getting-started-hop-gui.png[Hop Gui , 75% , align="left"]
-
-After clicking the 'New' icon in the upper left corner, you'll be presented with the window below.
-Choose either 'New Workflow' or 'New Pipeline'.
-
-image::getting-started/getting-started-new-dialog.png[Hop - New Dialog, 75% , align="left"]
-
-==== Pipeline Editor Overview
-
-Your new pipeline is created, and you'll see the dialog below.
-
-image::getting-started/getting-started-new-pipeline.png[Hop - New Pipeline, 75%, align="left"]
-
-Let's walk through the top toolbar:
-
-image::getting-started/getting-started-pipeline-toolbar.png[Hop - Pipeline Toolbar, align="left"]
-
-[width="85%", cols="15%,5%,80%", options="header"]
-|===
-|Action|Icon|Description
-|run|image:getting-started/icons/run.svg[Run, 25px, align="bottom"]|start the execution of the pipeline
-|pause|image:getting-started/icons/pause.svg[Pause, 25px, align="bottom"]|pause the execution of the pipeline
-|stop|image:getting-started/icons/stop.svg[Stop, 25px, align="bottom"]|stop the execution of the pipeline
-|||
-|preview|image:getting-started/icons/view.svg[Preview, 25px, align="bottom"]|preview the pipeline
-|debug|image:getting-started/icons/debug.svg[Debug, 25px, align="bottom"]|debug the pipeline
-|print|image:getting-started/icons/print.png[Print, 25px, align="bottom"]|print the pipeline
-|||
-|undo|image:getting-started/icons/Antu_edit-undo.svg[Undo, 25px, align="bottom"]|undo an operation
-|redo|image:getting-started/icons/Antu_edit-redo.svg[Redo, 25px, align="bottom"]|redo an operation
-|||
-|align|image:getting-started/icons/snap-to-grid.svg[Snap To Grid, 25px, align="bottom"]|align the specified (selected) transforms to the specified grid size
-|align left|image:getting-started/icons/align-left.svg[Align Left, 25px, align="bottom"]|align the selected transforms with left-most selected transform in the selection
-|align right|image:getting-started/icons/align-right.svg[Align Right, 25px, align="bottom"]|align the selected transforms with right-most selected transform in the selection
-|align top|image:getting-started/icons/align-top.svg[Align Top, 25px, align="bottom"]|align the selected transforms with top-most selected transform in the selection
-|align bottom|image:getting-started/icons/align-bottom.svg[Align Bottom, 25px, align="bottom"]|align the selected transforms with bottom-most selected transform in the selection
-|||
-|distribute horizontally|image:getting-started/icons/distribute-horizontally.svg[Distribute Horizontally, 25px, align="bottom"]|Distribute the selected transforms evenly between the left-most and right-most transform in your selection
-|distribute vertically|image:getting-started/icons/distribute-vertically.svg[Distribute Vertically, 25px, align="bottom"]|Distribute the selected transforms evenly between the top-most and bottom-most transform in your selection
-|===
-
-=== Build Your First Pipeline
-
-==== Concepts
-Pipelines consist of two main work items:
-
-* **transforms** are the basic operations in your pipeline. A pipeline typically consists of a lot of transforms that are chained together by hops.
-Transforms are granular, in the sense that each transform is designed and optimized to perform one and only one task. Although one transform by itself may not offer spectacular functionality, the combination of all transforms in a pipeline is makes your pipelines powerful.
-
-* **hops** link transforms together. When a transform finishes processing the data set it received, that data set is passed to the next transform through a hop.
-Hops are uni-directional (data can't flow backwards). Hops only buffer and pass data around, the hop itself is transform-agnostic, it doesn't know anything about the transforms it passes data from or to.
-Some transforms can read from or write to other transforms conditionally to or from a number of other transforms, but this a transform-specific configuration. The hop is unaware of it.
-Hops can be disabled by clicking on them, or through right-click -> disable.
-
-==== Add Transforms
-
-Click anywhere in the pipeline canvas, the area where you'll see the image below.
-
-image::getting-started/getting-started-click-anywhere.png[Hop - Click Anywhere, 45% , align="left"]
-
-Upon clicking, you'll be presented with the dialog shown below. The search box at the top of this dialog works for transform, name, tags (TODO) etc.
-Once you've found the transform you're looking for, click on it to add it to your pipeline. An alternative to clicking is arrow key navigation + enter.
-Repeat this step now or whenever you want to add more transforms to your pipeline.
-Once you've added a transform to your pipeline, you can drag to reposition it.
-
-TODO: link to transform documentation.
-
-image::getting-started/getting-started-add-transform.png[Hop - Add Transform, 75% , align="left"]
-
-Add a 'Generate Rows' and a 'Add Sequence' transform, and your pipeline should like the one below.
-
-image::getting-started/getting-started-add-two-transforms.png[Hop - Add two transforms, 75% , align="left"]
-
-
-==== Add a Hop
-
-There are a number of ways to create a hop:
-
-* shift-drag: while holding down the shift key on your keyboard. Click on a transform, while holding down your primary mouse button, drag to the second transform. Release the primary mouse button and the shift key.
-* scroll-drag: scroll-click on a transform , while holding down your mouse's scroll button, drag to the second transform. Release the scroll button.
-* click on a transform in your pipeline to open the 'click anywhere' dialog. Click the 'Create hop' image::getting-started/icons/HOP.svg[Create hop, 25px, align="bottom"] button and select the transform you want to create the hop to.
-
-image::getting-started/getting-started-create-hop.png[Hop - Create Hop, 65% , align="left"]
-
-=== Run your first Pipeline
-
-Click the 'run' button image::getting-started/icons/run.svg[Run, 25px, align="bottom"] in your pipeline toolbar
-
-image::getting-started/getting-started-run-pipeline-dialog.png[Hop - Create Hop, 75% , align="left"]
-
-Let's walk through the options in this dialog
-
-* Pipeline run configurations, edit, new, manage your run configurations. Run configurations are used to specify a name, description and engine to run your pipeline.
-* Log level: choose the log level for your pipeline. The available options are
-** Nothing
-** Error
-** Minimal
-** Basic (default)
-** Detailed
-** Debugging
-** Row Level (very detailed)
-* Clear log before running (enabled by default): logging information from previous runs will be cleared from the logging tab.
-* parameters: This table will show the parameter name, default value and description. enter your runtime parameters in the 'value' field.
-* variables: add the variable name and value you want to set in this tab.
-* always show dialog on run (enabled by default): You'll be presented with this dialog every time you run this dialog. When disabled, the pipeline will run with the default options.
-
-Click the 'New' button right next to the 'Pipeline run configuration'.
-Give your run configuration a name and (optionally) a description. Choose the 'local pipeline engine'. As the name implies, the 'local single threaded pipeline engine' runs the pipeline in a single CPU thread. The default 'local pipeline engine' will create a separate CPU thread for each transform in your pipeline to evenly spread the load of your pipeline over your CPU cores.
-
-image::getting-started/getting-started-run-configuration-dialog.png[Hop - Run Configuration Dialog, 75% , align="left"]
-
-Click 'Ok' to create your configuration and select it from the dropdown list.
-For this getting started guide, we'll leave all other options to the defaults. Click 'Launch'.
-
-Since we haven't saved our pipeline yet, you'll be prompted to do so by the dialog below.
-
-image::getting-started/getting-started-save-pipeline.png[Hop - Save Pipeline, 55% , align="left"]
-
-Your pipeline will finish in a matter of milliseconds, and the 'Execution Result' view will show up at the bottom of your IDE.
-This view has 5 tabs:
-
-* transform metrics: transformName, read, written, input, output, update, rejected, errors, buffers input, buffers output, speed, status (TODO: elaborate)
-* logging: the logging output for your pipeline
-* preview data: a preview of the data for the selected transform. This grid shows the data as it passed through this transform.
-* metrics: TODO
-* performance graph: TODO
-
-image::getting-started/getting-started-execution-results-metrics.png[Hop - Execution Results Metrics, 75% , align="left"]
-
-
-=== Preview your first Pipeline
-
-While developing your pipeline, you'll often want to check your data as it enters or exits a transform.
-Previews are an easy way to take a glance at the state of your data stream as it exits a transform.
-
-To preview the data that is processed by a transform, click on a transform and select 'Preview output'.
-The same result can be achieved by selecting a transform in your pipeline (rectangle select) and clicking the preview (eye) icon in the pipeline toolbar.
-
-image::getting-started/getting-started-preview-pipeline.png[Hop - Preview Transform, 75% , align="left"]
-
-You'll be presented with the dialog below. You can change the number of rows to preview (1000 by default), but in most cases, you'll just want to hit the green 'Quick Launch' button.
-
-image::getting-started/getting-started-preview-dialog.png[Hop - Preview Dialog, 75% , align="left"]
-
-Once your pipeline finished processing the selected number of rows for the selected transform, a new popup dialog will show your preview results.
-
-image::getting-started/getting-started-preview-results.png[Hop - Preview Results, 75% , align="left"]
-
-IMPORTANT: your **entire** pipeline is executed for a preview, you're just taking a peek into the processing at the selected transform. If your pipeline modifies data (writes, updates, deletes) further down the stream, those actions **will* be performed, even if you're previewing an earlier transform.
-
-Let's take a quick look at the buttons at the bottom of this dialog:
-
-* Close: closes the preview dialog. The pipeline will remain paused, and will therefore still be active.
-* Stop: stop the preview and the pipeline execution.
-* Get more rows: fetch the next 1000 (or any other selected amount of) rows for preview.
-
-=== Debug your first Pipeline
-
-Debugging a pipeline's transform is very similar to previewing. Instead of pausing the pipeline execution after a given number of rows, the pipeline is paused when a given condition is met.
-The process to start a debug session is similar to starting the preview: click on a transform and select 'Debug output' from the pop-up dialog, or select a transform and hit the bug-icon in the pipeline toolbar.
-
-image::getting-started/getting-started-debug-pipeline.png[Hop - Preview Transform, 75% , align="left"]
-
-You'll be presented with the dialog below. You'll recognize this dialog from the 'preview' we just did, but instead, the 'Retrieve first rows (preview)' option is now unchecked, and 'Pause pipeline on condition' is checked.
-
-In the 'Break-point / pause condition' below that option, you can specify on which condition you want to debug. This dialog is the same as the https://hop.apache.org/manual/latest/plugins/transforms/filterrows.html[Filter Rows] transform.
-
-In our very basic example, we've set a breakpoint on 'valuename > 5'.
-
-image::getting-started/getting-started-debug-dialog.png[Hop - Preview Dialog, 75% , align="left"]
-
-With the 'valuename > 5' breakpoint, our pipeline is paused as soon as this condition is met (valuename = 6). The rows preceding that moment are also shown, so you can investigate how your data was processed before the breakpoint condition was true.
-
-Similar to the preview options, you can close, stop or continue the debugging ('Get more rows'). When you tell your pipeline to 'Get more rows', the pipeline execution will be resumed until the breakpoint condition is met once more, instead of just fetching the next 1000 (default) rows.
-
-image::getting-started/getting-started-debug-results.png[Hop - Preview Results, 75% , align="left"]
-
-
-
-=== Create your first Workflow
-
-The design and execution of workflows is very similar to that of pipelines. However, keep in mind that there are significant differences between how Hop handles workflows and pipelines under the hood.
-
-To create a workflow, hit the 'new' icon or 'CTRL-N'. From the pop-up dialog, select 'New workflow'.
-
-image::getting-started/getting-started-new-workflow.png[Hop - New Workflow, 75% , align="left"]
-
-Add the following actions to your workflow and create the hops to connect them:
-
-* Start
-* Pipeline
-* Success
-
-image::getting-started/getting-started-new-workflow-actions.png[Hop - New Workflow with actions, 75% , align="left"]
-
-Double-click or single-click and choose 'Edit action' to configure the action for the pipeline you just created.
-
-In the pipeline dialog, use the 'Browse' button to select your pipeline and give the action an appropriate name, for example 'First Pipeline'.
-
-Click 'OK'.
-
-image::getting-started/getting-started-new-workflow-pipeline-action.png[Hop - New Workflow pipeline action, 75% , align="left"]
-
-Notice how the hops in your workflow are a little different from what you've seen in pipeline hops.
-
-Add a fourth action 'Abort' and create a hop from your pipeline action.
-
-image::getting-started/getting-started-new-workflow-abort.png[Hop - New Workflow abort, 75% , align="left"]
-
-You now have the three types of hops that are available in workflows:
-
-* unconditional (lock icon, black hop): 'unconditional' hops are followed no matter what the exit code (true/false) of the previous action is
-* success (green hop, check mark): 'success' hops are used when the previous action executed successfully.
-* failure (red hop, error mark): 'failure' or 'error' hops are followed when the previous action failed.
-
-NOTE: The hop type can be changed by clicking on the hop's icon.
-
-With these three hop types and the actions at your disposal, you're ready to create powerful data orchestration workflows.
-
-=== Run your first Workflow
-
-As with designing workflows, the steps to run a workflow are very similar to running a pipeline.
-
-Click the 'run' button image:getting-started/icons/run.svg[Run, 25px, align="bottom"] in your workflow toolbar
-
-In the workflow run dialog, hit the 'New' button in the upper right corner to create a new 'Workflow run configuration'.
-
-image::getting-started/getting-started-run-workflow-dialog.png[Hop - New Workflow Config, 75% , align="left"]
-
-In the dialog that pops up, add 'Local Workflow' as the workflow configuration name and choose the 'Local workflow engine'.
-
-image::getting-started/getting-started-run-workflow-config-dialog.png[Hop - New Workflow Config Dialog, 75% , align="left"]
-
-Click 'OK' to return to the workflow run dialog, make sure your configuration is selected and hit 'Launch'.
-
-image::getting-started/getting-started-run-workflow-with-config.png[Hop - New Workflow With Config Dialog, 75% , align="left"]
-
-This workflow with our very basic pipeline should execute in less than one second. You'll now have the execution results pane which again looks very similar to the pipeline execution results.
-
-The first tab in your workflow execution is 'Logging'. This tab shows the logging information for your entire workflow. Any errors that occurred in your workflow will be highlighted in red.
-
-image::getting-started/getting-started-run-workflow-logging.png[Hop - New Workflow Logging, 75% , align="left"]
-
-The second tab are your workflow metrics. This tab is less verbose, but gives you an action-by-action overview of the execution of your workflow. The black, green and red color codings indicate information, success and failure.
-In larger worfklows, the metrics tab will give you a quick overview of what happened in your workflow, what the required time per action was, etc.
-
-You'll use the logging tab to find more detailed information about what happened in your workflow or in a particular action.
-
-image::getting-started/getting-started-run-workflow-metrics.png[Hop - New Workflow Metrics, 75% , align="left"]
-
-
-== Hop Server
-
-After you've designed and tested your pipeline or transform locally, you may want to run it on a headless machine.
-
-The Hop Server is a light weight web server that you can use to run your workflows and pipelines remotely.
-
-First, we'll have to start the server. Head over to your Hop directory, and locate the 'hop-server' scripts (sh for Mac/Linux, bat for Windows).
-
-Running the script without any arguments will print its usage:
-
-[source,bash]
-Usage: hop-server <Interface address> <Port> [-h] [-p <arg>] [-s] [-u <arg>]
-or
-Usage: hop-server <Configuration File>
-Starts or stops the hopServer server.
- -h,--help This help text
- -p,--password <arg> The administrator password. Required only if
- stopping the Hop Server server.
- -s,--stop Stop the running hopServer server. This is only
- allowed when using the hostname/port form of the
- command.
- -u,--userName <arg> The administrator user name. Required only if
- stopping the Hop Server server.
-Example: hop-server.sh 127.0.0.1 8080
-Example: hop-server.sh 192.168.1.221 8081
-Example: hop-server.sh /foo/bar/hop-server-config.xml
-Example: hop-server.sh http://www.example.com/hop-server-config.xml
-Example: hop-server.sh 127.0.0.1 8080 -s -u cluster -p cluster
-
-As an example, let's run our server on our local machine on port 8085:
-
-On Linux:
-[source,bash]
- ./hop-server.sh localhost 8085
-
-On Windows:
-[source,bash]
-hop-server.bat localhost 8085
-
-The startup process shouldn't take more than 1 or 2 seconds, and should show 2 lines of logging information:
-
-[source,bash]
-2020/04/30 16:22:55 - HopServer - Installing timer to purge stale objects after 1440 minutes.
-2020/04/30 16:22:55 - HopServer - Created listener for webserver @ address : localhost:8085
-
-In your favorite browser, go to http://localhost:8085[] and sign in with the default user 'cluster' and password 'cluster'.
-
-Click the 'show status' link below to get to page shown in the second screenshot.
-
-image::getting-started/getting-started-server-index.png[Hop - Server Index, 75% , align="left"]
-
-image::getting-started/getting-started-server-status.png[Hop - Server Status, 75% , align="left"]
-
-We now have verified our server is up and running. Let's return to Hop Gui to configure a run configuration for it.
-Click the 'New' icon or 'CTRL-N' and select 'Slave Server'.
-
-image::getting-started/getting-started-new-slave.png[Hop - New Slave, 75% , align="left"]
-
-In the slave server dialog, enter the details for the local server we just created.
-
-image::getting-started/getting-started-new-slave-config.png[Hop - New Slave Config, 75% , align="left"]
-
-With our slave server in place, all that's left to do is to create a run configuration for this server.
-Head back to your pipeline (again, the process is similar for workflows), and hit 'run'. Before running your pipeline, create a new 'Pipeline run configuration'.
-
-Name this configuration 'Remote Pipeline', select 'Remote pipeline engine' as the engine type, select the 'local' run configuration we created earlier, and select 'localhost' for the slave server we just created.
-
-Select this run configuration and run your pipeline. Your execution results will be almost identical to the locale execution you did earlier, however, the logs will show you executed the pipeline remotely:
-
-[source,bash]
-2020/04/30 17:01:33 - first_pipeline - Executing this pipeline using the Remote Pipeline Engine with run configuration 'Remote Pipeline'
-...
-...
-...
-2020/04/30 17:01:34 - first_pipeline - Execution finished on a remote pipeline engine with run configuration 'Remote Pipeline'
-
-The execution results for this pipeline will now be available in our server's status page as well:
-
-image::getting-started/getting-started-server-status-after-run.png[Hop - Server Status, 75% , align="left"]
-
-Select the pipeline or workflow line that you want to investigate, and choose one of the options from the options in the upper left corner of the pipeline or workflow overview table.
-Click the eye icon to open the details for that specfific execution:
-
-image::getting-started/getting-started-server-status-after-run-details.png[Hop - Server Status Details, 75% , align="left"]
-
-
-== Hop Run
-
-Hop Run is the last tool we'll discuss in this getting started overview.
-In many cases, you'll want to run your workflows and pipelines on a headless server, but don't necessarily want to run through rest services or from Hop Gui.
-
-Hop Run is a command line that can be used to run workflows or pipelines e.g. over ssh of from a cron job.
-
-The command to run is 'hop-run' (sh on Mac/Linux, bat on Windows).
-Without any arguments, hop-run shows its usage syntax:
-
-[source,bash]
-A filename is needed to run a workflow or pipeline
-Usage: <main class> [-hotw] [-e=<environment>] [-f=<filename>] [-l=<level>]
- [-r=<runConfigurationName>] [-p=<parameters>[,
- <parameters>...]]... [-s=<systemProperties>[,
- <systemProperties>...]]...
- -e, --environment=<environment>
- The name of the environment to use
- -f, --file=<filename> The filename of the workflow or pipeline to run
- -h, --help Displays this help message and quits.
- -l, --level=<level> The debug level, one of NONE, MINIMAL, BASIC, DETAILED,
- DEBUG, ROWLEVEL
- -o, --printoptions Print the used options
- -p, --parameters=<parameters>[,<parameters>...]
- A comma separated list of PARAMETER=VALUE pairs
- -r, --runconfig=<runConfigurationName>
- The name of the Run Configuration to use
- -s, --system-properties=<systemProperties>[,<systemProperties>...]
- A comma separated list of KEY=VALUE pairs
- -t, --pipeline Force execution of a pipeline
- -w, --workflow Force execution of a workflow
-
-
-Since we've been working with a very basic pipeline, running it from hop-run is as easy as specifying:
-* the pipeline filename to run
-* the run configuration to use
-
-[source,bash]
- ./hop-run.sh -f /tmp/first_pipeline.hpl -r local
-
-You'll get output that will be very similar to the one below:
-
-[source,bash]
-2020/04/30 17:16:48 - first_pipeline - Executing this pipeline using the Local Pipeline Engine with run configuration 'local'
-2020/04/30 17:16:48 - first_pipeline - Execution started for pipeline [first_pipeline]
-2020/04/30 17:16:48 - Generate rows.0 - Finished processing (I=0, O=0, R=0, W=10, U=0, E=0)
-2020/04/30 17:16:48 - Add sequence.0 - Finished processing (I=0, O=0, R=10, W=10, U=0, E=0)
-2020/04/30 17:16:48 - first_pipeline - Pipeline duration : 0.079 seconds [ 0.079 ]
-2020/04/30 17:16:48 - first_pipeline - Execution finished on a local pipeline engine with run configuration 'local'
-./hop-run.sh -f /tmp/first_pipeline.hpl -r local 5.62s user 0.34s system 258% cpu 2.309 total
-
-== Where to go from here?
-
-We'll be adding more documentation as we go, so keep an eye on the https://hop.apache.org/manual/latest/[Apache Hop (Incubating)] documentation section.
-
-A good place to start exploring is the detailed documentation for:
-
-* https://hop.apache.org/manual/latest/plugins/actions.html[Workflow Actions]
-* https://hop.apache.org/manual/latest/plugins/transforms.html[Pipeline Transforms]
-
-NOTE: Apache Hop (Incubating) considers high-quality documentation a very important part of the project. Help us to improve by creating tickets for any documentation errors, suggestions or feature requests in our https://jira.project-hop.org[JIRA system].
-
diff --git a/hop-user-manual/modules/ROOT/pages/getting-started/hop-concepts.adoc b/hop-user-manual/modules/ROOT/pages/getting-started/hop-concepts.adoc
new file mode 100644
index 0000000..a98feee
--- /dev/null
+++ b/hop-user-manual/modules/ROOT/pages/getting-started/hop-concepts.adoc
@@ -0,0 +1,22 @@
+[[HopConcepts]]
+:imagesdir: ../../assets/images
+:page-pagination:
+
+= Hop Concepts
+
+== TL;DR
+
+Before we dive deeper, let's take a minute to familiarize ourselves with the Hop lingo.
+
+**Metadata** is by far the most important concept in all of Hop. Every item we'll cover below is defined as metadata. All interactions between Hop and other components in your data architecture are done through metadata. _Metadata is at the core of **everything** in Hop_.
+
+
+* **Pipelines** are a collections of **transforms**, connected by **hops**. All transforms in a pipeline run in parallel.
+
+* **Workflows** are a collection of **actions**, connected by **hops**. All actions in a workflow run sequentially by default.
+
+* **Projects** are logical collections of hop code and configuration. **Environments** contain the environment-specific (e.g. dev, uat, prd) metadata.
+
+include::../snippets/hop-concepts/item-types.adoc[]
+
+include::../snippets/hop-concepts/hop-projects-environments.adoc[]
\ No newline at end of file
diff --git a/hop-user-manual/modules/ROOT/pages/getting-started/hop-download-install.adoc b/hop-user-manual/modules/ROOT/pages/getting-started/hop-download-install.adoc
new file mode 100644
index 0000000..1064979
--- /dev/null
+++ b/hop-user-manual/modules/ROOT/pages/getting-started/hop-download-install.adoc
@@ -0,0 +1,27 @@
+[[DownloadInstall]]
+:imagesdir: ../../assets/images
+:page-pagination:
+
+= Download and Install Hop
+
+Hop is designed to be as easy and accessible to use as possible.
+
+Getting and starting Hop couldn't be easier:
+
+== Download
+
+Download Hop from the http://hop.apache.org/download/[downloads page], where you can choose between a Hop release or a nightly build (Current Development Builds).
+
+TIP: Development builds go through rigorous testing before a build is considered successful. Even though they are considered stable, you shouldn't run the latest nightly build in production without proper testing.
+
+== Prerequisites
+
+Hop is self contained, all you need is a Java runtime. Hop has been developed and tested with Java 8, but you shouldn't have any issues running Hop with Java 11. Check the https://java.com/en/download/help/download_options.html[Java docs] to download and install a Java runtime for your operating system.
+
+== Install
+
+Unzip Hop to a folder of your choice. From that folder, you'll be able to run the different Hop <<../hop-tools.adoc, tools>> through their corresponding scripts.
+
+Now that you have Hop installed, let's have a look at all of the Hop tools you have at your disposal.
+
+
diff --git a/hop-user-manual/modules/ROOT/pages/getting-started/hop-gui-pipelines.adoc b/hop-user-manual/modules/ROOT/pages/getting-started/hop-gui-pipelines.adoc
new file mode 100644
index 0000000..3536a98
--- /dev/null
+++ b/hop-user-manual/modules/ROOT/pages/getting-started/hop-gui-pipelines.adoc
@@ -0,0 +1,103 @@
+[[HopGuiPipelines]]
+:imagesdir: ../../assets/images
+:page-pagination:
+
+= Pipelines
+
+In xref:getting-started/hop-concepts.adoc[Concepts], we walked through pipelines, transforms and hops. Let’s remember:
+
+* A pipeline consists of a chain of transforms that read, process or write data. Transforms are connected through hops. Hops have a direction but can't create loops, which effectively makes Pipelines DAGs (Directed Acyclic Graphs).
+* A transform is each basic operation in your pipeline. Each transform performs an operation on the data: reads from a source, operates on data in the pipeline or writes to to a target.
+* A hop in a pipeline passes data between transforms.
+
+== Create a Pipeline
+
+There are two ways to create a pipeline.
+
+* click on the **New** option on the Horizontal toolbar and select the Pipeline option.
+
+image:getting-started/gs-hop-gui-create-pipeline-1.png[]
+
+* File -> New -> Pipeline
+
+image:getting-started/gs-hop-gui-create-pipeline-2.png[] +
+image:getting-started/gs-hop-gui-create-pipeline-3.png[]
+
+Your new pipeline is created. You’ll see the dialog below.
+
+image:getting-started/gs-hop-gui-create-pipeline-4.png[width=65%]
+
+== Add and connect Transforms
+
+=== Add Transforms
+
+Now you are ready to add the first transform. Click anywhere in the pipeline canvas, the area where you’ll see the image below.
+
+image:getting-started/gs-hop-gui-create-pipeline-5.png[]
+
+After clicking you will see the context dialog. This is the dialog you'll use every time you need to select transforms to add to your pipeline.
+
+image:getting-started/gs-hop-gui-create-pipeline-6.png[]
+
+Use the search box in this dialog to find the transforms you need. Click or use the arrow keys and hit enter to add a transform to your pipeline.
+
+For now, add a https://hop.apache.org/manual/latest/pipeline/transforms/rowgenerator.html[Generate Rows] and a http://localhost:1313/manual/latest/pipeline/transforms/addsequence.html[Add Sequence] transform to your pipeline.
+
+image:getting-started/gs-hop-gui-create-pipeline-add-two-transforms.png[]
+
+TIP: check the xref:pipeline/transforms.adoc[full list of transforms]. There are close to 130 transforms available in Hop 0.70, but you'll soon get to know the most commonly used ones.
+
+=== Create a Hop
+
+There are a number of ways to create a hop:
+
+* **shift-drag**: while holding down the shift key on your keyboard. Click on a transform, while holding down your primary mouse button, drag to the second transform. Release the primary mouse button and the shift key.
+* **scroll-drag**: scroll-click on a transform , while holding down your mouse’s scroll button, drag to the second transform. Release the scroll button.
+* click on a transform in your pipeline to open the context dialog (the dialog you opened in the '**click anywhere**' step). Click the 'Create hop' image:getting-started/icons/HOP.svg[Create hop, 25px, align="bottom"] button and select the transform you want to create the hop to.
+
+image:getting-started/gs-hop-gui-create-pipeline-create-hop.png[]
+
+
+== Run your pipeline
+
+Running a pipeline to see how it performs can be done in one of the following tasks:
+
+* Using the Run icon.
+
+image:getting-started/gs-hop-gui-run-pipeline-1.png[]
+
+* Select Run and click on Start Execution from the toolbar.
+
+image:getting-started/gs-hop-gui-run-pipeline-2.png[]
+
+* Press F8
+
+You will see the Run Options dialog.
+
+image:getting-started/gs-hop-gui-run-pipeline-3.png[] +
+
+image:getting-started/gs-hop-gui-run-pipeline-4.png[]
+
+TIP: a 'local' runtime configuration is created when you first start Hop Gui. Check the available xref:pipeline/pipeline-run-configurations/pipeline-run-configurations.adoc[runtime configurations] for other engines to run your pipelines on.
+
+Make sure your configuration is selected and hit Launch.
+
+You'll see green check marks in the upper right corner of the transforms when a pipeline ran successfully.
+
+image:getting-started/gs-hop-gui-run-pipeline-5.png[]
+
+After each run, the execution results are displayed in the panel on the bottom of your window. The Execution Results contains two tabs:
+
+* transform metrics
+* logging
+
+The Transform Metrics tab displays metrics per transform.
+
+image:getting-started/gs-hop-gui-run-pipeline-6.png[]
+
+The logging tab displays the log of the pipeline according to the log level chosen on execution.
+
+image:getting-started/gs-hop-gui-run-pipeline-7.png[]
+
+TIP: for more detailed information, check out the xref:pipeline/run-preview-debug-pipeline.adoc[Run, Preview and Debug a Pipeline] page.
+
diff --git a/hop-user-manual/modules/ROOT/pages/getting-started/hop-gui-workflows.adoc b/hop-user-manual/modules/ROOT/pages/getting-started/hop-gui-workflows.adoc
new file mode 100644
index 0000000..68c227e
--- /dev/null
+++ b/hop-user-manual/modules/ROOT/pages/getting-started/hop-gui-workflows.adoc
@@ -0,0 +1,72 @@
+[[HopGuiWorkflows]]
+:imagesdir: ../../assets/images
+:page-pagination:
+
+= Workflows
+
+In xref:getting-started/hop-concepts.adoc[Concepts], we walked through workflows, actions and hops. Let’s remember:
+
+* A _workflow_ is by default a sequential process that has a starting point and one or more endpoints.
+* An _action_ is a step that executes pipelines already implemented or any other element that allows orchestrating the execution of the data integration processes.
+* A _hop_ in a _workflow_ can conditionally connect _actions_ and determine which _action_ the _workflow_ needs to execute next.
+
+== Create a Workflow
+
+There are two ways to create a workflow.
+
+* Click on the New option on the Horizontal toolbar and select the Workflow option.
+
+image:getting-started/gs-hop-gui-create-workflow-1.png[]
+
+* File -> New -> Workflow
+
+image:getting-started/gs-hop-gui-create-workflow-2.png[]
+
+image:getting-started/gs-hop-gui-create-workflow-3.png[]
+
+Your new workflow is created, and you’ll see the dialog below.
+
+image:getting-started/gs-hop-gui-create-workflow-4.png[]
+
+NOTE: Note that when you create a workflow, Apache Hop automatically adds http://localhost:1313/manual/latest/workflow/actions/start.html[Start^] action by default.
+
+== Add and connect actions
+
+=== Add Actions
+
+Now you are ready to add the first action. Click anywhere in the workflow canvas, the area where you’ll see the image below.
+
+image:getting-started/gs-hop-gui-create-workflow-5.png[]
+
+After clicking you will see a dialog:
+
+image:getting-started/gs-hop-gui-create-workflow-6.png[]
+
+Just like you did with pipelines, use the search box in this dialog to find the actions you need. Click or use the arrow keys and hit enter to add an action to your workflow.
+
+For now, add a xref:workflow/actions/pipeline.adoc[Pipeline] action to your workflow.
+
+TIP: check the xref:workflow/actions.adoc[full list of actions]. There are over 50 actions available in Hop 0.70, but you'll soon get to know the most commonly used ones.
+
+
+=== Create a hop
+
+Creating a hop is identical to creating a hop in a pipeline:
+
+* **shift-drag**: while holding down the shift key on your keyboard. Click on a transform, while holding down your primary mouse button, drag to the second transform. Release the primary mouse button and the shift key.
+* **scroll-drag**: scroll-click on a transform , while holding down your mouse’s scroll button, drag to the second transform. Release the scroll button.
+* click on a transform in your pipeline to open the '**click anywhere**' dialog. Click the 'Create hop' image:getting-started/icons/HOP.svg[Create hop, 25px, align="bottom"] button and select the transform you want to create the hop to.
+
+image:getting-started/gs-hop-gui-create-workflow-add-pipeline-action.png[]
+
+Save your workflow:
+
+image:getting-started/gs-hop-gui-create-workflow-save.png[]
+
+At first, we have the Workflow run configuration session. A Workflow Run Configuration is a metadata object in Apache Hop and defines where the workflow is executed.
+
+Select the 'local' workflow runtime configuration that is available by default in your Hop installation and click 'Launch'.
+
+image:getting-started/gs-hop-gui-create-workflow-run.png[]
+
+You’ll now have an execution results pane very similar to the pipeline execution results.
\ No newline at end of file
diff --git a/hop-user-manual/modules/ROOT/pages/getting-started/hop-gui.adoc b/hop-user-manual/modules/ROOT/pages/getting-started/hop-gui.adoc
new file mode 100644
index 0000000..606cda1
--- /dev/null
+++ b/hop-user-manual/modules/ROOT/pages/getting-started/hop-gui.adoc
@@ -0,0 +1,43 @@
+[[HopGui]]
+:imagesdir: ../../assets/images/
+:page-pagination:
+
+= Hop Gui
+
+The Apache Hop GUI is your local development environment to build, run, preview and debug workflows and pipelines.
+
+== Start the Apache Hop GUI
+
+As we've seen in xref:getting-started/hop-tools.adoc[Hop Tools], starting Hop-Gui is easy:
+
+On Linux or Mac:
+
+[source,bash]
+./hop-gui.sh
+
+On Windows:
+
+[source,shell script]
+hop-gui.bat
+
+== Walking through the Hop GUI
+
+After starting the Apache Hop GUI, you’ll be presented with the window below.
+
+image:getting-started/gs-hop-gui-overview-1.png[Hop Gui Overview]
+
+{nbsp} +
+
+Let's divide the view into three parts:
+
+image:getting-started/gs-hop-gui-overview-2.png[Hop Gui Overview]
+
+
+* the **menu bar** includes options mainly for managing pipelines and workflows and the Apache Hop GUI configuration.
+* the **main toolbar** includes the New option to create files (pipelines and workflows) and metadata, and the options to manage projects and environments.
+* the **perspectives toolbar** includes switcher icons between the various perspectives.
+
+Let's see how we can use Hop Gui to do what Hop is all about: create pipelines and workflows!
+
+INFO: check the xref:../hop-gui/index.adoc[Hop Gui] section of the Hop documentation for a more detailed tour of the Hop Gui.
+
diff --git a/hop-user-manual/modules/ROOT/pages/getting-started/hop-next-steps.adoc b/hop-user-manual/modules/ROOT/pages/getting-started/hop-next-steps.adoc
new file mode 100644
index 0000000..eb58f8a
--- /dev/null
+++ b/hop-user-manual/modules/ROOT/pages/getting-started/hop-next-steps.adoc
@@ -0,0 +1,16 @@
+[[NetSteps]]
+:imagesdir: ../../assets/images
+:page-pagination:
+:page-pagination-no-next:
+
+= Next Steps
+
+You now know what Hop is and how to create your first workflows and pipelines.
+
+There's a lot more to discover in Hop. Here are a couple of topics you may want to look into:
+
+* xref:pipeline/pipelines.adoc[Pipelines] takes closer look at the various aspects of creating and running pipelines, and contains the entire list of transforms that are at your disposal
+* xref:workflow/workflows.adoc[Workflows] takes a closer look at the various aspects of create and running workflows, and contains the entire list of actions that are at your disposal
+* xref:projects/projects.adoc[Projects] explains how to work with projects and environments
+* xref:vfs.adoc[VFS] explains how you can access resources in the 3 main cloud platforms: AWS, Azure and GCP.
+* xref:logging/logging-basics.adoc[Logging] explains how to configure Hop for your desired log level and target platform
diff --git a/hop-user-manual/modules/ROOT/pages/getting-started/hop-tools.adoc b/hop-user-manual/modules/ROOT/pages/getting-started/hop-tools.adoc
new file mode 100644
index 0000000..e202ced
--- /dev/null
+++ b/hop-user-manual/modules/ROOT/pages/getting-started/hop-tools.adoc
@@ -0,0 +1,95 @@
+[[HopTools]]
+:imagesdir: ../../assets/images
+:page-pagination:
+
+= Hop Tools
+
+Hop contains a number of tools that are optimized for the various tasks Hop developers and administrators need to perform.
+
+== Hop GUI
+
+include::../snippets/hop-tools/hop-gui.adoc[]
+
+TIP: Hop Gui is designed to be platform independent. Hop Web is a version of Hop Gui that works on browsers and mobile devices, and will be available in the very near future.
+
+Windows
+[source,bash]
+hop-gui.bat
+
+MacOS, Linux
+[source,bash]
+ ./hop-gui.sh
+
+
+== Hop Conf
+
+include::../snippets/hop-tools/hop-conf.adoc[]
+
+Windows
+[source,bash]
+hop-conf.bat
+
+MacOS, Linux
+[source,bash]
+ ./hop-conf.sh
+
+== Hop Encrypt
+
+include::../snippets/hop-tools/hop-encrypt.adoc[]
+
+Windows
+[source,bash]
+hop-encrypt.bat
+
+MacOS, Linux
+[source,bash]
+ ./hop-encrypt.sh
+
+== Hop Run
+
+include::../snippets/hop-tools/hop-run.adoc[]
+
+Windows
+
+[source,bash]
+hop-run.bat
+
+MacOS, Linux
+[source,bash]
+ ./hop-run.sh
+
+xref::../hop-run/index.adoc[Read more]
+
+== Hop Search
+
+include::../snippets/hop-tools/hop-search.adoc[]
+
+== Hop Server
+
+include::../snippets/hop-tools/hop-server.adoc[]
+
+Windows
+[source,bash]
+hop-server.bat
+
+MacOS, Linux
+[source,bash]
+ ./hop-server.sh
+
+xref::../hop-server/index.adoc[Read more]
+
+== Hop Translator
+
+include::../snippets/hop-tools/hop-translator.adoc[]
+
+TIP: check the https://hop.apache.org/community/contribution-guides/translation-contribution-guide/[Translation Contribution Guide] if you want to find out more about translating Hop.
+
+Windows
+[source,bash]
+hop-translator.bat
+
+MacOS, Linux
+[source,bash]
+ ./hop-translator.sh
+
+https://hop.apache.org/community/contribution-guides/translation-contribution-guide/[Read more]
\ No newline at end of file
diff --git a/hop-user-manual/modules/ROOT/pages/getting-started/hop-what-is-hop.adoc b/hop-user-manual/modules/ROOT/pages/getting-started/hop-what-is-hop.adoc
new file mode 100644
index 0000000..cfa6245
--- /dev/null
+++ b/hop-user-manual/modules/ROOT/pages/getting-started/hop-what-is-hop.adoc
@@ -0,0 +1,33 @@
+[[WhatIsHop]]
+:imagesdir: ../../assets/images
+:page-pagination:
+
+= What is Apache Hop?
+
+== Visual Design and Metadata
+
+Apache Hop, short for **H**op **O**rchestration **P**latform, is a data orchestration and data engineering platform that aims to facillitate all aspects of data and metadata orchestration. Hop wants to let you focus on the problem you're trying to solve without technology getting in the way. Simple tasks should be easy, complex tasks need to be possible.
+
+Hop allows data professionals to work **visually**, using **metadata** to describe how data should be processed. Visual design enables data developers to focus on *what* they want to do instead of *how* that task needs to be done. This focus on the task at hand lets Hop developers be more productive than they would be when writing code.
+
+== Architecture
+
+Hop was designed to be as flexible as possible: at the core is the small but powerful Hop engine. All functionality is added through plugins. The default Hop installation comes with over 250 plugins. You can removed or add third-party plugins according to your needs to tailor Hop to be exactly what you need. Hop is designed to work in any scenario, from IoT to huge volumes of data, on-prem, in the cloud, on a bare OS or in containers and kubernetes.
+
+== Flexible Runtimes
+
+Hop developers create **workflows** and **pipelines** (more on that later) in a visual development environment called Hop Gui. These workflows and pipelines can be executed on a variety of engines: workflows and pipelines can run on the native Hop engine, both locally and remotely. Pipelines can also run on Apache Spark, Apache Flink and Google Dataflow through the Apache Beam runtime configurations. +
+
+In workflows and pipelines, hundreds of operations can be applied on the data: read from and write to a variety of source and target platforms, but also combine, enrich, clean and in many other ways manipulate data.
+Depending on the engine and selected functionality, your data can be processed in batch, streaming or in a batch/streaming hybrid.
+
+== Use Cases
+
+A number of common use cases for Hop are:
+
+* Loading large data sets into databases taking advantage of the cloud, clustered, and massively parallel processing environments.
+* Data warehouse population with built-in support for Slowly Changing Dimensions (SCD), Change Data Capture (CDC), and surrogate key creation.
+* Integrate between diverse data architectures, combining relational databases, files, NoSQL databases like Neo4j, MongoDB, Cassandra etc
+* Data migration between different databases and applications.
+* Data profiling and data cleansing.
+
diff --git a/hop-user-manual/modules/ROOT/pages/getting-started/index.adoc b/hop-user-manual/modules/ROOT/pages/getting-started/index.adoc
new file mode 100644
index 0000000..5ee7e41
--- /dev/null
+++ b/hop-user-manual/modules/ROOT/pages/getting-started/index.adoc
@@ -0,0 +1,22 @@
+[[GettingStarted]]
+:imagesdir: ../../assets/images
+:page-pagination:
+:page-pagination-no-back:
+
+= Getting Started
+
+This guide walks you through the Hop basics.
+
+We'll focus on the core knowledge you need to move around in Hop, without going in detail. At the end of this guide, there will be links to dive deeper into various Hop topics.
+
+This is what we'll cover:
+
+* xref:getting-started/hop-what-is-hop.adoc[What is Hop?]
+* xref:getting-started/hop-concepts.adoc[Concepts]
+* xref:getting-started/hop-download-install.adoc[Download & Install]
+* xref:getting-started/hop-tools.adoc[Tools]
+* xref:getting-started/hop-gui.adoc[Hop Gui overview]
+* xref:getting-started/hop-gui-pipelines.adoc[Pipelines]
+* xref:getting-started/hop-gui-workflows.adoc[Workflows]
+* xref:getting-started/hop-next-steps.adoc[Next Steps]
+
diff --git a/hop-user-manual/modules/ROOT/pages/snippets/hop-concepts/action.adoc b/hop-user-manual/modules/ROOT/pages/snippets/hop-concepts/action.adoc
new file mode 100644
index 0000000..f88e117
--- /dev/null
+++ b/hop-user-manual/modules/ROOT/pages/snippets/hop-concepts/action.adoc
@@ -0,0 +1 @@
+An Action is one operation performed in a Workflow. Actions are executed sequentially by default, with parallel execution as a configuration option. An Action returns a true or false exit code, which can be used (or ignored) in the Workflow’s execution.
\ No newline at end of file
diff --git a/hop-user-manual/modules/ROOT/pages/snippets/hop-concepts/environment.adoc b/hop-user-manual/modules/ROOT/pages/snippets/hop-concepts/environment.adoc
new file mode 100644
index 0000000..6e4f8ee
--- /dev/null
+++ b/hop-user-manual/modules/ROOT/pages/snippets/hop-concepts/environment.adoc
@@ -0,0 +1,2 @@
+A Hop Environment are instances of projects that hold the actual runtime configurations and other metadata objects for a project. +
+Example: the 'dev' environment for the 'Sales' project specifies to read from host '10.0.0.1' for the 'customers' database connection
diff --git a/hop-user-manual/modules/ROOT/pages/snippets/hop-concepts/hop-projects-environments.adoc b/hop-user-manual/modules/ROOT/pages/snippets/hop-concepts/hop-projects-environments.adoc
new file mode 100644
index 0000000..11418aa
--- /dev/null
+++ b/hop-user-manual/modules/ROOT/pages/snippets/hop-concepts/hop-projects-environments.adoc
@@ -0,0 +1,9 @@
+== Projects and Environments
+
+Project::
+include::project.adoc[]
+
+Environment::
+include::environment.adoc[]
+
+image::concepts/environments.png[Environment Examples]
diff --git a/hop-user-manual/modules/ROOT/pages/snippets/hop-concepts/hop.adoc b/hop-user-manual/modules/ROOT/pages/snippets/hop-concepts/hop.adoc
new file mode 100644
index 0000000..62fbff3
--- /dev/null
+++ b/hop-user-manual/modules/ROOT/pages/snippets/hop-concepts/hop.adoc
@@ -0,0 +1 @@
+A Hop links Actions in a Workflow or Transforms in a Pipeline. In Workflows, Hops operate based on the exit status of previous Actions, Hops in Pipelines pass data between Transforms.
\ No newline at end of file
diff --git a/hop-user-manual/modules/ROOT/pages/snippets/hop-concepts/item-types.adoc b/hop-user-manual/modules/ROOT/pages/snippets/hop-concepts/item-types.adoc
new file mode 100644
index 0000000..4f0413f
--- /dev/null
+++ b/hop-user-manual/modules/ROOT/pages/snippets/hop-concepts/item-types.adoc
@@ -0,0 +1,22 @@
+== Item types
+
+Action::
+include::action.adoc[]
+
+Hop::
+include::hop.adoc[]
+
+Pipeline::
+include::pipeline.adoc[]
+
+image::concepts/pipeline.png[Pipeline]
+
+Transform::
+include::transform.adoc[]
+
+Workflow::
+include::workflow.adoc[]
+
+image::concepts/workflow.png[Workflow]
+
+
diff --git a/hop-user-manual/modules/ROOT/pages/snippets/hop-concepts/lazy-loading.adoc b/hop-user-manual/modules/ROOT/pages/snippets/hop-concepts/lazy-loading.adoc
new file mode 100644
index 0000000..a1d063f
--- /dev/null
+++ b/hop-user-manual/modules/ROOT/pages/snippets/hop-concepts/lazy-loading.adoc
@@ -0,0 +1,3 @@
+If enabled, all data conversions (character decoding, data conversion, trimming, …) for the data being read will be postponed as long as possible, effectively reading the data as binary fields. Enabling lazy conversion can significantly decrease the CPU cost of reading data. +
+#When to avoid#: if the data conversion needs to be performed later in the stream anyway, postponing the conversion may slow things down instead of speeding up. +
+#When to use#: use cases where Lazy Conversion may speed things up when 1) data is read and written to another file without conversion, 2) data needs to be sorted and doesn’t fit in memory. In this case, serialization to disk is faster with lazy conversion because encoding and type conversions are postponed, or 3) bulk-loading to database without the need for data conversion. Bulk loading utilities typically read text directly and the generation of this text is faster (this does not appl [...]
\ No newline at end of file
diff --git a/hop-user-manual/modules/ROOT/pages/snippets/hop-concepts/metadata.adoc b/hop-user-manual/modules/ROOT/pages/snippets/hop-concepts/metadata.adoc
new file mode 100644
index 0000000..2e86f4b
--- /dev/null
+++ b/hop-user-manual/modules/ROOT/pages/snippets/hop-concepts/metadata.adoc
@@ -0,0 +1 @@
+Hop Metadata is the central storage repository for shared metadata like relational database connections, run configurations, servers, git repositories and so on. Metadata is persisted as json and is stored by default in a project's base folder.
diff --git a/hop-user-manual/modules/ROOT/pages/snippets/hop-concepts/pipeline.adoc b/hop-user-manual/modules/ROOT/pages/snippets/hop-concepts/pipeline.adoc
new file mode 100644
index 0000000..7d71ca1
--- /dev/null
+++ b/hop-user-manual/modules/ROOT/pages/snippets/hop-concepts/pipeline.adoc
@@ -0,0 +1 @@
+Pipelines are the actual data workers. Operations in a Pipeline read, modify, enrich, clean and write data. Orchestration of Pipelines is done through othere Pipelines and/or Workflows.
\ No newline at end of file
diff --git a/hop-user-manual/modules/ROOT/pages/snippets/hop-concepts/project.adoc b/hop-user-manual/modules/ROOT/pages/snippets/hop-concepts/project.adoc
new file mode 100644
index 0000000..7e49395
--- /dev/null
+++ b/hop-user-manual/modules/ROOT/pages/snippets/hop-concepts/project.adoc
@@ -0,0 +1,2 @@
+Hop Projects are a conceptual grouping of configurations, variables, metadata objects and workflows and pipelines. Projects can inherit metadata from parent projects. A project contains one or more environments where the actual configuration is defined. +
+Example: a 'Sales' project contains a 'customers' database connection and a number of workflows and pipelines. The runtime configurations, database connection properties etc are defined in the 'dev', 'uat' and 'prd' environments.
\ No newline at end of file
diff --git a/hop-user-manual/modules/ROOT/pages/snippets/hop-concepts/transform.adoc b/hop-user-manual/modules/ROOT/pages/snippets/hop-concepts/transform.adoc
new file mode 100644
index 0000000..5128597
--- /dev/null
+++ b/hop-user-manual/modules/ROOT/pages/snippets/hop-concepts/transform.adoc
@@ -0,0 +1 @@
+A Transform is a unit of work performed in a Pipeline. Typical Transform operations are reading data from files, databases, performing lookups or joins, enriching, cleaning data and more. All transforms in a Pipeline are executed in parallel. Transforms process data and move batches of processed data on Hops for processing by subsequent Actions.
\ No newline at end of file
diff --git a/hop-user-manual/modules/ROOT/pages/snippets/hop-concepts/workflow.adoc b/hop-user-manual/modules/ROOT/pages/snippets/hop-concepts/workflow.adoc
new file mode 100644
index 0000000..2fa0ef2
--- /dev/null
+++ b/hop-user-manual/modules/ROOT/pages/snippets/hop-concepts/workflow.adoc
@@ -0,0 +1 @@
+A Workflow is a sequence of operations that are performed sequentially by default (with optional parallel execution). Workflows usually do not operate on the data directly, but perform orchestration tasks. Typical tasks in a Workflow consist of retrieving and archiving data, sending emails, error handling etc. )
\ No newline at end of file
diff --git a/hop-user-manual/modules/ROOT/pages/snippets/hop-tools/hop-conf.adoc b/hop-user-manual/modules/ROOT/pages/snippets/hop-tools/hop-conf.adoc
new file mode 100644
index 0000000..79c4781
--- /dev/null
+++ b/hop-user-manual/modules/ROOT/pages/snippets/hop-tools/hop-conf.adoc
@@ -0,0 +1 @@
+Hop Conf is a command line tool to manage various aspects of your Hop configuration: projects, environments, cloud configuration and more
\ No newline at end of file
diff --git a/hop-user-manual/modules/ROOT/pages/snippets/hop-tools/hop-encrypt.adoc b/hop-user-manual/modules/ROOT/pages/snippets/hop-tools/hop-encrypt.adoc
new file mode 100644
index 0000000..233acdc
--- /dev/null
+++ b/hop-user-manual/modules/ROOT/pages/snippets/hop-tools/hop-encrypt.adoc
@@ -0,0 +1,3 @@
+Hop Encrypt is a command line tool that obfuscates or encrypts a plain text password for use in XML, password or metadata files.
+Make sure to also copy the password encryption prefix to indicate the obfuscated nature of the password.
+Hop will then be able to make the distinction between regular plain text passwords and obfuscated ones.
diff --git a/hop-user-manual/modules/ROOT/pages/snippets/hop-tools/hop-gui.adoc b/hop-user-manual/modules/ROOT/pages/snippets/hop-tools/hop-gui.adoc
new file mode 100644
index 0000000..ff980c3
--- /dev/null
+++ b/hop-user-manual/modules/ROOT/pages/snippets/hop-tools/hop-gui.adoc
@@ -0,0 +1 @@
+Hop Gui is the visual IDE where Hop data developers create, test, run and manage the life cycle for workflows and pipelines. In addition to functionality for development and life cycle management, Hop Gui contains tools and perspectives to manage projects and environments, to search and manage metadata, to manage and version control a large variety of files and to explore logging in a Neo4j graph.
diff --git a/hop-user-manual/modules/ROOT/pages/snippets/hop-tools/hop-run.adoc b/hop-user-manual/modules/ROOT/pages/snippets/hop-tools/hop-run.adoc
new file mode 100644
index 0000000..c7575c9
--- /dev/null
+++ b/hop-user-manual/modules/ROOT/pages/snippets/hop-tools/hop-run.adoc
@@ -0,0 +1 @@
+Hop Run is a command line tool to run workflows and pipelines, with options to (list or) specify projects, environments, properties and run configurations.
\ No newline at end of file
diff --git a/hop-user-manual/modules/ROOT/pages/snippets/hop-tools/hop-search.adoc b/hop-user-manual/modules/ROOT/pages/snippets/hop-tools/hop-search.adoc
new file mode 100644
index 0000000..4dca4c5
--- /dev/null
+++ b/hop-user-manual/modules/ROOT/pages/snippets/hop-tools/hop-search.adoc
@@ -0,0 +1 @@
+Hop Search is a command line tool to search all metadata available in a specific project or environment.
\ No newline at end of file
diff --git a/hop-user-manual/modules/ROOT/pages/snippets/hop-tools/hop-server.adoc b/hop-user-manual/modules/ROOT/pages/snippets/hop-tools/hop-server.adoc
new file mode 100644
index 0000000..9be8f5d
--- /dev/null
+++ b/hop-user-manual/modules/ROOT/pages/snippets/hop-tools/hop-server.adoc
@@ -0,0 +1 @@
+Hop Server is a web service interface to manage and run workflows and pipelines.
\ No newline at end of file
diff --git a/hop-user-manual/modules/ROOT/pages/snippets/hop-tools/hop-tools.adoc b/hop-user-manual/modules/ROOT/pages/snippets/hop-tools/hop-tools.adoc
new file mode 100644
index 0000000..a03de8f
--- /dev/null
+++ b/hop-user-manual/modules/ROOT/pages/snippets/hop-tools/hop-tools.adoc
@@ -0,0 +1,22 @@
+== Tools
+
+Hop Conf::
+include::hop-conf.adoc[]
+
+Hop Encrypt::
+include::hop-encrypt.adoc[]
+
+Hop Gui::
+include::hop-gui.adoc[]
+
+Hop Run::
+include::hop-run.adoc[]
+
+Hop Search::
+include::hop-search.adoc[]
+
+Hop Server::
+include::hop-server.adoc[]
+
+Hop Translate::
+include::hop-translator.adoc[]
diff --git a/hop-user-manual/modules/ROOT/pages/snippets/hop-tools/hop-translator.adoc b/hop-user-manual/modules/ROOT/pages/snippets/hop-tools/hop-translator.adoc
new file mode 100644
index 0000000..8db2065
--- /dev/null
+++ b/hop-user-manual/modules/ROOT/pages/snippets/hop-tools/hop-translator.adoc
@@ -0,0 +1 @@
+Hop Translator is a gui tool that allows non-technical users to translate Hop in their native language.
\ No newline at end of file