# Diagram templates

Templates cut the blank-page problem and, more usefully, make diagrams across a team look consistent without anyone policing it.

---

## Using one

When you insert a diagram, pick a template rather than an empty canvas. You get a copy to edit; the template itself is untouched.

## Making your own

Any diagram can be filed in the diagram library and offered as a starting point. Administrators control what appears there. See [Administration](https://help.gocapable.com/diagrams/administration.html).

## What templates are good for

* House styles for architecture diagrams, so every service page looks the same.
* Pre-built swimlane frames for process work.
* Standard legends and keys people otherwise redraw badly.

---

## A few things that catch people out

* A template is copied at insert time. Editing the template later does not update diagrams already made from it.
* Templates are per site, so a space cannot have its own private set.
* For a diagram that must stay in sync everywhere, use a reference instead. See [Find and reuse](https://help.gocapable.com/diagrams/find-and-reuse.html).

---

## Related

[AdministrationManaging the library.](https://help.gocapable.com/diagrams/administration.html)

[Find and reuseOne source, many pages.](https://help.gocapable.com/diagrams/find-and-reuse.html)

[ExamplesDiagrams worth templating.](https://help.gocapable.com/diagrams/examples.html)

---

_Start from something, not from nothing._