diff --git a/LIKEC4-QUICKSTART.md b/LIKEC4-QUICKSTART.md
new file mode 100644
index 0000000..38cc355
--- /dev/null
+++ b/LIKEC4-QUICKSTART.md
@@ -0,0 +1,112 @@
+# LikeC4 Integration - Quick Start
+
+Dieses Repository enthält jetzt die LikeC4-Architekturdokumentation aus edp-doc mit vollständiger Git-Historie.
+
+## Was wurde gemacht?
+
+1. ✅ **LikeC4-Modelle migriert** - `resources/likec4/` enthält alle C4-Modelle mit Git-Historie
+2. ✅ **Hugo-Integration erstellt** - CSS, JS und Loader-Scripte für Hugo/Docsy
+3. ✅ **Beispielseiten erstellt** - Dokumentation unter `content/en/docs/architecture/`
+4. ✅ **Konfiguration** - `hugo.toml` und Layout-Hooks konfiguriert
+
+## Nächste Schritte
+
+### 1. Webcomponent generieren
+
+```bash
+cd resources/likec4
+
+# Dependencies installieren (nur einmalig)
+npm install
+
+# Webcomponent generieren
+npx likec4 codegen webcomponent \
+ --webcomponent-prefix likec4 \
+ --outfile ../../static/js/likec4-webcomponent.js
+```
+
+Dies erzeugt `static/js/likec4-webcomponent.js` (~2-3 MB).
+
+### 2. Hugo Server starten
+
+```bash
+# Im Repository-Root
+hugo server -D
+
+# Öffne http://localhost:1313/docs/architecture/highlevelarch/
+```
+
+### 3. Änderungen committen
+
+```bash
+git add resources/likec4/
+git add static/
+git add layouts/
+git add content/en/docs/architecture/
+git add hugo.toml
+git commit -m "feat: integrate LikeC4 architecture documentation from edp-doc"
+```
+
+## Verfügbare Seiten
+
+- `/docs/architecture/` - Architektur-Übersicht
+- `/docs/architecture/highlevelarch/` - High-Level Architektur mit interaktivem Diagramm
+- `/docs/architecture/setup/` - Setup und Verwendungs-Anleitung
+
+## Workflow für Architektur-Änderungen
+
+1. **Modelle bearbeiten**: `.c4` Dateien in `resources/likec4/models/` oder `views/`
+2. **Vorschau**: `cd resources/likec4 && npx likec4 start` (öffnet http://localhost:5173)
+3. **Generieren**: Webcomponent neu generieren (siehe oben)
+4. **Testen**: Hugo Server starten und Seiten prüfen
+5. **Committen**: Sowohl `.c4` Dateien als auch `static/js/likec4-webcomponent.js`
+
+## Technische Details
+
+### Integration-Komponenten
+
+- `resources/likec4/` - LikeC4 Quellcode (migriert mit Git-Historie)
+- `static/js/likec4-loader.js` - Dynamischer Module Loader
+- `static/css/likec4-styles.css` - Styling inkl. Dark Mode
+- `layouts/partials/hooks/head-end.html` - Hugo Hook für JS/CSS Einbindung
+- `hugo.toml` - Konfiguration (`params.likec4.enable = true`)
+
+### Verwendung in Markdown
+
+```html
+
+
+
+
+ Loading architecture diagram...
+
+
+
+
+
+{{< alert title="Interactive Diagram" >}}
+The diagram above is interactive when viewed in a compatible browser.
+You can click on components to explore the architecture details.
+
+**Note:** The interactive diagram requires the LikeC4 webcomponent to be generated.
+See the [setup instructions]({{< ref "/docs/architecture/setup" >}}) for details.
+{{< /alert >}}
+
+## Architecture Overview
+
+The Enterprise Development Platform consists of several key components working together to provide a comprehensive development and deployment environment.
+
+### Key Components
+
+1. **OTC Foundry** - Central management and orchestration layer
+2. **Per-Tenant EDP** - Isolated development environments for each tenant
+3. **FaaS Environment** - Function-as-a-Service deployment targets on Open Telekom Cloud
+4. **Cloud Services** - Managed services including databases, storage, and monitoring
+
+### Deployment Environments
+
+- **Development Environment** (`*.t09.de`) - For platform team development and testing
+- **Production Environment** (`*.buildth.ing`) - For production workloads and tenant services
+
+## Component Details
+
+The interactive diagram above shows the relationships between different components and how they interact within the system architecture. You can explore the diagram by clicking on different elements to see more details.
+
+### Infrastructure Components
+
+- **Kubernetes Clusters** - Container orchestration using OTC CCE (Cloud Container Engine)
+- **ArgoCD** - GitOps continuous deployment and application lifecycle management
+- **Forgejo** - Git repository management and CI/CD pipelines
+- **Observability Stack** - Monitoring (Prometheus, Grafana), logging (Loki), and alerting
+
+### Security and Management
+
+- **Keycloak** - Identity and access management (IAM)
+- **OpenBao** - Secrets management (Hashicorp Vault fork)
+- **External Secrets Operator** - Kubernetes secrets integration
+- **Crossplane** - Infrastructure as Code and cloud resource provisioning
+
+### Developer Experience
+
+- **Backstage** - Internal developer portal and service catalog
+- **Forgejo Actions** - CI/CD pipeline execution
+- **Development Workflows** - GitOps-based inner and outer loop workflows
+
+## Setup and Maintenance
+
+To update or modify the architecture diagrams:
+
+1. Edit the `.c4` files in `resources/likec4/`
+2. Regenerate the webcomponent:
+
+ ```bash
+ cd resources/likec4
+ npx likec4 codegen webcomponent \
+ --webcomponent-prefix likec4 \
+ --outfile ../../static/js/likec4-webcomponent.js
+ ```
+
+3. Commit both the model changes and the regenerated JavaScript file
+
+For more information, see the [LikeC4 Integration Guide]({{< ref "/docs/architecture/setup" >}}).
diff --git a/content/en/docs/architecture/setup.md b/content/en/docs/architecture/setup.md
new file mode 100644
index 0000000..cc5a69d
--- /dev/null
+++ b/content/en/docs/architecture/setup.md
@@ -0,0 +1,291 @@
+---
+title: "LikeC4 Setup Guide"
+linkTitle: "Setup"
+weight: 10
+description: >
+ How to set up and use LikeC4 interactive architecture diagrams
+---
+
+This guide explains how to set up and use LikeC4 interactive architecture diagrams in this documentation.
+
+## Overview
+
+LikeC4 enables you to create interactive C4 architecture diagrams as code. The diagrams are defined in `.c4` files and compiled into a web component that can be embedded in any HTML page.
+
+## Prerequisites
+
+- Node.js (v18 or later)
+- npm or yarn
+
+## Initial Setup
+
+### 1. Install Dependencies
+
+Navigate to the LikeC4 directory and install dependencies:
+
+```bash
+cd resources/likec4
+npm install
+```
+
+### 2. Generate the Web Component
+
+Create the web component that Hugo will load:
+
+```bash
+npx likec4 codegen webcomponent \
+ --webcomponent-prefix likec4 \
+ --outfile ../../static/js/likec4-webcomponent.js
+```
+
+This command:
+- Reads all `.c4` files from `models/` and `views/`
+- Generates a single JavaScript file with all architecture views
+- Outputs to `static/js/likec4-webcomponent.js`
+
+### 3. Verify Integration
+
+The integration should already be configured in:
+
+- `hugo.toml` - Contains `params.likec4.enable = true`
+- `layouts/partials/hooks/head-end.html` - Loads CSS and loader script
+- `static/css/likec4-styles.css` - Diagram styling
+- `static/js/likec4-loader.js` - Dynamic module loader
+
+## Directory Structure
+
+```
+resources/likec4/
+├── models/ # C4 model definitions
+│ ├── components/ # Component models
+│ ├── containers/ # Container models
+│ ├── context/ # System context
+│ └── code/ # Code-level workflows
+├── views/ # View definitions
+│ ├── deployment/ # Deployment views
+│ ├── edp/ # EDP views
+│ ├── high-level-concept/ # Conceptual views
+│ └── dynamic/ # Process flows
+├── package.json # Dependencies
+└── INTEGRATION.md # Integration docs
+```
+
+## Using in Documentation
+
+### Basic Usage
+
+Add this to any Markdown file:
+
+```html
+