website-and-documentation/content/en/docs/_index.md

---
title: "Documentation"
linkTitle: "Documentation"
menu:
  main:
    weight: 20
---

# Edge Developer Platform (EDP) Documentation

Welcome to the EDP documentation. This documentation serves developers, engineers, and auditors who want to understand, use, and audit the Edge Developer Platform.

It describes the outcomes and products of the edgeDeveloperFramework (eDF) sub-project within IPCEI-CIS.

## Target Audience

* **Developers & Engineers**: Learn how to use the platform, deploy applications, and integrate services
* **Platform Engineers**: Understand the architecture, components, and operational aspects
* **Auditors & Governance**: Access project history, decisions, and compliance information

## Documentation Structure

The documentation is organized into three core areas:

* **[Edge Developer Platform (EDP)](/docs/edp/)**: The central platform to support developers working at the edge, based around Forgejo
* **[EdgeConnect Cloud](/docs/edgeconnect/)**: The sovereign edge cloud context and key deployment target for EDP integrations
* **[Governance](/docs/governance/)**: Project history, decision context, and audit-oriented traceability
chore(hugo-theme): moved to docsy. Started from https://github.com/google/docsy-example and ported all ipceicis content to there. removed all docsy example stuff 2024-08-05 11:56:38 +02:00			`---`
feat(docs): restructure documentation with new framework and templates - Archive old docs to docs-old/ for reference - Create new top-down documentation structure: * Platform Overview: purpose, audience, product structure * Components: individual platform components (Forgejo, Kubernetes, Backstage) * Getting Started: onboarding and quick start guides * Operations: deployment, monitoring, troubleshooting * Governance: ADRs, project history, compliance - Add DOCUMENTATION-GUIDE.md with writing guidelines and templates - Add component template (TEMPLATE.md) for consistent documentation - Simplify root README and move technical docs to doc/ folder - Update test configuration: * Exclude legacy content from markdown linting * Relax HTML validation for theme-generated content * Skip link checking for legacy content in test:links * Keep 'task test' clean for technical writers (100% pass) * Add 'task test:full' with comprehensive link checking - Update home page with corrected markdown syntax - Fix internal links in archived content BREAKING CHANGE: Documentation structure changed from flat to hierarchical top-down approach 2025-11-16 13:32:10 +01:00			`title: "Documentation"`
			`linkTitle: "Documentation"`
			`menu:`
			`main:`
			`weight: 20`
chore(hugo-theme): moved to docsy. Started from https://github.com/google/docsy-example and ported all ipceicis content to there. removed all docsy example stuff 2024-08-05 11:56:38 +02:00			`---`

feat(docs): restructure documentation with new framework and templates - Archive old docs to docs-old/ for reference - Create new top-down documentation structure: * Platform Overview: purpose, audience, product structure * Components: individual platform components (Forgejo, Kubernetes, Backstage) * Getting Started: onboarding and quick start guides * Operations: deployment, monitoring, troubleshooting * Governance: ADRs, project history, compliance - Add DOCUMENTATION-GUIDE.md with writing guidelines and templates - Add component template (TEMPLATE.md) for consistent documentation - Simplify root README and move technical docs to doc/ folder - Update test configuration: * Exclude legacy content from markdown linting * Relax HTML validation for theme-generated content * Skip link checking for legacy content in test:links * Keep 'task test' clean for technical writers (100% pass) * Add 'task test:full' with comprehensive link checking - Update home page with corrected markdown syntax - Fix internal links in archived content BREAKING CHANGE: Documentation structure changed from flat to hierarchical top-down approach 2025-11-16 13:32:10 +01:00			`# Edge Developer Platform (EDP) Documentation`

			`Welcome to the EDP documentation. This documentation serves developers, engineers, and auditors who want to understand, use, and audit the Edge Developer Platform.`

docs(documentation): finished documentation entry points 'Documentation' and 'Edge Developer platform' 2025-12-19 12:47:20 +01:00			`It describes the outcomes and products of the edgeDeveloperFramework (eDF) sub-project within IPCEI-CIS.`
docs(): removed internal documentation chapter, added an exsiting high level vision chart on the intro page 2025-12-16 12:34:50 +01:00
feat(docs): restructure documentation with new framework and templates - Archive old docs to docs-old/ for reference - Create new top-down documentation structure: * Platform Overview: purpose, audience, product structure * Components: individual platform components (Forgejo, Kubernetes, Backstage) * Getting Started: onboarding and quick start guides * Operations: deployment, monitoring, troubleshooting * Governance: ADRs, project history, compliance - Add DOCUMENTATION-GUIDE.md with writing guidelines and templates - Add component template (TEMPLATE.md) for consistent documentation - Simplify root README and move technical docs to doc/ folder - Update test configuration: * Exclude legacy content from markdown linting * Relax HTML validation for theme-generated content * Skip link checking for legacy content in test:links * Keep 'task test' clean for technical writers (100% pass) * Add 'task test:full' with comprehensive link checking - Update home page with corrected markdown syntax - Fix internal links in archived content BREAKING CHANGE: Documentation structure changed from flat to hierarchical top-down approach 2025-11-16 13:32:10 +01:00			`## Target Audience`

			`* Developers & Engineers: Learn how to use the platform, deploy applications, and integrate services`
			`* Platform Engineers: Understand the architecture, components, and operational aspects`
			`* Auditors & Governance: Access project history, decisions, and compliance information`

			`## Documentation Structure`

docs(documentation): finished documentation entry points 'Documentation' and 'Edge Developer platform' 2025-12-19 12:47:20 +01:00			`The documentation is organized into three core areas:`
feat(docs): restructure documentation with new framework and templates - Archive old docs to docs-old/ for reference - Create new top-down documentation structure: * Platform Overview: purpose, audience, product structure * Components: individual platform components (Forgejo, Kubernetes, Backstage) * Getting Started: onboarding and quick start guides * Operations: deployment, monitoring, troubleshooting * Governance: ADRs, project history, compliance - Add DOCUMENTATION-GUIDE.md with writing guidelines and templates - Add component template (TEMPLATE.md) for consistent documentation - Simplify root README and move technical docs to doc/ folder - Update test configuration: * Exclude legacy content from markdown linting * Relax HTML validation for theme-generated content * Skip link checking for legacy content in test:links * Keep 'task test' clean for technical writers (100% pass) * Add 'task test:full' with comprehensive link checking - Update home page with corrected markdown syntax - Fix internal links in archived content BREAKING CHANGE: Documentation structure changed from flat to hierarchical top-down approach 2025-11-16 13:32:10 +01:00
docs(index): update 'front door consistency' and remove drafts 2025-12-19 15:46:38 +01:00			`* [Edge Developer Platform (EDP)](/docs/edp/): The central platform to support developers working at the edge, based around Forgejo`
			`* [EdgeConnect Cloud](/docs/edgeconnect/): The sovereign edge cloud context and key deployment target for EDP integrations`
			`* [Governance](/docs/governance/): Project history, decision context, and audit-oriented traceability`