From 47b0c404f32abca24b48cc08d69772e775083487 Mon Sep 17 00:00:00 2001 From: Stephan Lo Date: Mon, 17 Nov 2025 17:44:15 +0100 Subject: [PATCH 01/11] docs(forgejo): some restructuring and review - tbc --- content/en/docs/components/_index.md | 3 +- content/en/docs/components/forgejo/actions.md | 5 +- content/en/docs/components/forgejo/forgejo.md | 29 ++++ .../docs/components/forgejo/project-mgmt.md | 2 +- .../forgejo/runner-orchestration.md | 127 ++++++++++++++ content/en/docs/components/forgejo/runner.md | 2 +- .../_index.md} | 155 ++++++------------ 7 files changed, 212 insertions(+), 111 deletions(-) create mode 100644 content/en/docs/components/forgejo/runner-orchestration.md rename content/en/docs/{DOCUMENTATION-GUIDE.md => documentation-guide/_index.md} (50%) diff --git a/content/en/docs/components/_index.md b/content/en/docs/components/_index.md index d93f56b..a50ba3b 100644 --- a/content/en/docs/components/_index.md +++ b/content/en/docs/components/_index.md @@ -32,9 +32,8 @@ The EDP consists of the following main component categories: * **Dev Environments**: Development environment provisioning * **Physical Environments**: Runtime infrastructure - ### Product Component Structure [TODO] Links -![alt text](website-and-documentation_resources_product-structure.svg) \ No newline at end of file +![alt text](website-and-documentation_resources_product-structure.svg) diff --git a/content/en/docs/components/forgejo/actions.md b/content/en/docs/components/forgejo/actions.md index c32fe35..029cf95 100644 --- a/content/en/docs/components/forgejo/actions.md +++ b/content/en/docs/components/forgejo/actions.md @@ -1,9 +1,8 @@ --- title: "Forgejo Actions" linkTitle: "Actions" -weight: 10 -description: > - GitHub Actions-compatible CI/CD automation +weight: 20 +description: GitHub Actions-compatible CI/CD automation --- {{% alert title="Draft" color="warning" %}} diff --git a/content/en/docs/components/forgejo/forgejo.md b/content/en/docs/components/forgejo/forgejo.md index 03a8654..8dc2edf 100644 --- a/content/en/docs/components/forgejo/forgejo.md +++ b/content/en/docs/components/forgejo/forgejo.md @@ -1,11 +1,40 @@ --- title: "Forgejo Integration, Extension, and Community Collaboration" +linkTitle: Forgejo Software Forge date: "2025-11-17" description: "Summary of the project's work integrating GARM with Forgejo and contributing key features back to the community." tags: ["Forgejo", "GARM", "CI/CD", "OSS", "Community", "Project Report"] categories: ["Workpackage Results"] +weight: 10 --- +{{% alert title="Draft" color="warning" %}} +**Editorial Status**: This page is currently being developed. + +* **Jira Ticket**: https://jira.telekom-mms.com/browse/IPCEICIS-6731 +* **Assignee**: Daniel +* **Status**: Draft +* **Last Updated**: 2025-11-17 +* **TODO**: + * [ ] Add concrete quick start steps + * [ ] Include prerequisites and access information + * [ ] Create first application tutorial +* **Review/Feedback**: + * [ ] Stephan: + * in general: + * some parts are worth to go th 'Governance' + * perhaps we should remove the emojis? + * perhaps we should avoid the impression that the text was copy/pated from AI + * some details/further ideas: + * where is it? why is it called 'edp.buildth.ing'? + * Friendly users? organisations? Public/private stuff? + * App Management discussions (we don't!)? + * what about code snippets how forgejo is deployed? + * Migrations we did, where is the migration code? + * what is our general experience? + * ... +{{% /alert %}} + ## 🧾 Result short description / cognitions Here is the management summary of the work package results: diff --git a/content/en/docs/components/forgejo/project-mgmt.md b/content/en/docs/components/forgejo/project-mgmt.md index 6c856c5..613827e 100644 --- a/content/en/docs/components/forgejo/project-mgmt.md +++ b/content/en/docs/components/forgejo/project-mgmt.md @@ -1,7 +1,7 @@ --- title: "Project Management" linkTitle: "Project Mgmt" -weight: 10 +weight: 50 description: > Project and issue management capabilities within Forgejo --- diff --git a/content/en/docs/components/forgejo/runner-orchestration.md b/content/en/docs/components/forgejo/runner-orchestration.md new file mode 100644 index 0000000..8c5aa1f --- /dev/null +++ b/content/en/docs/components/forgejo/runner-orchestration.md @@ -0,0 +1,127 @@ +--- +title: "Runner Orchestration" +linkTitle: "Runner Orchestration" +weight: 40 +description: GARM +--- + +{{% alert title="Draft" color="warning" %}} +**Editorial Status**: This page is currently being developed. + +* **Jira Ticket**: [TICKET-XXX](https://your-jira/browse/TICKET-XXX) +* **Assignee**: [Name or Team] +* **Status**: Draft +* **Last Updated**: YYYY-MM-DD +* **TODO**: + * [ ] Add detailed component description + * [ ] Include usage examples and code samples + * [ ] Add architecture diagrams + * [ ] Review and finalize content +{{% /alert %}} + +## Overview + +[Detailed description of the component - what it is, what it does, and why it exists] + +## Key Features + +* [Feature 1] +* [Feature 2] +* [Feature 3] + +## Purpose in EDP + +[Explain the role this component plays in the Edge Developer Platform and how it contributes to the overall platform capabilities] + +## Repository + +**Code**: [Link to source code repository] + +**Documentation**: [Link to component-specific documentation] + +## Getting Started + +### Prerequisites + +* [Prerequisite 1] +* [Prerequisite 2] + +### Quick Start + +[Step-by-step guide to get started with this component] + +1. [Step 1] +2. [Step 2] +3. [Step 3] + +### Verification + +[How to verify the component is working correctly] + +## Usage Examples + +### [Use Case 1] + +[Example with code/commands showing common use case] + +```bash +# Example commands +``` + +### [Use Case 2] + +[Another common scenario] + +## Integration Points + +* **[Component A]**: [How it integrates] +* **[Component B]**: [How it integrates] +* **[Component C]**: [How it integrates] + +## Architecture + +[Optional: Add architectural diagrams and descriptions] + +### Component Architecture (C4) + +[Add C4 Container or Component diagrams showing the internal structure] + +### Sequence Diagrams + +[Add sequence diagrams showing key interaction flows with other components] + +### Deployment Architecture + +[Add infrastructure and deployment diagrams showing how the component is deployed] + +## Configuration + +[Key configuration options and how to set them] + +## Troubleshooting + +### [Common Issue 1] + +**Problem**: [Description] + +**Solution**: [How to fix] + +### [Common Issue 2] + +**Problem**: [Description] + +**Solution**: [How to fix] + +## Status + +**Maturity**: [Production / Beta / Experimental] + +## Additional Resources + +* [Link to external documentation] +* [Link to community resources] +* [Link to related components] + +## Documentation Notes + +[Instructions for team members filling in this documentation - remove this section once complete] diff --git a/content/en/docs/components/forgejo/runner.md b/content/en/docs/components/forgejo/runner.md index 8a15857..1eccad0 100644 --- a/content/en/docs/components/forgejo/runner.md +++ b/content/en/docs/components/forgejo/runner.md @@ -1,7 +1,7 @@ --- title: "Action Runner" linkTitle: "Runner" -weight: 20 +weight: 30 description: > Self-hosted runner infrastructure with orchestration capabilities --- diff --git a/content/en/docs/DOCUMENTATION-GUIDE.md b/content/en/docs/documentation-guide/_index.md similarity index 50% rename from content/en/docs/DOCUMENTATION-GUIDE.md rename to content/en/docs/documentation-guide/_index.md index 5ed89f4..fa0ccb3 100644 --- a/content/en/docs/DOCUMENTATION-GUIDE.md +++ b/content/en/docs/documentation-guide/_index.md @@ -1,41 +1,44 @@ --- -title: "Documentation Guide" -linkTitle: "Documentation Guide" +title: "WiP Documentation Guide" +linkTitle: "WiP Doc Guide" weight: 1 -description: > - Guidelines and templates for creating EDP documentation. +description: Guidelines and templates for creating EDP documentation. This page will be removed in the final documentation. --- +{{% alert title="WiP - Only during creation phase" %}} +This page will be removed in the final documentation. +{{% /alert %}} + ## Purpose -This guide helps team members create consistent, high-quality documentation for the Edge Developer Platform. The documentation serves developers, engineers, and auditors who need to understand and use the platform. +This guide helps team members create consistent, high-quality documentation for the Edge Developer Platform. + ## Documentation Principles -### Focus on Outcomes +### 1. Focus on Outcomes -* Describe what the platform does and how to use it -* Emphasize practical usage over implementation details -* Include links to repositories for deeper technical information +1. Describe how the platform is comprised and which Products we deliver +2. If you need inspiration for our EDP product structure look at [EDP product structure tree](../components/website-and-documentation_resources_product-structure.svg) +2. Include links to repositories for deeper technical information or for not beeing too verbose and redundant with existing doumentation within the IPCEI-CIS scope or our EDP repos scope. -### Write for the Audience +### 2. Write for the Audience -* **Developers**: How to use the platform, deploy applications, integrate services -* **Engineers**: Architecture, operational procedures, troubleshooting -* **Auditors**: Project history, decisions, compliance information +1. **Developers**: How to use the software products +2. **Engineers**: Architecture +3. **Auditors**: Project history, decisions, compliance information -### Keep It Concise +### 3. Keep It Concise -* Top-down approach: start with overview, drill down as needed -* Less is more - avoid deep nested structures -* Use templates to maintain consistency +1. Top-down approach: start with overview, drill down as needed +2. Less is more - avoid deep nested structures +3. Avoid emojis +4. **When using AI**: Review the text that you paste, check integration into the rest of the documentation -### Maintain Quality +### 4. Maintain Quality -* Use present tense ("The system processes..." not "will process") -* Keep information up to date -* Test examples and procedures before documenting -* Run `task test` before committing changes +1. Use present tense ("The system processes..." not "will process") +2. Run `task test:quick` before committing changes ## Documentation Structure @@ -47,7 +50,13 @@ High-level introduction to EDP, target audience, purpose, and product structure. **Content focus**: Why EDP exists, who uses it, what it provides -### 2. Components +### 2. Getting Started + +Onboarding guides and quick start instructions. + +**Content focus**: Prerequisites, step-by-step setup, first application deployment + +### 3. Components Detailed documentation for each platform component. @@ -55,12 +64,6 @@ Detailed documentation for each platform component. **Template**: Use `components/TEMPLATE.md` as starting point -### 3. Getting Started - -Onboarding guides and quick start instructions. - -**Content focus**: Prerequisites, step-by-step setup, first application deployment - ### 4. Operations Deployment, monitoring, troubleshooting, and maintenance procedures. @@ -75,16 +78,30 @@ Project history, architecture decisions, compliance, and audit information. ## Writing Documentation -### Using Templates +### Components -Templates are provided for common documentation types: +#### Using Templates + +In section 'Components' Templates are provided for common documentation types: * **Component Documentation**: `content/en/docs/components/TEMPLATE.md` -* Review existing component pages for examples (Forgejo, Kubernetes, Backstage) + +#### Content Structure + +Follow this pattern for component documentation: + +1. **Overview**: What it is and what it does +2. **Key Features**: Bullet list of main capabilities +3. **Purpose in EDP**: Why it's part of the platform +4. **Getting Started**: Quick start guide +5. **Usage Examples**: Common scenarios +6. **Integration Points**: How it connects to other components +7. **Status**: Current maturity level +8. **Documentation Notes**: Instructions for filling in details (remove when complete) ### Frontmatter -Every markdown file starts with YAML frontmatter: +Every markdown file starts with YAML frontmatter according to [Docsy](https://www.docsy.dev/docs/adding-content/content/#page-frontmatter): ```yaml --- @@ -101,48 +118,13 @@ description: > * **weight**: Sort order (lower numbers appear first) * **description**: Brief summary for SEO and page previews -### Content Structure - -Follow this pattern for component documentation: - -1. **Overview**: What it is and what it does -2. **Key Features**: Bullet list of main capabilities -3. **Purpose in EDP**: Why it's part of the platform -4. **Getting Started**: Quick start guide -5. **Usage Examples**: Common scenarios -6. **Integration Points**: How it connects to other components -7. **Status**: Current maturity level -8. **Documentation Notes**: Instructions for filling in details (remove when complete) - -### Markdown Style - -* Use `*` for bullet lists (not `-`) -* Add blank lines around headings and lists -* Specify language for code blocks: ` ```bash ` or ` ```yaml ` -* Use relative links for internal pages - -### Including Code Examples - -Always specify the language: - -```bash -# Good example -task serve -``` - -```yaml -# Configuration example -apiVersion: v1 -kind: Service -``` - ## Testing Documentation Before committing changes: ```bash # Run all tests -task test +task test:quick # Build site locally task build @@ -151,13 +133,6 @@ task build task serve ``` -The test suite checks: - -* Markdown syntax (markdownlint) -* HTML validity -* Broken links -* Hugo build success - ## Adding New Sections When adding a new documentation section: @@ -168,34 +143,6 @@ When adding a new documentation section: 4. Update navigation in parent `_index.md` if needed 5. Test with `task test` -## Tips for Good Documentation - -### Do - -* Write clearly and concisely -* Use examples and code samples -* Include links to repositories and external resources -* Update documentation when features change -* Test procedures before documenting them -* Use templates for consistency - -### Don't - -* Create deep nested structures (keep it flat) -* Document implementation details extensively (link to code instead) -* Use future tense ("will do" → "does") -* Add documentation for incomplete features -* Forget to test your changes - -## Getting Help - -For questions about documentation: - -* Check existing pages for examples -* Review `doc/README-technical-writer.md` for Hugo/Docsy details -* Ask team members for review before committing -* Use `task serve` to preview changes locally - ## Reference * **Main README**: `/doc/README-technical-writer.md` From fc5dda68f8abd3a6e25fd661eb6cb0714c281d1f Mon Sep 17 00:00:00 2001 From: Stephan Lo Date: Mon, 17 Nov 2025 18:25:33 +0100 Subject: [PATCH 02/11] docs(forgejo): even more ideas --- content/en/docs/components/forgejo/forgejo.md | 10 ++++++++-- 1 file changed, 8 insertions(+), 2 deletions(-) diff --git a/content/en/docs/components/forgejo/forgejo.md b/content/en/docs/components/forgejo/forgejo.md index 8dc2edf..7a01976 100644 --- a/content/en/docs/components/forgejo/forgejo.md +++ b/content/en/docs/components/forgejo/forgejo.md @@ -26,12 +26,18 @@ weight: 10 * perhaps we should remove the emojis? * perhaps we should avoid the impression that the text was copy/pated from AI * some details/further ideas: - * where is it? why is it called 'edp.buildth.ing'? + * where is it, this Forgejo? Why is it called 'edp.buildth.ing'? + * what are the components we use - package managament, actions, ... * Friendly users? organisations? Public/private stuff? * App Management discussions (we don't!)? - * what about code snippets how forgejo is deployed? + * what about code snippets how forgejo is deployed? SSO? user base? Federation options? + * storages, Redis, Postgres ... deployment options ... helm charts ... * Migrations we did, where is the migration code? + * git POSIX filesystem concurrency discussion, S/3 bucket * what is our general experience? + * repository centric domain data model + * how did we develop? which version did we take first? how did we upgrade? + * which development flows did we use? which pipleines? * ... {{% /alert %}} From 44b722b0876c210605ccc2119aabba42ebcc6517 Mon Sep 17 00:00:00 2001 From: Stephan Lo Date: Mon, 17 Nov 2025 18:45:16 +0100 Subject: [PATCH 03/11] docs(forgejo): even more ideas II --- content/en/docs/components/forgejo/forgejo.md | 34 ++++++++++--------- 1 file changed, 18 insertions(+), 16 deletions(-) diff --git a/content/en/docs/components/forgejo/forgejo.md b/content/en/docs/components/forgejo/forgejo.md index 7a01976..29103b9 100644 --- a/content/en/docs/components/forgejo/forgejo.md +++ b/content/en/docs/components/forgejo/forgejo.md @@ -22,23 +22,25 @@ weight: 10 * **Review/Feedback**: * [ ] Stephan: * in general: - * some parts are worth to go th 'Governance' - * perhaps we should remove the emojis? - * perhaps we should avoid the impression that the text was copy/pated from AI + * [ ] some parts are worth to go th 'Governance' + * [ ] perhaps we should remove the emojis? + * [ ] perhaps we should avoid the impression that the text was copy/pated from AI * some details/further ideas: - * where is it, this Forgejo? Why is it called 'edp.buildth.ing'? - * what are the components we use - package managament, actions, ... - * Friendly users? organisations? Public/private stuff? - * App Management discussions (we don't!)? - * what about code snippets how forgejo is deployed? SSO? user base? Federation options? - * storages, Redis, Postgres ... deployment options ... helm charts ... - * Migrations we did, where is the migration code? - * git POSIX filesystem concurrency discussion, S/3 bucket - * what is our general experience? - * repository centric domain data model - * how did we develop? which version did we take first? how did we upgrade? - * which development flows did we use? which pipleines? - * ... + * [ ] where is it, this Forgejo? Why is it called 'edp.buildth.ing'? + * [ ] what are the components we use - package managament, actions, ... + * [ ] Friendly users? organisations? Public/private stuff? + * [ ] App Management discussions (we don't!)? + * [ ] what about code snippets how forgejo is deployed? SSO? user base? Federation options? + * [ ] storages, Redis, Postgres ... deployment options ... helm charts ... + * [ ] Migrations we did, where is the migration code? + * [ ] git POSIX filesystem concurrency discussion, S/3 bucket + * [ ] what is our general experience? + * [ ] repository centric domain data model + * [ ] how did we develop? which version did we take first? how did we upgrade? + * [ ] which development flows did we use? which pipleines? + * [ ] provide codeberg links for the PRs + * [ ] provide architecture drawings and repo links for the cache registry thing + * [ ] provide a hight level actions arch diagram from the perspective of forgejo - link to the GARM component here {{% /alert %}} ## 🧾 Result short description / cognitions From 829895fa73a2df2f14c1eeb1ca8729ea36ea95cb Mon Sep 17 00:00:00 2001 From: Stephan Lo Date: Mon, 17 Nov 2025 19:14:32 +0100 Subject: [PATCH 04/11] doc(stacks): added stacks documentation farme according to IPCEICIS-6729 --- content/en/docs/components/forgejo/forgejo.md | 2 +- .../components/orchestration/application.md | 128 ++++++++++++++++++ ...ture-provisioning.md => infrastructure.md} | 6 +- .../{platform-provisioning.md => platform.md} | 6 +- .../{stacks.md => stacks/_index.md} | 4 +- .../orchestration/stacks/component-1.md | 128 ++++++++++++++++++ .../orchestration/stacks/component-2.md | 128 ++++++++++++++++++ 7 files changed, 393 insertions(+), 9 deletions(-) create mode 100644 content/en/docs/components/orchestration/application.md rename content/en/docs/components/orchestration/{infrastructure-provisioning.md => infrastructure.md} (96%) rename content/en/docs/components/orchestration/{platform-provisioning.md => platform.md} (96%) rename content/en/docs/components/orchestration/{stacks.md => stacks/_index.md} (96%) create mode 100644 content/en/docs/components/orchestration/stacks/component-1.md create mode 100644 content/en/docs/components/orchestration/stacks/component-2.md diff --git a/content/en/docs/components/forgejo/forgejo.md b/content/en/docs/components/forgejo/forgejo.md index 29103b9..c358644 100644 --- a/content/en/docs/components/forgejo/forgejo.md +++ b/content/en/docs/components/forgejo/forgejo.md @@ -11,7 +11,7 @@ weight: 10 {{% alert title="Draft" color="warning" %}} **Editorial Status**: This page is currently being developed. -* **Jira Ticket**: https://jira.telekom-mms.com/browse/IPCEICIS-6731 +* **Jira Ticket**: [TICKET-6731](https://jira.telekom-mms.com/browse/IPCEICIS-6731) * **Assignee**: Daniel * **Status**: Draft * **Last Updated**: 2025-11-17 diff --git a/content/en/docs/components/orchestration/application.md b/content/en/docs/components/orchestration/application.md new file mode 100644 index 0000000..6c6fe3b --- /dev/null +++ b/content/en/docs/components/orchestration/application.md @@ -0,0 +1,128 @@ +--- +title: "Application Orchestration" +linkTitle: "Application Orchestration" +weight: 50 +description: > + Application-level component provisioning via Stacks +--- + +{{% alert title="Draft" color="warning" %}} +**Editorial Status**: This page is currently being developed. + +* **Jira Ticket**: [TICKET-XXX](https://your-jira/browse/TICKET-XXX) +* **Assignee**: [Name or Team] +* **Status**: Draft +* **Last Updated**: YYYY-MM-DD +* **TODO**: + * [ ] Add detailed component description + * [ ] Include usage examples and code samples + * [ ] Add architecture diagrams + * [ ] Review and finalize content +{{% /alert %}} + +## Overview + +[Detailed description of the component - what it is, what it does, and why it exists] + +## Key Features + +* [Feature 1] +* [Feature 2] +* [Feature 3] + +## Purpose in EDP + +[Explain the role this component plays in the Edge Developer Platform and how it contributes to the overall platform capabilities] + +## Repository + +**Code**: [Link to source code repository] + +**Documentation**: [Link to component-specific documentation] + +## Getting Started + +### Prerequisites + +* [Prerequisite 1] +* [Prerequisite 2] + +### Quick Start + +[Step-by-step guide to get started with this component] + +1. [Step 1] +2. [Step 2] +3. [Step 3] + +### Verification + +[How to verify the component is working correctly] + +## Usage Examples + +### [Use Case 1] + +[Example with code/commands showing common use case] + +```bash +# Example commands +``` + +### [Use Case 2] + +[Another common scenario] + +## Integration Points + +* **[Component A]**: [How it integrates] +* **[Component B]**: [How it integrates] +* **[Component C]**: [How it integrates] + +## Architecture + +[Optional: Add architectural diagrams and descriptions] + +### Component Architecture (C4) + +[Add C4 Container or Component diagrams showing the internal structure] + +### Sequence Diagrams + +[Add sequence diagrams showing key interaction flows with other components] + +### Deployment Architecture + +[Add infrastructure and deployment diagrams showing how the component is deployed] + +## Configuration + +[Key configuration options and how to set them] + +## Troubleshooting + +### [Common Issue 1] + +**Problem**: [Description] + +**Solution**: [How to fix] + +### [Common Issue 2] + +**Problem**: [Description] + +**Solution**: [How to fix] + +## Status + +**Maturity**: [Production / Beta / Experimental] + +## Additional Resources + +* [Link to external documentation] +* [Link to community resources] +* [Link to related components] + +## Documentation Notes + +[Instructions for team members filling in this documentation - remove this section once complete] diff --git a/content/en/docs/components/orchestration/infrastructure-provisioning.md b/content/en/docs/components/orchestration/infrastructure.md similarity index 96% rename from content/en/docs/components/orchestration/infrastructure-provisioning.md rename to content/en/docs/components/orchestration/infrastructure.md index aef2bbd..b36f4ac 100644 --- a/content/en/docs/components/orchestration/infrastructure-provisioning.md +++ b/content/en/docs/components/orchestration/infrastructure.md @@ -1,7 +1,7 @@ --- -title: "Infrastructure Provisioning" -linkTitle: "Infrastructure" -weight: 10 +title: "Infrastructure Orchestration" +linkTitle: "Infrastructure Orchestration" +weight: 20 description: > Infrastructure deployment and catalog management (infra-deploy, infra-catalogue) --- diff --git a/content/en/docs/components/orchestration/platform-provisioning.md b/content/en/docs/components/orchestration/platform.md similarity index 96% rename from content/en/docs/components/orchestration/platform-provisioning.md rename to content/en/docs/components/orchestration/platform.md index 162ef9f..447f55d 100644 --- a/content/en/docs/components/orchestration/platform-provisioning.md +++ b/content/en/docs/components/orchestration/platform.md @@ -1,7 +1,7 @@ --- -title: "Platform Provisioning" -linkTitle: "Platform" -weight: 20 +title: "Platform Orchestration" +linkTitle: "Platform Orchestration" +weight: 30 description: > Platform-level component provisioning via Stacks --- diff --git a/content/en/docs/components/orchestration/stacks.md b/content/en/docs/components/orchestration/stacks/_index.md similarity index 96% rename from content/en/docs/components/orchestration/stacks.md rename to content/en/docs/components/orchestration/stacks/_index.md index da659c6..756cb80 100644 --- a/content/en/docs/components/orchestration/stacks.md +++ b/content/en/docs/components/orchestration/stacks/_index.md @@ -1,7 +1,7 @@ --- title: "Stacks" linkTitle: "Stacks" -weight: 20 +weight: 10 description: > Platform-level component provisioning via Stacks --- @@ -9,7 +9,7 @@ description: > {{% alert title="Draft" color="warning" %}} **Editorial Status**: This page is currently being developed. -* **Jira Ticket**: [TICKET-6418](https://your-jira/browse/TICKET-XXX) +* **Jira Ticket**: [TICKET-6729](https://jira.telekom-mms.com/browse/IPCEICIS-6729) * **Assignee**: [Name or Team] * **Status**: Draft * **Last Updated**: YYYY-MM-DD diff --git a/content/en/docs/components/orchestration/stacks/component-1.md b/content/en/docs/components/orchestration/stacks/component-1.md new file mode 100644 index 0000000..4f6b18c --- /dev/null +++ b/content/en/docs/components/orchestration/stacks/component-1.md @@ -0,0 +1,128 @@ +--- +title: "Component 1" +linkTitle: "Component 1" +weight: 20 +description: > + Component 1 +--- + +{{% alert title="Draft" color="warning" %}} +**Editorial Status**: This page is currently being developed. + +* **Jira Ticket**: [TBD] +* **Assignee**: [Name or Team] +* **Status**: Draft +* **Last Updated**: YYYY-MM-DD +* **TODO**: + * [ ] Add detailed component description + * [ ] Include usage examples and code samples + * [ ] Add architecture diagrams + * [ ] Review and finalize content +{{% /alert %}} + +## Overview + +[Detailed description of the component - what it is, what it does, and why it exists] + +## Key Features + +* [Feature 1] +* [Feature 2] +* [Feature 3] + +## Purpose in EDP + +[Explain the role this component plays in the Edge Developer Platform and how it contributes to the overall platform capabilities] + +## Repository + +**Code**: [Link to source code repository] + +**Documentation**: [Link to component-specific documentation] + +## Getting Started + +### Prerequisites + +* [Prerequisite 1] +* [Prerequisite 2] + +### Quick Start + +[Step-by-step guide to get started with this component] + +1. [Step 1] +2. [Step 2] +3. [Step 3] + +### Verification + +[How to verify the component is working correctly] + +## Usage Examples + +### [Use Case 1] + +[Example with code/commands showing common use case] + +```bash +# Example commands +``` + +### [Use Case 2] + +[Another common scenario] + +## Integration Points + +* **[Component A]**: [How it integrates] +* **[Component B]**: [How it integrates] +* **[Component C]**: [How it integrates] + +## Architecture + +[Optional: Add architectural diagrams and descriptions] + +### Component Architecture (C4) + +[Add C4 Container or Component diagrams showing the internal structure] + +### Sequence Diagrams + +[Add sequence diagrams showing key interaction flows with other components] + +### Deployment Architecture + +[Add infrastructure and deployment diagrams showing how the component is deployed] + +## Configuration + +[Key configuration options and how to set them] + +## Troubleshooting + +### [Common Issue 1] + +**Problem**: [Description] + +**Solution**: [How to fix] + +### [Common Issue 2] + +**Problem**: [Description] + +**Solution**: [How to fix] + +## Status + +**Maturity**: [Production / Beta / Experimental] + +## Additional Resources + +* [Link to external documentation] +* [Link to community resources] +* [Link to related components] + +## Documentation Notes + +[Instructions for team members filling in this documentation - remove this section once complete] diff --git a/content/en/docs/components/orchestration/stacks/component-2.md b/content/en/docs/components/orchestration/stacks/component-2.md new file mode 100644 index 0000000..0244aa7 --- /dev/null +++ b/content/en/docs/components/orchestration/stacks/component-2.md @@ -0,0 +1,128 @@ +--- +title: "Component 2" +linkTitle: "Component 2" +weight: 30 +description: > + Component 2 +--- + +{{% alert title="Draft" color="warning" %}} +**Editorial Status**: This page is currently being developed. + +* **Jira Ticket**: [TBD] +* **Assignee**: [Name or Team] +* **Status**: Draft +* **Last Updated**: YYYY-MM-DD +* **TODO**: + * [ ] Add detailed component description + * [ ] Include usage examples and code samples + * [ ] Add architecture diagrams + * [ ] Review and finalize content +{{% /alert %}} + +## Overview + +[Detailed description of the component - what it is, what it does, and why it exists] + +## Key Features + +* [Feature 1] +* [Feature 2] +* [Feature 3] + +## Purpose in EDP + +[Explain the role this component plays in the Edge Developer Platform and how it contributes to the overall platform capabilities] + +## Repository + +**Code**: [Link to source code repository] + +**Documentation**: [Link to component-specific documentation] + +## Getting Started + +### Prerequisites + +* [Prerequisite 1] +* [Prerequisite 2] + +### Quick Start + +[Step-by-step guide to get started with this component] + +1. [Step 1] +2. [Step 2] +3. [Step 3] + +### Verification + +[How to verify the component is working correctly] + +## Usage Examples + +### [Use Case 1] + +[Example with code/commands showing common use case] + +```bash +# Example commands +``` + +### [Use Case 2] + +[Another common scenario] + +## Integration Points + +* **[Component A]**: [How it integrates] +* **[Component B]**: [How it integrates] +* **[Component C]**: [How it integrates] + +## Architecture + +[Optional: Add architectural diagrams and descriptions] + +### Component Architecture (C4) + +[Add C4 Container or Component diagrams showing the internal structure] + +### Sequence Diagrams + +[Add sequence diagrams showing key interaction flows with other components] + +### Deployment Architecture + +[Add infrastructure and deployment diagrams showing how the component is deployed] + +## Configuration + +[Key configuration options and how to set them] + +## Troubleshooting + +### [Common Issue 1] + +**Problem**: [Description] + +**Solution**: [How to fix] + +### [Common Issue 2] + +**Problem**: [Description] + +**Solution**: [How to fix] + +## Status + +**Maturity**: [Production / Beta / Experimental] + +## Additional Resources + +* [Link to external documentation] +* [Link to community resources] +* [Link to related components] + +## Documentation Notes + +[Instructions for team members filling in this documentation - remove this section once complete] From d10f888985faf7e3ebce3a6c80c16bfa17255c23 Mon Sep 17 00:00:00 2001 From: Stephan Lo Date: Mon, 17 Nov 2025 19:24:02 +0100 Subject: [PATCH 05/11] doc(stacks): added actions documentation farme according to IPCEICIS-6730 --- .../docs/components/forgejo/actions/_index.md | 27 +++++++++++++++++++ .../forgejo/{ => actions}/actions.md | 2 +- .../{ => actions}/runner-orchestration.md | 2 +- .../forgejo/{ => actions}/runner.md | 2 +- .../docs/components/forgejo/project-mgmt.md | 2 +- .../components/orchestration/application.md | 2 +- .../orchestration/infrastructure.md | 2 +- .../docs/components/orchestration/platform.md | 2 +- .../components/orchestration/stacks/_index.md | 2 +- 9 files changed, 35 insertions(+), 8 deletions(-) create mode 100644 content/en/docs/components/forgejo/actions/_index.md rename content/en/docs/components/forgejo/{ => actions}/actions.md (99%) rename content/en/docs/components/forgejo/{ => actions}/runner-orchestration.md (99%) rename content/en/docs/components/forgejo/{ => actions}/runner.md (99%) diff --git a/content/en/docs/components/forgejo/actions/_index.md b/content/en/docs/components/forgejo/actions/_index.md new file mode 100644 index 0000000..e450675 --- /dev/null +++ b/content/en/docs/components/forgejo/actions/_index.md @@ -0,0 +1,27 @@ +--- +title: "Forgejo Actions" +linkTitle: "Forgejo Actions" +weight: 20 +description: Forgejo Actions. +--- + +{{% alert title="Draft" color="warning" %}} +**Editorial Status**: This page is currently being developed. + +* **Jira Ticket**: [TICKET-6730](https://jira.telekom-mms.com/browse/IPCEICIS-6730) +* **Assignee**: [Name or Team] +* **Status**: Draft +* **Last Updated**: YYYY-MM-DD +* **TODO**: + * [ ] Add detailed component description + * [ ] Include usage examples and code samples + * [ ] Add architecture diagrams + * [ ] Review and finalize content +{{% /alert %}} + +Forgejo provides source code management, project management, and CI/CD automation for the EDP. + +## Sub-Components + +* **Project Management**: Issue tracking and project management features +* **Actions**: CI/CD automation (see CI/CD section) diff --git a/content/en/docs/components/forgejo/actions.md b/content/en/docs/components/forgejo/actions/actions.md similarity index 99% rename from content/en/docs/components/forgejo/actions.md rename to content/en/docs/components/forgejo/actions/actions.md index 029cf95..c8d4d85 100644 --- a/content/en/docs/components/forgejo/actions.md +++ b/content/en/docs/components/forgejo/actions/actions.md @@ -1,7 +1,7 @@ --- title: "Forgejo Actions" linkTitle: "Actions" -weight: 20 +weight: 10 description: GitHub Actions-compatible CI/CD automation --- diff --git a/content/en/docs/components/forgejo/runner-orchestration.md b/content/en/docs/components/forgejo/actions/runner-orchestration.md similarity index 99% rename from content/en/docs/components/forgejo/runner-orchestration.md rename to content/en/docs/components/forgejo/actions/runner-orchestration.md index 8c5aa1f..151fff8 100644 --- a/content/en/docs/components/forgejo/runner-orchestration.md +++ b/content/en/docs/components/forgejo/actions/runner-orchestration.md @@ -1,7 +1,7 @@ --- title: "Runner Orchestration" linkTitle: "Runner Orchestration" -weight: 40 +weight: 30 description: GARM --- diff --git a/content/en/docs/components/forgejo/runner.md b/content/en/docs/components/forgejo/actions/runner.md similarity index 99% rename from content/en/docs/components/forgejo/runner.md rename to content/en/docs/components/forgejo/actions/runner.md index 1eccad0..8a15857 100644 --- a/content/en/docs/components/forgejo/runner.md +++ b/content/en/docs/components/forgejo/actions/runner.md @@ -1,7 +1,7 @@ --- title: "Action Runner" linkTitle: "Runner" -weight: 30 +weight: 20 description: > Self-hosted runner infrastructure with orchestration capabilities --- diff --git a/content/en/docs/components/forgejo/project-mgmt.md b/content/en/docs/components/forgejo/project-mgmt.md index 613827e..b98dd7f 100644 --- a/content/en/docs/components/forgejo/project-mgmt.md +++ b/content/en/docs/components/forgejo/project-mgmt.md @@ -1,6 +1,6 @@ --- title: "Project Management" -linkTitle: "Project Mgmt" +linkTitle: "Forgejo Project Mgmt" weight: 50 description: > Project and issue management capabilities within Forgejo diff --git a/content/en/docs/components/orchestration/application.md b/content/en/docs/components/orchestration/application.md index 6c6fe3b..976aeba 100644 --- a/content/en/docs/components/orchestration/application.md +++ b/content/en/docs/components/orchestration/application.md @@ -1,7 +1,7 @@ --- title: "Application Orchestration" linkTitle: "Application Orchestration" -weight: 50 +weight: 30 description: > Application-level component provisioning via Stacks --- diff --git a/content/en/docs/components/orchestration/infrastructure.md b/content/en/docs/components/orchestration/infrastructure.md index b36f4ac..6d02a3e 100644 --- a/content/en/docs/components/orchestration/infrastructure.md +++ b/content/en/docs/components/orchestration/infrastructure.md @@ -1,7 +1,7 @@ --- title: "Infrastructure Orchestration" linkTitle: "Infrastructure Orchestration" -weight: 20 +weight: 10 description: > Infrastructure deployment and catalog management (infra-deploy, infra-catalogue) --- diff --git a/content/en/docs/components/orchestration/platform.md b/content/en/docs/components/orchestration/platform.md index 447f55d..baa528f 100644 --- a/content/en/docs/components/orchestration/platform.md +++ b/content/en/docs/components/orchestration/platform.md @@ -1,7 +1,7 @@ --- title: "Platform Orchestration" linkTitle: "Platform Orchestration" -weight: 30 +weight: 20 description: > Platform-level component provisioning via Stacks --- diff --git a/content/en/docs/components/orchestration/stacks/_index.md b/content/en/docs/components/orchestration/stacks/_index.md index 756cb80..1c23b2d 100644 --- a/content/en/docs/components/orchestration/stacks/_index.md +++ b/content/en/docs/components/orchestration/stacks/_index.md @@ -1,7 +1,7 @@ --- title: "Stacks" linkTitle: "Stacks" -weight: 10 +weight: 40 description: > Platform-level component provisioning via Stacks --- From 751202516c1170beee1ffd69c09c44ad380e4242 Mon Sep 17 00:00:00 2001 From: Stephan Lo Date: Mon, 17 Nov 2025 19:34:54 +0100 Subject: [PATCH 06/11] doc(stacks): added infrastructure orchestration documentation frame according to IPCEICIS-6732 --- .../_index.md} | 4 +- .../orchestration/infrastructure/provider.md | 127 +++++++++++++++++ .../orchestration/infrastructure/terraform.md | 128 ++++++++++++++++++ 3 files changed, 257 insertions(+), 2 deletions(-) rename content/en/docs/components/orchestration/{infrastructure.md => infrastructure/_index.md} (95%) create mode 100644 content/en/docs/components/orchestration/infrastructure/provider.md create mode 100644 content/en/docs/components/orchestration/infrastructure/terraform.md diff --git a/content/en/docs/components/orchestration/infrastructure.md b/content/en/docs/components/orchestration/infrastructure/_index.md similarity index 95% rename from content/en/docs/components/orchestration/infrastructure.md rename to content/en/docs/components/orchestration/infrastructure/_index.md index 6d02a3e..4f7e6ec 100644 --- a/content/en/docs/components/orchestration/infrastructure.md +++ b/content/en/docs/components/orchestration/infrastructure/_index.md @@ -9,8 +9,8 @@ description: > {{% alert title="Draft" color="warning" %}} **Editorial Status**: This page is currently being developed. -* **Jira Ticket**: [TICKET-XXX](https://your-jira/browse/TICKET-XXX) -* **Assignee**: [Name or Team] +* **Jira Ticket**: [TICKET-6732](https://jira.telekom-mms.com/browse/IPCEICIS-6732)) +* **Assignee**: Martin * **Status**: Draft * **Last Updated**: YYYY-MM-DD * **TODO**: diff --git a/content/en/docs/components/orchestration/infrastructure/provider.md b/content/en/docs/components/orchestration/infrastructure/provider.md new file mode 100644 index 0000000..c6e8c46 --- /dev/null +++ b/content/en/docs/components/orchestration/infrastructure/provider.md @@ -0,0 +1,127 @@ +--- +title: "Provider" +linkTitle: "Provider" +weight: 20 +description: Used Provider we deploy on +--- + +{{% alert title="Draft" color="warning" %}} +**Editorial Status**: This page is currently being developed. + +* **Jira Ticket**: [TICKET-6732](https://jira.telekom-mms.com/browse/IPCEICIS-6732)) +* **Assignee**: Martin +* **Status**: Draft +* **Last Updated**: YYYY-MM-DD +* **TODO**: + * [ ] Add detailed component description + * [ ] Include usage examples and code samples + * [ ] Add architecture diagrams + * [ ] Review and finalize content +{{% /alert %}} + +## Overview + +[Detailed description of the component - what it is, what it does, and why it exists] + +## Key Features + +* [Feature 1] +* [Feature 2] +* [Feature 3] + +## Purpose in EDP + +[Explain the role this component plays in the Edge Developer Platform and how it contributes to the overall platform capabilities] + +## Repository + +**Code**: [Link to source code repository] + +**Documentation**: [Link to component-specific documentation] + +## Getting Started + +### Prerequisites + +* [Prerequisite 1] +* [Prerequisite 2] + +### Quick Start + +[Step-by-step guide to get started with this component] + +1. [Step 1] +2. [Step 2] +3. [Step 3] + +### Verification + +[How to verify the component is working correctly] + +## Usage Examples + +### [Use Case 1] + +[Example with code/commands showing common use case] + +```bash +# Example commands +``` + +### [Use Case 2] + +[Another common scenario] + +## Integration Points + +* **[Component A]**: [How it integrates] +* **[Component B]**: [How it integrates] +* **[Component C]**: [How it integrates] + +## Architecture + +[Optional: Add architectural diagrams and descriptions] + +### Component Architecture (C4) + +[Add C4 Container or Component diagrams showing the internal structure] + +### Sequence Diagrams + +[Add sequence diagrams showing key interaction flows with other components] + +### Deployment Architecture + +[Add infrastructure and deployment diagrams showing how the component is deployed] + +## Configuration + +[Key configuration options and how to set them] + +## Troubleshooting + +### [Common Issue 1] + +**Problem**: [Description] + +**Solution**: [How to fix] + +### [Common Issue 2] + +**Problem**: [Description] + +**Solution**: [How to fix] + +## Status + +**Maturity**: [Production / Beta / Experimental] + +## Additional Resources + +* [Link to external documentation] +* [Link to community resources] +* [Link to related components] + +## Documentation Notes + +[Instructions for team members filling in this documentation - remove this section once complete] diff --git a/content/en/docs/components/orchestration/infrastructure/terraform.md b/content/en/docs/components/orchestration/infrastructure/terraform.md new file mode 100644 index 0000000..5985ecb --- /dev/null +++ b/content/en/docs/components/orchestration/infrastructure/terraform.md @@ -0,0 +1,128 @@ +--- +title: "Terrafrom" +linkTitle: "Terraform" +weight: 10 +description: > + Infrastructure deployment and catalog management (infra-deploy, infra-catalogue) +--- + +{{% alert title="Draft" color="warning" %}} +**Editorial Status**: This page is currently being developed. + +* **Jira Ticket**: [TICKET-6732](https://jira.telekom-mms.com/browse/IPCEICIS-6732)) +* **Assignee**: Martin +* **Status**: Draft +* **Last Updated**: YYYY-MM-DD +* **TODO**: + * [ ] Add detailed component description + * [ ] Include usage examples and code samples + * [ ] Add architecture diagrams + * [ ] Review and finalize content +{{% /alert %}} + +## Overview + +[Detailed description of the component - what it is, what it does, and why it exists] + +## Key Features + +* [Feature 1] +* [Feature 2] +* [Feature 3] + +## Purpose in EDP + +[Explain the role this component plays in the Edge Developer Platform and how it contributes to the overall platform capabilities] + +## Repository + +**Code**: [Link to source code repository] + +**Documentation**: [Link to component-specific documentation] + +## Getting Started + +### Prerequisites + +* [Prerequisite 1] +* [Prerequisite 2] + +### Quick Start + +[Step-by-step guide to get started with this component] + +1. [Step 1] +2. [Step 2] +3. [Step 3] + +### Verification + +[How to verify the component is working correctly] + +## Usage Examples + +### [Use Case 1] + +[Example with code/commands showing common use case] + +```bash +# Example commands +``` + +### [Use Case 2] + +[Another common scenario] + +## Integration Points + +* **[Component A]**: [How it integrates] +* **[Component B]**: [How it integrates] +* **[Component C]**: [How it integrates] + +## Architecture + +[Optional: Add architectural diagrams and descriptions] + +### Component Architecture (C4) + +[Add C4 Container or Component diagrams showing the internal structure] + +### Sequence Diagrams + +[Add sequence diagrams showing key interaction flows with other components] + +### Deployment Architecture + +[Add infrastructure and deployment diagrams showing how the component is deployed] + +## Configuration + +[Key configuration options and how to set them] + +## Troubleshooting + +### [Common Issue 1] + +**Problem**: [Description] + +**Solution**: [How to fix] + +### [Common Issue 2] + +**Problem**: [Description] + +**Solution**: [How to fix] + +## Status + +**Maturity**: [Production / Beta / Experimental] + +## Additional Resources + +* [Link to external documentation] +* [Link to community resources] +* [Link to related components] + +## Documentation Notes + +[Instructions for team members filling in this documentation - remove this section once complete] From 6bd7f6b5a158bf9771307532269324c85af85645 Mon Sep 17 00:00:00 2001 From: Stephan Lo Date: Mon, 17 Nov 2025 19:44:01 +0100 Subject: [PATCH 07/11] doc(stacks): added deployments documentation frame according to IPCEICIS-6733 --- .../en/docs/components/deployments/_index.md | 4 +- .../{edgeconnect.md => edgeconnect/_index.md} | 0 .../{ => edgeconnect}/edgeconnect-client.md | 0 .../edgeconnect/edgeconnect-sdk.md | 128 ++++++++++++++++++ content/en/docs/components/deployments/otc.md | 4 +- .../orchestration/infrastructure/_index.md | 2 +- .../orchestration/infrastructure/provider.md | 2 +- .../orchestration/infrastructure/terraform.md | 2 +- .../components/orchestration/stacks/_index.md | 2 +- 9 files changed, 136 insertions(+), 8 deletions(-) rename content/en/docs/components/deployments/{edgeconnect.md => edgeconnect/_index.md} (100%) rename content/en/docs/components/deployments/{ => edgeconnect}/edgeconnect-client.md (100%) create mode 100644 content/en/docs/components/deployments/edgeconnect/edgeconnect-sdk.md diff --git a/content/en/docs/components/deployments/_index.md b/content/en/docs/components/deployments/_index.md index 3698a67..c68c6ff 100644 --- a/content/en/docs/components/deployments/_index.md +++ b/content/en/docs/components/deployments/_index.md @@ -9,8 +9,8 @@ description: > {{% alert title="Draft" color="warning" %}} **Editorial Status**: This page is currently being developed. -* **Jira Ticket**: [TICKET-XXX](https://your-jira/browse/TICKET-XXX) -* **Assignee**: [Name or Team] +* **Jira Ticket**: [TICKET-6733](https://jira.telekom-mms.com/browse/IPCEICIS-6733) +* **Assignee**: Patrick * **Status**: Draft * **Last Updated**: YYYY-MM-DD * **TODO**: diff --git a/content/en/docs/components/deployments/edgeconnect.md b/content/en/docs/components/deployments/edgeconnect/_index.md similarity index 100% rename from content/en/docs/components/deployments/edgeconnect.md rename to content/en/docs/components/deployments/edgeconnect/_index.md diff --git a/content/en/docs/components/deployments/edgeconnect-client.md b/content/en/docs/components/deployments/edgeconnect/edgeconnect-client.md similarity index 100% rename from content/en/docs/components/deployments/edgeconnect-client.md rename to content/en/docs/components/deployments/edgeconnect/edgeconnect-client.md diff --git a/content/en/docs/components/deployments/edgeconnect/edgeconnect-sdk.md b/content/en/docs/components/deployments/edgeconnect/edgeconnect-sdk.md new file mode 100644 index 0000000..5500feb --- /dev/null +++ b/content/en/docs/components/deployments/edgeconnect/edgeconnect-sdk.md @@ -0,0 +1,128 @@ +--- +title: "EdgeConnect SDK" +linkTitle: "EdgeConnect SDK" +weight: 10 +description: > + Software Development Kit for establishing EdgeConnect connections +--- + +{{% alert title="Draft" color="warning" %}} +**Editorial Status**: This page is currently being developed. + +* **Jira Ticket**: [TICKET-XXX](https://your-jira/browse/TICKET-XXX) +* **Assignee**: [Name or Team] +* **Status**: Draft +* **Last Updated**: YYYY-MM-DD +* **TODO**: + * [ ] Add detailed component description + * [ ] Include usage examples and code samples + * [ ] Add architecture diagrams + * [ ] Review and finalize content +{{% /alert %}} + +## Overview + +[Detailed description of the component - what it is, what it does, and why it exists] + +## Key Features + +* [Feature 1] +* [Feature 2] +* [Feature 3] + +## Purpose in EDP + +[Explain the role this component plays in the Edge Developer Platform and how it contributes to the overall platform capabilities] + +## Repository + +**Code**: [Link to source code repository] + +**Documentation**: [Link to component-specific documentation] + +## Getting Started + +### Prerequisites + +* [Prerequisite 1] +* [Prerequisite 2] + +### Quick Start + +[Step-by-step guide to get started with this component] + +1. [Step 1] +2. [Step 2] +3. [Step 3] + +### Verification + +[How to verify the component is working correctly] + +## Usage Examples + +### [Use Case 1] + +[Example with code/commands showing common use case] + +```bash +# Example commands +``` + +### [Use Case 2] + +[Another common scenario] + +## Integration Points + +* **[Component A]**: [How it integrates] +* **[Component B]**: [How it integrates] +* **[Component C]**: [How it integrates] + +## Architecture + +[Optional: Add architectural diagrams and descriptions] + +### Component Architecture (C4) + +[Add C4 Container or Component diagrams showing the internal structure] + +### Sequence Diagrams + +[Add sequence diagrams showing key interaction flows with other components] + +### Deployment Architecture + +[Add infrastructure and deployment diagrams showing how the component is deployed] + +## Configuration + +[Key configuration options and how to set them] + +## Troubleshooting + +### [Common Issue 1] + +**Problem**: [Description] + +**Solution**: [How to fix] + +### [Common Issue 2] + +**Problem**: [Description] + +**Solution**: [How to fix] + +## Status + +**Maturity**: [Production / Beta / Experimental] + +## Additional Resources + +* [Link to external documentation] +* [Link to community resources] +* [Link to related components] + +## Documentation Notes + +[Instructions for team members filling in this documentation - remove this section once complete] diff --git a/content/en/docs/components/deployments/otc.md b/content/en/docs/components/deployments/otc.md index c958d93..2ee32f5 100644 --- a/content/en/docs/components/deployments/otc.md +++ b/content/en/docs/components/deployments/otc.md @@ -9,8 +9,8 @@ description: > {{% alert title="Draft" color="warning" %}} **Editorial Status**: This page is currently being developed. -* **Jira Ticket**: [TICKET-XXX](https://your-jira/browse/TICKET-XXX) -* **Assignee**: [Name or Team] +* **Jira Ticket**: [TICKET-6733](https://jira.telekom-mms.com/browse/IPCEICIS-6733) +* **Assignee**: Patrick * **Status**: Draft * **Last Updated**: YYYY-MM-DD * **TODO**: diff --git a/content/en/docs/components/orchestration/infrastructure/_index.md b/content/en/docs/components/orchestration/infrastructure/_index.md index 4f7e6ec..fc84a9d 100644 --- a/content/en/docs/components/orchestration/infrastructure/_index.md +++ b/content/en/docs/components/orchestration/infrastructure/_index.md @@ -9,7 +9,7 @@ description: > {{% alert title="Draft" color="warning" %}} **Editorial Status**: This page is currently being developed. -* **Jira Ticket**: [TICKET-6732](https://jira.telekom-mms.com/browse/IPCEICIS-6732)) +* **Jira Ticket**: [TICKET-6732](https://jira.telekom-mms.com/browse/IPCEICIS-6732) * **Assignee**: Martin * **Status**: Draft * **Last Updated**: YYYY-MM-DD diff --git a/content/en/docs/components/orchestration/infrastructure/provider.md b/content/en/docs/components/orchestration/infrastructure/provider.md index c6e8c46..236c0cc 100644 --- a/content/en/docs/components/orchestration/infrastructure/provider.md +++ b/content/en/docs/components/orchestration/infrastructure/provider.md @@ -8,7 +8,7 @@ description: Used Provider we deploy on {{% alert title="Draft" color="warning" %}} **Editorial Status**: This page is currently being developed. -* **Jira Ticket**: [TICKET-6732](https://jira.telekom-mms.com/browse/IPCEICIS-6732)) +* **Jira Ticket**: [TICKET-6732](https://jira.telekom-mms.com/browse/IPCEICIS-6732) * **Assignee**: Martin * **Status**: Draft * **Last Updated**: YYYY-MM-DD diff --git a/content/en/docs/components/orchestration/infrastructure/terraform.md b/content/en/docs/components/orchestration/infrastructure/terraform.md index 5985ecb..69e1813 100644 --- a/content/en/docs/components/orchestration/infrastructure/terraform.md +++ b/content/en/docs/components/orchestration/infrastructure/terraform.md @@ -9,7 +9,7 @@ description: > {{% alert title="Draft" color="warning" %}} **Editorial Status**: This page is currently being developed. -* **Jira Ticket**: [TICKET-6732](https://jira.telekom-mms.com/browse/IPCEICIS-6732)) +* **Jira Ticket**: [TICKET-6732](https://jira.telekom-mms.com/browse/IPCEICIS-6732) * **Assignee**: Martin * **Status**: Draft * **Last Updated**: YYYY-MM-DD diff --git a/content/en/docs/components/orchestration/stacks/_index.md b/content/en/docs/components/orchestration/stacks/_index.md index 1c23b2d..f8d30b1 100644 --- a/content/en/docs/components/orchestration/stacks/_index.md +++ b/content/en/docs/components/orchestration/stacks/_index.md @@ -10,7 +10,7 @@ description: > **Editorial Status**: This page is currently being developed. * **Jira Ticket**: [TICKET-6729](https://jira.telekom-mms.com/browse/IPCEICIS-6729) -* **Assignee**: [Name or Team] +* **Assignee**: Stephan * **Status**: Draft * **Last Updated**: YYYY-MM-DD * **TODO**: From 4169b999d4147cf41e6a993dbad52a1353914e3f Mon Sep 17 00:00:00 2001 From: Stephan Lo Date: Mon, 17 Nov 2025 19:48:36 +0100 Subject: [PATCH 08/11] doc(stacks): added orchestration documentation frame according to IPCEICIS-6734 --- content/en/docs/components/orchestration/_index.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/content/en/docs/components/orchestration/_index.md b/content/en/docs/components/orchestration/_index.md index 46d2978..6246d1b 100644 --- a/content/en/docs/components/orchestration/_index.md +++ b/content/en/docs/components/orchestration/_index.md @@ -9,8 +9,8 @@ description: > {{% alert title="Draft" color="warning" %}} **Editorial Status**: This page is currently being developed. -* **Jira Ticket**: [TICKET-XXX](https://your-jira/browse/TICKET-XXX) -* **Assignee**: [Name or Team] +* **Jira Ticket**: [TICKET-6734](https://jira.telekom-mms.com/browse/IPCEICIS-6734) +* **Assignee**: Stephan * **Status**: Draft * **Last Updated**: YYYY-MM-DD * **TODO**: From 3eed5fe70d5cacd44d93b23eb052e6f3839ed64d Mon Sep 17 00:00:00 2001 From: Stephan Lo Date: Mon, 17 Nov 2025 19:59:46 +0100 Subject: [PATCH 09/11] doc(stacks): added edgeconnect documentation frame according to IPCEICIS-6735 --- content/en/docs/components/deployments/edgeconnect/_index.md | 4 ++-- .../components/deployments/edgeconnect/edgeconnect-client.md | 4 ++-- .../components/deployments/edgeconnect/edgeconnect-sdk.md | 4 ++-- 3 files changed, 6 insertions(+), 6 deletions(-) diff --git a/content/en/docs/components/deployments/edgeconnect/_index.md b/content/en/docs/components/deployments/edgeconnect/_index.md index 8a1d607..d31bd74 100644 --- a/content/en/docs/components/deployments/edgeconnect/_index.md +++ b/content/en/docs/components/deployments/edgeconnect/_index.md @@ -9,8 +9,8 @@ description: > {{% alert title="Draft" color="warning" %}} **Editorial Status**: This page is currently being developed. -* **Jira Ticket**: [TICKET-XXX](https://your-jira/browse/TICKET-XXX) -* **Assignee**: [Name or Team] +* **Jira Ticket**: [TICKET-6734](https://jira.telekom-mms.com/browse/IPCEICIS-6734) +* **Assignee**: Waldemar * **Status**: Draft * **Last Updated**: YYYY-MM-DD * **TODO**: diff --git a/content/en/docs/components/deployments/edgeconnect/edgeconnect-client.md b/content/en/docs/components/deployments/edgeconnect/edgeconnect-client.md index 0b30a77..7c08aca 100644 --- a/content/en/docs/components/deployments/edgeconnect/edgeconnect-client.md +++ b/content/en/docs/components/deployments/edgeconnect/edgeconnect-client.md @@ -9,8 +9,8 @@ description: > {{% alert title="Draft" color="warning" %}} **Editorial Status**: This page is currently being developed. -* **Jira Ticket**: [TICKET-XXX](https://your-jira/browse/TICKET-XXX) -* **Assignee**: [Name or Team] +* **Jira Ticket**: [TICKET-6734](https://jira.telekom-mms.com/browse/IPCEICIS-6734) +* **Assignee**: Waldemar * **Status**: Draft * **Last Updated**: YYYY-MM-DD * **TODO**: diff --git a/content/en/docs/components/deployments/edgeconnect/edgeconnect-sdk.md b/content/en/docs/components/deployments/edgeconnect/edgeconnect-sdk.md index 5500feb..152d044 100644 --- a/content/en/docs/components/deployments/edgeconnect/edgeconnect-sdk.md +++ b/content/en/docs/components/deployments/edgeconnect/edgeconnect-sdk.md @@ -9,8 +9,8 @@ description: > {{% alert title="Draft" color="warning" %}} **Editorial Status**: This page is currently being developed. -* **Jira Ticket**: [TICKET-XXX](https://your-jira/browse/TICKET-XXX) -* **Assignee**: [Name or Team] +* **Jira Ticket**: [TICKET-6734](https://jira.telekom-mms.com/browse/IPCEICIS-6734) +* **Assignee**: Waldemar * **Status**: Draft * **Last Updated**: YYYY-MM-DD * **TODO**: From 79e94d738a4dfbfdac7cd9ccacc57ebea7fa5397 Mon Sep 17 00:00:00 2001 From: Stephan Lo Date: Mon, 17 Nov 2025 20:00:12 +0100 Subject: [PATCH 10/11] doc(stacks): added documentationsystem documentation frame according to IPCEICIS-6736 --- .../en/docs/components/documentationsystem.md | 27 +++++++++++++++++++ 1 file changed, 27 insertions(+) create mode 100644 content/en/docs/components/documentationsystem.md diff --git a/content/en/docs/components/documentationsystem.md b/content/en/docs/components/documentationsystem.md new file mode 100644 index 0000000..d3b182a --- /dev/null +++ b/content/en/docs/components/documentationsystem.md @@ -0,0 +1,27 @@ +--- +title: "Documentation System" +linkTitle: "Documentation System" +weight: 100 +description: The developer 'documentation as code' documentation System we use ourselfes and over to use for each development team. +--- + +{{% alert title="Draft" color="warning" %}} +**Editorial Status**: This page is currently being developed. + +* **Jira Ticket**: [TICKET-6736](https://jira.telekom-mms.com/browse/IPCEICIS-6736) +* **Assignee**: Stephan +* **Status**: Draft +* **Last Updated**: YYYY-MM-DD +* **TODO**: + * [ ] Add detailed component description + * [ ] Include usage examples and code samples + * [ ] Add architecture diagrams + * [ ] Review and finalize content +{{% /alert %}} + +The Orchestration manages platform and infrastructure provisioning, providing the foundation for the EDP deployment model. + +## Sub-Components + +* **Infrastructure Provisioning**: Low-level infrastructure deployment (infra-deploy, infra-catalogue) +* **Platform Provisioning**: Platform-level component deployment via Stacks From d3d99086715aec2815a2fd5f2c7eb3ba6b044ab8 Mon Sep 17 00:00:00 2001 From: Stephan Lo Date: Mon, 17 Nov 2025 20:05:12 +0100 Subject: [PATCH 11/11] doc(stacks): added governance documentation frame according to IPCEICIS-6737 --- content/en/docs/governance/_index.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/content/en/docs/governance/_index.md b/content/en/docs/governance/_index.md index 9ebbad2..c5ab30c 100644 --- a/content/en/docs/governance/_index.md +++ b/content/en/docs/governance/_index.md @@ -9,8 +9,8 @@ description: > {{% alert title="Draft" color="warning" %}} **Editorial Status**: This page is currently being developed. -* **Jira Ticket**: TBD -* **Assignee**: Team +* **Jira Ticket**: [TICKET-6737](https://jira.telekom-mms.com/browse/IPCEICIS-6737) +* **Assignee**: Sophie * **Status**: Draft - Structure only * **Last Updated**: 2025-11-16 * **TODO**: