AI NativeContent Studio turns a measurement gap into a publishable draft. The loop is: identify a gap in the WHY Ledger or Opportunities, generate a draft, publish it, then re-scan to see whether the number moved. See Opportunities for where the gaps come from.
Generating a draft
The generate form takes a topic, an optional target AI query, an optional gap note, a channel, and a lever. When you click "Generate with AI," the platform writes a draft grounded in your product's positioning and verified facts.
The WHY Ledger and Opportunities pages have a "Create content" action that pre-fills the form before you land here. You can also type topic and gap context manually for topics not yet in those views. Every draft enforces hard rules at generation time: no competitor brand names, no em-dashes or en-dashes, no unverifiable figures, and the current year.
Draft statuses
Each draft carries one of three statuses:
Draft - the generated text exists and is editable. It has not been approved for publication.
Approved - reviewed and marked ready to publish. Approved drafts are candidates for CMS publishing.
Published - the draft has been sent to the connected CMS or manually marked published. A URL field records where it lives.
You move between statuses using the buttons below each card. Clicking "Publish to CMS" pushes to the connector and sets the status automatically.
Publish to CMS
The "Publish to CMS" button appears on each draft card. Clicking it sends the draft to whichever connector is configured in Workspace > Settings. The platform shows a confirmation prompt before sending.
For a webhook connector, the draft payload (title, angle, body, target query, channel, lever) is posted as JSON to your configured endpoint. What happens next depends on how your endpoint is set up.
For a WordPress connector, the platform creates a post in your WordPress site with the title and body converted from markdown to HTML. The post lands as a draft inside WordPress, not as a live page. A human reviews and publishes it from within WordPress.
If no CMS connector is configured, the button returns an error telling you to add one in Workspace > Settings.
Exporting and viewing a draft
Each draft card has an "export .md" link that downloads the draft as a markdown file (title, angle, body, and the target AI query in a comment). Draft bodies are collapsed by default; the "view draft" toggle expands a scrollable markdown preview.
Questions
Where do the pre-filled topic and gap fields come from?
When you navigate to Content Studio from the WHY Ledger or Opportunities page using the "Create content" action, those pages pass the topic, target query, and gap context as prefill values into the generate form. Creating drafts this way connects each piece of content directly to the measurement gap it is trying to close.
Does Content Studio enforce any content rules automatically?
Yes. Every generated draft is bound by rules applied at generation time: no competitor brand names, no em-dashes or en-dashes, no figures the brand cannot verify, and the current year. These rules are not adjustable; they apply to every draft regardless of who generates it.
What is the difference between marking a draft published and clicking Publish to CMS?
Marking a draft "published" via the status button changes the status and lets you record a URL manually. It does not send anything to your CMS. "Publish to CMS" actively sends the draft to the configured connector endpoint and records the returned URL if one is provided.
Can a published draft be moved back to draft or approved?
Yes. The status buttons are always visible, so a published draft can be set back to approved or draft at any time. The published URL field is not cleared automatically; you can edit or remove it manually.
What happens if the CMS connector call fails?
The platform shows the error returned by the connector. The draft status is not changed. You can retry by clicking "Publish to CMS" again once the connector issue is resolved.
Does the WordPress connector publish the post live?
No. The connector creates a draft post inside WordPress, not a live page. Someone on your team reviews and publishes it from within WordPress.
Who can generate drafts and change statuses?
Members with the mutate permission (editors and admins) can generate drafts, change statuses, and trigger CMS publishing. Read-only members can view draft content but cannot generate or change anything.