Feature Request

I need to know if any other articles link to the one I'm currently working on. This helps to both understand the relationship tree of information, but also to know what will break if I delete an article.

For Advanced WYSIWYG, the format toolbar should not be hidden away to the right along with the code button. I'd like to be able — or at least have the option — to see the toolbar at the top of my article, Microsoft Word-style. From a UI standpoint, I'm not sure how hiding this toolbar in the first place benefits users, since format is so critical when creating documentation. Thank you! :)

While editing an article, I'd like to be able to see whether a header is an H2, H3, or H4 without having to delete the header entirely. Perhaps have the header type to the left of the header when your curser is on that line? Thank you! :)

This request was created on behalf of Kristopher At this time, the entire table width is resized usign 'Fit to width'. We want each column should be sized based upon the content of all of the rows (not equally sized within the table's space). Thank you.

It would be ideal to have a schedule to unpublish in addition with the schedule to publish feature that was just released. Impact: Having a schedule feature in the product would make it so we wouldn't have to make calendar reminders to unpublish articles. Calendar invites can be missed and if someone is out of office unexpectedly the task can be missed. This requires the entire team to be added to calendar invites that then 'clutters' calendars and can get missed by accident. Use case #1: We consistently enhance our products, and sometimes that involves removing functionality or a module. We have a 'ramp down' and sometimes have no work on the article between when it is announced and final removal. Use case #2: We sometimes sunset products, sunsets can last from 1 to 3 years and after a end-of-support date we no longer update articles, sometimes this is a year or so before actual sunset. Use case #3: We post time-specific content, such as release notes, announcements, project/initiatives landing pages, etc. that are only valid for a period of time and then we want them removed from public view. Depending on the content this can range from a couple weeks to a couple of years depending on data retention policy.

Currently AI Chatbot is not supported in the Greek language. Our customers would like the AI chatbot to be available in the Greek language. Could you please check this and share your insights?

I am raising this request on behalf of the customer. Currently the category depth level is limited to 7 and there is request to increase the catgeory level limit.

The customer has requested that the sub-headings in the TOC section remain collapsed by default. We understand that we previously received a requirement to do the opposite—i.e., to have the TOC sub-items expanded—which led to our recent implementation. In light of these differing needs, we suggest implementing a toggle option that allows users to choose whether TOC headings are expanded or collapsed by default, based on their preference or requirement.

For both bold text and headers, what I'm seeing in the Advanced WYSIWYG editor is not what appears when I move to preview. For the attached pictures, each header is a) not in the correct font, b) not the correct size, and c) not the correct color. Is there any way to make edit mode look exactly like preview so I don't have to even switch back and forth? Thank you! :)

The customer reported that the terminology used during project export is a bit confusing. In a single-language workspace, using the regular project export option provides HTML/Markdown files, which led to some confusion. As a result, the customer mistakenly exported the offline documentation instead.