My website has been running on the same codebase since 2021: a Sapper app — Svelte’s now-deprecated predecessor — with Tailwind 2, a service worker I never looked at again, and a Cloudflare Worker proxying GitHub data for a 3D contributions chart nobody asked for. It worked. It also bit-rotted quietly for five years, which is exactly the kind of debt a personal site shouldn’t have.
So I tore it down and rebuilt it. This post is about what changed and why.
Why rebuild?
The old stack did two things a personal site doesn’t need. First, it shipped a client-side router and hydration bundle for a handful of pages that barely had interactivity. Second, its build pipeline — Rollup, Babel, a Sapper/Polka server, a PurgeCSS post-processing step — was the part most likely to break, and the part that delivered the least value.
The new requirement list is short:
- Markdown posts, rendered at build time
- No database, no server, no client framework
- Deploy to Cloudflare Pages exactly like before
- Keep it fast, keep it readable
The new stack
Astro was the obvious fit. Static by default, content collections for the posts, and a build output that’s just HTML and CSS — which means the site can’t really break at runtime.
// astro.config.mjs
import { defineConfig } from 'astro/config';
import sitemap from '@astrojs/sitemap';
import rehypeSlug from 'rehype-slug';
export default defineConfig({
site: 'https://iamfelipenascimento.dev',
output: 'static',
markdown: {
shikiConfig: { theme: 'github-dark-default' },
rehypePlugins: [rehypeSlug],
},
integrations: [sitemap()],
});
Content collections
Posts live in src/content/posts/ as plain markdown files with a typed frontmatter schema.
The posts list, the post pages, the table of contents and the RSS feed all derive from the same
collection — one source of truth, generated once at build time.
Static output
astro build emits plain HTML into dist/, and Cloudflare Pages serves it from the edge. The
_redirects-free setup means old /blog URLs are gone for good — no redirect table to maintain
for content that was placeholder posts anyway.
What I left behind
The teardown was deliberately ruthless:
- The Sapper app, service worker and PWA manifest — no client-side routing needed
- The GitHub 3D chart and its Cloudflare Worker — fun in 2021, noise today
- Tailwind — the design system is now a single CSS file with custom properties
- The “roles” section — the same information now lives as tags on the work page
Static sites are not a step backwards. They’re a well-earned simplification.
What’s next
The site is now boring in the best way: it builds in seconds, the output is inspectable, and adding a post is committing a markdown file. That’s the whole point — the less machinery between an idea and a published page, the more likely I am to actually write.
If you’re maintaining a personal site on a five-year-old stack, consider this your sign.