doc(solution): added design documentation structure and first proposal for agnostic EDF deployments

.vscode/settings.json

@@ -0,0 +1,22 @@
+{
+    "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"
+    },
+    "peacock.remoteColor": "#61dafb"
+}

content/en/docs/solution/design/_index.md

@@ -0,0 +1,7 @@
+---
+title: Design
+weight: 1
+description: Edge Developver Framework Design Documents
+---
+
+This design documentation structure is inspired by the [design of crossplane](https://github.com/crossplane/crossplane/tree/main/design#readme).

content/en/docs/solution/design/proposal-local-deployment.md

@@ -0,0 +1,23 @@
+---
+title: Agnostic EDF Deployment
+weight: 2
+description: The implementation of EDF must be kubernetes provider agnostic
+---
+
+* Type: Proposal
+* Owner: Stephan Lo (stephan.lo@telekom.de)
+* Reviewers: EDF Architects
+* Status: Speculative, revision 0.1
+
+## Background
+
+EDF is running as a controlplane - or let's say an orchestration plane, correct wording is still to be defined - in a kubernetes cluster.
+Right now we have at least ArgoCD as controller of manifests which we provide as CNOE stacks of packages and standalone packages.
+
+## Proposal
+
+The implementation of EDF must be kubernetes provider agnostic. Thus each provider specific deployment dependency must be factored out into provider specific definitions or deployment procedures.
+
+## Local deployment
+
+This implies that EDF must always be deployable into a local cluster, whereby by 'local' we mean a cluster which is under the full control of the platform engineer, e.g. a kind cluster on their laptop.