Feature Request

We have some very long named snippets that version 2 just doesn't allow us to continue with our standard naming convention for snippets due to a character limit that does not appear to be an issue or limitation in the regular version of Document360

We use snippets for small sets of instructions that are included throughout our documentation. I'd like to be able to include variables such as buttons and field labels within the snippets.

We use a lot of snippets and it is inconvenient that we are unable to rename a snippet. I would like to have the option to rename a snippet or create a second copy of an existing snippet. It is time consuming to create a new snippet and delete the existing one when all I need to do is rename it.

For the global find/replace feature, add the ability to replace static text with variables/snippets. This seems like a fairly common use case. I have a term that appears hundreds of times in my docs, which is currently static text. I want to create a snippet for it, and then replace all instances of the static text with the snippet.

The customer initially added snippets in the Global language but is now exploring language-specific snippets to enable translations. However, since most of their articles are already published, there doesn’t appear to be a way to replace the global snippets with language-specific ones. They would like to know if there is an option to update the snippets from Global to language specific.

The customer would like to have the below implementations in the snippet. Dual States for Snippets: Implement draft and published states for snippets, similar to how articles are managed. Snippet updates remain in a draft state until explicitly published by the user. Context-Sensitive Snippet Versioning: When an article is in draft mode, it should reference the draft version of the snippet. Published articles should only reference the published version of the snippet. Change Notification: Notify users when a referenced snippet is updated. Bulk Publishing Workflow: Allow users to publish all pending snippet changes simultaneously, either from a centralized snippet management page or during the article's publication process. Provide an option during article publication to include snippet updates, e.g., "Publish article and related snippet changes." Change Tracking for Snippets

Currently, we have the option to check the revision history of an article which allows us to understand the changes made within versions of the article. Currently, there are no control/track changes on the snippet values. A feature to maintain the history of snippets and an option to roll back to the previous version of snippets would help us to maintain the history of snippets and understand who has made changes.

It would be nice if snippets weren't a forced paragraph block element, and could thus be used inline.

I'd like to be able to organize snippets in folders.

Please provide editing capabilities that apply to articles. We need the ability to open and edit snippets from within an article and ensure that they include all formatting features, such as adding variables, callouts, and accordions. Currently, we are unable to apply the note style we select as a callout in snippets, and the available font options for snippets are limited. Snippets should have the same comprehensive editing features as any other articles.