Release Notes System
Everything you need to create consistent, high-quality release notes.This section is for documentation maintainers and AI agents creating release notes.
Quick Start
For AI Agents:- Read AI Agent Guide
- Select appropriate template from below
- Follow the 6-step process
- Validate against checklists
- Read Playbook for workflow
- Keep Quick Reference open while writing
- Follow Style Guide for writing standards
Templates
Choose based on release type:General Template
Standard improvements and bug fixes
Feature Template
New features and capabilities
Major Release
Version launches and major updates
Hotfix
Critical urgent fixes
Security
Security updates and patches
Reference Guides
Taxonomy
Tags, components, and classifications
Style Guide
Writing standards and rules
Quick Reference
One-page cheat sheet
Audience Guide
How to choose the right audience
Icon Guide
Visual standards and color codes
Playbook
Complete workflow from start to finish
Verification Standards
Mandatory verification for accuracy
Mintlify Components
Approved components for release notes
AI Agent Resources
AI Agent Guide
Complete prompt and process for AI-generated release notes
File Organization
Standards at a Glance
| Aspect | Standard |
|---|---|
| File naming | YYYY-MM-DD-short-title.mdx |
| Length | 200-400 words |
| Voice | Active, user-focused |
| Tense | Present for features, past for fixes |
| Audience | You, not we |
| UI refs | Bold exact labels |
| Icons | Mintlify built-in only |
| Tags | From taxonomy only |
Common Workflows
Creating a New Feature Release
- Open
template-feature.mdx - Fill in frontmatter using
taxonomy.mdx - Write sections following
STYLE.md - Validate with
QUICKREF.mdchecklist - Place in correct folder
Writing a Security Update
- Open
template-security.mdx - Fill vulnerability details
- Include impact assessment table
- Add timeline
- Mark as
hotfixseverity - Publish immediately
Batch Writing Multiple Releases
- Keep
QUICKREF.mdopen - Use consistent tags from taxonomy
- Follow same structure for each
- Validate each against checklist
- Update indices when done
Validation Checklist
Before any release note is complete:- Follows selected template
- All frontmatter fields valid
- Tags from approved taxonomy
- Audience appropriate
- No internal jargon
- UI references exact and bold
- Length 200-400 words
- Benefits clear in first sentences
- Instructions actionable
- Breaking changes documented (if any)
- File named correctly
- In correct folder location
Need Help?
- Questions about taxonomy? → Taxonomy guide
- Unsure about style? → Style guide
- Don’t know workflow? → Playbook
- Quick lookup needed? → Quick reference
- Creating NEW documentation? → New Doc Guide
- UPDATING existing docs? → Update Guide
- AI generation issues? → AI Agent Guide
- Need universal standards? → Documentation Standards
- Need to verify features? → Verification Standards
- Component questions? → Mintlify Reference
This system ensures every release note is consistent, clear, and user-focused. Follow the guides and your release notes will meet BeatPass quality standards.