Sarkarverse:Article size

From Sarkarverse
Jump to: navigation, search
"SV:AS" and "SV:SIZE" redirect here. For information on the size of Sarkarverse, see Sarkarverse:Statistics.

This page contains an overview of the key issues concerning article size. Three measures are key:

  • Readable-prose size: all viewable text in the main sections only, not including any viewable text in a table or a list, and not including any footer sections
  • Wiki markup size: all viewable wikitext in the editable file, as shown in the character count of the edit history page
  • Browser-page size: the total size. This is the size that a web browser loads.

For any given article there is no specific relation between the three, although general relations can be assumed.

Usability considerations concerning the size of an article have been determined to include:

  • reader issues, such as an attention span, readability, organization, information saturation, etc.
  • editor issues, for example easing a tense talkpage experience, arguments over trivial contributions, debates on how to split up a large article, etc.
  • contribution issues, such as articles ceasing to grow significantly once they reach a certain size – this does not imply, however, that there is no more information on the topic to be contributed
  • other technical issues, for example, browser limitations, slow upload speeds, etc.

When an article seems to be the wrong size, five rule-of-thumb administrative responses are given here based on readable-prose size. The decision to divide a large article, break part of it out into a new article, or combine all or part of it into another existing article is an editorial decision that requires consensus. Other solutions for too-large articles, and guidelines on the size of articles, are provided below. The licensing policy mandates that any decision to "break out" or combine articles must be accompanied by an edit summary ala "new content from the [[page name]]".

Readability issues

Each Sarkarverse article is in a process of evolution and is likely to continue growing. Other editors will add to articles when you are done with them. This is not a technical problem, because, for most practical purposes, Sarkarverse has unlimited storage space; however, long articles may be more difficult to read, navigate, and comprehend.

An article longer than one or two pages when printed should be divided into sections to ease navigation (see Sarkarverse:Manual of Style and Sarkarverse:Layout for guidance). For most long articles, division into sections is natural anyway. Readers of the Mobile Web version of Sarkarverse can be helped by ensuring that sections are not so long or so numerous as to impede navigation.

A page of about 30 kB to 50 kB of readable prose, which roughly corresponds to 4,000 to 10,000 words, takes between 30 and 40 minutes to read at average speed, which is right on the limit of the average concentration span of 40 to 50 minutes.[1] At 50 kB and above it may benefit the reader to consider moving some sections to other articles and replace them with summaries per Sarkarverse:Summary style - see WP:SIZERULE for "a rule of thumb". Comprehension of standard texts at average reading speed is around 65%.

Articles that cover particularly technical subjects should, in general, be shorter than articles on less technical subjects. While expert readers of such articles may accept complexity and length provided the article is well written, the general reader requires clarity and conciseness. Most articles do not need to be excessively long; however, there are times when a long or very long article is unavoidable, though its complexity should be minimized. Readability is a key criterion.

Measuring "readable prose" size

"Readable prose" is the main body of the text, excluding material such as: footnotes and reference sections ("see also", "external links", bibliography, etc.); diagrams and images; tables and lists; Wikilinks and external URLs; and formatting and mark-up.

The following script is helpful for estimating readable prose size: User:Dr_pda/prosesize.

Lists, tables and summaries

Script error Lists, tables, and other material that is already in summary form may not be appropriate for reducing or summarizing further by the summary style method. If there is no "natural" way to split or reduce a long list or table, it may be best to leave it intact, and a decision made to either keep it embedded in the main article or split it off into a stand-alone sub-article. Regardless, a list or table should be kept as short as is feasible for its purpose and scope. Too much statistical data is against policy.

Technical issues

Further information: Sarkarverse:Browser notes

Total article size should be kept reasonably low, because many users edit from low-speed connections including dial-up connections, smartphones, and low-end broadband connections. The text on a 32kB page takes about five seconds to load for editing on a dial-up connection, with accompanying images taking additional time, so pages significantly larger than this are difficult for older browsers to display. Articles of about 200kB (~30 pages) are not uncommon for topics that require depth and detail, but it's typical that articles of such size get split into two or more sub-articles.

Mobile browsers can be a problem because these devices usually have little memory and a slow CPU; long pages can take too much time to process, if they can be fully loaded at all. When using slow connections, e.g., a desktop computer with an analog modem dial-up or the wireless connection of some mobile devices, long articles can take too much time to load. For notes on unrelated problems that various web browsers have with MediaWiki sites, and for a list of alternative browsers you can download, see Sarkarverse:Browser notes.

The maximum limit for Sarkarverse is set by the MediaWiki software default article size limit, 2048 kilobytes.

Splitting an article

Script error

For more details on this topic, see Sarkarverse:Summary style.

Very large articles should be split into logically separate articles. Long stand-alone list articles are split into subsequent pages alphabetically, numerically, or subtopically. For non-mainspace articles, consider splitting and transcluding into the split parts.

When you split a section from a long article into an independent article, you should leave a short summary of the material that is removed along with a pointer to the independent article. In the independent article, put the {{SubArticle}} or {{Summary in}} tag on the talk page to create a banner that refers back to the main article.

To conform with Sarkarverse's licensing requirements, which permit modification and reuse but require attribution of the content contributors, the new page should be created with an edit summary noting "split content from [[article name]]". (Do not omit this step or omit the page name.) A note should also be made in the edit summary of the source article, "split content to [[article name]]", to protect against the article subsequently being deleted and the history of the new page eradicated. The {{Copied}} template can also be placed on the talk page of both articles.

No need for haste

As browsers have improved, there is no need for haste in splitting an article when it starts getting large. Sometimes an article simply needs to be big to give the subject adequate coverage. If uncertain, or with high profile articles, start a discussion on the talkpage regarding the overall topic structure. Determine whether the topic should be treated as several shorter articles and, if so, how best to organize them. If the discussion makes no progress consider adding one of the split tags in order to get feedback from other editors.

Breaking out trivial or controversial sections

For more details on this topic, see Sarkarverse:Content forking.

A relatively trivial fact may be appropriate in the context of the larger article, but inappropriate as the topic of an entire article in itself. In most cases, it is a violation of the neutral point of view to specifically break out a controversial section without leaving an adequate summary. It also violates the neutral point of view policy to create a new article specifically to contain information that consensus has rejected from the main article. Consider other organizational principles for splitting the article, and be sure that both the title and content of the broken-out article reflect a neutral point of view.

Breaking out an unwanted section

If a section of an article is a magnet for unhelpful contributions (such as the "external links" section or trivia sections), be aware that while moving it to another article may help to clean up the main article, it creates a new article that consists entirely of a section for unwanted contributions. If an article includes large amounts of material not suitable for inclusion in the encyclopedia, it is better to remove that content than to create a new article for it.

Size guideline

Script error Some useful rules of thumb for splitting articles, and combining small pages:

Readable prose size What to do
> 100 kB Almost certainly should be divided
> 60 kB Probably should be divided (although the scope of a topic can sometimes justify the added reading material)
> 50 kB May need to be divided (likelihood goes up with size)
< 40 kB Length alone does not justify division
< 1 kB If an article or list has remained this size for over a couple of months, consider combining it with a related page. Alternatively, why not fix it by adding more info? See Sarkarverse:Stub.
Please note:

These rules of thumb only apply to readable prose (found by counting the words, perhaps with the help of Shubinator's DYK tool or Prosesize) and not to wiki markup size (as found on history lists or other means). It also applies somewhat less to disambiguation pages and naturally do not apply to redirects. They also apply less strongly to list articles, especially if splitting them would require breaking up a sortable table.

Content removal

Content should not be removed from articles simply to reduce length; see Sarkarverse:Content removal#Reasons for acceptable reasons.

How to find articles by markup size

The largest articles (by markup size, not readable prose size on which the above size guideline is based) are listed at Special:Longpages.

You can find the size of the markup of a page in bytes from its page history (near the bottom). Also the search box entry: intitle:Article title will show both number of words in the article and the size of the article in kilobytes. In most cases these are not reliable indications on their own of whether an article should be split.

Note that the ability to edit a section rather than the entire page decreases wait time, removing some of the many, oversized-page problems for editors; however, readers with slow modems will still have to wait for the entire page to load.

You can set your preferences (by changing the "Threshold for stub link formatting" under the "Appearance" menu) to make links to pages smaller than a certain size appear in a different colour. "Size" in this context means the size of the source text seen in the edit box.

If you have problems editing a long article

If you have encountered an article that is so long you can't edit it, or if your browser chops off the end of the article when you try to edit it, there are a few ways you can solve the problem.

The best permanent solution is to simply upgrade to a more modern web browser, if possible. No major modern web browsers have this problem on their recent versions, and there are many other benefits to upgrading to their latest version: more recent versions will be considerably more secure, will do a better job displaying content written to more modern HTML (and other standards), and will have fixed many bugs, besides this one. Many articles on Sarkarverse may be longer than 32kB on a permanent basis, so you will continue to have occasional problems with article length as long as you are using an older browser.

As a temporary solution, you should be able to edit the article one section at a time by using the "Edit" links you see next to each header in the article. This should work as long as none of the sections are longer than 32kB, which they really shouldn't be. You can edit text before the first section by editing the first section, then changing the &section=1 part of the URL to &section=0. (See bugzilla:156 and two JavaScript workarounds: 1, 2.) You can insert a new section either by using the "New section" link (if there is one) in the "Views" section, or by editing an existing section and explicitly adding a second header line within it. See also Section editing and Editing before the first section.

If you find a section too long to edit correctly and safely, you can post a request for assistance on the help desk. Follow the "New section" link, which will allow you to post a new comment without editing any existing text.


  1. ^ John V. Chelsom, Andrew C. Payne, Lawrence R. P. Reavill (8 Apr 2005) "Management for Engineers, Scientists and Technologists" John Wiley & Sons p. 231 retrieved 20 February 2013