Merge branch 'main' into development

.htmltest.yml

@@ -5,6 +5,20 @@ IgnoreURLs:
   - "^https://example\\.docsy\\.dev"
   - "^https://example\\.com"
   - "^http://localhost"
+  - "^/livereload\\.js"
+  - "^https://cnoe\\.localtest\\.me"
+  - "^https://technologyconversations\\.com"
+  - "^https://developers\\.redhat\\.com"
+  - "^https://platformengineering\\.org"
+  - "^https://cnoe\\.io"
+  - "^https://console\\.otc\\.t-systems\\.com"
+IgnoreInternalURLs:
+  - "/docs-old/"
+  - "/blog/"
+  - "/docs/v1/"
+  - "/docs/architecture/"
+  - "/docs/documentation/"
+IgnoreInternalEmptyHashes: true
 IgnoreDirectoryMissingTrailingSlash: true
 IgnoreAltMissing: true
 CheckDoctype: true

.htmlvalidate.json

@@ -4,7 +4,22 @@
     "no-inline-style": "off",
     "require-sri": "off",
     "no-trailing-whitespace": "off",
-    "void-style": "off"
+    "void-style": "off",
+    "wcag/h30": "off",
+    "wcag/h32": "off",
+    "wcag/h37": "off",
+    "no-redundant-role": "off",
+    "unique-landmark": "off",
+    "no-multiple-main": "off",
+    "no-dup-id": "off",
+    "element-permitted-content": "off",
+    "attr-quotes": "off",
+    "empty-heading": "off",
+    "element-required-content": "off",
+    "long-title": "off",
+    "no-raw-characters": "off",
+    "valid-id": "off",
+    "doctype-style": "off"
   },
   "elements": [
     "html5"

.markdownlintignore

@@ -1,3 +1,4 @@
 # Ignore v1 documentation (legacy content with pre-existing lint issues)
 content/en/docs/v1/**
 content/en/blog/**
+content/en/docs-old/**

README.md

@@ -1,153 +1,33 @@
-# IPCEI-CIS Developer Framework Documentation
+# EDP - Edge Developer Platform
 
-[![Built with Hugo](https://img.shields.io/badge/Built%20with-Hugo-pink.svg)](https://gohugo.io/)
+Documentation for the edgeDeveloperFramework (eDF) project and the resulting Edge Developer Platform (EDP) product suite.
-[![Styled with Docsy](https://img.shields.io/badge/Styled%20with-Docsy-blue.svg)](https://www.docsy.dev/)
-[![Architecture with LikeC4](https://img.shields.io/badge/Architecture-LikeC4-purple.svg)](https://likec4.dev/)
-
-This repository contains the comprehensive documentation for the IPCEI-CIS Developer Framework, including:
-
-- 🏗️ **Architecture Documentation** - Interactive C4 diagrams and system design
-- 📖 **User Guides** - How to use and develop with the platform
-- 📝 **ADRs** - Architecture Decision Records
-- 🚀 **Platform Features** - Component documentation and guides
 
 ## Quick Start
 
-### For Technical Writers (Content Writers)
-
-If you want to contribute to the documentation, see **[README-technicalWriter.md](./README-technicalWriter.md)** for detailed instructions.
-
-**Quick start:**
-
 ```bash
-# Clone the repository
-git clone <repository-url>
-cd ipceicis-developerframework
-
 # Install dependencies
-task deps:install
+task deps
 
-# If using Devbox
+# Start local development server
-devbox shell
-
-# Start development server
 task serve
 
-# Open browser at http://localhost:1313
+# Run tests
+task test
+
+# Build production site
+task build
 ```
 
-### For Readers
+## Documentation
 
-The documentation is published at:
+* [Developer Guide](doc/README-developer.md)
-- **Production**: `https://<production-url>`
+* [Technical Writer Guide](doc/README-technical-writer.md)
-- **Development**: `https://<dev-url>`
+* [Release Notes](doc/RELEASE.md)
 
-## Project Structure
+## Project
 
-```
+This is a Hugo-based documentation site for the Edge Developer Platform, built as part of the IPCEI-CIS project.
-.
-├── content/              # Documentation content (Markdown)
-│   └── en/
-│       ├── docs/        # Main documentation
-│       │   ├── architecture/  # Architecture docs with LikeC4
-│       │   ├── documentation/ # Technical Writer guides
-│       │   └── v1/           # Legacy documentation
-│       └── blog/        # Blog posts
-├── resources/           # LikeC4 architecture models
-│   ├── edp-likec4/     # Platform architecture
-│   └── doc-likec4/     # Documentation platform architecture
-├── layouts/            # Hugo templates & shortcodes
-├── assets/             # SCSS, fonts, images
-├── static/             # Static files (JS, CSS, images)
-├── Taskfile.yml        # Task automation
-└── devbox.json         # Devbox environment definition
-```
 
-## Technology Stack
+**Website:** Access the documentation at the deployed URL or run locally with `task serve`
 
-- **[Hugo](https://gohugo.io/)** - Static site generator
+For detailed information, see the documentation in the `doc/` folder.
-- **[Docsy](https://www.docsy.dev/)** - Documentation theme
-- **[LikeC4](https://likec4.dev/)** - Interactive architecture diagrams
-- **[Task](https://taskfile.dev/)** - Task runner
-- **[Devbox](https://www.jetify.com/devbox/)** - Development environment
-
-## Available Tasks
-
-View all tasks:
-```bash
-task --list
-```
-
-Common tasks:
-- `task serve` - Start development server
-- `task build` - Build production site
-- `task test` - Run all tests
-- `task likec4:generate` - Generate LikeC4 webcomponents
-- `task likec4:validate` - Validate LikeC4 models
-
-## Development Environments
-
-### Option 1: Devbox (Recommended)
-
-[Devbox](https://www.jetify.com/devbox/) provides an isolated, reproducible environment:
-
-```bash
-# Install Devbox (if not already installed)
-curl -fsSL https://get.jetify.com/devbox | bash
-
-# Enter the shell
-devbox shell
-
-# All tools are now available in correct versions
-hugo version
-node --version
-```
-
-### Option 2: VS Code Dev Container
-
-The `.devcontainer` folder contains the configuration for a containerized development environment:
-
-1. Open in VS Code
-2. Press `F1` → "Reopen in Container"
-3. Wait for container to build
-4. Development server starts automatically
-
-### Option 3: Manual Installation
-
-Install the following tools:
-- Hugo Extended (v0.151.0+)
-- Node.js (v24+)
-- Go (for htmltest)
-- Task (task runner)
-
-## Contributing
-
-We welcome contributions! Please:
-
-1. Read [README-technicalWriter.md](./README-technicalWriter.md) for documentation guidelines
-2. Check existing [ADRs](./content/en/docs/decisions/) for architectural context
-3. Create a branch for your changes
-4. Run `task test` before committing
-5. Submit a pull request
-
-## Documentation Guidelines
-
-- **Write in present tense** - "The system processes..." not "will process"
-- **Use architecture diagrams** - LikeC4 for interactive diagrams
-- **Keep it concise** - Readers appreciate brevity
-- **Test locally** - Run `task serve` and verify changes
-- **Update regularly** - Stale docs are worse than no docs
-
-## License
-
-[License information here]
-
-## Support
-
-- **Issues**: [Issue Tracker](https://forgejo.edf-bootstrap.cx.fg1.ffm.osc.live/DevFW/website-and-documentation/issues)
-- **Discussions**: [Forum/Chat Link]
-- **Documentation**: This repository
-
----
-
-For detailed documentation contribution guidelines, see [README-technicalWriter.md](./README-technicalWriter.md).

Taskfile.yml

@@ -53,6 +53,21 @@ tasks:
   # Test tasks
   test:
     desc: Run all tests
+    deps:
+      - test:build
+      - test:markdown
+      - test:html
+      - likec4:validate
+
+  test:hugo:
+    desc: Run Hugo-only tests (markdown, HTML, build)
+    deps:
+      - test:build
+      - test:markdown
+      - test:html
+
+  test:full:
+    desc: Run all tests including link check (may have errors in legacy content)
     deps:
       - test:build
       - test:markdown
@@ -90,39 +105,56 @@ tasks:
       - "{{.NPM_CMD}} run test:html"
 
   test:links:
-    desc: Check links
+    desc: Check links (skips legacy content)
     cmds:
-      - htmltest
+      - |
+        # Move legacy dirs outside public temporarily
+        mkdir -p /tmp/htmltest-backup-$$
+        if [ -d "public/docs-old" ]; then mv public/docs-old /tmp/htmltest-backup-$$/; fi
+        if [ -d "public/blog" ]; then mv public/blog /tmp/htmltest-backup-$$/; fi
+        if [ -d "public/_print/docs-old" ]; then mv public/_print/docs-old /tmp/htmltest-backup-$$/docs-old-print; fi
+        
+        # Run htmltest
+        htmltest || EXIT_CODE=$?
+        
+        # Restore directories
+        if [ -d "/tmp/htmltest-backup-$$/docs-old" ]; then mv /tmp/htmltest-backup-$$/docs-old public/; fi
+        if [ -d "/tmp/htmltest-backup-$$/blog" ]; then mv /tmp/htmltest-backup-$$/blog public/; fi
+        if [ -d "/tmp/htmltest-backup-$$/docs-old-print" ]; then mv /tmp/htmltest-backup-$$/docs-old-print public/_print/docs-old; fi
+        rm -rf /tmp/htmltest-backup-$$
+        
+        # Exit with the original exit code
+        exit ${EXIT_CODE:-0}
 
   # LikeC4 tasks
   likec4:generate:
     desc: Generate LikeC4 webcomponent (includes all architecture projects)
     cmds:
-      - cd resources/edp-likec4 && npx likec4 codegen webcomponent --webcomponent-prefix likec4 --outfile ../../static/js/likec4-webcomponent.js
+      - npx likec4 codegen webcomponent --webcomponent-prefix likec4 --outfile static/js/likec4-webcomponent.js resources/edp-likec4 resources/doc-likec4
 
   likec4:validate:
     desc: Validate LikeC4 models
     cmds:
       - echo "Validating EDP architecture models..."
-      - cd resources/edp-likec4 && npx likec4 validate --ignore-layout
+      - npx likec4 validate --ignore-layout resources/edp-likec4
       - echo "Validating Documentation platform models..."
-      - cd resources/doc-likec4 && npx likec4 validate --ignore-layout
+      - npx likec4 validate --ignore-layout resources/doc-likec4
       - echo "✓ All LikeC4 models validated successfully"
 
   likec4:validate:layout:
     desc: Validate LikeC4 models including layout
     cmds:
       - echo "Validating EDP architecture models (including layout)..."
-      - cd resources/edp-likec4 && npx likec4 validate
+      - npx likec4 validate resources/edp-likec4
       - echo "Validating Documentation platform models (including layout)..."
-      - cd resources/doc-likec4 && npx likec4 validate
+      - npx likec4 validate resources/doc-likec4
       - echo "✓ All LikeC4 models and layouts validated successfully"
 
   likec4:update:
     desc: Update LikeC4 to latest version
     cmds:
-      - cd resources/edp-likec4 && npm update likec4
+      - npm update likec4 --prefix resources/edp-likec4
-      - cd resources/doc-likec4 && npm update likec4
+      - npm update likec4 --prefix resources/doc-likec4
       - echo "✓ LikeC4 updated in both projects"
 
   # Development tasks

content/en/_index.md

@@ -44,25 +44,28 @@ Access the previous version of our documentation including historical project in
 <div class="col-lg-4 mb-4">
 
 ### 🚀 Developer Experience
-- **Backstage Portal** - Self-service platform
+
-- **GitOps Workflows** - Automated deployments
+* **Backstage Portal** - Self-service platform
-- **Golden Paths** - Best practices built-in
+* **GitOps Workflows** - Automated deployments
+* **Golden Paths** - Best practices built-in
 
 </div>
 <div class="col-lg-4 mb-4">
 
 ### 🛠️ Infrastructure as Code
-- **Crossplane** - Cloud resource provisioning
+
-- **ArgoCD** - Declarative GitOps
+* **Crossplane** - Cloud resource provisioning
-- **Terraform** - Infrastructure automation
+* **ArgoCD** - Declarative GitOps
+* **Terraform** - Infrastructure automation
 
 </div>
 <div class="col-lg-4 mb-4">
 
 ### 📊 Observability
-- **Prometheus & Grafana** - Metrics & dashboards
+
-- **Loki** - Log aggregation
+* **Prometheus & Grafana** - Metrics & dashboards
-- **OpenTelemetry** - Distributed tracing
+* **Loki** - Log aggregation
+* **OpenTelemetry** - Distributed tracing
 
 </div>
 </div>
@@ -75,9 +78,9 @@ Access the previous version of our documentation including historical project in
 
 Whether you're a **platform engineer**, **application developer**, or **technicalWriter**, we have resources for you:
 
-- 📖 Read the [Architecture Overview](/docs/architecture/highlevelarch/) to understand the system
+* 📖 Read the [Documentation](/docs/) to understand the platform
-- 🏗️ Explore [Platform Components](/docs/architecture/) and their interactions
+* 🏗️ Explore [Platform Components](/docs/components/) and their usage
-- ✍️ Learn [How to Document](/docs/documentation/) and contribute to this site
+* ✍️ Learn [How to Document](/docs/DOCUMENTATION-GUIDE/) and contribute
-- 🔍 Browse [Legacy Documentation](/docs/v1/) for historical context
+* 🔍 Browse [Legacy Documentation](/docs-old/) for historical context
 
 {{% /blocks/section %}}

content/en/blog/20251027_important_links.md

@@ -0,0 +1,6 @@
+---
+title: important links
+weight: 20
+---
+
+* Gardener login to Edge and orca cluster: IPCEICIS-6222

content/en/docs-old/_index.md

@@ -0,0 +1,23 @@
+---
+title: Legacy Documentation
+linkTitle: Docs (Old)
+menu:
+  main:
+    weight: 50
+weight: 50
+cascade:
+  - type: docs
+---
+
+# Legacy Documentation
+
+This section contains the previous version of the documentation for reference purposes.
+
+**Note**: This documentation is archived and may be outdated. Please refer to the main [Documentation](../docs/) section for current information.
+
+## Available Sections
+
+* [Architecture](architecture/) - System architecture and diagrams
+* [Documentation](documentation/) - Meta documentation about the documentation system
+* [Platform Overview](platform-overview/) - Overview document
+* [v1 (Legacy)](v1/) - Original v1 documentation

content/en/docs-old/architecture/highlevelarch.md

@@ -17,7 +17,7 @@ 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.
+See the [setup instructions]({{< ref "/docs-old/architecture/setup" >}}) for details.
 {{< /alert >}}
 
 ## Architecture Overview
@@ -76,4 +76,4 @@ To update or modify the architecture diagrams:
 
 3. Commit both the model changes and the regenerated JavaScript file
 
-For more information, see the [LikeC4 Integration Guide]({{< ref "/docs/architecture/setup" >}}).
+For more information, see the [LikeC4 Integration Guide]({{< ref "/docs-old/architecture/setup" >}}).

content/en/docs-old/platform-overview.md

@@ -0,0 +1,75 @@
+---
+title: "eDF Documentation Overview"
+description: "Comprehensive guide for users and auditors to understand and use the eDF."
+---
+
+# Meta
+
+## Guidelines
+
+1. for users/developers/engineers we describe our output / outcome as product
+    * it is usable
+    * there are links / lists to repos
+2. we have and describe a 'product-structure-tree'
+3. for auditors / governance we have a list / cross reference to Jira tickets
+    * R&D ?, 
+    * mappen auf die projektphasen, wie erstellt ein team eine plattform? 
+        * stw. mobbing, mob programming
+    * mapping auf deliverables von IPCEI-CIS ???, bzw. mapping auf epics?
+    * projekthistorie, projektdynamic, teilprojekt von eDF , teilprojekt-abhängigkiet zB 'Platform'
+    * friendly user phase
+    * forgejo community, OSS, PR handling
+    * externe stakeholder, user experience, think ahead integration
+    * technolgien, technologie-schwerpunkte, cutting-edge research
+    * design/specification und bewertung von lösungsentürfen (zB VictoriaMetrics, GARM, terraform, argoCD, ...)
+    * CI/CD, golden paths (anm.: ist in grobkonzept, deployment von apps von developern fehlt)
+
+# Introduction
+- Purpose of the eDF
+- Target audience (developers, engineers, auditors)
+- High-level product structure overview
+- High-level architecture overview
+
+# eDF Components Overview
+- List of all major components
+- Vertical and horizontal layers explained
+- Component maturity/status (fully integrated, partial, experimental)
+
+# Getting Started
+- Quickstart guide for developers
+- Onboarding steps for eDF engineers
+- Prerequisites and environment setup
+
+# Component Details
+For each component:
+- Description and purpose
+- Repository link
+- README summary
+- Architecture diagrams (link to Miro/Lucid)
+- Usage instructions
+- Integration points
+
+# Development Experience
+- How to contribute
+- Local development workflow
+- CI/CD pipelines
+- Testing and validation
+
+# Operational Experience
+- Deployment guides
+- Monitoring and observability
+- Troubleshooting
+
+# Audit & Compliance
+- Overview of implemented controls
+- Ticket references (Jira, changelogs)
+- Documentation of decisions and reviews
+- Evidence of value and coverage
+
+# FAQ & Support
+- Common issues and solutions
+- Contact points for help
+
+# Appendix
+- Glossary
+- References to external resources