// the find
ttttonyhe/ouorz-mono
A Monorepo for My ( :earth_asia: Personal Website / :microscope: Academic Profile ) and { Other Related Projects }
A personal website monorepo for lipeng.ac, combining a Next.js frontend that pulls content from a headless WordPress CMS with a self-hosted Umami analytics fork and a shared component library. It's one developer's production site made public — useful as a reference for how to wire these pieces together, not as a starter template you'd fork directly.
Turborepo with pnpm workspaces is set up correctly — remote caching, per-package scripts, and a clear filter pattern that makes running cross-package commands predictable. The WordPress-as-headless-CMS pattern is genuinely useful: custom theme functions.php shapes REST API responses instead of fighting with plugins, and all uploads go to external object storage so the container stays stateless. Cypress E2E tests exist and run in CI via GitHub Actions, which is more than most personal sites bother with. The Docker setup for WordPress includes sensible Redis and SSL options via WORDPRESS_CONFIG_EXTRA rather than hardcoding them.
Redux + Redux Saga for a personal blog is a lot of machinery — this is the author's own README admitting it's 'completely overkill', and they're right. Anyone studying this to learn state management patterns will pick up habits they'd need to unlearn for most real projects. The analytics app is a fork of an older Umami version (pre-1.0 API shape, Prisma with raw SQL migrations) rather than a dependency, which means security patches and upstream improvements don't flow in automatically. The component library (twilight-toolkit) has a 'Foundation/Adaptor implementation coming soon' note that's been there long enough to suggest it's never shipping. There's no multi-tenancy or auth story beyond the single-owner assumption baked into the WordPress setup, so the infrastructure patterns don't transfer to anything serving real users without significant rework.