That would mean storing the template on a "page profile", for which we
could make default fallback assumptions (similar to the language
fallbacks for instance), depending on deviceatlas-defined "device
classes" (tablet, phone, desktop,...)?
It would obviously make database queries more costy, and will not help
solve the human ressource problem that front-enders will have to make
several sets of templates instead of only one... but that's another
story.
Also, we now need plenty more menus (we currently cache one menu per
language per site, it will need to be one menu per language per site
per "device class")
Does that make any sense?
- Trib'