Board Thread:General Discussion/@comment-27105226-20151121093800

Some change recommendations/brainstorming:

Considering how many different browsers are out there & the ever-changing compatibility of those browsers. I think the best option for catering to mobile users is simply serving the same content in different containers. After looking through several large Wikias it just seems excessively messy to try to write extensive templates, CSS, and java to accomplish simple tasks. It also makes editing page content very unfriendly. So here's my current thoughts: That being said, here's my current solution for reducing screen area used by Servant Stages (Not ready to implement, untested):
 * CSS could have multiple classes which restrict displayed content based on screen size.
 * Templates could be modified (where needed) to show content in different ways.
 * Java just flat out shouldn't be used to modify most display content, even though that seems like a Wikia standard on the large sites... Plus the "verification" process takes time.
 * Extensions are a nice option, but in my opinion it's just better to avoid them. Too many things can go wrong lol.
 * Leaving out Java, Extensions, & extensive CSS rewrites allows all Templates to be reverse compatible. Content appearance can then easily be changed with a simple template modification.

CSS @media only screen and (max-width: 600px) { .NotMobile { display:none; } } @media only screen and (min-width: 601px) { .OnlyMobile { display:none; } }
 * Class "NotMobile" will hide that content on mobile devices but show it on non-mobile.
 * Class "OnlyMobile" will hide that content on non-mobile devices but show it on mobile.

Template:Characters |- style="text-align:center;"
 * With the above CSS, this would show our normal tabber on Desktop, while showing a Gallery on mobile.
 * colspan="2" |



So... Thoughts, opinions, ideas, criticisms, etc.? Keep in mind that we shouldn't restrict content available to mobile, only optimize the way that content is displayed. 