configuration page
diff --git a/docs/api-details/api.md b/docs/api-details/api.md
deleted file mode 100644
index c2dfec8..0000000
--- a/docs/api-details/api.md
+++ /dev/null
@@ -1,35 +0,0 @@
----
-id: api
-title: API
-sidebar_label: API
----
-
-Open-api specifications are provided for the core "vanilla" Milagro HTTP REST services and for both the shipped plugins: Bitcoin Address and Safeguard Secret
-
-* [Standard API](https://raw.githubusercontent.com/apache/incubator-milagro-dta/develop/open-api.yaml) Here it is in a [Swagger UI](/swagger/index.html)
-* [Bitcoin Plugin API](https://raw.githubusercontent.com/apache/incubator-milagro-dta/develop/pkg/bitcoinplugin/open-api.yaml)
-* [Safeguard Secret API](https://raw.githubusercontent.com/apache/incubator-milagro-dta/develop/pkg/safeguardsecret/open-api.yaml)
-
-## Testing The API
-
-(This assumes that your local DTA is running on port 5558 as described in the [quick start guide](/docs/dta-details/quickstart)
-
-Instructions for installing Swagger UI can be found [here](https://github.com/swagger-api/swagger-ui/blob/master/docs/usage/installation.md)
-
-For example...
-
-```
-docker pull swaggerapi/swagger-ui  
-
-docker run -p 80:8080 swaggerapi/swagger-ui
-
-```
-
-In your browser hit http://localhost:80
-
-Paste the URL of one of the API docs above into the text box at the top of the screen. 
-
-Have fun!
-
-
-
diff --git a/docs/api-details/authentication.md b/docs/api-details/authentication.md
deleted file mode 100644
index fdc71ed..0000000
--- a/docs/api-details/authentication.md
+++ /dev/null
@@ -1,25 +0,0 @@
----
-id: authentication
-title: Authentication
-sidebar_label: Authentication
----
-When you first install Milagro DTA the API endpoints are not authenticated by default. In otherwords any simple CURL command will ellicit the expected reposnse. Milagro DTA supports oAth bearer token authentication our of the box
-
-:::caution
-We strong recommend that you ***do not*** run Milagro DTA server without authentication
-:::
-
-To configure authentication all that is required is a standard oAuth 2.0 service. If you do not have an oAuth service currently running in your own infrastructure we recommend any of these fine service providers who will be able to authenticate your API users.
-* [AWS Cognito](https://aws.amazon.com/cognito/)
-* [Azure Active Directory](https://azure.microsoft.com/en-gb/services/active-directory/)
-* [AuthO](https://auth0.com/)
-
-## Configuration
-
-```
-config.yaml
-
-
-
-
-
diff --git a/docs/api-details/configuration.md b/docs/api-details/configuration.md
deleted file mode 100644
index 64322d8..0000000
--- a/docs/api-details/configuration.md
+++ /dev/null
@@ -1,21 +0,0 @@
----
-id: configuration
-title: Configuration
-sidebar_label: Configuration
----
-Milagro DTA can be passed options at start-up either via the congif.yaml file, by command line arguments or environment variables. Thesefull list of options are defined in milagro/service/flags/flags.go. But the minimum configuration is:
-```
-config.yaml
-
-listen_type: http
-listen_addr: :port
-kvstore: ***local*** NOTE: CHANGE THIS!
-cors-allow: http://localhost:port - if you are hitting the API from a browser
-
-
-cli
-
-./milagro-dta -listen-addr=http://localhost:port
-
-
-```
\ No newline at end of file
diff --git a/docs/dta-plugins/d-ta-plugins.md b/docs/dta-plugins/d-ta-plugins.md
deleted file mode 100644
index 97f1f9a..0000000
--- a/docs/dta-plugins/d-ta-plugins.md
+++ /dev/null
@@ -1,63 +0,0 @@
----
-id: plugins-overview
-title: D-TA Plugins Overview
-sidebar_label: Plugins Overview
----
-
-Out-of-the-box Milagro D-TA doesn't do much: a Principal gets a public key from a Master Fiduciary and at a later date can request the corresponding secret key. (Although it does this in a hard-to-hack, and fully auditable way). However this basic capability unlocks a huge range of potential uses cases. Some use cases relate to the Prinicpal i.e. what the keys can be used for, and some relate to the Master Fiduciary i.e. how the seret key is kept safe (a.k.a. custody). Open source "vanilla" Milagro is an attempt to engage a wider community to make the communication between these parties as robust as possible, the plugin framework enables developers to extend Milagro's core capability and apply it to solve real world problems.
-
-Out of the box Milagro comes with two plugins:
-1. **EncryptAThing** - allows the principal to use the public key to encrypt a string, then get the secret key back from the Master Fiduciary D-TA and decrypt it
-
-2. **BitCoin Address** - uses the public key to genarate a Bitcoin address and the constructs the corresponding secret key only when it is needed (this is a neat trick using eliptic curve magic).
-
-***A Note About Security***
-
-The point of these plugins is to show you how the framework works and encourage you to develop your own, they do not (out of the box) provide a secure way to store your secret keys. The key pair seed is stored only in the Master Fiduciary's onboard database - there are obviously better ways do this, contact a Milagro D-TA compatible Custodial Service Provider to find out how...
-
-## Approach
-The Milagro D-TA plugin framework has been designed with following assumptions:
-
-* **Compile-Time**
-
-    Milagro D-TA plugins are compiled into the Milagro D-TA - to include one you simply clone the plugin into to the pkg directory and pass a reference to the plugin as a build directive like this...
-    ```
-    go build -tags "plugin encryptAThing" -o target/service github.com/apache/incubator-milagro-dta/cmd/service
-    ```
-    We considered run-time plugins using shared objects via the [Go Plugin Package](https://golang.org/pkg/plugin/) however this presented significant security challenges. We would very much like explore this idea further with the developer community.
-
-* **One-at-a-Time**
-
-   Each Milagro server can only run one plugin at a time. We considered how to allow multiple plugins to interoperate but this produces significant operational and security concerns. (We'd really appreciate your thoughts about that). Of course if you run a pair of servers as Principal and Master Fiduciary then they can each run different plugins
-* **No New Endpoints**
-
-    You can only write plugins to support the [Standard Endpoints](http://localhost:3000/swagger/). This probably seems quite restrictive but we think it is important that Milagro D-TA operates within a defined scope and in a predictable way. Milagro D-TA is about the distributed management of key pairs, we are concerned that if the plugin framework allowed developers to add endpoints such as *GET fastfood/burger?orderby=mostTasty* then Milagro would just become a cool implementation of [Go kit](https://gokit.io/) and it would become impossible for users and integrators to predict what it will do. **However...**
-    * **Let's Talk** As a community we're excited to add new features to Milagro D-TA. Propose your new endpoint as a feature (or even submit a PR) and we'll collectively consider adding it
-    * **Let's Fork** Go ahead and fork the Milagro D-TA. (But remember that Milagro D-TA is basically a communication protcol so keep it compatible with other Milagro users)
-
-* **Extensions** 
-
-   Although we restrict what endpoints Milagro provides we give you a highly flexible way to define what data each endpoint accepts and returns via the **extensions** JSON prop. For example the encryptAThing plugin extends the POST /order endpoint like this:
-   ```
-    POST /order
-    
-    Request    
-    {
-        "beneficiaryIDDocumentCID" : "IPFSAddress",
-        "extensions" : {
-            "plainText":"encryptme"
-            }
-    }
-
-    Response
-    {
-    	"orderPart1CID" : "IPFSAddress",
-	    "orderPart2CID" : "IPFSAddress",
-	    "commitment"    : "IPFSAddress",
-	    "createdAt"     : 1563982017,
-        "extensions" : {
-            "cypherText":"iAmEncrypted"
-        }	    
-    }
-   ```
-
diff --git a/docs/dta-plugins/plugin-dev-guide.md b/docs/dta-plugins/plugin-dev-guide.md
deleted file mode 100644
index 83a6f69..0000000
--- a/docs/dta-plugins/plugin-dev-guide.md
+++ /dev/null
@@ -1,65 +0,0 @@
----
-id: plugin-dev-guide
-title: D-TA Plugins Developers Guide
-sidebar_label: Developers Guide
----
-We have provided a template plugin that provides the same functionality as out-of-the-box milagro.
-
-## Developer Notes
-
-You need to install protobufs
-
-If you change the portobufs definition run 
-
-$ protoc -I=. --go_out=. ./docs.proto
-
-To add a new endpoint to the goKit Microservices framework
-
-1. First define the contract in milagro/pkg/milagroservice/proto.go
-
-Add structs for http transport
-Add responses to milagro/swagger/swagger.config,yaml
-
-2. Add and endpoint definition
-
-milagro/pkg/milagroendpoints/endpoints.go
-
-3. Create a handler factory
-
-**Thise instructions still aren't perfect**
-
-1. Clone the repo and make sure that it works by following the [Quick Start](/docs/dta-details/quickstart) instructions
-2. Copy the plugin template
-```
-cp -r pkg/plugintemplate pkg/encryptastring
-```
-3. Rename the package and service 
-on a mac you could do this...
-```
-sed -i "" "s/template/encryptastring/g" pkg/encryptastring/service.go
-```
-4. Now create a plugin regsitration file
-```
-sed -i "" "s/plugintemplate/encryptastring/g" plugins/encryptastring.go
-sed -i "" "s/pluginTemplate/encryptAString/g" plugins/encryptastring.go
-```
-5.  Update the Config File
-```
-nano ~/.milagro/config.yaml
-
-update....
-
-plugins:
-  service: encryptastring
-
-```
-6. See your plugin in action!
-```
-go build -o target/service github.com/apache/incubator-milagro-dta/cmd/service
-target/service
-```
-Point your browser at:
-http://localhost:5555/status
-
-you should see
-
diff --git a/website/sidebars.json b/website/sidebars.json
index 04099f2..1691bdc 100644
--- a/website/sidebars.json
+++ b/website/sidebars.json
@@ -15,15 +15,10 @@
       ],
     "Distributed Trust Authority": 
       [
-      "d-ta-overview",
-      "dta-details/quickstart",
-          "api-details/api",
-      {
-        "type":"subcategory",
-        "label":"D-TA Details",
-        "ids":[ 
-                ]
-      }
+        "d-ta-overview",
+        "dta-details/quickstart",
+        "dta-details/api",
+        "dta-details/configuration"
     ],  
     "ZKP-MFA Clients/Servers": [
       "zkp-mfa-overview",