doc(expert-workshop): WiP memo status until part 1 of day 2

.vscode/settings.json

@@ -1,3 +1,22 @@
 {
-    "peacock.remoteColor": "#61dafb"
+    "peacock.remoteColor": "#61dafb",
+    "workbench.colorCustomizations": {
+        "activityBar.activeBackground": "#93e6fc",
+        "activityBar.background": "#93e6fc",
+        "activityBar.foreground": "#15202b",
+        "activityBar.inactiveForeground": "#15202b99",
+        "activityBarBadge.background": "#fa45d4",
+        "activityBarBadge.foreground": "#15202b",
+        "commandCenter.border": "#15202b99",
+        "sash.hoverBorder": "#93e6fc",
+        "statusBar.background": "#61dafb",
+        "statusBar.foreground": "#15202b",
+        "statusBarItem.hoverBackground": "#2fcefa",
+        "statusBarItem.remoteBackground": "#61dafb",
+        "statusBarItem.remoteForeground": "#15202b",
+        "titleBar.activeBackground": "#61dafb",
+        "titleBar.activeForeground": "#15202b",
+        "titleBar.inactiveBackground": "#61dafb99",
+        "titleBar.inactiveForeground": "#15202b99"
+    }
 }

content/en/docs/project/expert-workshop-1/_index.md

@@ -0,0 +1,20 @@
+---
+title: Expert Workshop Intro
+weight: 50
+description: Researchinh platforms
+linktitle: Expert Workshop 1
+---
+
+
+## 11h15 Defining platform
+
+platform -> framework -> platform
+
+framework: instantiates the platfrom
+platform: what the custoemr uses
+
+reponsibilities for components
+
+think at the problems that matter - huge developer teams, daily problems, nor only project starting problems 
+
+e.g. billing component

content/en/docs/project/expert-workshop-1/memo.md

@@ -0,0 +1,5 @@
+
+
+## claims
+
+* you need to have developer pains

content/en/docs/project/plan-in-2024/poc/_index.md

@@ -13,3 +13,33 @@ The use cases/application lifecycle and deployment flow is drawn here: https://c
 
 
 ![alt text](./_assets/image-1.png)
+
+## day 2
+
+keynote, '8 jahre plattform development erfahrung'
+
+* gregor hohpe https://leanpub.com/platformstrategy
+* Platfrom examples
+    * NEO Thoughtworks, Backstage
+
+* dogfood discussion: DSS only 'some microservices', use your own product was not an aspect
+)Anm.: product vs. project discussion at lunch time was confusing)
+* Vision: also descope (don't only scope what you will do, also scope what you don't)
+* also bring business value
+* the user/developer doesn't care about the used components (like argo)
+
+* write down your decisions ('we use kubernetes this and thats why')
+* collect your assumptions and evaluate tehm
+
+* use security from beginning on ... least privilige pattern
+* agile threat modelling
+
+* good architecture: integrate / decide things which are expensive to change later
+
+* have a log of architectural decisions, think about security
+
+
+## 11h30 Kratix demo 
+
+1) set up kratix with shell scripts, managment cluster, worker cluster build with terraform
+2) set up promise (capability to provide)