Ghost CMS
Publish posts, newsletters, and media to a Ghost site from the Assistant while keeping publishing auditable and previewable.
Audience: Content operators and authors who publish newsletters, blog posts, or media via Nexus.
Current Version
1.0
Documentation aligned to the current operational build of Chat, Automations, Contacts, and workflow runtime.
Scope
1
A standalone documentation page with a stable URL you can share directly.
Quick Start
How the system is meant to be used
Step 1
Read the platform overview first so you understand how Chat, apps, and runtime work together.
Step 2
Start your first conversation in Chat with a real business outcome, not just a general prompt.
Step 3
Let Nexus turn that intent into a durable record, workflow, or next-step artifact.
Step 4
Connect the systems required for context, communication, and execution as setup requires.
Step 5
Move into the relevant app surface to review, manage, approve, and operate the resulting work.
Operating Principle
Chat compiles. Apps operate. Runtime executes.
Nexus is not a chatbot that happens to call tools. It is a structured operating system where conversational intent is translated into durable records, validated state, and auditable actions.
This docs site is the product-level reference for how that model works today and how the current 1.0 surfaces fit together.
Audience
Content operators and authors who publish newsletters, blog posts, or media via Nexus.
Ghost CMS
Publish posts, newsletters, and media to a Ghost site from the Assistant while keeping publishing auditable and previewable.
Philosophy
Treat CMS publishing as an explicit, auditable capability: generation, preview, and publish are distinct, reviewable steps.
Technically Managed By
- OAuth-authorized Ghost integration that issues publish credentials
- Draft/preview → approve → publish workflow with content/html payloads
- Media registration and binary upload for images and attachments
- Post metadata management (tags, authors, visibility, scheduling)
How Users Should Use and Manage It
- 1Connect Ghost in Integrations and verify site permissions before publishing.
- 2Use the Assistant to generate draft content, then open the draft for human review.
- 3Preview rendered HTML before publishing to avoid formatting regressions.
- 4Schedule or set visibility on publish if you need delayed release or member-only posts.
How It Fits in Nexus
- Enables AI-assisted content creation while preserving editorial review.
- Publishes content under the operator’s authorized account and retains audit traces.
- Supports newsletters and posts as durable artifacts surfaced in Automations or Inbox.
What Matters
- Draft generation
- Preview rendering
- Media attachments
- Scheduled publishing
Reference Notes
Next Step
Use the docs as the product contract.
As new apps and runtime behaviors ship, extend this documentation hub first so users and internal teams have one clear reference for how Nexus is supposed to work.