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

As a site admin I can use the page hierarchy for the navigation of a site, so that I don't have to create navigation menus for cases where they are not really needed

    Details

      Description

      Context

      Liferay 7.1 introduced the concept of navigation menus, which are decoupled from the page hierarchy, in order to support advanced navigation use cases, common specially in public websites. However this has caused some undesired complexity for other scenarios where just managing pages and use their hierarchy directly for navigation is enough. 

      Proposed solution

      The proposed solution is to offer the best of both worlds by enabling back the ability for a page hierarchy to be used directly for site navigation. The following improvements will need to be made to make it possible:

      • Add back the ability to move a page in the hierarchy (i.e. changing the parent page) 
      • Add back the ability to reorder sibling pages
      • Allow selecting the page hierarchy when displaying a menu (from the Navigation Menu widget). If the site has both public pages and private pages, it should be possible to select either of them as the menu.
      • Add back the "hidden" checkbox when editing a page to allow specifying whether a page should be shown in the "Page Hierarchy Menu" or not.
        • If possible, make the text the reverse, to be positive. So instead of "Hidden" make it "Show in Pages Hierarchy Menu"
        • If there are public and private pages, then the text should be "Show in Public Pages Hierarchy Menu" and "Show in Private Pages Hierarchy Menu" respectively
      • It is no longer necessary to automatically create a navigation menu from the page hierarchy the first page an admin goes to "Navigation Menus" administration.
      • When adding a page, the checkbox to select a menu to automatically add the page to should not be displayed if there isn't any menu marked as "Add pages to this menu by default". If there is, the checkbox should be unchecked by default. Ideally, if there are several menus, each of them should have their own checkbox.

      After these changes, navigation menus are still available, but are not necessary. They can be used when multiple navigation menus are desired, when there is a need to mix public and private pages, etc.

        Attachments

          Issue Links

          1.
          Don't create default navigation menus LPS-85619 Technical Task Closed Brian Chan  
          2.
          Allow show hidden pages in the page hierarchy menu LPS-85701 Technical Task Closed Brian Chan  
          3.
          Allow to select individual menus to add new page automatically LPS-85711 Technical Task Closed Pavel Savinov (Inactive)  
          4.
          [UX] Analyze UX of Miller Columns and define how drag & drop through the hierarchy should work LPS-85728 Technical Task Closed Jorge Ferrer (Inactive)  
          5.
          Allow to reorder sibling pages with drag and drop LPS-85729 Technical Task Closed Brian Chan  
          6.
          Allow to move a page in the hierarchy by drag and drop LPS-85730 Technical Task Closed Brian Chan  
          7.
          Allow selecting the page hierarchy when displaying a menu LPS-85784 Technical Task Closed Brian Chan  
          8.
          Modify Miller Columns styles to fit new UX prototype LPS-85920 Technical Task Closed Brian Chan  
          9.
          Refresh path when the user stops a second on an item while dragging LPS-86008 Technical Task Closed Brian Chan  
          10.
          Adds plus button when we have selected pages hierarchy LPS-86060 Technical Task Closed Brian Chan  
          11.
          Allow moving active items inside other items LPS-86159 Technical Task Closed Brian Chan  
          12.
          Fix horizontal scroll problems with drag and drop LPS-86239 Technical Task Closed Brian Chan  
          13.
          Reorganize drag and drop code LPS-86601 Technical Task Closed Brian Chan  
          14.
          Re-enable pages of type page set LPS-87158 Technical Task Closed Brian Chan  
          15.
          Manual testing LPS-87132 Technical Testing Closed Kyle Miho  
          16.
          Automation Testing LPS-87134 Technical Testing Closed Brian Chiu (Inactive)  
          17.
          Minor adjustments to fit UX prototype LPS-87315 Technical Task Closed Brian Chan  
          18.
          Document the changes LPS-87279 Technical Documentation Closed Stephen Kostas (Inactive)  

            Activity

              People

              Assignee:
              marta.elicegui Marta Elicegui
              Reporter:
              jorge.ferrer Jorge Ferrer (Inactive)
              Recent user:
              Kiyoshi Lee
              Participants of an Issue:
              Votes:
              1 Vote for this issue
              Watchers:
              8 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:

                  Packages

                  Version Package
                  Master