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

When searching, the suggested article highlights the section where the possible content is. Today, clicking on the possible article just opens to the top article. It requires the reader to scope / ctrl+f the article Ask - when clicking on a search result, take the user to the section of the article where the highlighted resulted is pointed to.

When looking at analytics for different articles, it would be great to have the feature to be able to select an article and then see which specific accounts have viewed the article and how many times

White labelling of docs portal with customer-specific logos and data

It would be useful if when editing in the code view the place in the document is remembered when returning to WYSIWYG.

It would be helpful if articles would have specific IDs (detected on google devtools). In that way we can apply CSS rules for only specific articles

Would be great if we could provide our readers the ability to sort content in a table by the header.

It would be great to have spelling checked within the editor, or at least allow the browser to do so.

If I add a replacement file, it should archive the existing one and keep the new file – I shouldn’t have to go and reattach to articles later. This is a regular use-case for me – when we update our guidance, we update the attachments, and it should be a simple matter to drop a file into Drive, obsoleting the existing file.

current restriction of readers works on project/version/Categories. Would be usefule to have the capabilty also on individual articles or restrict by keyword/tag