Feature Request

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.

Add a built-in feature to convert Advanced WYSIWYG (rich-text) articles into clean, standards-compliant Markdown with a single action. Problem Statement Many teams author content using Advanced WYSIWYG editors because they’re user-friendly and support rich formatting. However, Markdown (MD) is increasingly preferred for: -> AI/LLM crawling and ingestion -> Developer documentation workflows -> Version control and diffing -> Content portability across platforms Currently, converting WYSIWYG content to Markdown requires manual effort or unreliable third-party tools, leading to: -> Formatting inconsistencies -> Loss of semantic structure (headings, lists, code blocks) -> Increased friction in publishing pipelines

Near release, 3 reviewers need to review release notes in a limited period of time. There is not enough time or flexibility to wait until another reviewer has finished. Reviewers need to be able to review at the same time.

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

I strongly urge you to consider how the custom data attributes affect our ability to use the code view. If such data needs to be added for things to work on your end, they should be added after processing the page, and not rendered in the code view. The way it is implemented now adds undue complexity for your users to sort through your added code. It makes for a quite bad user experience.

In addition to the accordion and tab options in articles, add an "image carousel" insert option that allows users to "click" through each image individually. This would prevent the article from getting too long when there are images included, reducing the user's need to scroll.

We need the ability to link words or phrases within inline code blocks to other articles. Currently, the Doc360 editor supports inline linking, but the link doesn't render in the editor or on the published site, making it invisible to users (images 1, 2, and 3). This native support is critical for our documentation, as we frequently use inline code for visual formatting of important terms and require those terms to be linked to topics that explain at length about them.

Currently, code blocks don't have line numbers. I'd like to include line numbers so that I can refer and explain specific line sections (for example, lines 9-16, etc) in documentation

We often have very long tables in our docs that users would like to filter for specific headings. It would be great if this could be implemented.

Enable the ability to be able to multi-select different sections of an article that will have the same formatting. This will save a lot of time. Now, if I want to change the formatting of all H2 headers, I have to select each one to make the change. Similar concept with a paragraph; if I want to change the formatting to highlight certain words to bold them all at once, I have to change each one individually.