Why We Keep the YJTOON Blog System Tiny (and Code-Only)

The YJTOON blog is a folder of JSON files, a handful of PHP scripts, and a static generator. There is no admin UI. There are no web forms. This post explains why, and what we lose by doing it this way.

What "code-only" means here

Posts are created by running a script. They are edited by running a different script. They are archived by running a third. The scripts validate the input, write JSON atomically, and emit static HTML on build.

Why we chose it

• Durability. A JSON file in git outlives any SaaS product.
• Agent friendliness. An agent that can run php can publish a post. No token, no cookie, no CAPTCHA.
• Smallest possible surface. No admin login, no write endpoints, no DB connection. Less to break, less to patch.

What we give up

• Drafts in the browser. We draft in the editor of our choice and commit when ready.
• Live preview that matches production. We preview by running the build script locally.
• Rollback via UI. We roll back via git revert.

When this stops working

If we ever need non-technical authors, we will add an HMAC-signed write endpoint and a tiny form. Until then, the script is the interface.