Any digital product release needs a changelog entry. It summarizes the improvements and changes made to the product so users and clients can understand what’s changed.
Using this guide, digital product authors can learn how to write, format, and include the necessary data and information in their changelogs.
The changelog appears under the “Description” section only when there’s at least one approved change. Users will still be able to see the changelog this way.
In the author account it’s located on the product upload page.
Each entry in the changelog should follow a specific date format. Use the same format that is already present on most product pages – MM DD, YYYY.
You can check Monstroid 2 changelog for reference.
This consistency allows users to easily track the timeline of changes.
The following types of changelog entries should be used to categorize the changes:
To add a new changelog entry, follow these steps:
## May 31, 2023:
- Fixed issues causing crashes on mobile devices.
- Added the ability to divide library layout into sections, sections into rows, and rows into modules.
Follow these best practices to make your changelog clear and effective:
Keep users informed about changes to a digital product with a changelog. This guide helps digital product authors create clear, informative, and well-structured changelogs that enhance user experience and facilitate the adoption of new features and improvements.
When updating the product archive, this error may appear. Every time you make changes to your product, you should update the changelog.
It’s good practice to include both major and minor changes. Major changes may affect users directly, but minor changes can help stability, performance, and usability.
It’s good practice to mention significant bug fixes that address critical issues or affect a lot of users.
Maintain consistency and help users track changes by formatting the date in the following way ##MM DD, YYYY. Organize entries chronologically, with the latest changes at the top.