FANDOM


Did you know the awesome, beautiful content you collectively write is read by over 100 million people all over the world each month? For the majority of our communities, most visitors are doing so on mobile devices.

FANDOM's best practices will help you build and format your content to look great on any device, be it our rich and dynamic desktop site, our reader-oriented mobile site, or our specialized mobile apps.

What are best practices?

FANDOM worked with several experienced admins and community members to establish a set of supported do's and don'ts for wiki content and templates. Our goals are to support and foster the creativity that exists on the FANDOM platform today while encouraging modern web practices and standards.

The best practices are easy to add to your existing templates and content. Most of your existing content will continue to look and function exactly as it does today on desktop, but even better on mobile phones and tablets, including our Community Apps. Additionally, abiding with these best practices can improve SEO rankings for your communities and decrease page load times.

There's already a healthy amount of sharing and similarities between communities, but following our best practices will help FANDOM identify different content types (infoboxes, navboxes, quote templates, etc.) and display them appropriately to provide world-class reading and editing experiences for existing fragmented elements.

Best practices

Infoboxes

Help:Infoboxes includes information on FANDOM's new recommended markup for infoboxes, often called "portable infoboxes".

Templates

Help:Template types includes information on how to properly organize your templates to ensure the FANDOM mobile skin knows how to best display them.

Tables

Improper use of tables can have adverse effects on how article pages render on any device — desktop, tablet, or mobile.

The first best practice for tables is to avoid building and formatting pages entirely out of tables. Tables should only be used to organize and display data, such as a statistical breakdown of a video game weapon or a list of actors in an episode. To achieve specific designs for your article pages, use modern HTML and CSS practices, such as those demonstrated on W3Schools.com.

The second best practice for tables is to avoid nesting tables. Instead, merge cells whenever possible, or abide by W3Schools conventions.

The third best practice for tables is to be reasonable with the number of columns and rows you use to make sure they are easy to read on both desktop and mobile devices. Break up large amounts of data into smaller, easier-to-digest tables.

Questions?

If you have any questions about these best practices, or need help adapting your contents to follow these best practices, please reach out for help through the Community Central forums, the Portability Hub, or a Special:Contact.

See also

Further help and feedback