Best first template
Template gallery hub with six above-the-fold starter diagrams.
Templates reduce the blank-canvas problem. This page should act as the bridge from free diagram.now usage to Confluence installation: open a useful template first, then install the Marketplace app when the team wants editable diagrams in pages.
Template gallery hub with six above-the-fold starter diagrams.
Send search visitors to the browser editor first. Ask for Marketplace install only after they know the diagram is useful.
When the diagram belongs in a spec, runbook, ADR, or process page, install diagram.now so it stays editable beside the docs.
Publish templates for architecture decisions, incident runbooks, SaaS billing ERDs, API auth sequences, BPMN approvals, release workflows, cloud architecture, network diagrams, mind maps, and wireframes.
Put the diagram near the decision or process it explains. Add a short caption that states what changed, who owns it, and when the diagram should be reviewed again.
Each template should include two CTAs: open it free in the browser and install diagram.now for Confluence. The first CTA creates value; the second captures team workflow intent.
Use the browser editor for the first draft. If the diagram becomes team documentation, install diagram.now from Atlassian Marketplace and keep it editable inside Confluence.
It is a reusable starting diagram for a Confluence page, such as a flowchart, architecture map, ERD, UML sequence, process diagram, or wireframe.
Yes. Template pages can capture specific use-case search intent and create internal links into the free editor and Marketplace pages.
Start with incident response flowchart, SaaS billing ERD, API auth sequence, architecture decision diagram, BPMN approval process, and cloud reference architecture.