Update the understand section

content/en/docs/Get-Started/Understand the @platform/dess.md → content/en/docs/Get-Started/Understand the @platform/data_architecture.md

@@ -1,10 +1,13 @@
 ---
 title: 'Data Architecture'
-SEOtitle: 'dess : distributed edge secondary server  - @platform(at_platform or AtPlatform)'
+SEOtitle: 'No Backend Data Architecture Infrastructure Free'
 linkTitle: 'Data Architecture'
 weight: 2
 content: Run your @platform secondary server on your own infrastructure
 description: Run your @platform secondary server on your own infrastructure
+toc_hide: true
+hide_summary: true
+draft: true
 ---
 
 ## 1. What is dess?

content/en/docs/Get-Started/Understand the @platform/free-atsigns.md

@@ -1,17 +1,20 @@
 ---
-title: "Namespaces"
+title: "To be deleted"
 SEOtitle: "Namespaces on the @platform (at_platform or AtPlatform) with free @signs (AtSign or at_sign)"
-linkTitle: "Namespace"
+linkTitle: "To be deleted"
 Description: "An overview to namespaces and their importance"
 content: "Easily setup your own @platform secondary server for free!"
 
 weight: 1
 date: 2022-01-17
+toc_hide: true
+hide_summary: true
+draft: true
 ---
 
 ## What are Namespaces?
 
-If you've spent enough time on our developer site, you are more than likely to have come across the word 'namespace'. But what are these, and why are they so important? We have published an article that answers both of these questions!
+Namespace is a common term that may occur when reading about the @platform. 
 
 Feel free to read all about namespaces [here](https://atsigncompany.medium.com/the-hidden-beauty-of-protocol-namespaces-6f5fab7f7a09).
 

content/en/docs/Get-Started/Understand the @platform/namespaces.md

@@ -0,0 +1,90 @@
+---
+title: "Namespaces"
+SEOtitle: "Namespaces on the @platform (at_platform or AtPlatform) with free @signs (AtSign or at_sign)"
+linkTitle: "Namespace"
+Description: "An overview to namespaces and their importance"
+content: "Easily setup your own @platform secondary server for free!"
+
+weight: 1
+date: 2022-01-17
+---
+
+Namespace is a common term that may occur when reading about the @platform. Luckily for you, we briefly explain what a namespace is here! 
+
+As our CTO, Colin Constable, delicately described it, " A namespace is a place to put a set of strings or characters together." So how exactly is this relevant to our end-to-end encryption protocol?
+
+Most people are familiar with DNS (Domain Name System): for example, if you type “cnn.com”, “fox.com”, or “bbc.com”, you get news sites. But you can’t just type in “news” and expect the Internet to tell you which particular flavor of news you want. 
+
+We need to create namespaces so that humans can remember the name and computers can translate it to Internet protocol. Once there is a namespace like “bbc.com,” you can reliably know that somebody owns that particular space, and it needs to be managed so that there are no clashes. 
+
+For instance, you don’t want to type “bbc.com” and get sent to Amazon’s home page. That’s why they have to be unique.
+
+
+Feel free to read more on namespaces [here](https://atsigncompany.medium.com/the-hidden-beauty-of-protocol-namespaces-6f5fab7f7a09).
+
+<!-- ## Getting @signs and keys.
+
+Your first step is to get a couple of @signs, it is best to get at least two, so you can experiment with sharing end-to-end
+encrypted data across the @platform.
+
+### There are two methods to get @signs.
+
+#### The first
+
+Go to [atsign.com](https://atsign.com) and clicking [Get an @sign](https://atsign.com/get-an-sign/). If you go
+this route then you have more influence on your free @sign or pay for one of your choosing. Once you have your @signs,
+do not forget to activate them.
+
+![activate @sign](/docs/Get-Started/get-an-atsign/images/activate-ui.png)
+
+Activating creates a microservice (we call the secondary server) and once
+that is spun up on The @ Company infrastructure you will see a QR-Code to scan with an @ enabled application.
+
+![activated @sign](/docs/Get-Started/get-an-atsign/images/activated.png)
+
+The pairing consists of your device creating cryptographic
+keys and sharing the public keys to the secondary server, you will be asked to store your private keys.
+Storing your keys is vitally important as only you have the keys.
+
+#### The second
+
+The experience of getting a @sign via the website is great for developers as you have advanced options available, to reset
+@signs and to point your @sign to your own infrastructure. For getting people onboarded quickly, a better experience would
+be to get a free @sign within the app itself, this is option 2.
+
+![generate @sign](/docs/Get-Started/get-an-atsign/images/generate-free-@sign.png)
+
+The [onboarding widget](https://pub.dev/packages/at_onboarding_flutter) together with an API key provides a button
+marked "Generate Free @sign".
+
+![generate @sign-pair](/docs/Get-Started/get-an-atsign/images/generate-free-@sign-pair.png)
+
+When selected a number of free @signs given to chose from, once selected it is quickly activated,
+then once again you will be asked to store the cryptographic keys for the @sign.
+
+### Once you have your @signs and keys
+
+You are ready to start using the @platform! We have a number [demo apps](https://github.com/atsign-foundation/at_demos) that are constantly being updated, feel free to
+fork or clone and try them.
+There is also another nice app in development by [xavierchanth](https://github.com/XavierChanth/chit_chat) which is a
+chat app using the @platform. It is a nice example to follow as it uses the [contacts](https://pub.dev/packages/at_contact)
+combined with the [at_chat_flutter](https://pub.dev/packages/at_chat_flutter) widgets to create a simple chat app between
+@signs.
+
+![ChitCh@t](/docs/Get-Started/get-an-atsign/images/ChitCh@t-low.png)
+
+Each @ enabled application will ask you once for your @sign and then your keys, so it can synchronize with your secondary server.
+This means you might like to store your keys on a personal network drive or service (e.g. gdrive/idrive/onedrive) so
+you can connect other @ enabled apps to your @sign easily. Remember not to share and protect your keys.
+
+### Other widgets and the @platform/@protocol source code
+
+We have an ever-growing number of widgets on [pub.dev](https://pub.dev/publishers/atsign.org/packages)
+The @plaform and the @protocol are open source projects on [GitHub](https://github.com/atsign-foundation). If you see something missing,
+or not working let us know or better still contribute with a PR!
+
+## Where should I go next?
+
+First, if you haven't setup Flutter, do that [here](/docs/get-started/setup-your-env/).
+
+Otherwise, continue to building your first app [here](/docs/get-started/create-a-project/). -->

content/en/docs/Get-Started/Understand the @platform/polymorphism.md

@@ -5,4 +5,16 @@ linkTitle: 'Polymorphism'
 weight: 6
 content: Polymorphism
 description: Understanding Polymorphism on the @platform
----
+---
+
+Polymorphism on the @platform is the ability to share different data depending on the context of who's asking.
+@platform applications enable you to setup multiple personas for different areas of your life.
+When you share data with someone else, the value of that data may be different depending on the person receiving that data.
+
+For example:
+
+@alice's work persona may have a different value for email than her personal persona.
+When she shares her email to her colleagues, they will receive her work email, however when she shares it to her friends and family, they will see her personal email.
+As she updates the data in each of her personas, the changes will be reflected to each person that she has shared the data with.
+
+To learn more about polymorphism see [this article post](https://medium.com/flutter-community/building-flutter-apps-with-no-backend-9715b764a81e#67d3).