PesWiki.com

Menu

PESWiki:Find or fix a stub

Lasted edited by Andrew Munsey, updated on June 14, 2016 at 9:37 pm.

  • 62 errors has been found on this page. Administrator will correct this soon.
  • This page has been imported from the old peswiki website. This message will be removed once updated.

There was an error working with the wiki: Code[1]

{| class="Talk-Notice"

|-

||'''This page is originally from There was an error working with the wiki: Code[1]. You can help by adapting it to PESWiki .

|}

{| style="border: 1px solid #aaaaaa background-color: #f9f9f9 width: 80% margin: 0 auto 1em auto padding: .2em text-align: justify"

|-

|
Image:Blue check.png

|This page is considered a PESWiki:Policies and guidelines on PESWiki. It is generally accepted among editors and is considered a standard that all users should follow. It illustrates standards of conduct, which many editors agree with in principle. However, it is not set in stone and should be treated with common sense and the There was an error working with the wiki: Code[1]. It is not policy. When in doubt, discuss first on the talk page.

|}

Stubs are articles which have not yet received substantial attention from editors of the Wikipedia, and as such do not yet contain enough information to be truthfully considered articles. The community believes that stubs are far from worthless, despite what many people may think. They are, rather, the first step articles take on their course to becoming complete.

The objective of this article is to provide a general guide for dealing with stubs. It is recommended that all users read the There was an error working with the wiki: Code[18] section, which consists of the first half of the article. There was an error working with the wiki: Code[19] contains data which might be of interest only to advanced users, and thus is optional.

Essential information

A stub is an article which is clearly too short, but not so short as to be useless. In general, it must be long enough to at least define the article's title, which generally means 3 to 10 short sentences. Note that a longer article may be a stub if the topic is complex enough conversely, a short article on a topic which has a very narrow scope may not be a stub.

Another way to define a stub is an article so incomplete that an editor who knows little or nothing about the topic could improve its content after a superficial internet search or a few minutes in a reference library. One that can be improved by only a rather knowledgeable editor, or after significant research, may not be a stub.

Sizable articles which lack There was an error working with the wiki: Code[20] or There was an error working with the wiki: Code[21] to be added to them, instead. Note that small articles with little information may end up being nominated for There was an error working with the wiki: Code[22] or be There was an error working with the wiki: Code[23] into another relevant article. Wikipedia is not a dictionary, but has a sister project—the There was an error working with the wiki: Code[35]—which is. If your article is very short consider either moving it to the Wiktionary or, even better, adding more information to it.

Once a stub has been properly expanded and becomes an article rather than just a stub, you or any editor may remove the stub tag from it. No There was an error working with the wiki: Code[24] action or formal permission is needed.

Categorizing stubs

After writing or finding the short article, the editor should insert what is called a stub template, which makes it possible for the article to be flagged as a stub. By convention, these stub templates should be placed near the bottom of the article. Stub templates are composed of two distinct parts: first, a short message stating that said article is a stub of a particular kind and encouraging editors to expand it second, a category link, which places the article on a stub category, together with other stubs with the same subject as it.

The need for stub categories arose when the main stub category—There was an error working with the wiki: Code[2]—became so full that it got quite hard to find articles on a specific topic. With stub categories, if an editor is, for example, a There was an error working with the wiki: Code[36], he or she can look for articles with the tag There was an error working with the wiki: Code[3] on said category and easily find stubs to which they can add, subtract or modify.

In general, the naming convention for stub templates is topic-stub for a complete list of these templates, refer to There was an error working with the wiki: Code[37]. When marking articles as stubs, please be as precise and accurate as you possibly can—it saves other editors a lot of work further down the road. If an article overlaps two potential categories, two different stub templates may be used, but using more than two is strongly discouraged.

Stub-related activities are centralized on There was an error working with the wiki: Code[38] (shortcut There was an error working with the wiki: Code[39]). The project should be your main reference when it comes to this subject.

Ideal stub article

When you write a stub article, it is important to bear in mind that its main interest is to be expanded, and that thus it ideally contains enough information to give a basis for other editors to expand upon. Your initial research may be done either through books or through a reliable search engine such as There was an error working with the wiki: Code[25].

Begin by giving a definition or description of the topic in question. Avoid There was an error working with the wiki: Code[40]. Since at times definitions are impossible, you should write a clear and informative description of the subject. State, for example, what a person is famous for, where a place is located and what it is known for, or the basic details of an event and when it happened.

Next, you should try to expand this basic definition. The previously mentioned research methods will often fetch you enough information for you to be able to expose the basic points of the subject. Once you have a couple of well-structured and well-written sentences, you should internally link relevant words, so that users unfamiliar with the specifics of a subject can understand what is written on the article. Avoid linking words needlessly in case you are in doubt, you should use the preview button and try reading the article from the point of view of somebody who has had no exposure to information regarding the subject. If no word seems hard to comprehend or relevant enough, simply don't link anything.

Once you have submitted the article, there are a number of courses it may take. An editor might get interested in it and develop it further, or you could expand it yourself once you have found greater information about the subject or once you have more free time on your hands.

Locating stubs

:There was an error working with the wiki: Code[41] the main list of stub categories and of articles contained within them

:There was an error working with the wiki: Code[42] deprecated, but still receives a few articles periodically

:Stubsensor a script which detects long articles with the stub tag attached to them and is used to organize periodic cleanup projects

:There was an error working with the wiki: Code[43]

:There was an error working with the wiki: Code[44]

Additional information

New stub categories

If you identify a group of stubs that do not fit in an existing category, or if an existing stub category is growing too large and might be optimized by creating a narrower category, you might propose the creation of a new stub category. Proposed new stub types are debated at There was an error working with the wiki: Code[45]. Before you propose a new stub category, make sure you consider these six guidelines:

#Is there a stub for this topic already?

#:Check There was an error working with the wiki: Code[26].

#Will the new category be well-defined enough to help editors identify articles that they have the expertise to expand?

#:Remember that using stubs categories is a way to facilitate article expansion.

#Does the new category cover ground not covered by other categories, or create a well-defined subcategory that does?

#:A new category might fit as a subcategory of more than one existing category, such as in the case of There was an error working with the wiki: Code[4], which is a child of both There was an error working with the wiki: Code[5] and There was an error working with the wiki: Code[6].

#Will there be a significant number of stubs in this category are there enough article stubs to warrant this new type?

#:Typically the threshold ranges from 100 to 300 articles. This threshold is waived if the stub category exists as a tool for use by a There was an error working with the wiki: Code[27]. In general any new category must have at least 60 articles.

#Would your new category overlap with other categories?

#:For example, geography stubs are sorted by country so you wouldn&#8217t want to create mountain-stub or river-stub.

#If you are breaking a subcategory out of a pre-existing category, will the new stub reduce the size of the parent category by a significant amount?

#:This is not an absolute necessity, but it has been a driver for the creation of most of the existing stub categories.

If you think you have satisfied these guidelines, propose the new stub category at There was an error working with the wiki: Code[46]. If there are no objections within a week, you can go ahead and create the new stub category.

Creating the stub template

NB: do not create new stub types prior to discussing them at There was an error working with the wiki: Code[47].

Once the creation has been agreed upon, you will need to create the template which will be displayed on the articles which contain the stub. This should be named logically, following this model: Template:topic-stub. For more information please refer to There was an error working with the wiki: Code[28].

This is the basic format for new stub templates:

This There was an error working with the wiki: Code[29]. You can There was an error working with the wiki: Code[30] Wikipedia by [There was an error working with the wiki: Code[7]There was an error working with the wiki: Code[8]:There was an error working with the wiki: Code[9]|action=edit}} expanding it].

There was an error working with the wiki: Code[48]

You might find use in pasting this code into the new template and customizing it by inserting different text into it. Replacing the letters A and B as such:

A: The stub topic goes into this field. For example, Road. The topic must have a developed article, and thus not be another stub.

B: This should be replaced by a proper category, so that the stub will automatically be listed together with other stubs of its kind. Continuing with the previous example, you would replace B with Road or Road-related. When the page is saved, a new template will have been created. In this example, There was an error working with the wiki: Code[10].

It is also possible to automate the procedure of creating new stub templates somewhat by using the following syntax:

There was an error working with the wiki: Code[11]

This will produce a message saying "This A is a stub. You can help Wikipedia by expanding it" and will put stubs in category named "B stubs", just like the above manual method.

It is also possible to add a small image to the stub template (the "stub icon"). However, this is discouraged because it increases the strain on the Wikipedia servers. If you still wish to use images, apply formatting such as that provided by There was an error working with the wiki: Code[12] (and remember to use it with the subst: prefix).

Creating the stub category

NB: do not create new stub categories prior to discussing them at There was an error working with the wiki: Code[49].

Next, you will need to create a category to hold the articles which will have the new stub tag attached to them. Do this before you add your new template to any articles.

To start editing it, you should follow the red category link on the stub template you have created. In this case, it would appear as There was an error working with the wiki: Code[50]. Here's the basic format for stub categories:

There was an error working with the wiki: Code[13]

A: Insert the description of the category here. In this case it would be roads, you can expand the description by adding additional terms. So you could, for example, add road transportation.

B: Insert the name of the new stub here.

C: Insert the name of an appropriate higher level non-stub category, for this example it would be road transport.

This syntax does four things, it:

# adds the There was an error working with the wiki: Code[51] to There was an error working with the wiki: Code[52]

# provides a description of the category

# displays the stub text

# inserts this category into a higher level category, in this case the Category:Road stubs will be a member of Category:Road transport.

So, in this example, the formatting would look like this:

There was an error working with the wiki: Code[14]

It is also advisable to add it to a larger stub category, if an appropriate one exists. For There was an error working with the wiki: Code[53], no such category exists however.

In order to increase the category's effectiveness and visibility, it's generally advisable to add your category to several categories. For example, this would add it to the Roads category:

There was an error working with the wiki: Code[54]

When you are done, it is important that you make sure that the new stub and the new stub category are linked correctly to other categories. Using the road-stub as an example, the road-stub category needs to be a member of There was an error working with the wiki: Code[55] (because it's a stub category) and There was an error working with the wiki: Code[56] (because it's a category consisting of roads). If your new category has been made from part of an existing stub category or categories, these should also be listed here (so, for example, There was an error working with the wiki: Code[57] should be part of There was an error working with the wiki: Code[58] and There was an error working with the wiki: Code[59]).

At this point, you should add the new stub category to this list: There was an error working with the wiki: Code[60]

Once the new stub category is approved by the There was an error working with the wiki: Code[61] (which should normally be done before it is created), to make clear that it underwent the mandatory revision process and was approved by means of consensus, add the There was an error working with the wiki: Code[15] template to the category page.

If you have doubts or comments regarding any part of the process, don't hesitate to address them There was an error working with the wiki: Code[31].

See also

There was an error working with the wiki: Code[62]

There was an error working with the wiki: Code[32]

There was an error working with the wiki: Code[33]

There was an error working with the wiki: Code[34]

Comments