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

Last change on this file since 1158 was 1158, checked in by piv, 15 years ago

add more description to this product

  • Property svn:eol-style set to native
File size: 1.8 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 much more 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 on portal
19content structure.
20
21It also allows you to define if to put content tabs before or after action tabs,
22and a bit more... For details see below.
23
24
25Requires
26--------
27
28  Plone 3.0+
29
30
31Install
32-------
33
34  * first follow instructions inside docs/INSTALL.txt document
35
36  * then install product with Quick Installer
37
38
39Migration from qPloneDropDownMenu
40---------------------------------
41
42In case qPloneDropDownMenu product was previously installed in a site
43installation procedure will automatically detect legacy settings and migrate
44it to a newly created tool along with removing old portal_dropdownmenu one.
45
46Also installation procedure will uninstall qPloneDropDownMenu product itself
47(in case it's still installed) and clean up everything after it.
48
49Note: to successfully migrate old tabs it's required to have a valid html
50markup, otherwise migration procedure won't be able to move tabs correctly.
51
Note: See TracBrowser for help on using the repository browser.