Changes between Version 38 and Version 39 of quintagroup.dropdownmenu

Timestamp:

Jun 5, 2013 3:11:46 PM (11 years ago)

Author:

naomin

Comment:

--

quintagroup.dropdownmenu

@@ -7 +7 @@
 Many sites, even responsive ones, stick to the belief that navigation belongs at the top of any given page. This approach can cause usability problems on mobile devices because mobile users are often short of two things: screen space and time. Quintagroup.dropdownmenu package offers a solution by providing mobile-first multilevel navigation menu. It means the product enables device-native interactive interface for navigating through the website in more accessible way. Smart select box takes up minimum space on mobile phones, while tablet users are presented with a glorious multilevel top menu.
 
- [[Image(mobile-navigation.jpeg, nolink)]]
 
 == Links ==
@@ -63 +62 @@
 Activate Plone Drop-Down Menu via Quickinstaller in Plone: Site Setup -> Add-ons. 
 
-== Configuration ==
+== Configuration/Usage ==
 
 After installation in Plone, you'll see '''!DropDown Menu''' item under '''Add-on Configuration''', that include the following setting options:
@@ -69 +68 @@
  [[Image(settings.jpeg, nolink)]]
 
+To enable mobile navigation you need to tick the box for '''Display menu as select for small screens'''
+ 
+ [[Image(mobile-navigation.jpeg, nolink)]]
 
+'''Building you dropdown menu with portal_actions'''
+
+Starting from Plone 3 portal actions introduced CMF Action Category containers, it opened opportunity to build nested actions trees. Though CMF Action Category does not behave as a regular action, it has different set of properties. We introduced convention in quintagroup.dropdownmenu that requires to have a specially named Action for each Actions Category. The id of each such action must be build using the rule:
+
+{{{action_id = prefix + category_id + suffix}}}
+where:
+
+category_id:    is id of correspondent CMF Action Category
+prefix: defined in DropDownMenu configlet, default value ''
+suffix: defined in DropDownMenu configlet, default value '_sub'
+So, the actions structure can look like:
+
+{{{+ portal_tabs
+|- home
+|- blog_sub
+|-+ blog
+| |-- 2009
+| |-- 2010}}}
+By default the root of dropdown menu is 'portal_tabs' category.
+
+