The editor

The editor is where a draft becomes the team's. A draft from Create, from Ask Viewfield or from an AI visibility item opens here at /drafts/<id>: read it, revise it, mark it Final, and take it out. It is the one quiet room in the studio: no 3D, no tiles, no chat beside the document, the words and nothing else.

One document for every kind

Every draft is the same editable document, whatever its kind: a blog post, a LinkedIn post, an X post, an X thread, a newsletter or a custom piece. The kind is a label and a hint for the tone of the next rewrite; it never changes the editor. An X thread is numbered paragraphs ("1/", "2/") in the document, so there is no thread composer, no per-network preview and no character counter. Change the kind from the chip at the top; the words stay.

Every draft autosaves as you type, with a toolbar for paragraph and heading styles, lists, links, tables and images pasted into the body. Saves never overwrite a newer copy: if a teammate saved while you were editing, the save stops with your work intact and offers to keep yours or load theirs. Work typed while offline is kept on the device until the server confirms it.

The header

• Kind: the chip at the top.
• Title: click it to rename.
• Saved: whether your latest words are saved ("Saving...", or "Offline. Changes are on this device.").
• Draft / Final: where the piece stands. Final means reviewed and ready to take out; nothing is published by marking it. A published piece shows "Published on" your site and the day instead, with Edit (see Status below).
• Export: take the words out (below).
• Publish (⌘ Enter): send a blog post to your website, or copy out a social post or a newsletter (below). For a piece written for an AI visibility question, Publish leads.
• Under them: who edited it last, the Owner and Categories (who is responsible and how it is filed), History (versions), Check claims, and the trash icon.

Comments sits at the right of the toolbar, with the count of open threads.

Inline revisions

Select a sentence or a paragraph and the revision bubble appears: Shorter, Punchier, More us, Add proof, Simpler (or the keys 1 to 5), or Ask to type your own instruction ("Ask for a change to this passage"); the same bubble also holds bold, italic, a link and a comment. ⌘. (Ctrl .) opens the Ask field on the selection, or on the paragraph the cursor is in.

The rewrite is written with your whole brand context behind it, and the moment it is ready it goes straight into the document where the selection was, with no diff and no cross-outs; a row under it asks what you think. Keep (Enter) keeps it, Revert (Esc) puts the original back, and Try another (the right arrow) writes another take, up to three, which the arrow keys flip between. Clicking elsewhere keeps the rewrite. The Ask field closes when you click elsewhere, press Esc, or move or scroll away from the selection.

On a phone, the bubble docks above the keyboard as a bar of chips.

Update with AI

The one control under the draft. Say what should change ("tighten the hook", "angle this at finance leads", "cut the second section and add a closing question") and press Update. The whole piece is rewritten with your voice, the words you never say, your writing rules, your brand basics, the rule for its kind, the draft's own brief and the checks. The rewrite lands in the document the moment it is written, saved as a version, and a strip above the draft says "Rewritten in your voice" and asks Keep (Enter) or Revert (Esc); Revert puts the words from before back, as another version. Stop halts a rewrite still being written. The editor holds still while the model writes, so your last keystrokes are never lost under the rewrite.

Ask Viewfield (⌘K) can do the same from a conversation: ask for a change to the draft you have open, press Put it in the draft on the card it answers with, and the revision lands the same way, with Keep or Revert.

Never-say marks

The words you never say (Brand › Writing rules) and the anti-slop check's own list are underlined as you type, in amber, after a short pause. Click one to see the rule and two presses: Ignore skips that exact string for the session, and Fix repairs the containing paragraph and swaps the result in. The count in the toolbar toggles the underlines. The check is a plain pattern match with no model call, and your voice always outranks it.

Claim checks

Check claims saves the draft, finds its checkable factual claims and checks them against the web: each comes back as a chip in a Claims strip, Supported, Unverified or Contradicted. Press a chip for the note and, where there is one, The source. The strip says when it was checked, and the chips are advice; hide the strip when you are done. Checks run only when someone asks (here, in Ask Viewfield, or with verify_claims over MCP), spend from the allowance, and are not offered on a published piece.

Comments

Members comment on a selection: open a thread, reply, @mention a teammate (who is notified) and resolve it when it is settled. Comments lists every thread. Only workspace members take part; there are no outside share links.

Versions

Every draft keeps its history behind History: a baseline, a version around each AI edit and restore, a snapshot at most once an hour while you write, and the versions you save yourself with Save version. Restore any earlier one, or rename or delete a saved one. A restore is itself recorded, so it can be undone.

Export

Export takes the words out in whatever shape you need. Every row renders the same document.

Row	What you get
Copy as text	Plain paragraphs, stripped to what X or LinkedIn's composer accepts, ready to paste
Copy Markdown	The document as Markdown, on your clipboard
Download .md	The same Markdown as a file
Download .docx	A Word file with headings, bold and italics, lists, quotes, links and images
Download .pdf	A laid-out PDF with selectable text and working links
Open as Google Doc	A real Google Doc in your Drive
Save to Google Drive as Word (.docx)	The same Word file, saved to your Drive unconverted

Copying straight from the editor works the same way. Select some or all of a draft and press ⌘C: a plain text box (X, LinkedIn, a text field) gets exactly what Copy as text gives, with one blank line between paragraphs and each list item on its own line, and Google Docs, Word, an email or your CMS gets the paragraphs, headings, lists, bold, italics and links as the editor shows them, with no extra empty lines. Pasting an article into a draft from Google Docs or Word does not bring their empty lines along either.

The two Google rows use the workspace's Google connection, which sees only the files it creates. A manager who chooses one before Google is connected is taken through the Google sign-in and brought back to the draft, where the export finishes; a contributor sees the rows disabled with "Ask a manager to connect Google in Settings". A Word file too big for Drive's single upload has its pictures turned into linked captions first, so every word and table still goes; only a file still too big after that is refused.

Publish

Publish in the header (⌘ Enter) opens one of two trays, by kind.

A blog post, a custom piece or a piece for an AI visibility question goes to your own CMS through the Publish tray. A manager saves it there as a draft, and publishes it with a separate press. Any member can open the tray and preview.

1. Choose where it goes: a destination (your blog's collection, say). Each one shows whether it is ready.
2. Check the post details: the title, the address it will have, the excerpt and SEO fields (Suggest summary and SEO writes them for you to read before you save), the cover image, and anything your CMS requires. Preview shows exactly what will be sent, the body as your CMS will hold it; it sends nothing.
3. Save as draft in your CMS: a manager's press. It lands as the CMS's own draft; nothing goes live. Open in your CMS takes you to it.
4. Publish on your site is a separate press, offered where your CMS lets Viewfield publish one item safely. Where it cannot (a Framer project with other unpublished changes, a BaseHub commit, a pull request your team merges), you publish in the CMS and press I published it in your CMS.
5. Visible on website appears once your public page actually serves the piece, and the piece itself then reads Published. Until then the post reads Website update pending, and Viewfield keeps checking. Check (your site) again reads the page now.

If you edit the piece after its draft was saved, the post says so, and you Save the update as a draft in your CMS before publishing. A send that times out reads Outcome unknown, and Viewfield checks the CMS before anything is sent again. See Publishing.

An X post or thread, a LinkedIn post or a newsletter gets Publish this (its kind): Viewfield never posts for you. Copy as text, Open X or Open LinkedIn, a copy button per post of a thread, Copy subject, Copy preview line and Copy body for a newsletter, and the Export menu. Then paste the address where it went under "Where it was published" and press Mark as published, so the team can find it later (Unmark clears it). Marking it records the address and nothing else: the piece stays editable, Draft or Final.

Status

Status	Meaning
Writing	Still being written
Draft	Being worked on
Final	Reviewed and ready to take out
Published	Its page on your site was seen live (or a manager confirmed it). Shown as "Published on" your site and the day

Move a piece between Draft and Final with the switch in the header, or with set_content_status over MCP. Nobody sets Published by hand: a piece becomes Published when its page is seen live, whatever the road there (the Publish press, a pull request merged on GitHub, or I published it in your CMS). A published piece is final: it is read-only, and Edit reopens it as a draft. Send the update the same way, and once the page shows it, it reads Published again. While you edit, the post says Editing the live post: the page keeps the published version until then.

Viewfield reads a live page again every day. A page that answers "not found" no longer counts as live, and the piece goes back to Final.