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

# Write and publish

> Create one source draft, customize it for each network, and send or schedule every destination with confidence.

Write is the complete publishing workspace in Omni Writes. Build the shared post in **Main**, keep a separate custom version where a network needs one, then send or schedule the destinations that are ready.

<CardGroup cols={2}>
  <Card title="Main" icon="pen" color="#ff6b35">
    The shared source copy and media that selected networks use by default.
  </Card>

  <Card title="Customize by Network" icon="share-nodes" color="#ff6b35">
    A preview and editing workspace for destination-specific copy, media, threads, and channel options.
  </Card>

  <Card title="Library" icon="books" color="#ff6b35">
    Saved drafts and recent activity that can reopen a complete post in Write.
  </Card>

  <Card title="Send" icon="paper-plane" color="#ff6b35">
    Immediate or scheduled delivery, tracked separately for every selected destination.
  </Card>
</CardGroup>

## Create a post

<Steps>
  <Step title="Select connected accounts">
    Select the account icons at the top of Write. The active selection controls character limits, media rules, and the destinations shown in **Customize by Network**.

    If an account needs attention, reconnect it before trying to send. See [Connect accounts](/account/connections).
  </Step>

  <Step title="Build the Main version">
    Enter the shared idea in the main editor. Add supported media, a GIF, saved hashtags, alt text, or a Threads topic tag when those controls are available for the selected destinations.

    The counter and validation messages update for the current account selection. Resolve blocking errors before continuing.
  </Step>

  <Step title="Let the draft save">
    Write autosaves the current workspace and shows whether draft changes are saving or saved. Choose the **Save to Draft** icon when you want an explicit item in the Library.
  </Step>

  <Step title="Customize by network">
    Choose **Customize by Network** to review the selected accounts. A destination continues to use Main until it has a custom version.

    Choose **Adapt by Network** to generate destination-aware drafts, or open a destination to edit its copy, media, thread structure, and available channel settings yourself. Review generated facts and claims before sending.
  </Step>

  <Step title="Review every destination">
    Check the status and preview for each account. Fix **Too long**, **Could not adapt**, **Needs attention**, and media errors. Use **Retry** to regenerate an eligible failed adaptation, or **Use main** to discard that destination's custom version and return it to Main.
  </Step>

  <Step title="Send or schedule">
    Open the orange **Send** menu. Choose **Send** for immediate delivery or **Schedule** for a future date and time.

    Keep the completed workspace visible until every selected destination has the expected result. Choose **New Post** only when you are ready to clear it and begin another post.
  </Step>
</Steps>

## Main and custom versions

Each destination uses one content source at a time.

| Version    | What it controls                                                                 | What happens when Main changes                                 |
| ---------- | -------------------------------------------------------------------------------- | -------------------------------------------------------------- |
| **Main**   | Shared copy and media                                                            | Destinations still using Main receive the current Main version |
| **Custom** | Copy, media, thread structure, and supported channel options for one destination | The custom version stays protected from Main edits             |

<Note>
  **Adapt by Network** does not overwrite an existing protected custom version during a normal multi-network adaptation. Open that destination and deliberately retry or replace it when you want a new result.
</Note>

In the network preview:

* **Ready** means the destination version passed the current adaptation checks.
* **Review suggested** means the draft needs your judgment before sending.
* **Could not adapt** offers a destination-specific retry when available.
* **Sent**, **Scheduled**, or **Failed · Retry** reflects that destination's delivery progress.

## Drafts, Library, and recovery

The workspace preserves more than text. Saved work can include Main content, media, selected destinations, custom network versions, threads, and supported channel settings.

* Open **Library** from the right edge of Write to browse saved drafts and recent activity.
* Select a draft—or drag it into Main on desktop—to open the complete saved post.
* If the current workspace contains meaningful unsaved changes, Write saves a checkpoint before replacing it with the Library item.
* If another tab has newer changes, Write shows an inline sync notice and updates the draft without requiring a hard refresh.

<Warning>
  Wait for the visible save or upload state to settle before closing the page, replacing the workspace, or sending. If Write reports a save error, retry the save in place so the complete post stays recoverable.
</Warning>

## Media and validation

Omni Writes validates media against the selected networks before delivery. The strictest relevant rule may block Main even when another selected network would accept the same file.

| Check                   | What to do                                                                                             |
| ----------------------- | ------------------------------------------------------------------------------------------------------ |
| Upload state            | Wait for every required file to finish uploading; remove and add a failed upload again                 |
| File rules              | Use a supported type and stay within the product's size, image-count, video-count, and duration limits |
| Mixed media             | Keep photos, video, and GIFs separate when a selected network does not allow them together             |
| Destination differences | Move into a custom version when one network needs different media or ordering                          |
| Alt text                | Add a description where supported; the composer accepts up to **125 characters** per media item        |

Missing alt text may produce an accessibility reminder without blocking delivery. A pending, failed, unsupported, or over-limit media item can block Send or Schedule.

See the [X](/channels/x), [Threads](/channels/threads), [LinkedIn](/channels/linkedin), [Instagram](/channels/instagram), and [Facebook](/channels/facebook) guides for channel-specific behavior.

## Threads, Ghost Mode, and X Articles

<AccordionGroup>
  <Accordion title="Multi-post threads and chains" icon="list-ol">
    X and Threads support multi-post composition. Add posts manually or use auto-split; a chain can contain up to **11 posts**. Review every numbered post and its own media before delivery.
  </Accordion>

  <Accordion title="Threads topic tags and Ghost Mode" icon="at">
    A normal Threads post can include one supported topic tag. **Ghost Mode** is available only when Threads is the sole selected network and the content is one text-only post. It turns off if you select another network or convert the post into a chain. Ghost posts archive on Threads after 24 hours.
  </Accordion>

  <Accordion title="X Articles" icon="newspaper">
    When an eligible X account is the only selected destination, Write can show the X Article editor. Articles have their own title, rich body, media, save, Send, and Schedule flow. If the control is not visible, the connected X account is not currently marked as Article-eligible.
  </Accordion>
</AccordionGroup>

## Understand delivery outcomes

A multi-destination action is not one all-or-nothing result. Omni Writes keeps each destination's outcome separate, so one account can be **Sent** or **Scheduled** while another remains **Failed** or unsent.

<Warning>
  **Scheduled** means Omni Writes accepted and stored the post for future processing. It does not mean the network has published it yet. Authorization, media availability, or a provider rule can still cause a failure at publish time.
</Warning>

When only some destinations fail:

1. Keep the current workspace open and read the exact destination error.
2. Fix the connection, copy, media, or channel setting for that destination.
3. Retry only the failed or remaining destination. Completed destinations are not sent again.
4. Confirm the final state in [Calendar](/workflows/calendar).

<CardGroup cols={2}>
  <Card title="Calendar" icon="calendar-days" href="/workflows/calendar">
    Review scheduled, processing, published, failed, and cancelled content.
  </Card>

  <Card title="Omni Intelligence" icon="waveform-lines" href="/workflows/omni-intelligence">
    Learn how accepted writing evidence guides voice-aware writing and adaptation.
  </Card>

  <Card title="Troubleshooting" icon="life-ring" href="/account/troubleshooting">
    Recover connection, media, scheduling, and publishing errors.
  </Card>
</CardGroup>