Feature Request

Could you please allow for inviting co-authors for working on the same article, like the Dropbox Paper approach. There, you can invite a colleague who then either provides comments on existing text, or adds text to the article itself. This greatly helps building articles across teams, like the Software Engineers and Product Managers working together on the same article.

Currently, the only way to add a Markdown-based article is to set the whole site to Markdown, create the article, and then switch back to WYSIWYG. This is not good as most people creating new articles can not change portal settings. Consider adding a markdown option to the Add dialog. Leave the Article in MD unless converted to WYSIWYG. Once converted to WYSIWYG, it can NOT be converted back to MD. The wisdom behind this is that many developers writing technical documents are familiar with and already writing in MD in Git Hub. Allowing the creation of a single document in MD format eases their transition to Document 360 while allowing others to work in WYSIWYG.

Instead of using tables without borders, it would be great to have the ability to change sections of text from one column to multiple columns. This would be especially useful any time long lists are used in articles as it would save space.

We use snippets extensively in our content. It is a show stopper that glossary entries are not supported in snippets. The whole point of a knowledge base is content reuse and content management, but Document360 does not correctly handle snippets, variables, and glossary terms. These need to be integrated.

It would be nice if there were "search and replace" functionality while in the Code view.

Reviewers are currently unable to add review comments to the content within code blocks, or to the code blocks themselves. Please add this capability. The current workaround is that our users are adding comments (about the code samples) to the paragraph above the code block, which is OK but not ideal.

Very often we come across steps that may have the same screenshot... and could be a snippet... but this step appears somewhere in the middle of a document.. We can't use the current snippet as the numbering will break if we were to create one for a step that appears at step 6 in some articles and step 8 in others (for example)

Would like to be able to use columns to organize data, where text could be set on one side and the corresponding image on the other. Being able to put images/text/headers/etc. within columns would keep the blocks lined up when published. Right now, images can be set inline with the text, but this does not allow them to be arranged with any precision, and it's very difficult to work with. See attached screenshot taken from Interact software, where I can create two columns (in this example, 70/30, but column options there include 50/50, 30/70, 25/50/25, 33/33/33, etc.), place the text instructions on the left, and the corresponding image on the right. Everything stays lined up correctly is published which makes it easy for end users to read and follow the required steps. When using a lot of screenshots, being able to set them in columns beside text rather than below or above or inline, keeps the published page much cleaner and clearer to read. I would like to do the same thing in Document360, with the ability to put different blocks within columns to set different data types side by side. Thanks!

I may have posted this a while back but this is one of my biggest frustrations. I need to edit an Article to view\copy parts of its HTML and then Undo the fork. Administrators should have an option to View HTML without having to edit anything.

It would be incredibly useful to have the ability to move table rows up or down within tables in Document360 articles. Currently, rearranging rows requires manual copy-pasting or recreating rows, which is time-consuming and error-prone—especially in long or structured tables. Suggested Implementation: Add drag-and-drop support for table rows, OR Include "Move Up"/"Move Down" buttons for each row in the table editing UI. Use Cases: Reordering steps in procedural or instructional content Organizing comparison or configuration tables Adjusting table hierarchy after editing or feedback Impact: This feature would significantly enhance content editing efficiency and improve the overall authoring experience—especially for technical writers who frequently work with complex tables.