refactor(ipceicis-460-cnoe-deep-dive): project level documentation refoctored

content/en/docs/project/_index.md

@@ -1,45 +1,6 @@
 ---
 title: Project
 weight: 5
+description: How we organize work and proceed as team, which decisions we made, what outputs and outcomes we have
 ---
 
-Here we document organisation, vision, plan, outcomes of the IPCEI-CIS Developer Platform project.
-
-## First Blue Print in 2024 
-
-Our first architectural blue print for the IPCEI-CIS Developer Framework derives from Humanitecs Reference Architecture, see links in [Blog](../../blog/240823-archsession.md)
-
-![alt text](image-2024-8-14_10-50-27.png)
-
-## C4 Model
-
-> (sources see in ./ressources/architecture-c4)
-
-> How to use: install C4lite VSC exension and/or C4lite cli - then open *.c4 files in ./ressources/architecture-c4
-
-First system landscape C4 model:
-
-![c4-model](./planes.png)
-
-## In Confluence
-
-https://confluence.telekom-mms.com/display/IPCEICIS/Architecture
-
-
-## Dimensionierung Cloud für initiales DevFramework
-
-### 28.08.24, Stefan Bethle, Florian Fürstenberg, Stephan Lo
-
-1) zuerst viele DevFrameworkPlatformEngineers arbeiten lokal, mit zentralem Deployment nach OTC in **einen/max zwei** Control-Cluster
-2) wir gehen anfangs von ca. 5 clustern aus
-3) jeder cluster mit 3 Knoten/VM (in drei AvailabilityZones)
-4) pro VM 4 CPU, 16 GB Ram, 50 GB Storage read/write once, PVCs 'ohne limit'
-5) public IPs, plus Loadbalancer
-6) Keycloak vorhanden
-7) Wildcard Domain ?? --> Eher ja
-
-Next Steps: (Vorschlag: in den nächsten 2 Wochen)
-1. Florian spezifiziert an Tobias
-2. Tobias stellt bereit, kubeconfig kommt an uns
-3. wir deployen
-

content/en/docs/project/conceptual-onboarding/1_intro/_index.md

@@ -1,10 +1,9 @@
 ---
-title: Onboarding
+title: Introduction
 weight: 1
+description: The 5-step storyflow of this Onboarding chapter
 ---
 
-
-
 {{% pageinfo color="info" %}}
 ## Summary
 

content/en/docs/project/conceptual-onboarding/2_edge-developer-framework/_index.md

@@ -1,6 +1,7 @@
 ---
 title: Edge Developer Framework
-weight: 1
+weight: 2
+description: Driving requirements for a platform
 ---
 
 {{% pageinfo color="info" %}}

content/en/docs/project/conceptual-onboarding/3_platforming/_index.md

@@ -1,7 +1,8 @@
 ---
 title: Platform Engineering aka Platforming
 linktitle: Platforming
-weight: 2
+weight: 3
+description: DevOps is dead - long live next level DevOps in platforms
 ---
 
 
@@ -10,7 +11,7 @@ weight: 2
 
 Since 2010 we have DevOps. This brings increasing delivery speed and efficiency at scale. 
 But next we got high 'cognitive loads' for developers and production congestion due to engineering lifecycle complexity. 
-So we need on top of DevOps an instrumentation to ensure and enforce speed, quality, security in modern, cloud native software development. This instrumentation is called 'goldne paths' in intenal develoepr platforms (IDP).
+So we need on top of DevOps an instrumentation to ensure and enforce speed, quality, security in modern, cloud native software development. This instrumentation is called 'golden paths' in intenal develoepr platforms (IDP).
 {{% /pageinfo %}}
 
 

content/en/docs/project/conceptual-onboarding/4_orchestrators/_index.md

@@ -1,6 +1,7 @@
 ---
 title: Orchestrators
-weight: 10
+weight: 4
+description: Next level platforming is orchestrating platforms
 ---
 
 {{% pageinfo color="info" %}}

content/en/docs/project/conceptual-onboarding/5_cnoe/_index.md

@@ -1,6 +1,7 @@
 ---
 title: CNOE
-weight: 20
+weight: 5
+description: Our top candidate for a platform orchestrator
 ---
 
 {{% pageinfo color="info" %}}

content/en/docs/project/conceptual-onboarding/6_cnoe-showtime/_index.md

@@ -1,6 +1,7 @@
 ---
 title: CNOE Showtime
-weight: 50
+weight: 6
+description: CNOE hands on
 ---
 
 {{% pageinfo color="info" %}}

content/en/docs/project/conceptual-onboarding/7_conclusio/_index.md

@@ -1,6 +1,7 @@
 ---
 title: Conclusio
-weight: 100
+weight: 7
+description: 'Summary and final thoughts: Always challenge theses concepts, accumptions and claims!'
 ---
 
 {{% pageinfo color="info" %}}

content/en/docs/project/conceptual-onboarding/_index.md

@@ -0,0 +1,9 @@
+---
+title: 'Platform 101: Conceptual Onboarding '
+linktitle: Conceptual Onboarding
+weight: 20
+description: How to conceptually onboard onto the Edge Developer Framework (EDF) requirements and the designed solution
+---
+
+
+

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

@@ -0,0 +1,45 @@
+---
+title: Plan in 2024
+weight: 30
+description: The planned project workload in 2024
+---
+
+
+## First Blue Print in 2024 
+
+Our first architectural blue print for the IPCEI-CIS Developer Framework derives from Humanitecs Reference Architecture, see links in [Blog](../../blog/240823-archsession.md)
+
+![alt text](image-2024-8-14_10-50-27.png)
+
+## C4 Model
+
+> (sources see in ./ressources/architecture-c4)
+
+> How to use: install C4lite VSC exension and/or C4lite cli - then open *.c4 files in ./ressources/architecture-c4
+
+First system landscape C4 model:
+
+![c4-model](./planes.png)
+
+## In Confluence
+
+https://confluence.telekom-mms.com/display/IPCEICIS/Architecture
+
+
+## Dimensionierung Cloud für initiales DevFramework
+
+### 28.08.24, Stefan Betkle, Florian Fürstenberg, Stephan Lo
+
+1) zuerst viele DevFrameworkPlatformEngineers arbeiten lokal, mit zentralem Deployment nach OTC in **einen/max zwei** Control-Cluster
+2) wir gehen anfangs von ca. 5 clustern aus
+3) jeder cluster mit 3 Knoten/VM (in drei AvailabilityZones)
+4) pro VM 4 CPU, 16 GB Ram, 50 GB Storage read/write once, PVCs 'ohne limit'
+5) public IPs, plus Loadbalancer
+6) Keycloak vorhanden
+7) Wildcard Domain ?? --> Eher ja
+
+Next Steps: (Vorschlag: in den nächsten 2 Wochen)
+1. Florian spezifiziert an Tobias
+2. Tobias stellt bereit, kubeconfig kommt an uns
+3. wir deployen
+