43 results found
-
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 -
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.
-
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 -
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 -
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 -
Include component name in validation error message
Currently, when we try to publish and some required properties are missing from an experience or a component from the experience outline, we only see a simple validation message that the property is missing. The problem is that we might have that property on many components and we can't tell from the validation message alone which is the component that causes the problem, so we have to manually find it.
It would be great to also include the component name in the validation message.
1 vote -
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 -
Shareable external preview links for unpublished (draft) content
Problem
In Optimizely CMS (SaaS) there is currently no way for content editors to generate a long-lived, shareable preview link for unpublished/draft content that external stakeholders can open without a CMS / Opti ID account.
Current limitations:The official preview token expires in only 5–10 minutes.
The only official recommendation is to give stakeholders limited CMS access so they can open the page in Visual Builder themselves.
This creates friction for external reviews (clients, legal, marketing stakeholders, executives, agencies, etc.) and forces customers to either:
Maintain a separate staging environment, or
Build custom workarounds.This was a solved problem on…
1 vote -
Saas CMS LongString TextArea
Adding an optional toggle to allow Longstring properties to display as Text areas for CMS editors would be useful.
22 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.
-
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 -
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 -
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 -
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 -
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 Block Taxonomy
Request for SaaS CMS to support 'categories' or a comparable taxonomy at the block level.
10 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
- Don't see your idea?