57 results found
-
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…
7 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.
7 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!
-
Implement Image Renditions for CMS
The Optimizely Content Marketing Platform has a feature called "Image Renditions" which has several features to reduce friction for Web Editors managing images in the CMS.
This entire feature set looks promising, but here are 3 Key features which I'm most hungry for addition to the CMS:
• Option to Resize & Crop at the same time
• The addition of focal points for images
• The creation and management of multiple instances of a single image asset, in order to optimize view for the image to be displayed in multiple aspect ratios.Please consider adding this feature set, or any of its…
16 votesThank you for raising this feedback. We continue to develop our CMS x DAM integration and absolutely recognise the need for renditions in CMS. This is something we plan to bring to the product in the near future.
-
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.3 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.
9 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.
-
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.
4 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.8 votes -
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.
2 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!
-
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.
2 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!
-
Date/time element for forms
The current supported form types for SaaS CMS do not support a date/time element. This is a common element for dates, DOB etc
Reference
https://docs.developers.optimizely.com/content-management-system/v1.0.0-CMS-SaaS/docs/form-elements2 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!
-
User experience improvement for Export Data
There is an Export property setting option that appears at the bottom of a screen ONLY when one or more Content Type options are selected. It is otherwise unexposed, and perhaps in the wrong place. I have a suggestion.
TL:DR The problem arises when you select the Content Types section on the Export Data window, which presents a long list of content types. (See attached screenshots.)The user might select a few content types from the top or Select All and click Export and never see that the Export property setting option "magically" appeared off-screen below three other sections (Export tabs,…
2 votes -
PaaS Portal - Delete cached content also deletes Graph Cache
There should be a button (or by clicking the CDN-cache purge) that cleares/invalidates the Graph cache.
This is especially useful (necessary) when Graph synchronization fails, as the cache is only cleared upon sync completed.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.
1 vote -
Allow authorable field names in Forms
With the new SaaS forms, there is no way to set a custom field name. I can add an additional field to a from field in the CMS, but if I do that, I am blocked from publishing the form field. Field name is essential. When you submit a form in HTML, the 'name' attribute on a property is how the form knows what to submit. The examples you provide suggest formatting the label value. This is insufficient. An example of why this is a problem: If I am submitting a form to a third party service, like Eloqua, the…
3 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. We’ll share updates here as our thinking evolves.
-
Support Geo Seach on Content Types
I work on a tourism website where many of our content types are tied to a Geographic location. We would like the ability to 'Geo Search' the graph but I understand this is not possible using content types (i.e. PageData, BlockData etc). I am to understand this is only possible using custom types.
1 - Can the Geo Search capability be extended to support content types (pages and blocks etc)?
2 - In the meantime, to avoid confusion, can the documentation (https://docs.developers.optimizely.com/platform-optimizely/docs/geo-search) be updated to reflect that this is only possible on custom types?4 votesThanks for sharing this idea. Our product and design teams are looking into it now. We’re exploring possible solutions and figuring out what implementation could involve. We are also actively currently updating our documentation. We’ll keep you posted here as things progress.
-
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.
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!
-
Saas CMS LongString TextArea
Adding an optional toggle to allow Longstring properties to display as Text areas for CMS editors would be useful.
6 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.
-
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.
3 votes
.png){kind=link}
.png){kind=link}
- Don't see your idea?