Five Posts, One Tool

What we've been building — and what to read first

scsiwyg is a headless, API-first blogging platform for developers. No editor, no CMS, no browser tab. You POST a JSON document and your post is live. That's the whole contract.

We've been publishing here since day one — via the API, from the IDE, the same way we're telling you to. Here's what exists and what's worth your time.

Ranked for sharing

1. Headless Is the Head

The philosophical case — why no editor is the right design

The best entry point if you've never thought about why a blogging platform shouldn't have an editor. Sets up the whole argument in a short read.

🔗 scsiwyg.com/making-scsiwyg/headless-is-the-head

X copy: A blogging platform with no editor sounds like a joke. It's actually the only design that makes sense for developers. Here's why. →

2. The IDE Blog Is for the Person Who Forgets to Write

The audience — who this is actually for

Not for people who want to write essays. For people who had three clear sentences at 11pm and didn't write them down. If that's ever been you, this one lands.

🔗 scsiwyg.com/making-scsiwyg/the-ide-blog-is-for-the-person-who-forgets-to-write

X copy: The best developer blogs die because the friction of publishing is higher than the impulse to write. Here's what fixes that. →

3. The Product Is Also the Story

The strategy — how building in public becomes the marketing

Every post about building scsiwyg is published via scsiwyg. The documentation is the proof. The arc of posts is harder to fake than a landing page.

🔗 scsiwyg.com/making-scsiwyg/the-product-is-also-the-story

X copy: Every post I write about scsiwyg is published via scsiwyg. The dogfooding loop is also the marketing strategy. Here's why that works. →

4. Making scsiwyg

The origin — what problem it actually solves

Where it started. One frustration, one decision to build the tool instead of tolerating the friction.

🔗 scsiwyg.com/making-scsiwyg/making-scsiwyg

X copy: Every blogging platform I tried had an editor I didn't want. So I built one with no editor at all. →

5. Ambient Publishing

The concept — publishing as a byproduct of working

The idea that the best post is the one you didn't decide to write — it happened because you were already working and the threshold was low enough you didn't notice you crossed it.

🔗 scsiwyg.com/making-scsiwyg/ambient-publishing

X copy: There are two kinds of blog posts: ones you decide to write, and ones that happen while you're working. Only one of those produces an honest record. →

The thread version

If you want to introduce scsiwyg on X as a thread:

1/ I built a blogging platform with no editor.

Here's the full argument for why that's right. 🧵

2/ Most developer blogs die because publishing lives in a different place than the work.

You have to context-switch. That switch has friction. The friction accumulates. The blog stops.

3/ scsiwyg is an API. POST a JSON doc with your markdown, get a live post.

No browser tab. No login. No editor.

From the terminal, from Claude, from any tool that can make an HTTP call.

4/ Once it became an MCP server, the AI that helps you write code can also publish the post about the code — without breaking context.

That's ambient publishing. The post happens as a byproduct of the work.

5/ Five posts explaining the whole thing:
→ Headless Is the Head
→ The IDE Blog Is for the Person Who Forgets to Write
→ The Product Is Also the Story
→ Making scsiwyg
→ Ambient Publishing

The blog is live. The API is live. The MCP server is live.

scsiwyg.com