Feature Request

We’ve received feedback from a customer requesting additional heading levels (H5 and H6) in the Document360 editor. Currently, the editor supports H2, H3, and H4, with H1 reserved for the article title. This limitation is making it challenging for them to structure complex documentation effectively, as they are constrained to a limited hierarchy. The customer has highlighted that having support for H5 and H6, would significantly improve content organization, scalability, and overall readability. This enhancement would help users create more structured and maintainable documentation, especially for detailed or multi-layered content.

Currently only linking to headings 2,3,4 are supported. Looking to also include headings 5 & 6.

We would like to customize the look and feel of the sort and filter feature in the table. This would help ensure that the UI matches our product UI. Thank you.

Would it be possible to have the option to set expiration dates on Conditional Content. We have several articles that include information available to all of our clients but have some information that is exclusive to one or two clients for a period of time (typically one year). Rather than pend reminders for ourselves to go back to the article in one year and remove the Conditional Content settings, could we have the option to set either periods of time (30 days, 90 days, 1 year, etc.) or a specific date (e.g., "30/04/2027") when the Conditional Content removes itself? The block would then be visible to all readers who have access to that article.

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 Editor does not allow applying different colors to specific words within an article title. This enhancement would enable better visual emphasis and improve content readability. Providing the ability to style partial text within titles would help users highlight important labels or statuses more effectively.

Currently we can only see that an article has been replicated form the secondary location (where it was replicated too). There is no indication from the source article that it has been replicated. I think it needs to be indicated from both places to ensure the writer has the ability to decide to break the connection if ever they need to update only the source file.

Hi, In WYSIWYG editor: Frequently, I need to reference the HTML code for a published article that's not in EDIT mode. The only way I can do so is to click EDIT (see screenshot please) to force the article into EDIT mode. This extra step is cumbersome and should not be required. Suggestion is to allow READ-ONLY view of HTML code when the article is not in EDIT mode. Thank you.

I love the new feature where you can scroll a table with the freeze on the rows and columns! It would be helpful if this feature was available to put inside an accordion/FAQ style. In this way, since the table is so large that we are using the freeze feature, it would be helpful to have the information stored away inside an accordion, so it does not take up so much room. thank you

When you create a new table, its width doesn't automatically adjust to 100%, which would make the page responsive. Instead, the table width defaults to the size of the browser window. Even if you switch to Code view and manually set the width to 100%, the change won't be saved and the width will revert to that of the browser window. This behavior should be changed and default to the old implementation.