Merge branch 'development' into likec4

.gitignore

@@ -0,0 +1 @@
+node_modules

docs/technical-documentation/.pages

@@ -0,0 +1,6 @@
+title: Technical doc
+arrange:
+  - concepts
+  - architecture
+  - product
+  - project

docs/technical-documentation/concepts/.pages

@@ -0,0 +1,6 @@
+title: Concepts
+arrange:
+  - overview.md
+  - general
+  - customer-developer
+  - edp-developer

docs/technical-documentation/concepts/edp-developer/.pages

@@ -0,0 +1,10 @@
+title: edgeDeveloper Framework
+arrange:
+  - storyline.md
+  - introduction.md
+  - edge-developer-framework.md
+  - platforming.md
+  - orchestrators.md
+  - cnoe.md
+  - cnoe-showtime.md
+  - conclusio.md

docs/technical-documentation/concepts/edp-developer/orchestrators.md

@@ -6,7 +6,8 @@ description: Next level platforming is orchestrating platforms
 
 ## Summary
 
-When defining and setting up platforms next two intrinsic problems arise: 
+When defining and setting up platforms next two intrinsic problems arise:
+
 1. it is not declarative and automated
 2. it is not or least not easily changable
 
@@ -21,7 +22,7 @@ This is something extremely new since late 2023 - the rise of the automation of
 
 It was Humanitec creating a definition of platform architecture, as they needed to defien what they are building with their 'orchestrator':
 
-<img src="./vendor-neutral-idp-final.gif" width="600" alt="https://developer.humanitec.com/introduction/overview/">
+![https://developer.humanitec.com/introduction/overview/](./4_orchestrators/vendor-neutral-idp-final.gif)
 
 ## Declarative Platform Orchestration
 
@@ -29,16 +30,13 @@ Based on the refence architecture you next can build - or let's say 'orchestrate
 
 https://humanitec.com/reference-architectures
 
-<img src="./platform-architectures.webp" width="600" alt="https://humanitec.com/blog/aws-azure-and-gcp-open-source-reference-architectures-to-start-your-mvp">
+
+![https://humanitec.com/blog/aws-azure-and-gcp-open-source-reference-architectures-to-start-your-mvp](./4_orchestrators/platform-architectures.webp)
 
 > Hint: There is a [slides tool provided by McKinsey](https://platformengineering.org/blog/create-your-own-platform-engineering-reference-architectures) to set up your own platform deign based on the reference architecture 
 
-
-{{% pageinfo color="info" %}}
-### What comes next?
-
-[Next](../cnoe/) we'll see how we are going to do platform orchestration with CNOE!
-{{% /pageinfo %}}
+> What comes next?
+> [Next](./cnoe.md) we'll see how we are going to do platform orchestration with CNOE!
 
 ## Addendum
 
@@ -46,6 +44,4 @@ https://humanitec.com/reference-architectures
 
 You remember the [capability mappings from the time before orchestration](../platforming)? Here we have a [similar setup based on Humanitecs platform engineering status ewhite paper](https://humanitec.com/whitepapers/state-of-platform-engineering-report-volume-2):
 
-<img src="./platform-tooling-humanitec-platform-report-2024.PNG" width="600" alt="https://humanitec.com/whitepapers/state-of-platform-engineering-report-volume-2 Whitepaper_ State of Platform Engineering Report.pdf">
-
-
+![https://humanitec.com/whitepapers/state-of-platform-engineering-report-volume-2 Whitepaper_ State of Platform Engineering Report.pdf](./4_orchestrators/platform-tooling-humanitec-platform-report-2024.PNG)

docs/technical-documentation/concepts/edp-developer/platforming.md

@@ -18,7 +18,7 @@ Let's start with a look into the history of platform engineering. A good startin
 
 They create lots of [beautiful articles and insights](https://humanitec.com/blog), their own [platform products](https://humanitec.com/products/) and [basic concepts for the platform architecture](https://humanitec.com/platform-engineering) (we'll meet this later on!).
 
-<img src="./humanitec-history.png" width="600" alt="https://platformengineering.org/blog/the-story-of-platform-engineering">
+<img src="./3_platforming/humanitec-history.png" width="600" alt="https://platformengineering.org/blog/the-story-of-platform-engineering">
 
 
 ### Further nice reference to the raise of platforms
@@ -41,7 +41,7 @@ When looking at these 'capabilities', we have CNCF itself:
 
 There is a CNCF working group which provides the definition of [Capabilities of platforms](https://tag-app-delivery.cncf.io/whitepapers/platforms/#capabilities-of-platforms) and shows a first idea of the layered architecture of platforms as **service layer for developers** ("product and application teams"):
 
-<img src="./platforms-def.drawio.png" width="600">
+<img src="./3_platforming/platforms-def.drawio.png" width="600">
 
 
 > Important: As Platform engineer also notice the [platform-eng-maturity-model](https://tag-app-delivery.cncf.io/whitepapers/platform-eng-maturity-model/)
@@ -50,7 +50,7 @@ There is a CNCF working group which provides the definition of [Capabilities of
 
 Or, in another illustration for the platform as a developer service interface, which also defines the **'Platform Engineering Team'** inbetween: 
 
-<img src="./platform-self-services.webp" width="600" alt="https://medium.com/@bijit211987/what-is-platform-engineering-and-how-it-reduce-cognitive-load-on-developers-ac7805603925">
+<img src="./3_platforming/platform-self-services.webp" width="600" alt="https://medium.com/@bijit211987/what-is-platform-engineering-and-how-it-reduce-cognitive-load-on-developers-ac7805603925">
 
 ## How to set up Platforms
 
@@ -77,7 +77,7 @@ Build or buy - this is also in pltaform engineering a tweaked discussion, which
 {{% pageinfo color="info" %}}
 ### What comes next?
 
-[Next](../orchestrators/) we'll see how these concepts got structured!
+[Next](./orchestrators.md) we'll see how these concepts got structured!
 {{% /pageinfo %}}
 
 ## Addendum

docs/technical-documentation/concepts/edp-developer/storyline.md

@@ -1,3 +1,11 @@
+---
+title: 'Storyline'
+linktitle: Conceptual Onboarding
+weight: 20
+description: How to conceptually onboard onto the Edge Developer Framework (EDF) requirements and the designed solution
+---
+
+# Platform 101: Conceptual Onboarding
 
 ## Storyline 
 
@@ -24,5 +32,3 @@
 3. Don't miss to further investigate and truely understand **CNOE solution**
 
 ## Architecture
-
-

docs/technical-documentation/concepts/general/_index.md

@@ -0,0 +1,7 @@
+---
+title: General Concepts
+weight: 1
+description: The underlying platforming concepts of the Edge Developer Framework (EDF) solution, i.e. the problem domain
+---
+
+The underlying platforming concepts of the Edge Developer Framework (EDF) solution, i.e. the problem domain

docs/technical-documentation/concepts/overview.md

@@ -1,7 +1,8 @@
 ---
-title: Concepts
+title: Overview
 weight: 1
 description: The underlying platforming concepts of the Edge Developer Framework (EDF) solution, i.e. the problem domain
 ---
 
+The underlying platforming concepts of the Edge Developer Framework (EDF) solution, i.e. the problem domain
 

docs/technical-documentation/product/_index.md

@@ -1,6 +1,7 @@
 ---
-title: Solution
+title: Overview
 weight: 2
 description: "The implemented platforming solutions of EDF, i.e. the solution domain. The documentation of all project output: Design, Building blocks, results, show cases, artifacts and so on"
 ---
 
+The implemented platforming solutions of EDF, i.e. the solution domain. The documentation of all project output: Design, Building blocks, results, show cases, artifacts and so on