WiP statkeholder workshop

content/en/docs/project/intro-stakeholder-workshop/DevOps-Story.md

@@ -0,0 +1,45 @@
+---
+title: DevOps Story
+weight: 2
+description: The storyline of DevOps - why we need Platforms
+---
+
+
+## Platforms as the result of DevOps
+
+
+
+#### DevOps since 2010
+
+
+![alt text](DevOps-Lifecycle.jpg)
+
+
+```mermaid
+block-beta
+  columns 1
+  a["Platform-Orchestrating"] 
+  b["Platforming"]
+  c["DevOps"]
+  style a fill:yellow
+  style b fill:lightblue
+  style c fill:orange
+  
+```
+
+
+
+
+* Spotify
+* Airbnb
+* Zalando
+* Uber
+* Netflix
+* Salesforce
+* Google
+* Booking.com
+* Amazon
+* Autodesk
+* Adobe
+* Cisco
+*  ...

content/en/docs/project/intro-stakeholder-workshop/_index.md

@@ -0,0 +1,31 @@
+---
+title: Workshop Intro
+weight: 50
+description: Another overall eDF introduction for stakeholders
+---
+
+
+> This section is derived from [conceptual-onboarding-intro](../conceptual-onboarding/1_intro/)
+
+## Edge Developer Framework Solution Overview
+
+1. We have the ['Edge Developer Framework'](./edgel-developer-framework/). \
+  In short the mission is:
+    * Build a european edge cloud IPCEI-CIS
+    * which contains typical layers infrastructure, platform, application
+    * and on top has a new layer 'developer platform'
+    * which delivers a **cutting edge developer experience** and enables **easy deploying** of applications onto the IPCEI-CIS
+2. We think the solution for EDF is in relation to ['Platforming' (Digital Platforms)](./platforming/)
+    1. The next evolution after DevOps
+    2. Gartner predicts 80% of SWE companies to have platforms in 2026
+    3. Platforms have a history since roundabout 2019
+    4. CNCF has a working group which created capabilities and a maturity model
+3. Platforms evolve - nowadys there are [Platform Orchestrators](./orchestrators/)
+    1. Humanitec set up a Reference Architecture
+    2. There is this 'Orchestrator' thing - declaratively describe, customize and change platforms!
+4. Mapping our assumptions to the [CNOE solution](./cnoe/)
+    1. CNOE is a hot candidate to help and fulfill our platform building
+    2. CNOE aims to embrace change and customization!
+
+
+![alt text](DevOps-Lifecycle-1.jpg)

content/en/docs/project/intro-stakeholder-workshop/devops-layers.c4

@@ -0,0 +1,31 @@
+specification {
+    element layer
+    tag devopstag
+}
+
+model {
+    layer orchestrationlayer "Platform-Orchestration" {
+        #devopstag
+        style {
+            color amber
+        }
+    }
+    layer platformlayer "Platforming" {
+        #devopstag
+        style {
+            color indigo
+        }
+    }
+    layer devopslayer "DevOps" {
+        #devopstag
+        style {
+            color sky
+        }
+    }
+}
+
+views {
+    view {
+        include * where tag == #devopstag
+    }
+}

content/en/docs/project/intro-stakeholder-workshop/eDF-Story.md

@@ -0,0 +1,29 @@
+---
+title: eDF Story
+weight: 1
+description: The storyline of the eDF solution - from requirements to the POC
+---
+
+> This section is derived from [conceptual-onboarding-intro](../conceptual-onboarding/1_intro/)
+
+## Edge Developer Framework Solution Overview
+
+1. We have the ['Edge Developer Framework'](./edgel-developer-framework/). \
+  In short the mission is:
+    * Build a european edge cloud IPCEI-CIS
+    * which contains typical layers infrastructure, platform, application
+    * and on top has a new layer 'developer platform'
+    * which delivers a **cutting edge developer experience** and enables **easy deploying** of applications onto the IPCEI-CIS
+2. We think the solution for EDF is in relation to ['Platforming' (Digital Platforms)](./platforming/)
+    1. The next evolution after DevOps
+    2. Gartner predicts 80% of SWE companies to have platforms in 2026
+    3. Platforms have a history since roundabout 2019
+    4. CNCF has a working group which created capabilities and a maturity model
+3. Platforms evolve - nowadys there are [Platform Orchestrators](./orchestrators/)
+    1. Humanitec set up a Reference Architecture
+    2. There is this 'Orchestrator' thing - declaratively describe, customize and change platforms!
+4. Mapping our assumptions to the [CNOE solution](./cnoe/)
+    1. CNOE is a hot candidate to help and fulfill our platform building
+    2. CNOE aims to embrace change and customization!
+
+