library menu-builder {🖫 5,384, ⚐ 13, ★ 5}

toxic-lemurs/menu-builder

A simple database driven menu manager for Laravel 5

Sunday, March 18, 2018
by ToxicLemurs
Repository
1 Watchers
5 Stars
5,384 Installations

PHP
0 Dependents
0 Suggesters
3 Forks
0 Open issues
13 Versions
15 % Grown

The README.md

This package allows you to create tree based menu structures that are database driven (Eloquent) and renders HTML based on fully customizable templates and views. There is no limit the nesting level but the amount of levels will need to be handled in your views / templates., _(*1)

Installation:

Require this package in your composer.json and update composer. This will download the package and all the dependencies:, _(*2)

"toxic-lemurs/menu-builder": "2.*"

Alternatively you can require this through composer via the command line:, _(*3)

$ composer require toxic-lemurs/menu-builder

Laravel Package Auto Discovery:

The Menu-Builder package supports Package Auto Discovery. If you don't want to use package auto discovery you can add the provider in your config/app.php in the providers array:, _(*4)

ToxicLemurs\MenuBuilder\MenuBuilderServiceProvider::class,

Optionally you can make use of the Facade by adding the facade in the aliases array:, _(*5)

'MenuBuilder' => ToxicLemurs\MenuBuilder\Facades\MenuBuilder::class,

Publish migrations and assets:

Publish the Menu Builder migrations:, _(*6)

$ php artisan vendor:publish --provider="ToxicLemurs\MenuBuilder\MenuBuilderServiceProvider" --tag=migrations
$ php artisan migrate

You can optionally publish the views so you can easily override them with your site's styling and layout:, _(*7)

$ php artisan vendor:publish --provider="ToxicLemurs\MenuBuilder\MenuBuilderServiceProvider" --tag=views

Publish the config to tie and modify the default administration routes to your project:, _(*8)

$ php artisan vendor:publish --provider="ToxicLemurs\MenuBuilder\MenuBuilderServiceProvider" --tag=config

Getting started:

In your views / templates you can use the Facade to render your menu:, _(*9)

{!! MenuBuilder::render('Group Name') !!}

Alternatively if you do not want to use the Alias:, _(*10)

{!! ToxicLemurs\MenuBuilder\Facades\MenuBuilder::render('Group Name') !!}

Default routes have been setup for managing the menu:, _(*11)

/menu - Manages your actual menu items that gets attached to menu groups
/group - Setup menu groups to easily group your different menus

You can override the default routes with your own custom routes (The package routes are currently defined individually and not as resources to allow for override flexibility):, _(*12)

Route::get('my/route/menu', ['uses' => '\ToxicLemurs\MenuBuilder\Http\Controllers\MenuController@index', 'as' => 'menu.index'])

Overriding the views:

You can override the default implementation of how the menu gets rendered by modifying your published views:, _(*13)

views/menu/default.blade.php - This is the master template for binding the menu partials
views/menu/partials/list.blade.php - This is the partial that creates the list items / html for the menu

Alternatively you can specify custom templates to use for your base templates on a per menu level:, _(*14)

{!! MenuBuilder::render('Group Name', $options = [
    'templates' => [
        // The container file overrides the views/menu/default.blade.php template
        'container' => 'foo.bar', // resources/views/foo/bar.blade.php

        // The builder file overrides the views/menu/partials/list.blade.php
        'builder' => 'bar.foo', // resource/views/bar/foo.blade.php
    ]
]) !!}

You can look inside the example folder for an implementation of the Menu Builder by copying the vendor folder into your resources folder. Make sure your database contains menu items. Example source can be found here., _(*15)