> ## Documentation Index
> Fetch the complete documentation index at: https://docs.hiveku.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Use the Marketing Content Review Workflow

> Collaborate on blog posts and marketing copy with drafts, comments, versions, and approvals

Marketing content rarely ships without at least three sets of eyes on it — founder, marketer, SEO, legal. Without structure, that turns into email chains and "final\_v3\_ACTUAL.docx". The Content module gives you proper review, comments, versioning, and approvals in one place.

<Info>
  Path: **Marketing > Content**
</Info>

## Why Use Content Reviews

<CardGroup cols={2}>
  <Card title="Keeps versions straight" icon="code-branch">
    Every save is a version you can compare or restore
  </Card>

  <Card title="Ends the email chain" icon="comments">
    Comments live on the content, threaded and resolvable
  </Card>
</CardGroup>

## Pipeline Stages

Every piece of content moves through four stages:

1. **Draft** — owner writes and edits freely, no reviewers notified
2. **In Review** — reviewers assigned, comments and approvals collected
3. **Approved** — all required reviewers approved, ready to publish
4. **Published** — live on your site

You can customize the stages per workspace, but the default covers most teams.

## Creating Content

<Steps>
  <Step title="Open Content">
    Go to **Marketing > Content**.
  </Step>

  <Step title="Click + New">
    Pick a type — blog post, landing page copy, email, case study, social post. Each type has its own template and metadata fields.
  </Step>

  <Step title="Fill in the essentials">
    Title, slug (if applicable), target audience, target keyword (for SEO content), author. These populate the final published version and inform any SEO checks.
  </Step>

  <Step title="Write the draft">
    Rich text editor with markdown shortcuts, images, embeds, AI writing assistance. Save frequently — every save creates a version you can roll back to.
  </Step>
</Steps>

## Requesting a Review

<Steps>
  <Step title="Click Request Review">
    Top-right of the document. The stage changes from **Draft** to **In Review**.
  </Step>

  <Step title="Assign reviewers">
    Pick team members. Mark any as **Required** — the piece can't move to Approved until required reviewers sign off.
  </Step>

  <Step title="Add a note (optional)">
    Context for reviewers: "SEO review only please" or "Legal: check the claims in paragraph 3".
  </Step>

  <Step title="Send">
    Reviewers receive notification (email + in-app). They can open the doc with a single click.
  </Step>
</Steps>

## Leaving Feedback

Reviewers work inline, not in a separate doc.

<Steps>
  <Step title="Highlight the text">
    Select any word, phrase, or paragraph.
  </Step>

  <Step title="Click Comment">
    A comment thread pins to that text. Type your note.
  </Step>

  <Step title="Optionally @mention">
    `@Abe` notifies that specific person. Useful for questions: "@Abe is the pricing on this correct?"
  </Step>

  <Step title="Resolve when addressed">
    Once the author makes the change, either the author or the reviewer can mark the thread **Resolved**. Resolved threads collapse but remain visible for audit.
  </Step>
</Steps>

## Approvals

<Steps>
  <Step title="Review all comments">
    Reviewers click through each pinned comment, reading context and making sure nothing was missed.
  </Step>

  <Step title="Approve or Request Changes">
    Top-right buttons. **Request Changes** sends it back to the author with a required note.
  </Step>

  <Step title="All required approvals complete">
    Status automatically moves to **Approved**. The author gets notified.
  </Step>
</Steps>

## Publishing

From Approved, click **Publish**. The content pushes to your site. Blog posts appear at `/blog/<slug>`, landing pages deploy as configured.

If you need to update published content, edit it and re-publish — versioning tracks the published history separately from the draft history.

## Version History

Every save is a version. To review or restore:

1. Click the **Version** icon (clock) in the document header
2. Browse versions with timestamp, author, and change summary
3. **Compare** any two versions side-by-side
4. **Restore** any prior version as the current draft

<Info>
  Very old versions (beyond 12 months) may be archived to cold storage. Contact support to retrieve archived versions — usually available within 24 hours.
</Info>

## Images, Files, and Tags

* **Images** — drag-drop into the editor, stored in your project's asset library, auto-optimized for web
* **File attachments** — PDFs, videos, decks. Referenced in the doc or kept as metadata.
* **Tags** — organize by category, campaign, channel. Filter the dashboard by any tag.

## Roles

Each piece of content has defined roles:

* **Owner** — writes, edits, manages the review
* **Editor** — can modify draft but not publish
* **Reviewer** — comments and approves, can't modify
* **Observer** — read-only access

Set roles per document, or use workspace defaults (e.g., "everyone in the Marketing group is Editor on all content").

## Useful Dashboard Filters

* **My drafts** — everything you own that's still in Draft
* **Awaiting my review** — requests sent to you
* **Recently published** — last 30 days of live content, for stakeholder updates
* **Overdue** — in-review pieces that have been sitting too long

<Tip>
  Standardize your review process and write it down. "SEO reviews all posts, legal reviews any health/finance claims, founder reviews anything about pricing or positioning." Put it in a team doc so expectations are clear.
</Tip>

## Verify It Worked

Create a test doc. Request review on a teammate. Have them leave one comment, resolve it, and approve. Confirm status moves to **Approved**. Publish and check the content is live.

## Troubleshooting

<AccordionGroup>
  <Accordion title="Reviewers aren't getting notified">
    Check that reviewers have verified email addresses in their workspace profile. Also confirm workspace notification settings aren't suppressing content review emails at the user level.
  </Accordion>

  <Accordion title="Comments don't save">
    Browser tab may have lost connection. Refresh the page — unsaved comments appear in a recovery draft in the bottom-right. Recover and resubmit.
  </Accordion>

  <Accordion title="Version history is missing old versions">
    Versions older than 12 months may be archived. Check the **Archived versions** link in the version panel, or contact support to retrieve a specific timestamp.
  </Accordion>

  <Accordion title="I can't approve a piece I'm meant to review">
    You have to be in the reviewer list set by the person who requested the review. If you're not, ask them to add you via **Edit review** in the document sidebar.
  </Accordion>

  <Accordion title="Published content doesn't update on the site">
    Your site may be caching aggressively. Check the [Deploy Site](/how-tos/deploy-site) guide — you may need to trigger a redeploy to bust the cache for the updated page.
  </Accordion>
</AccordionGroup>

## What's Next?

<CardGroup cols={2}>
  <Card title="Post a Blog" icon="pencil" href="/how-tos/post-a-blog">
    Walk through publishing a blog post end-to-end
  </Card>

  <Card title="Brand Guide" icon="palette" href="/how-tos/brand-guide">
    Lock in consistent voice, tone, and style
  </Card>
</CardGroup>