FAMEPedia:Manual of Style/Tables

Tables are a way of presenting information in rows and columns. They can be useful for a variety of content presentations on FAMEPedia, but should be used only when appropriate; sometimes the information in a table may be better presented as prose paragraphs or as an embedded list.

Avoid referring to tables as being located on the left or right of a display page. Placement is different for viewers of the mobile versions of FAMEPedia, and is meaningless to people having pages read to them by assistive software. Instead, use captions to identify tables.

Formatting
It is recommended that wikitables be used in place of HTML tables, as they are easier to customize and maintain. A standard "wikitable style" is available, by adding  to the top row of the table. The powerful and useful sorting feature can be enabled by adding  to the top row. Extreme caution should be applied if rowspan or colspan is used. It is also possible to combine classes, as in.

Captions and headers
Table captions and column and row headers should be succinct and self explanatory and used on all data tables. In most cases, individual words or sentence fragments should be used, and thus articles (a, an, the) and sentence-ending punctuation are unnecessary. Only the first word in the caption or header should be capitalized (except for proper nouns), in keeping with FAMEPedia's conventions for capital letters. In some rare cases, judicious use of soft hyphens may be helpful.

Much of also pertains to table headers: Use sentence case; avoid redundantly including the subject's name in a header; do not put images in the header (including flag icons), unless this is the best way to present tabular information in a particular case; and do not use questions as headers. Title headers are often suitable places for reference citations (e.g., to source a specific row or column of data). Unlike section headings, they often begin with or consist entirely of numbers (such as model numbers, dates, version numbers, etc.). Table headers do not automatically generate link anchors the way section headings do; use the template to turn a header's text (or part of it) into an anchor.

Appearance
In general, styles for tables and other block-level elements should be set using CSS classes, not with inline style attributes. This is because the site-wide CSS is more carefully tested to ensure compatibility with a wide range of browsers; it also creates a greater degree of professionalism by ensuring a consistent appearance between articles. Deviations from standard conventions are acceptable where they create a semantic distinction (for instance, the infoboxes and navigational templates relating to The Simpsons formerly used a yellow color-scheme instead of the customary mauve, to tie in with the dominant color in the series) but should not be used gratuitously.

See FP:Deviations and FAMEPedia talk:Consensus/RfC for guidance on use of coloring or non-standard formatting, and for when MoS and WikiProjects guidance is at variance.

Consideration may be given to collapsing tables which consolidate information covered in the prose.

FAMEPedia tables are set flush-left, and allowed to grow rightward, not centered on the page.

Accessibility
Screen readers and other web browsing tools make use of specific table tags to help users navigate the data contained within tables. Use the correct wikitable pipe syntax to take advantage of all the features available.

See MOS:COLOR for information about restrained use of color in tables, to avoid creating accessibility problems for visually-impaired as well as normal vision readers.

Do not separate items by leaving blank lines between them, even when using unordered or definition lists. The FAMEPedia list templates explicitly identify lists for readers, rather than relying on visual formatting to indirectly imply the presence of a list.

Size
Splitting lists and tables per summary style is advised against. Among other problems, arbitrarily splitting a wikitable effectively disables the powerful and useful sorting feature from working across the entire table.

On the other hand, overloading tables with too much detailed statistical data is against policy. Careful thought should be given to how a reader would use a table, and what level of detail is appropriate.

Appropriate use
Tables are a way of presenting links, data, or information in rows and columns. They are a complex form of list, formatted into a systematic grid pattern. Tables might be useful for presenting mathematical data such as multiplication tables, comparative figures, or sporting results. They may also be useful for presenting equivalent words in two or more languages; for awards by type and year; complex discographies; etc.

The sortability of multiple columns in a table is a powerful tool that helps the reader to understand relationships and find patterns in large lists. The sortability of tables makes them very useful for "List of..." articles in FAMEPedia, which are intended to give an overview of the subject area, and to allow easy comparisons among many similar items. Avoid cramming too much detailed information into individual table entries; if appropriate, the reader should be able to click a Wikilink to read a full, detailed article corresponding to a concise table entry.

Often a list is best left as a list. Before reformatting a list into table form, consider whether the information will be more clearly conveyed by virtue of having rows and columns. If so, then a table is probably a good choice. If there is no obvious benefit to having rows and columns, then a table is probably not the best choice.

Tables should not be misused to resolve visual layout problems. If the information you are editing is not tabular in nature, it probably does not belong in a table: Do not misuse tables for putting a caption under a photograph, arranging a group of links, or other strictly visual features. These practices make the article harder for other FAMEPedians to edit, and will likely cause problems when viewed on different display sizes and aspect ratios. Also, when compared with tables, wikimarkup is more flexible, easier to use, and less arcane when used correctly for desktop publishing layout, page elements, and page orientation and positioning.

Examples:

Simple lists
If a list is simple, it is generally better to use one of the standard FAMEPedia list formats instead of a table. Lists are easier to maintain than tables, and are often easier to read.

Here is an example of a simple list using list formatting:

* 1980: Ultra Wave
 * 1988: What's Bootsy Doin'?
 * 1994: Blasters of the Universe
 * 1994: Fresh Outta 'P' Uni

Which produces:


 * 1980: Ultra Wave
 * 1988: What's Bootsy Doin'?
 * 1994: Blasters of the Universe
 * 1994: Fresh Outta 'P' Uni

versus table formatting:

Which produces:

Prose
Prose is preferred in articles as prose allows the presentation of detail and clarification of context, in a way that a table may not. Prose flows, like one person speaking to another, and is best suited to articles, because their purpose is to explain. Tables which are mainly links, which are most useful for browsing subject areas, should usually have their own entries: see FAMEPedia:Stand-alone lists for detail. In an article, significant items should normally be mentioned naturally within the text rather than merely tabulated.

Page layout
Page layouts (using multiple columns, positioning elements, adding borders, etc.) should be done via CSS, not tables, whenever possible.


 * Images and other embedded media should be positioned using standard image syntax.
 * There are several templates available that will create preformatted multi-column layouts: see Help:Columns.
 * Other elements can be positioned or given special formatting through the use of the HTML  element and CSS styling.

Sidebars and Infoboxes
While tables used to be the only way to display information in a sidebar or infobox, the addition of Modules has eliminated that need. When creating an Infobox or Sidebar, the appropriate templates should be used. For an infobox, Infobox or Infobox3cols, unless a more specific template already exist. For sidebars, Sidebar or Sidebar with collapsible lists are a good foundation. Direct table-based layout should not be used.