Skip to main content

The dashboard

Reelwire turns things that happen into posts. The shape of the product follows that sentence:

  1. Content arrives. From a feed you subscribe to, from your own systems over the API, or from a post you write by hand in a post list.
  2. It is drawn into a clip. A template decides what the video looks like; your brand decides the colours, type, logo and the legal line at the bottom.
  3. It goes out. To the channels you have connected, after approval where you have asked for it.

Everything on the screen is one of those three steps, or the evidence of them.

Setting up, in order​

The pages below are in the order somebody meets them the first time.

  1. Brands. The look your clips wear. A channel cannot be made without one.
  2. Channels. One account, one platform, one language, one brand.
  3. Platform connections. The credentials that let a finished clip reach the account it belongs to.
  4. Templates and Media library. What a clip is drawn through, and the files it uses.
  5. One of the three ways content arrives: Feeds, Post lists or the Custom API.

Then the screens you read rather than fill in: Posts for where everything stands, Received for what arrived and made nothing, Approvals where a person clears posts first, and Schedule for what is due.

Team, Your profile and Plan, allowance and billing cover who is here and what it costs.

Two things that trip people up early​

A channel publishes only what it listens to. Making a channel does not make it post. Open it, press Sources, and add a feed, a post list or a stream. A channel listening to nothing renders nothing, and that looks exactly like everything being fine.

A brand is shared, deliberately. Editing one changes every channel wearing it at once. Press Used by before you save.

Talking to Reelwire from your own code​

Everything the dashboards do, your own systems can do. See the API reference, and AI assistants for pointing an assistant at it.