Skip to content
← Turn your feedback into functionality

CMS PaaS (Content Management System)

CMS PaaS (Content Management System)

Categories

Welcome! 👋

(thinking…)

Enter your idea and we'll search to see if someone has already suggested it.

If a similar idea already exists, you can support and comment on it.

If it doesn't exist, you can post your idea so others can support it.

Enter your idea and we'll search to see if someone has already suggested it.

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback

65 results found

  1. Being able to delete/move to trash orphaned blocks and media

    As an editor I would like to be able to remove/move to trash a block or a media content item from the property view in the CMS.
    As it is now you need to have the Block or Media widget open, and if a piece of content is orphaned you don't see it in any list.
    I would like there to be a delete and move option the "Tools" dialog (See attached screenshot.
    A alternative solution would be to have a automated "Orphaned" folder in the block/media view so you can actually select the delete option from there.

    22 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    Gathering Feedback  ·  0 comments  ·  Editing (Content)  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

  2. Visual compare feature in core product

    We're using this add-on on Episerver World and it's very good: https://www.david-tec.com/2018/03/visual-compare-option-available-for-episerver-11/
    I think it should be included in the core product so that it is available to everyone.

    13 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    Gathering Feedback  ·  0 comments  ·  Editing (Content)  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

  3. On-page comparison tool improvement

    When comparing a submitted version of a page to the published version of a page, it would be helpful to have an indication of what content has been added, edited, or deleted. Currently we need to eyeball it to see what the submitter has changed and I'm sure edits are being missed. If we only had to check the places that were changed, it would streamline the process and lower the amount of time spent on each page.

    5 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    Research & Design  ·  0 comments  ·  Editing (Content)  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

  4. As an editor, I'd like to see where my content blocks are used in the Catalog.

    Currently, if we author a block within the catalog but then go to make edits to that block we often see "this block isn't used anywhere" but that is false. It would be helpful to know all the placements within the catalog.

    9 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    Research & Design  ·  0 comments  ·  Editing (Content)  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

  5. Allow container pages that don't generate a URL segment

    Some functionality cascades down the page tree, like approvals or permissions. Sometimes you want to group pages together so you can apply values and functionality to branches of pages, but these necessarily affects the URL, since any page generates a new URL segment.
    "Container" pages can't be accessed directly, but they still generate a URL segment, so they can't be transparently used for grouping content.
    It would be helpful to allow a type of container page that doesn't generate a URL segment. When ancestors are collected to form a URL for a descendant page, this type of page could simply…

    3 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    Gathering Feedback  ·  0 comments  ·  Editing (Content)  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
1 2 4 Next →
  • Don't see your idea?