73 results found
-
Allowable Section Types in an Experience Type
Can we have allowable section types in an Experience Type?
In a large implementation, we can have several components/blocks enabled as 'Sections' so that they can be directly added to the Experience page.
The GraphQL query for an Experience becomes very big as we specify more blocks as 'sections' Can we add a feature where a developer can define 'allowable' sections on an experience, so that the graphQL query that is formed contains only a limited allowable types?
1 vote -
Monitoring & Alerting
Monitoring & Alerting
Optimizely to enable monitoring and alerting capabilities:
I. Monitoring
Development of a dashboard for API monitoring, providing visibility into:
⦁ API availability
⦁ API failures
⦁ Traffic trends
⦁ Infra utilizationII. Alerts (Email & Mobile)
Enable proactive alerts to RAKBANK stakeholders for:
⦁ Any API failure
⦁ No traffic detected
⦁ High CPU utilization
⦁ Hardware‑related issuesIII. Alerts should be delivered via:
⦁ Email
⦁ Mobile notifications1 vote -
Is DNS SEC on Optimizely's roadmap and when will it be targeted?
We would like for Optimizely to offer the capability to support DNS SEC for security reasons and are wondering if / when this will be available. Thank you, Laura
2 votes -
Drag-and-drop reordering for repeatable content structures
Currently, repeatable or ordered content structures within CMS: such as table rows/cells, and content links, rely on manual move up/ move down controls to reposition content one step at a time.
For example, within our Table Block, authors must repeatedly click move up/down to reorder rows or cells, which can become inefficient for larger content structures.
This request is to add native drag and drop reordering functionality for applicable repeatable content structures within the CMS authoring experience.
Desired Behavior:
Authors can drag and reposition items in a single action
Visual drag handles or intuitive reorder controls
Improved efficiency over repeated…7 votes -
CMS 13 - DAM Asset Picker Showing Multiple CMP instances
In CMS 13 with CMP DAM integration, the DAM Library Picker currently prompts users to manually select a CMP instance when they have access to multiple instances. For users such as partners who frequently work across multiple instances, this creates unnecessary friction and interrupts the workflow.
The expected behavior is that CMS should automatically open or restrict the picker to a specific CMP instance based on its configuration, eliminating the need for manual selection. The DAM Library Picker already supports targeting specific instances (e.g., via instanceIds), but this capability is not currently utilized or exposed in the CMS integration.https://docs.developers.optimizely.com/content-marketing-platform/docs/library-picker#pass-options-in-url
…
2 votes -
Retain outline structure on all translations when making changes in Experience
When I have multiple languages of my site and I want to retain the outline of my Experience of all languages this is currently not synced. When I move sections around I have to manually do this for every language.
We would like an option to keep the outline in sync for all languages, and only adjust the translations
Currently Experiences are not an option for sites that use multiple languages but are managed by a single team that wants the same structure. They are better off using Pages
2 votes -
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.
2 votes -
Include OCP synced fields in CMS search
Problem
CMS search currently only finds synced assets by title. Users cannot search metadata like description, tags, or other synced external fields.Request
Allow internal CMS search to index and search OCP synced metadata fields.Examples
Description
Tags / Keywords
Categories
Custom external fields
Product IDsExpected Outcome
Users can find synced assets using metadata, not just title.Value
Better asset discovery, faster editor workflow, improved usability.2 votes -
On-Page Editing not available when using the JS SDK
On-Page Editing (https://docs.developers.optimizely.com/content-management-system/v1.0.0-CMS-SaaS/docs/live-preview-with-react?_gl=1*ye51gc*_gcl_au*MjUyOTYwNjQ4LjE3NzMxNTUxMzcuMTg0NzgxNDg3NS4xNzc2NzgxMjQ4LjE3NzY3ODE0MDU.*_ga*MTMzMjkyMTY1My4xNzczMTU1MTM3*_ga_C7SLJ6HMJ5*czE3NzY3ODEzMDAkbzE1JGcwJHQxNzc2NzgxNDM2JGo2MCRsMCRoODIzOTg0Njc1#use-preview-utilities-for-on-page-editing) is not currently available in the JS SDK (https://github.com/episerver/content-js-sdk/issues/270#issuecomment-4236777609).
2 votes -
property-level permissions
Ability to set permissions either at the property level or the tab/property group level.
Example scenario: you have SEO fields on a page/experience type that only people in an "SEO Manager" role should be able to modify, while other roles can modify the rest of the page properties/content.
1 vote -
Undo Button for Visual Builder
There should be an undo button that restores the visual builder page to its state before a new section was added or modified.
2 votes -
Restrict Content and Content types via API keys to a group or site
As a CMS admin, I want to provide access to my development team/delivery apis to a site or sites and content types with the right level of access. (Read, Edit, delete, Create)
This would enable teams to work in an isolated manner that.
One thought is to be able to assign a Content type to a Site or Sites.
1 voteThis effort will be taken up as part of an API framework that will be added to our REST API's. We are expected to pick up the development later in 2026.
-
Desktop/Tablet/mobile feature for preview is not available for standard page in visual builder
For content managers and editors, it is essential to have the ability to preview pages across multiple device types. Currently, this functionality is limited to Experience Types only.
This is a significant gap, as standard pages are also being created and previewed within the Visual Builder. Enabling multi-device preview for these pages would greatly enhance the content editing and validation experience for editors and managers.
1 vote -
Boosting to be be applied directly to a nested field like HeroBlock.Heading in the where clause.
I'm a developer, currently using optimzely CMS SaaS. My client would like to take advantage of boosting for specifc fields in a where clause of our GraphiQL search queries. I have learned however that in Optimizely Graph, boosting can be applied only directly to fields that belong to the top level content type, such as Title, MetaDescription, or _fulltext. These properties are directly available in the GraphQL schema for the content type, which is why boosting works as expected when applied to them.
Properties that belong to blocks placed inside a Content Area, such as the Heading property in a…
1 voteWe’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!
-
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,…
3 votes -
Optimizely DAM picker in TinyMCE
Today, it’s not possible to insert an image or video from Optimizely DAM directly into the TinyMCE rich text editor (unless using a third-party component).
For customers migrating from the built-in CMS media library to Optimizely DAM, native support for this would be expected.
This applies to both SaaS CMS and CMS 13.
2 votes -
TinyMCE editor toolbar configuration
I'm a software developer. I would like to be able to configure the toolbar of the TinyMCE xhtml editor in Optimizely CMS SaaS so it matches the exact wishes of my client. Currently we only have 3 options: minimal, standard and extended. It would be convenient if we could configure the toolbar ourselves. I'm think of an option to insert code snippets, but also simple thinks like support for H2 to H5 but not H1. Basically, I would like to be able to configure everything that TinyMCE allows to be configured out-of-the-box.
2 votes -
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.
2 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!
-
Converting single use blocks into shared blocks easily
Currently blocks created for a specific page cannot be covered into shared blocks. (Shared blocks can be covered into single use block). Therefore if we want to convert the single use of block into a shared block, we will have to create a shared block from the scratch. This functionality is available in other headless CMSs and I believe it's useful.
9 votes -
Setting expiration and scheduled publish date
The idea is to place the expiration date and scheduled publish date together. So a content integrator can see at glance what dates have been set on the page and on the dashboard. The current counting down the expiration date can be kept, perhaps next to the end date itself.
2 votesThanks for reaching out! I will look into this with design!
- Don't see your idea?