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

# Posts

> The posts lane: the four ways to start one, the board where it gets written, and the per-platform versions that go out.

**Posts** in the sidebar is where a social post is made. The lane is a front
door, not an editor: you pick how you want to start, and the piece opens on its
own board where the writing, the platform versions and the timing all live.

## Start a post

Four ways in, and each one makes the piece and takes you straight to it:

| Door                | Use it when                                                                    |
| ------------------- | ------------------------------------------------------------------------------ |
| **Talk it out**     | Nothing is written yet and you want to think it through with Goosy.            |
| **I have content**  | You have a draft, a photo or some notes to paste in.                           |
| **Repurpose**       | The idea already exists as a video, a Short, an email or something on a board. |
| **From a template** | You want to start from a shape that already works — yours or ours.             |

Whichever you press, you land on the piece's board. There is nothing to edit on
the lane itself.

## The rest of the lane

Under the doors, three bands answer *what is already going on*:

* **Pick up where you left off** — the pieces in progress, and how many are
  waiting on you. When more are waiting than the band can show, a link takes
  you to the full list.
* **On deck** — unstarted post slots from your cadence. It is a short list, not
  a second calendar; [the Schedule board](/work/schedule) holds the full week.
* **Suggested topics** — drawn from what this workspace typically posts and
  refreshed weekly. If the pool is due a refresh, the band says so and offers
  the link that refreshes it.

At the foot of the page, **Browse every set** opens the full list of posts and
groupings.

## The piece's board

A rail runs across the top of the board — **Source · Destinations · Master
content · Variants · Schedule · Review · Publish** — and it tells you where you
are on it, *step 2 of 7*. The first five are the ones you settle; the last two
are the approval and the send.

So a post is ready when those five are settled, and the board names whichever of
them is still outstanding in the same words a refused publish would use:

1. **Say what this piece is built from** — its source.
2. **Choose where it goes** — the platforms it publishes to.
3. **Write the piece itself** — the master content every version starts from.
4. **Write a version for every destination.**
5. **Set when it goes out.**

The bar at the bottom of the board names the *first* outstanding thing rather
than listing all five, because that is the one to do next.

## Choosing platforms, and the versions that follow

Choosing where a piece goes is a step of its own, and it is what creates the
per-platform versions. Each version is written and sized for its own home — its
own caption or post text, its own aspect ratio, and the account it will publish
to. A carousel that reads well on Instagram is not the same post on LinkedIn,
so the product keeps them as separate versions of one piece rather than one
text sent everywhere.

Which platforms are on offer depends on what your workspace has connected —
see [Publishing channels](/make/publishing-channels).

## Approval and scheduling

One approval covers the whole piece, every platform on it included. Until that
approval exists the board reads **Waiting on approval**; once it lands the board
reads **Approved** and says *it goes out at the times set on it*.

Everything on the piece goes out together unless you stagger a version. The
piece then appears on [the Schedule board](/work/schedule) at its day and time,
and anything still waiting on your decision appears in
[Review](/work/reviews).

Publishing is one of the four things that never happens on an assistant's own
judgement — see [How approvals work](/how-approvals-work).
