Wikipedia:Summary style

This page documents an English Wikipedia editing guideline.

It is a generally accepted standard that editors should attempt to follow, though it is best treated with common sense, and occasional exceptions may apply. Any substantive edit to this page should reflect consensus. When in doubt, discuss first on the talk page.

Shortcuts

This page in a nutshell:

Sections of long articles should be spun off into their own articles, leaving summaries in their place.
Summary sections are linked to the detailed article with a {{Main|name of detailed article}} or comparable template.
To preserve links to the edit history of the moved text, the first edit summary of the new article links back to the original.

Wikipedia articles cover topics at several levels of detail: the lead contains a quick summary of the topic's most important points, and each major subtopic is detailed in its own section of the article. The length of a given Wikipedia article tends to grow as people add information to it. This does not go on forever: very long articles would cause problems and should be split.

A fuller treatment of any major subtopic should go in a separate article of its own. Each subtopic or child article is a complete encyclopedic article in its own right and contains its own lead section that is quite similar to the summary in its parent article. It also contains a link back to the parent article and enough information about the broader parent subject to place the subject in context for the reader, even if this produces some duplication between the parent and child articles. The original article should contain a section with a summary of the subtopic's article as well as a link to it. This type of organization is made possible because Wikipedia is an online encyclopedia: unlike traditional paper encyclopedias, it only takes a click for readers to switch between articles, and there is no need to conserve paper by preventing duplication of content.

It is advisable to develop new material in a subtopic article before summarizing it in the parent article. (An exception to this is when the subtopic is non-notable; see below.) For copyright purposes, the first edit summary of a subtopic article formed by cutting text out of a parent article should link back to the original (see WP:Copying within Wikipedia). Templates are available to link to subtopics and to tag synchronization problems between a summary section and the article it summarizes.

1 Rationale
- 1.1 Article size
- 1.2 Levels of detail
2 Technique
- 2.1 Naming conventions
3 When to avoid splits
- 3.1 Non-notable topics and relocating material
- 3.2 POV forks
4 Synchronization
- 4.1 Using selective transclusion for article synchronization
  - 4.1.1 Additional markup for selectively transcluded sub-article leads
5 Other specifics
- 5.1 Lead section
- 5.2 Further reading/external links
6 Notes
7 See also
- 7.1 Templates

Rationale[edit]

Article size[edit]

Articles over a certain size may not cover their topic in a way that is easy to find or read. Opinions vary as to what counts as an ideal length; judging the appropriate size depends on the topic and whether it easily lends itself to being split up. Size guidelines apply somewhat less to disambiguation pages and to list articles, especially if splitting them would require breaking up a sortable table. This style of organizing articles is somewhat related to news style except that it focuses on topics instead of articles.

This is more helpful to the reader than a very long article that just keeps growing, eventually reaching book length. Summary style keeps the reader from being overwhelmed by too much information up front, by summarizing main points and going into more details on particular points (subtopics) in separate articles. What constitutes "too long" is largely based on the topic, but generally 40 kilobytes of readable prose is the starting point at which articles may be considered too long. Articles that go above this have a burden of proof that extra text is needed to efficiently cover their topics and that the extra reading time is justified.

Sections that are less important for understanding the topic will tend to be lower in the article, while more important sections will tend to be higher (this is news style applied to sections). Often this is difficult to do for articles on history or that are otherwise chronologically based, unless there is some type of analysis section. However, ordering sections in this way is important because many readers will not finish reading the article.

Levels of detail[edit]

Shortcut

WP:DETAIL

Since Wikipedia is not divided into a Macropædia, Micropædia, and concise version, as is the Encyclopædia Britannica, we must serve all three user types in the same encyclopedia. Summary style is based on the premise that information about a topic need not all be contained in a single article since different readers have different needs:

Many readers need just a quick summary of the topic's most important points (lead section).
Others need a moderate amount of information on the topic's more important points (a set of multiparagraph sections).
Some readers need a lot of details on one or more aspects of the topic (links to full-sized separate subarticles).

The parent article should have general summary information, and child articles should expand in more detail on subtopics summarized in the parent article. The child article in turn can also serve as a parent article for its own sections and subsections on the topic, and so on, until a topic is very thoroughly covered. The idea is to summarize and distribute information across related articles in a way that can serve readers who want varying amounts of details. Breakout methods should anticipate the various levels of detail that typical readers will look for.

This can be thought of as layering inverted pyramids where the reader is first shown the lead section for a topic, and within its article any section may have a {{Main|subpage name}} hatnote or similar link to a full article about the subtopic summarized in that section. For example, Yosemite National Park#History and History of the Yosemite area are two such related featured articles. Thus, by navigational choices, several different types of readers each get the amount of details they want.

Technique[edit]

Longer articles are split into sections, each usually several good-sized paragraphs long. Subsectioning can increase this amount. Ideally, many of these sections will eventually provide summaries of separate articles on the subtopics covered in those sections. Each subtopic article is a complete encyclopedic article in its own right and contains its own lead section that is quite similar to the summary in the parent article. It also contains a link back to the parent article, and enough information about the broader parent subject to place the subject in context for the reader, even if this produces some duplication between the parent and child articles. In the parent article, the location of the detailed article for each subtopic is indicated at the top of the section by a link such as "Main page: Wikipedia:Splitting", generated by the template {{Main|name of child article}}. Other template links include {{Details}} and {{Broader}}. For article pairs with a less hierarchical parent/child relationship, {{See also}} may apply. Whenever you break up a page, please note the split (including the subtopic page names between double square brackets) in the edit summary.

If possible, content should be split into logically separate articles. Long stand-alone lists may be split alphanumerically or chronologically or in another way that simplifies maintenance without regard to individual notability of the subsections (common selection criteria: lists created explicitly because most or all of the listed items do not warrant independent articles; short, complete lists of every item that is verifiably a member of the group). However, a split by subtopic is preferable. Judging the appropriate size depends on the topic, although there are rules of thumb that can be applied. In some cases, to improve the understanding of readers, complex subjects may be split into more technical and less technical articles, such as in Evolution and Introduction to evolution.

Each article on Wikipedia must be able to stand alone as a self-contained unit (exceptions noted herein). For example, every article must follow the verifiability policy, which requires that all quotations and any material challenged or likely to be challenged be attributed to a reliable, published source in the form of an inline citation. This applies whether in a parent article or in a summary-style subarticle.

Naming conventions[edit]

Subarticles (not to be confused with subpages) of a summary-style article are one of a few instances where an exception to the common-names principle for article naming is sometimes acceptable.

Unless all subarticles of a summary-style article are fully compliant with the common-names principle, it is a good idea to provide a navigational template to connect the subarticles both among themselves and along with the summary-style parent article. An example of such a navigation template, used on subarticles of the Isaac Newton article, is {{IsaacNewtonSegments}}.

When to avoid splits[edit]

Shortcut

WP:AVOIDSPLIT

Non-notable topics and relocating material[edit]

Article and list topics must be notable, or "worthy of notice". Editors are cautioned not to immediately split articles if the new article would meet neither the general notability criterion nor the specific notability criteria for their topic. In this case, editors are encouraged to work on further developing the parent article first, locating coverage that applies to both the main topic and the subtopic. Through this process, it may become evident that subtopics or groups of subtopics can demonstrate their own notability, and thus can be split off into their own article. Also consider whether a concept can be cleanly trimmed, removed, or merged elsewhere on Wikipedia instead of creating a new article. Some topics are notable, but do not need their own article; see WP:NOPAGE.

If only a few sentences could be written and supported by sources about the subject, that subject does not qualify for a separate article, but should instead be merged into an article about a larger topic or relevant list. It is not uncommon for editors to suggest that articles nominated for deletion instead be merged into a parent article. Note that notability guidelines only outline how suitable a topic is for its own article or list. They do not limit the content of an article or list because notability guidelines do not apply to article content.

POV forks[edit]

In applying summary style to articles, care must be taken to avoid a POV fork (that is, a split that results in either the original article or the spinoff violating NPOV policy), a difference in approach between the summary section and the spinoff article, etc. Note that this doesn't mean that an article treating one point of view is automatically considered a POV fork. A good example is Assassination of John F. Kennedy, which has a split or spinoff to John F. Kennedy assassination conspiracy theories. However, certain types of content can be difficult to write neutrally in independent articles, such as "Criticism of..." articles (see WP:CSECTION), and if the subject is controversial it may also increase editors' maintenance burden.

Where an article has lots of subtopics with their own articles, remember that the sections of the parent article need to be appropriately balanced. Do not put undue weight into one part of an article at the cost of other parts. If one subtopic has much more text than another subtopic, that may be an indication that that subtopic should have its own page, with only a summary section left on the main page.

Synchronization[edit]

Shortcut

WP:SYNC

Sometimes editors will add details to a summary section without adding those facts to the more detailed article. To keep articles synchronized, editors should first add any new material to the appropriate places in the detailed article, and, if appropriate, summarize the material in the summary section. If the detailed article changes considerably without updating the parent article, the summary section will need to be rewritten to do it justice. These problems may be tagged with {{Sync}}.^{[n 1]}

Since the lead of any article should be the best summary of the article, it can be convenient to use the subarticle's lead as the content in the summary section, with a {{main}} hatnote pointing to the subarticle. High-level or conceptual articles (such as Philosophy) are often composed mostly or entirely of summary sections, other than their own leads. Whether a detail is important enough to include in the lead of the detailed article is a good rule of thumb for whether it is important enough to be placed in the summary.

Using selective transclusion for article synchronization[edit]

Selective transclusion can be used to ensure that the content in the lead of a sub-article is perpetually synchronized with a summary-style section in its parent article. When this method is used, the citation templates for all of the references that cite the sub-article's lead must be included in sub-article's lead section. Otherwise, an undefined reference error message will appear in the parent article since the references in the body of the sub-article are not transcluded with its lead section.

In order to selectively transclude the lead of a sub-article into a section of the parent article, replace all of the content in the relevant section of the parent article with the following wikitext markup:

{{Transcluded section|SUB-ARTICLE_PAGENAME}}

{{trim|{{#section-h:SUB-ARTICLE_PAGENAME}}}}

Additional markup for selectively transcluded sub-article leads[edit]

Per MOS:LEAD#Format of the first sentence, the first instance of the sub-article title should appear in bold in the first lead sentence of that article; this is often not desirable for a transclusion to a section of the parent article. In addition, the parent article is often wikilinked in the lead of a sub-article; when transcluded to the parent article, this wikilink will appear as bold text. The wikitext markup listed below can be used to address both of these problems.

To ensure that the article title is bolded in the first sentence of the sub-article, but unbolded and wikilinked in the transclusion to the parent article, make the following replacement in the sub-article's first lead sentence:

Replace

'''SUB-ARTICLE_PAGENAME'''

with

<noinclude>'''</noinclude>{{No selflink|SUB-ARTICLE_PAGENAME}}<noinclude>'''</noinclude>

If there is a wikilink to the parent article in the lead section of the sub-article, replacing the wikilink to the parent article with a {{no selflink}} template will ensure that it is wikilinked in the sub-article's lead but not in the transclusion to the parent article. In other words:

If the wikilink to the parent article is not a WP:Piped link, replace [[PARENT_ARTICLE]] with {{no selflink|PARENT_ARTICLE}} in the sub-article's lead
If the wikilink to the parent article includes a pipe (e.g., this link), replace [[PARENT_ARTICLE|Piped link wikitext]] with {{No selflink|PARENT_ARTICLE|Piped link wikitext}} in the sub-article's lead

Other specifics[edit]

Lead section[edit]

The lead section of an article is itself a summary of the article's content. For planned paper Wikipedia 1.0, one recommendation is that the lead section of the web version will be used as the paper version of the article. Summary style and news style can help make a concise introduction that works as a standalone article.

Notes[edit]

^ To eliminate this maintenance burden, editors can use partial transclusion as explained at Wikipedia:Transclusion#Partial transclusion.
However, discussions in 2010 highlighted issues with viewing historical renditions of the main page (the partial transclusion will be from the current subpage, which may even have been deleted). Therefore, it seems to be recommended to use this process only with consensus and when articles are rapidly evolving.
In circumstances where there is consensus to delete a sub-article which has been transcluded to a parent article, the sub-article's edit history can be preserved by moving it to a sub-page of the parent article's talk page and deleting the redirect in the mainspace.

Wikipedia:Summary style

Contents

Rationale[edit]

Article size[edit]

Levels of detail[edit]

Technique[edit]

Naming conventions[edit]

When to avoid splits[edit]

Non-notable topics and relocating material[edit]

POV forks[edit]

Synchronization[edit]

Using selective transclusion for article synchronization[edit]

Additional markup for selectively transcluded sub-article leads[edit]

Other specifics[edit]

Lead section[edit]

Further reading/external links[edit]

Notes[edit]

See also[edit]

Templates[edit]

Navigation menu

Personal tools

Namespaces

Variants

Views

More

Search

Navigation

Interaction

Tools

Print/export

Languages