Mission log
Static-First Deployment Notes
Why the MVP targets static hosting first while preserving a standalone container path.
Static hosting keeps the operating model small. The portfolio compiles routes, posts, projects, RSS, sitemap, and robots metadata into files that can be served from a CDN.
Why static first?
The site does not need a database or always-on server for the MVP. Content lives in MDX, animation runs on the visitor's device, and the hosting bill is mostly static asset delivery.
Why keep Docker?
A standalone Docker image makes future backend features easier to add. Contact forms, comments, auth, or private dashboards can be introduced later without discarding the frontend architecture.
Deployment security
Cloudflare deployments should use a scoped Pages token. AWS deployments should use GitHub OIDC to assume a role instead of storing long-lived access keys.