15 results found
-
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.
-
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 -
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 -
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 -
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!
-
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 -
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 -
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 -
Saas CMS LongString TextArea
Adding an optional toggle to allow Longstring properties to display as Text areas for CMS editors would be useful.
11 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.
-
SaaS CMS Inconsistent Date formats
When editing a DateTime property in the CMS Content Types panel the date time is using my local format of dd/mm/yyyy. When a CMS Editor edits on the page the DateTime format changed to mm/dd/yyyy. It would be nice if DateTime pickers used the users local DateTime format throughout the CMS.
6 votes -
SaaS CMS Block Taxonomy
Request for SaaS CMS to support 'categories' or a comparable taxonomy at the block level.
4 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
-
SaaS Warning messages
It would be helpful to content editors if SaaS had a validation option for text or in general where we can chose to show a warning message instead of it always being an error.
1 vote
- Don't see your idea?