Page History

h2. Story

I can manage all assets I use on my web pages easily in AdminCentral. Assets may be stored inside a page, stored inside a special asset workspace and referenced in a page, or may even be located on an external storage device or space and referenced in a page.

There's a nice overview of all assets, whether they're stored locally on a page, in the asset workspace or on external storage; the overview groups assets according to their storage location and/or their type.

h2. Description of desired behavior

h3. Accessing Digital Asset Management

AdminCentral serves as the main hub to digital assets in Magnolia. It provides a separate entry in the [main menu|Main menu] for accessing [all three DAM levels|Digital Asset Management conceptual overview#Strategic placement] Magnolia defines and supports. Support for these levels lead to two types of setups.

h4h3. Setup 1: supporting assets attached to a page only

This setup covers the basic level as defined in [the conceptual overview of Digital Asset Management|Digital Asset Management conceptual overview#Strategic placement] only. Assets are not actually managed, but are merely uploaded to a single page and thus may not be re-used on another page at the same time. Still, Magnolia offers some support for controlling such assets by providing an overview over all assets used on all pages. There has been a significant amount of feedback requesting for an overview over all images and other media assets used on all pages. 

Assets on pages are internally mapped to an [asset set|Digital Asset Management conceptual overview#The Asset Type and Asset Set], which is accessed directly by clicking on the corresponding main menu entry in AdminCentral. This asset set can't be configured and its assets are not editable. Uploaded assets are mapped to an asset with a single rendition only and, again, both are not editable.

{mockup}


h3. Setup 2: supporting actual management of assets

The second setup adds actual asset management to Magnolia. This covers both the [intermediate and advanced levels|Digital Asset Management conceptual overview#Strategic placement], adding internal management and adapters to external systems at the same time. The main menu entry points to the main interface for asset management.

{mockup}

Assets on pages (see [setup 1|#Setup 1\: supporting assets attached to a page only] above) may still be supported, but that shall be configurable: it must be possible for certain sites to disallow uploading assets to pages and force editors to use managed assets only instead. If assets on pages are allowed, the overview showing the corresponding asset set is by default demoted to a sub menu item \- the asset set of assets on pages must not appear as equal among the other asset sets. This, again, could be configurable.

{mockup}