Feature Request

The "Document Difference Viewer" that displays when comparing article versions could use some improvements. Currently, I have to copy and paste each version into a third-party editor to properly compare versions. The red that is used to highlight changes does not have sufficient contrast for WCAG certification. For the "Code diff" section, when comparing pages made using the Markdown editor, it would be nice to display the text of each version in numbered lines (like in github, vscode, etc.) to make comparing between versions easier. Other UI improvements that could significantly improve the UX would be navigation that allows you to easily scroll between each difference ("Next difference ->", "<- previous difference", etc.), a search bar, and a toggle that allows you to scroll both versions at the same time (instead of independently) Thanks!

Any time the edit button is clicked, it creates a version. This adds to the noise. Sometimes, we may just want to copy a section of the article. It automatically creates a version. And becomes a mess in bulk operations. Instead, when the article is closed, if there is no change, the article must not be saved to create a new version. Only if there is some change made, should there be a version created. Our software has this ability. In fact if the user were to click Ctrl + Save... it returns a message saying no changes detected.

Can we please use a lighter shade of red when comparing versions. It's very difficult to read black text on red background.

Need to be able to see the approver on the article history

It is confusing that articles previously published and replaced by newer versions are labeled as "draft." Instead, we can use terms like "previous version," "replaced," or similar alternatives for clarity.

Sometimes we fork a version of an article, to update it for the next SW release, before the current version is published. So we have more than one valid unpublished fork of an article. It would be nice if we would be able to write next to the fork, or make some sort of internal notation next to these forks as to which SW release it belongs so, or which feature it is documenting, so various authors will easily understand what is going on and so that an incorrect version will not be published by accident.

I would love to be able to generate a list of all the new articles published in a given time period, as well as the number of articles that were updated in the time period. Currently, you can only provide a list by publication date, but there's no way to determine whether it's a new or updated article, and any article that was updated again after the end of the time period is not included. That is to say, if I export a list of articles published in December 2022, what I get right now is only a list of what was published that month but not since then; if I have an article that I published in December but then updated in January 2023, it is not included in the December list. This would be very helpful for our reporting purposes, to allow us to know how many new and updated articles we're producing. Thanks for considering this request.

Hi, Would love to have a feature, which provides ability to select a previous Version from drop-down and fetch all content from previous releases up till the current releases. Specifically for Release Notes. Example: Current RN version is 23.1.4 and Previous RN version selected is 23.0.0-beta4, then compare will give you all content from 23.0.0-beta4 TO 23.1.4. From customers perspective, it is useful to have such feature, where they don't need to go to each RN and understand what capabilities are provided from version 'w' to version 'z'. Does this sound like a cool feature ? Please check and let us know, when this can be prioritized. Regards, Tariq

It's hard to read info such as the last revision date and comment. Way too small, and zooming in with browser not practical. If increasing the font resulted in fewer revisions displaying at one time, I'd consider it to be a fair trade-off. Ping me if you have questions. Thanks.