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 pipeline taking raw images through stages — generate a draft alt text, rename to a meaningful filename, strip EXIF, human review — and out to a published image with complete, clean metadata

    Field guide · Jun 17, 2026

    Automating alt text and image metadata at scale

    A practical approach to image metadata when there are too many images to handle by hand: what metadata actually covers, why alt text is for people before search engines, how to use AI to draft alt text without shipping confident nonsense, generating filenames and stripping EXIF as a pipeline step, and a build-time check that keeps the whole library honest.

    • Automate the toil, keep the judgement
    • AI drafts alt text; a human approves
    • Strip EXIF; check it at build

    NSS Background Remover

    Read
  2. A webhook shown as event-driven push: an event happens in one app, which sends a small message to a second app the instant it occurs, contrasted with polling where a second app repeatedly asks "anything new yet?" on a clock

    Field guide · Jun 16, 2026

    Webhooks explained for people who don't write code

    A no-jargon explanation of webhooks for non-developers: the postcard-versus-phone-call analogy, how webhooks differ from polling and why that matters, what is actually inside a webhook message, how to wire two tools together with a no-code platform, and the few reliability and security details — retries, verifying the sender, acknowledging receipt — that keep an automation from silently failing.

    • One app pings another instantly
    • Push, not constant polling
    • No code needed to use them

    Novus Stream Solutions (hub)

    Read
  3. An automation step retried three times producing exactly one result because an idempotency key deduplicates the repeats — versus a naive step that produces three duplicate records

    Field guide · Jun 15, 2026

    Idempotency and safe retries: no-code automations you can re-run without fear

    Why automations fire twice, what idempotency actually means in plain terms, the keys and checks that make a step safe to re-run, how to handle the steps you do not control, and a simple checklist for building no-code workflows that survive retries without double emails, double charges, or ghost records.

    • Why automations fire twice
    • Idempotency in plain terms
    • A safe-retry checklist

    Novus Stream Solutions (hub)

    Read
  4. Content posts flowing into a row of validators — missing image, broken link, bad metadata, schema check — leading to a pass/fail gate that blocks the deploy when any check fails

    Field guide · Jun 11, 2026

    A build-time validation gate: catching content errors before deploy

    How to build an automated gate that validates a whole content catalog before it can deploy: the classes of error worth checking (missing assets, broken internal links, malformed metadata, schema gaps), why running them at build time beats hoping at run time, making failures specific and fast to fix, and keeping the gate honest as it grows.

    • Silent rot becomes a build failure
    • Author catches it, not the reader
    • Specific errors, blocking the deploy

    Novus Stream Solutions (hub)

    Read
  5. A support pipeline with automation layers — self-service, triage, macros, AI drafts — and human checkpoints at every exit

    Field guide · Jun 10, 2026

    Support automation that stays human: macros, AI drafts, and escalation paths

    A layered design for small-team support automation: self-service that deflects honestly, triage that routes instead of replies, macros written like humans, AI drafts with a human on send, and the escalation paths that keep edge cases from being crushed by templates.

    • Automate typing, not judgment
    • AI drafts, human sends
    • Always a visible path to a person

    Novus Stream Solutions

    Read
  6. An automated pipeline with a single deliberate human checkpoint placed before the high-stakes, irreversible step, while routine steps flow through automatically

    Field guide · Jun 10, 2026

    Human-in-the-loop automation: where to keep a person in the workflow

    Why full automation is the wrong default for some steps, the four signals that a step needs a human (high stakes, low reversibility, fuzzy judgment, trust-defining), how to design a checkpoint that adds value instead of friction, and how to move the line over time as you build confidence.

    • When NOT to automate
    • Four signals for a checkpoint
    • Designing the human step well

    Novus Stream Solutions (hub)

    Read
  7. Automating SVG hero art: a house style as code generates unique, on-brand art per post at scale

    Field guide · Jun 8, 2026

    Automating SVG hero art for a 150-post blog

    How to automate original hero and inline art across a large blog: a house style as code, topic-specific content in a consistent frame, why SVG beats raster here, and keeping every post visually unique at scale.

    • Original art per post
    • House style as code
    • Unique at scale, on-brand

    Novus Stream Solutions

    Read
  8. Turning a changelog into content: each real feature becomes an article connected to docs

    Field guide · Jun 7, 2026

    Turning a changelog into content: a repeatable system

    A repeatable system for turning a changelog into content: why the changelog is a content goldmine, how to expand a release note into an article, and how to keep it honest and connected to docs.

    • Every feature is an article
    • Release notes into posts
    • Honest, connected content

    Novus Stream Solutions

    Read
  9. Four automated email flows branching from store events: signup, cart abandonment, purchase, and going quiet

    Field guide · Jun 7, 2026

    The email automation flows every small store needs

    The core automated flows — welcome, abandoned cart, post-purchase, and win-back — what each one does, why it recovers revenue, and how to set them up without a big team.

    • Welcome & abandoned-cart flows
    • Post-purchase & win-back
    • Set once, runs in the background

    Novus Stream Solutions (hub)

    Read
  10. The honest workflow of building a marketing site with Claude Code: division of labor and guardrails

    Field notes · Jun 5, 2026

    Building a marketing site with Claude Code: the honest workflow

    A grounded account of building a marketing and content site with Claude Code: the code-as-content architecture that fits, where AI assistance genuinely helps, where it needs a human, and the quality guardrails that keep it from producing slop.

    • Honest division of labor
    • Code-as-content fits AI
    • Guardrails against slop

    Novus Stream Solutions

    Read