Feature Request

Currently, the “Link to Current Article Heading” functionality does not work when the target heading is placed inside an accordion block. Enhance the internal heading link functionality so that headings placed inside accordion components can be recognized as valid anchor points and linked to using the “Link to Current Article Heading” option.

Currently, Document360 inserts images as single block elements, which prevents authors from placing multiple images side-by-side within an article. This creates challenges when documenting product interfaces or workflows that require visual comparison. Documentation teams frequently need to display screenshots next to each other for scenarios such as: Comparing UI changes between product versions Showing different user experiences (e.g., Customer Portal v2 vs v3) Displaying before-and-after configuration states Presenting step-by-step visual differences across settings or pages At the moment, authors must rely on workarounds such as combining images externally, inserting images into table columns, or using custom HTML. These approaches add extra manual work, reduce editing flexibility, and can make articles harder to maintain when screenshots need updating. Native support for side-by-side images (for example, a multi-image block, grid layout, or image row option) would improve documentation clarity and significantly streamline the content creation workflow. This feature would be particularly valuable for teams documenting SaaS products, where UI comparisons are common and screenshots are frequently updated.

It'll be great to have an expanding section of text

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

Raising this feature request on behalf of a customer. Table columns needs to set as fixed and the horizontal scroll needs to be applied for the rest of the columns based on selection. Also, provide a CSV export option to export the table data that has been selected to be viewed. Please find the similar table requirement in link below for reference. https://docs.merge.dev/integrations/hris/supported-fields/

Currently, we have options to add conditional content to articles. But there is no centralised place in the portal for content creators to see where the conditional content is used across the portals. Hence, it will save a lot of time for the Users to go to a central place to manage all the dependencies of conditional content.

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.

It's currently very difficult to locate an image in Drive when you are starting with an Article open in the Editor. You have to carefully note the image name and then go searching in Drive for that specific image name. And this action alone makes you lose your focus on the article itself, because you must switch your focus to the Drive section of the portal. This loss of focus on the article is _especially_ bad when you had to temporarily fork the article just to view the image name. Now that you've lost focus on the article, it's easy to forget to undo the fork. So now you're in Drive, you've searched for the exact image name, and you see a results list. But the single file in the results list does NOT show it's location in the Drive folder hierarchy! There is NO possible way to learn where exactly that file sits in your Drive hierarchy! User expectations and use cases: Sometimes you want to find the location of an image so that you can review it in the context of all its sibling images. Are any of them stale and need removed or replaced? Maybe you want to bulk download a bunch of closely-related images to re-use in a lesson module in a training LMS? It should be an easy task to jump right from an image's location in an _article_ to that image's location (folder) in Drive.

Upgrading from CodeMirror version 5.x to 6.x for numerous benefits: Modular System, Language Support, Improved Editor View, Enhanced Handling of Multiple Changes, Support for ES6 Module Imports

Need the ability for content author to make edits and have reviewers see the changes (think Track Changes in Word)