Documents vs Templates
A note on terminology before you dig in: Typograph's primary content unit is the template. The word "document" is used more loosely, and the two relate like this:
- A template is the versioned design file you create in the Editor, store in a project, and render with the Publisher. Templates have UUIDs, permissions, comments, invites — all the collaborative machinery.
- A document is the output of running a template through the Publisher (a PDF, image, or set of images), or the JSON payload the API validates via the Document Service.
There is no separate "documents" section in the Portal. If you want to:
- Create new design content → create a template inside a project.
- Generate a PDF or image from a template → that's a publisher job, triggered from the template's menu or via the API.
- Upload images or fonts → those go under the project as media / assets.
Why This Matters
If you're used to tools where "documents" and "templates" are separate things (one is the reusable structure, the other is the filled-in instance), Typograph collapses that distinction: you always work with templates. When you need a one-off variant, duplicate the template. When you need a batch, one output per row of a CSV, run a publisher job through the API: each column of the CSV fills a merge field of the template, a named text frame or image, whether an element prints, or a {{key}} placeholder (what the CSV holds).
Actions on a Template
From the template list or the Editor, you can:
| Action | What it does |
|---|---|
| Edit | Open in Editor |
| Duplicate | Create a copy inside the same project |
| Move | Move to another project (or team) |
| Invite | Share with a specific person and role |
| Favorite (heart icon) | Add to Favorites for quick access |
| Comment | Attach a comment to the template |
| Export / Publish | Trigger a publisher job (PDF / image) |
| Move template to trash | Moves it to the Trash, from the Editor's ⋮ menu; it can be restored from there |
| Restore | Available from the Trash in the sidebar |
API Equivalents
| Portal action | API endpoint |
|---|---|
| Create template | POST /v1/file/templates or POST /v1/file/projects/{id}/templates |
| Edit (autosave) | PATCH /v1/file/templates/{id} |
| Render to PDF | POST /v1/publisher/jobs |
| Validate schema | POST /v1/document/validate |
See File Service and Publisher in the developer docs for full details.