Making scsiwyg

29 March 2026#scsiwyg#devlog#building-in-public

scsiwyg started with a simple frustration: every blogging platform I tried had an editor I didn't want.

I don't want a text box in a browser tab. I write in my IDE. I think in code. I wanted to publish the same way I ship everything else — by POST-ing a JSON file.

So I built scsiwyg.

What it is

scsiwyg is a headless, API-first blogging platform. There's no CMS, no rich-text editor, no drag-and-drop. You write your post as a JSON document and POST it to the API. That's it.

json

{
  "slug": "my-first-post",
  "title": "My First Post",
  "date": "2026-03-29",
  "body": "# Hello\n\nThis is my post.",
  "tags": ["hello"]
}

From your terminal:

bash

curl -X POST https://scsiwyg.com/api/scsiwyg/{username}/posts \
  -H "Authorization: Bearer YOUR_TOKEN" \
  -H "Content-Type: application/json" \
  -d @post.json

Or from Claude Code, Cursor, Copilot — any AI IDE that can make HTTP calls.

Why API-first

Because the best publishing workflow is the one that's already part of your flow. I'm in my editor all day. Switching tabs to a web CMS breaks the thread. With scsiwyg, I write a markdown string inside a JSON file, run one curl command, and the post is live.

AI-powered IDEs make this even better. I can ask Claude to draft a post, write it directly into a JSON file, and POST it — without ever leaving the editor.

This post

This post was published via the scsiwyg API. No web interface. No login form. Just a JSON payload and a Bearer token.

That's the whole point.

𝕏 Post