Product blog

Product blog

Product updates, field guides, and field notes—each with links to docs and the hub where relevant. High-level milestones also appear on the changelog.

  1. 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.

    • One App Router project
    • components/sections pattern
    • Shared layout, metadata, sitemap

    Engineering

    Read
  2. 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.

    • IndexedDB local saves
    • Accounts add cross-device durability
    • Match saving to the product

    Novus Stream Solutions

    Read
  3. 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.

    • No CMS, no database
    • Posts are typed TS objects
    • Content ships with the code

    Engineering

    Read
  4. 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.

    • A union type for doc links
    • Structured sections, not raw HTML
    • Broken content = build failure

    Engineering

    Read
  5. A model registry being checked against the Hugging Face API, with unverified entries flagged and replaced

    Field guide · Jun 1, 2026

    Shipping a model registry you can trust: auditing against Hugging Face

    An engineering note on auditing an AI model registry for honesty — verified IDs, real sizes and licenses, and classical baselines labelled as such.

    • Audited vs HF API + Transformers.js v3
    • Five unverified IDs replaced
    • Classical baselines labelled honestly

    Stack & engineering

    Read