Overview and key concepts¶
Link to pages, custom URLs, or a combination of both¶
The custom URL field won’t force you to enter a valid URL, so you can add things like #request-callback
or #signup
to link to areas on the active page (perhaps as JS modals).
You can also define additional values to be added to a page’s URL, letting you jump to a specific anchor point on a page, or include fixed GET parameters for analytics or to trigger custom functionality.
Suitable for single-site or multi-site projects¶
While main menus always have to be defined for each site, for flat menus, you can support multiple sites using any of the following approaches:
Define a new menu for each site
Define a menu for your default site and reuse it for the others
Create new menus for some sites, but use the default site’s menu for others
You can even use different approaches for different flat menus in the same project. If you’d like to learn more, take a look at the fall_back_to_default_site_menus
option in Supported arguments
A copy feature is also available from the flat menu management interface, allowing you to quickly and easily copy existing menus from one site to another.
In a multi-site project, you can also configure wagtailmenus to use separate sets of templates for each site for rendering (See Using preferred paths and names for your templates)