Workspace documents, imports and writing rules

Documents are everything a draft reads before it's written. Edit them, import brand guides from Drive, Notion or Confluence, and set words drafts must never use.

Updated

Workspace documents are the brief, voice, rules and reference material every draft reads before it’s written. You manage them on the Documents page, and you set the words drafts must never use under Settings → Writing rules. Wavefront’s own house rules apply on top of both.

What’s on the Documents page

Saving a plan creates the first documents: the strategy, voice, keywords, calendar and ideas, plus the workspace profile. You can add your own, such as a style guide, product facts or past posts. The page groups documents by folder, with a summary of each.

Files the app manages itself (the workspace profile, a strategy’s calendar, keywords, ideas and backlog files, and the writing rules file) aren’t listed with the rest. Owners see them in a collapsed System files section, each with a link to where it’s edited.

Edit a document

Owners and editors can:

  • Choose a document, then Edit to change its text. Press ⌘S or choose Save.
  • Choose New document, give it a Path, and Create it.
  • Delete a document. Drafts stop reading it.
  • Open History and restore any earlier version. Restoring creates a new version, so nothing is lost.

Every change is a new numbered version, and the message after each change offers Undo. A draft’s Details box links to the documents version it read. Viewers can read every document.

Import from Google Drive, Notion or Confluence

You can bring brand guides, product docs and past posts in as documents. The source stays unchanged.

  1. An owner connects the source under Settings → Integrations → Document imports: Google Drive (Google Docs, PDFs and Markdown files you pick), Notion (pages and databases you share with the Wavefront integration) or Confluence (spaces and pages on the site you allow).
  2. On Documents, choose Import and pick what to bring in. Only the owner who connected a source picks from it.
  3. Preview what would come in, then import it. It lands under imported/ as one new version. One import brings in at most 50 documents.
  4. Optionally set it to Resync daily, or leave Resync on demand.

The message after an import offers Undo. Editors can resync imports, change their schedule or stop tracking them. Each imported document starts with a note of its source and import time.

If the workspace profile lists an imported document as a rule every draft must follow, the preview warns you. With a daily resync, anyone who can edit the source can change those rules without review, so consider resyncing on demand.

Set writing rules

Owners open Settings → Writing rules to list the site’s own words and phrases:

  • Never use: a draft can’t be approved until these are gone. The editor rewrites them.
  • Avoid: flagged for the editor, who rewrites them unless they’re the right word.
  • Words we use literally: never flagged, even when a rule would, such as “underscore” on a site about film music.

Each entry can have an optional reason. Choose Save writing rules when done. The page also shows how many built-in rules apply, with examples. Owners get Advanced: regular expressions for pattern rules.

Wavefront’s house rules

Some rules apply to every workspace without being listed as documents. For articles, among others:

  • Never mention how the article was made: the brief, the research, the rules or the tools.
  • No padding. An entry you would have to excuse is left out.
  • Numbers, dates, prices, rankings and quotations come from the evidence or your documents.
  • A numbered title gets exactly that many entries.
  • Factual superlatives and firsts need evidence. A “best” pick is the site’s judgment.
  • Sources go where your site wants them, with no added “Sources” section.

Every draft is also scanned for common AI-writing tells, leftover chatbot text and placeholders. Leftover tokens, chatbot phrases and placeholders block approval. Most other tells are warnings, unless your writing rules block them.

Your documents add to these rules and win where they’re more specific. If a document repeats a house rule, you can cut it from the document; the rule still applies. See how drafts are checked.

If something goes wrong

  • A document is too large. Drafts can read only so much. Shorten or split documents, or delete ones drafts don’t need.
  • The page says it’s managed in Git. That workspace’s documents come from a repository and are read-only here.
  • Changes made by an agent are holding up auto-approve. See autopilot and auto-approve.

Still need help? Email support@adwave.com with your workspace name and what you were doing.