-
-
Notifications
You must be signed in to change notification settings - Fork 23
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Navigation Menu Fields #201
Labels
Comments
Great idea! |
I'll shelve this for a next major release, but sounds good! |
Whilst I'm happy to keep this open, as a "maybe" and see how much interest there is for it - my main concern will be about performance and extra queries due to the parent navigation being an element. Particularly from the front-end, so I'll need to do some experiments with how much of a trade-off it'll be. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I have repeatedly come across the need to add configurable options to a specific navigation menu as a whole (and not just the individual nodes inside the menu).
I think the most flexible and reliable way to support this would be to turn navigation menu models into elements, which can have their own field layout (a bit like craft's builtin Globalsets do), on top of the nodes' field layout.
This way, developers are free to configure the options and data available for each menu as they please by adding existing craft fields. The fields would appear at the top of the navigation menu's edit screen, where editors can change the data associated to the menu.
Another big win with this approach is that it would come with multi-site/multi-lingual support for the menu's data/options out of the box.
The text was updated successfully, but these errors were encountered: