Use the published versions of the diagrams.

Author: simonbrowndotje

docs/component-diagram.md

@@ -8,7 +8,7 @@ The Component diagram shows how a container is made up of a number of "component
 
 This is an example Component diagram for a fictional Internet Banking System, showing some (rather than all) of the components within the API Application. Here, there are two Spring MVC Rest Controllers providing access points for the JSON/HTTPS API, with each controller subsequently using other components to access data from the Database and Mainframe Banking System.
 
-![An example Component diagram](images/component-diagram-1.png)
+![An example Component diagram](https://static.structurizr.com/workspace/36141/diagrams/Components.png)
 
 See [InternetBankingSystem.java](https://github.com/structurizr/examples/blob/main/java/src/main/java/com/structurizr/example/bigbankplc/InternetBankingSystem.java) for the code, and [https://structurizr.com/share/36141/diagrams#Components](https://structurizr.com/share/36141/diagrams#Components) for the diagram.
 

docs/container-diagram.md

@@ -10,6 +10,6 @@ This is an example Container diagram for a fictional Internet Banking System. It
 
 Both the Single-Page Application and Mobile App use a JSON/HTTPS API, which is provided by another Java/Spring MVC application running on the server. The API Application gets user information from the Database (a relational database schema). The API Application also communicates with the existing Mainframe Banking System, using a propreitary XML/HTTPS interface, to get information about bank accounts or make transactions. The API Application also uses the existing E-mail System if it needs to send e-mails to customers.
 
-![An example Container diagram](images/container-diagram-1.png)
+![An example Container diagram](https://static.structurizr.com/workspace/36141/diagrams/Containers.png)
 
 See [InternetBankingSystem.java](https://github.com/structurizr/examples/blob/main/java/src/main/java/com/structurizr/example/bigbankplc/InternetBankingSystem.java) for the code, and [https://structurizr.com/share/36141/diagrams#Containers](https://structurizr.com/share/36141/diagrams#Containers) for the diagram.

docs/deployment-diagram.md

@@ -6,6 +6,6 @@ A deployment diagram allows you to illustrate how containers in the static model
 
 As an example, a Deployment diagram for the live environment of a simplified, fictional Internet Banking System might look something like this. In summary, it shows the deployment of the Web Application and the Database, with a secondary Database being used for failover purposes.
 
-![An example Deployment diagram](images/deployment-diagram-1.png)
+![An example Deployment diagram](https://static.structurizr.com/workspace/36141/diagrams/LiveDeployment.png)
 
 See [InternetBankingSystem.java](https://github.com/structurizr/examples/blob/main/java/src/main/java/com/structurizr/example/bigbankplc/InternetBankingSystem.java) for the code, and [https://structurizr.com/share/36141/diagrams#LiveDeployment](https://structurizr.com/share/36141/diagrams#LiveDeployment) for the diagram.

docs/dynamic-diagram.md

@@ -6,7 +6,7 @@ A simple dynamic diagram can be useful when you want to show how elements in a s
 
 As an example, a Dynamic diagram describing the customer sign in process for a simplified, fictional Internet Banking System might look something like this. In summary, it shows the components involved in the sign in process, and the interactions between them.
 
-![An example Dynamic diagram](images/dynamic-diagram-1.png)
+![An example Dynamic diagram](https://static.structurizr.com/workspace/36141/diagrams/SignIn.png)
 
 See [InternetBankingSystem.java](https://github.com/structurizr/examples/blob/main/java/src/main/java/com/structurizr/example/bigbankplc/InternetBankingSystem.java) for the code, and [https://structurizr.com/share/36141/diagrams#SignIn](https://structurizr.com/share/36141/diagrams#SignIn) for the diagram.