> Rally Help Center. Index of every page: https://rallywith.ai/help/llms.txt
> This chapter's pages: https://rallywith.ai/help/things-rally-makes/llms.txt

# Things Rally makes

> Documents, images, recordings and live web pages that Rally creates, plus the files and items you bring into a Channel.

So far this book has treated a Channel as a conversation. You write, Rally answers, teammates join in, and the whole thing scrolls upward like an unusually polite group chat. That picture is true, but it leaves something out.

A Channel is a conversation with a shelf beside it.

On the shelf go the things the conversation produces. Ask Rally for a one-page plan and you do not get a plan pasted into the chat, wedged between "sounds good" and somebody's lunch order. You get a document: a real file with a title, sitting on the shelf, that you can open, read beside the conversation, pop out onto a second screen or save to your Mac. Ask for a picture and you get an image file. Ask for a voice recording and you get audio. Ask for a sign-up sheet for the team offsite and Rally builds a small working web page, puts it on the internet and hands you its address. These are **artifacts**, Rally's word for anything it made for you.

The first idea: an artifact is one thing that changes over time. When you ask Rally to change a document, it edits that same document. It does not post "Plan (final) (2) (really final)". The title stays the same, the card in the conversation still points at it, and every earlier draft is kept. If Tuesday's version had a paragraph you liked better, you can go back and read it. Nothing Rally replaces is thrown away.

The second idea is that the shelf takes deliveries too. Rally puts things on it, and so does the world outside Rally. A Channel that started from a Slack thread remembers that thread. The things that come in from your other tools sit on the same shelf as **resources**, so both you and Rally can see where a piece of work came from and what it was built on. Artifacts are what the Channel made; resources are what it was given.

Put those two ideas together and a Channel stops being something you scroll through to find the good bit. The good bits are on the shelf, labelled, with their history attached.

The pages that follow go along the shelf from left to right. First, how Rally decides to make a document instead of a chat reply, and how versions work. Then the ways to open, dock, pop out and download what it made. Then live sites, the small web pages and apps Rally builds and hosts, which need more care than a document because they have a public address. Then resources, the things you bring in. Last comes every way content can leave Rally, for the day someone asks you to "send that over".

One small warning before you start. Once you get used to asking for a document instead of an answer, you may find yourself asking for documents about everything. That is fine. Rally does not run out of shelf.