124 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 -
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 -
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 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 -
CTAs are not removable when prompting external link or email
When a user:
Configures a CTA to link to an email address (mailto:) or external link
Saves and publishes the item/component
Returns later to edit the same item
…the user is unable to remove the optional CTA/link afterward.
This creates a blocking editing issue where previously configured optional email links become effectively permanent unless overwritten with another value.
2 votes -
Left navigation automatic setting
Create an automatic way, rather than doing it manually, to set the attributes that show in the left navigation bar. That functionality would allow the user to create rule(s) where an attribute would show as a filter only if the attribute meets a specified criteria - for example if 5 items in the category have a value, then show it, if not don't show. Currently no way to set up such a rule.
All I found is a way to say yes or no to attribute showing in the filters, more like an all-or-nothing situation.
8 votesThank you for sharing. We’re currently gathering additional feedback on this idea to understand wider demand. If you have any more context or examples you would like to share, please do include them - it really helps us understand how this would best support your workflow. Thanks for contributing to the conversation!
-
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 -
CMS Headless Preview Endpoint Selection
Editors cannot choose which head (localhost/dev/qa) to preview a page in - only one endpoint is available and tightly coupled.
2 votes -
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 -
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 -
Saas CMS LongString TextArea
Adding an optional toggle to allow Longstring properties to display as Text areas for CMS editors would be useful.
22 votesThank you for your suggestion! We have this on the roadmap, however not limited to LongString properties. As the regular string supports up to 255 chars it applies to this type as well.
-
editing our website is not intuitive and the button symbols are so rarely intuitive with their functions
I manage our website and we just switched over to Optimizely. It is FAR better than our old system! However, editing our website is not intuitive and the button symbols are so rarely intuitive with their functions. Minimally when you hover over a button it should tell you what it's function is, please!
1 vote
- Don't see your idea?