refactor(technical-documentation): first itration finished. can be pushed as mkdocs-awesome-pages-plugin is now implemented in backstage-edp

docs/technical-documentation/.pages

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

docs/technical-documentation/concepts/.pages

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

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

@@ -5,3 +5,6 @@ arrange:
   - edge-developer-framework.md
   - platforming.md
   - orchestrators.md
+  - cnoe.md
+  - cnoe-showtime.md
+  - conclusio.md

docs/technical-documentation/concepts/edp-developer/7_conclusio/README.md

@@ -1,18 +0,0 @@
-// 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 .

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="./4_orchestrators/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/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

docs/technical-documentation/product/operations/_index.md

@@ -1,6 +0,0 @@
----
-title: Scenarios
-weight: 1
-description: Usage scenarios and system architecture
----
-

docs/technical-documentation/project/_index.md

@@ -1,6 +1,7 @@
 ---
-title: Project
+title: Overview
 weight: 5
 description: How we organize work and proceed as team, which decisions we made, what outputs and outcomes we have
 ---
 
+How we organize work and proceed as team, which decisions we made, what outputs and outcomes we have

likec4/README.md

@@ -1 +1,24 @@
-Run ´npx likec4 start´ to start dev server
+# LikeC4 architecture documentation
+
+Run `npx likec4 start` to start dev server
+
+## with docker and how to render/export images
+
+// 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 .