doc(onboarding): added conclusio

content/en/docs/project/onboarding/conclusio/README.md

@@ -0,0 +1,18 @@
+// how to create/export c4 images:
+// see also https://likec4.dev/tooling/cli/
+
+docker run -it --rm --name likec4 --user node -v $PWD:/app node bash
+npm install likec4
+exit
+
+docker commit likec4 likec4
+docker run -it --rm --user node -v $PWD:/app -p 5173:5173 likec4 bash
+
+// as root
+npx playwright install-deps 
+npx playwright install
+
+npm install likec4
+
+// render
+node@e20899c8046f:/app/content/en/docs/project/onboarding$ ./node_modules/.bin/likec4 export png -o ./images .

content/en/docs/project/onboarding/conclusio/_index.md

@@ -0,0 +1,17 @@
+---
+title: Conclusio
+weight: 1
+---
+
+## From Devops over Platform to Framework Engineering
+
+We come along from a quite well known, but already complex discipline called 'Platform Engineering', which is the next level devops. 
+On top of these two domains we now have 'Framework Engineering', i.e. buildung dynamic, orchestrated and reconciling platforms:
+
+|  |  |  |
+| -- | -- | -- |
+| <img src="./images/layers-and-platform-engineer.png" width="200"> |<img src="./images/layers.png" width="200"> | <img src="./images/layers-and-framework-engineer.png" width="200"> |
+
+## The whole picture of engineering
+
+<img src="./images/modern.png" width="600">

content/en/docs/project/onboarding/conclusio/domain-architecture.c4

@@ -0,0 +1,102 @@
+specification {
+    tag engineering
+    element domain
+    element engineer  {
+        style {
+            shape person
+        }
+    }
+}
+
+model {
+
+    engineer framework-engineer 'Framework Engineer' 'Build and maintain one platform orchestrating framework'{
+        style {
+            color: sky
+        }
+        -> framework-engineering
+        -> platform-engineer
+    }
+
+    domain framework-engineering 'Framework Engineering' 'Building and maintaining frameworks'{
+        #engineering
+        style {
+            color: sky
+        }
+        -> framework
+        -> platform-engineering
+    }
+
+    domain framework '"Framework" (IPCEI wording!)' 'A platform defining system' {
+        style {
+            color: sky
+        }
+        -> platform
+    }
+
+    engineer platform-engineer 'Platform Engineer'  {
+         style {
+            color: indigo
+        }
+        -> platform-engineering
+        -> devops-engineer
+    }
+
+    domain platform-engineering 'Platform Engineering' 'Building and maintaining platforms' {
+        #engineering
+        style {
+            color: indigo
+        }
+        -> platform
+        -> devops-engineering
+    }
+
+    domain platform 'Platform' 'A Devops defining system' {
+        style {
+            color: indigo
+        }
+        -> devops
+    }
+
+    engineer devops-engineer 'Devops Engineer'  {
+        style {
+            color: amber
+        }
+        -> devops-engineering
+    }
+
+    domain devops-engineering 'Devops Engineering' 'Building and maintaining devops means'  {
+        #engineering
+        style {
+            color: amber
+        }
+        -> devops
+    }
+    domain devops 'Devops' 'A software lifecycle enabling tool and process setup' {
+        style {
+            color: amber
+        }
+    }
+
+}
+
+views {
+    view modern {
+        title 'Modern Devops'
+        description 'Devops is abstarcted by Platforms, Platforms are abstracted by Frameworks (IPCEI wording!)'
+        include element.kind==domain, element.kind==engineer
+
+    }
+
+    view layers {
+        include devops, platform, framework
+    }
+
+    view layers-and-framework-engineer {
+        include devops, platform, framework, framework-engineering, framework-engineer
+    }
+
+    view layers-and-platform-engineer {
+        include devops, platform, platform-engineering, platform-engineer
+    }
+}