Open JKoelman opened 5 years ago
Why do we need separate non-responsive views? I would advocate make all responsive first.
that's probably better, but as there are several options (responsive/non-responsive/alternative) it can be usefull to provide an option to choose... ah well not needed for now.
It can be useful... But I don't see the use-case? Why should I need two completely different views of the same component? It requires to include everything everything twice on a page, e.g. doubled css. And there may be some complications with doubled js and same function names.
Just an idea,
but is it something to add an option in the front (option for menu-item) where you as admin can define if a menu-item view needs to be responsive? Something like
Responsive?
pass that setting to the params and catch it in the front.