diff --git a/.c4builder b/.c4builder
index 7660d04..20da7bb 100644
--- a/.c4builder
+++ b/.c4builder
@@ -29,13 +29,6 @@
"hasRun": true,
"checksums": [
"eff025a09817785485a7c3cd9c62fb1dbd79c5682e01e362ca2cc0ea1942d5b4",
- "a2eedf6c5abeeca7f8b53f0cd9cb65eaac03604ec92ef3ac629236029f969237",
- "3837a4607372c49d01edf97f7b326201ed285e5f892c9c92e464f50088d9923a",
- "8250c7ad340f312f4f0cd143d02fec9f91d485ac2fa2f723632d3eb054ff7f05",
- "f57402710ac6c2b5ef571bdf22e1032dbb638d9b389c8bb9603bfa248eb1f41c",
- "ea4010458811a2daf2d4deb96f5345434f4ea7e7a98abb9a244e2f1c31ff8a18",
- "59fe5d9d4b0a242920e837fcae655661e7a27e8adc70b9d077a804c147786bc5",
- "0fc8404e9339eec0b40b3f6feca250c908c9340069527790c6f4bb4ceb549900",
- "4cb917a45c22e48cce813cf8dbf5ee42a19da8c490233c03d79ded4ed6d210ef"
+ "8b44a66306857c99d88d1445be9d9636c1d5003b7a0cf39caf480e04ccb53d2b"
]
}
\ No newline at end of file
diff --git a/docs/1 Internet Banking System/1 Internet Banking System.pdf b/docs/1 Internet Banking System/1 Internet Banking System.pdf
deleted file mode 100644
index bf31a3b..0000000
Binary files a/docs/1 Internet Banking System/1 Internet Banking System.pdf and /dev/null differ
diff --git a/docs/1 Internet Banking System/API Application/API Application.pdf b/docs/1 Internet Banking System/API Application/API Application.pdf
deleted file mode 100644
index 28ab30a..0000000
Binary files a/docs/1 Internet Banking System/API Application/API Application.pdf and /dev/null differ
diff --git a/docs/1 Internet Banking System/API Application/HOME.md b/docs/1 Internet Banking System/API Application/HOME.md
deleted file mode 100644
index f93ea90..0000000
--- a/docs/1 Internet Banking System/API Application/HOME.md
+++ /dev/null
@@ -1,18 +0,0 @@
-# API Application
-
-
-
-[Download container diagram](container.svg ':ignore')
-
-**Level 3: Component diagram**
-
-Next you can zoom in and decompose each container further to identify the major structural building blocks and their interactions.
-
-The Component diagram shows how a container is made up of a number of "components", what each of those components are, their responsibilities and the technology/implementation details.
-
-**Scope**: A single container.
-
-**Primary elements**: Components within the container in scope.
-Supporting elements: Containers (within the software system in scope) plus people and software systems directly connected to the components.
-
-**Intended audience**: Software architects and developers.
\ No newline at end of file
diff --git a/docs/1 Internet Banking System/API Application/README.md b/docs/1 Internet Banking System/API Application/README.md
deleted file mode 100644
index fede92b..0000000
--- a/docs/1 Internet Banking System/API Application/README.md
+++ /dev/null
@@ -1,34 +0,0 @@
-# API Application
-
-`\1 Internet Banking System\API Application`
-
-* [PySocial Project](../../README.md)
- * [1 Internet Banking System](../../1%20Internet%20Banking%20System/README.md)
- * [**API Application**](../../1%20Internet%20Banking%20System/API%20Application/README.md)
- * [Single Page Application](../../1%20Internet%20Banking%20System/Single%20Page%20Application/README.md)
- * [Dynamic Diagram](../../1%20Internet%20Banking%20System/Single%20Page%20Application/Dynamic%20Diagram/README.md)
- * [Extended Docs](../../1%20Internet%20Banking%20System/Single%20Page%20Application/Extended%20Docs/README.md)
- * [2 Deployment](../../2%20Deployment/README.md)
-
----
-
-[1 Internet Banking System (up)](../../1%20Internet%20Banking%20System/README.md)
-
----
-
-
-
-[Download container diagram](container.svg ':ignore')
-
-**Level 3: Component diagram**
-
-Next you can zoom in and decompose each container further to identify the major structural building blocks and their interactions.
-
-The Component diagram shows how a container is made up of a number of "components", what each of those components are, their responsibilities and the technology/implementation details.
-
-**Scope**: A single container.
-
-**Primary elements**: Components within the container in scope.
-Supporting elements: Containers (within the software system in scope) plus people and software systems directly connected to the components.
-
-**Intended audience**: Software architects and developers.
\ No newline at end of file
diff --git a/docs/1 Internet Banking System/API Application/container.svg b/docs/1 Internet Banking System/API Application/container.svg
deleted file mode 100644
index e726157..0000000
--- a/docs/1 Internet Banking System/API Application/container.svg
+++ /dev/null
@@ -1,368 +0,0 @@
-
\ No newline at end of file
diff --git a/docs/1 Internet Banking System/HOME.md b/docs/1 Internet Banking System/HOME.md
deleted file mode 100644
index 3499431..0000000
--- a/docs/1 Internet Banking System/HOME.md
+++ /dev/null
@@ -1,20 +0,0 @@
-# 1 Internet Banking System
-
-
-
-[Download system diagram](system.svg ':ignore')
-
-**Level 2: Container diagram**
-
-Once you understand how your system fits in to the overall IT environment, a really useful next step is to zoom-in to the system boundary with a Container diagram. A "container" is something like a server-side web application, single-page application, desktop application, mobile app, database schema, file system, etc. Essentially, a container is a separately runnable/deployable unit (e.g. a separate process space) that executes code or stores data.
-
-The Container diagram shows the high-level shape of the software architecture and how responsibilities are distributed across it. It also shows the major technology choices and how the containers communicate with one another. It's a simple, high-level technology focussed diagram that is useful for software developers and support/operations staff alike.
-
-**Scope**: A single software system.
-
-**Primary elements**: Containers within the software system in scope.
-Supporting elements: People and software systems directly connected to the containers.
-
-**Intended audience**: Technical people inside and outside of the software development team; including software architects, developers and operations/support staff.
-
-**Notes**: This diagram says nothing about deployment scenarios, clustering, replication, failover, etc.
\ No newline at end of file
diff --git a/docs/1 Internet Banking System/README.md b/docs/1 Internet Banking System/README.md
deleted file mode 100644
index 76e9f55..0000000
--- a/docs/1 Internet Banking System/README.md
+++ /dev/null
@@ -1,40 +0,0 @@
-# 1 Internet Banking System
-
-`\1 Internet Banking System`
-
-* [PySocial Project](../README.md)
- * [**1 Internet Banking System**](../1%20Internet%20Banking%20System/README.md)
- * [API Application](../1%20Internet%20Banking%20System/API%20Application/README.md)
- * [Single Page Application](../1%20Internet%20Banking%20System/Single%20Page%20Application/README.md)
- * [Dynamic Diagram](../1%20Internet%20Banking%20System/Single%20Page%20Application/Dynamic%20Diagram/README.md)
- * [Extended Docs](../1%20Internet%20Banking%20System/Single%20Page%20Application/Extended%20Docs/README.md)
- * [2 Deployment](../2%20Deployment/README.md)
-
----
-
-[PySocial Project (up)](../README.md)
-
-- [API Application](../1%20Internet%20Banking%20System/API%20Application/README.md)
-
-- [Single Page Application](../1%20Internet%20Banking%20System/Single%20Page%20Application/README.md)
-
----
-
-
-
-[Download system diagram](system.svg ':ignore')
-
-**Level 2: Container diagram**
-
-Once you understand how your system fits in to the overall IT environment, a really useful next step is to zoom-in to the system boundary with a Container diagram. A "container" is something like a server-side web application, single-page application, desktop application, mobile app, database schema, file system, etc. Essentially, a container is a separately runnable/deployable unit (e.g. a separate process space) that executes code or stores data.
-
-The Container diagram shows the high-level shape of the software architecture and how responsibilities are distributed across it. It also shows the major technology choices and how the containers communicate with one another. It's a simple, high-level technology focussed diagram that is useful for software developers and support/operations staff alike.
-
-**Scope**: A single software system.
-
-**Primary elements**: Containers within the software system in scope.
-Supporting elements: People and software systems directly connected to the containers.
-
-**Intended audience**: Technical people inside and outside of the software development team; including software architects, developers and operations/support staff.
-
-**Notes**: This diagram says nothing about deployment scenarios, clustering, replication, failover, etc.
\ No newline at end of file
diff --git a/docs/1 Internet Banking System/Single Page Application/2020-01-10-16-21-41.png b/docs/1 Internet Banking System/Single Page Application/2020-01-10-16-21-41.png
deleted file mode 100644
index ea176bb..0000000
Binary files a/docs/1 Internet Banking System/Single Page Application/2020-01-10-16-21-41.png and /dev/null differ
diff --git a/docs/1 Internet Banking System/Single Page Application/Dynamic Diagram/Dynamic Diagram.pdf b/docs/1 Internet Banking System/Single Page Application/Dynamic Diagram/Dynamic Diagram.pdf
deleted file mode 100644
index b18d5b4..0000000
Binary files a/docs/1 Internet Banking System/Single Page Application/Dynamic Diagram/Dynamic Diagram.pdf and /dev/null differ
diff --git a/docs/1 Internet Banking System/Single Page Application/Dynamic Diagram/HOME.md b/docs/1 Internet Banking System/Single Page Application/Dynamic Diagram/HOME.md
deleted file mode 100644
index b172474..0000000
--- a/docs/1 Internet Banking System/Single Page Application/Dynamic Diagram/HOME.md
+++ /dev/null
@@ -1,15 +0,0 @@
-# Dynamic Diagram
-
-
-
-[Download dynamic diagram](dynamic.svg ':ignore')
-
-**Dynamic diagram**
-
-A simple dynamic diagram can be useful when you want to show how elements in a static model collaborate at runtime to implement a user story, use case, feature, etc. This dynamic diagram is based upon a UML communication diagram (previously known as a "UML collaboration diagram"). It is similar to a UML sequence diagram although it allows a free-form arrangement of diagram elements with numbered interactions to indicate ordering.
-
-**Scope**: An enterprise, software system or container.
-
-**Primary and supporting elements**: Depends on the diagram scope; enterprise (see System Landscape diagram), software system (see System Context or Container diagrams), container (see Component diagram).
-
-**Intended audience**: Technical and non-technical people, inside and outside of the software development team.
\ No newline at end of file
diff --git a/docs/1 Internet Banking System/Single Page Application/Dynamic Diagram/README.md b/docs/1 Internet Banking System/Single Page Application/Dynamic Diagram/README.md
deleted file mode 100644
index e352c9a..0000000
--- a/docs/1 Internet Banking System/Single Page Application/Dynamic Diagram/README.md
+++ /dev/null
@@ -1,31 +0,0 @@
-# Dynamic Diagram
-
-`\1 Internet Banking System\Single Page Application\Dynamic Diagram`
-
-* [PySocial Project](../../../README.md)
- * [1 Internet Banking System](../../../1%20Internet%20Banking%20System/README.md)
- * [API Application](../../../1%20Internet%20Banking%20System/API%20Application/README.md)
- * [Single Page Application](../../../1%20Internet%20Banking%20System/Single%20Page%20Application/README.md)
- * [**Dynamic Diagram**](../../../1%20Internet%20Banking%20System/Single%20Page%20Application/Dynamic%20Diagram/README.md)
- * [Extended Docs](../../../1%20Internet%20Banking%20System/Single%20Page%20Application/Extended%20Docs/README.md)
- * [2 Deployment](../../../2%20Deployment/README.md)
-
----
-
-[Single Page Application (up)](../../../1%20Internet%20Banking%20System/Single%20Page%20Application/README.md)
-
----
-
-
-
-[Download dynamic diagram](dynamic.svg ':ignore')
-
-**Dynamic diagram**
-
-A simple dynamic diagram can be useful when you want to show how elements in a static model collaborate at runtime to implement a user story, use case, feature, etc. This dynamic diagram is based upon a UML communication diagram (previously known as a "UML collaboration diagram"). It is similar to a UML sequence diagram although it allows a free-form arrangement of diagram elements with numbered interactions to indicate ordering.
-
-**Scope**: An enterprise, software system or container.
-
-**Primary and supporting elements**: Depends on the diagram scope; enterprise (see System Landscape diagram), software system (see System Context or Container diagrams), container (see Component diagram).
-
-**Intended audience**: Technical and non-technical people, inside and outside of the software development team.
\ No newline at end of file
diff --git a/docs/1 Internet Banking System/Single Page Application/Dynamic Diagram/dynamic.svg b/docs/1 Internet Banking System/Single Page Application/Dynamic Diagram/dynamic.svg
deleted file mode 100644
index 993760c..0000000
--- a/docs/1 Internet Banking System/Single Page Application/Dynamic Diagram/dynamic.svg
+++ /dev/null
@@ -1,341 +0,0 @@
-
\ No newline at end of file
diff --git a/docs/1 Internet Banking System/Single Page Application/Extended Docs/Extended Docs.pdf b/docs/1 Internet Banking System/Single Page Application/Extended Docs/Extended Docs.pdf
deleted file mode 100644
index eaabd3b..0000000
Binary files a/docs/1 Internet Banking System/Single Page Application/Extended Docs/Extended Docs.pdf and /dev/null differ
diff --git a/docs/1 Internet Banking System/Single Page Application/Extended Docs/HOME.md b/docs/1 Internet Banking System/Single Page Application/Extended Docs/HOME.md
deleted file mode 100644
index b0d2b2d..0000000
--- a/docs/1 Internet Banking System/Single Page Application/Extended Docs/HOME.md
+++ /dev/null
@@ -1,19 +0,0 @@
-# Extended Docs
-
-
-
-[Download class diagram](class.svg ':ignore')
-
-
-
-[Download sequence diagram](sequence.svg ':ignore')
-
-Multiple markdowns can be ordered using `.1.md, .2.md .. ..md`
-
-You can choose where to place a certain diagram by using ``
-
-
-
-[Download ditaa diagram](ditaa.png ':ignore')
-
-Feel free to add any additional details necesary.
diff --git a/docs/1 Internet Banking System/Single Page Application/Extended Docs/README.md b/docs/1 Internet Banking System/Single Page Application/Extended Docs/README.md
deleted file mode 100644
index b49ae34..0000000
--- a/docs/1 Internet Banking System/Single Page Application/Extended Docs/README.md
+++ /dev/null
@@ -1,35 +0,0 @@
-# Extended Docs
-
-`\1 Internet Banking System\Single Page Application\Extended Docs`
-
-* [PySocial Project](../../../README.md)
- * [1 Internet Banking System](../../../1%20Internet%20Banking%20System/README.md)
- * [API Application](../../../1%20Internet%20Banking%20System/API%20Application/README.md)
- * [Single Page Application](../../../1%20Internet%20Banking%20System/Single%20Page%20Application/README.md)
- * [Dynamic Diagram](../../../1%20Internet%20Banking%20System/Single%20Page%20Application/Dynamic%20Diagram/README.md)
- * [**Extended Docs**](../../../1%20Internet%20Banking%20System/Single%20Page%20Application/Extended%20Docs/README.md)
- * [2 Deployment](../../../2%20Deployment/README.md)
-
----
-
-[Single Page Application (up)](../../../1%20Internet%20Banking%20System/Single%20Page%20Application/README.md)
-
----
-
-
-
-[Download class diagram](class.svg ':ignore')
-
-
-
-[Download sequence diagram](sequence.svg ':ignore')
-
-Multiple markdowns can be ordered using `.1.md, .2.md .. ..md`
-
-You can choose where to place a certain diagram by using ``
-
-
-
-[Download ditaa diagram](ditaa.png ':ignore')
-
-Feel free to add any additional details necesary.
diff --git a/docs/1 Internet Banking System/Single Page Application/Extended Docs/class.svg b/docs/1 Internet Banking System/Single Page Application/Extended Docs/class.svg
deleted file mode 100644
index cb3faab..0000000
--- a/docs/1 Internet Banking System/Single Page Application/Extended Docs/class.svg
+++ /dev/null
@@ -1,77 +0,0 @@
-
\ No newline at end of file
diff --git a/docs/1 Internet Banking System/Single Page Application/Extended Docs/ditaa.png b/docs/1 Internet Banking System/Single Page Application/Extended Docs/ditaa.png
deleted file mode 100644
index 6a000c9..0000000
Binary files a/docs/1 Internet Banking System/Single Page Application/Extended Docs/ditaa.png and /dev/null differ
diff --git a/docs/1 Internet Banking System/Single Page Application/Extended Docs/sequence.svg b/docs/1 Internet Banking System/Single Page Application/Extended Docs/sequence.svg
deleted file mode 100644
index ec0510d..0000000
--- a/docs/1 Internet Banking System/Single Page Application/Extended Docs/sequence.svg
+++ /dev/null
@@ -1,31 +0,0 @@
-
\ No newline at end of file
diff --git a/docs/1 Internet Banking System/Single Page Application/HOME.md b/docs/1 Internet Banking System/Single Page Application/HOME.md
deleted file mode 100644
index 64f6fde..0000000
--- a/docs/1 Internet Banking System/Single Page Application/HOME.md
+++ /dev/null
@@ -1,22 +0,0 @@
-# Single Page Application
-
-
-
-[Download container diagram](container.svg ':ignore')
-
-**Level 3: Component diagram**
-
-Next you can zoom in and decompose each container further to identify the major structural building blocks and their interactions.
-
-The Component diagram shows how a container is made up of a number of "components", what each of those components are, their responsibilities and the technology/implementation details.
-
-**Scope**: A single container.
-
-**Primary elements**: Components within the container in scope.
-Supporting elements: Containers (within the software system in scope) plus people and software systems directly connected to the components.
-
-**Intended audience**: Software architects and developers.
-
-> Example of included local image
-
-
\ No newline at end of file
diff --git a/docs/1 Internet Banking System/Single Page Application/README.md b/docs/1 Internet Banking System/Single Page Application/README.md
deleted file mode 100644
index 8eda68d..0000000
--- a/docs/1 Internet Banking System/Single Page Application/README.md
+++ /dev/null
@@ -1,42 +0,0 @@
-# Single Page Application
-
-`\1 Internet Banking System\Single Page Application`
-
-* [PySocial Project](../../README.md)
- * [1 Internet Banking System](../../1%20Internet%20Banking%20System/README.md)
- * [API Application](../../1%20Internet%20Banking%20System/API%20Application/README.md)
- * [**Single Page Application**](../../1%20Internet%20Banking%20System/Single%20Page%20Application/README.md)
- * [Dynamic Diagram](../../1%20Internet%20Banking%20System/Single%20Page%20Application/Dynamic%20Diagram/README.md)
- * [Extended Docs](../../1%20Internet%20Banking%20System/Single%20Page%20Application/Extended%20Docs/README.md)
- * [2 Deployment](../../2%20Deployment/README.md)
-
----
-
-[1 Internet Banking System (up)](../../1%20Internet%20Banking%20System/README.md)
-
-- [Dynamic Diagram](../../1%20Internet%20Banking%20System/Single%20Page%20Application/Dynamic%20Diagram/README.md)
-
-- [Extended Docs](../../1%20Internet%20Banking%20System/Single%20Page%20Application/Extended%20Docs/README.md)
-
----
-
-
-
-[Download container diagram](container.svg ':ignore')
-
-**Level 3: Component diagram**
-
-Next you can zoom in and decompose each container further to identify the major structural building blocks and their interactions.
-
-The Component diagram shows how a container is made up of a number of "components", what each of those components are, their responsibilities and the technology/implementation details.
-
-**Scope**: A single container.
-
-**Primary elements**: Components within the container in scope.
-Supporting elements: Containers (within the software system in scope) plus people and software systems directly connected to the components.
-
-**Intended audience**: Software architects and developers.
-
-> Example of included local image
-
-
\ No newline at end of file
diff --git a/docs/1 Internet Banking System/Single Page Application/Single Page Application.pdf b/docs/1 Internet Banking System/Single Page Application/Single Page Application.pdf
deleted file mode 100644
index 5fdc693..0000000
Binary files a/docs/1 Internet Banking System/Single Page Application/Single Page Application.pdf and /dev/null differ
diff --git a/docs/1 Internet Banking System/Single Page Application/container.svg b/docs/1 Internet Banking System/Single Page Application/container.svg
deleted file mode 100644
index 3ca0e6a..0000000
--- a/docs/1 Internet Banking System/Single Page Application/container.svg
+++ /dev/null
@@ -1,347 +0,0 @@
-
\ No newline at end of file
diff --git a/docs/1 Internet Banking System/system.svg b/docs/1 Internet Banking System/system.svg
deleted file mode 100644
index d77cff3..0000000
--- a/docs/1 Internet Banking System/system.svg
+++ /dev/null
@@ -1,312 +0,0 @@
-
\ No newline at end of file
diff --git a/docs/1 PySocial System/1 PySocial System.pdf b/docs/1 PySocial System/1 PySocial System.pdf
new file mode 100644
index 0000000..daeb61e
Binary files /dev/null and b/docs/1 PySocial System/1 PySocial System.pdf differ
diff --git a/docs/1 PySocial System/HOME.md b/docs/1 PySocial System/HOME.md
new file mode 100644
index 0000000..1effb7c
--- /dev/null
+++ b/docs/1 PySocial System/HOME.md
@@ -0,0 +1,30 @@
+# 1 PySocial System
+
+
+
+[Download system diagram](system.svg ':ignore')
+
+**Level 2: Diagrama de contêiner**
+
+
+**Scope**: Sistema de software PySocial.
+
+**Elementos primários**:
+* PyWebView UI
+* Python Application
+* API Interface
+
+
+
+**Elementos de suporte:**
+* Usuário
+* Facebook API
+* Instagram API
+* X (Twiiter) API
+* TikTok API
+* YouTube API
+
+
+
+
+**Público-alvo**: Técnicos dentro e fora da equipe de desenvolvimento de software; incluindo arquitetos de software, desenvolvedores e equipe de operações/suporte.
\ No newline at end of file
diff --git a/docs/1 PySocial System/README.md b/docs/1 PySocial System/README.md
new file mode 100644
index 0000000..6429250
--- /dev/null
+++ b/docs/1 PySocial System/README.md
@@ -0,0 +1,41 @@
+# 1 PySocial System
+
+`\1 PySocial System`
+
+* [PySocial Project](../README.md)
+ * [**1 PySocial System**](../1%20PySocial%20System/README.md)
+
+---
+
+[PySocial Project (up)](../README.md)
+
+---
+
+
+
+[Download system diagram](system.svg ':ignore')
+
+**Level 2: Diagrama de contêiner**
+
+
+**Scope**: Sistema de software PySocial.
+
+**Elementos primários**:
+* PyWebView UI
+* Python Application
+* API Interface
+
+
+
+**Elementos de suporte:**
+* Usuário
+* Facebook API
+* Instagram API
+* X (Twiiter) API
+* TikTok API
+* YouTube API
+
+
+
+
+**Público-alvo**: Técnicos dentro e fora da equipe de desenvolvimento de software; incluindo arquitetos de software, desenvolvedores e equipe de operações/suporte.
\ No newline at end of file
diff --git a/docs/1 PySocial System/system.svg b/docs/1 PySocial System/system.svg
new file mode 100644
index 0000000..82788ba
--- /dev/null
+++ b/docs/1 PySocial System/system.svg
@@ -0,0 +1,313 @@
+
\ No newline at end of file
diff --git a/docs/2 Deployment/2 Deployment.pdf b/docs/2 Deployment/2 Deployment.pdf
deleted file mode 100644
index 6261b51..0000000
Binary files a/docs/2 Deployment/2 Deployment.pdf and /dev/null differ
diff --git a/docs/2 Deployment/HOME.md b/docs/2 Deployment/HOME.md
deleted file mode 100644
index 15050ef..0000000
--- a/docs/2 Deployment/HOME.md
+++ /dev/null
@@ -1,15 +0,0 @@
-# 2 Deployment
-
-
-
-[Download deployment diagram](deployment.svg ':ignore')
-
-**Deployment diagram**
-
-A deployment diagram allows you to illustrate how containers in the static model are mapped to infrastructure. This deployment diagram is based upon a UML deployment diagram, although simplified slightly to show the mapping between containers and deployment nodes. A deployment node is something like physical infrastructure (e.g. a physical server or device), virtualised infrastructure (e.g. IaaS, PaaS, a virtual machine), containerised infrastructure (e.g. a Docker container), an execution environment (e.g. a database server, Java EE web/application server, Microsoft IIS), etc. Deployment nodes can be nested.
-
-**Scope**: A single software system.
-
-**Primary elements**: Deployment nodes and containers within the software system in scope.
-
-**Intended audience**: Technical people inside and outside of the software development team; including software architects, developers and operations/support staff.
\ No newline at end of file
diff --git a/docs/2 Deployment/README.md b/docs/2 Deployment/README.md
deleted file mode 100644
index 1281367..0000000
--- a/docs/2 Deployment/README.md
+++ /dev/null
@@ -1,31 +0,0 @@
-# 2 Deployment
-
-`\2 Deployment`
-
-* [PySocial Project](../README.md)
- * [1 Internet Banking System](../1%20Internet%20Banking%20System/README.md)
- * [API Application](../1%20Internet%20Banking%20System/API%20Application/README.md)
- * [Single Page Application](../1%20Internet%20Banking%20System/Single%20Page%20Application/README.md)
- * [Dynamic Diagram](../1%20Internet%20Banking%20System/Single%20Page%20Application/Dynamic%20Diagram/README.md)
- * [Extended Docs](../1%20Internet%20Banking%20System/Single%20Page%20Application/Extended%20Docs/README.md)
- * [**2 Deployment**](../2%20Deployment/README.md)
-
----
-
-[PySocial Project (up)](../README.md)
-
----
-
-
-
-[Download deployment diagram](deployment.svg ':ignore')
-
-**Deployment diagram**
-
-A deployment diagram allows you to illustrate how containers in the static model are mapped to infrastructure. This deployment diagram is based upon a UML deployment diagram, although simplified slightly to show the mapping between containers and deployment nodes. A deployment node is something like physical infrastructure (e.g. a physical server or device), virtualised infrastructure (e.g. IaaS, PaaS, a virtual machine), containerised infrastructure (e.g. a Docker container), an execution environment (e.g. a database server, Java EE web/application server, Microsoft IIS), etc. Deployment nodes can be nested.
-
-**Scope**: A single software system.
-
-**Primary elements**: Deployment nodes and containers within the software system in scope.
-
-**Intended audience**: Technical people inside and outside of the software development team; including software architects, developers and operations/support staff.
\ No newline at end of file
diff --git a/docs/2 Deployment/deployment.svg b/docs/2 Deployment/deployment.svg
deleted file mode 100644
index 7207ec3..0000000
--- a/docs/2 Deployment/deployment.svg
+++ /dev/null
@@ -1,363 +0,0 @@
-
\ No newline at end of file
diff --git a/docs/2020-01-10-16-21-41.png b/docs/2020-01-10-16-21-41.png
deleted file mode 100644
index ea176bb..0000000
Binary files a/docs/2020-01-10-16-21-41.png and /dev/null differ
diff --git a/docs/PySocial Project.pdf b/docs/PySocial Project.pdf
index d53d030..9a40266 100644
Binary files a/docs/PySocial Project.pdf and b/docs/PySocial Project.pdf differ
diff --git a/docs/PySocial.md b/docs/PySocial.md
index 8b6e292..70348d6 100644
--- a/docs/PySocial.md
+++ b/docs/PySocial.md
@@ -1,12 +1,7 @@
# PySocial
* [PySocial Project](#PySocial-Project)
- * [1 Internet Banking System](#1-Internet-Banking-System)
- * [API Application](#API-Application)
- * [Single Page Application](#Single-Page-Application)
- * [Dynamic Diagram](#Dynamic-Diagram)
- * [Extended Docs](#Extended-Docs)
- * [2 Deployment](#2-Deployment)
+ * [1 PySocial System](#1-PySocial-System)
---
@@ -37,150 +32,38 @@
**Público-alvo**: Todos, técnicos e não técnicos, dentro e fora da equipe de desenvolvimento de software.
-## 1 Internet Banking System
+## 1 PySocial System
-`\1 Internet Banking System`
+`\1 PySocial System`
[PySocial Project](#PySocial)
-
+
-[Download system diagram](/1%20Internet%20Banking%20System/system.svg ':ignore')
+[Download system diagram](/1%20PySocial%20System/system.svg ':ignore')
-**Level 2: Container diagram**
+**Level 2: Diagrama de contêiner**
-Once you understand how your system fits in to the overall IT environment, a really useful next step is to zoom-in to the system boundary with a Container diagram. A "container" is something like a server-side web application, single-page application, desktop application, mobile app, database schema, file system, etc. Essentially, a container is a separately runnable/deployable unit (e.g. a separate process space) that executes code or stores data.
-The Container diagram shows the high-level shape of the software architecture and how responsibilities are distributed across it. It also shows the major technology choices and how the containers communicate with one another. It's a simple, high-level technology focussed diagram that is useful for software developers and support/operations staff alike.
+**Scope**: Sistema de software PySocial.
-**Scope**: A single software system.
+**Elementos primários**:
+* PyWebView UI
+* Python Application
+* API Interface
-**Primary elements**: Containers within the software system in scope.
-Supporting elements: People and software systems directly connected to the containers.
-
-**Intended audience**: Technical people inside and outside of the software development team; including software architects, developers and operations/support staff.
-
-**Notes**: This diagram says nothing about deployment scenarios, clustering, replication, failover, etc.
-
-## API Application
-
-`\1 Internet Banking System\API Application`
-
-[PySocial Project](#PySocial)
-
-
-
-
-[Download container diagram](/1%20Internet%20Banking%20System/API%20Application/container.svg ':ignore')
-
-**Level 3: Component diagram**
-
-Next you can zoom in and decompose each container further to identify the major structural building blocks and their interactions.
-
-The Component diagram shows how a container is made up of a number of "components", what each of those components are, their responsibilities and the technology/implementation details.
-
-**Scope**: A single container.
-
-**Primary elements**: Components within the container in scope.
-Supporting elements: Containers (within the software system in scope) plus people and software systems directly connected to the components.
-
-**Intended audience**: Software architects and developers.
-
-## Single Page Application
-
-`\1 Internet Banking System\Single Page Application`
-
-[PySocial Project](#PySocial)
-
-
-
-
-[Download container diagram](/1%20Internet%20Banking%20System/Single%20Page%20Application/container.svg ':ignore')
-
-**Level 3: Component diagram**
-
-Next you can zoom in and decompose each container further to identify the major structural building blocks and their interactions.
-
-The Component diagram shows how a container is made up of a number of "components", what each of those components are, their responsibilities and the technology/implementation details.
-
-**Scope**: A single container.
-
-**Primary elements**: Components within the container in scope.
-Supporting elements: Containers (within the software system in scope) plus people and software systems directly connected to the components.
-
-**Intended audience**: Software architects and developers.
-
-> Example of included local image
-
-
-
-## Dynamic Diagram
-
-`\1 Internet Banking System\Single Page Application\Dynamic Diagram`
-
-[PySocial Project](#PySocial)
-
-
-
-
-[Download dynamic diagram](/1%20Internet%20Banking%20System/Single%20Page%20Application/Dynamic%20Diagram/dynamic.svg ':ignore')
-
-**Dynamic diagram**
-
-A simple dynamic diagram can be useful when you want to show how elements in a static model collaborate at runtime to implement a user story, use case, feature, etc. This dynamic diagram is based upon a UML communication diagram (previously known as a "UML collaboration diagram"). It is similar to a UML sequence diagram although it allows a free-form arrangement of diagram elements with numbered interactions to indicate ordering.
-
-**Scope**: An enterprise, software system or container.
-
-**Primary and supporting elements**: Depends on the diagram scope; enterprise (see System Landscape diagram), software system (see System Context or Container diagrams), container (see Component diagram).
-
-**Intended audience**: Technical and non-technical people, inside and outside of the software development team.
-
-## Extended Docs
-
-`\1 Internet Banking System\Single Page Application\Extended Docs`
-
-[PySocial Project](#PySocial)
-
-
-
-
-[Download class diagram](/1%20Internet%20Banking%20System/Single%20Page%20Application/Extended%20Docs/class.svg ':ignore')
-
-
-
-
-[Download sequence diagram](/1%20Internet%20Banking%20System/Single%20Page%20Application/Extended%20Docs/sequence.svg ':ignore')
-
-Multiple markdowns can be ordered using `.1.md, .2.md .. ..md`
-
-You can choose where to place a certain diagram by using ``
-
-
-
-
-[Download ditaa diagram](/1%20Internet%20Banking%20System/Single%20Page%20Application/Extended%20Docs/ditaa.png ':ignore')
-
-Feel free to add any additional details necesary.
-
-
-## 2 Deployment
-
-`\2 Deployment`
-
-[PySocial Project](#PySocial)
-
-
-
-
-[Download deployment diagram](/2%20Deployment/deployment.svg ':ignore')
-
-**Deployment diagram**
+
-A deployment diagram allows you to illustrate how containers in the static model are mapped to infrastructure. This deployment diagram is based upon a UML deployment diagram, although simplified slightly to show the mapping between containers and deployment nodes. A deployment node is something like physical infrastructure (e.g. a physical server or device), virtualised infrastructure (e.g. IaaS, PaaS, a virtual machine), containerised infrastructure (e.g. a Docker container), an execution environment (e.g. a database server, Java EE web/application server, Microsoft IIS), etc. Deployment nodes can be nested.
+**Elementos de suporte:**
+* Usuário
+* Facebook API
+* Instagram API
+* X (Twiiter) API
+* TikTok API
+* YouTube API
-**Scope**: A single software system.
-**Primary elements**: Deployment nodes and containers within the software system in scope.
+
-**Intended audience**: Technical people inside and outside of the software development team; including software architects, developers and operations/support staff.
\ No newline at end of file
+**Público-alvo**: Técnicos dentro e fora da equipe de desenvolvimento de software; incluindo arquitetos de software, desenvolvedores e equipe de operações/suporte.
\ No newline at end of file
diff --git a/docs/PySocial.pdf b/docs/PySocial.pdf
index 9e257e8..b326059 100644
Binary files a/docs/PySocial.pdf and b/docs/PySocial.pdf differ
diff --git a/docs/README.md b/docs/README.md
index acbc64a..c3de3d0 100644
--- a/docs/README.md
+++ b/docs/README.md
@@ -1,18 +1,11 @@
# PySocial Project
* [**PySocial Project**](README.md)
- * [1 Internet Banking System](1%20Internet%20Banking%20System/README.md)
- * [API Application](1%20Internet%20Banking%20System/API%20Application/README.md)
- * [Single Page Application](1%20Internet%20Banking%20System/Single%20Page%20Application/README.md)
- * [Dynamic Diagram](1%20Internet%20Banking%20System/Single%20Page%20Application/Dynamic%20Diagram/README.md)
- * [Extended Docs](1%20Internet%20Banking%20System/Single%20Page%20Application/Extended%20Docs/README.md)
- * [2 Deployment](2%20Deployment/README.md)
+ * [1 PySocial System](1%20PySocial%20System/README.md)
---
-- [1 Internet Banking System](1%20Internet%20Banking%20System/README.md)
-
-- [2 Deployment](2%20Deployment/README.md)
+- [1 PySocial System](1%20PySocial%20System/README.md)
---
diff --git a/docs/_sidebar.md b/docs/_sidebar.md
index b6fdb5b..5e38867 100644
--- a/docs/_sidebar.md
+++ b/docs/_sidebar.md
@@ -1,7 +1,2 @@
* [PySocial Project](HOME)
- * [1 Internet Banking System](1%20Internet%20Banking%20System/HOME)
- * [API Application](1%20Internet%20Banking%20System/API%20Application/HOME)
- * [Single Page Application](1%20Internet%20Banking%20System/Single%20Page%20Application/HOME)
- * [Dynamic Diagram](1%20Internet%20Banking%20System/Single%20Page%20Application/Dynamic%20Diagram/HOME)
- * [Extended Docs](1%20Internet%20Banking%20System/Single%20Page%20Application/Extended%20Docs/HOME)
- * [2 Deployment](2%20Deployment/HOME)
+ * [1 PySocial System](1%20PySocial%20System/HOME)
diff --git a/src/1 Internet Banking System/API Application/container.md b/src/1 Internet Banking System/API Application/container.md
deleted file mode 100644
index e784698..0000000
--- a/src/1 Internet Banking System/API Application/container.md
+++ /dev/null
@@ -1,12 +0,0 @@
-**Level 3: Component diagram**
-
-Next you can zoom in and decompose each container further to identify the major structural building blocks and their interactions.
-
-The Component diagram shows how a container is made up of a number of "components", what each of those components are, their responsibilities and the technology/implementation details.
-
-**Scope**: A single container.
-
-**Primary elements**: Components within the container in scope.
-Supporting elements: Containers (within the software system in scope) plus people and software systems directly connected to the components.
-
-**Intended audience**: Software architects and developers.
\ No newline at end of file
diff --git a/src/1 Internet Banking System/API Application/container.puml b/src/1 Internet Banking System/API Application/container.puml
deleted file mode 100644
index 26ed266..0000000
--- a/src/1 Internet Banking System/API Application/container.puml
+++ /dev/null
@@ -1,28 +0,0 @@
-@startuml
-!include https://raw.githubusercontent.com/adrianvlupu/C4-PlantUML/latest/C4_Component.puml
-
-LAYOUT_WITH_LEGEND()
-
-Container(spa, "Single Page Application", "javascript and react", "Provides all the internet banking functionality to customers via their web browser.")
-Container(ma, "Mobile App", "Xamarin", "Provides a limited subset ot the internet banking functionality to customers via their mobile mobile device.")
-Container(db, "Database", "Relational Database Schema", "Stores user registration information, hashed authentication credentials, access logs, etc.")
-System_Ext(mbs, "Mainframe Banking System", "Stores all of the core banking information about customers, accounts, transactions, etc.")
-
-Container_Boundary(api, "API Application") {
- Component(sign, "Sign In Controller", "MVC Rest Controlle", "Allows users to sign in to the internet banking system")
- Component(accounts, "Accounts Summary Controller", "MVC Rest Controlle", "Provides customers with a summory of their bank accounts")
- Component(security, "Security Component", "Spring Bean", "Provides functionality related to singing in, changing passwords, etc.")
- Component(mbsfacade, "Mainframe Banking System Facade", "Spring Bean", "A facade onto the mainframe banking system.")
-
- Rel(sign, security, "Uses")
- Rel(accounts, mbsfacade, "Uses")
- Rel(security, db, "Read & write to", "JDBC")
- Rel(mbsfacade, mbs, "Uses", "XML/HTTPS")
-}
-
-Rel(spa, sign, "Uses", "JSON/HTTPS")
-Rel(spa, accounts, "Uses", "JSON/HTTPS")
-
-Rel(ma, sign, "Uses", "JSON/HTTPS")
-Rel(ma, accounts, "Uses", "JSON/HTTPS")
-@enduml
diff --git a/src/1 Internet Banking System/Single Page Application/2020-01-10-16-21-41.png b/src/1 Internet Banking System/Single Page Application/2020-01-10-16-21-41.png
deleted file mode 100644
index ea176bb..0000000
Binary files a/src/1 Internet Banking System/Single Page Application/2020-01-10-16-21-41.png and /dev/null differ
diff --git a/src/1 Internet Banking System/Single Page Application/Dynamic Diagram/dynamic.md b/src/1 Internet Banking System/Single Page Application/Dynamic Diagram/dynamic.md
deleted file mode 100644
index c01ca1b..0000000
--- a/src/1 Internet Banking System/Single Page Application/Dynamic Diagram/dynamic.md
+++ /dev/null
@@ -1,9 +0,0 @@
-**Dynamic diagram**
-
-A simple dynamic diagram can be useful when you want to show how elements in a static model collaborate at runtime to implement a user story, use case, feature, etc. This dynamic diagram is based upon a UML communication diagram (previously known as a "UML collaboration diagram"). It is similar to a UML sequence diagram although it allows a free-form arrangement of diagram elements with numbered interactions to indicate ordering.
-
-**Scope**: An enterprise, software system or container.
-
-**Primary and supporting elements**: Depends on the diagram scope; enterprise (see System Landscape diagram), software system (see System Context or Container diagrams), container (see Component diagram).
-
-**Intended audience**: Technical and non-technical people, inside and outside of the software development team.
\ No newline at end of file
diff --git a/src/1 Internet Banking System/Single Page Application/Dynamic Diagram/dynamic.puml b/src/1 Internet Banking System/Single Page Application/Dynamic Diagram/dynamic.puml
deleted file mode 100644
index 7709819..0000000
--- a/src/1 Internet Banking System/Single Page Application/Dynamic Diagram/dynamic.puml
+++ /dev/null
@@ -1,15 +0,0 @@
-@startuml
-!include https://raw.githubusercontent.com/adrianvlupu/C4-PlantUML/latest/C4_Dynamic.puml
-
-Container(spa, "Single Page Application", "javascript and Angular", "Provides all the internet banking functionality to customers via thier web browser.")
-ContainerDb(db, "Database", "Oracle Database Schema", "Stores user registration information hashed authentication credentials, access logs, etc.")
-Container_Boundary(bc, "API Application"){
- Component(signin, "Sign In Controller", "Spring MVC Rest Controller", "Allows users to sign in to the internet Banking System")
- Component(security, "Security Component", "Spring Bean", "Provides functionality related to signing in, changing passwords, etc.")
-}
-
-Rel(spa, signin, "Submits credentials to", "JSON/HTTPS")
-Rel(signin, security, "Calls isAuthenticated() on")
-Rel(security, db, "select * from users where username = ?", "JDBC")
-
-@enduml
diff --git a/src/1 Internet Banking System/Single Page Application/Extended Docs/class.puml b/src/1 Internet Banking System/Single Page Application/Extended Docs/class.puml
deleted file mode 100644
index cd726b2..0000000
--- a/src/1 Internet Banking System/Single Page Application/Extended Docs/class.puml
+++ /dev/null
@@ -1,26 +0,0 @@
-@startuml
-' Split into 4 pages
-page 2x2
-skinparam pageMargin 10
-skinparam pageExternalColor gray
-skinparam pageBorderColor black
-
-class BaseClass
-
-namespace net.dummy #DDDDDD {
- .BaseClass <|-- Person
- Meeting o-- Person
-
- .BaseClass <|- Meeting
-
-}
-
-namespace net.foo {
- net.dummy.Person <|- Person
- .BaseClass <|-- Person
-
- net.dummy.Meeting o-- Person
-}
-
-BaseClass <|-- net.unused.Person
-@enduml
\ No newline at end of file
diff --git a/src/1 Internet Banking System/Single Page Application/Extended Docs/details.1.md b/src/1 Internet Banking System/Single Page Application/Extended Docs/details.1.md
deleted file mode 100644
index 214c72e..0000000
--- a/src/1 Internet Banking System/Single Page Application/Extended Docs/details.1.md
+++ /dev/null
@@ -1 +0,0 @@
-Multiple markdowns can be ordered using `.1.md, .2.md .. ..md`
\ No newline at end of file
diff --git a/src/1 Internet Banking System/Single Page Application/Extended Docs/details.md b/src/1 Internet Banking System/Single Page Application/Extended Docs/details.md
deleted file mode 100644
index 82e37ec..0000000
--- a/src/1 Internet Banking System/Single Page Application/Extended Docs/details.md
+++ /dev/null
@@ -1,5 +0,0 @@
-You can choose where to place a certain diagram by using ``
-
-
-
-Feel free to add any additional details necesary.
diff --git a/src/1 Internet Banking System/Single Page Application/Extended Docs/ditaa.puml b/src/1 Internet Banking System/Single Page Application/Extended Docs/ditaa.puml
deleted file mode 100644
index 62aac64..0000000
--- a/src/1 Internet Banking System/Single Page Application/Extended Docs/ditaa.puml
+++ /dev/null
@@ -1,9 +0,0 @@
-@startditaa -E
-+---------+ /--------\ +-------+
-| cBLU +--+cAAA +---+Version|
-| | | Data | | V3 |
-| +----+ | Base | |cRED{d}|
-| |cPNK| | {s}| +-------+
-| | | \---+----/
-+----+----+
-@endditaa
\ No newline at end of file
diff --git a/src/1 Internet Banking System/Single Page Application/Extended Docs/sequence.puml b/src/1 Internet Banking System/Single Page Application/Extended Docs/sequence.puml
deleted file mode 100644
index 5f13ffa..0000000
--- a/src/1 Internet Banking System/Single Page Application/Extended Docs/sequence.puml
+++ /dev/null
@@ -1,21 +0,0 @@
-@startuml
-participant User
-
-User -> A: DoWork
-activate A
-
-A -> B: << createRequest >>
-activate B
-
-B -> C: DoWork
-activate C
-C --> B: WorkDone
-destroy C
-
-B --> A: RequestCreated
-deactivate B
-
-A -> User: Done
-deactivate A
-
-@enduml
\ No newline at end of file
diff --git a/src/1 Internet Banking System/Single Page Application/container.md b/src/1 Internet Banking System/Single Page Application/container.md
deleted file mode 100644
index 282e9b8..0000000
--- a/src/1 Internet Banking System/Single Page Application/container.md
+++ /dev/null
@@ -1,16 +0,0 @@
-**Level 3: Component diagram**
-
-Next you can zoom in and decompose each container further to identify the major structural building blocks and their interactions.
-
-The Component diagram shows how a container is made up of a number of "components", what each of those components are, their responsibilities and the technology/implementation details.
-
-**Scope**: A single container.
-
-**Primary elements**: Components within the container in scope.
-Supporting elements: Containers (within the software system in scope) plus people and software systems directly connected to the components.
-
-**Intended audience**: Software architects and developers.
-
-> Example of included local image
-
-
\ No newline at end of file
diff --git a/src/1 Internet Banking System/Single Page Application/container.puml b/src/1 Internet Banking System/Single Page Application/container.puml
deleted file mode 100644
index 8124325..0000000
--- a/src/1 Internet Banking System/Single Page Application/container.puml
+++ /dev/null
@@ -1,21 +0,0 @@
-@startuml
-!include https://raw.githubusercontent.com/adrianvlupu/C4-PlantUML/latest/C4_Component.puml
-
-LAYOUT_WITH_LEGEND()
-
-Container(api, "API Application", "java and Spring MVC", "Delivers the static content and the internet banking single page application.")
-
-Container_Boundary(spa, "Single Page Application") {
- Component(routing, "Routing", "React router", "Handler slient side routing")
- Component(store, "Data Store", "Redux", "The central object holding the application state")
- Component(login, "Login form", "React Class", "The login page")
- Component(profile, "Profile Page", "React Class", "The page where the logged in user can view and edit his/her information")
-}
-
-Rel(spa, api, "Uses", "JSON/HTTPS")
-
-Rel(login, store, "Uses");
-Rel(routing, store, "Uses");
-Rel(profile, store, "Uses");
-
-@enduml
diff --git a/src/1 Internet Banking System/system.md b/src/1 Internet Banking System/system.md
deleted file mode 100644
index 13cedbc..0000000
--- a/src/1 Internet Banking System/system.md
+++ /dev/null
@@ -1,14 +0,0 @@
-**Level 2: Container diagram**
-
-Once you understand how your system fits in to the overall IT environment, a really useful next step is to zoom-in to the system boundary with a Container diagram. A "container" is something like a server-side web application, single-page application, desktop application, mobile app, database schema, file system, etc. Essentially, a container is a separately runnable/deployable unit (e.g. a separate process space) that executes code or stores data.
-
-The Container diagram shows the high-level shape of the software architecture and how responsibilities are distributed across it. It also shows the major technology choices and how the containers communicate with one another. It's a simple, high-level technology focussed diagram that is useful for software developers and support/operations staff alike.
-
-**Scope**: A single software system.
-
-**Primary elements**: Containers within the software system in scope.
-Supporting elements: People and software systems directly connected to the containers.
-
-**Intended audience**: Technical people inside and outside of the software development team; including software architects, developers and operations/support staff.
-
-**Notes**: This diagram says nothing about deployment scenarios, clustering, replication, failover, etc.
\ No newline at end of file
diff --git a/src/1 Internet Banking System/system.puml b/src/1 Internet Banking System/system.puml
deleted file mode 100644
index 2c73f08..0000000
--- a/src/1 Internet Banking System/system.puml
+++ /dev/null
@@ -1,28 +0,0 @@
-@startuml
-!include https://raw.githubusercontent.com/adrianvlupu/C4-PlantUML/latest/C4_Container.puml
-
-LAYOUT_WITH_LEGEND()
-
-Person(pbc, "Personal Banking Customer", "A customer of the bank, with personal bank accounts.")
-System_Ext(es, "E-mail system", "The internal Microsoft Exchange e-mail system.")
-System_Ext(mbs, "Mainframe Banking System", "Stores all of the core banking information about customers, accounts, transactions, etc.")
-System_Boundary(ibs, "Internet Banking") {
- Container(wa, "Web Application", "java and Spring MVC", "Delivers the static content and the internet banking single page application.")
- Container(spa, "Single Page Application", "javascript and angular", "Provides all the internet banking functionality to customers via their web browser.")
- Container(ma, "Mobile App", "Xamarin", "Provides a limited subset ot the internet banking functionality to customers via their mobile mobile device.")
- Container(db, "Database", "Relational Database Schema", "Stores user registration information, hashed authentication credentials, access logs, etc.")
- Container(api, "API Application", "java and String MVC", "Provides internet banking functionality via a JSON/HTTP API.")
-
- Rel(api, es, "Sends e-mails", "SMTP")
- Rel(api, mbs, "Uses", "XML/HTTPS")
- Rel(api, db, "Reads & writes to", "JDBC")
- Rel(wa, spa, "Delivers")
- Rel(spa, api, "Uses", "JSON/HTTPS")
- Rel(ma, api, "Uses", "JSON/HTTPS")
-}
-
-Rel(pbc, wa, "Uses", "HTTPS")
-Rel(pbc, spa, "Uses")
-Rel(pbc, ma, "Uses")
-Rel(es, pbc, "Sends e-mails to")
-@enduml
diff --git a/src/1 PySocial System/system.md b/src/1 PySocial System/system.md
new file mode 100644
index 0000000..a360663
--- /dev/null
+++ b/src/1 PySocial System/system.md
@@ -0,0 +1,24 @@
+**Level 2: Diagrama de contêiner**
+
+
+**Scope**: Sistema de software PySocial.
+
+**Elementos primários**:
+* PyWebView UI
+* Python Application
+* API Interface
+
+
+
+**Elementos de suporte:**
+* Usuário
+* Facebook API
+* Instagram API
+* X (Twiiter) API
+* TikTok API
+* YouTube API
+
+
+
+
+**Público-alvo**: Técnicos dentro e fora da equipe de desenvolvimento de software; incluindo arquitetos de software, desenvolvedores e equipe de operações/suporte.
\ No newline at end of file
diff --git a/src/1 PySocial System/system.puml b/src/1 PySocial System/system.puml
new file mode 100644
index 0000000..e8cf566
--- /dev/null
+++ b/src/1 PySocial System/system.puml
@@ -0,0 +1,29 @@
+@startuml
+!include https://raw.githubusercontent.com/adrianvlupu/C4-PlantUML/latest/C4_Container.puml
+
+LAYOUT_WITH_LEGEND()
+
+Person(user, "Usuário", "Um usuário que possue a necessidade de enviar o mesmo conteúdo para várias redes sociais.")
+System_Ext(face, "Facebook API", "Interface de comunicação com rede social Facebook.")
+System_Ext(inst, "Instagram API", "Interface de comunicação com rede social Instagram.")
+System_Ext(x, "X (Twiiter) API", "Interface de comunicação com rede social X.")
+System_Ext(tt, "TikTok API", "Interface de comunicação com rede social TikTok.")
+System_Ext(yt, "YouTube API", "Interface de comunicação com rede social YouTube.")
+
+System_Boundary(pys, "PySocial System") {
+ Container(pyWeb, "PyWebView UI", "Python3", "UI da aplicação")
+ Container(py, "Python Application", "Python3", "Core domain da aplicação")
+ Container(pyAcl, "API Interface", "Python3", "ACL da aplicação")
+
+ Rel(pyWeb, py, "Uses")
+ Rel(py, pyAcl, "Uses")
+}
+
+Rel(user, pyWeb, "Interage com", "UI")
+Rel(pyAcl, face, "requisita", "JSON/HTTPS")
+Rel(pyAcl, inst, "requisita", "JSON/HTTPS")
+Rel(pyAcl, x, "requisita", "JSON/HTTPS")
+Rel(pyAcl, tt, "requisita", "JSON/HTTPS")
+Rel(pyAcl, yt, "requisita", "JSON/HTTPS")
+
+@enduml
diff --git a/src/2 Deployment/deployment.md b/src/2 Deployment/deployment.md
deleted file mode 100644
index 99e9ccd..0000000
--- a/src/2 Deployment/deployment.md
+++ /dev/null
@@ -1,9 +0,0 @@
-**Deployment diagram**
-
-A deployment diagram allows you to illustrate how containers in the static model are mapped to infrastructure. This deployment diagram is based upon a UML deployment diagram, although simplified slightly to show the mapping between containers and deployment nodes. A deployment node is something like physical infrastructure (e.g. a physical server or device), virtualised infrastructure (e.g. IaaS, PaaS, a virtual machine), containerised infrastructure (e.g. a Docker container), an execution environment (e.g. a database server, Java EE web/application server, Microsoft IIS), etc. Deployment nodes can be nested.
-
-**Scope**: A single software system.
-
-**Primary elements**: Deployment nodes and containers within the software system in scope.
-
-**Intended audience**: Technical people inside and outside of the software development team; including software architects, developers and operations/support staff.
\ No newline at end of file
diff --git a/src/2 Deployment/deployment.puml b/src/2 Deployment/deployment.puml
deleted file mode 100644
index a812d6a..0000000
--- a/src/2 Deployment/deployment.puml
+++ /dev/null
@@ -1,46 +0,0 @@
-@startuml
-!include https://raw.githubusercontent.com/adrianvlupu/C4-PlantUML/latest/C4_Deployment.puml
-
-LAYOUT_WITH_LEGEND()
-
-Deployment_Node(plc, "Big Bank plc", "Big Bank plc data center"){
- Deployment_Node(dn, "bigbank-api***\tx8", "Ubuntu 16.04 LTS"){
- Deployment_Node(apache, "Apache Tomcat", "Apache Tomcat 8.x"){
- Container(api, "API Application", "Java and Spring MVC", "Provides Internet Banking functionality via a JSON/HTTPS API.")
- }
- }
- Deployment_Node(bigbankdb01, "bigbank-db01", "Ubuntu 16.04 LTS"){
- Deployment_Node(oracle, "Oracle - Primary", "Oracle 12c"){
- ContainerDb(db, "Database", "Relational Database Schema", "Stores user registration information, hashed authentication credentials, access logs, etc.")
- }
- }
- Deployment_Node(bigbankdb02, "bigbank-db02", "Ubuntu 16.04 LTS"){
- Deployment_Node(oracle2, "Oracle - Secondary", "Oracle 12c"){
- ContainerDb(db2, "Database", "Relational Database Schema", "Stores user registration information, hashed authentication credentials, access logs, etc.")
- }
- }
- Deployment_Node(bb2, "bigbank-web***\tx4", "Ubuntu 16.04 LTS"){
- Deployment_Node(apache2, "Apache Tomcat", "Apache Tomcat 8.x"){
- Container(web, "Web Application", "Java and Spring MVC", "Delivers the static content and the Internet Banking single page application.")
- }
- }
-}
-
-Deployment_Node(mob, "Customer's mobile device", "Apple IOS or Android"){
- Container(mobile, "Mobile App", "Xamarin", "Provides a limited subset of the Internet Banking functionality to customers via their mobile device.")
-}
-
-Deployment_Node(comp, "Customer's computer", "Mircosoft Windows of Apple macOS"){
- Deployment_Node(browser, "Web Browser", "Google Chrome, Mozilla Firefox"){
- Container(spa, "Single Page Application", "JavaScript and Angular", "Provides all of the Internet Banking functionality to customers via their web browser.")
- }
-}
-
-Rel(mobile, api, "Makes API calls to", "json/HTTPS")
-Rel(spa, api, "Makes API calls to", "json/HTTPS")
-Rel(web, spa, "Delivers to the customer's web browser")
-Rel(api, db, "Reads from and writes to", "JDBC")
-Rel(api, db2, "Reads from and writes to", "JDBC")
-Rel(db, db2, "Replicates data to")
-
-@enduml
\ No newline at end of file