Download the PHP package studioespresso/craft-navigate without Composer
On this page you can find all versions of the php package studioespresso/craft-navigate. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download studioespresso/craft-navigate
More information about studioespresso/craft-navigate
Files in studioespresso/craft-navigate
Package craft-navigate
Short Description Navigation plugin for Craft CMS
License proprietary
Informations about the package craft-navigate
Navigate for Craft CMS
Menu's & navigations made easy.

Requirements
This plugin works with Craft CMS 3.x, 4.x and 5.x
Installation
To install the plugin, follow these instructions.
cd /path/to/project
composer require studioespresso/craft-navigate
./craft install/plugin navigate
Templating
craft.navigate.raw
craft.navigate.raw will give you an array of the items you added to the navigation, with children for each if you have those.
For each node you will have access to:
This gives you complete control over the HTML & CSS used to display your navigation.
Here's an example of how to show a navigation and it's possible children using a twig macro:
Headings
Since 2.3.0, headings can be added to make it easier to build larger navigations with mulitple sections or columns. To make full use of this you check check node.type == "heading" and add the html you need in the condition.
These only work on multiple levels (eg: 3 headings on the top level, each with navigation items on deeper levels).
Console commands
Navigate ships console commands for building navigations from the command line — handy for
seeding, scripting, and AI-assisted prototyping. All support --json for machine-readable
output. (Prefix with your environment's runner, e.g. ddev craft … or ./craft ….)
--type accepts url, entry, asset, category or heading. entry/asset/category
require --element-id; url requires --url. Other add options: --site, --parent,
--blank, --classes. Run ./craft help navigate/nodes/add for the full list.
Programmatic API
Navigate also exposes two services for managing navigations and their items in code — useful inside migrations, modules, or a tinker/eval context. (There are no GraphQL mutations; the console commands above are the quickest way to script navigation changes.)
Navigate::$plugin->navigate—NavigateService, manages navigations.Navigate::$plugin->nodes—NodesService, manages nodes (menu items).
Agents working in this repo should also read AGENTS.md.
Creating a navigation
title, handle, allowedSources and enabledSiteGroups are required.
Adding items (nodes)
A node's type is always lowercase: url, element, or heading. Required on every
node: name, navId, siteId, type. save() returns the saved NodeModel (with id)
or false.
Optional node attributes: blank (open in new tab), classes (CSS classes), enabled
(default true), and parent (a parent node id — nest items by setting it; the parent
navigation's levels must be > 1). New nodes get their order assigned automatically.
Node types reference
type |
Extra attributes | Notes |
|---|---|---|
url |
url |
Literal/relative URL; supports env & object tags |
element |
elementType, elementId |
elementType ∈ entry, asset, category |
heading |
— | Non-link label; only meaningful when levels > 1 |
Known issue — always use lowercase types. Node types are stored and rendered in lowercase (
url,element,heading; seeNodesService::parseNode()andNodeModel::active()). The CP "add/edit item" slide-out (NodesController::actionAddSlideOut()/actionEditSlideOut()) compares against capitalized'Url'/'Heading', so those branches don't fire and a node'surl/classesmay not be set through that path. The console commands and service API above use the correct lowercase values — prefer them, and use lowercase if you ever settypeyourself.
Reading in PHP
Configuration
You can create a file called navigate.php in the config directory (you can copy this one to start) to manage these settings in your code. The ones listed here are not available through the CP.
Disabling caching
Out of the box, the plugin will cache the querries it makes when devMode is not enabled.
If you want to disable caching within the plugin entirely, you can do so by setting disableCaching to true in the plugin's configuration file. (see example here)
CSS class option list
Instead of the "Classes" field being a plain text field, you can also change it to a predefined dropdown with class that you want to make available for the user.
The nodeClasses setting takes an array where that contains "Class to be applied" => "Label to be shown in the cp".
``
Make sure to also include an empty option in case you don't want the the first item to be selected by default
Brought to you by Studio Espresso