Skip to content

CMS SaaS (Content Management System)



CMS SaaS (Content Management System)

Categories

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

26 results found

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

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  2. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  3. Editors cannot choose which head (localhost/dev/qa) to preview a page in - only one endpoint is available and tightly coupled.

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  4. 2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  5. There should be an undo button that restores the visual builder page to its state before a new section was added or modified.

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  6. Editors cannot choose which head (localhost/dev/qa) to preview a page in - only one endpoint is available and tightly coupled.

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
2 Next →
  • Don't see your idea?