plank/frontdesk

Build dynamic navigation bars for your Laravel application

frontdesk's Issues

Menuable should have a custom Pivot

Description

It could be useful to define a pivot model for the menuable table to allow easy traversal between linkables and menus

Potential Enhancement:

What if we renamed this to navs (or something else) and made it a custom morph pivot like Nav, so you can at least go backward from a menu to the things that reference it.

Ie: $menu->navs->first()->menuable

Otherwise you get forced into knowing in advance the Content types it links to in order to do something like $menu->pages.

If Menu instances dont need to be linked to multiple pieces of Menuable content/objects, then we could always just put the menuable morphs on the menus table.

Originally posted by @kfriars in #2 (comment)

Navigation model must be implemented

Description

A Model must be implemented that allows for navigations items to be created. These navigation items will allow a user to either create arbitraty links to external resources / websites, or to link to some internal resource, like a specific model or route.

This means the model must support:

• Polymorphic relations to any "Navigatable" model (ie: a set of morph columns + a trait to easily enable a model as navigateable)
• A Route to pass the related model to when viewing it (as well as a way to supply any other required parameters)
• Arbitrary URLs as destinations. In this case the morph relation is null