2 results found

1. 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 sub-features, to the Optimizely CMS.

   See documentation on this feature set here: https://support.optimizely.com/hc/en-us/articles/11190755829773-Image-renditions

   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… more

   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

   Building  ·  0 comments  ·  Media / Asset Management / DAM  ·  Delete…  ·  Admin →

2. SaaS CMS BasePage Type

   In PaaS, we could create a base page type, and then actual pages inherit from this, ensuring all pages have the same base set of fields. This is very convenient for several reasons:

   1. When creating a new page type, I only need to define the fields that are unique to the page type

   2. If I want to perform some action that looks at all pages, I have a hard time. I have to explicitly call out each page type for my graph query, and I cannot perform any query type actions like filtering based on fields that are custom to a page type.

   For example:

   I want to add a check box to all pages called "Exclude From Search". Then I want to create a my site search query. To get all pages I query on type _Page. But I cannot filter for this "Exclude From Search" field on the type _Page.

   It would be great to add fields right to _Page, or some other intermediary type, that I can query.

   In PaaS, we could create a base page type, and then actual pages inherit from this, ensuring all pages have the same base set of fields. This is very convenient for several reasons:

   1. When creating a new page type, I only need to define the fields that are unique to the page type

   2. If I want to perform some action that looks at all pages, I have a hard time. I have to explicitly call out each page type for my graph query, and I cannot perform any query type actions like filtering based on fields that are custom to… more

   5 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

   Building  ·  1 comment  ·  Other  ·  Delete…  ·  Admin →