A durable technical site keeps content, presentation, and deployment concerns separate. Markdown stays portable, structured metadata drives repeated layouts, and static output keeps hosting simple.
Design principles
- Keep localized interface strings in one module.
- Store release facts as structured content.
- Give images stable, predictable paths.
- Add server-side features only when a real workflow needs them.
An article can still include code:
const releaseChannel = 'github-releases';