Thoughts on best practices for a View
I am just looking for some advice/ideas here.
My application has multiple different settings such as finance settings, Account settings etc. Each Set of settings is a different resource.
I am trying to think of a way to consolidate them to make it easy for user navigation.
It would be perfect i think to have a secondary menu so
Settings
--Finance Settings
--Status Settings
etc. but that looks messy on the main nav- it would be better to have a settings menu under the user menu, but it doesnt support nested menus.
My next thought would be have the Settings on the User Menu link, and have a secondary sidebar on the page, but i cant think of an easy way to do this except make every resource a custom page and add a livewire component to it for the links to the seperate menu items - seems clunky!
The last idea i had was to use tabs, but i cant figure a way to load views into tabs for different resources!
Any thoughts, ideas, suggestions greatly appreciated!!!
My application has multiple different settings such as finance settings, Account settings etc. Each Set of settings is a different resource.
I am trying to think of a way to consolidate them to make it easy for user navigation.
It would be perfect i think to have a secondary menu so
Settings
--Finance Settings
--Status Settings
etc. but that looks messy on the main nav- it would be better to have a settings menu under the user menu, but it doesnt support nested menus.
My next thought would be have the Settings on the User Menu link, and have a secondary sidebar on the page, but i cant think of an easy way to do this except make every resource a custom page and add a livewire component to it for the links to the seperate menu items - seems clunky!
The last idea i had was to use tabs, but i cant figure a way to load views into tabs for different resources!
Any thoughts, ideas, suggestions greatly appreciated!!!
