Short version:

A set of configuration values for cache management should be a first class citizen, which can be applied to assets in the same way paint layouts or designs can.

Long version:

There are multiple levels of caching happening in any Matrix install, some of them configurable, some not. Eg.

> OS filesystem cache (not configurable within Matrix)

> Dejavu (on/off toggle only, not configurable within Matrix)

> Matrix cache (configurable)

> Proxy/Accelerator cache (configurable)

> Browser cache (configurable)

The current cache configuration UX quickly become impenetrable when configuring a site even with modest complexity. This situation is only going to get worse when we're using Trinity more. By reworking cache configuration as a first class citizen (ie, an Asset), we can reduce the complexity of the UX markedly and help both us and our customers achieve their desired outcome.

The idea is to create a cache settings screen (probably not an entire screen, perhaps just belongs on the existing settings screen for an asset) that allows applying a cache configuration to an asset, optionally cascading the configuration.

Further detail here: - https://squizmap.squiz.net/matrix/12194