It would be good to know the file dependencies before an article is deleted so that links can be fixed in advanced and not as an after process.

I need some way for readers to view new versions of articles before they are published/re-published. This will allow us to have our changes reviewed by the content experts before they are published and able to be seen by a wider audience. It would be sufficient to be enable a preview link to be sent but enable it to be reviewed. This should be able to be set by reader group so that not all readers would have this ability.

Today, a read-only reviewer can only start discussion on topics. We need SMEs to be able select parts of content and leave comments on it in like you can do in google docs, confluence, Microsoft word.

Within Content Tools -> Bulk operations I would like to also perform operations in categories that are appropriate. In my case, I am tagging articles and categories with a specific tag to publish at the same time. When I select the tag using the Tags filter, I see the articles listed but not the categories. I would like to be able to include categories in this list and perform operations (such as publish) with all of these pages at the same time.

When updating a slug from within the SEO tag section, D360 needs to add same pop-up "to redirect links" that it provides when you update a slug from under the title of an article. If a user updates the slug from the SEO/Tag section it breaks the linking from other articles. If you update it from under the title, it (rightfully) prompts you to re-direct links.

Users would like to be able to include screenshots when providing feedback on articles.

Sometimes if the image length goes down the article and a scroll bar is required to view the entire image. In such cases, if we click on the image and zoom it, the zoomed in image appears to be smaller than the original image. In such scenarios, if the image contains text content, it is impossible for the readers to read the text content in a zoomed in image.

Search on public site - pressing enter to display all results instead of opening the first matching article

Users should be able to move articles between various projects/versions. Currently, the <Move to> option can only help you move articles within the same version. Add an additional layer on top of this so that users can select their respective projects/versions to move articles.

When we hide an existing article it gives a 404 when accessed. Instead of completely removing the article, can we just remove it from the ToC and keep the article published? If we can have this capability, then we can share the articles privately. Ideally, we should have an option of choosing which article goes in ToC and which stays out. Not all articles need to be the ToC.