// the take
Daniel Roe's personal site and blog, built on Nuxt. He explicitly uses it as a testbed for new Nuxt features, custom build tooling, and an AT Protocol (Bluesky) integration rather than as a reusable site template. Most useful to developers who want to see how a Nuxt core team member structures a real, production-sized Nuxt app.
Custom Nuxt modules (tree-shake, dedupe-hoisted, reduce-chunks, build-cache) demonstrate concrete bundle-size and build-time tricks that aren't documented anywhere official. The hand-rolled admin CMS (Nitro server routes + GitHub OAuth, covering talks, projects, AMA, uses-page, invites) is a solid real-world example of a bespoke admin panel built without a framework. The AT Protocol/Bluesky work (lexicons, comment sync, cross-posting to Mastodon/LinkedIn/dev.to) is one of the more complete open examples of building on AT Protocol outside Bluesky's own apps. CI includes less common patterns like an agent-scan workflow and an autofix workflow worth looking at for inspiration.
The README explicitly warns against copying code directly — this is a playground, so APIs, auth flow, and conventions shift as experiments get swapped in and out, making it a bad base to fork. The custom build-time modules have no visible unit tests, which is exactly the kind of code that silently breaks on a Nuxt or Vite upgrade. The admin panel and auth are tightly coupled to Daniel's own GitHub account and invite system, so it isn't reusable as a general-purpose CMS. Parts of the repo lean on unreleased or bleeding-edge Nuxt internals given its stated purpose, so expect pieces that don't work against the latest stable Nuxt release.
We read the README, the directory tree and a key source file in October 2026. Nobody pays to be listed. How we judge →