Uploaded image for project: 'PUBLIC - Liferay Portal Community Edition'
  1. PUBLIC - Liferay Portal Community Edition
  2. LPS-76805

As a Designer or Marketer I can create a display page associated to a web content structure to determine how the web content will be displayed

    Details

    • Type: Story
    • Status: Closed
    • Priority: Minor
    • Resolution: Completed
    • Affects Version/s: None
    • Fix Version/s: 7.1.X, Master
    • Component/s: WCM
    • Labels:
    • Priority Level:
      Low
    • Epic Link:
    • Sprint:
      09_Sansa Stark, 11_Viserys Targaryen, 12_Catelyn Stark, 13_Cersei Lannister (Week 16), 14_Jorah Mormont, 15_Bran Stark, 17_Jorah Mormont, 16_Arya Stark

      Description

      Currently there are two ways to display a web content in a site built with Liferay:

      1. Leverage Asset Publisher to display a list of web content and allows users to click on them to show the web content in detail (either within Asset Publisher or "in context")
      2. Create an specific page for that web content and use Web Content Display or Asset Publisher to manually select the asset and display it.

      In order to be able to display a web content "in context" the site must have an associated "Content Display Page". This is a traditional layout page built with widgets (aka portlets) which has one Asset Publisher portlet which will be used to display the detail of the "selected" web content. Web Content which have an associated Display page gain a unique URL for displaying the web content (which is dependent of the page where it's linked from).

      The goal of this story is to improve the solution to this use case providing additional benefits such as:

      1. Make it easier to create a display page for web content. All Display Pages will be listed in a single administration UI separate from other pages.
      2. Allow associating a display page as the default for web content with an specific structure so that it's not necessary to associate each web content with it individually.
      3. Provide more flexibility to control the look and feel of the page that displays assets of each type (by leveraging page fragments instead of widgets)

      The Web Content Display Page will be built using an editor that allows:

      1. Adding page fragments
      2. Map each editable text within the fragments with generic fields of a web content and the view of the web content (rendered with its template). 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. (Note: LPS-76821 will add the ability to map fields that are specific to the selected structure)

      A Marketer can create several Web Content Display Pages, even several for each structure. 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.

      It's worth noting that any existing web content display page created with the old mechanism (the Content Display Page page template) will still work. It will also still be possible to associate new web content to the traditional display pages.

       

      Mockups
      https://liferay.invisionapp.com/share/2WGG9DB389Q#

      Style and use cases

      https://liferay.invisionapp.com/share/CBI5I9EZVEX#/

        Attachments

          Issue Links

          1.
          Creation of Asset Display Pages Templates Technical Task Closed Brian Chan  
          2.
          Update sidebar to allow multiple tabs Technical Task Closed Brian Chan  
          3.
          Register contributors for asset display pages Technical Task Closed Brian Chan  
          4.
          Show assets and fields in order to allow mapping when creating an Asset Display Page Technical Task Closed Beatriz Martin (Inactive)  
          5.
          Create new layout type controller for asset display pages Technical Task Closed Pavel Savinov  
          6.
          Create URL resolver for Asset Display Pages Technical Task Closed Brian Chan  
          7.
          Show content for a specific asset type if there is a contributor for it Technical Task Closed Brian Chan  
          8.
          Prepare Journal and Blogs Asset Display Contributors so that they can be rendered in their default template Technical Task Closed Brian Chan  
          9.
          Allow the user to set an asset display template to be the default one for a given asset type / sub type Technical Task Closed Brian Chan  
          10.
          Remove WC Display Page Template Technical Task Closed Brian Chan  
          11.
          Mark as deprecated the old features that are better solved by the new Display Pages Technical Task Closed Brian Chan  
          12.
          Change the display page selector (used when editing a web content) to allow selecting the new display pages Technical Task Closed Jürgen Kappler  
          13.
          Mapping of general web content text or fields to editable fragment areas Technical Task Closed Pablo Molina  
          14.
          Update localized editables to fit design colors Technical Task Closed Brian Chan  
          15.
          Update mappeable editables to fit design colors Technical Task Closed Brian Chan  
          16.
          Move "Display Pages" to a tab along with "Pages" and "Page Templates" Technical Task Closed Brian Chan  
          17.
          FragmentsEditor's Available, Added and Mapping tabs are not correctly ordered Technical Task Closed Brian Chan  
          18.
          Sort Contextual Sidebar tabs properly Technical Task Closed Pablo Molina  
          19.
          Render structure fields in the display page Technical Task Closed Eudaldo Alonso  
          20.
          Make AlloyEditor appear only on user selection Technical Task Closed Brian Chan  
          21.
          Let user choose if want to map or edit an editable field on click Technical Task Closed Brian Chan  
          22.
          Introduce the concept of types for asset fields Technical Task Closed Brian Chan  

            Activity

              People

              • Votes:
                0 Vote for this issue
                Watchers:
                0 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Packages

                  Version Package
                  7.1.X
                  Master