Ideas

When using Litium in a project which has nullables enabled the services seem to incorrectly always indicate that they are not null. For example VariantService.Get() says it returns a non null Variant. Which makes using the full nullable functional...

If Accelerator source code was moved to github or some other accessible repo it would be possible to: Fork the repo so that partners could create and maintain their own accelerators Create pull requests so that bugfixes could be created by the co...

Add a new entity type for custom data based on the field framework with templates and fieldtypes In many project we need to add data that's not directly related to pages or products and we often add custom tables to the db to support this data. In...

Change the way history is presented. Today the History tab is useless: It holds so much data that the site just loads for a long time to in the end is not able to present it. When the history in the beginning did load (because it didn't have that ...

The possibility of adding restrictions on what a back office admin is allowed to edit. For example a “EnglishAdmin” user can edit the english values of Website fields, but not the swedish values.

It would be useful to be able to add custom fields to addresses in Customers. This could be used for receiver company name, address-id, delivery information etc.

In Litium 8 you can't see which channels a variant is published on in a single view, you have to open up all markets using the "Select variants"'popup and find the variant to see if it is published there. This makes publishing very tedious if you ...

It would be useful if a field template could inherit fields from another template by marking it as parent. That would allow creating a single base template with fields common to all products and new templates would just need to define its unique f...

A button in Backoffice to force a purge of the Redis cache.

On front end be able to display product variants based on a choosen field. Sort accending or Decending. Preferable a field on category template/level