TL;DR: The blog is our new long-form format for shipping product notes, technical writeups, and small launch stories in a way that feels native to unblob.ai.
We needed an editorial surface that could carry more context than a changelog entry and more structure than a short announcement.
The blog is that missing layer. It lets us publish notes that explain why a feature exists, how it should be used, and where it fits into real extraction workflows.
Why the blog exists
Product teams usually end up with too many places to explain things: release notes for shipping, docs for reference, and social posts for launch energy.
That leaves a gap for the in-between story: the practical narrative around how a feature actually behaves once it meets real files, messy pages, and production constraints.
The blog fills that gap.
It is where we can write about:
- extraction edge cases we keep seeing in the wild
- the tradeoffs behind parser and UX decisions
- small workflow patterns that help teams go from URL or file to clean output faster
A layout built for technical writing
The design direction is inspired by editorial product posts with strong structure: a clear title block, a metadata rail, a sticky table of contents, and code that feels like part of the story instead of a generic embed.
That matters because technical writing is easier to trust when the layout makes hierarchy obvious.
Readers should be able to scan the shape of an article before they commit to every paragraph.
Content lives in MDX
Every post is authored in MDX under content/ and rendered through the app directly.
That keeps writing close to the codebase, which is useful when a launch note needs links, code, headings, and small interactive affordances like anchor copying and code copying.
import { getBlobEntry } from "@/content/blob";
const article = getBlobEntry("introducing-blog", "en");
if (!article) {
throw new Error("Missing article");
}
The important part is not the helper itself. The important part is that a post is now a first-class part of the product, not an afterthought.
What comes next
We will use the blog for feature launches, implementation notes, and compact playbooks around extraction work.
Expect posts that stay close to the actual product surface: file pipelines, URL ingestion, markdown cleanup, and the decisions that shape output quality.
If you are building with unblob.ai, the blog should become the fastest way to understand how a capability behaves before you wire it into production.