Welcome to oriz-blog

Welcome to oriz-blog — the long-form writing arm of the chirag127/oriz family of static sites. Most of what I publish here is engineering work I'd otherwise forget: notes on shipping small things, debugging stories with the fix written down so I don't repeat the search, and the occasional opinionated take on a tool I've used long enough to have one.

What you'll find

Three buckets, roughly:

• Engineering notebooks. Architecture decisions, debugging walk-throughs, and the kind of "I just spent four hours on this" post that's mostly for me but might save you the same four hours.
• Open-source ships. Whenever I push a new oriz-family site (eleven of them and counting), the cross-post engine (oriz-omnipost) pings here and the newsletter and dev.to and Bluesky in one go.
• Books and finance. The non-engineering side of my reading. Less frequent, more digested.

Every post lives as an .mdx file in this repo's src/content/posts/ directory — no headless CMS, no admin login, no second source of truth. See the markdown-in-repo-only decision for the why.

Code samples come from elsewhere

Per the family-wide code-embed lock (Batch 6), runnable code goes into a StackBlitz or CodePen project, or a GitHub Gist for non-runnable snippets, and gets embedded back into the post. This blog post embed pattern keeps the MDX file short, the runtime example always-up-to-date, and the JS bundle out of the static build.

A taste:

For non-runnable snippets, a Gist:

How to read

The chrome here is intentionally minimal. The header has a search box that hits the family-wide MultiSearch (looks across every site in oriz, not just this blog). The footer has the three feeds — /rss.xml, /atom.xml, /feed.json — pick whichever your reader prefers. Comments are at the bottom of each post, gated behind a "Load comments" click so the iframe doesn't ship until you ask for it.

If something here helps you, the best thank-you is a star on chirag127/oriz or a reply on Bluesky.

— Chirag