Page History

...

The list view shows all assets of a particular asset set as a flat list. Thus, if this asset set supports folders, the list ignores the hierarchy set up by them and shows all assets of all levels at the same time. Note that the list view only shows the assets in a single asset set, since every asset is at least contained in one asset set. You may not obtain a list of all assets in all asset sets at once.

The list view is very convenient to sort all existing assets using one of the criteria shown by columns. The columns shown typically also contain the asset's status (published, changed and published, unpublished) and an indicator if the asset is currently in a work flow.

...

Renditions are shown along their typical characterizing data set allowing to easily identify one specific rendition. Such data could include a format string combining both their format, resolution, and color info (or whatever is appropriate for the asset type). It should also be obvious if a rendition is currently published or not, and whether it is being currently worked on in a work flow. For rows showing renditions, the column layout of the surrounding tree does not apply, but information should nevertheless appear well aligned and ordered to ease reading.

...

It's ok to allow a user to select both renditions and assets at the same time, even though the actions and preview view may then not show much of interest and mostly disabled actions only.

...

By default, the list view shows the list of assets. You may UX:open an asset to show its renditions. A switch in the toolbar allows to switch the list to show the (flat) list of all renditions instead. This comes in handy if you would like to sort renditions by one of the criteria offered by the table columns or if you'd like to restrict the list to only show items you may actually place on a page (that's what renditions are for).

...