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

As a site administrator I can create a custom master that can be used as the foundation to create site pages

    Details

    • Sprint:
      S01E01 - Fruittis Volcano, S01E02 - Giants Enigma, S01E03 - Floating Bottle

      Description

      Context

      LPS-102202 introduces the concept of Master Pages which can have common elements across several fragment based pages.

      The goal of this Story is to add support for custom master pages for a site. A master can be created using the same tool as other Page Templates, using layouts and fragments. In addition to that, each master must have one and only one special "fragment" which specified the area where creators of pages based on this master will be able to place the page-specific fragments (Some potential names for this special fragment are: "Drop Zone", "Page Fragments Zone", ...).

      It must be possible to keep a Master in draft mode when it's first created and when a later update is done, until all desired changes are made. Whenever changes are made and published, they must be propagated to all pages based on the master.

      Configuration & Look and feel 

      When editing the "Look and feel" of a Master only the following options must be shown:

      • Theme
      • JavaScript: This would be added in addition to what each specific page may provide.

      In other words, the following sections are not shown:

      • Master
      • Mobile device rules

      Also, when editing a page with a master other blank, the page editor should not be able to change the Theme (since it should use the one chosen in the master).

      Master pages should not provide access to the configuration (General, SEO) at this point. Later on we can reconsider whether it would make sense to support some SEO options that could be automatically applied to all pages with the master.

      Acceptance Criteria

      • Given a custom master has been created in a site 
      • When a user tries to create a new page
      • Then the custom master must be offered as an option to create the page and when the page is created the common elements must be part of the page
         
      • Given a page created with a custom master as its base
      • When the page is edited
      • Then the fragments from the master cannot be changed in any way and fragments can only be added to the area identified as the "Drop Zone" by the master creator
         
      • Given a valid master
      • When the creator publishes it
      • Then the changes must be propagated to all pages, page templates and display pages based on the master 
      • Given a master which does not have any "Drop Zone"
      • When the creator tries to publish it
      • Then the system must warn that adding a "Drop Zone" is mandatory
      • Given a master 
      • When the creator edits it and clicks the configuration icon at the top right
      • Then only the settings that make sense for a Master are shown

        Attachments

        1.
        Render the master page when editing a Page Technical Task Closed Brian Chan  
        2.
        Product QA | Test Scenarios/Cases Creation Technical Testing Closed Manoel Cyreno  
        3.
        Adds new methods to creates pages with a master page Technical Task Closed Brian Chan  
        4.
        Adds actions to admin portlet for master pages (add, delete, rename, ...) Technical Task Closed Brian Chan  
        5.
        Adds new fragments for drop zone Technical Task Closed Brian Chan  
        6.
        Mark a row or a column as drop zone Technical Task Closed Brian Chan  
        7.
        Cleanup not needed variables in soy files Technical Task Closed Brian Chan  
        8.
        Allow only one drop zone per page and only allow publishing when one drop zone is present Technical Task Closed Brian Chan  
        9.
        Render master page when viewing a Page Technical Task Closed Brian Chan  
        10.
        Rename masterLayoutPageTemplateEntryId to masterLayoutPlid Technical Task Closed Eudaldo Alonso  
        11.
        Hide and show options of configuration depending on we are on a master page or we are on a content page Technical Task Closed Brian Chan  
        12.
        Product QA | Test Validation - Round 1 Technical Testing Open Support QA  
        13.
        Style drop zone to fit design Technical Task Closed Brian Chan  
        14.
        Hide portlets controls on master page widgets when displaying in a content page Technical Task Closed Brian Chan  
        15.
        Apply master pages to page templates Technical Task Closed Brian Chan  
        16.
        Uses theme options for master pages on pages Technical Task Open Eudaldo Alonso  
        17.
        After adding a drop zone you cannot add more fragments to the master page Technical Task Closed Brian Chan  
        18.
        Apply master pages to display pages Technical Task Closed Brian Chan  
        19.
        Change master page editable values language when changing language in the Translation selector Technical Task Closed Brian Chan  
        20.
        Master pages should start with a drop zone added to the page Technical Task Closed Brian Chan  

          Activity

            People

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

              Dates

              • Created:
                Updated:

                Packages

                Version Package