117 results found
-
Give admins tenant-level control over enabling new platform capabilities
New platform capabilities (for example a new AI feature or a Visual Builder enhancement) are exposed to all authors automatically, so authors may see UI changes with no lead time or training. Request: administrator controls to stage the rollout of new capabilities - enable first in a Dev environment, train authors, pilot with one or a few sites, then roll out to Production when ready.
1 vote -
Do not pre-apply Files and Images filters in the DAM picker
When selecting an asset from the DAM inside the CMS, the picker pre-filters to 'Files' and 'Images,' and there is no way to disable these default filters. We would prefer no filters applied by default so authors get an unfiltered view of available assets. Request: make the default picker view unfiltered, or make the default filters configurable.
1 vote -
Automatic per-edit revision history with before-and-after diff
There is no automatic per-edit revision history. The Change Log records that a save or publish occurred, by which user and when, but identifies content only by machine references (ContentGuid, ContentLink, ContentTypeId) and does not show what changed. The Versions gadget requires manually creating version records and is capped at 20, which does not work for frequently edited pages. Request: automatic per-edit versioning with a visual before-and-after diff and no practical version cap. Our current platform provides this natively, including who made each edit, plus a site-level activity view.
1 vote -
Prevent silent overwrites of concurrent edits with conflict warning and field-level locking
Concurrent edits to the same page can be silently overwritten (last write wins). Both editors work against a single shared draft, so whoever publishes second overwrites the first with no conflict warning and no merge. The 'currently being edited' notice is dismissable and does not prevent this, there is no field-level locking, and comments are page-level rather than field-level. Request: a conflict warning on save or publish when another user has changed the draft, and/or field-level locking to protect in-progress edits.
1 vote -
Filter content by site or partner when selecting content in multi-site instances
When selecting content (for example using Select Content to reference a program), the picker shows content across ALL sites and partners on the platform with no way to filter to a specific site or partner. This creates governance and usability problems for large multi-site portfolios. Request: allow filtering the content picker by site or partner.
1 vote -
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.
1 vote -
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.
1 vote -
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.
1 vote -
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.
1 vote -
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.
1 vote -
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.
1 vote -
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.
1 vote -
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.
1 vote -
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.
1 vote -
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.
1 vote -
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.
1 vote -
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
- Don't see your idea?