Better changelog updates
I created my first changelog item today. Here are a few feedback items:
The Rich Text Editor is semi-markdown compatible. If I past some content in markdown mode, it automatically converts code blocks but I guess that's it. If possible converting markdown to compatible formatting upon paste would be a great feature.
I'm posting about a new version, it's a changelog, right? So even though it can be useful in certain scenarios, it's somewhat redundant having both title and version fields. Version is the main actor. (At least I think so)
I'm a big fan of conventions when it comes to software development. Semantic Versioning, Conventional Commits, Keep a Changelog and many more that I can't remember right now. How about following Keep a Changelog convention with changelog updates?
Platforms section in Changelog Details has limited options. I'm developing a CLI tool and I had to select Desktop, even though it's not a desktop app.
Cheers!
byEmreu/emre
Hey u/emre! Thanks a lot for the detailed feedback.
Congrats on your first changelog item! Point by point:
Markdown paste: You're right, and honestly the code-block conversion you noticed was more of a happy accident than a feature. I've decided to build proper markdown-on-paste conversion: headings, bold/italic, lists, links. And not just in the changelog editor; it'll work in every rich text editor across ProductLog (comments, feedback, stories too).
Title + version: Fair point, but I am keeping both, and here's why: titles in ProductLog are per-language (you can publish the same update with an English and a Turkish title), while the version label is a single global value. The title is also what shows up in social share previews, follower notifications, and search. Moreover "Dark mode is finally here!" travels a lot better there than "v1.2.0". So version stays the release identifier, title stays the headline. That said, nothing stops you from keeping titles short and version-flavored if that's your style.
Keep a Changelog: Love this one, and we found a home for it that fits naturally: the Status Tags in Changelog Details. We're aligning them with the convention, you'll get the full set: Added, Changed, Deprecated, Removed, Fixed, Security, and you can tag a single update with several of them, just like a proper Keep a Changelog release.
Platforms: Guilty as charged. I am expanding the list CLI included, plus Browser Extension and Plugin and adding custom platform labels, so if you're shipping something we didn't think of - an LLM model, a Figma plugin - you can just type your own. The picker is moving to an "Add Platform" button with a popover so the form stays tidy.
Thanks again — three of these are now on our board. Cheers!