Chapter 6
Things Rally makes
Documents, spreadsheets, images, recordings, PDFs and reactive web pages that Rally creates in a Canvas, plus the files and items you bring in.
Chapter 2 treated a Canvas mostly as a conversation. You write, Rally answers, teammates join in, and the whole thing scrolls upward like an unusually polite group chat. This chapter is about the other half of the page: the panel on the right, where the things Rally makes appear.
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 in the panel, that you can read beside the conversation, pop out onto a second screen or save to your computer. Ask for a budget and you get a spreadsheet. 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, and every one of them lives in a Canvas.
The first idea: an artifact is one thing that changes over time. When you ask Rally to change a document, it publishes a new version of 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 version 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 a Canvas takes deliveries too. Rally puts things in it, and so do you: files you attach, and items from your other tools that you point Rally at. Those are resources, so both you and Rally can see what a piece of work was built on. Artifacts are what the Canvas made; resources are what it was given.
The pages that follow start with 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 reactive 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 Canvases.
In this chapter
- 6.1Artifacts
Rally writes documents, images and other files as artifacts that live in a Canvas and keep every version.
- 6.2Opening, docking and downloading
Preview any file, keep an artifact open beside the chat, pop it into its own tab or window, or save it to your computer.
- 6.3Reactive sites
Ask for a web page or small app and Rally builds it, hosts it and gives it its own address.
- 6.4Resources: things you bring in
Bring files and items from your connected tools into a Canvas, and trace a Sidekick run back to what started it.
- 6.5Saving and sharing what Rally wrote
Turn a reply into a polished image or PDF, copy text and tables, and know every way content leaves Rally.