docs(graphics): update placeholders

camunda · Dec 10, 2024 · c30e59e · c30e59e
1 parent bf55326
commit c30e59e
Show file tree

Hide file tree

Showing 13 changed files with 15 additions and 13 deletions.
diff --git a/docs/self-managed/reference-architecture/img/management-cluster.jpg b/docs/self-managed/reference-architecture/img/management-cluster.jpg
diff --git a/docs/self-managed/reference-architecture/img/orchestration-cluster.jpg b/docs/self-managed/reference-architecture/img/orchestration-cluster.jpg
diff --git a/docs/self-managed/reference-architecture/img/placeholder.png b/docs/self-managed/reference-architecture/img/placeholder.png
diff --git a/docs/self-managed/reference-architecture/manual/aws-ec2.md b/docs/self-managed/reference-architecture/manual/aws-ec2.md
@@ -22,13 +22,11 @@ Following this guide will incur costs on your Cloud provider account, namely for
 
 The architecture as depicted focuses on a standard deployment consisting of a three-node setup distributed over 3 [availability zones](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/using-regions-availability-zones.html) within an AWS region, as well as an OpenSearch domain with the same conditions. The focus is on a highly available setup and redundancy in case a zone should fail.
 
-<!--
-  The diagram can be found in the folder (InfraEx - Arch - AWS)
-  https://drive.google.com/drive/u/0/folders/1-4mLeGDSw8i10wfLo32AQAG4ynJFwT99
-  https://drive.google.com/file/d/1TA0EDhZYmnpq9kM5L6u9oftndaCQoDD0/view?usp=sharing
--->
+<!-- The following diagram should be exported as an image and as a PDF from the sources https://miro.com/app/board/uXjVL-6SrPc=/ --->
+<!-- To export: click on the frame > "Export Image" > as PDF and as JPG (low res), then save it in the ./assets/ folder --->
 
-![AWS EC2 Architecture](./img/aws-ec2-arch.png)
+_Infrastructure diagram for a 3 node EC2 architecture (click on the image to open the PDF version)_
+[![AWS EC2 Architecture](./img/aws-ec2-arch.jpg)](./img/aws-ec2-arch.pdf)
 
 The setup consists of:
 

diff --git a/docs/self-managed/reference-architecture/manual/img/aws-ec2-arch.jpg b/docs/self-managed/reference-architecture/manual/img/aws-ec2-arch.jpg
diff --git a/docs/self-managed/reference-architecture/manual/img/aws-ec2-arch.pdf b/docs/self-managed/reference-architecture/manual/img/aws-ec2-arch.pdf
diff --git a/docs/self-managed/reference-architecture/manual/img/aws-ec2-arch.png b/docs/self-managed/reference-architecture/manual/img/aws-ec2-arch.png
diff --git a/docs/self-managed/reference-architecture/manual/img/manual-ha.jpg b/docs/self-managed/reference-architecture/manual/img/manual-ha.jpg
diff --git a/docs/self-managed/reference-architecture/manual/img/manual-single.jpg b/docs/self-managed/reference-architecture/manual/img/manual-single.jpg
diff --git a/...self-managed/reference-architecture/manual/img/placeholder-manual-ha.drawio.png b/...self-managed/reference-architecture/manual/img/placeholder-manual-ha.drawio.png
diff --git a/...-managed/reference-architecture/manual/img/placeholder-manual-single.drawio.png b/...-managed/reference-architecture/manual/img/placeholder-manual-single.drawio.png
diff --git a/docs/self-managed/reference-architecture/manual/manual-overview.md b/docs/self-managed/reference-architecture/manual/manual-overview.md
@@ -23,7 +23,7 @@ This section of the Camunda Deployment Reference Architectures provides guidance
 
 Other deployment options, such as containerized deployments or managed services, might offer more convenience and automation. However, VM based deployment gives you the flexibility to tailor the deployment to your exact needs, which can be beneficial for regualted or highly customized environments.
 
-For documentation on the orchestration cluster, Web Modeler and Console separation, refer to  [the documentation](/self-managed/reference-architecture/reference-architecture.md#orchestration-cluster-vs-web-modeler-and-console)
+For documentation on the orchestration cluster, Web Modeler and Console separation, refer to [the documentation](/self-managed/reference-architecture/reference-architecture.md#orchestration-cluster-vs-web-modeler-and-console)
 
 ## Reference implementations
 
@@ -43,9 +43,7 @@ Before you begin with the self-managed single JAR setup, please consider the com
 
 ## Architecture
 
-<!-- TODO: switch placeholder pictures to the new miro approach of Léo -->
-
-![Single JAR](./img/placeholder-manual-single.drawio.png)
+![Single JAR](./img/manual-single.jpg)
 
 This above diagram illustrates a single-machine deployment using the single JAR package. While simple and effective for lightweight setups, scaling to multiple machines requires careful planning.
 
@@ -59,7 +57,7 @@ When scaling from a single machine to multiple machine, ensure that the `Optimiz
 
 ### High availability (HA)
 
-![HA JAR](./img/placeholder-manual-ha.drawio.png)
+![HA JAR](./img/manual-ha.jpg)
 
 For high availability, a minimum of three machines is recommended to ensure fault tolerance and enable master election in case of failures. Refer to the [clustering chapter](/components/zeebe/technical-concepts/clustering.md) to learn more about the raft protocol and clustering concepts.
 

diff --git a/docs/self-managed/reference-architecture/reference-architecture.md b/docs/self-managed/reference-architecture/reference-architecture.md
@@ -31,7 +31,13 @@ We recognize that deviations from the reference architecture are unavoidable. Ho
 
 <!-- TODO: include the overview that Andrey has done -->
 
-![Camunda Architecture](./img/placeholder.png)
+### Orchestration Cluster
+
+![Orchestration Cluster](./img/orchestration-cluster.jpg)
+
+### Web Modeler and Console
+
+![Web Modeler and Console](./img/management-cluster.jpg)
 
 ### Orchestration Cluster vs Web Modeler and Console
 
@@ -46,7 +52,7 @@ The included components are:
 - [Zeebe](/components/zeebe/zeebe-overview.md): A workflow engine for orchestrating microservices and managing stateful, long-running business processes.
 - [Operate](/components/operate/operate-introduction.md): A monitoring tool for visualizing and troubleshooting workflows running in Zeebe.
 - [Tasklist](/components/tasklist/introduction-to-tasklist.md): A user interface for managing and completing human tasks within workflows.
-- [Optimize](#TODO): An analytics tool for generating reports and insights based on workflow data.
+- [Optimize]($optimize$/components/what-is-optimize/): An analytics tool for generating reports and insights based on workflow data.
 - [Identity](/self-managed/identity/what-is-identity.md): A service for managing user authentication and authorization.
 - [Connectors](/components/connectors/introduction.md): Pre-built integrations for connecting Zeebe with external systems and services.