Personally for simple projects i go with bootstrap DIY mode.

But for more serious work i just get a good HTML template and do it semi-DIY

So laravel-menu already have a pull request with L5 support waiting to be merged: https://github.com/lavary/laravel-menu/pull/54

I've merged that pull request and a composer.json fix requiring the needed package (illuminate/html) in https://github.com/sdbruder/laravel-menu.

This is temporary, when lavary/laravel-menu solves it I will drop it, no need to maintain my fork after that.

So as Im not publishing it as a separate forked package if you want to use it include my repo in composer.json first and then composer require lavary/laravel-menu away.

There is also this package.

https://github.com/caffeinated/menus

Please forgive my noobishness - but when you say bootstrap DIY, i assume you mean just using the OL/UL classes found in bootstrap CSS? Side note: having a good menu system would be pretty sweet to have.

sdbruder said:

So laravel-menu already have a pull request with L5 support waiting to be merged: https://github.com/lavary/laravel-menu/pull/54

sdbruder said:

I've merged that pull request and a composer.json fix requiring the needed package (illuminate/html) in https://github.com/sdbruder/laravel-menu.

Are you able to affect laravel-menu's behaviour with the config-files using your fork? Because the PR you're using in your fork apparently doesn't register the config-options properly. I wasn't able to tell laravel-menu to append the active-class to the item (li-tag), rather than the link (anchor-tag) for instance.