Currently there are two ways to display an asset in a site built with Liferay:
- Leverage a portlet that lists that type of asset and also provides a link to see the detail in the same page (blogs, asset publisher, ...)
- Create an specific page for that asset and use Web Content Display or Asset Publisher to manually select the asset.
The goal of this story is to create a new way that provides additional benefits such as:
- Provide more flexibility to control the look and feel of the page that displays assets of each type (since it will be built with page fragments not portlets)
- Provide an specific page (and URL) for displaying each asset (instead of it being dependent of the page where it's linked from).
The creation of an Asset Display Page is done through an editor that allows:
- Adding page fragments
- Map each editable text within the fragments with fields of the asset type selected. The mapping should take into account the types of editable elements. That way the UI should only allow mapping a text field to an editable text, an image field to an editable image, etc.
A Marketer can create several Asset Display Pages for an asset type. This allows using a different one for each specific asset. However, which should be used for assets that have not specified which specific display page to use?
To solve this, the marketer/designer will be able to specify which of the existing display pages should be used by default. The first display page to be created for an specific asset type should be marked as default automatically.