source: products/quintagroup.dropdownmenu/trunk/README.txt @ 2539

Last change on this file since 2539 was 1340, checked in by piv, 11 years ago

add note about css tabs levels

  • Property svn:eol-style set to native
File size: 2.1 KB
Line 
1Introduction
2============
3
4This package allows Plone websites display multilevel portal dropdown menu based
5on portal actions settings and site structure.
6
7You may ask why we may need one more dropdown menu product for Plone, having
8already qPloneDropDownMenu, webcouturier.dropdownmenu and other products
9providing similar functionality. While qPloneDropDownMenu product just displays
10manually edited html code with nested unordered list, webcouturier.dropdownmenu
11went further and is trying to display submenus for each standard portal tab be
12it action from portal_actions tool or be it auto generated tab based on content
13structure.
14
15But neither of those products use newly introduced portal_actions tool's
16feature: nested categories. That's why quintagroup.dropdownmenu package was
17introduced. It allows to build multilevel portal dropdown menu based on nested
18portal_actions categories inside portal_tab category as well as based on portal
19content structure.
20
21It also allows you to define whether to put content tabs before or after action
22tabs, and a bit more... For details see below.
23
24
25Notes
26-----
27
28  * you may have actions/content-based tabs as deep as you wish, but then you'll
29    need to tweek default dropdown menu css rules a bit, default css rules show
30    only the first 4 levels of tabs
31
32Requirement
33-----------
34
35  Plone 3.0+
36
37
38Installation
39------------
40
41  * first follow instructions inside docs/INSTALL.txt document
42
43  * then install product with Quick Installer in Plone
44
45
46Migration from qPloneDropDownMenu
47---------------------------------
48
49In case qPloneDropDownMenu product was previously installed, it will
50automatically detect legacy settings, migrate it to a newly created settings
51registry and update portal_actions tool if required along with removing old
52portal_dropdownmenu one.
53
54Also installation procedure will uninstall qPloneDropDownMenu product itself
55(in case it's still installed) and clean up everything after it.
56
57Note: to successfully migrate old tabs it's required to have a valid html
58markup, otherwise migration procedure won't be able to move tabs correctly.
Note: See TracBrowser for help on using the repository browser.