127 results found
-
Content dependency and impact analysis before publish, change, or delete
Before publishing, changing, or deleting a component, asset, page, or taxonomy term, authors have no way to see what references it. Request: a references or where-used view that lists every page, component, template, and experience that references the selected item, shown before the change is made. This is especially important in large multi-site environments where a single change can have wide downstream impact.
2 votes -
Improve multi-site management and navigation for cross-site editors
Managing multiple sites is not intuitive for users who work across sites. The long list of sites and pages down the left side is difficult to scan and navigate, which slows editors who move between many sites. Request: a more usable multi-site navigation experience (for example search/filter, grouping, or a collapsible site and page tree) so cross-site editors can find content and switch context quickly. This is especially important for large multi-site portfolios.
3 votes -
Allow inserting an image inline without navigating to a separate area
Adding an image requires navigating to a separate area, which interrupts the authoring flow. Request: enable inline image insertion directly where the author is working in the editor.
2 votes -
Reduce the number of clicks required to insert a link in the editor
Adding a link currently takes four to five clicks versus about two on our previous platform. For a very common authoring task, this adds up across a site. Request: streamline the link-insertion flow to reduce the number of clicks required.
2 votes -
Add a filter to show only Blueprints on the Add Section screen
When adding a new section to a page, there is no way to filter to only Blueprints; they are comingled with all components. Request: add a filter and keyword search on the Add Section screen so authors can quickly find Blueprints.
3 votes -
Filter the shared-block picker to blocks valid for the current section
The shared-block picker shows every reusable block on the site rather than only the blocks valid for the section or content area being edited. Invalid options appear (some grayed out, some opening to nothing), which makes the picker hard to navigate. Request: filter the picker to show only the blocks allowed in the current context.
5 votes -
Add spell check to the rich text editor
The rich text editor has no built-in spell check, and it overrides the browser's native spell check so even the browser no longer flags errors. Request: provide built-in spell check in the rich text editor, or at minimum stop suppressing the browser's native spell check so authors can catch typos.
3 votes -
Add word and character count to the rich text editor
The rich text editor has no word or character count. Request: display a live word and character count in the editor so authors can meet content standards and length limits without copying text into another tool.
2 votes -
Make the admin and authoring UI extensible with init modules, plugins, and custom editor descriptors
The admin and authoring UI is not customizable in SaaS. There is no support for initialization modules, plugins, or custom editor descriptors, which limits how far the authoring and governance experience can be tailored to a client's needs. These extension points exist in PaaS. Request: provide supported extension points so customers and partners can customize the authoring and admin experience in SaaS.
1 vote -
Allow deleting a section or component from the Outline view
A section or component cannot be removed from the page-level Outline view. Removing one requires opening the section/component first and then using its options menu, which adds an extra step. Request: add a remove/delete action directly in the Outline view so authors can remove items in a single step.
2 votes -
Add an edit button to edit pages from the live front-end
When viewing a page on the live/front end there is no edit button and no back button, so authors must open a new tab or navigate away and re-find the page in the CMS to make a change. Request: allow a logged-in user to jump straight into editing from the live page via an edit button. Our current platform supports this and it significantly speeds up routine edits.
1 vote -
Keep editor focus at the component level after saving a component
After saving a modified component, the editor returns to the page level instead of staying at the component just edited. When editing several components in sequence, this forces the author to re-locate and re-open the next component each time, interrupting flow. Request: after save, keep focus at the component level (or return to the edited component) so authors can continue editing adjacent components efficiently.
2 votes -
Allow arbitrary nesting of components inside other components
Component nesting is currently flat: a component can only be dropped inside another component if that nesting was purpose-built into the component definition. Authors cannot nest components arbitrarily at edit time. Request: allow authors to drop components inside other components' content areas without each nesting relationship being pre-built by a developer. Our previous platform allowed this flexibility, which matters for building richer layouts without custom development for every combination.
2 votes -
Cannot create custom folder-type instances inside shared blocks from the CMS UI
In Optimizely SaaS CMS there is no way to create an instance of a custom folder content type (a content type based on the folder / _folder base type) inside a shared block through the CMS UI. The New Folder action creates only the built-in system folder type and offers no picker to choose a custom folder type. Separately, the New Folder action is currently not working at all in this context. As a result, custom folder instances can only be created via the Content Management REST API or Opal.
Steps to reproduce:
- Define a content type based on the…
4 votes -
Include component name in validation error message
Currently, when we try to publish and some required properties are missing from an experience or a component from the experience outline, we only see a simple validation message that the property is missing. The problem is that we might have that property on many components and we can't tell from the validation message alone which is the component that causes the problem, so we have to manually find it.
It would be great to also include the component name in the validation message.
1 vote -
Shareable external preview links for unpublished (draft) content
Problem
In Optimizely CMS (SaaS) there is currently no way for content editors to generate a long-lived, shareable preview link for unpublished/draft content that external stakeholders can open without a CMS / Opti ID account.
Current limitations:The official preview token expires in only 5–10 minutes.
The only official recommendation is to give stakeholders limited CMS access so they can open the page in Visual Builder themselves.
This creates friction for external reviews (clients, legal, marketing stakeholders, executives, agencies, etc.) and forces customers to either:
Maintain a separate staging environment, or
Build custom workarounds.This was a solved problem on…
1 vote -
Support relocating components across fields without recreating them
We need the ability to move an existing component from one content field to another (e.g. from one column to a different column that allows the same component types), not just duplicate it in place. Currently there's no way to relocate a component across fields — the only option is to delete it and fully recreate it from scratch in the destination, re-entering text, re-uploading/re-linking images, and reconfiguring settings each time. This makes routine page reorganization slow and error-prone, especially for content-heavy components like Rich Text blocks or Link Columns.
10 votes -
Bulk publish content item with all child items
In Optimizely CMS (SaaS), there is currently no built-in way to publish a content item along with all its descendant items (child pages/blocks) in a single action. Editors must publish each item individually, one at a time, through the UI.
Impact:
For content trees with many nested pages or blocks (e.g., large campaign launches, section rewrites, or bulk imports), publishing item-by-item is slow and time-consuming, especially as the number of child items grows.Suggested solution:
Add a "Publish with children" (or similar) action in the content tree/edit view that recursively publishes a selected item and all its descendants. Alternatively, expose…12 votesThank you for raising this feature request. This is something we are actively pursuing and is on our roadmap to deliver later in the year.
-
Retrieve references/usages of local (inline) blocks
For shared blocks and other content types, we can already query Optimizely Graph to find every instance of a given type. For example:
query FindByType {
_Content(where: { _metadata: { types: { in: ["<ContentTypeName>"] } } }) {
total
items {
_metadata { key displayName types url { default } }
}
}
}This works because shared blocks are standalone content items with their own key/ContentLink, so they're indexed and queryable like any other content type.
Local (inline) blocks don't support this. Since they're stored as embedded property data on the parent content item rather than as standalone content…
6 votes -
Need the ability to set the TinyMCE Toolbar height
CMS (SaaS) does not currently expose an explicit height/width setting for the rich-text editor. Unlike CMS PaaS (where the editor size can be set in code via the TinyMCE Configuration API), SaaS is configured entirely through the content-type contract, and the only editor setting available for a rich-text property is the toolbar preset.
As a developer worried with the user experience, I would like to have the ability to set the text area's height, at least.
1 vote
- Don't see your idea?