43 results found
-
Content Reference field should show additional information like ID, path etc.
Content Reference field shows only the name of the referenced item. In a large multisite implementation it is hard to determine if it is referring to the correct item
See attached screenshot, content-reference field shows a page named MBA-Cybersecurity, it shows the same page name upon hover.
There are several similarly named pages in our content tree, so it is difficult to see if it is referring to the correct page. Can we show additional metadata like the key, item path upon hover?
1 vote -
Ordering of content in UI
Scenario: An editor creates many news articles and then needs to find them again in the UI.
Challenges
Any content, when added, is ordered in the order it was created, not alphabetically. This makes content difficult to find in the content tree.You can manually reorder content, but this takes time.
In PaaS, you can define how child content is ordered; this isn't available in SaaS, and I feel it would be beneficial to bring this feature back, as we are getting a lot of negative feedback from the clients' editors.
Or, at least in the short term, order the…
3 votes -
Language management on Multiple sites
Scenario: I have a SaaS instance with multiple sites/applications enabled and multiple languages enabled.
Challenge 1
In CMS 12, the admin was able to configure which languages are enabled for the site; this is no longer available and leads to confusion for editors.Editors should be able to edit content and work only in the languages enabled for that site.
Challenge 2
I want to create a new application/site, and the master language is different to the master language of all the other sites.i.e. I want to create a site where the master language is zh-hant, not the default…
3 votes -
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 -
Choose whether to copy child pages, and how many levels, when copying a page
When a page that has child pages is copied, the CMS always copies the entire subtree. There's no way to copy only the parent. Request: when copying a page, let the author choose to copy the parent only, or the parent plus its children. If children are included, let the author choose how many levels deep to copy. We need both: duplicating a single page as a starting point without its subtree, and cloning a section or template tree to a chosen depth to stand up new sites. Related: "Option to do a shallow copy when duplicating (copy/paste) a page"…
3 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 -
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 -
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 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 -
Filter the shared-block picker to blocks valid for the current section
The shared-block picker shows every reusable block on the site rather than only the blocks valid for the section or content area being edited. Invalid options appear (some grayed out, some opening to nothing), which makes the picker hard to navigate. Request: filter the picker to show only the blocks allowed in the current context.
4 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 -
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 -
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 -
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 -
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 -
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 -
Cannot create custom folder-type instances inside shared blocks from the CMS UI
In Optimizely SaaS CMS there is no way to create an instance of a custom folder content type (a content type based on the folder / _folder base type) inside a shared block through the CMS UI. The New Folder action creates only the built-in system folder type and offers no picker to choose a custom folder type. Separately, the New Folder action is currently not working at all in this context. As a result, custom folder instances can only be created via the Content Management REST API or Opal.
Steps to reproduce:
- Define a content type based on the…
4 votes -
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
- Don't see your idea?