Ideas

Background & Use Case Currently in L8 it is possible to add Cart Amount conditions to a discount of type "Cart Amount" and "Product Selection" (price lists) But this is a bit to limited, example use case is "Buy 2 of those products to get a Gi...

Case: If you are in the campaign tool and need to create a campaign for a certain target group, it's time consuming to have to go back to the customer area and create a target group. A solution to this would be a shortcut button in the campaign to...

Currently, if you look at a the block tab of a page where you've added blocks you can only see the template names of the blocks and not the name for that specific block (what is in the name field on the block) unless they're global blocks. We'd li...

Some issue that I think would greatly improve the user experience if resolved: Its unclear what block area a block is in Cannot move a block from one block area to another Cannot easily add a block at the bottom of a page if many blocks, add block...

It would be nice to have a trashcan for media like the one for pages. It often happen that clients accidently remove media files and folders, then they want them restored. As of today there is no way to do that.

Currently in edit mode, every field has a preview of it's content right below it. This adds a great deal of unnecessary clutter when you have a lot of fields that are multi culture. We'd like the ability to hide field previews, either all together...

As default in the Accelerator, CMS blocks can only link to pages, which is not enough for our customers and thus drives time in almost all projects. Litium is using the "Pointer" for CMS Urls, and that is typically a bad option, there should exist...

For an editor when using blocks it is hard to distinguish the type of blocks from each other for example in primary navigation in the headless accelerator. Especially when working with nested blocks as you can lose track of where you are if you ar...

To improve security it would be useful to enable multi-factor authentication for Litium login.

It would be great if the platform itself noticed when changes demands an incrementation of the Elistic search index prefix. As this is a manual operation for the development team, this should be automated with decrease risk of failing deploys to t...