Stephan Lo
62999b41d0
- 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
54 lines
1.4 KiB
Markdown
54 lines
1.4 KiB
Markdown
---
|
|
title: "Forgejo"
|
|
linkTitle: "Forgejo"
|
|
weight: 1
|
|
description: >
|
|
Self-hosted Git service with repository management and collaboration features.
|
|
---
|
|
|
|
## Overview
|
|
|
|
Forgejo is a self-hosted Git service that provides repository management, issue tracking, pull requests, and collaboration features. It serves as a core component of the EDP for source code management.
|
|
|
|
## Key Features
|
|
|
|
* Git repository hosting
|
|
* Issue tracking and project management
|
|
* Pull requests and code review
|
|
* CI/CD integration with Woodpecker
|
|
* User and organization management
|
|
* API for automation and integration
|
|
|
|
## Purpose in EDP
|
|
|
|
Forgejo serves as the primary source code management platform, providing developers with a familiar Git workflow while maintaining full control over the hosting infrastructure.
|
|
|
|
## Repository
|
|
|
|
**Code**: [Link to Forgejo repository]
|
|
|
|
**Documentation**: [Link to Forgejo-specific documentation]
|
|
|
|
## Getting Started
|
|
|
|
[To be documented: Quick start guide for using Forgejo in EDP]
|
|
|
|
## Integration Points
|
|
|
|
* **Woodpecker CI**: Automated pipeline triggers on git events
|
|
* **ArgoCD**: GitOps repository source
|
|
* **Backstage**: Service catalog integration
|
|
|
|
## Status
|
|
|
|
**Maturity**: Production
|
|
|
|
## Documentation Notes
|
|
|
|
This is a template page. Team members should fill in:
|
|
|
|
* Specific deployment details
|
|
* Access URLs and credentials management
|
|
* Common workflows and usage patterns
|
|
* Troubleshooting information
|
|
* Screenshots or examples
|