Wikipedia talk:Stub/Archive 15

Semi-protected edit request on 24 January 2021
1. defines 'repoussoir' as "a strongly defined figure in the FOREGROUND of a picture to 'push back' or give depth to, and enhance the principal scene or episode'. On that basis, the figure on the right in the Rubens picture is the 'repoussoir'.

2.I do not think the figures, front-right, in the Caillebotte, could be described so either, as they tend to draw the eye out of the scene (of course in doing that, they DO emphasise the depth of the scene); but still, I would suggest, NOT 'repoussoir.

3.As for the tree in the Ruisdael,I would refer to it as a 'coulisse' -as in the , meaning 'wing (as in a theatre) I.E. something that functions as a framing device in the picture itself.

In short, it is the images that need to be replaced. I could suggest two Giotto's Arena Chapel images. 1. The 'Nativity scene', where the two angels on the far right direct our gaze inward towards the angels who are celebrating the birth over the roof of the stable and the sheep in the near right, several of which direct our view to Mary And Jesus. And, 2. the Kiss of Judas, where the 'Pharisee' on the right directs our attention (and that of the soldiers) to Jesus John O&#39;Riordan (talk) 20:03, 24 January 2021 (UTC)
 * Red information icon with gradient background.svg Not done: Are you sure you are in the right place? I have no idea what you are asking. This is not an encyclopedia article, it is a project coordination and policy page. Elliot321 (talk &#124; contribs) 20:54, 24 January 2021 (UTC)

Different template
I realize I may be in the wrong place but here goes. Stubs are bad. We know that because we have a template that asks people to help improve each stub page and adds the page to a category. But some stubs, I submit, are permanent. An example is George A. Loyd. He was born in Ohio, served in the Civil War, was awarded the Medal of Honor before the language included "above and beyond," was discharged, and died in 1917. Loyd gets a page because of the Medal but that's the only reason. His page will never be anything BUT a stub. Do we need a template named "permstub" (or something) that acknowledges the fact of the "stubness" but doesn't put the page on a to-be-fixed list/category?-- Georgia Army Vet Contribs Talk 20:29, 6 June 2020 (UTC)
 * Stubs are not bad. Precisely because we have permanent stubs, and that is fine.
 * At the same time, I support the idea of having a separate template for article that we expect to remain stubs forever.
 * I'd call the template Template:Permanent stub, with abbreviations like Template:Permstub as a redirect. Debresser (talk) 13:56, 7 June 2020 (UTC)
 * I should have gotten back to you sooner. "Bad" should have been in quotes from the start; I occasionally forget that voice inflection doesn't carry well to the printed page. I'd like to see additional editor weight in on this.-- Georgia Army Vet Contribs Talk 02:27, 9 June 2020 (UTC)
 * At that point, what is such a template even saying? "This is a short article"? I think the reader can see that for themselves. I would support just removing any stub templates from articles like George A. Loyd. If absolutely necessary, maybe we could have a permastub template which has no visible output which just exists to make sure that stub tags don't get re-added by bots or semi-automated tools (though that sounds like an annoying hack). Colin M (talk) 18:13, 23 April 2021 (UTC)

Vipin Agnihotri
Vipin Agnihotri is an award winning writer and film director. Rachitjournalist (talk) 17:25, 28 May 2021 (UTC)


 * You are on the wrong page. Please see your talk page for a Welcome message and links to information about editing in Wikipedia. - Donald Albury 18:03, 28 May 2021 (UTC)

Question - Duration for an article being a Stub
I got a question that I just recently thought of and want some input on. If an article that is deemed a Stub is not expanded upon by editors with additional information over a considerable period of time (i.e. more than four years), does it have a duration of notability on it under this circumstance, and if so, how long does that period last before it is considered that the notability of the subject should be questioned? GUtt01 (talk) 11:12, 1 July 2021 (UTC)
 * WP:There is no deadline. -- Red rose64 &#x1f339; (talk) 20:43, 1 July 2021 (UTC)

Use-Mention Distinction in introduction
In the introductory paragraph Stub, the second bullet point following the "the distinction between dictionary and encyclopedia articles is best expressed by the use–mention distinction" phrase gives a wordy, accurate explanation, but I think some examples of good Articles for Wikipedia vs. dictionary articles would be helpful. And the link to "use-mention distinction" is pretty arcane to be useful. I'd toss out an example "example" but it's likely to not be too good of an example. I know quite well the difference but some concrete examples should be helpful here for the average new editor. MeekMark (talk) 22:07, 10 August 2021 (UTC)

Unused Stub Templates
This is part of a discussion that I've started on WikiProject Templates to create a task force monitoring the unused templates on Wikipedia. According to one of the users, there are about 1,000 unused stub templates. Are any members of this project going to nominate them for a Tfd? It would help minimize the workload for the proposed task force. --WikiCleanerMan (talk) 22:46, 7 September 2021 (UTC)
 * Do we have a link to a list of them? Cas Liber (talk · contribs) 23:12, 7 September 2021 (UTC)
 * Once upon a time there was a report, but the last time it was run was 2016. If anyone knows how to run the report, now's the time for it. Her Pegship (?) 23:20, 7 September 2021 (UTC)
 * Unless a stub template is malformed in some way, or duplicates another stub template, I see no reason to delete it: it might be needed tomorrow. Stub templates are used temporarily: if, in an ideal world, every article in the encyclopedia was improved beyond stub status, every stub template would become unused until another stub was created. Pam  D  23:25, 7 September 2021 (UTC)
 * The ones I'm aware of are the ones listed at the Unused templates database at the bottom of page 16 and page 17. --WikiCleanerMan (talk) 23:26, 7 September 2021 (UTC)
 * Thanks. The majority of those look perfectly fine; on a quick skim through I've nominated 4 for deletion as malformed duplicates, or in one case a malformed, unused, stub not part of an existing hierarchy. Other stub geeks might spot a few more.  Pam  D  07:28, 8 September 2021 (UTC)
 * There's also this Unlisted stub types report but hasn't been updated since 2018. --WikiCleanerMan (talk) 23:31, 7 September 2021 (UTC)
 * Holy cats! I've never seen Database reports/Unused templates. Very useful. Her Pegship (?) 18:00, 8 September 2021 (UTC)
 * You've not? The TfD pages would be a lot emptier without it. -- Red rose64 &#x1f339; (talk) 12:14, 9 September 2021 (UTC)
 * Her Pegship, if you're interested in my task force proposal or anyone else for that matter feel free to join on the Template project talk page as this question about the Stub templates is a part of the main discussion. --WikiCleanerMan (talk) 18:50, 9 September 2021 (UTC)

Stub deletion
I cannot find any information on Wikipedia that references stub deletion, which is probably the answer to my question. I would like to know if there is a policy or guideline about deleting stubs. I am not the author of the stub. Thank you for any assistance. God bless and happy editing! MarydaleEd (talk) 22:43, 11 September 2021 (UTC)
 * The general deletion policy at WP:DELETE applies. I'm not aware of any special deletion rules or processes that are specific to stubs. Colin M (talk) 22:53, 11 September 2021 (UTC)
 * There aren't. Deletion policy for stubs is exactly the same as for any other article. In short, there are four routes - WP:CSD, WP:PROD, WP:BLPPROD and WP:AFD. Of these, BLPPROD can only be used on biographies of living persons, and PROD can only be used if the article has never previously been taken to either PROD or AFD. -- Red rose64 &#x1f339; (talk) 23:30, 11 September 2021 (UTC)

Discussion at Wikipedia:Village pump (idea lab) § Why do we customize appearance of stub tags by topic?
You are invited to join the discussion at Wikipedia:Village pump (idea lab) § Why do we customize appearance of stub tags by topic?. &#123;{u&#124; Sdkb  }&#125;  talk 00:27, 21 September 2021 (UTC)

Tables
is tabular content to be ignored in assessing whether an article is a stub? The list of  is full of articles - many election results, histories of sports events  and the like - which are very substantial, but in table form, and it has been put to me that "We don't build articles out of tables. We build them out of prose. How is an article with just two articles of prose above a stub?" Rathfelder (talk) 08:36, 30 August 2015 (UTC)
 * "Ignored" is probably a strong word, but tabular data probably doesn't count for a lot. What may happen, though, is that an article that consists and probably always will consist of such data is often really a list that needs to be renamed to "List of whatever", and judged as a list not as a prose article.  — SMcCandlish ☺ ☏ ¢ ≽ʌⱷ҅ᴥⱷʌ≼  23:29, 30 August 2015 (UTC)
 * Stand-alone lists are essentially articles built out of tables so the advice you received is hard to defend. ~Kvng (talk) 14:23, 3 September 2015 (UTC)

Taxonomy stub redirects
Howdy. Is there any harm in creating templates in the form Template:LessCommonName-stub that redirect to Template:AlreadyExisting-stub? I've started doing this for some species/taxonomy stubs, e.g. Template:Parastacoidea-stub to Template:Crayfish-stub. This is helpful for one of my scripts, which relies on the taxonomic name when figuring out what stub to use. I realized I'm starting to make a bunch of these so I figured I'd better double check here. Thanks. – Novem Linguae (talk) 02:36, 27 January 2022 (UTC)


 * I decided to delete these. Templates with zero transclusions usually get deleted eventually. And I figured out a way to write my script without depending on these redirects. – Novem Linguae (talk) 04:55, 28 January 2022 (UTC)

Minimum size
Some stubs say next to nothing, e.g. "Xtrynyr is a community in Ruritania", with no clue about where the information came from. A stub like this is annoying to users who follow the bluelink to Xtrynyr and find no useful information. This is to propose adding something like the following to this guideline:
 * "As a rule, a stub should provide some information about the subject that will be useful to readers, even if that information is minimal. It should also give at least one source for the information provided. Creation of stubs that provide no useful information and/or include no sources is deprecated"

Comments? Aymatth2 (talk) 17:32, 1 November 2011 (UTC)
 * Such pages may be eligible for speedy deletion under WP:CSD. -- Red rose64 (talk) 19:00, 1 November 2011 (UTC)
 * Ugh, this is not what A3 is for, despite its misuse. "Xtrynyr is a community in Ruritania" absolutely does not meet A3--read the criteria... Calliopejen1 (talk) 21:55, 1 November 2011 (UTC)


 * Although we certainly would like all new articles to have at least one source, it is not an absolute requirement outside the realm of WP:BLP articles. Nor should it be. The rest of your proposal is contradictory. You say they should "provide some information about the subject that will be useful to readers, even if that information is minimal. " That's exactly what these one-liners do, provide minimal information on a notable subject that can later be expanded into a fully-fleshed out article. Many of our geographic location articles started out in such a state, whether mass-created or not. Somebody lives some tiny village and finds it isn't mentioned here, so they add it. Later on someone else comes along and expands it and adds refs. That's exactly how Wikipedia is supposed to work. Beeblebrox (talk) 19:34, 1 November 2011 (UTC)


 * In principal I would agree with Aymatth2 that all new created articles really should have bare minimum one fact, preferably referenced. However, I as was recently discussed am prone to getting carried away with some batches of contentless articles if there is a large number of articles to work thorugh from a category from another wikipedia. A big project of mine at the moment is Turkish villages of which 26,000 are missing all of which have content in the articles on Turkish wikipedia and all of which have population data available. I believe they are worth starting as xxx is a village in xxx province, Turkey because at some point I know they can easily be expanded and if I was to take it in a one by one approach I would never even ttempt to try to dtart 200 let alone 26,000. In the long term I believe we are better off having even one liners on villages in Turkey as I know they can be expanded. I think there is a difference though between an article which is intended to be transwikied with content which already exists in another language and those which are unverifiable. I would rarely create an unsourced "sub stub" if it wasn't a transwiki thing. Most of my articles are sourced and contain a fact or two, especially if created in their own right not as part of the INterntranswiki project. Personally I would allow leeway in regards to short articles which exist in detail on another wikipedia and are intended to be transferred. I believe we should not think of the other wikipedias as a separate sites but as part of the same project.♦ Dr. Blofeld  19:41, 1 November 2011 (UTC)
 * I am o.k. with that. Presumably a person creating a stub has access to some knowledge about the subject, maybe from another wikipedia, and can provide a bit of information with a source. Then the stub does not irritate people who follow the blue link before it gets expanded. Saying "Xtrynyr is a community in the Strznx province of Ruritania with a population of 30 people as of 2002" gives some useful information - but it should be sourced. Aymatth2 (talk) 19:53, 1 November 2011 (UTC)
 * Most of the useless stubs I come across appear to be created in the hopes that someone else will come along and provide extensive information about a very narrow subject, which is only likely to happen if a) you have an editor who is that obsessed with the subject, or b) there is a PD source of information handy to copy and paste. In the latter category, too many National Register of Historic Places stubs come to mind.  Never mind that if these places are on the NRHP, they're notable because of historically significant events or occurrences, not because of their mere placement on the NRHP.  Just from reading the articles in question, however, you would think notability was due to the latter rather than the former.  I would hope that if any editor is doing this with a noble cause in mind, that it would be human knowledge, not the titular subject of one article or another.  Keeping that in mind, perhaps making more extensive use of article merging where necessary?RadioKAOS (talk) 19:55, 1 November 2011 (UTC)


 * (ex x2)I find the one-line mass-created stubs absolutely useless and think it's even worse to see one of these without any reference at all. The information would be much better presented as part of a list (List of villages in XXX province, Turkey, for example). This way the encyclopedia could still have the basic information (now we know the village exists), and an article on a particular village can be created later, when sources have been identified and someone is actually interested enough to write a real article about it. That said, the proposed text is so vague that the current stub creation would qualify. Karanacs (talk) 19:56, 1 November 2011 (UTC)
 * With all due respect Karanacs dictating what should be written into this encyclopedia because of "interest to actually write a real article about it" is the extreme problem we are suffering from. Systematic bias, which is why we have GAs on hundred of US TV series episodes and are missing 95% of the lakes of Sweden. The vast majority are only interested in their part of the world and popular culture/sport. Sorry but because the average Joe doesn't want to write a full article about a legit town of a few thousand people in Benin that is not a reason to exclude it from the encyclopedia. Of course we need some interest from one or two to expand it. Take this as an example. Articles are usually developed by one or two people. There are enough people in the world who could potentially use wikipedia and have the full range of interests.♦ Dr. Blofeld  20:05, 1 November 2011 (UTC)
 * I do not understand why it is better to have thousands or hundreds of thousands of one-line articles instead of a few dozen or few hundred lists that contain the same information. Karanacs (talk) 20:15, 1 November 2011 (UTC)

What Aymatth2 would be your minimum requirement? Like Ataliklikun Bay, Gbégourou or Axaren. Would Château de Gaujacq be acceptable to you given that sources and information is already there on French wikipedia? I'm gathering that most here (myself included) would frown against ones like Axaren which are as they stand useless. One fact and source minimum requirement I could agree on.♦ Dr. Blofeld  20:01, 1 November 2011 (UTC)
 * I should point out that this is a guideline, not a policy. I would say Ataliklikun Bay is fine - plenty of sourced information. Gbégourou is fine too. The location is described and shown on the map, and the population is given with a source. Axaren passes the criterion of having some useful information (the province) but has no sources. Maybe this is an imaginary lake. I would fail it. I would fail Château de Gaujacq too, for the same reason, but would have no problem if one of the sources on the :fr wikipedia were brought across. With trans-wiki articles, we still need some basic proof of existence from external sources. Other wikis have quality problems too. Aymatth2 (talk) 20:20, 1 November 2011 (UTC)


 * If you think they are useless, why do you create them? Karanacs (talk) 20:17, 1 November 2011 (UTC)

"Which are as they stand are useless" and "are useless" are two different things. We are a wiki and content can be added within seconds/minutes if anybody wants to add it. I only start articles which I believe are notable topics and can be expanded. The idea Karanacs is that in a few years time we end up with hundreds of thousands of full length sourced articles!! The ultimate goal is that by 2015 we see many articles started developed like this. Tall order perhaps but the world is a big place!! I create them because I feel it is important for us to cover notable topics which get excluded due to bias and want us to at least try to start covering the world evenly! OK maybe start the article will not change the fact that many are no interested in Swedish lakes but that doesn't make them unencyclopedic.. I could accept a rule that "if a reader visits an article he MUST be able to learn one fact at bare minimum about that subject". So for a town a population figure or location information in relation to other settlements, with rivers or lakes an area/length figure, with mountains an altitude figure etc. ♦ Dr. Blofeld  20:01, 1 November 2011 (UTC)


 * The making of stubs should be actively encouraged, The principles are building the web, and that Wikipedia is supposed to be an encyclopedia --even incomplete information is useful, as long as it is verifiable.   Whether we would do better making combination articles is a question of style, that basically does not greatly matter: people may do as they please about it.  Nothing stops consensus from merging articles later, or splitting them either.


 * The relevant question can therefore only be whether we should encourage the making of stubs without sources. We should not. We should encourage all articles to be sourced. An encyclopedia without explicit or implied verifiability is close to useless, & our method of working requires explicit verifiability, as no editor here can be assumed to be reliable..  Nonetheless, the creation of articles even with out sources should be permitted, because someone else may wish to source them--and usually someone does do that.  But someone who insists on created unsourced articles--large or small, minimal or more than minimal, is not being as constructive as they ought to be.   DGG ( talk ) 20:26, 1 November 2011 (UTC)
 * Giunssani is practically unsourced though and I think its a very constructive article.♦ Dr. Blofeld  22:31, 1 November 2011 (UTC)

@Aymatth2 In my opinion Château de Gaujacq if the 1686 fact was sourced that would be bare minimum right?♦ Dr. Blofeld  20:27, 1 November 2011 (UTC)
 * That would be good enough for me. A source would verify existence of the chateau, and likely leads to further information. The article has useful information about the chateau, even a picture, so would not annoy the reader who clicked on the bluelink. They might want more, but at least get something. Aymatth2 (talk) 13:12, 2 November 2011 (UTC)

Coming from the discussion at ANI, my issue with auto creation of very short stubs that are obviously verifiable is that they lack notability. Notability's only a guideline, and of course there are some classes of articles like geographical features that are generally accepted on the long-term presumption of notability, but these present a problem when we're ready to willy-nilly delete articles on television episodes, fictional characters, garage bands, local businesses, etc. I fully understand the difference, but it is very hard to quell the calls that call out to WP:OTHERSTUFFEXISTS by the newer users that see these articles get deleted while we have stubby articles on a river that only 100 people in the world may even know about. Personally, articles that are likely going to be stubs for a long long time should instead be created as redirects to a list of such notable features, so that when that stub actually can be expanded, its a non-admin action that any editor can undertake. --M ASEM (t) 20:28, 1 November 2011 (UTC)

I disagree. A notable topic will always be notable however short. The problem as you say is that some of them may take an awful amount of time to be developed. IN regards to settlements time and time again I've requested a bot creates lists of settlements in a table like List of populated places in Peru by country using coordinates from geonames and we redirect until enough info can be found to create half decent articles. Given that there appears to be support for this why didn't any of you lot support me for I proposed this huh? ♦ Dr. Blofeld  20:31, 1 November 2011 (UTC)


 * Which we don't allow for any other topic unless it has been assessed via one of the sub-notability guidelines. And even then, the presumption of notability is how much the community tolerates the lack of proof. The fact that notability guidelines for geographic features have been presented and rejected by the community suggests that these don't have automatic notability.  Yes, at some point, the Foundation should have pages dedicated to being a gazetteer to list out all these features, but this screams to either break out a WikiAtlas project, or to use reason seasons to group common features into list/tables within the encyclopedic side. No information is lost by the latter process. --M ASEM  (t) 20:35, 1 November 2011 (UTC)


 * Again I proposed WIkiAtlas to the foundation back in 2009. But I'm not getting what I wanted. And you'll find virtually all geo features if covered in sources will be notable.♦ Dr. Blofeld  20:44, 1 November 2011 (UTC)


 * It is acceptable to create very short stubs about types of subject generally accepted as notable, as long as they have at least one reliable source to satisfy verifiability. High schools are generally found in AFD to be notable, for instance.  "Blivet High School was a high school in Tennessee," referenced to a Tennessee Department of Education database, would be minimally acceptable. It would be better to inform the reader that "Blivet High School was a high school in Dickson County, Tennessee from 1895 until 1950, when it was merged into Dickson County Central High School." A similar one line minimal stub about a present or former licensed radio or TV  station which produced a portion of its programming would be acceptable if referenced to the FCC (or appropriate national) database. Its frequency, power, ownership, format etc would be useful info but not essential if someone wanted to create a category of related stubs from a reliable source. The same goes for some politicians such as state legislators. "Ambrose Abbott was a member of the Maine Legislature" would be minimally acceptable, referenced to the state legislature database. It would be desirable and helpful to the reader to note that Abbott served in one term, from January to March, 1874.  Local newspapers (not indexed in Google Newspaper archive) and the state archives likely have much more information than I could find online, for someone to fill in his biographical details. I object to treating any Wikipedia as a reliable source; the English language Wikipedia has contained at various times hoax articles describing military heroes, persons of nobility, towns, and even wars. I suspect that some other language Wikipedias, with fewer administrators, likely have a number of hoax, mistake, or simply incorrect entries as well. A seasoned editor creating hundreds or thousands  of stubs, such as Dr. Blofeld has frequently done, should cite a reliable source to verify each one.  This is different from a naive editor creating a stub about his hometown, as his first edit. Many times I have spent hours referencing such an article when I am on "new article patrol," rather than just tagging it as unreferenced. The quality and reputation of Wikipedia diminish when it gains thousands of unreferenced stubs, some of which may be mistakes or hoaxes. The time of wikignomes is better spent helping new editors get their articles referenced, than following a seasoned editor around and trying to determine where he got his information for a stub. Is a "ricochet reference" acceptable? If the Spanish Wikipedia cites a reliable sounding source for a fact, is it acceptable to just copy that ref and insert in the article in this Wikipedia, or is the editor expected to actually have checked and verified the reference? Is there a way of copying the reference (could also be from a different article in the English Wikipedia) and noting that the reference cited has not actually been viewed? When a non-English article is translated, that is likely to happen, since the foreign editor may have had access to paper references not available in the English speaking editor's country. Edison (talk) 20:36, 1 November 2011 (UTC)

I agree Edison, new stubs should really contain one fact and one source standard procedure. @Karanacs do you think Watom Island, Urara Island, Ataliklikun Bay, Ningi Chiefdom, Buta Territory are useless stubs or do you see them as a positive move towards covering poorly documented parts of the world and addressing systematic bias?♦ Dr. Blofeld  20:37, 1 November 2011 (UTC)


 * I think very minimal stubs could be ok but they shouldn't contain mistakes or to be misleading. Also even minimal stub should have an infobox with the most important information (length, mouth, country - for rivers; population, coordinates, administration subjects - for settlements). We should keep wikipedia as a source of information but not as a copy of google maps. Hugo.arg (talk) 20:51, 1 November 2011 (UTC)
 * Dr Blofield, the examples you listed are, in my opinion, decent stubs. They contain more information than "this place exists".  I don't see the point in sub-stubs that establish that something exists without telling us anything at all about them.  In my opinion, having lots of one-line stubs on a distant geographical area is only giving lip service to the idea of countering bias.  Is it better to have 1000 articles, each containing 10 words, so that we now have 10,000 words on this topic, or to have 10 articles with 1,000 words each, so that we have some depth to the topic?  Is it really bias to not have articles on the English wikipedia on topics where sources cannot be found in English to do more than verify existance?   Karanacs (talk) 21:36, 1 November 2011 (UTC)
 * Non-English sources are just as acceptable as English sources - see WP:NONENG. Calliopejen1 (talk) 21:56, 1 November 2011 (UTC)
 * Agreed that actually one line stubs untouched for two three years illuminate the sytematic bias problem by exisitng and remaining untouched. But I get exasperated at times at our ignorance of real notable subjects which should have full articles by now that occasionally I resort to auto drill if there are too many to consider creating slowly one at a time.♦ Dr. Blofeld  21:44, 1 November 2011 (UTC)

There should be no limit to how many stubs we can create. If I [we] need to destroy all the red links by creating every village in China, I will do so at a reasonable speed. We are here to build an encyclopedia, not to finish it. I rest my case! Jaguar (talk) 21:11, 1 November 2011 (UTC)

If you look at the new pages right you'll find worse articles than stub I created which are poorly formatted, unsourced, lacking basic wikification/categories. At least my measliest stubs have the "infrastructure" in place. Its a big problem that we don't have enough editors to sort out all of the new ones coming in. Helmipuuro for instance is unsourced but clearly looks notable but are we to reject it for not having sources? And how many newish editors know how the referencing works? I didn't for quite some time.

The way I see it is that we are here to provide the most comprehensive encyclopedia we can possibly create and that ignoring 700 rivers of some province of a country is a wiki sin! Especially if the article equivalent on another wikipedia is very developed and sourced. In my view the article existing at least shows it as been highlighted as being notable, even if initally lacking in content. ♦ Dr. Blofeld  21:52, 1 November 2011 (UTC)
 * Just dropping by to say I oppose any attempt whatsoever to create a minimum stub size. Assuming that a stub is not totally empty, it provides information to our users. (Reader: "Oh, Xtrynyr is located in Ruritania.") Tiny stubs are sometimes created by clueless newbies--it's no use to delete their (meager, but marginally helpful) contributions. Tiny stubs are also often created by users like Dr. Blofeld, who provide the correct formatting for future contributions. That way, instead of some totally unformatted, uncategorized article created by a Ruritanian trying to write an article on their town, we'll get something that at least in some category framework and properly formatted. The perennial debate about whether red links or poor-quality blue links do the best at motivating content creation is the only possible reason I could see to impose a minimum stub size, but until some sort of data on this topic is obtained, it would make no sense to remove useful (marginally useful, but still useful) content from the encyclopedia based on unfounded speculation. Minimum stub sizes and referencing requirements are also barriers to entry to new users, and could be demoralizing if works in progress were to be deleted. Calliopejen1 (talk) 22:04, 1 November 2011 (UTC)

In regards to myself I only create unsourced stubs on topics intended to be directly transferred from another wikipedia. I have proposed a User:Transwikibot which uses google translate to auto generate articles in our wikipedia space and once checked/proof read and a source or two added they can simply be moved into the mainspace. I would strongly urge people here to support me on this as you'd no longer see the pathetic attempts to transfer content but a system in which more fuller articles could be create relatively quickly piece by piece. Of course some translations i certian languages are better than others but if we had a bot creating an english equivalent of eveyr missing article on another wikipedia in our work space we would be much more organized. I think most people here grossly underestimate the value of missing articles on other wikipedias. I want WP:Intertranswiki to be much more organized and constructive and to have the ability to generate articles more fully first time with minimum effort. That's one of the key problems in this, is sheer mass of missing content and amount of time. We desperately need something powerful to get us organized.♦ Dr. Blofeld  22:08, 1 November 2011 (UTC)
 * I totally agree, I got warned by a sysop to create articles with at least one reference, which I have been doing now. There shouldn't be a limit to the number of words/byes that a stub should have, a stub is ready to be expanded anytime and almost all of them are notable enough especially if they have been transferred from foreign Wikipedias or if they are based on real places. Jaguar (talk) 22:12, 1 November 2011 (UTC)

I think the point of the discussions that took place elsewhere, which is being entirely missed here is not that what you guys are doing/want to do is "wrong", just that your priorities are deeply misplaced. Also see my comments at Jimbo's page.  Volunteer Marek  23:40, 1 November 2011 (UTC)


 * I think that the minimum size for a stub is one sentence. Even if that one sentence is "next to nothing, e.g. 'Xtrynyr is a community in Ruritania'," that first sentence is what many of our editors actually want to know.
 * It happens that I wouldn't mass-create such stubs; being a mergeist, I'd create a list or sections in an article instead. But eventually both need to exist, so you won't find me complaining about the person who's doing the other half of the work.
 * The only restriction I might put on mass stub creation is that if you're creating more than  at a time, then you must add both a category and a citation to a reliable source (which need not be an WP:Inline citation; a WP:General reference is good enough), ideally in the first draft (mostly to save the rest of us from trouble caused by the occasional competence-challenged CSD tagger). WhatamIdoing (talk) 00:44, 2 November 2011 (UTC)

Random break
The purpose of Wikipedia is to provide useful and verifiable information to readers in an accessible form. The question is whether the WP:Stub guideline should explicitly say that stubs should give some useful information and provide at least one source, and that stubs that have no useful information and/or do not quote any source should be "deprecated". My view is that such stubs do not help readers or editors. The comment right at the start of this discussion from is hard to dispute: "Such pages may be eligible for speedy deletion under WP:CSD". The question is really whether the WP:Stub guideline should restate policy, or at least I think it is. There is no hurry at all, but perhaps at some point a straw poll would be useful. Aymatth2 (talk) 02:00, 2 November 2011 (UTC)
 * A3 does not apply to stubs with any meaningful content. A3 is intended for articles with just infoboxes, external links, or a rephrasing of the title. Alpha_Quadrant    (talk)  04:33, 2 November 2011 (UTC)
 * (ec)If I start a stub on the number 56334956 is that notable? I can put in some "meaningful content" in there, as in "56334956 is the natural number between 56334955 and 56334957" (and that's it). I could maybe even put in some kind of Math template and an infobox (with a bit of a stretch). And hell, "sourcing" this won't be that hard either (I'm sure I can find some statistics textbook which lists it in its random numbers table ;)) On that note, it seems to me that the Category:Integers gives up too easily (around 301 or so). There is a lot, like an infinity, of them missing. Someone should get going on that.   Volunteer Marek 


 * Are we agreed that "X is a species of Y" or "X is a comet" or "X is a Y in Z" articles are minimally acceptable, (if not admirable,) so long as they have at least one reliable source, to satisfy verifiability? On random article patrol, I often find things like"Xarfax is an island in the Adriatic Sea," "Flamflim is Iceland's leading hiphop band" or "The Upchuck is a species of butterfly, Nymphalidae Danaini Vomitus." I spend countless hours which could be better spent in other ways improving the encyclopedia, searching fruitlessly for references to confirm the dubious claim. I cannot prove the negative: that no reliable sources exist. An experienced editor should cite the reliable source he used in creating the article. Dr. Blofeld proposes transwiki-ing articles, which is not unreasonable, but I have concerns of verifiability and reliable sourcing, since this Wikipedia has definitely had bogus references in many articles. If a German Wikipedian cited a book which may or may not exist, is it acceptable to duplicate that ref in the English Wikipedia without any editor of this Wikipedia having retrieved it from an online source, or eyeballed a paper copy of it? Would a 'pedia editor lie? YES! Editors have claimed that refs stated things they do not say. and some hoaxers have even cited false paper references. We lose credibility when we allow hoaxers or spin doctors to manipulate us into having articles lacking reliable and verifiable sourcing. Edison (talk) 05:12, 2 November 2011 (UTC)
 * Are we agreed that... - again, this is completely missing the point.  Volunteer Marek   05:17, 2 November 2011 (UTC)
 * Your point, maybe, though it has not been clearly stated. Your presentation both on Jimbo's page and here is unclear and rambling. Edison (talk) 05:43, 2 November 2011 (UTC)
 * Agreed, Marek stop rambling on!!♦ Dr. Blofeld  09:10, 2 November 2011 (UTC)
 * Dr. Blofeld, I suspect that my "rambling" generates more value added to the encyclopedia than all your mass-created stubs put together.  Volunteer Marek   17:24, 2 November 2011 (UTC)
 * Speaking of unclear statements "Your point, maybe, though it has not been clearly stated." does not even make grammatical sense. Let me rephrase. Unclear statements though yours are maybe are somehow. I don't think it's my presentation that is unclear here. Sure, go out there and create some stubs.  Volunteer Marek   06:39, 2 November 2011 (UTC)
 * Marek, you are one strange fellow. You talk in riddles and seem to like confusing things and getting your tongue in a twist. Nobody cares what you say, and that goes for Jimbo who likely scans over your ramblings to read constructive comments!.♦ Dr. Blofeld  18:46, 2 November 2011 (UTC)
 * Well, Dr., you're a strange fellow yourself. For someone who "doesn't care what I say" you sure get huffy (up to and including removing my comments from talk pages, which is a no-no). I wasn't expecting that anything but "Stubs good!" or "Stubs bad!" would be taken as "confusing" by some. And I didn't know you had a psychic link with Jimbo which lets you know how he reads the comments on his page. Are you sure you're not over-reaching there and projecting your innermost hopes on the innocent man? Take care.   Volunteer Marek   18:51, 2 November 2011 (UTC)
 * I wouldn't say there is anything wrong with creating stubs? It's merely red link destroying and it has to be done to expand the content of Wikipedia. Stubs are not always stubs - I created 2011 England riots and Operation Ellamy a couple of hours after they were announced. They have both made the front page and are massive. Jaguar (talk) 18:34, 2 November 2011 (UTC)


 * As I already said numerous times, there's nothing "wrong" per se with mass creating stubs or "red link destroying" (I can actually can think of somethings - like the fact that a red link exists for a good reason and you're taking away a signal to others who might create a REAL article). And of course pretty much every article starts as a stub, so it's not a surprise that something like 2011 England riots winds up being vastly improved. But for every stub that became an FA or GA I can show you a few dozen that have languished as stubs since their creation three or four years ago, with not a single(ok maybe one) meaningful edit to them. Ergo, "red link destroying" and "mass creating stubs" is NOT "content creation". It's a notch above spamming. Now, because it is a "notch above" it may very well be within Wikipedia policy. But if you're looking to really improve the encyclopedia than rather than mass creating stubs that will just sit there for the next five years, how about going to the library, getting a book or two, reading them, sitting down, writing, referencing and improving some already existing long forgotten stub. Oh yeah, that's like... real work. And your edit count doesn't go up all that much. Nevermind.  Volunteer Marek   18:47, 2 November 2011 (UTC)
 * I understand your point however I'm not interested in my edit count. I've got more important things to do such as some coursework and revising for exams than going to a library - I'm not saying that's too much effort, I'm just saying that there is little point in doing that because after all it is going to be hard trying to find material for a Chinese village in the middle of nowhere. I do see your point, and I am a good copy editor and I am interested in content, but I am also interested in getting rid of all these masses of red links even if they all have a reference for each. Jaguar (talk) 20:17, 2 November 2011 (UTC)


 * Minimum stub-size is a non-arguement. It either meets the GNG or it doesn't. Is a stub with 20 words OK? What if it was only 19 long, for example? If it has no context, then the speedy deletion becomes applicable.  Lugnuts  (talk) 08:16, 2 November 2011 (UTC)

I don't think there should be a minimum size. I do think we can make a requirement that batch creation of stubs should meet some minimal standards, like having at least one reliable source (not a foreign wikipedia version or other wikiproject). And we can also wonder why identical one-line stubs (whether sourced or not) like X is a river in Y can not be more efficiently be grouped in a list (or number of lists), "list of rivers in Y", with redirects from the individual articles. It seems to me to be a lot more reader-friendly to group such clearly related info, instead of having so many articles almost entirely void of meaningful info. Fram (talk) 09:39, 2 November 2011 (UTC)

"And we can also wonder why identical one-line stubs (whether sourced or not) like X is a river in Y can not be more efficiently be grouped in a list (or number of lists), "list of rivers in Y", with redirects from the individual articles. " Well the answer is simple to that one, many of the river articles have full content article son the other wiki which is intended to be translated. Given that we are not paper and space it not an issue, it would be more productive to fully translate.♦ Dr. Blofeld  10:08, 2 November 2011 (UTC)


 * And nothing stops you or anyone to change the redirect into an article at the moment that this translation is done. Your reply does not provide a reason against the preference for a list instead of identical microstubs. Fram (talk) 10:40, 2 November 2011 (UTC)

You mentioned Aspen (Botkyrka Municipality) ‎. Well its better off having its own article as the vast majority of the others are.♦ Dr. Blofeld  11:59, 2 November 2011 (UTC)

As far as this discussion is in effect a proposal to require at least one source for a stub, I'd like to point you all to Village_pump_(proposals)/Archive_75, a proposal from July 2011 that failed after a good deal of community discussion. No use beating a dead horse here on a relatively obscure talk page, where this proposal has already failed after a broader discussion. Calliopejen1 (talk) 14:43, 2 November 2011 (UTC)


 * Not exactly. This is a proposal to expand the guideline so it "deprecates" creation of stubs that provide no useful information and/or include no sources. Basically: "we much prefer that stubs have at least some information and quote at least one source". This is not change in policy but in the guideline. Aymatth2 (talk) 15:14, 2 November 2011 (UTC)

Perhaps some attention should be given to WP:MASSCREATION, which is part of a policy. Basically, there is no difference between rapidly creating 50 microstubs with "subst:pagename is a river in Poland" and what is described in that bot policy. So why are these creations not restricted by that same policy? Fram (talk) 15:19, 2 November 2011 (UTC)


 * This proposal has nothing to do with the way in which articles are created. It would apply to stubs created manually, semi-automatically or automatically. WP:MASSCREATION says the last two categories need approval, but says nothing about their content.  This proposal is to refine the guideline about stub content to say:
 * "As a rule, a stub should provide some information about the subject that will be useful to readers. It should also give at least one source for the information provided. Creation of stubs that provide no useful information and/or include no sources is deprecated"
 * Note the terms "As a rule" and "is deprecated". The proposed guideline change does not require that all stubs have useful information and cite a source. It recognizes that there will be exceptions, but recommends that in most cases some useful information be included with a source. Aymatth2 (talk) 16:43, 2 November 2011 (UTC)
 * Two thoughts, Aymatth2. (1) Regardless whether I support or oppose your propsoed guideline, I'd suggest that instead of "deprecated" you should have "discouraged" or similar language; "deprecated" would distract the reader with questions like "you mean, we could do this -- why the change?" or "what does deprecate mean in this instance?" (2) Your proposal doesn't really resolve this disagreement, beyond encouraging the use of sources. What I see in this discussion is that all concerned parties disagree on exactly how much information "will be useful to readers": we have people above arguing that "X is a river in Y" is sufficiently enough information to be useful to our readers. (And responding to their assertions with language along the lines of "That's not right" won't get us to a concensus on the matter. ;) -- llywrch (talk) 17:34, 2 November 2011 (UTC)
 * I agree with both points, llywrch. "Discouraged" is a better word. And the proposal does not fully resolve the issue. It expresses a preference for useful information backed up by sources, which should not be controversial. How much is enough to be useful? I would not attempt to define that. But a guideline does not have to be legalistically rigorous to be useful. Expressing a general preference, even if bit vague, is presumably better than nothing. Aymatth2 (talk) 18:06, 2 November 2011 (UTC)


 * IMO the barest 'x is a y in z' is OK and provides enough context. But I'd support something here along the lines of 'a reliable source is strongly recommended.' As to whether the ref has been read. There is a Assume Good Faith issue here, when it comes to articles from other language Wikis. EN-WP editors do this by default all the time - whenever someone copyedits an article with offline sources they haven't read, or an article translated from another Wiki, or supports an FA, GA, or DYK without having read and understood every single word in the sources, they are in effect affirming their trust in the info. Novickas (talk) 20:51, 2 November 2011 (UTC)
 * Hi. I just noticed this conversation and wanted to voice my opinion that I agree with some of the above users about that there should be a requirement about some external source. This could be at minimum a hyperlink within single brackets, and is a better solution than having "this article has less than X words, it must be deleted" mentality. If the article is really short (as in less than a paragraph or so) and lacks any citations of any kind, then it should be deleted. This should serve as a springboard for anyone who wants to further expand the article. Best, Jessemv (talk) 06:10, 3 November 2011 (UTC)


 * There is some support above for collecting linked stubs together as lists. Indeed, it makes sense for a number of topics to have a list article or set index article which compliments the articles on the individual items in the list, regardless of the length of the individual articles, so creating such a list at any time is desirable.
 * I think the question here is not should we have information on all the rivers in Vlasticnovia, or all the episodes of Porky and Butbum, or all the beers made by Pisshead Brewery, or all the stations on the Random Valley Line, or all the players in Awesome Football Team, but where should we place that information where it is most useful for our readers? And where we should place it would depend largely on the amount of information we have. If we have little more than a directory listing, "Foo is part of Foo", then it might be more useful to have that information in context - either as part of a parent article or a list or set index article. Having the information in context tells the reader more as the reader can see the set and the relationships, and it is easier to scan and access. If the information is contained in a parent or list article, and a reader clicks on a link to be given the same information in a stub, then that stub has simply created frustration.
 * If the information is already in Wikipedia, then it should not be split out into a standalone article until it either provides more information than is in the parent article, or the amount of information in the parent article is so large it can be reduced per WP:Summary style and a new article created.
 * If the information doesn't already exist on Wikipedia consideration should be given as to where it is best placed - as a standalone article or as part of a parent or list article, or both.
 * I would be hesitant to put too many limitations on creating a new article, as articles may develop from the most unpromising beginnings; however, if an article has been around for a little while (a week? a month?) and has not grown, then serious consideration should be given to merging the content into a parent or list article if possible.
 * It might be appropriate to list this discussion on CENT to get more opinions.  SilkTork   ✔Tea time  02:26, 9 November 2011 (UTC)
 * I generally agree with the above. The irritation factor is what mostly concerns me - readers getting to a stub that tells them nothing new. But before putting this on CENT, it is worth planning how to avoid a confused and inconclusive rehash of fixed and incompatible positions. How should the discussion should be structured and facilitated? To me there are a series of ideas here:
 * Should provide some useful information
 * Should say more than the parent article
 * Should have at least one source
 * May be better in a parent rather than stand-alone if there is not much content
 * Should be merged into a parent after a while if it has not grown
 * All of these are, I think, advice rather than rules. But have there been any cases of multiple-part recommendations being successfully taken to a conclusion? Aymatth2 (talk) 02:52, 9 November 2011 (UTC)

Proposed wordings
See discussions above on concerns regarding the usefulness of directory style or very short stubs. Aymatth2 has proposed some new wording (#1) and I have added three more:-



Please indicate if you support or oppose any or all of the suggestions. Further suggestions and amendments are invited and welcome.  SilkTork   ✔Tea time  02:37, 9 November 2011 (UTC)
 * I think stubs are the core of Wikipedia. Much of our content is composed of stubs. Stubs can be very useful, too. It makes information easier to find, for one. It also makes someone think, "Hey, I can add information to this article". If a topic is covered in a list, most readers won't be inclined to think that they should (or could) add more information about it. I agree that stubs should present more information than "X is a Y", but often, that information can be in an infobox, and possibly uncited. We shouldn't ban stubs because they are unsourced&mdash;we should find sources instead. I also agree that forking articles into stubs is rather silly, but I don't think we need an arbitrary time limit for redirecting stubs. If someone wants to redirect a stub, they can do so; if someone else disagrees, they can revert. Then a discussion can be held. Every stub is different, so we don't need a bureaucratic rule that adds another layer of complexity to the BRD process. If anything, it either just delays an inevitable revert and discussion, or delays an uncontested redirection. / ƒETCH COMMS  /  02:56, 9 November 2011 (UTC)


 * This whole discussion seems to be predicated on the assumption that "Xtrynyr is a community in Ruritania" doesn't impart any useful information, when it self evidently does impart what is probably the most important peice of information that readers will be looking for when they come across the name "Xtrynyr" in a book or newspaper and want to find out what it is. Phil Bridger (talk) 14:21, 9 November 2011 (UTC)
 * Support 1, 2, and 3. I think the wording is good, but perhaps "deprecated" is not the best word. How about "not appropriate"? On another point, I think we should avoid instruction creep on when to redirect - why 7 days? Why not 2 days or 30 days? Each stub is different, after all.bobrayner (talk) 16:26, 9 November 2011 (UTC)
 * I'd support 1, but we already have it. It's the speedy deletion criteria for lack of content or context. An article has to say what it's about. WP grows from tubs, mostly, and it is almost impossible to rule out something as non-expandable.  When I see a new article submitted in full at the first edit, I start suspecting either copyvio or commercial Press release. I see nothing wrong with a series of stubs: checking Diderot's encylopédie, he has thousands of one-line articles, as do almost all traditional .encyclopedias.  DGG ( talk ) 17:15, 9 November 2011 (UTC)


 * The wording should say "It should give at least one reliable source," not just "It should give at least one source." For instance, the existence of an article about the topic in a different language Wikipedia is "one source," but not a sufficient one, since it is no more a reliable source than any other source "anyone can edit anonymously." It is unreasonable to assume that some other Wikipedia has no hoaxers or charlatans editing it, and to assume that sources referenced in the other Wikipedia can be relied on without our editor actually seeing them. Edison (talk) 17:00, 9 November 2011 (UTC)
 * Requiring that a stub have "useful" information is a very bad idea: who's going to decide what's useful or what's not useful? We shouldn't have such vague requirements.  Nyttend (talk) 01:42, 10 November 2011 (UTC)
 * Oppose all per instruction creep. We already have a CSD for truly empty articles, anything beyond that--in my view--imparts useful information. We also have a recent, large-scale RFC rejecting a one-source requirement on new articles. Yes, longer is always better, and more sources are always better, but this is common sense and doesn't need to be added to the rules as vague, non-mandatory recommendations. Calliopejen1 (talk) 14:00, 10 November 2011 (UTC)
 * Support... I hereby support anything that will get rid of the hundreds of thousands of tiny articles about run of the mill roads and obscure villages. Just hit "random article" a few times to see the incredible raft of unmaintainable crap we have. Gigs (talk) 20:19, 10 November 2011 (UTC)
 * Oppose all There is no reason to tolerate any article that does not include substantive information. This strikes me as a clear WP:Creep problem. That being said, there are no inherent problems with stubs - they represent our best opportunity to attract new editors willing to expand on a subject. A stub which can be expanded and improved is a much better starting point than asking a new editor to write an article from scratch. The more, the merrier.  Jim Miller  See me 21:06, 10 November 2011 (UTC)
 * Oppose all. Useless instruction creep that will mainly serve to male discussion more contentious. Wikipedia and its users are often well served by short, unvarnished articles conveying essential, unvarnished information. Hullaballoo Wolfowitz (talk) 19:54, 16 November 2011 (UTC)
 * Oppose all, just in case my !vote wasn't clear from my comment above. No coherent explanation has been given of why our current guidelines fail to support our mission of building an encyclopedia. These proposals would hinder that process by making the first step in creating articles much more difficult. Phil Bridger (talk) 21:11, 16 November 2011 (UTC)
 * Oppose all. Stubs are a useful stage in building an article, and as has been explained above, they do contain some useful information. Adding rules which try to get rid of stubs is both instruction creep and likely to discourage long-term expansion of topics which don't already have substantial articles. TheCatalyst31 Reaction•Creation 23:21, 16 November 2011 (UTC)
 * Oppose All I agree with the comment by Fetchcomms above. Many article do start out as stubs. Banning their creation is counterproductive. Adding guidelines for redirecting stubs is unnecessary instruction creep. Alpha_Quadrant    (talk)  19:19, 18 November 2011 (UTC)
 * Oppose all: If someone were to create a stub and bearing in mind that the stub could be a small village in the middle of err... Moldova, then the chances are that a tiny village in Moldova would not have any information. If a Moldavian reader who knows English could update that article, that would be fair. However these new proposals aren't that fair. Jaguar (talk) 20:52, 18 November 2011 (UTC)
 * Support with Edison's addition offered above, although I'd prefer seeing something even stronger. There has apparently been a long tradition of the creation of masses of such one-sentence substubs with no sources or clearly unacceptable sources. (I've seen a bunch of geographical articles lately, each of which cited Google Maps, of all things, as a sole source [with no link to the relevant map]. And when I checked, I found that not all of the place names actually appear on Google Maps, at any zoom level.) It's about time that this stopped. If someone wants to write an article about a place, let him or her do enough research to at least sustain a reasonable stub. Deor (talk) 22:32, 18 November 2011 (UTC)
 * Oppose all. This would do more harm than good by biting new users who will become long-term community members, we do far too much of that already. Thryduulf (talk) 10:11, 25 November 2011 (UTC)

I don't see a consensus for change emerging from this. People feel that we don't need any further guidance which might discourage the creation of stubs per se, and that existing guidelines and consensus are in place to allow the deletion or redirection of clearly inappropriate stubs. I will remove the listing from CENT.  SilkTork   ✔Tea time  10:58, 28 November 2011 (UTC)

Semi-protected edit request on 8 April 2022
The information is not correct. The cricket Association of Cambodia is not legitimate body of cricket in Cambodia. There is no national team in Cambodia. As per law of association in Cambodia the Association must be registered with Ministry of Interior Royal government of Cambodia. 43.226.13.8 (talk) 12:57, 8 April 2022 (UTC)
 * Red information icon with gradient background.svg Not done: this is the talk page for discussing improvements to the page Wikipedia:Stub. Please make your request at the talk page for the article concerned. ScottishFinnishRadish (talk) 13:59, 8 April 2022 (UTC)

Not everything is a stub
I'm finding that lately, a lot of people seem to think that "stub" means "literally any article that isn't FA". Like, look at Carol, Carl, Whoopi and Robin. That was tagged as a stub. What exactly is causing overzealous stub tagging like this? Should the entire stub system be overhauled? Ten Pound Hammer • (What did I screw up now?) 23:14, 25 May 2022 (UTC)


 * Perhaps that article was expanded and someone forgot to remove the stub tag. It's been marked as a stub since its very first edit, when the article was 2 sentences long. – Novem Linguae (talk) 23:34, 25 May 2022 (UTC)
 * That still doesn't change the fact that I'm finding "stubs" that are several pages long because no one ever bothers to remove the tag, or because they think "article isn't featured, therefore it's a stub by default". I've seen people add stub tags to articles several pages long. Ten Pound Hammer • (What did I screw up now?) 00:45, 26 May 2022 (UTC)
 * Then revert them, and drop an explanatory note on their talk page directing them to Stub. -- Red rose64 &#x1f339; (talk) 14:09, 26 May 2022 (UTC)

Double blank lines, again

 * "It is usually desirable to leave two blank lines between the first stub template and whatever precedes it." WP:STUBSPACING

Since bots and WP:AWB are setup to automatically add that extra newline, removing it is largely useless, but most editors do not know about this guideline and instinctively remove one of them whenever they see two. Using two blank lines (ie three newlines) is generally frowned upon, not just on WP, and that for good reasons. If we can agree that the spacing above the first stub template is something we want, then let's fix that in CSS. The  selector is supported in all modern browsers. This works in Chrome 49:

.stub:first-of-type { margin-top: 2rem; }

To see it in action, go to an article with more than one stub templates (eg Solenopora) and add the CSS (in Google Chrome: Developer Tool --> Elements --> "+").

If this is not possible for some reason, I think we need to pick one of the two styles and stick with it. It makes little sense to allow bots/AWB to make this change en masse (that is there's consensus for two blank lines) while at the same time calling it "usually desirable" (consensus to use either). jonkerz ♠talk 16:21, 27 April 2016 (UTC)
 * Yes, we want the visual spacing; yes, CSS can handle this better today. We don't need to say "usually"; that was someones "I hate firm rules on Wikipedia" PoV pushing, and guidelines should not use wishy-washy wording like that without good reason, and provide an explanation/example of the case for variance, otherwise is just confuses editors and leads to disputes about interpretation.  — SMcCandlish ☺ ☏ ¢ ≽ʌⱷ҅ᴥⱷʌ≼  21:23, 27 April 2016 (UTC)
 * Here's what I wrote on this page : When there are no blank lines before the first stub template, I add one; where there are three or more, I reduce them to two. But if there are either one or two, I leave them alone. (it's still on this page, unarchived). Nobody has yet complained about me doing that, and so I still follow that practice. -- Red rose64 (talk) 11:18, 28 April 2016 (UTC)
 * Funny, I searched the archives but forgot to look this page... hidden in plain sight. Some previous discussions:
 * Wikipedia_talk:Stub/Archive_8 (2007)
 * Wikipedia_talk:Stub/Archive_11 (2009)
 * Wikipedia_talk:Stub/Archive_11 (2009)
 * Wikipedia_talk:Manual_of_Style/Layout/Archive_7 (2010)
 * Wikipedia_talk:Stub/Archive_14 (2011)
 * Wikipedia_talk:AutoEd (2015)
 * jonkerz ♠talk 13:54, 28 April 2016 (UTC)


 * The discussion in the previous archive never really concluded, but it seemed like the consensus was against double lines.  McLerristarr &#124;  Mclay1  12:58, 28 April 2016 (UTC)


 * I changed "It is usually desirable to leave two blank lines" to "Leave two blank lines" some time ago, since regardless of the eventual outcome of the above discussion about whether we want two blank lines or not, there is no rationale provided, no logical reason, and no excuse for providing wishy-washy, confusing, pseudo-advice that just begs the question. "It is usually desirable" indicates that there is some criterion for deciding whether or not the standard result is desirable or, for some reason, not desirable in a specific circumstance.  But this is simply not true.  There are no special circumstances outline by anyone in which we would want an inconsistent layout to be used in one particular article.  I'm restoring the edit, considering BRD to have already been satisfied quite some time ago. If anyone had a real reason for this pointless hand-waving verbiage, they would have provided it and backed it up long before this.  Either we should say to use two lines, or not; there is no case for saying "maybe" do it, without providing any guidance on when and when not to do it and for what reasons.  — SMcCandlish ☺ ☏ ¢ ≽ʌⱷ҅ᴥⱷʌ≼  08:19, 25 May 2016 (UTC)

Two blank lines may no longer be strictly needed since there are other mechanisms to achieve the same effect. However, leaving one blank line is still necessary. Many editors simply add new categories to the end of what they perceive as being the category list without noticing whether the last item on the list is actually a stub template. This makes manual hunting for stubs (in order to remove or sort them) and repositioning of them at the end of the category list a much slower task. For that reason, "Leave a blank line" seems like the optimal instruction. Grutness...wha?  01:45, 26 May 2016 (UTC)


 * Again, no-one can provide a valid reason on why there should be any blank lines. I've reverted SMcCandlish's bold edit, as the text has been like that for a long, long time, and changes to it need to be via a WP:CONSENSUS.  Lugnuts  Dick Laurent is dead 07:12, 26 May 2016 (UTC)
 * At least from 2008, from a quick check of the page history.  Lugnuts  Dick Laurent is dead 07:16, 26 May 2016 (UTC)
 * That's just WP:REVERTWARing to make a WP:POINT, and you have no real point to make, since this is covered at WP:CONTENTAGE. You cannot provide a valid  it should say something so pointless and editor-confusing, multiple editors object to it (see below as well, plus recent page history), zero editors have provided a rationale for that wording, this discussion has turned circular, it has been running just short of a month, ergo WP:BRD, which is just an essay and an optional process, is already satisfied.  Further discussion may determine whether we want to keep advising insertion of blank lines, to advise a different number of them, or to handle this some other way, e.g. with a CSS class.  Discussion is never going to arrive at a consensus to continue using meaningless, question-begging wording.  — SMcCandlish ☺ ☏ ¢ ≽ʌⱷ҅ᴥⱷʌ≼  08:53, 26 May 2016 (UTC)
 * Well you're the one being pointy/edit-warring, McCandlish. Discussion here is clear that there's no consensus on the spacing either, so that's been removed. Carry on with your disruption. And to add to this user's hypocrisy, he's shooting down WP:BRD as an essay, but using WP:CONTENTAGE for his lame argurement for edit-warring. Yes, you've guessed it, CONTENTAGE is an essay. Where's my pot and kettle?  Lugnuts  Dick Laurent is dead 10:58, 26 May 2016 (UTC)
 * Lugnuts, I find it interesting that you write "no-one can provide a valid reason on why there should be any blank lines" immediately underneath my explanation of valid reasons for why there should be blank lines. Please read what you're replying to before you reply! Grutness...<small style="color:#008822;">wha?  01:35, 27 May 2016 (UTC)
 * Your rationale is invalid. "This makes manual hunting for stubs ... ...a much slower task". I call bullshit on that. I've never had a problem finding the stub tag on an article. 06:38, 27 May 2016 (UTC)
 * And I call bullshit on your response. From personal experience I can definitely verify that it makes manual hunting and replacing a much slower task. I repeat -I have provided a valid reason why. If you find no difficulty, then you're lucky. For the rest of us, it makes the work harder. Note that PamD and Peter coxhead both state that the differentiation of stub templates from categories in this way is desirable. Grutness...<small style="color:#008822;">wha?  07:05, 27 May 2016 (UTC)
 * "I can definitely verify that it makes manual hunting and replacing a much slower task" - well blaming that for your lack of skills in editing is certainly an interesting rationale for keeping it. Not my fault you're not really up to doing a very straight forward task.  Lugnuts  Dick Laurent is dead 07:24, 27 May 2016 (UTC)
 * Just as it's not my fault that you prefer a personal attack to a reasoned rebuttal. Please stick to the subject at hand, rather than questioning whether I am up to doing a task. Grutness...<small style="color:#008822;">wha?  01:54, 29 May 2016 (UTC)
 * I'm not questioning if you can do a task, as that's already clear.  Lugnuts  Dick Laurent is dead 11:54, 31 May 2016 (UTC)


 * The phrase "it is usually desirable" raises the question "In what cases is it not desirable?", which is unanswered. The documentation would be improved if this vagueness was removed: just "Leave two blank lines". I have no strong views on one versus two blank lines. At present we need to campaign against the omission of any blank lines at all - too many articles come through with stub tagged onto the same line as the previous template, making it less easy to spot and stub-sort. Pam  D  07:50, 26 May 2016 (UTC)
 * I also find it interesting that Lugnuts throws around accusations of editwarring immediately after reverting, with no actual rationale, an edit made with a very, very clear rationale that no one can refute. And someone else restored that edit of mine. WP:BRD is not a weapon to use against other editors, it's a process which sometimes works, when everyone engages in it in good faith and reasonableness. Go actually read it, Lugnuts. It concludes with the clear observation that after discussion (and a month of it going nowhere is way more than enough) fails to produce a useful outcome, it is time again for bold action. It has been taken, other editors support it, zero editors have defended Lugnuts's insistence on including language that makes no sense, so I cannot see how this matter is anything but closed.  I strongly suggest we return to discussion of what the actual optimal  is: What do we want this segments of self-referential content to do, under what circumstances, and what is the best way to get that result? I.e., what will produce the lowest error/confusion rate?


 * Maybe there are different practices in different areas, but in my experience of editing, the standard practice is to leave two blank lines. The advantage is that it clearly picks out the stub template from the normal categories when editing, and in the viewed article differentiates real from "housekeeping" information. Peter coxhead (talk) 21:54, 26 May 2016 (UTC)
 * exactly. There needs to be at least one blank line to separate the stub templates from the categories, if only simply for the ease of editing and housekeeping. Grutness...<small style="color:#008822;">wha?  01:35, 27 May 2016 (UTC)
 * Looks like I'm being tag-teamed by the likes of McCandlish and his buddy Peter coxhead. Great!  Lugnuts  Dick Laurent is dead 06:36, 27 May 2016 (UTC)
 * "Tag-teamed"? Nice pun! Rather, though, it's that you're the one person who's decided that everyone else is out of step. So far in this argument I count five people in favour of leaving blank lines, two who made general comments which didn't indicate a preference one way or the other, and just you, Lugnuts, who sees anything wrong with there being blank lines. Grutness...<small style="color:#008822;">wha?  07:05, 27 May 2016 (UTC)
 * Well the stub-sorting clique sure showed me.  Lugnuts  Dick Laurent is dead 07:24, 27 May 2016 (UTC)
 * Lugnuts, think logically about this for a minute. Why would some imagined "tag-team" of stub-sorters want to make themselves more work by checking articles to maintain a gap between tags and categories? Surely if there is some "clique", it would be in their best interests not to care how many lines there are, or whether there are any at all. It wouldn't go out of its way to make more work for itself - that would defeat any possible purpose it might have. The only reason any editors would want to expend more effort is if they see a useful purpose to that effort. Which in this case, there is. It's no "clique" - it's just editors who all see good reason for a gap to be placed between categories and stub templates. Grutness...<small style="color:#008822;">wha?  01:51, 29 May 2016 (UTC)
 * Aaaiiieee! It's a  Or maybe Lugnuts needs to review WP:1AM. PS: It's hilarious someone thinks I'm part of a stub-sorting cabal, since I have not touched squat in that area in years (not since I was new and  thought there was a stub-sorting cabal, and got mad, then realized it was mostly poor documentation confusing people, so I rewrote it without changing anything substantive, everyone seemed to like it, and I moved on.  Heh.  I think that was in 2006 or so.  — SMcCandlish ☺ ☏ ¢ ≽ʌⱷ҅ᴥⱷʌ≼  02:00, 30 May 2016 (UTC)
 * Another essay from McCandlish. You sure do like them. You moved on? By crying to the admin who didn't do your page protection request four days after getting shot down? Ho ho.  Lugnuts  Dick Laurent is dead 11:52, 31 May 2016 (UTC)

I'm in favor of giving clear direction on this. I don't think that the leaving at least on blank line makes it easier to find the stub tag(s) is a bullshit argument. I'd like it if we could make things look nice and consistent with 0, 1 or 2 blank lines. Maybe there's some template magic that can achieve that and make this discussion a little less important. Not that it's actually all that important as things stand :) ~Kvng (talk) 17:13, 27 May 2016 (UTC)
 * Sorry, just read from the beginning. If the templates and CSS is now taking care of this, let's toss the two-line recommendation, I haven't seen a good argument for that and there's no other similar formatting suggestions as far as I'm aware. Let's specify one blank line between stub template(s) and other stuff to set it off for editors. ~Kvng (talk) 17:50, 27 May 2016 (UTC)
 * I would certainly agree that the extra space in the rendered text is displayed via CSS, then the double line can be replaced by a single line. However, this hasn't been implemented, afaik. Peter coxhead (talk) 21:09, 27 May 2016 (UTC)

Two issues
There are two different issues involved here: Peter coxhead (talk) 21:20, 27 May 2016 (UTC)
 * 1) Marking stub templates as a different "block" of wikitext from other parts of an article, particularly categories, for the benefit of . Other than, everyone else seems to be in agreement on this issue.
 * 2) Marking stub templates as clearly separate from the text of the article which appears above them, since they are "housekeeping", not content, the separation being for the benefit of . A double space in the wikitext does this, but the same effect could be achieved by CSS. I think there's a consensus that CSS is the way to go, after which the double blank line can be replaced by a single blank line. Or am I wrong about this second issue?
 * You're not wrong. I will add that I don't think anyone is up for editing all stubs to remove extra blank lines. We either need to get a bot to do this or we need to implement the template/CSS so that the page layout produced is the same whether there are 0, 1 or 2 blank lines preceding the stub template. ~Kvng (talk) 22:36, 27 May 2016 (UTC)
 * At Wikipedia talk:Stub/Archive 14 in my post of 16:57, 1 March 2011 (UTC) I suggested don't change explicit "two blank lines" to explicit "a blank line", change it to "either one or two blank lines". I have come up with some CSS which will give an increased top margin to the first stub template of a group, leaving the other members of the group alone:  You can test that by pasting it into Special:MyPage/common.css, and viewing an article with several stub templates but just one blank line, such as Dastarkhān. Try varying the first value from   to something else. -- Red rose64 (talk) 07:19, 28 May 2016 (UTC)
 * I agree - leaving a gap for readers is important, and is best served in CSS; leaving a gap for editors is also important, and can be served by one or more blank lines. Redrose's ancient talk post seems much more sensible than the hard-and-fast "must be two" or the frankly pointless "two in most circumstances" (has anyone pointed out any circumstances where blank lines are not "desirable"?) Grutness...<small style="color:#008822;">wha?  01:46, 29 May 2016 (UTC)
 * It may be worth looking into whether any of the "new" feature of HTML5 can be used here yet (things like the <aside ></aside> tag. It would be nice to semantically separate the housekeeping material at the code level. Marked up this way, one blank line might be enough for editors, and spacing at the reader level adjusted with CSS.  — SMcCandlish ☺ ☏ ¢ ≽ʌⱷ҅ᴥⱷʌ≼  02:00, 30 May 2016 (UTC)

Two blank lines, again
has added. I have traced the earliest form of that sentence to at 21:38, 21 April 2007 (UTC) by. It seems to have lost the last phrase at some point. -- Red rose64 &#x1f339; (talk) 13:11, 7 August 2022 (UTC)
 * Oh dear, a can of worms, reopened. Thanks, . &middot; &middot; &middot; Peter Southwood (talk): 14:31, 7 August 2022 (UTC)
 * I asked because of a request for a software fix at Page_Curation/Suggested_improvements, which does not seem to be a useful way to spend developer time. Cheers, &middot; &middot; &middot; Peter Southwood (talk): 14:50, 7 August 2022 (UTC)
 * I removed the following,, from the project page, as it think it can be resolved here. The instruction to have two blank lines preceding a stub notice is for aesthetic reasons. If there is only one blank line before the stub notice ln the wiki text, the stub notice is displayed immediately under any preceding nav template. It takes two blank lines in the wiki text to produce one blank line in the displayed page. See also the comment in Wikipedia talk:Stub/Archive 7, from 2007. - Donald Albury 16:30, 7 August 2022 (UTC)
 * I've added this explanation on the project page. If anyone thinks it is unnecessary, they can remove it. Donald Albury 16:46, 7 August 2022 (UTC)
 * I didn't see this discussion when I posted. I will note that it remains the case that the first blank line does not show in the rendered text after a nav template, but does show if there is no nav template. A lot of stubs do have nav templates. - Donald Albury 18:05, 7 August 2022 (UTC)
 * Yes. It's a long-standing technical problem the devs will likely never address.  — SMcCandlish ☏ ¢ 😼  05:56, 8 August 2022 (UTC)