User:SOTO/Forum Archive/The Panopticon/@comment-27000174-20190225180655/@comment-1432718-20190226032305: Difference between revisions
From Tardis Wiki, the free Doctor Who reference
(Bot: Automated import of articles) |
m (Bot: Automated text replacement (-'''User:(SOTO/Forum Archive)/(.*?)/\@comment-([\d\.]+)-(\d+)/\@comment-([\d\.]+)-(\d+)'''\n([\s\S]*)\[\[Category:SOTO archive posts\]\] +\7\2/\4-\3/\6-\5)) |
||
| Line 1: | Line 1: | ||
Yes, there is a policy located at [[Tardis:Infoboxes]]. Basically it amounts to this: it is not necessary to populate every field of the infobox with as much information as possible. If something is notable enough to appear in the infobox, '''it should appear in the body of the article''' (with the kind of exceptions noted on the policy page). There are two things at work here: | Yes, there is a policy located at [[Tardis:Infoboxes]]. Basically it amounts to this: it is not necessary to populate every field of the infobox with as much information as possible. If something is notable enough to appear in the infobox, '''it should appear in the body of the article''' (with the kind of exceptions noted on the policy page). There are two things at work here: | ||
* First, as the policy states, "Infoboxes are cool, but they're not the main purpose of an article. They should be only a summary of what's in the article." We don't want people to read a bunch of stuff in the infobox and then leave the article; we want the infobox to be a teaser of what is in the article. | * First, as the policy states, "Infoboxes are cool, but they're not the main purpose of an article. They should be only a summary of what's in the article." We don't want people to read a bunch of stuff in the infobox and then leave the article; we want the infobox to be a teaser of what is in the article. | ||
* Second, an infobox that is longer than the article itself is bad design. In addition, a very long infobox can sometimes shove the table of contents '''past''' the items it's listing, and on story pages a very long infobox also shoves images down the page, causing a clumping of images just below the table of contents. This results in a messy-looking page. | * Second, an infobox that is longer than the article itself is bad design. In addition, a very long infobox can sometimes shove the table of contents '''past''' the items it's listing, and on story pages a very long infobox also shoves images down the page, causing a clumping of images just below the table of contents. This results in a messy-looking page. | ||
<noinclude>[[Category:SOTO archive posts]]</noinclude> | <noinclude>[[Category:SOTO archive posts|The Panopticon/20190225180655-27000174/20190226032305-1432718]]</noinclude> | ||
Latest revision as of 22:56, 27 April 2023
Yes, there is a policy located at Tardis:Infoboxes. Basically it amounts to this: it is not necessary to populate every field of the infobox with as much information as possible. If something is notable enough to appear in the infobox, it should appear in the body of the article (with the kind of exceptions noted on the policy page). There are two things at work here:
- First, as the policy states, "Infoboxes are cool, but they're not the main purpose of an article. They should be only a summary of what's in the article." We don't want people to read a bunch of stuff in the infobox and then leave the article; we want the infobox to be a teaser of what is in the article.
- Second, an infobox that is longer than the article itself is bad design. In addition, a very long infobox can sometimes shove the table of contents past the items it's listing, and on story pages a very long infobox also shoves images down the page, causing a clumping of images just below the table of contents. This results in a messy-looking page.
