Manual Changelog Creation

Create and publish changelogs manually in your Saylo dashboard

Manual Changelog Creation

Create and publish changelogs manually in your Saylo dashboard.

What you'll get

  • Full control over changelog content and timing
  • Rich markdown editor for formatting
  • Draft mode for team review
  • Image upload support
  • Email notifications to subscribers

Setup

Step 1: Create a new changelog

  1. Go to your Saylo dashboard
  2. Click "Changelog" in the navigation
  3. Click "New Changelog" button

Step 2: Fill in basic information

  • Title: Create a descriptive title (e.g., "v2.1.0 - New Dashboard Features")
  • Summary: Brief overview of the release
  • Content: Detailed changelog content using markdown
  • Image: Upload a cover image (optional but recommended)
  • Publish Date: Set when this version was released

Step 3: Write your content

Use the markdown editor to write your changelog. Here's a recommended structure:

## 🚀 New Features

- **Dashboard Analytics**: Added comprehensive analytics dashboard
- **User Profiles**: Users can now customize their profiles
- **Dark Mode**: Added dark mode support across the app

## 🐛 Bug Fixes

- Fixed login issues on mobile devices
- Resolved data export problems
- Fixed notification delays

## 🔧 Improvements

- Improved page load performance by 40%
- Enhanced search functionality
- Updated UI components for better accessibility

Publishing options

Draft mode

  • Save as draft to work on your changelog
  • Preview how it will look to users
  • Edit later before publishing
  • Share with team for feedback

Publishing

  • Publish immediately
  • Send email notifications to subscribers
  • Appear on your public hub
  • Share on social media

Required fields

When publishing a changelog, all these fields are required:

  • Title
  • Summary
  • Content
  • Image
  • Publish Date

Best practices

Writing style

  • Use clear, non-technical language
  • Be specific about what changed
  • Write from the user's perspective
  • Keep each item brief but informative

Structure

  • Group changes by type (Features, Fixes, Improvements)
  • Use emojis for visual hierarchy
  • Put important changes first
  • Include context for user impact

Templates

Feature release

## 🎉 What's New

### [Feature Name]
Brief description of the new feature and how it helps users.

## 🔧 Improvements

- Enhanced performance in [specific area]
- Improved user experience for [specific action]

## 🐛 Bug Fixes

- Fixed issue with [specific problem]
- Resolved [specific bug description]

Bug fix release

## 🐛 Bug Fixes

- Fixed [specific bug] that was affecting [users/functionality]
- Resolved [another issue] in [specific area]
- Corrected [third issue] for better reliability

## 🔧 Minor Improvements

- Small improvements to [specific feature]
- Better error messages for [specific action]

Need help?

Contact our support team through your dashboard or visit our help center for additional resources.