Architecture Executive Summary¶
Summary¶
Stakeholder-level summary of SkyCMS architecture, deployment patterns, and governance model.
Reading path: Architecture overview > Architecture Executive Summary > Core Platform Architecture > Architecture Decision Matrix
One-page summary¶
SkyCMS is a multi-tenant CMS platform with clear separation between authoring and public delivery. The platform supports static, dynamic, and hybrid delivery patterns so teams can choose the right balance of performance, flexibility, and operational complexity.
What is stable across all modes¶
- Tenant-aware architecture is foundational and enforced early in request flow.
- Editor and Publisher remain independently deployable.
- Publish actions are the control point for public content lifecycle.
- Storage, CDN, and database providers are pluggable behind consistent abstractions.
Delivery options at a glance¶
| Delivery option | Best for | Primary benefit | Primary tradeoff |
|---|---|---|---|
| Static | Public, cache-heavy content estates | Lowest request-time cost and high edge performance | Less request-time flexibility |
| Dynamic | Interactive or personalized experiences | Maximum runtime flexibility | Higher runtime complexity and cost |
| Hybrid | Mostly static with protected or specialized routes | Balance of performance and control | Requires clear route governance |
Governance and decision model¶
- Architecture choices are backed by ADRs.
- Mode selection uses the architecture decision matrix.
- High-impact changes should pass the architecture review checklist.
Current architecture trajectory¶
The architecture documentation model is moving from scattered topic references to a structured, comparable framework:
- Core platform architecture as the canonical base model.
- Mode-specific profiles with consistent sections and route-class guidance.
- Decision matrix for selecting static, dynamic, or hybrid patterns.
- ADR summary mapping for rapid governance onboarding.