FANDOM


More and more people are visiting FANDOM on mobile devices every day. To improve the mobile experience for visitors to your communities, FANDOM has created what we are calling Mobile Web. The mobile web is the first thing you'll see once you open a wiki on your mobile device's web browser, and is optimized for effortless and speedy article content browsing. So how can you improve how your wiki looks on mobile?

A few tips

Wikia How To - Making Your Wikia Mobile Friendly04:22

Wikia How To - Making Your Wikia Mobile Friendly

This How To video focuses on how to make your wiki look great on the mobile web.

  • To see how your wiki looks, start by visiting your community with a smartphone. You can also use a shortcut from your desktop by adding ?useskin=mercury to the end of the a page's url. Make sure to narrow the window size to simulate a phone screen. A common screen size is 320 x 480 pixels, so it’s a good idea to to check out your wiki in different sizes. If you are fortunate enough to have a choice between a real smartphone and software emulation, always prefer the genuine article.
  • The most important aspects to consider are whether your community's pages are clear, simple and flexible. If they have a clear hierarchy and a simple layout then your wiki will better adjust to different platforms.
  • What appears at the top of a page is the first place you should focus your attention. Smartphones have a much smaller content space. This means that the first view of your a page will include only what is at the very top of the page.
  • For images, make sure you place an image next to the relevant written content in the editor. Sometimes users move images to another section to better format for desktop display, but on mobile, this means that the images end up getting displayed in the other section, not the one with the relevant content. Remember, as the content size changes, so does the display, so it’s best to keep images with their relevant content. Images that are larger than 30 pixels span the width of the phone screen. This provides a better view of the image and allows for the content to be full width above and below it. If multiple images appear together, or the page includes a gallery, the first image will be displayed and by tapping, the other images can be viewed in a lightbox. This ensures that a user who is trying to read content won’t be frustrated by a long column of images. So if you have a favorite image and want to make sure it is shown within the article, make sure it’s standalone or the first image in the gallery.
  • A final area to consider is your community's navigation. The navigation is likely what a visitor uses to explore your wiki’s content; so keeping an organized and clear navigation will help visitors find important sections on your wiki.

What to avoid

  • Some communities have used the top of the page for warning templates or other notices for editors. These can make reading a page confusing and difficult. If a reader has to scroll through multiple templates while looking to learn about a character, they will likely be discouraged. We recommend moving these types of warnings to the talk or policy page. The top of each page on your wiki should include the most important information and encourage the visitor to continue to read. If your community disapproves of moving these sort of templates off the page, please make sure that they're given a template type of Notice so that your mobile readers won't have to experience them.
  • We recommend that you are selective with use of tables. Tables are great for organizing data but not ideal for making page layouts. Pages that use tables as layouts end up being a lot more inflexible, and difficult to display. Many tables are too wide, and require swiping to view, rather than allowing for full viewing within the screen. Try to use alternative layout tools, such as sliders, galleries or div tags. These are more flexible and work well with varying content sizes.
  • Because navboxes have a widescreen orientation, they just don't fit in a phone held at portrait orientation. You should try to limit the number of navboxes you have on your wiki. Strongly consider whether the navboxes are actually providing a service that categories can't. And always make sure your navboxes have the template type of Navbox.

Remember

Keep things simple and let the content speak for itself. Make sure to check your wiki often from a mobile device and update often to keep your it looking great. When editing a page, you can use the preview option to see how it will look on a mobile device before you save the changes. This results in the best mobile and desktop experiences for all visitors and editors on your community.

See also

Further help and feedback