Resource hub

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.

15 articles

Sub-topic

All15The stack6AI-assisted engineering9

Type

All typesHighlightsGuidesField notes
  1. Push to preview URL, promote to production, and instant rollback as the solo deploy loop

    Field guide · Jun 3, 2026

    Shipping on Vercel solo: the deploy and preview workflow that keeps overhead near zero

    The deploy, preview, and rollback loop that removes the ops tax from running multiple apps as a solo operator.

    Engineering

  2. A page request producing an on-demand Open Graph image at the edge from the page title and description

    Field guide · Jun 2, 2026

    Generating social share images at the edge

    How an edge image route turns the typed post data into a per-page share card automatically, and why dynamic beats static here.

    Engineering

  3. A single Next.js app serving many hub sections, with product spokes as linked external apps

    Field guide · Jun 2, 2026

    One Next.js app, many sections: routing a hub-and-spoke portfolio from a single codebase

    How a single App Router codebase serves an entire multi-product hub, and why that beats a constellation of separate apps when one person maintains it.

    Engineering

  4. The persistence ladder: in-memory state, IndexedDB local saves, and account-backed durable saves

    Field guide · Jun 2, 2026

    Durable saves without a backend war: IndexedDB, account sync, and when you finally add login

    An engineering field note on persistence for browser tools: in-memory loss, local IndexedDB saves, the jump to account-backed durability, and matching the saving model to the product rather than the fashion.

    Novus Stream Solutions

  5. Content stored as typed TypeScript objects compiled into the site versus a separate CMS and database

    Field guide · Jun 1, 2026

    Code-as-content: why our blog is hundreds of TypeScript objects, not a CMS

    The case for treating content as code — version-controlled, type-checked, deployed with the app — instead of running a content management system.

    Engineering

  6. A union type constraining doc links and a structured section schema rejecting malformed posts at compile time

    Field guide · Jun 1, 2026

    Type-safe content: how a DocSlug union and structured sections stop broken posts

    How a few lines of TypeScript types make broken links and malformed posts impossible to ship, not just unlikely.

    Engineering

Browse every topic in the resource hub