# Projects
All Projects notes →10 — Templates
Reusable authoring templates for ADRs, RFCs, runbooks, post-mortems, and Confluence pages across the ShipSolid platform.
Communication Templates
Copy-paste communication templates for incidents.
ADR Template
- **Status**: Proposed | Accepted | Rejected | Superseded
Alert Runbook Template
- **Alert Name**: [FILL: exact name from alerting system — must match 1:1]
Confluence Content Templates — SRE / Observability / Platform
**Space:** `OBS` or `PLT` **Parent page:** `Decision Log (ADRs)`
Service Onboarding Checklist Template
- **Team**: [FILL] - **Service(s)**: [FILL: comma-separated if multiple]
Incident Post-Mortem Template
- **Incident Commander**: [FILL: name] - **Severity**: SEV1 | SEV2 | SEV3
RFC Template
- **RFC ID**: rfc-YYYY-MM-<slug> - **Authors**: [Name(s), Role(s)]
# Internal Developer Platforms
All Internal Developer Platforms notes →1 — Why Templates Matter
Why software templates, not documentation, are the mechanism that actually makes a golden path get followed.
2 — Service Templates
Service-level templates that scaffold a new microservice with the organization's standards already applied.
3 — Infrastructure Templates
Infrastructure-level templates for provisioning the cloud resources a service depends on alongside its code scaffold.
4 — Organization Standards
How organization-wide standards, language versions, CI pipelines, security baselines, get encoded into templates rather than enforced after the fact.
5 — Template Versioning
Versioning strategy for templates so that already-scaffolded services can adopt improvements without a breaking migration.
6 — Template Governance
Governance over who can publish a template, how it gets reviewed, and how deprecation of an old template is communicated.