1 min readperformance
Static-first pages, dynamic only where it matters
A simple rule for personal sites: make marketing and content static; keep mutations behind small API routes.
Marketing pages, articles, and project write-ups rarely need per-request personalization. Generate them statically or revalidate on a cadence so edge caches stay hot.
When to use dynamic rendering
Use server dynamics for authenticated dashboards, form submissions, and anything that must reflect private state. Keep those routes small and well isolated.
Related ideas
Pair static content with incremental static regeneration when you want fresh data without sacrificing the default fast path for anonymous visitors.
Vite vs Webpack: development speed is not the same as build architecture
NewerBuilding a modular personal site with MDX