Feature Request

We have content we'd like to document and share with customers as an article link WITHOUT requiring a private KB setup. The URL of this article should only be accessible if they have the direct link BUT it should not be searchable and crawled for SEO.

Notification should be sent to the readers as well on the updating article, newly added article, etc through email. Readers should have the capability to view the difference between the previous and updated one.

It would be very helpful to be able to "unpublish" a new article. For instance, if someone prematurely published a new article that has no previous versions, I could just click a button that would revert the article back to its unpublished state. (This is not the same as switching to a previous forked version -- I'm thinking of new articles that have no revision history yet.)

We're looking for a way to support multiple departments who have some degree of shared information, but also some specialized knowledge that's only relevant to their department. It would be great if each of their respective versions had ALL the information that department needs, not just the specialized knowledge. Further, it would be important that articles could be shared across those multiple KB versions - so if someone edited it in one place, it updates in both versions.

Some contributors are lazy about image naming, and will simply add a bunch of images named "image" , one at a time, to an article as they work. This results in many image files in drive with names like image(78).png, image(102).png, and so on. This of course is bad practice and makes it difficult for editors and authors to maintain topics. For example, a common and frequent use case is the need to _update_ an image with a newer screenshot as product interfaces evolve. In this use case, you are looking at the article in the editor, seeing the image name, and then opening Drive in a separate browser tab and searching for that image name so that you can use "Replace" to update that image with a newer screenshot/diagram/etc. Problem is, when contributors are lazy with their image file naming as they author, and you end up with vague file names like image(35).png, an editor might want to _rename_ that image file to be more descriptive of its content, and to follow style guidelines and naming conventions. Except Doc360 does not allow us to rename existing images. Why not? You know the image dependencies. Why not allow us to rename an existing image, and Doc360 can follow the dependencies and update the image name portion of the imageURL to match, in all dependent articles? The [Title](imageURL) syntax is plain text and should be simple to update automatically when someone renames the corresponding image over in Drive.

Often, we need to take down articles, but we also need to be able to retrieve them later... and go back to it. So the ability to archive content is pretty important.

I apologise if this issue is already logged as a wish-list item but the following feature is so obvious and would make life so much easier for Editors and Admin site managers. Please can we have the ability to run a search and identify all images within a specific MY DRIVE FOLDER or that currently has zero dependencies. We then need the ability to move them to a nominated folder or to delete them. Please note - the search function cannot only be for the first 20 items in a view if the folder contains 400-500 images! We need to be able to clean up content fast on my Drive and manually selecting decencies (file by file) is definitely not a feasible for a software that has so much potential to be amazing to work in. Please see image attached.

It would be helpful if it was possible to use standard keyboard shortcuts to search for text in the code editors.

It will be nice to have some table design and layout options such as: borders colors shading ...