Creator devlogs

Write and publish through the CLI

Available in CLI 0.0.12. Use your normal Inkwell login or creator API key. Commands return JSON including the post ID and revision. The game comes from --game or your local Inkwell project config.

# Create a private draft from a Markdown file.
inkwell devlog create --game my-game --title "A bigger world" --body-file UPDATE.md
# Publish the saved draft using its publicId from the response.
inkwell devlog publish --game my-game --post POST_ID
# Or create and publish in one command.
inkwell devlog create --game my-game --title "What changed this week" --body-file UPDATE.md --publish
# List and inspect posts, including drafts.
inkwell devlog list --game my-game
inkwell devlog show --game my-game --post POST_ID
# Edit, preserving its current publication status.
inkwell devlog update --game my-game --post POST_ID --body-file UPDATE.md
# Hide a published post while retaining it as a private draft.
inkwell devlog unpublish --game my-game --post POST_ID

You can pass --body for inline Markdown instead of a file. Titles allow 160 characters and bodies allow 40,000. Creation defaults to a draft. Use the returned nextOffset with list --offset for more posts.

Safe edits and retries

Updates, publication changes and deletion carry a revision number. By default the CLI reads the current revision before writing. Pass --revision N to require the revision you previously inspected. A concurrent edit returns 409; fetch the post, reconcile changes and retry with its new revision.

Creation uses a UUID request ID. Automation can supply --request-id UUID. If a request fails with an uncertain outcome, the CLI reports that ID; reuse it with the same content to recover the original post without duplicating it. Reusing it for different content returns 409.

# Permanent removal requires explicit confirmation.
inkwell devlog delete --game my-game --post POST_ID --yes

Reading and following updates

The game page shows the three most recent published posts and links to the full archive. New and edited posts are marked relative to the previous game-page or archive visit in that browser. These markers do not sync across accounts or devices.

Follow updates via RSS on the archive subscribes a feed reader to the game's latest 20 posts. The feed is at /games/:slug/devlog/feed.xml. Public and unlisted games with playable publications can have feeds. Private-game posts remain restricted to the creator and invited testers, and are excluded from RSS.

Drafts are visible only in the creator tools. Publishing a devlog does not change the game's visibility or publish a game build. Republishing a post retains its original publication date and URL.

HTTP API

# Creator session or API key; list includes drafts.
GET /api/v1/games/:slug/devlogs?offset=0
POST /api/v1/games/:slug/devlogs
{ "title": "Update", "bodyMarkdown": "New areas to explore.", "status": "draft", "requestId": "UUID" }
GET /api/v1/games/:slug/devlogs/:postId
PATCH /api/v1/games/:slug/devlogs/:postId
{ "revision": 1, "status": "published" }
DELETE /api/v1/games/:slug/devlogs/:postId
{ "revision": 2 }
# Published posts only; normal game access rules apply.
GET /api/v1/catalog/games/:slug/devlogs?offset=0
GET /api/v1/catalog/games/:slug/devlogs/:postId

List responses contain posts and nextOffset, at most 20 per page. Single-post and write responses contain post. Raw HTML in Markdown is not rendered, and unsafe link protocols are filtered.