diff --git a/README.md b/README.md
index 9141fb4..282050d 100644
--- a/README.md
+++ b/README.md
@@ -62,6 +62,8 @@ project.
Registry and Project resources are declaratively configured as separate files.
For examples, see the `examples` directory.
+For more details, feel free to review the content of the [Documentaion folder](doc/README.md).
+
## Usage
### Applying the configuration
diff --git a/doc/README.md b/doc/README.md
new file mode 100644
index 0000000..ab6097b
--- /dev/null
+++ b/doc/README.md
@@ -0,0 +1,37 @@
+# Registryman Documentation
+
+## Concepts
+Registryman (Registry Manager) allows configuration of container image registry
+projects, project members and project replication rules in a declarative way (by
+virtue of k8s custom resources / YAML files) on top of multiple types of container image registries.
+
+Registryman can manage configuration of multiple registries at once and supports building hierarchical
+registry solutions, consisting of:
+
+ - **Global Registry Hub**, which acts as a single source of truth for centralized image & vulnerability management,
+ - **Multiple Local Registries** potentially located in different regions to have the images in close location to users.
+
+The Registryman ensures automatic replication of images between the Global and Local registries based on
+the intent described using Registryman API.
+
+An example of such deployment is shown on the following picture:
+
+![global-registry-overview.svg](./img/global-registry-overview.svg "Overview")
+
+To summarize the concepts shown on the picture:
+
+- the setup consists of a single Global Registry Hub and multiple Local Registries,
+- configuration and policies for projects across the whole setup can be managed using Registryman,
+- Registryman ensures that projects, project members and project replication rules configuration is always synchronized across the setup,
+- the users of global projects can push the images into the Global Registry Hub,
+- images of the global projects will be automatically synchronized to all Local Registries,
+- image consumers can pull the image from any Local (or Global) registry, e.g. based on their physical location,
+- local project can exist within the Local Registries, they can be managed via Registryman, but are not replicated anywhere.
+
+## Implementation Details
+For more implementation details, you can review the following documents:
+
+- [Registries and Projects](projects.md)
+- [Data Model](datamodel.md)
+- [Reconciliation](reconciliation.md)
+- [Actions](actions.md)
diff --git a/doc/architecture.graphml b/doc/img/architecture.graphml
similarity index 100%
rename from doc/architecture.graphml
rename to doc/img/architecture.graphml
diff --git a/doc/architecture.svg b/doc/img/architecture.svg
similarity index 100%
rename from doc/architecture.svg
rename to doc/img/architecture.svg
diff --git a/doc/img/global-registry-overview.svg b/doc/img/global-registry-overview.svg
new file mode 100644
index 0000000..d423fcf
--- /dev/null
+++ b/doc/img/global-registry-overview.svg
@@ -0,0 +1,3 @@
+
+
+
\ No newline at end of file
diff --git a/doc/img/global-registry-overview.xml b/doc/img/global-registry-overview.xml
new file mode 100644
index 0000000..77939e5
--- /dev/null
+++ b/doc/img/global-registry-overview.xml
@@ -0,0 +1,162 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
diff --git a/doc/reconciliation.md b/doc/reconciliation.md
index cf4bfaa..f928767 100644
--- a/doc/reconciliation.md
+++ b/doc/reconciliation.md
@@ -8,7 +8,7 @@ and then compares it to the expected state.
The architecture or registryman is shown below.
-![architecture.svg](./architecture.svg "Architecture")
+![architecture.svg](./img/architecture.svg "Architecture")
### The main packages