Feature Request

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.

Currently, the system will not allow two files to have the same name, globally, across the entire Knowledge Base site. This is very problematic in technical documents where software expects files to have a certain name. In our case, we need to provide example config files for many different scenarios. If the software in question expects some config files to be named "foo.conf" and others to be named "ding.list", renaming them to be unique across every example would be very confusing for the audience. The usual solution for this scenario is to create multiple directories (folders). The directory name plus the file name is then still unique. Indeed, I tried creating different folders in the "Drive" file management tool, but it renames every file I upload to be unique across the entire drive. It seems that your current implementation uses a single directory on the CDN for the entire site. Presumably the limitation extends from this. The folder structure maintained in the "Drive" is apparently for display purposes only. It seems like a straight-forward way to fix this would be to extend the folder structure created in "Drive" to the CDN. For example, if I created folders "simple" and "fruit" in the "Drive", and under the "fruit" folder, further created folders "banana" and "apple", and uploaded a "foo.conf" file to each of them, the resulting CDN paths might be: https://cdn.document360.io/fb0cfe40-8232-41f1-8fc7-68adda25cdcb/Images/Documentation/simple/foo.conf https://cdn.document360.io/fb0cfe40-8232-41f1-8fc7-68adda25cdcb/Images/Documentation/fruit/foo.conf https://cdn.document360.io/fb0cfe40-8232-41f1-8fc7-68adda25cdcb/Images/Documentation/fruit/apple/foo.conf https://cdn.document360.io/fb0cfe40-8232-41f1-8fc7-68adda25cdcb/Images/Documentation/fruit/banana/foo.conf The only tricky part would be that existing sites of course expect their Drive folder structure to have no effect on their links. Simply enabling everywhere it would break existing sites. Enabling it only for new folders might still be confusing to people used to the old way. Perhaps some kind of site-global option for "Advanced Drive paths" or something like that could be offered. Once that option was enabled, new folders would have their path reflected in the CDN. Existing folders would continue to use the root for storage, for compatibility. The built-in system folders would be exempted from this treatment regardless.

The current limit doesn't allow editors to upload files with file sizes that exceed 150 MB. This will be extremely helpful if there is no size limitation or limit to a maximum 1GB.

I would like the ability to rename assets directly from Drive. Currently that is not possible, and forces you to have to re-upload an asset just to change the name.

There should be a button for expanding and collapsing all Drive folders so that I can see the entire tree structure with one click.

When I create a new category, it would be very helpful if I was given the option to create the drive folder at the same time. It's very time consuming to create the Drive folders in a second step - especially when we have a lot of categories for our initial setup.

This request was created on behalf of Georgia When we create articles and uploads the files, the files that we upload are also stored in the drive. In the drive though all editors have access, but we want to limit the access to only the editor that uploads the file. Thank you.

I want to be able to create links that open files hosted on Doc360 Drive. Currently, the ctl+k menu only facilitates links to existing articles and external URL's. I'd like an option link to an existing file in Drive. I see that this feature has been requested since at least 2021. Adding a new request since I expect the older ones have been deprioritized.

When I insert an image into a document, the image is named "image" and is placed into a single root folder. This leads to duplication, needless storage use, and makes reviewing documentation and image reuse unnecessarily difficult. When an image is added, it should be added to a folder associated with that document. Name it whatever you feel you have to if you can't do any better, but the image should be easily addressable by association.

Currently, it is not possible to replace a file with a different format, such as SVG to PNG or PNG to SVG. It would be great to have an option in Drive to support replacing files across different formats.