Architecture
Serverless Is A Content Strategy
For a personal site, serverless is not just infrastructure: it shapes how often you publish, how much you maintain, and how safely you expose dynamic features.
A portfolio does not need a database just because it has content. It does not need a server just because it has a form.
When most pages are generated at build time, the publishing workflow becomes simpler: content is source-controlled, reviewable, and portable.
The dynamic layer should stay narrow. In this site, that means contact intake only.