How this site is built

A quick tour of the stack behind peery.me, for the curious.

The stack

Layer	Choice
Framework	Next.js 16 (App Router, Cache Components)
UI	React 19, Tailwind CSS 4, Motion
Content	MDX files in the repo
Auth	Better Auth + Drizzle on Neon Postgres
Payments	Stripe Checkout + webhooks
Email	Resend
Files	Vercel Blob

Content is just files

Posts are .mdx files with typed frontmatter. A cached loader reads them at build time:

src/lib/content.ts

export async function getPosts(): Promise<Post[]> {
  "use cache"
  cacheLife("max")
  return load("blog")
}

Because the loader is cached, every post is prerendered into the static shell and served from the edge. Publishing is a git push.

Payments without the success-page trap

Fulfilment happens in the Stripe webhook, never on the success page. Customers don't always make it back to your site, but webhooks always arrive (and retry).

That's the gist. Questions? Get in touch.