Visual Editor

For better content organization, I suggest adding internal tagging. That’s an efficient way to group all types of content (page, data model, section, etc.) that are related arbitrarily. Say you are running a sale event which needs 5 new pages 15 s...

Some CSS properties do not need to be seen by non technical members of a design team. There could be an option when registering a design token in the visual editor that lets you hide the display of the actual CSS value of a design token. For examp...

Custom components using type rich text quite a powerful tool. However it seems to be lacking 2 noticeable features. 1. the ability to control font size on rich text2. the ability to have more control over how bold text should be. Currently you can...

Allow developers to edit the style tab. Register new inputs for the style tab, such as overflow settings. Hide/remove inputs from the style tab. Rearrange the style tab. Validate inputs with custom rules and design tokens so that a design system i...

Custom tracking events are currently based on a session, the same as with conversion events. It would be great if there was a setting or something you could pass into a custom event to say this should be tracked to the session or only tracked dire...

It would be great to have the color swatches be the same as your design token colors instead of having to maintain both separately. Currently, even if you have design token colors set (and strict mode), the swatches are of different (default - but...

In order to be ADA compliant, there needs to be an ability to add a closed caption file to videos or a way to have auto generated CC's similar to other video hosting websites.

You should be able to easiliy query data based on it's presence in a folder. This would be very handy for using data in query on the page builder. For example, if I am showing a leadership page that displays the list of company leaders it would be...

Renaming inputs is currently a painfully awkward process since it takes quite some time for caches to update before those new names become available for use in the UI which is needed to have confidence that you're doing the right thing when updati...

Right now assets can only be categorized in the Asset Library in Production (Main). We stage all of our content on a Staging branches, so it's more work to go to production to categorize assets and then go back into Staging to use the assets