Publishing

Publishing delivers a finished article to its destination — the built-in Terradium CMS or your own webhook. Articles can publish automatically when they finish, or stay as drafts until you publish them by hand.

How publishing works

When an article is published, Terradium delivers it to the project's target. Delivery runs on a background sweep (about once a minute), so a just-published article may show Publishing… briefly before it goes live. A project's publish state is derived from what's actually been delivered, so it always reflects reality.

Auto-publish vs draft

This is set per project under project settings → Publishing → After generation:

• Save as draft (default) — finished articles wait as drafts for your review.
• Publish automatically — finished articles are delivered the moment they complete, no extra click.

Publish targets

Also in project settings, choose where published articles go:

• Terradium CMS — a built-in content store served read-only by the public content API. Best if you want to pull posts into your own frontend by API key.
• Webhook — Terradium POSTs the finished article as a signed JSON payload to your URL, so you can ingest it into your own system. Verification details are in the API reference.

Manual publish

When auto-publish is off, you publish on demand:

• From an article, click Publish (or Retry publish if a delivery failed).
• From the Publish screen's Drafts tab, publish a single article or use Publish all to send every draft for the selected project.

The publishing queue

The Publish screen has three tabs:

• Drafts — finished articles not yet published.
• Published — live articles, with their slug, a copy URL action, and an Unpublish button.
• Queue — in-flight and failed deliveries, with retry counts and any error. Failed rows can be Retried; pending rows can be Cancelled.

Publish states

An article shows one of these states:

• Draft — finished but not published.
• Publishing — queued or mid-delivery.
• Published — live (served by the API or delivered to your webhook).
• Failed — a delivery error you can retry.
• Unpublished — previously live, now taken down.

Unpublishing

You can take a published article down at any time — from the article's publishing card or the Published tab — with Unpublish. It stops being served by the public API; you can publish it again later.