127 results found
-
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 -
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 -
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 -
Access to graphiQL
Hi Team,
The default GraphiQL dashboard operates on a single key principle, which means it lacks authentication mechanisms. Consequently, even if the consuming team implements the OIDC feature for authenticating graph usage, this authentication cannot be enforced when accessing the graph through the dashboard. As a result, "Read" access is granted universally, rather than being restricted to specific groups.
Implementing authentication for graph usage, potentially through the Identity Provider (IdP) that users log in with, would significantly enhance security. This approach would ensure that content is not universally accessible and is only available to authorized products, effectively "hiding" it from…
11 votesWe’re currently gathering additional feedback on this idea. If you have any more context, examples, or specific use cases, please share them - it really helps us understand how this would best support your workflow. Thanks for contributing to the conversation!
-
convert a page into an experience.
Client has requirement to convert convert a page into an experience in CMS SAAS.
11 votesThank you for reaching out. Can you give more concrete examples of the data loss you're describing.
-
Subject: Feature Request / Support Ticket: Support query-only parameters (?key=val) in External Link input to allow local domain control in
Ticket Details
Product / Feature: Optimizely Web Experimentation (Visual Editor / Link & CTA Configuration)
Request Type: Feature Request / Product Enhancement (Follow-up to support phone call)
Target Component: Visual Editor — External Link Input Field
Context & Background
Per our recent discussion with Optimizely phone support, we confirmed that the External Link input field currently auto-prepends http:// whenever an input is not formatted as a fully qualified, absolute URL.
Support advised us to submit this formal ticket to request functionality that permits entering query parameters only (e.g., ?utm_content=Homepage-hero) into the External Link input field without the system forcing http://…
1 vote -
Content Reference field should show additional information like ID, path etc.
Content Reference field shows only the name of the referenced item. In a large multisite implementation it is hard to determine if it is referring to the correct item
See attached screenshot, content-reference field shows a page named MBA-Cybersecurity, it shows the same page name upon hover.
There are several similarly named pages in our content tree, so it is difficult to see if it is referring to the correct page. Can we show additional metadata like the key, item path upon hover?
1 vote -
Isolated Optimizely Graph environment for automated & ephemeral testing
As a developer, I would like to run Optimizely Graph in an automated and isolated environment—such as CI/CD pipelines or GitHub Actions—so that I can reliably test features without relying on shared cloud instances.
A common example would be some kind of official container image that allows me to spin up a local or ephemeral instance of Optimizely Graph for integration testing.
6 votesWe’re currently gathering additional feedback on this idea. If you have any more context, examples, or specific use cases, please share them - it really helps us understand how this would best support your workflow. Thanks for contributing to the conversation!
-
Accessibility of show more link in blocks selection
In the content editor, on a page with blocks, there are details about which blocks are allowed for that property. The "Show all" link is barely readable contrast.
1 vote -
Conditional Content Tagging
Hello!
We have teams which we are migrating over to Optimizely SaaS who have a need for conditional content tagging. What I mean by that is when a category is selected on a block, it shows specific fields that are unique to that category. A category could have 0 unique fields or multiple unique fields.
This is important to help prevent our content model or blocks from getting "messy". The only way around this, that we've found, would be to either list out all available fields, which would be confusing to content authors, or have a unique block per category,…
5 votes -
Control how content is indexed in a content area, or a content area item.
When a block or page is added to a content area the 'Searchable' fields from the referenced page/block are automatically added to the _fullText field of the parent page.
I would like to have more control; for example, specify whether content in a content area is indexable, as when a page is referenced the content from that page are polluting the _fullText field of the parent page and causing content to be included in search results that are not relevant.
1 vote -
In-line blocks in a content area with "Unique value per language" setting turned on can't be translated
Currently, you can't edit inline-blocks within a content area outside of the master language. Meaning if you want to translate anything it's not possible unless you make it a shared block.
This makes it very difficult for content editors to understand but also maintain all of this as you'll be unnecessarily working with tons of shared blocks just to support the language/translation functionality.
The content area should be locked which is correct (no reordering) but the in-line blocks inside of it should still be translated.
4 votes -
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 -
Customisable Content Type Icons via API
Currently, Folder Page and Page have the same icon in the SaaS CMS making it difficult for users to easily identify the content type.
We would like the ability to update Content Types icons via the API.23 votes -
add a full URL read-only field in experience settings
In the Settings tab of the Experience properties panel, we currently only see the "Name in URL" for the individual page. It would be very helpful to also have a read-only field showing the full page URL, including all parent pages in the hierarchy.
This would make it much easier to quickly verify a page's complete URL path without having to navigate up through each parent page individually.
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 -
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 -
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!
- Don't see your idea?