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

As part of our documentation workflow, we anticipate needing a way to receive feedback from and collaborate with people across our internal departments as well as external partners. The current features of discussions or notes within the editing platform are intended mostly for internal collaboration between writers and editors. What we're really looking for is a way to share an article while in draft form (perhaps via direct link) so that stakeholders can add comments on individual words/sentences/sections of the article. This would allow us to get feedback from key stakeholders for relevant articles without giving them full editorial access or responsibilities. For example, we might want to have a "new feature" article reviewed by the developer who created the feature, but we wouldn't necessarily want her to review everything else we're working on. In short, it would be great to have something like LinkedIn's ability to share drafts ( linkedin.com/help/linkedin/answer/85039/share-a-draft-of-your-article-before-publishing?lang=en ) but with a way for readers to add comments (as one would in Word or Google Docs).

A search option for locating images that don't have any dependencies would be great. It would help removing old images not is use, freeing up space in the drive.

We want to use one project and make most of its folders public while a few will be private

Shortcut keys for the Editor will be really helpful. Such as, for Publishing, creating links and so on.

I love the new review workflow feature. I would suggest, for a further enhancement - to give me the ability to add specific users to each stage. For example, if my attorney needed to review and I made a step called 'legal review' - it would be nice to be able to have that person persistently there as getting assigned to review per the workflow. Currently, I have to assign the same people every time.

I had a request from a security minded employee to improve how passwords are issued. There is concern about sending temp passwords as plain text via email. Are there any ways this process can be improved to reduce the risk of that password being insecure?

I need to add a code block written in YAML, but YAML is not one of the language options Document360 gives me. Other code formats look okay for presenting the YAML code block, but it's definitely problematic for readers that the name of the language appears in the code block header. I've tried to delete the header in code view, but Document360 adds it back in. Please add YAML as one of Document360's code block options or at least allow users to create a generic code block that doesn't require a header.

Currently if you create a user and add it to a reader group they, by default, can still see everything in the project. you must manually on each reader user set documentation scope to NONE. this makes little sense. it would be nice to set a default documentation scope for all new users.

Add the Position option for images when editing an article. Today, we don't see such options and it will be nice in order to create proper short documentation and not having a long page because of the lack of this feature.