Starting in Tiki7, there is a dedicated menu module.
You can use it in a wiki page with this syntax:

{module module="menu" structureId=1}

where structureId is the ID of the structure. You can find the id of the node (or subnode) of the structure that you want to start the menu with, when you visit the page to edit a structure. Each page of the structure has a page_ref_id number associated with it. This is the ID that you can place in the param structureId of the module.

{menu id=43 css=y type=horiz toLevel=0}

## Example based on Structure (sub)tree

Imagine that we have this structure defined in our Tiki:

Introduction
Methodology
Design of Experiment
Wet Lab work
Data processing work
Statistics work
Results
Discussion
Bibliography

Those pages, once created the structure, will receive and Id number (page_ref_id param).

Click to expand

The homepage of the structure has page_ref_id=6. If we added that number to the module menu Structure Id param, the full structure tree would be used for the menu. If we use another page_ref_id, from a subtree of the structure (like page_ref_id=8, for the subsections of "Methodology"), then that subtree would be used to create the menu.

Click to expand

Click to expand

If we add new pages to that structure subtree, they would show up automatically as links in the menu also.

1. Use the module menu in the "top" section with the following parameters:
• id= (put the ID of the menu you want there)
• type=horiz
• css=y
• nobox=y

1. Use the module menu in the "topbar" section with the following parameters:
• id= (put the ID of the menu you want there)
• type=horiz
• css=y
• nobox=y

### Using CSS option (instead of bootstrap) so the sub-level menu open where there is room.

If you use a CSS menu instead of the default bootstrap in the footer (for example, a horizontal one there when there's no left column on the page), then the dropdowns will slide upward to stay in view.

1. Sample using a module menu in the "bottom" section with thre following parameters:
• id= (put the ID of the menu you want there)
• type=horiz
• bootstrap=n
• css=y

### Bottom menu sub-level that dropup (slide up) and instead of dropdown (slide down)

On admin-modules, under the menu or for other dropdown-containing module's you can go to "Appearance" tab, add "dropup" for the "custom class" option.

## Comparison with other modules

What is better with the "module menu" compared to the "module wikistructuremenu", is that the "module menu" you can use for horizontal and vertical menus, whilst the "module wikistructuremenu" works only vertically.

## Example

The main horizontal navigation menu in the top bar, that you can see aswell on the one column HomePage, is a "module menu" with a "standardly assigned menuId".
Each of the topnavigation items link to a wikistructure startpage, each assigned to an appropriate category.

There is a second horizontal menu - not in the topbar, but in the pagetop.
This is the same menu than lefthandside, so it is a wikistructuremenu - but this one is made with the "module menu" (instead of the lefthand ones, which are said to be "modules wikistructuremenu").
So you see that a wikistructure menu works with the "module menu" aswell.

If the menu should be restructured - mostlikely the new pages autoposition in the menu does not fit exactly - somebody with permission to admin the structure has to move up and to deprecate or to promote the page in the structure - that is done only with arrows up/down/left/right

In the admin area of the specific structure, you also can add (or delete) pages to this structure and depending of the settings regarding autocategorisation, these added pages also appear in the menu automagically (if a structured page would not be in the structures category, the menu would disappear).

This way, you do not need to give any editor the task and/or permission to edit menus.
The moving of pages in the structure is such time-un-consuming, that a few people with permissions on structure administration might be enough and this might not necessarily a permission for all editors.

See these pages for information that applies for all modules:

### Keywords

Keywords serve as "hubs" for navigation within the Tiki documentation. They correspond to development keywords (bug reports and feature requests):

Accessibility (WAI and 508)
Accounting
Articles and Submissions
Banners
Batch
BigBlueButton audio/video/chat/screensharing
Blog
Bookmark
Browser Compatibility
Calendar
Category
Chat
Clean URLs
Communication Center
Compression (gzip)
Content Templates
Contribution
Credit
Date and Time
Debugger Console
Documentation link from Tiki to doc.tiki.org (Help System)
Docs
Draw
Dynamic Content
Dynamic Variable
External Authentication
FAQ
File Gallery
Forum
Friendship Network (Community)
Groups
Hotword
HTML Page
i18n (Multilingual, l10n, Babelfish)
Image Gallery
Import-Export
Install
Integrator
Interoperability
Inter-User Messages
InterTiki
Kaltura video management
Karma
Live Support
Logs (system & action)
Look and Feel
Lost edit protection
Mail-in
Map with Mapserver
Meta Tags
Mobile Tiki and Voice Tiki
Mods
Module
MultiTiki
MyTiki
Payment
Permissions
Platform independence (Linux-Apache, Windows/IIS, Mac, BSD)
Polls
Profiles
Profile Manager
Report
Toolbar
Quiz
Rating
Feeds
Score
Search engine optimization
Search
Search and Replace
Security
Share
Shopping cart
Shoutbox
Slideshow
Smiley
Social Networks
Spam protection (Anti-bot CATPCHA)
Spellcheck
Stats
Surveys
Tags
Tell a Friend, alert + Social Bookmarking
TikiTests
Theme CSS & Smarty
Trackers
Transitions
TRIM
User Administration including registration and banning
User Files
Watch
WebDAV
Webmail
Web Services
Wiki History, page rename, etc
Wiki Plugin extends basic syntax
Wiki Syntax
Wiki structure (book and table of content)
Workspace
WSOD
WYSIWYCA
WYSIWYG
XMLRPC