Category
Stack & engineering
The locked, opinionated stack behind the Novus ecosystem and how it is built: code-as-content architecture, type-safe content, edge rendering, and the AI-assisted engineering workflow that ships it solo.
26 articles
About the Stack & engineering thread
The technical record of how this ecosystem is built. The stack is deliberately locked and narrow (one framework, one styling approach, content as typed code rather than a CMS) because a solo operation cannot afford the tax of maintaining variety across nine apps.
Content-as-code is the decision with the longest reach, and several articles work through its consequences. When every article, tutorial, and app statistic is a typed TypeScript object, a broken internal link, a missing image, or a renamed app becomes a compile error rather than a support ticket. The cost is that content edits go through a build; the benefit is that content cannot silently rot.
The AI-assisted engineering material is written from production experience rather than demos: where frontier models genuinely compress the work, where the review burden eats the gain, and what has to be true of a codebase before either is possible.
What this topic covers
- The locked stack, and why narrow beats flexible for a small team
- Content-as-code: typed registries, build-time validation, and what it prevents
- Edge rendering, caching strategy, and static generation choices
- Shipping production work with frontier AI: where it helps and where it costs
- Testing and release discipline for a small operation, including zero-downtime content deploys
Who it's for
Engineers building content-heavy sites, solo developers maintaining several products, and anyone weighing AI-assisted development honestly.
26 articles in this thread, newest first. Every one is free to read with no signup.
10 articles in this threadReset filters
