[16:41:11] <xover>	 Any guidance and best practices for good /Main_Page design anywhere?
[16:46:35] <xover>	 I'm fiddling with it to address the changes from T32405 and running into some… challenges.
[16:46:35] <stashbot>	 T32405: [EPIC] MobileFrontend extension should stop special-casing main page - https://phabricator.wikimedia.org/T32405
[17:08:18] <xover>	 For instance, I'm wondering whether .skin-minerva is reasonable to rely on to determine if the user visiting through the .m. proxy.
[17:09:38] <xover>	 (In which case I want to serve them the mobile styles even if their device has a desktop-sized display)
[17:11:22] <xover>	 Isn't there a skin-independent class I could select for for this, in case the mobile skin gets swapped out eventually?
[17:16:05] <xover>	 Hmm. Or maybe another way to put it, if you're visiting through .m. you should always get the mobile view regardless of the properties of your device, which media queries can't achieve.
[17:17:46] <xover>	 But users not coming in though .m. should get the appropriate view for their device regardless of whether they're using Vector or Minerva.
[17:18:07] <xover>	 *through .m.
[17:20:24] <xover>	 An .onmobile class that's the opposite number for .nomobile, or some such.