127 results found
-
Improve multi-site management and navigation for cross-site editors
Managing multiple sites is not intuitive for users who work across sites. The long list of sites and pages down the left side is difficult to scan and navigate, which slows editors who move between many sites. Request: a more usable multi-site navigation experience (for example search/filter, grouping, or a collapsible site and page tree) so cross-site editors can find content and switch context quickly. This is especially important for large multi-site portfolios.
3 votes -
Add a filter to show only Blueprints on the Add Section screen
When adding a new section to a page, there is no way to filter to only Blueprints; they are comingled with all components. Request: add a filter and keyword search on the Add Section screen so authors can quickly find Blueprints.
3 votes -
Add spell check to the rich text editor
The rich text editor has no built-in spell check, and it overrides the browser's native spell check so even the browser no longer flags errors. Request: provide built-in spell check in the rich text editor, or at minimum stop suppressing the browser's native spell check so authors can catch typos.
3 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.
3 votesThanks for reaching out! I will look into this with design!
-
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.
3 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!
-
Show "Versions" gadget by default
When a new user accesses the CMS for the first time, they must manually add the "Versions" gadget to the UI. Can we have that included by default?
3 votes -
Enable Brotli Support For WebP and Avif
Brotli support can be enabled in Cloudflare for assets and is the best compression mechanism.
Also for Core WebVitals we and many other solutions compress images to Avif (best or WebP (second best so that they are delivered in the best way.
The default compression formats do not support these formats for Brotli https://developers.cloudflare.com/speed/optimization/content/compression/#compression-between-cloudflare-and-website-visitors and need compression rules enabled to support enabling it.
Current the DXP does not allow us to do that and we would like the ability to add these file types so that Brotli can be used.3 votes -
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 Content Variations in Export/Import
We would like support for Content Variations to be included when using the Export/Import feature
2 votes -
Add an external media embed option (YouTube, Vimeo, Wistia) to the rich text editor
The rich text editor has no option to embed external media such as YouTube, Vimeo, or Wistia videos. Authors can't place a video inline within body content without developer help or a purpose-built component. Request: add an embed action to the RTE toolbar that accepts a video URL (or oEmbed-compatible link) and renders a responsive player in both the visual editor and on the published page. This is common in higher-ed program content, such as program overviews, faculty introductions, and student testimonials. At a multi-site scale, requiring a custom component for every inline video adds friction for non-technical authors.
2 votes -
PA on a Page with a Content Area / nested Content Areas
For Preview functionality scrolling logic and OPE in the visual preview only works on property fields in Pages and the entire Content Area, but not on its in-line/shared items.
Using Pages with Content Areas containing nested blocks remains a core part of our implementation and workflow. Not supporting scrolling logic for these in-line items makes On-Page Editing practically unusable for our editors.
Please update the visual preview so that scrolling logic and focus behavior work properly on in-line and shared items inside Content Areas.
This is a critical issue for teams who rely on Content Area architectures and need a…
2 votes -
Enable selective block/page export across different paths
We are currently struggling using Export Content Items since we can not export specific blocks and pages from different paths into a single package.
As a workaround, we have to create multiple packages for each path and manually clean up the child content after importing.
We would like to request an enhancement to the export content items feature that allows us to cherry-pick specific pages and blocks across multiple paths
2 votes -
Give admins tenant-level control over enabling new platform capabilities
New platform capabilities (for example a new AI feature or a Visual Builder enhancement) are exposed to all authors automatically, so authors may see UI changes with no lead time or training. Request: administrator controls to stage the rollout of new capabilities - enable first in a Dev environment, train authors, pilot with one or a few sites, then roll out to Production when ready.
2 votes -
Automatic per-edit revision history with before-and-after diff
There is no automatic per-edit revision history. The Change Log records that a save or publish occurred, by which user and when, but identifies content only by machine references (ContentGuid, ContentLink, ContentTypeId) and does not show what changed. The Versions gadget requires manually creating version records and is capped at 20, which does not work for frequently edited pages. Request: automatic per-edit versioning with a visual before-and-after diff and no practical version cap. Our current platform provides this natively, including who made each edit, plus a site-level activity view.
2 votes -
Content dependency and impact analysis before publish, change, or delete
Before publishing, changing, or deleting a component, asset, page, or taxonomy term, authors have no way to see what references it. Request: a references or where-used view that lists every page, component, template, and experience that references the selected item, shown before the change is made. This is especially important in large multi-site environments where a single change can have wide downstream impact.
2 votes -
Allow inserting an image inline without navigating to a separate area
Adding an image requires navigating to a separate area, which interrupts the authoring flow. Request: enable inline image insertion directly where the author is working in the editor.
2 votes -
Reduce the number of clicks required to insert a link in the editor
Adding a link currently takes four to five clicks versus about two on our previous platform. For a very common authoring task, this adds up across a site. Request: streamline the link-insertion flow to reduce the number of clicks required.
2 votes -
Add word and character count to the rich text editor
The rich text editor has no word or character count. Request: display a live word and character count in the editor so authors can meet content standards and length limits without copying text into another tool.
2 votes -
Allow deleting a section or component from the Outline view
A section or component cannot be removed from the page-level Outline view. Removing one requires opening the section/component first and then using its options menu, which adds an extra step. Request: add a remove/delete action directly in the Outline view so authors can remove items in a single step.
2 votes
- Don't see your idea?