Board Thread:New Features/@comment-24739709-20150518230347/@comment-3328029-20150522143248

Interesting... However, it seems even more restrictive than the lua template! I understand you guys want to make a better mobile experience, but please recall your desktop users as well! :) My main concern is that this doesn't seem to support a 2 column layout even on desktop (you could just make the 2 columns "convert" to the title above on mobile only), and just like the lua template, it seems that I can't define custom classes on specific cells / rows. Also, unlike the lua template, it doesn't seem to even be possible to set a class for the infobox to use (where each cell gets a class based on the infobox's class name). I like the general idea though (since infoboxes are confusing yet common, this could help make it "simpler" for new users), but you need to make it as fluid as possible! Make sure we can use all the normal html atrributes we already can (title="", class="", id="", etc), and consider odd usages!

However, I must support the above questions; what exactly was broken in mobile, and why couldn't it just be fixed by updating how the current infobox system works? The only real difference I seem to see is have a left/right side data cells (which can already be done; and notice how rarely it's done, so not really all that helpful), and the big difference is having the header cells one "row" above the content; this could surely be done automatically?

Also as mentioned above, any infobox that currently breaks on mobile would already be a mess... and odds are those communities either don't care, or don't know about the issue, and as such wouldn't really implement this, and thus this wouldn't actually fix the "mobile" issue (which, again, we all would love to hear specific about).

Anyways, keep up the good work, and please remember not everyone uses mobile (and that not all handheld devices use the mobile skin), and thank you very much for putting this out there in such a community-involved way! It's always appreciated!

Edit: I personally would prefer a "navboxbuilder" more than yet another new way to make infoboxes; navboxes can be very complex, and seem to be ones of the more common annoyances in mobile! It would be great if you made a navbox builder similar to how wikipedia / the layton wikia do it, and then navboxes could use bullet point lists in them right out of the box, which also gives you more control how they would be displayed on mobile. I already use the layton "branch" of the navbox on many of my wikis, but considering how complex the code is (and how limited the default one is), navboxes really need your love more than infoboxes!