PHPackages                             dewsign/nova-navigation - PHPackages - PHPackages  [Skip to content](#main-content)[PHPackages](/)[Directory](/)[Categories](/categories)[Trending](/trending)[Leaderboard](/leaderboard)[Changelog](/changelog)[Analyze](/analyze)[Collections](/collections)[Log in](/login)[Sign up](/register)

1. [Directory](/)
2. /
3. [Utility & Helpers](/categories/utility)
4. /
5. dewsign/nova-navigation

ActivePackage[Utility & Helpers](/categories/utility)

dewsign/nova-navigation
=======================

Navigation/Menu manager for Laravel Nova

v1.2.2(6y ago)15042MITPHPPHP >=7.0.0CI failing

Since Oct 17Pushed 6y ago3 watchersCompare

[ Source](https://github.com/dewsign/nova-navigation)[ Packagist](https://packagist.org/packages/dewsign/nova-navigation)[ RSS](/packages/dewsign-nova-navigation/feed)WikiDiscussions master Synced 2d ago

READMEChangelog (2)Dependencies (9)Versions (18)Used By (0)

Navigation/Menu manager for Laravel Nova
========================================

[](#navigationmenu-manager-for-laravel-nova)

Installation
------------

[](#installation)

`composer require dewsign/nova-navigation`

`php artisan migrate`

Usage
-----

[](#usage)

To get started, you will need to create your first Navigation area. E.g. Header or Footer navigation. You are free to structure the files as you wish or you can use the conventions from the examples if you prefer.

We simply use the default Nova folder to register our new navigation as it will load automatically.

```
// app/Nova/HeaderNavigation.php

namespace App\Nova;

use Dewsign\NovaNavigation\Nova\Navigation;

class HeaderNavigation extends Navigation
{
    public static $zone = 'header';

    public static function label()
    {
        return __('Header Links');
    }
}
```

The `$zone` is used to differentiate the various navigation areas in the database and code and avoids requiring new tables for each new navigation area.

Your new navigation zone will now be available within Nova, with the default custom link item as the only option.

Outputting the navigation (Blade)
---------------------------------

[](#outputting-the-navigation-blade)

### Navigation Blade Directive

[](#navigation-blade-directive)

A blade directive is included to render navigation zones primarily through views. A default unordered list view is included and can be published from the package.

Inside your blade view template or layout ...

```
@novaNavigation('my-zone')
```

This will render all navigation items recursively using the default view. To create a custom view you can make a new blade view in `resources/views/vendor/nova-navigation/zone//my-zone.blade.php`.

You can use the default view as a template.

```

    @foreach ($items as $item)

            {!! $item->view !!}
            @if ($item->navigations->count())
                @novaNavigation($zone, $item->navigations)
            @endif

    @endforeach

```

You will notice that it renders the same view for each level of navigation nested within the parent item. If you don't want this you will need to manually loop through the child items. You can access any sub-items through the `navigations` relationship.

```
@foreach($navigationItem->navigations as $item)
    {!! $item->view !!}
@endforeach
```

The `view` property renders the assigned blade view for the navigation item type. The default custom item view can be published and modified through the vendor views `resources/views/vendor/nova-navigation/custom.blade.php`

If you don't want to render the navigation item's default view, you can manually build an inline view and use the `label` and `action` properties.

```
{{ $navigationItem->label }}
```

Link Types
----------

[](#link-types)

The packages attempts to determine the type of link entered and returns this on the item through the `linkType` attribute. You can access this within the `view` using `$item->linkType`. This can be useful for adding icons to links for example.

TypeDescriptionmailtoAn email linktelA telephone linkdownloadA link pointing to a download. You can customise the file extensions which are treated as downloads in the config.externalA link pointing off-siteinternalA link pointing to a URL within your siteExtending
---------

[](#extending)

You can create your own navigation item types by creating a couple of new files and loading them in. This is useful for making your content types available as selectable navigation items instead of manually typing in custom URLs. As an example, if you have a Blog and want the user to be able to select an article or category to link to.

You will need:

- An Eloquent Model, complete with migration
- A Nova resource to manage the content
- A blade view to render the item

```
// app/Navigation/Models/Category.php

use Dewsign\NovaNavigation\Models\NavigationItem;

class Section extends NavigationItem
{
    public static $viewTemplate = 'nova-navigation::category';

    public function category()
    {
        // BlogCategoryModel is used as an example. Include your actual blog category model.
        return $this->belongsTo(BlogCategoryModel::class);
    }

    // Return the url for this navigation item
    public function resolveAction()
    {
        return route('blog.category', $this->category);
    }

    // Return the label to display in the navigation
    public function resolveLabel($category = null)
    {
        // Automatically use the category title as navigation label
        return $category->title;
    }
}
```

```
// database/migrations/your_migration.php

Schema::create('nav_categories', function (Blueprint $table) {
    $table->increments('id');
    $table->integer('category_id')->nullable();
    $table->timestamps();
});
```

```
// app/Navigation/Nova/Category.php

...
use Dewsign\NovaNavigation\Nova\Items\NavigationItem;

class Section extends NavigationItem
{
    // The model we just created
    public static $model = App\Navigation\Models\Category::class;

    public static function label()
    {
        return __('Category');
    }

    public function fields(Request $request)
    {
        return [
            // BlogCategoryResource is used as an example. Include your actual blog category nova resource.
            BelongsTo::make('Category', 'category', BlogCategoryResource::class)->searchable(),
        ];
    }
}
```

Next you need to tell the system how you want to render the category navigation item. Create a new view at the location specified in the Model (in this example `resources/views/vendor/nova-navigation/category.blade.php`). Or you can set the view in the model to the default `nova-navigation::custom` if you simply want to render the same layout for all navigation items.

```
{{ $model->label }}
```

`$model` references the Category Model we created. To access the actual blog category you can refer to the relationship `$model->category` if you wanted to include additional details in your view. E.g.

```

    {{ $model->label }} ({{ $model->category->articles()->count() }})

```

Finally, load the new navigation item through the `novanavigation` config

```
return [
    "repeaters" => [
        \App\Navigation\Nova\Category::class,
    ],
    "replaceRepeaters" => false,
];
```

User can now add a `Category` navigation item and select an existing category to link to. The benefit is that when the category changes, the navigation item also reflects these.

Hyperlinks Repeater Blocks
--------------------------

[](#hyperlinks-repeater-blocks)

If you are using [Nova Repeater Blocks](https://github.com/dewsign/nova-repeater-blocks) to build out your content, you may want to include a repeater block which acts like a navigation zone to add inline links. Add the included `NrbHyperlinks` for your repeater blocks.

```
    // config/repeater-blocks
    ...
    "repeaters" => [
        ...
        Dewsign\NovaNavigation\Nova\NrbHyperlinks::class,
    ],
```

This will render each navigation item using their respective views. The wrapper for each item can be customised by creating new templates in the `views/vendor/nova-navigation/hyperlinks` directory. You can publish and modify the default if required.

###  Health Score

31

—

LowBetter than 68% of packages

Maintenance20

Infrequent updates — may be unmaintained

Popularity16

Limited adoption so far

Community12

Small or concentrated contributor base

Maturity65

Established project with proven stability

 Bus Factor1

Top contributor holds 89.7% of commits — single point of failure

How is this calculated?**Maintenance (25%)** — Last commit recency, latest release date, and issue-to-star ratio. Uses a 2-year decay window.

**Popularity (30%)** — Total and monthly downloads, GitHub stars, and forks. Logarithmic scaling prevents top-heavy scores.

**Community (15%)** — Contributors, dependents, forks, watchers, and maintainers. Measures real ecosystem engagement.

**Maturity (30%)** — Project age, version count, PHP version support, and release stability.

###  Release Activity

Cadence

Every ~43 days

Recently: every ~60 days

Total

12

Last Release

2288d ago

Major Versions

v0.2.1 → v1.0.02019-06-11

### Community

Maintainers

![](https://www.gravatar.com/avatar/767ab4e0eedaace1862603a74f2c37f2ef7f72811855d4748a3b8d02f3ad81df?d=identicon)[dewsign](/maintainers/dewsign)

---

Top Contributors

[![m2de](https://avatars.githubusercontent.com/u/17720020?v=4)](https://github.com/m2de "m2de (35 commits)")[![crumb1e](https://avatars.githubusercontent.com/u/18497168?v=4)](https://github.com/crumb1e "crumb1e (4 commits)")

###  Code Quality

Code StylePHP\_CodeSniffer

### Embed Badge

![Health badge](/badges/dewsign-nova-navigation/health.svg)

```
[![Health](https://phpackages.com/badges/dewsign-nova-navigation/health.svg)](https://phpackages.com/packages/dewsign-nova-navigation)
```

###  Alternatives

[wireui/wireui

TallStack components

1.8k1.3M16](/packages/wireui-wireui)[livewire/volt

An elegantly crafted functional API for Laravel Livewire.

4195.3M84](/packages/livewire-volt)[ramonrietdijk/livewire-tables

Dynamic tables for models with Laravel Livewire

21147.4k](/packages/ramonrietdijk-livewire-tables)

PHPackages © 2026

[Directory](/)[Categories](/categories)[Trending](/trending)[Changelog](/changelog)[Analyze](/analyze)