Markdown on Alwaldend

This X Article was generated from Markdown

Wed, 30 Sep 2026 00:00:00 +0000

I’ve had the displeasure of using X’s Article editor and it has left me unsatisfied - it’s utter dogshit. Naturally, I’ve decided to avoid it altogether. There probably exists a ready-made solution, but I’ve decided to just write it myself. After all, how hard can it be?

Not that hard, to be honest. X exposes an API to upload articles in DraftJS format, so that leaves two tasks:

X Article uploader

Mon, 01 Jan 0001 00:00:00 +0000

This project compiles a blog post into an X Article draft. It has two operations with different inputs, outputs, and trust requirements:

Conversion compiles a post’s Markdown body into the DraftJS content_state document the X Articles draft endpoint accepts. It is offline, deterministic, and credential-free; it performs no network access.
Draft creation resolves the body images and article banner through the media upload endpoint, then creates an X Article draft. It is the only operation that performs network calls, and the only one that needs credentials. The uploader creates drafts only and never publishes.

Splitting the two lets a draft be produced and diffed offline before anything reaches X, and keeping the tool to draft creation means no invocation of it can make a post publicly visible.

X Article uploader

Mon, 01 Jan 0001 00:00:00 +0000

The X Article uploader creates an X Article draft from a blog post. It compiles a post’s Markdown body into the DraftJS content_state the Articles endpoint accepts, then creates a draft from it; it never publishes.

Features

Offline, deterministic Markdown-to-content_state conversion
Drafts only: no invocation can publish an article
Images resolved through the media upload endpoint by content digest
OAuth 1.0a credentials injected through the repository’s Vault flow