Feature Request

Several help centers now have this widget that makes it easy for readers to feed the content into an LLM in a single click. Mintlify provides it by default. Can Doc360 provide this feature?

The left-hand navigation panel currently has a fixed width, which causes article and category titles to be truncated. This limits visibility and makes it difficult for users to quickly identify and navigate to the correct content, especially when titles are longer or similarly named. Requested Enhancement: Allow the left-hand navigation panel to be resizable, similar to functionality available in the portal view. This should include: Drag-to-resize capability for adjusting panel width Retention of user preference (optional but ideal) Responsive behavior to ensure usability across different screen sizes Business Impact: Improves navigation efficiency and user experience Reduces confusion caused by truncated or indistinguishable titles Enhances accessibility and readability of content structure Aligns functionality with existing portal capabilities Current Behavior: Left-hand navigation has a static width Article and category titles are truncated with limited visibility Expected Behavior: Users can resize the navigation panel to fully view titles as needed

The current “Listen” feature does not fully support accessibility when encountering tables. Instead of reading the table content, it provides a generic message such as: “There is a table present that you may want to look at.” This behavior limits usability for users who rely on audio narration, as it prevents access to critical information contained within tables. Requested Enhancement: Update the “Listen” feature to fully narrate table content, similar to standard screen readers. This should include: Reading table headers and corresponding row values Maintaining logical reading order (left to right, top to bottom) Clearly identifying header relationships for context Supporting complex tables where applicable Business Impact: Improves accessibility and aligns with inclusive design standards (e.g., WCAG compliance) Ensures all users can access table-based information without relying on visual interaction Reduces dependency on external screen readers Current Behavior: Announces presence of a table without reading its contents Expected Behavior: Fully narrates table structure and data in a clear, structured format

When a user clicks on an article, the focus in the Category Manager shifts to another item. We expect the focus to remain on the article that was clicked. Thanks.

Currently, high resolution images used in web pages causes them to be downloaded each time the page loads. This increases load time depending on the user’s internet bandwidth. When image resolution is higher, it further impacts performance and leads to slowness in the home page.

Request to implement Canonical URL for all Dedicated pages, like what's new/ Glossary/tags/contributor/search of the KB site 2.0 for both Normal and API versions.

Currently, only article URLs are indexed via the sitemap. Critical navigational and informational pages, including contributor profiles, tag listings, glossary term pages, and search-related structures, are excluded. Enhance the sitemap generation framework to include dedicated non-article pages. This will ensure complete URL discoverability for search engines and drive improved SEO performance across the Knowledge Base.

Currently, the breadcrumb display within the widget is inconsistent across different sections: In the Search results and Recommendations lists, the breadcrumb includes the slug for the article (while parent levels use titles). In Top searched articles, the breadcrumb correctly displays the parent levels and the article title. This inconsistency leads to confusion and affects the visual uniformity of the widget for end users. Requesting to standardize the breadcrumb.

Actual Behavior The navigation tree position changes inconsistently - sometimes shifting upward, sometimes downward - causing the selected node to move out of view. Expected Behavior The selected article in the navigation tree should remain consistently visible and positioned in a predictable manner (e.g., static or centered), similar to the behavior in the API documentation.

When Floik content is added to an article and users attempt to preview it, the experience may fail if browser pop-ups are blocked. Currently, there is no proactive notification guiding users to enable pop-ups, which can result in confusion and incomplete previews. This request proposes adding a user-facing notification prompting users to enable browser pop-ups when Floik content is detected during article creation or preview.