diff --git a/docs/api-details/configuration.md b/docs/api-details/configuration.md
new file mode 100644
index 0000000..6f7b9f6
--- /dev/null
+++ b/docs/api-details/configuration.md
@@ -0,0 +1,10 @@
+---
+id: configuration
+title: Configuration
+sidebar_label: Configuration
+---
+Config file
+
+Flags
+
+Env vars
\ No newline at end of file
diff --git a/docs/dta-details/usage.md b/docs/dta-details/usage.md
new file mode 100644
index 0000000..e0184f6
--- /dev/null
+++ b/docs/dta-details/usage.md
@@ -0,0 +1,22 @@
+---
+id: usage
+title: Using Milagro DTA
+sidebar_label: Using Milagro DTA
+---
+Milagro DTA is designed to be built into the workflow of any organisation that needs to entrust another organisation to store the secret part of a key pair securely. It provides a [simple REST api](/swagger/index.html) "out-of-the-box" that can easily be integrated with an existing back office system or attached to a front-end application (or called from CURL, Postman, Swagger etc. if you just want to see what it does). 
+
+The API has three parts to it:
+
+1. _Identity Endpoints_ - that support creation and retrieval of identity documents
+2. Secret Endpoints 
+    1. Creates orders for new secrets
+    2. Requets for existing secret keys to be revealed (redeemed)
+    3. Allows orders to be searched and listed
+3. Fulfilment RPC - these are the server-to-server calls that enable the Principal DTA to communicate with the Fiduciary
+
+## Bootstrapping An Identity
+
+In order to run a Milagro DTA Node it needs to be configured with an idenity. This is usually passed to the node via one of the [configuration options](api-details/configuration.md), however if you are running a server for the first time it will prompt you to create a new one.
+
+
+
diff --git a/website/static/img/dta/Envelope.png b/website/static/img/dta/Envelope.png
new file mode 100644
index 0000000..28f8ff4
--- /dev/null
+++ b/website/static/img/dta/Envelope.png
Binary files differ