99 results found
-
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 -
Ability to Pick Nested Property for Header in Block List Properties
When enabling the "List" option for a "block" property type, adding blocks to an actual instance of my item only shows the name of the block type in the list and it is impossible to differentiate each item without opening them all (see attached screenshot). In the non-SaaS version of the CMS I see there is a way in code to set a nested property as the item header using
ListItemHeaderPropertyas described here https://docs.developers.optimizely.com/content-management-system/docs/property-value-listPlease enable the ability to select a nested property as the header in SaaS CMS, either via the API or the UI for defining content…
1 vote -
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 -
I would like to have editor on a field such as color picker
On a field in a content type, instead of asking editor enter color by hex code we would like to have an editor for color picker.
This should be built-in or somewhere from market or allow custom app.4 votes -
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 -
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!
-
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.
2 votesThis 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.
2 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.
1 vote -
Add Export Button to CMS Built-in Reports
CMS has several built-in reports under the Reports tab (Simple Addresses, Expired Pages, Link Status, etc.) that display useful content data, but none of them offer an export option. Users can view the data on screen, but have no way to download it, only copy paste it.
Adding a CSV export button to these reports would be helpful. The data is already being generated and rendered. The Simple Addresses report is a common pain point, as customers regularly need to audit simple addresses across their site and currently have to resort to Graph queries or custom API calls to extract…
1 vote -
Localised Alt Text Support with CMS/DAM Integration
There is no option to add Alt Text in multiple languages to assets when using the DAM Asset Picker within the CMS.
With the European Accessibility Act (EAA) taking effect in June it is imperative that we are able to maintain the level of accessibility (via localised alt text) that we had prior to using the DAM integration.
11 votesGood news - this idea is now being explored by our product and design teams. We’re researching potential solutions and scoping out what an implementation might look like.
-
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…
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!
-
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.
3 votesThanks for reaching out! I will look into this with design!
-
Opti SaaS allowing periods in the url
When using Opti SaaS to create a new page that includes a period, the resulting URL segment also contains the period. For example, if you create a page titled "Online on Oct. 4," the URL segment generated will be "online-on-oct.-4," which may render the page inaccessible. It is recommended that the SaaS product automatically remove periods from the URL segment when creating pages.
3 votesThe current url segment generation is based on the RFC 3986 where punctuation is a valid character to include in a URI, see section 2.3 in ietf.org/rfc/rfc3986.txt.
Could you elaborate on the problems you're seeing with these characters in URL's, as reality doesn't always have to align with theory when it comes to these things!
-
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 -
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 -
Assign approval workflow only to certain roles in CMS
When setting up approval workflows to publish content, the workflow gets automatically assigned to all roles.
However I only want to apply this review requirement to certian low level roles. I, as a Content Admin, should not have to send my own edits for review and then approve my own changes. It is multiple extra clicks, which is redundant.
When creating an approval workflow, I should have the option to assign it to specific roles. Roles not assigned to should be exempt from the need to send for review.
2 votes -
graph indexing
Request: ability to trigger Graph indexing job programmatically
If you update content types via import or API, my understanding is that you need to manually trigger the Optimizely Graph indexing job to sync those model changes to Graph.
The ability to trigger that indexing job via API would enable more automated processes for introducing changes to content types to a SaaS CMS instance.
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!
-
SaaS CMS Block Taxonomy
Request for SaaS CMS to support 'categories' or a comparable taxonomy at the block level.
9 votesThanks for sharing this feedback! We have both tagging and categorization as roadmap items as we know these are important tools for organizing content in CMS
-
thumbnail for content type
Add thumbnail image for content type or page type items so that the Create New screen doesn't consist of a million useless "no preview"images that mean absolutely nothing.
5 votes
.png){kind=link}
.png){kind=link}
- Don't see your idea?