Content review and public blog

Draft review

Content workflows save drafts for human review. The Content area lists drafts and their states, opens the generated body and metadata, and allows authorized users to approve eligible work.

Typical states move from draft or review to approved, then published when delivery is confirmed.

EDITORIAL DELIVERY

A generated draft becomes approved public content

1. 01

   Draft

   A workflow creates a reviewable content artifact.

2. 02

   Review

   A human checks accuracy, tone, and publication risk.

3. 03

   Approve

   Authorization changes the content's delivery state.

4. 04

   Publish

   The hosted route and SEO projection become visible.

Approval and delivery are intentionally separate. Approval records editorial authorization; publication records that a destination accepted or exposed the content. Do not manually mark an item published before confirming its destination reference.

Public blog

Approved publishable content can appear on the public blog. Blog pages include article metadata and are available without an authenticated session.

Publication eligibility is enforced by the server; a guessed draft URL does not expose unapproved venture content.

The public route reads from the published-content projection rather than directly rendering workflow drafts. Soft-deleted or non-visible records behave as not found. Sitemap and feed consumers use the same visibility boundary through read-scoped API routes.

External publication state

When content is delivered outside the hosted blog, the product can record the external destination, identifier, URL, publication time, and error details.

Only two destinations deliver on their own today:

• the hosted blog, the complete supported path;
• X (Twitter) threads, in Beta — credentials must be added by hand as an API key resource named for Twitter, there is no connect wizard, and a delivery failure is recorded without failing the rest of the run.

Automatic delivery to any other channel, including LinkedIn, is not available. Content can be adapted to those formats, but you post it yourself in that channel and record the resulting URL.

What to expect

The hosted blog is the supported end-user publication path. Use the review actions shown on the content item, and complete external-channel delivery in the connected channel when no destination action is offered in Organ.