diff --git a/GNUmakefile b/GNUmakefile
new file mode 100644
index 0000000..1edcc99
--- /dev/null
+++ b/GNUmakefile
@@ -0,0 +1,2 @@
+index.html: README.adoc README-docinfo.html README-docinfo-header.html
+ asciidoc -b html5 -a data-uri -a icons --theme ladi -o index.html README.adoc
diff --git a/README-docinfo-header.html b/README-docinfo-header.html
new file mode 100644
index 0000000..e69de29
diff --git a/README-docinfo.html b/README-docinfo.html
new file mode 100644
index 0000000..b9c7dc7
--- /dev/null
+++ b/README-docinfo.html
@@ -0,0 +1,5 @@
+
+
+
+
+
diff --git a/README.adoc b/README.adoc
index 2eaa284..b50a7f1 100644
--- a/README.adoc
+++ b/README.adoc
@@ -3,3 +3,20 @@ ladici - The LADI Continuous Integration software
.WORK IN PROGRESS
[NOTE]
This is Work In Progress.
+
+Goals:
+
+ * Minimal dependencies
+ ** lua
+ ** luasocket
+ ** fengari (optional, for the client-side scripting frontend)
+ * IRC based LPC/RPC
+ * no database. Use lua files for configuration. Use filesystem symlinks & hardlinks where a simple filesystem tree is not enough.
+
+Concepts:
+
+ * ladici HQ - the central machine/node
+ * ladici factory - a machine/node (can be the HQ one) where lanes are hosted
+ * ladici lane - a chain or DAG of rules & commands to be executed by ladici factories
+
+In simplest case, ladici deployment consists of single machine/node running ladici. This central node, HQ. The process running HQ can also run a factory and is pre-configured so with one that runs lane to create tarballs from sources.