Skip to main content
Changelogs in Featul provide a beautiful, organized way to communicate product updates, new features, bug fixes, and improvements to your users. They close the feedback loop by showing users what you’ve shipped.

​
What is a Changelog?

A changelog is a chronological feed of product updates published to your users. Each entry documents what changed, why it matters, and (optionally) links back to the original feature requests or feedback posts. Changelogs help you:
  • Communicate value by showcasing continuous improvement
  • Build trust by demonstrating you listen to feedback
  • Drive engagement with new feature announcements
  • Reduce support burden by proactively sharing updates
  • Close the feedback loop by linking to requests that got built

​
Changelog Structure

​
Changelog Entries

Each changelog entry includes:
  • Title: Clear, user-friendly description of the update
  • Content: Rich text with formatting, images, code blocks, lists
  • Summary: Brief excerpt for listings and social sharing
  • Cover Image: Optional visual (screenshot, diagram, graphic)
  • Tags: Categorization labels (e.g., feature, improvement, bug-fix)
  • Published Date: When the update went live
  • Author: Team member who created the entry

​
Entry Status

Draft: Work-in-progress, visible only to workspace members Published: Live and visible to all users on your changelog Drafts let you prepare entries ahead of time and publish when ready.

​
Creating Changelog Entries

​
From the Changelog Dashboard

  1. Navigate to workspace settings → Changelog
  2. Click “Create Entry”
  3. Fill in the changelog editor:
    • Enter a descriptive title
    • Write content using the rich text editor
    • Add a cover image (optional)
    • Select relevant tags
    • Set publish date (now or schedule for later)
  4. Save as draft or publish immediately
Write changelog entries from your user’s perspective. Focus on benefits and value, not technical implementation details.

​
Rich Text Editor

The changelog editor supports:
  • Formatting: Bold, italic, underline, strikethrough
  • Headings: H2, H3, H4 for structure
  • Lists: Bulleted and numbered lists
  • Links: Inline and reference-style links
  • Images: Inline images with captions
  • Code: Inline code and code blocks with syntax highlighting
  • Blockquotes: Highlighted quotes or callouts
  • Embeds: YouTube videos, tweets (coming soon)

​
Cover Images

Upload eye-catching cover images:
  • Supported formats: JPG, PNG, GIF, WebP
  • Recommended size: 1200x630px (optimized for social sharing)
  • Stored securely in cloud storage
  • Displayed at the top of entries and in previews
Cover images improve engagement and make entries more shareable on social media.

​
Organizing Changelogs

​
Tags

Categorize entries with tags for easy filtering: Common tag examples:
  • new-feature: Major new capabilities
  • improvement: Enhancements to existing features
  • bug-fix: Resolved issues
  • performance: Speed and efficiency updates
  • mobile: Mobile app specific updates
  • api: Developer/API changes
  • security: Security patches and improvements
Create workspace-level tags in board settings, then apply to entries.

​
Filtering

Users can filter your changelog by:
  • Tags: Show only entries with specific tags
  • Date Range: View updates from specific time periods
  • Search: Full-text search across titles and content
Filters help users find relevant updates quickly.

​
Chronological Order

Entries are displayed newest-first by default. Users scroll down to see older updates. Each entry shows:
  • Publish date (relative or absolute)
  • Title and summary
  • Tags
  • Author (optional)

​
Publishing Workflow

​
Draft → Review → Publish

  1. Draft: Create and refine content
  2. Review: Share draft link with team for feedback
  3. Edit: Make revisions based on review
  4. Publish: Set status to published

​
Scheduled Publishing

Schedule entries to publish at a specific date/time:
  • Align with product releases
  • Coordinate with marketing campaigns
  • Publish during peak user hours
Scheduled entries remain in draft until the publish time.
Schedule changelog entries to publish right when a feature goes live for maximum impact.

​
Edit Published Entries

Update published entries anytime:
  • Fix typos or errors
  • Add additional details
  • Update status of ongoing rollouts
  • Append follow-up information
Edits are immediately visible. Entries show “Last updated” timestamp if modified after publishing.

​
Linking to Feedback

​
From Roadmap Items

When you complete a roadmap item:
  1. Create a changelog entry
  2. In the editor, reference the original post
  3. System automatically links the entry to the post
  4. Users who voted on the post get notified
This demonstrates you built what users requested.

​
Feedback-Driven Entries

Structure entries to highlight user impact: 
## Image Editor Now Supports Layers

Based on feedback from 127 users, we've added layer support to the image editor.

You can now:
- Create multiple layers
- Reorder and rename layers
- Toggle layer visibility
- Blend modes and opacity

Thanks to everyone who requested this!
Explicitly crediting user feedback builds community.

​
Changelog Display

​
Public Changelog Page

Your changelog is accessible at:
  • yourworkspace.featul.com/changelog
  • Custom domain: feedback.yoursite.com/changelog
Public changelog shows:
  • All published entries (drafts hidden)
  • Tag filters
  • Search functionality
  • RSS feed subscription link

​
Embedding Changelogs

Embed your changelog on your main website: 
<!-- Full changelog embed -->
<iframe src="https://yourworkspace.featul.com/changelog" />

<!-- Latest 5 entries widget -->
<script src="https://yourworkspace.featul.com/embed/changelog.js"></script>
Keep users informed without leaving your site.

​
Email Digests

Send automated changelog digests:
  • Weekly summary of new entries
  • Monthly roundup
  • Instant notifications for major releases
Manage subscriptions in workspace settings.

​
Changelog Best Practices

Publish Regularly: Consistent updates (weekly or bi-weekly) build anticipation and show active development.
User-Focused Language: Write for users, not developers. Explain benefits, not technical implementations.
Visuals Matter: Include screenshots, GIFs, or videos showing new features in action.
Credit Users: Mention and link to users or posts that inspired features. Builds community.
Group Related Changes: Combine multiple small updates into themed entries rather than many tiny posts.
Don’t publish changelogs for internal technical changes that don’t affect users. Focus on user-visible improvements.

​
Entry Templates

​
New Feature

# [Feature Name]

[Brief description of what it is and why it's useful]

## What's New
- [Key capability 1]
- [Key capability 2]
- [Key capability 3]

## How to Use
1. [Step 1]
2. [Step 2]
3. [Step 3]

[Screenshot or demo]

Requested by [number] users. Thanks for the feedback!

[Link to original request]

​
Bug Fix

# Fixed: [Issue Description]

We've resolved an issue where [problem description].

**What was happening**: [Explanation of the bug]

**What's fixed**: [How it works now]

Thanks to [users] for reporting this!

​
Improvement

# Improved: [Feature Name]

[Feature] is now [faster/easier/more powerful].

**Before**: [Old behavior]

**Now**: [New behavior]

**Impact**: [Benefit to users]

[Visual comparison if applicable]

​
Advanced Features

​
Import from External Sources

Automatically create changelog entries from: GitHub Releases:
  • Connect your GitHub repo
  • Auto-import release notes
  • Sync tags and version numbers
Notra Integration:
  • Import from Notra changelog tool
  • Preserve formatting and structure
  • One-time or continuous sync
Configured in workspace settings → Integrations.
Imported entries are created as drafts. Review and publish manually to ensure quality.

​
Bulk Operations

Manage multiple entries efficiently:
  • Bulk Delete: Remove multiple draft entries
  • Bulk Tag: Apply tags to multiple entries
  • Bulk Publish: Publish several drafts at once
  • Export: Download entries as JSON or Markdown
Access bulk actions from the changelog dashboard.

​
Version Tagging

Tag entries with version numbers:
  • Matches semantic versioning (e.g., v1.2.3)
  • Groups related entries by release
  • Generates version-specific changelog pages
  • Useful for API versioning or mobile releases

​
Analytics

Track changelog engagement:
  • Views: How many users read each entry
  • Time on Page: Average read time
  • Click-through: Links clicked within entries
  • Referrers: Where traffic comes from
  • Popular Tags: Most-viewed categories
Use analytics to refine your communication strategy.

​
Notifications

​
User Subscriptions

Users can subscribe to changelog updates:
  • Email notifications for new entries
  • RSS feed subscriptions
  • In-app notification badges
  • Weekly/monthly digest emails
Manage subscription settings in user preferences.

​
Targeted Announcements

Send changelog entries to specific user segments:
  • Users who requested the feature
  • Trial users (to demonstrate value)
  • Enterprise customers (for their requested features)
  • Beta testers (for experimental updates)
Segmented notifications increase relevance and engagement.

​
Social Sharing

Optimize entries for social media:
  • Open Graph tags: Rich previews on Facebook, LinkedIn
  • Twitter Cards: Enhanced tweets with images
  • Meta descriptions: Custom summaries for links
  • Cover images: Eye-catching visuals (1200x630px)
Share entries on:
  • Twitter/X
  • LinkedIn
  • Product Hunt
  • Slack communities
  • Email newsletters

​
Next Steps

Build docs developers (and LLMs) love

Get started for freeTalk to us