Templates

Templates let you standardize how you write changelog entries, so every update follows the same structure and tone. Instead of starting from a blank page each time, you can create reusable templates with pre-filled titles, content, categories, and links — then apply them whenever you publish a new entry. This is especially useful if multiple people contribute to your changelog and you want consistency across entries.

How to create and manage a template

1. Go to Changelog > Templates in your workspace.
2. Click New Template to open the template editor.
3. Give your template a Name and optional Description so your team can identify its purpose at a glance.
4. Choose a Category (e.g. New, Improvement, Fix) — this sets the default label shown on entries created from this template.
5. Fill in the Title Template and Content Template fields with your standard wording, structure, or placeholders.
6. Optionally add a Link Title and Link URL if entries from this template should always reference the same resource (like a docs page or status page).
7. Click Save to add it to your workspace's template library.
8. To reuse a stock template as a starting point, browse the built-in template gallery and copy it into your workspace before customizing.
9. To make changes later, click the Pencil icon on any template to edit it, or the Trash icon to delete it (you'll be asked to confirm before deletion).

In practice

An IT service desk lead at an enterprise creates a "Planned Maintenance" template with a pre-written structure covering affected systems, downtime window, and impact. Whenever a new outage is scheduled, they duplicate the template, fill in the specifics, and publish — cutting prep time and ensuring nothing important gets left out.

A product manager at a software company builds a "Release Notes" template with sections for What's New, Improvements, and Bug Fixes, plus a standard link to the docs site. Every release, they reuse the template so customer-facing notes stay consistent in tone and format.

Tips

• Start from a stock template if you're not sure how to structure a category — you can customize it fully after copying it in.
• Keep template names specific (e.g. "Security Patch Notice") so contributors pick the right one quickly.
• Review your templates periodically — as your changelog evolves, update wording or links so entries stay accurate.