5 results found

1. 'view on website' should open in a new tab

   'View on website' should open in a new brower tab.

   7 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   Committed  ·  1 comment  ·  Content Manager  ·  Delete…  ·  Admin →
   How important is this to you?

   Nice to have You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

2. Bulk publish content item with all child items

   In Optimizely CMS (SaaS), there is currently no built-in way to publish a content item along with all its descendant items (child pages/blocks) in a single action. Editors must publish each item individually, one at a time, through the UI.

   Impact:
   For content trees with many nested pages or blocks (e.g., large campaign launches, section rewrites, or bulk imports), publishing item-by-item is slow and time-consuming, especially as the number of child items grows.

   Suggested solution:
   Add a "Publish with children" (or similar) action in the content tree/edit view that recursively publishes a selected item and all its descendants. Alternatively, expose a dedicated batch-publish endpoint in the Content Management API that accepts a parent key and publishes the full subtree server-side, rather than requiring per-item :publish calls.

   In Optimizely CMS (SaaS), there is currently no built-in way to publish a content item along with all its descendant items (child pages/blocks) in a single action. Editors must publish each item individually, one at a time, through the UI.

   Impact:
   For content trees with many nested pages or blocks (e.g., large campaign launches, section rewrites, or bulk imports), publishing item-by-item is slow and time-consuming, especially as the number of child items grows.

   Suggested solution:
   Add a "Publish with children" (or similar) action in the content tree/edit view that recursively publishes a selected item and all its descendants. Alternatively, expose… more

   4 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Content Manager  ·  Delete…  ·  Admin →
   How important is this to you?

   Nice to have You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating
   Committed  ·  AdminTom Bramley (Senior Product Manager, Optimizely) responded

   Thank you for raising this feature request. This is something we are actively pursuing and is on our roadmap to deliver later in the year.

3. Group Content Types

   In the PaaS version of the CMS it is possible to group Page and Blocks. This acts as a visual aid for editors allowing them to easily locate the relevant content type when there is a long list.

   This should also be manageable via the management api.

   4 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   1 comment  ·  Other  ·  Delete…  ·  Admin →
   How important is this to you?

   Nice to have You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating
   Committed  ·  AdminHåkan Edling (Senior Product Manager, Optimizely) responded

   Thank you for your feedback! This is on the roadmap!

4. Saas CMS LongString TextArea

   Adding an optional toggle to allow Longstring properties to display as Text areas for CMS editors would be useful.

   22 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   3 comments  ·  Editing Content and Visual Builder  ·  Delete…  ·  Admin →
   How important is this to you?

   Nice to have You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating
   Committed  ·  AdminHåkan Edling (Senior Product Manager, Optimizely) responded

   Thank 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.

5. 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

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   Committed  ·  0 comments  ·  Editing Content and Visual Builder  ·  Delete…  ·  Admin →
   How important is this to you?

   Nice to have You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating