69 results found
-
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.
8 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…
10 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.
8 votesThank you for reaching out. Can you give more concrete examples of the data loss you're describing.
-
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!
-
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.16 votes -
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 -
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 -
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 -
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!
-
SaaS CMS -- undo/redo feature within versions
On PaaS CMS, there's an ability to roll back/undo changes made within a content version during the current session (see screenshot).
For ex: if I make multiple changes to this page, then clicking that "Undo" link will revert the last change (and clicking it again will revert the prior change, etc) all within the current content version.
In PaaS, if you leave the CMS, or just change pages within the CMS, that link goes away, but it can be helpful at times -- would be great to have this available in SaaS CMS.
5 votes -
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.
10 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.
-
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 -
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
…
1 vote -
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
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.
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.
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!
-
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
.png){kind=link}
.png){kind=link}
- Don't see your idea?