Log in Get started

Compose

The Content Studio is where captures become real, structured content. A composition is built from elements — headings, rich text, quotes, lists, code, images, embeds, and calls-to-action — so one piece of writing can later be reshaped into any output format without losing structure.

Building the page

Add element, above the element list, adds a block to the bottom of the composition — text, heading, quote, list, code, call-to-action, or image. Each block has a small trash icon in its header to remove it again; removing a block that holds an uploaded image deletes the image too.

You don't have to start from a blank page. A composition drafted from a capture arrives with its elements already written, and templates come with their blocks laid out ready to fill in.

The editor

Text and heading elements use a rich-text editor with the formatting you'd expect; other element types have focused editors of their own — a list, for instance, is one item per line, with a switch for bullets or numbers. Everything autosaves as you type (watch the indicator in the header), and version history lets you compare and restore earlier states with a side-by-side diff.

AI, element by element

Every element carries inline AI actions:

  • Rewrite — same idea, better sentences.
  • Expand — grow a stub into a full passage.
  • Clarify — simplify without changing meaning.
  • Critique — get honest editorial feedback in a side panel.

Rewrites and expansions are steered by your workspace's brand-voice profile — a distillation of how you write, learned from your own samples — so AI output sounds like you, not like a model. You'll always see a preview before any AI change is applied.

Templates

The templates gallery holds reusable composition skeletons ("hook → story → lesson → CTA"). Instantiating one pre-populates a fresh draft with the template's slots so you start from structure instead of a blank page.

Drafting from captures

When a composition is born from a capture, the AI drafts the full element tree from the capture's content, and the lineage stays linked — you can always trace published posts back to the original spark.