Hi, there! I'm Isaac, from FANDOM's Community Technical staff. My job on FANDOM largely involves helping communities so that they're presented in the best way to your complete audience. In the process of other discussions, I made some other discoveries about some of your articles and the ways that they appear on mobile devices. ESB has a sizable mobile audience, and they need to be able to see all of your great content accessibly. For our purposes, that means the entire article must display reasonably and readably in Mercury, our mobile skin. For some of your articles, that's not happening.
Some of your articles — namely character articles that use CTab — appear like SpongeBob here. They don't show the full article.
This screenshot is so big, it can't be uploaded. It is too big to embed, but represents the 11MB download to get to the bottom of the Eugene H. Krabs page. It has 366 images, and the screenshot itself still doesn't reach the bottom.
Neither of these experience works for a mobile audience that wants to see your hard work and content. Whether you use Mercury yourself or not, there are truly hundreds of thousands of unique visitors that use the mobile skin every month.
So, here are two things that can be done to address these issues:
- Moving the navigation functions of CTab to somewhere mobile-accessible that is not at the bottom of a long string of images. This ensures everyone can get to all the articles.
- Moving the nested tabbers of "Design" that are currently in some infoboxes to somewhere else on the page (or to the gallery pages you already have set up). From there, they can either be made with a single layer of tabbers or (more preferably, as this is more bandwidth efficient) a
<gallery>. If these images remain inside the infoboxes, they must be inside<gallery>tags, as tabbers will not be supported in Mercury.
We appreciate the hard work that has gone into these, which is why we'd like to see these moved and reorganized rather than deleted. We hope that you can produce an organization scheme (in a single layer) that really surfaces these images well, wherever they are moved to.
Those issues (navigation with no content hiding, nested tabbers in the infobox) must be resolved. If your community chooses to make the effort, please do so by 2017-09-15. Otherwise, FANDOM will need to intervene directly and make the changes needed in a manner we feel is best. Not resolving these issues hurts your community significantly, and blocking parts of the articles to force desktop views is not an acceptable compromise.
I'm available for comments and consults on these and other portability issues, and am happy to answer any specific questions you have. Hopefully we can get your community out there to an even greater audience quickly and effectively!
