Projects

What a project is for

If you build one deck, you do not need a project. If you build ten decks for the same audience, you will find yourself typing the same context into every prompt: who the audience is, what to open on, which words to avoid, which document to work from.

A project remembers that context and applies it to every deck built inside it.

Projects are optional. A deck does not have to belong to one, and most will not.

What a project holds

Instructions. Standing rules for every deck in the project. Plain text, and worth being blunt in:

We are a B2B fintech selling to CFOs at mid-market companies. Always open on the customer's problem, never on our product. Never use the word "synergy". One idea per slide. Our pricing is $499/mo. Do not quote anything else.

Brand. Optional. Pick one and every deck in the project is built in it, without choosing it each time.

Files. The documents the decks are written from. Upload them here or pick from files you already have. Preso reads them and grounds the writing in them, so you do not re-upload the same brief for every deck.

Building in a project

Open the project and use the composer at the top of it. The deck is created inside the project, and starts already knowing the instructions, the brand, and everything in the files. You can also pick the project from the composer on the dashboard.

Housekeeping

Rename a project by clicking its title. Favourite it from the menu next to the title, and it sorts to the top of the list.

Deleting a project does not delete your work. The decks and files inside it are kept. All that goes is the grouping.