Files
goplt/docs/content/index.md
2025-11-05 11:00:36 +01:00

4.0 KiB

Go Platform Documentation

Welcome to the Go Platform documentation! This is a plugin-friendly SaaS/Enterprise platform built with Go.

What is Go Platform?

Go Platform is a modular, extensible platform designed to support multiple business domains through a plugin architecture. It provides:

  • Core Kernel: Foundation services including authentication, authorization, configuration, logging, and observability
  • Module Framework: Plugin system for extending functionality
  • Infrastructure Adapters: Support for databases, caching, event buses, and job scheduling
  • Security-by-Design: Built-in JWT authentication, RBAC/ABAC authorization, and audit logging
  • Observability: OpenTelemetry integration for tracing, metrics, and logging

Documentation Structure

📋 Overview

🏛️ Architecture

🏗️ Architecture Decision Records (ADRs)

All architectural decisions are documented in ADR records, organized by implementation epic:

  • Epic 0: Project Setup & Foundation
  • Epic 1: Core Kernel & Infrastructure
  • Epic 2: Authentication & Authorization
  • Epic 3: Module Framework
  • Epic 5: Infrastructure Adapters
  • Epic 6: Observability & Production Readiness
  • Epic 7: Testing, Documentation & CI/CD

📝 Implementation Tasks

Detailed task definitions for each epic are available in the Stories section:

  • Epic 0: Project Setup & Foundation
  • Epic 1: Core Kernel & Infrastructure
  • Epic 2: Authentication & Authorization
  • Epic 3: Module Framework
  • Epic 4: Sample Feature Module (Blog)
  • Epic 5: Infrastructure Adapters
  • Epic 6: Observability & Production Readiness
  • Epic 7: Testing, Documentation & CI/CD
  • Epic 8: Advanced Features & Polish (Optional)

Quick Start

  1. Review the Requirements to understand the platform goals
  2. Check the Implementation Plan for the epic-based approach
  3. Follow the Playbook for implementation details
  4. Refer to ADRs when making architectural decisions
  5. Use the Task Stories as a checklist for implementation

Key Principles

  • Clean/Hexagonal Architecture: Clear separation between core and plugins
  • Microservices Architecture: Each module is an independent service from day one
  • Plugin-First Design: Extensible architecture supporting static and dynamic modules
  • Security-by-Design: Built-in authentication, authorization, and audit capabilities
  • Observability: Comprehensive logging, metrics, and tracing
  • API-First: OpenAPI/GraphQL schema generation

Contributing

When contributing to the platform:

  1. Review relevant ADRs before making architectural decisions
  2. Follow the task structure defined in the Stories
  3. Update documentation as you implement features
  4. Ensure all tests pass before submitting changes