Get startedCLIAPIMCPWebDesktopAgentsSupportBillingChangelog
Guide

Templates

Pre-built workspaces operators actually run. One click drops a fully configured workspace into your sidebar with columns set, sample rows in place, and a starting doc body. Swap or delete the samples once your real data lands.

Browse the catalog

The live catalog is at trydock.ai/templates. 21 templates today across four categories: Build, Run, Write, Research. Each category has its own landing page (/templates/category/build and so on) for SEO + as a starting point if you only want one slice of the catalog.

The four categories

Category
What it's for
Example templates
Build
Shipping code or running technical operations. Engineering rituals, infrastructure runbooks, agent audit cycles.
Agent runbook & audit cycle · Sprint planning · Engineering on-call
Run
Operating the business day to day. Pipelines, trackers, recurring rituals, anything that lives in a table with rows.
Launch tracker · Sales pipeline · Design-partner pipeline · Product roadmap · Onboarding checklist
Write
Long-form work that lives in a doc body. Specs, calendars, briefs, anything that's mostly prose with some structure.
Product spec · Content calendar · Company wiki
Research
Capture and organize what you learn. Customer interviews, market notes, anything where the row IS a finding.
Customer research notebook

How a remix works

Every template ships an “Open in Dock” CTA on its detail page. Clicking it:

  1. Fetches the canonical starting markdown from /templates/<slug>/raw.md.
  2. Mints a new workspace in your default org. Slug = template-slug suffixed if taken. Columns + sample rows are seeded from the template definition; doc body is seeded from the markdown above.
  3. Redirects you to the new workspace. Same workspace as if you built it by hand; nothing about a remixed workspace is special-cased after creation.

You can also remix programmatically via POST /api/workspaces with template: "<slug>". Agents calling the API get the same remix flow as the web UI.

Adding a template

Templates are code, not user content. The catalog lives in src/lib/templates.ts as a single TEMPLATES array. Each entry carries:

  • Card metadata: title, category, shape, audience, agents, surfaces.
  • Detail copy: one-line hook, longer description, who-runs-it paragraph.
  • Starting markdown body: the structured doc the remixed workspace ships with. Headings + sample tables + callouts as appropriate.
  • Optional steps: a list of recommended first-day actions surfaced on /templates/<slug>/steps.

Adding a new template is one edit to src/lib/templates.ts; the listing page, the detail page, the raw-markdown route, and the Open-in-Dock CTA all wire up from that single record.

  • Welcome workspace: the workspace every new signup gets — same scaffolding shape as a template remix, seeded with a launch-prep example.
  • POST /api/workspaces: remix from API instead of the web UI.
Updated