Template talk:Nutshell/Archive 1

Archive 1

Overused

This template is being overused. Looking through the "what links here" I found it being used helpfully on WP:SOCK but it was sitting there and being totally useless on WP:NPA and WP:NOT. Don't use this when the article will not benefit from a one-line summary. Ashibaka tock 19:26, 13 January 2006 (UTC)

I agree with Ashibaka that this template is vastly overused. Many if not most of the summaries fail to capture the essence of the policies, and the summaries contribute to the policy bloat they were intended to address. The Uninvited Co., Inc. 21:40, 15 August 2006 (UTC)

Center text

Does anyone mind if I alter the template so the text is aligned to center? I think it looks especially wrong when the description is very short. - Drrngrvy 16:25, 25 April 2006 (UTC)

Tricky one - center-aligned looks bad when the text is long (two or more lines). Do you have an example of text shorter than half a line? Stevage 09:31, 1 June 2006 (UTC)

I think that left justification looks bad on multiple lines too. I hope noone minds that I was bold and changed it - along with the large picture size. Fresheneesz 22:38, 10 September 2006 (UTC)

I think multi-lined, centered text looks amateurish. It's poor design IMHO. Rfrisbie^talk 23:02, 10 September 2006 (UTC)

Now text alignment is a parameter. Rfrisbie^talk 23:46, 10 September 2006 (UTC)

Good call. Fresheneesz 04:44, 11 September 2006 (UTC)

Aw, nuts!

I should probably ask this some place else, but... what do people actually think of all the nutshells? One might argue they cause laziness and incomplete comprehension of policy, since in effect most policy pages cannot really be reduced to a single line. >Radiant< 17:17, 11 September 2006 (UTC)

Parsimony is a virtue. ;-) Rfrisbie^talk 17:49, 11 September 2006 (UTC)

• And brevity is... wit! - R.

Beyond that, I think the nutshell summaries allow someone to know what they're reading when they do read the rest. It sets the stage. Fresheneesz 22:18, 11 September 2006 (UTC)

I just said this on a particular page discussing the use of the template there but should have made the comment here because the criticism applies to all the "nutshell" templates.

The "policy in a nutshell" idea seemed like a good idea at the time but now that we've got more experience with it, I think they just clutter up the pages for little purpose. The best "policy in a nutshell" is the policy title. No original research is a good example. It's clear, succinct and tells me exactly what to expect from the rest of the page. The next level of detail should be in the opening paragraph. In most cases, the "nutshell" sentences were actually pulled from older versions of the opening paragraph. This infobox tries to fill a middle ground between the two. Because of that, it's inevitably vague and general. I don't think it adds anything to the reader's understanding of the page.

Frankly, I doubt that most people even read them. When they're laid out on the page, they just blur into the generic "this is official policy" infoboxes and get discounted as administrivia. With very few exceptions, I think the pages would be easier to read and understand if the "nutshell" statement were merged back into the opening paragraph of the policy. Rossami (talk) 05:35, 12 September 2006 (UTC)

By the way, I encourage anyone new to this debate to also review Template talk:Guideline one liner where this practice was first discussed. In my opinion, the initial objections have never been satisfactorily addressed. I'm ready to call this a failed experiment. Rossami (talk) 05:38, 12 September 2006 (UTC)

I have to say that I like them. I was the one who posted the question that Rossami made the original reply above to. I think they are useful, as long as they are simple, clear, and straight. Often when new users make a mistake, the reverting editor will point them to standard policies such as WP:NOT and WP:SPAM. Without the nutshells, some policy pages may seem overwhelming, confusing, or too boring to read. The nutshells are graphically more interesting than the rest of the page. They draw a user in and give them a quick summary that may either tell them what they need to know, or encourage them to read more. I think the nutshells should stay, but an effort should be made to make sure the summary is accurate and useful. -- Renesis (talk) 05:48, 12 September 2006 (UTC)

• That's precisely the point though, with the nutshells, people may (and in my experience, not infrequently do) draw the wrong conclusion. If a guideline can be summarized in a few words, the title suffices. If not, the nutshell won't suffice either. I concur with Rossami. >Radiant< 14:39, 12 September 2006 (UTC)

I agree that with Rossami and Radiant that the nutshellisms are (a) a source of visual clutter, (b) in general are poor summaries, and (c) are prone to being gamed. I also believe that where the content of the nutshellism is valuable, it should be used as the opening sentence or two of the policy page. There is no need to set it apart visually. The Uninvited Co., Inc. 23:26, 27 September 2006 (UTC)

I am not sure is this is the right place for this discussion, but let me add my 2 cents. I personally find nutshells very useful and visually appealing. When I first started learning policies, not that long ago, the nuts were very helpful to me to get a quick grasp of the highlights of each policy/guideline, and to some extent I still find them useful. I think we would lose this benefit if we forfeit this important tool. Crum375 23:40, 27 September 2006 (UTC)

• I should think that being visually appealing is not at all a goal for policy/guideline pages. I understand that people find them useful for learning policies, but the result seems to be that people misunderstand the policies. Crum, you seem to be opposing these things for no other reason than that "process wasn't followed" or "it wasn't properly discussed". On Wikipedia, those arguments aren't very convincing, and I'd hate to say this but it's quite possible that the nutshells are in part to blame for this misunderstanding on your part. >Radiant< 00:03, 28 September 2006 (UTC)

Radiant, I'll try to address your points. First, I think visual appeal is important, as it helps most people grasp a concept quicker if it's presented in a clear and concise visual way. It sure helped me.

Second, regarding process over action, I am no stickler to process per se, but I do like efficiency. I think it's more efficient discussing a big change in format that applies to multiple pages and reaching consensus prior to just wildly making changes. Nothing to do with process - just makes life easier on everyone, and will get us there quicker. If it's a small change, yes being bold is good. Oh, and I do read the full policy pages nowadays ;^) Crum375 00:14, 28 September 2006 (UTC)

No, it is usually more efficient to just do it. Only a minor fraction of things that are just done are possibly objectionable. This is, as you say, only a visual formatting change, not major. —Centrx→talk • 05:54, 28 September 2006 (UTC)

I really don't like the nutshells. When I see one on a Wikipedia guideline page, I feel like the page is telling me: "This guideline isn't written well enough to be clear, so here's what the guideline is trying to say." Plus, the infobox that the nutshell is in pushes the rest of the page down, making it an even greater distance from the top of the page to any actual meaningful content. In my opinion, nutshells should be done away with, and the "nutshell" itself should be made the first sentence of the guideline. - Brian Kendig 15:30, 18 January 2007 (UTC)

As I noted elsewhere, the nutshells are part of a concerted attempt to make WP user friendly and graphically pleasing, especially to the newer users. Many new users (such as myself when I was one) are intimidated when they see a long complex dissertation, when all they want is to understand the overall scope and key concepts of a policy or guideline. The introduction or the table of contents are the next best thing to the nutshell, but a user never feels comfortable just skimming those as they are not guaranteed to deliver all the essential points, which could conceivably could be embedded deeper in the text. OTOH, following the nut icon is an easy way for a novice to get an overall feel for what our policies and guidelines are about and they user can be confident that the nuts cover, by definition, all the essential elements. If they need more information, the complete article is always there. I think that getting new users to easily grasp the core concepts of our policies is a worthwhile goal, that justifies moving the intro sentence down a little on the page, requiring just a bit of scrolling. Crum375 23:40, 18 January 2007 (UTC)

The nutshell is also an important learning tool. By providing a summary of the content beforehand, the reader is able to more easily assimilate the detailed information that follows, because it has already been given context. It also helps people scan through the various policy documents to find the one they need.Dhaluza 02:43, 19 January 2007 (UTC)

That's what the introduction is for. —Centrx→talk • 18:36, 20 January 2007 (UTC)

I agree with your goals, but I still don't like the nutshells. In my opinion they make Wikipedia more intimidating, by adding more ugly infobox clutter to the top of the guideline page, and by implicitly suggesting that the guideline is too confusing to present its main idea concisely on its own. The opening paragraph of the guideline is supposed to provide a summary of its scope and key concepts, and if the opening paragraph doesn't do a good enough job of this, then it should be rewritten. Conversely: is there any situation in which the very first sentence of a guideline should not be the same exact thing as in the nutshell? - Brian Kendig 05:40, 19 January 2007 (UTC)

As several of us have commented above, we concede that the nutshells are well-intentioned but feel that they fail in their goal. While intended to make the page easier to read, they actually make it harder to read and understand. Nutshells should be deprecated in favor of better page-naming and better section headers and better introductory paragraphs. Rossami (talk) 14:10, 19 January 2007 (UTC)

The topic is unfortunately spread out over a number of threads here, plus various archived Talk pages, so there is redundancy and overlap. The bottom line is that there are at least 2 schools of thought: those who think that the nut is an important asset (like myself), and those who don't. I suggest you read all the related threads here, as they cover the pros and cons fairly well. Like anything else on WP, this issue, which applies to all policies and guidelines, should be decided by consensus. Crum375 21:18, 19 January 2007 (UTC)

The so-called "schools of thought" are not that complicated. Simply, you think that the nutshells are a "graphically appealing" summary and others think that the summary belongs in the introduction and that "graphical appeal" is for children, not encyclopedia editors. —Centrx→talk • 18:39, 20 January 2007 (UTC)

Perhaps so, but aren't we all children at heart? Crum375 18:49, 20 January 2007 (UTC)

No. Rossami (talk)

Well, on a more serious note then, I think the novice editors who first encounter all the complex policy/guideline pages, who want to do a quick pass to get the essence of all that complexity before digging deeper, appreciate having a quick and simple guide. I know I did when I was a novice, as I do when I have a quick and simple guide included with a heavy and complex manual for some new complicated device. Crum375 01:00, 21 January 2007 (UTC)

Not just for novices, it can also help more experienced users find the right document. The titles are descriptive, but if you have confused one with another, the nutshell will make it faster and easier to find the right document. And it is complementary with the intro. The title is a very brief statement (clause), the nutshell is a summary (sentence), and the intro is a more detailed statement (paragraph). This is building from simple to more complex, an effective teaching technique.Dhaluza 01:36, 21 January 2007 (UTC)

The opening paragraph's purpose is to be this "quick and simple guide" of which you speak. If the opening paragraph isn't serving this purpose, then it needs to be rewritten. We don't need the purpose of a guideline to be expressed three times in a row (its title, its nutshell, and its opening paragraph). Can you think of any situation where the first sentence of the first paragraph should not, or can not, explain the guideline in a nutshell? - Brian Kendig 23:29, 21 January 2007 (UTC)

We have been through these arguments many times before. Unfortunately they are spread out over many threads. To answer your point, the purpose of the nut is to allow a new user a quick understanding of the essence of a complex policy or guideline. Even if the intro paragraph is re-written and improved 1000 times, it will not change the simple fact that a new user coming to a new complex page does not trust the intro to really encompass all the crucial points, while the nut is by definition the essence. The new user may believe that the intro could simply be an opening salvo of a long dissertation, while s/he assumes that the writers have made a special attempt to summarize all the essential elements in the nutshell. This gives the new user more confidence that a quick read of the nutshell will allow him/her to come away with an initial and basic understanding of what this page is about, perhaps to be followed at a later point by reading the intro, scanning the TOC, and so on. The goal is to make WP friendlier to new users and make it easier for them to learn the ropes quickly. Crum375 23:44, 21 January 2007 (UTC)

Good point. So, in a nutshell, the template box must summarize the article, while the opening paragraph may or may not. Dhaluza 01:41, 22 January 2007 (UTC)

"The purpose of the nut is to allow ... a quick understanding of the essence of a complex policy or guideline." That's also the purpose of the opening paragraph. "A new user coming to a new complex page does not trust the intro to really encompass all the crucial points." Even if I did agree with this statement, and even if it were our responsibility to second-guess what a reader might "trust" or "believe" about a guideline, a nutshell does not "encompass all the crucial points" - it's a nutshell. I still hold that rather than expecting that the opening paragraph will be insufficient and expecting editors to put together a good nutshell, it's far better to simply expect editors to put together a good opening paragraph. Nutshells add unsightly clutter to a page and make it look more complicated; we should be making the guidelines as straightforward as possible. Why don't regular Wikipedia articles have nutshells? How long will it be before people start creating mini-nutshells to summarize a particularly confusing nutshell? - Brian Kendig 03:29, 22 January 2007 (UTC)

I've been looking over some guideline pages, and in some cases, I actually like the nutshells. Wikipedia:Editing policy - "Improve pages wherever you can, and don't worry about leaving them imperfect." Wikipedia:Avoid weasel words - "Avoid 'some people say' statements without sources." Wikipedia:Be bold in updating pages - "If in doubt, fix it." Other pages, however, have nutshells which look more like first sentences. Wikipedia:External links - "Adding external links can be a service to our readers, but they should be kept to a minimum of those that are meritable, accessible and appropriate to the article." Wikipedia:No original research - "Articles may not contain any unpublished arguments, ideas, data, or theories; or any unpublished analysis or synthesis of published arguments, ideas, data, or theories that serves to advance a position." In trying to be all-encompassing, these nutshells end up failing as nutshells. I would be comfortable with nutshells if a requirement were added that they be pithy. If a nutshell reads like the first sentence of a guideline, then it should instead be the first sentence of the guideline. - Brian Kendig 15:06, 22 January 2007 (UTC)

While your "mini-nutshell" argument is a straw man, I agree with you that some of those you quote (EL, NOR) could use a lot of work. Considering that we don't have any "nutshell policy" (how ironic would that be?) there's no need to add a requirement "that they be pithy", but it would be a good idea to either just be bold and change it, or bring it up on the talk page and see what other people think it could be changed to. -- Renesis (talk) 17:02, 22 January 2007 (UTC)

WP:NPOV is another example of a bad nut. It just echo's the first sentence. I edited it this AM, but was reverted. Have a look at it, and try editing it, or restore my edits (or both).Dhaluza 23:10, 22 January 2007 (UTC)

I agree that it's a good example of a pointless nutshell. The opening paragraph is clear, succinct and appropriate. I don't think it can be improved on easily and certainly can't be improved upon in the nutshell. That is a page which would be improved by the simple removal of the nutshell. Rossami (talk) 23:30, 22 January 2007 (UTC)

I hope you can appreciate the irony of using NPOV to promote a POV on nutshells. Seriously though, look at it, and see that bit about other content is in the nut, but not in the first paragraph. So, the first sentence can be improved by moving it down.Dhaluza 23:42, 22 January 2007 (UTC)

The nutshells and intros serve a different purpose, and often a different audience. The current NPOV nut doesn't exactly echo the intro, as the intro has additional detail, and even if it did mirror it exactly, I don't see a problem with it. Our goal is to provide a 'follow the nut' quick learning path for new editors, akin to a pre-tutorial, where the new editor can quickly and efficiently be exposed to the essence of all policies and guidelines. That the nutshell happens to be close to the intro of a given page is inconsequential - the new editor may just move on to the next page anyway, while following the nut path. And if s/he does want more detail for a given page, s/he can read the intro (which even in your example has some minor additions), then scan the TOC, then read selected sections, etc. In any case, improving each and every nut should be discussed and performed at the specific page, as the issues are typically very specific to each page. Please see also other threads on this page which address this very issue - it seems we are going around in circles. Crum375 23:38, 22 January 2007 (UTC)

Another interesting case is WP:NAME. I cut down the nut, and it grew right back. Dhaluza 01:10, 23 January 2007 (UTC)

I think your current version there looks good. My own preference is to have the shortest possible nut that still covers the bare essentials, and this one seems to fit the bill. But in general I think specific nut discussions should be relegated to the respective Talk pages. Crum375 01:22, 23 January 2007 (UTC)

Proposed addition to the template:

Perhaps it ought to be made clear that nutshells are merely summaries of the policy, and are not binding. Otherwise, their use may create loopholes which allow circumvention of the policies themselves. --EngineerScotty 19:28, 26 September 2006 (UTC)

Personally I think most users are intelligent enough to understand the difference between a nut and a shell. But a tiny (non distracting) disclaimer is always possible, if we ever find someone who seriously thought the nutshell was the whole nut. Crum375 23:53, 27 September 2006 (UTC)

Adding extra text to the nutshell kind of defies the whole point. >Radiant< 00:03, 28 September 2006 (UTC)

I tend to agree. Crum375 00:15, 28 September 2006 (UTC)

The point of the nutshells is that any policy or guideline that can't be summed up in a clear sentence or two is probably ill-constructed. They should be useful both as an intro to new users and as a mnemonic to current users. A good nutshell is one you can read and not go too far wrong on acting on. This requires some remarkable feats of clear writing, but we have good writers.

People looking for loopholes will find them wherever they can. No rule can protect against stupidity and no rule can protect against malice. Trying will not work and will only make confusion for the clueful of good faith.

And I strongly question whether the talk page of the nutshell template is itself any place to determine a meaningful 'consensus' on them being a bad idea - David Gerard 11:13, 28 September 2006 (UTC)

Your point then boils down to that many policies are ill-constructed (or at least, way too complex). I tend to agree and would be happy to work on simplifying them. Complex policy (or enumerating badness, for instance) only encourages misunderstood formalism and wikilawyering vexlits. >Radiant< 11:15, 28 September 2006 (UTC)

Yes, I just came back here after thinking about it to say just that ;-) A good nutshell can help refocus a project page and be the guide in rewriting it - David Gerard 11:41, 28 September 2006 (UTC)

And conversely, a bad nutshell can derail a project page and cause its further erosion by people who misunderstood it. I see no reason to assume that all, or even most, nutshells are good ones. It would be better, instead of focusing on summaries, to rewrite the actual policy content and if necessary base a good nut on that - but for the best policy pages, the 'nutshell' is simply the title. >Radiant< 12:05, 28 September 2006 (UTC)

I personally find the nutshells a very useful reminder now, and a quick way to grasp the essence in the past. Are they perfect? nothing ever is. But I think minor tweaking can take care of most issues. One proposal maybe would be to set a hard limit of maximum words per nutshell. But I can see problems with that (some don't need the max, others may need more), so maybe just a strong admonition to keep words to minimum while expressing the essence would suffice. A nutshell writing guide, if not already in existence, may help too. Crum375 12:37, 28 September 2006 (UTC)

I fear more words on the subject may just turn into another attempt to define cluefulness for the clueless. Either people get it or they don't - David Gerard 15:24, 28 September 2006 (UTC)

True. But not all titles can be that long ;-) The nutshells came from Stevage asking me if summarising our vast and confusing pile of policy was a good idea. I said "no," he did it anyway, I saw that it was better than what was there before.

A good policy or guideline should be able to put well in one or two sentences. I think that doing so will help us in the quest to make our piles of process more usable. For great encyclopedia. - David Gerard 15:23, 28 September 2006 (UTC)

• I don't agree that Stevage's summaries were good overall. I'm sure that some pages can benefit from a nutshell (e.g. at BLP it is far from obvious from the title what the policy is about) but we shouldn't automatically use one everywhere (e.g. No Legal Threats is about as obvious as it's going to get, and we needn't insult the intelligence of our editors by adding a nutshell stating "do not make legal threats") and several of the existing ones need rewording or pruning. >Radiant< 15:53, 28 September 2006 (UTC)

Why not place those overviews instead in the first paragraph of the introduction rather than in an ignorable template clustered at the top? —Centrx→talk • 18:04, 28 September 2006 (UTC)

Centrx, those who want to 'ignore' will selectively ignore anything. I think we need to cater to two main categories of readers: those who are in a hurry and want a quick glipse of the essentials, and those who want to learn more deeply about the details. I think the nutshell format is ideal for the first kind - they will get the gist of the policy, and perhaps miss on the trees, but will at least see the forest. The second kind of readers will carefully read the intro, table of contents, and individual sections. Of course there are in-between cases - they will benefit from both approaches. As I have mentioned many times now, to me personally having the graphically crisp nutshell format was very helpful in the past as I was learning the ropes. I think other newcomers should also be able to benefit from this mechanism to get a quick and simple overview of each policy. Thanks, Crum375 18:16, 28 September 2006 (UTC)

• Centrx has a point though. People do tend to overlook templates, especially if a page has a lot of them. People who are in a hurry could plausibly read the first paragraph instead of the nutshell, which would be a good argument for placing the summary there. >Radiant< 18:22, 28 September 2006 (UTC)

I agree that if the page has too many busy templates, the nutshell could be hard to find or easy to miss. One important helper would be the nutshell's distinctive icon and format, that a person who is already aware of the nutshell mechanism in other policy articles would specifically look for when reading a new (to him/her) policy page. The other would be to cut down on template clutter to a bare minimum. Crum375 19:00, 28 September 2006 (UTC)

Why can't the hurried user read the first couple of sentences of the introduction? —Centrx→talk • 19:18, 28 September 2006 (UTC)

Speaking for myself, because I never know if an intro is really the whole story at a top level view, or just the beginning. Seeing a 'nutshell' format assures me that the authors believe that the nutshell words are a summary of the key salient points. Crum375 19:22, 28 September 2006 (UTC)

Then fix the intro and/or change the title of the page.
Putting the text in a template box may appeal to some readers. But I think that our growing experience with confused readers is evidence that more readers overlook them than are helped by them. Rossami (talk) 22:57, 28 September 2006 (UTC)

From my own experience again, I don't think that 'fixing the intro' would help any. After reading lots of articles in many diverse places I have my own expectations of things, and I just don't trust or expect the intro to cover all the important points in general, and see it more as an opening salvo, perhaps with the best or some keys points coming later. Therefore, as a new user, having the nutshell was a big helper for me, because I realized that here the authors kept the essence of their policy, so I can get a quick overview of the forest before delving into the trees, branches and leaves at a later time. Had I not such a convenience, since as I said I would not trust the intro, I would have had to scan the intro, read the TOC, look for what seemed to be important, randomly scan various sections, etc. - much harder work, taking much longer and with much more doubtful results. As I also noted earlier, in no case did I find the nutshell misleading. Now, this was me - maybe other newcomers are different. Crum375 23:22, 28 September 2006 (UTC)

If you don't trust the intro, why would you trust the nutshell? If the solution to misleading nutshells is to fix them[1], why isn't the solution to incomplete intros to fix them? —Centrx→talk • 23:35, 28 September 2006 (UTC)

Let me try again - I am sure it's my fault as a lousy communicator, so please bear with me. What I am trying to convey is that as a rule I don't trust that authors will always present the key points in the intro, since intro could mean, to some, 'opening remarks with the best to follow'. On the other hand, I do trust that they will put the key points inside a box called 'the policy in a nutshell', since the mandate there is crystal clear - try to put the essential ingredients inside the box. This to me, as a (supposed new) reader, gives a higher degree of confidence that in that box I will find the real goods versus the intro, where it's "nice to have" a summary but maybe it's just opening remarks. I simply assume, perhaps incorrectly, that many or even most newcomers will think like me and will "follow the nut" when they read new (to them) policy pages. Hopefully this makes it clearer. Crum375 00:40, 29 September 2006 (UTC)

To clarify, my point has nothing to do with the actual quality of the intro - hence 'fixing' it would be irrelevant - it's the mindset of the reader. Crum375 00:44, 29 September 2006 (UTC)

Nutshells on policy documents

I like the idea of nutshells on policy (and other Wikipedia) documents, but some of the arguments against their use are also persuasive. Essentially though, Wikipedia policy is (or should be) mostly common sense. Most of the time I think about what I would do if there were no guidelines. Then I check the guidelines. 99% of the time, my common sense agrees with the masses and masses of policy pages out there. But what about those people genuinely seeking guidance. Do the nutshells help them? I think they do, and I think nutshells should stay. Also, a massive reorgansiation and summarising of the policy and guideline pages is still long overdue. That is more important than debating nutshells! Carcharoth 15:49, 1 October 2006 (UTC)

• That's a reasonable point of view. I think nutshells are useful on some policy pages, but not all of them (some are not easily summarizable, or already summarized in the title). >Radiant< 20:35, 1 October 2006 (UTC)

Let's take a specific case: WP:NPOV

First of all, "nutshells" are necessary devices for conveying to a new person the 1) decisions and 2) conceptual material treated in the individual modules of any complex system.

Likewise, a well-written "nutshell" for the WP:NPOV page could be useful in conveying to new editors the 1) decisions and 2) conceptual material treated in the detailed text of the WP:NPOV page. However, the policy text of the WP:NPOV page is murky, ambiguous, and self-contradictory. And to remove the "nutshell" from the WP:NPOV page only makes the situation much worse.

In any rational approach to problem-solving, the "nutshell" is both a 1) design tool to make sure the policy text under it is self-consistent and a 2) "mnemonic formula" against which the reader can make sense of the detail. May I quote a sage: "A good nutshell can help refocus a project page and be the guide in rewriting it."

I give you an example of the use of "nutshells" to make clear the 1) decision points and 2) conceptual material of the detailed text that follows. Robert Boyd & Joan B. Silk (2003), in their How Humans Evolved, New York: W. W. Norton & Company, Inc., use a "nutshell" on almost every page. Here is an example from page 176.

• Males do not care for their offspring when 1) they can easily use their resources to acquire many additional matings or 2) when caring for their offspring would not appreciably increase the offspring's fitness.

And of course in the following page and a half of text, the authors explain that they are not talking about individual "males"; they are talking about the behavior of the median male in a population consisting of males and females, where the population has evolved over millennia under stable resource conditions. But that "nutshell" serves to 1) focus the questions and challenges of the reader accurately and to 2) provide a quality control device to make sure that the following text is self-consistent.

For all of the above reasons, this template should be retained and filled with clear and concise text. The Wikipedia community refuses to do the necessary work to make its policy pages clear and self-consistent. And removal of this template is just another work avoidance. What do you think we should do to rectify the murky, ambiguous, and self-contradictory text of WP:NPOV, just for starters? --Rednblu 18:13, 29 September 2006 (UTC)

• Regardless of nutshelling, a self-contradictory policy (or even two mutually contradicting policies) is bad and should be fixed. >Radiant< 18:32, 29 September 2006 (UTC)
• Why can't the first part of the introduction serve these purposes? —Centrx→talk • 21:23, 7 October 2006 (UTC)

An example of the confusion caused by these templates

Here is an excellent example of why these templates cause more harm than good. Users look at the "nutshell" and incorrectly assume that they know everything about the policy page. They make it far too easy for users to ignore the nuance and the qualifications which the policy page describes. Worse, they make it too easy for those lazy users to attempt to bludgeon other users rather than engaging in rational discourse.

(Note: If the section-link doesn't work, you might have to look in the page history to see the discussion. DRVs are traditionally blanked when the discussion is complete.) Rossami (talk) 20:57, 20 October 2006 (UTC)

Any tool can be mis-used or mis-applied. In most cases this is not a reason to toss the tool away. The nutshell allows new users to get up to speed quickly. Taking it away could force them to carefully read every word of a complex policy, OTOH it could just force them to scan quickly, pick up a couple of keywords, and leave with a bigger misimpression or misconception than a possibly oversimplified nutshell phrasing. In the issue in question, the nutshells are used to 'prove' that the AfD'd article deserves another chance. The editors are saying that the old AfD determined it was a 'howto' guide and non-encyclopedic, and it has not changed since, hence the conformance to the individual words of the policies does not magically convert it from a 'howto' to an encyclopedia article. I don't think the issue here is the oversimplification of the nutshells - the proponent could have used a lot more verbiage and still the same conclusion would have been reached. IMO, this is a case of WP:NOT a howto trumping the WP:V, WP:NOR, WP:N policies, not a reason to deprecate the nutshells. Crum375 21:18, 20 October 2006 (UTC)

They could simply read the introduction, which would serve the purpose of the nutshell, but not be a redundant fork. —Centrx→talk • 01:13, 27 October 2006 (UTC)

I think, as I mentioned before, the intro and the nutshell serve a different purpose. The nutshell is a simple visual tool to let someone in a real rush get a quick overview of the essential ingredients of the policy. OTOH, the intro's job is to present the policy by introducing the main issues that will be addressed. Yes, there are a lot of similarities, and one can benefit from the other, but their missions are not identical. For example, we can let the intro run a little longer, maybe use some more background or rationale, whereas the nutshell should always be short and sweet list of essential points. Also, for someone used to "following the nut trail", going quickly from policy to policy to quickly learn the ropes, it is very convenient and visually pleasing to follow the crispy nut templates. To me personally it is a very useful tool, and I know the intro and all the rest are there for me, for whenever I have the need and/or time to dig deeper. Crum375 01:23, 27 October 2006 (UTC)

As the creator of this template, I'd like to make the following comments:

• People arguing over the text of the nutshell summary is good. It means they're actually debating what the policy means, which doesn't really happen when the whole policy itself is up for grabs.
• People reading the nutshell summary and "thinking they know what the policy is about" is the whole idea. The alternative is them reading nothing at all, and having no idea what the policy is about. We're all agreed that no one reads *all* the policies. So let's stick with a workable trade-off.
• Visual clutter? A question for the graphic designers. Floating boxes everywhere *is* a bad idea. So fix it.
• The best summary is a succinct title? Yes, but there are obviously limits. I would happily support renaming all our policies to be succinct summaries. Wikipedia:Username would be a great place to start.
• I'm finding the nutshell summaries a really good way to keep up with how the policies are changing. They really do capture subtle shifts in interpretation without forcing me to re-read the whole policy. Stevage 14:00, 26 November 2006 (UTC)

Text alignment parameter

With all the modifications to the template, adding a text alignment parameter no longer works. Was this a by-product of formatting the caption for the template? If so, please restore the ability to specify how the text quoted in the template is aligned. (I'd do it myself, but I'm not well-versed in templates.) Thanks.—Chidom ^talk  06:24, 2 December 2006 (UTC)

The template is meant to be used in the official WP policy pages, and should be as much as possible standardized for uniform appearance. Can you give an example of which policy page you want a different alignment in? Thanks, Crum375 15:24, 2 December 2006 (UTC)

There was also an issue with this on Wikipedia:Verifiability. If it continues to be centered, it is not going to be used on that page. I also don't see why centering is necessary for every other page. Please explain; this was in fact left-aligned until a few weeks ago. —Centrx→talk • 07:07, 3 December 2006 (UTC)

I am looking at WP:V and the template looks nice and centered right now. What is the specific problem you are referring to? see below Crum375 14:37, 3 December 2006 (UTC)

As a former typesetter who understands how the human eye moves to read text, a numbered list should never be centered; the eye needs to move back to the same horizontal space to begin the next numbered item. It may be appropriate to center this text in the template when it is one or two lines of unnumbererd type; up until recently, there was an option to choose the appopriate text alignment based on the content of the template.—Chidom ^talk  18:46, 3 December 2006 (UTC)

Yes, now that you mention it, the list does look kind of ugly being centered. I guess part of the problem is that the 'nutshell' text there is kind of long, and maybe a list inside a nutshell is too much. I am for any ideas for improvement in that case. Crum375 18:50, 3 December 2006 (UTC)

I agree with Centrx and Chidom, and I have restored the parameter-controlled alignment, with default=left. Crum375 19:56, 3 December 2006 (UTC)

Thanks. It looks much better and, more importantly, is more readable. I appreciate the help.—Chidom ^talk  06:36, 6 December 2006 (UTC)

Template:Nutshell2

I created a new Nutshell2 template with the image on the left for compatibility with template:style-guideline. I added it to WP:CONTEXT and I think it improves readability (compare to previous version).Dhaluza 23:39, 15 January 2007 (UTC)

Your layout is better, so I've merged it into {{nutshell}}. —David Levy 19:20, 20 January 2007 (UTC)

OK, thanks. I changed WP:CONTEXT and tagged {{nutshell2}} for speedy delete. Dhaluza 21:04, 20 January 2007 (UTC)

And I've deleted it. Ah, the great circle of life... er...templates. :) --Brad Beattie (talk) 09:15, 21 January 2007 (UTC)

One of the valid objections raised here is the difference or lack thereof between the nutshell and the intro paragraph. And I've noted a few pages where there is no difference, making the nutshell redundant and useless. Repetition is a useful learning tool, but redundancy is not. I think they should convey information differently, like the difference between Microsoft Word and PowerPoint (sorry for the brand reference, but you get the point).

So to start the ball rolling again, I have regenerated the {{Nutshell2}} template as bulleted list, and applied it to WP:CONTEXT again. To address the clutter issue, I have hard coded it to a maximum of three bullets. Have a look, and post your observations here. I know there are some people who will not be happy with anything we create, but their concerns are still valid and should be addressed. Dhaluza 03:58, 23 January 2007 (UTC)

The same style of list can easily be created with the standard {{nutshell}} template. It's inappropriate to fork this thing again, especially for the purpose of imposing an arbitrary and artificial (as well as undiscussed) set of rules. There might be a good reason to include four items, and that's what boldness and discussion are for.

You noted on my talk page that you "created this template as a prototype for discussion," but you could have done that outside the template namespace (where these forks have a tendency to breed).

FYI, I replaced and redirected your new template before I saw the above message (and I began typing my reply before you reverted).—David Levy 04:11, 23 January 2007 (UTC)

Yes, and your reply beat mine here as well. Dhaluza 04:16, 23 January 2007 (UTC)

I added a bold note on the {{Nutshell2}} about the proposed usage and the lack of consensus. Dhaluza 04:22, 23 January 2007 (UTC)

It would be easier to simply move the template to your user space. —David Levy 04:31, 23 January 2007 (UTC)

Another editor pointed out that the same effect can be obtained by using {{nutshell}}. I created this template as a prototype for discussion to possibly replace the main nutshell template again. The current formulation forces the list to be bulleted, and caps it at three entries (unless you employ the code trick). The idea is to constrain the nutshell to a narrower range of acceptable usages. Dhaluza 04:14, 23 January 2007 (UTC)

1. As I noted, it's inappropriate to create a new template in the template namespace to demonstrate a proposed reformat of an existing template. This misleads inexperienced users to believe that it's a good idea to create countless minor variants of existing templates. Would you object to moving it to User:Dhaluza/Nutshell and deleting the redirect again?

2. Again, it's unreasonable to deliberately impose artificial limitations as a means of forcing editors to do something a certain way (thereby bypassing discussion). Furthermore, this style of list actually wastes a great deal of space; it would make many nutshell transclusions larger, even if their verbiage were reduced. —David Levy 04:31, 23 January 2007 (UTC)

You noted that nothing prevents someone from doing the same thing with the existing template. I think the purpose of templates is precisely to have people do something a certain way to create a unified style, for example the {{otheruses}} templates. The bulleted list will use more vertical column space with 3 bullets (hence the limit) but white space is actually an effective layout tool if used correctly. I would like to let others have a chance to comment. I think you formed a snap judgment on this (even before I was able to lay out the initial case). Dhaluza 11:40, 23 January 2007 (UTC)

1. You didn't address point 1. Is it okay with you to move this to your user space?

2. It's difficult to use white space as an effective layout tool when everyone sees a differernt amount of it. (At my resolution, I see far more than I do text.)

3. If there's consensus for changing every nutshell transclusion to the bullet style, we can add such code to the template. There's no valid reason, however, to place an artificial limitation on the number of items. If someone wants to include more than three, there might be a valid reason. This is something that should be determined (and discussed, if need be) on an individual basis, not arbitrarily determined on the template level. —David Levy 12:28, 23 January 2007 (UTC)

No one objected the last time. Let others weigh in first.Dhaluza 13:20, 23 January 2007 (UTC)

To what are you responding? —David Levy 14:44, 23 January 2007 (UTC)

Opinions requested

Would y'all please weigh in on the nutshell for WP:NPOV, as being discussed on Wikipedia talk:Neutral point of view? I believe this case is important in setting precedent for future guidelines - Brian Kendig 16:48, 23 January 2007 (UTC)

Actually, I'm a bit concerned. At first I didn't like nutshells, because I saw them as excuses for a poor opening paragraph. Then I saw some good nutshells such as WP:BOLD - "If in doubt, fix it." So I've been trying to tweak other nutshells to be succinct, and people have been reverting my changes. Two examples:

WP:NOR - original nutshell: "Articles may not contain any unpublished arguments, ideas, data, or theories; or any unpublished analysis or synthesis of published arguments, ideas, data, or theories that serves to advance a position."

My edit, which was reverted: "Wikipedia articles may only contain information that's been published in other sources."

WP:NPOV - original nutshell: "All Wikipedia articles and other encyclopedic content must be written from a neutral point of view, representing views fairly, proportionately and without bias."

My first edit, which was reverted: "Bias is unacceptable in articles. Be fair when presenting conflicting points of view."

My second edit, which was reverted: "Wikipedia articles must be written from a neutral point of view, representing viewpoints without bias."

There seems to be an opinion that changes to nutshells are changes to policy, and must gain approval on the Talk page before they can be made. There also seems to be an opinion that a nutshell must be comprehensive - even when I tried to remove "and other encyclopedic content" from the NPOV nutshell, I got pushback. So, let me ask you this: am I wrong in feeling that a nutshell should be a friendly-sounding "gist" of the general purpose of the article? Should a nutshell really try to cover all bases? - Brian Kendig 17:10, 23 January 2007 (UTC)

I'm with you in principle, but I don't believe that your changes were improvements.

Your WP:NOR nutshell tag actually was vague enough to be misleading; "Wikipedia articles may only contain information that's been published in other sources." could be misinterpreted to mean that the actual prose must be copied from other sources.

Your versions of the WP:NPOV nutshell tag didn't convey any false information, but they did omit some of the page's scope.

In both cases, I really don't see any benefit to these changes. I agree that the nutshell summaries shouldn't be too long, but the ones in question already were succinct enough. In my opinion, yours were too succinct. —David Levy 18:00, 23 January 2007 (UTC)

I can accept that. I was inspired by the "If in doubt, fix it" nutshell of WP:BOLD. I like the nutshells which are refreshingly congenial in tone, and I feel that's a goal that all nutshells should strive for, even at the expense of omitting details - that's what the rest of the guideline is there to take care of. - Brian Kendig 18:09, 23 January 2007 (UTC)

Please see my reply at Wikipedia talk:Neutral point of view. —David Levy 18:27, 23 January 2007 (UTC)

Your reply makes a good point, and makes me think that perhaps some guidelines for nutshells are a good idea to have. It would be a good thing to have some rules of thumb so that nutshells can be consistent in tone and in level of detail. - Brian Kendig 18:43, 23 January 2007 (UTC)

More reason why I feel we really need to agree on a policy: The nutshell for WP:NAME was an exact copy of the article's fifth sentence. I changed it to "Have a general audience in mind when naming Wikipedia articles" - not the best nutshell, I admit, but more approachable than the original, IMHO. It was reverted with this comment: "General audience" of what? Those who know nothing about the subject? The experts? Rockhopper penguins? I believe that this is a dangerous justification to use. If nutshells are required to qualify themselves, then they cease being nutshells at all, and are merely repetitions of some part of the guideline below them. So, what should nutshells be? Friendly and succinct? Or specific and detailed? - Brian Kendig 04:09, 24 January 2007 (UTC)

I think a good nutshell, which is certainly a challenge to achieve, strikes a balance between brevity and completeness. It should try to best describe the essential elements of the policy or guideline. Assume you just read and understood the entire page and someone asked you to summarize it for them in 20 words. Crum375 04:18, 24 January 2007 (UTC)

Usage

I removed the depreciated usages from the main page. While I was there, I added a very brief summary of some of the pearls of wisdom gleaned from the discussion page as guidance to others using the template.Dhaluza 02:24, 23 January 2007 (UTC)

I applied a notes template to the template notes, and did some minor edits.Dhaluza 03:37, 25 January 2007 (UTC)

Just FYI, you may get some pushback on those criteria you added - specifically the meanings of "brief" and "significant weight", and "the nutshell should not simply repeat text from the main article." These, especially the latter, are currently being disputed at WP:NPOV and WP:NOR and WP:NAME, all three of which use nutshells copied verbatim from the text below them. You may want to seek consensus before putting these criteria into the template usage notes. - Brian Kendig 06:22, 25 January 2007 (UTC)

Yes, that's exactly why I put them there and posted the notice here. I believe they are a summary of topics discussed in the talk page here, and I added them to the template notes to test for consensus, per the standard WP:Consensus process (not the alternative process used on those pages based on interpretation of {{policy}}). Dhaluza 11:54, 25 January 2007 (UTC)

I personally believe that the last 2 items are unnecessary and prefer the 'usage' to be simpler. If others insist on adding them, I suggest reaching consensus on this page first. Thanks, Crum375 12:45, 25 January 2007 (UTC)

I feel somewhat strongly in favor of "The nutshell should not simply repeat text from the main article." In my opinion, if the nutshell repeats the first sentence of the guideline, then it's redundant and kind of silly-looking. If it repeats some line further down in the guideline, then that means that the main idea of the guideline is buried and should be brought up to the first sentence, and that again makes the nutshell redundant. IMHO, the nutshell should paraphrase the guideline in a way that values brevity over covering all bases. I've seen the value of nutshells, and I really like them in a few cases, but I really do not like the trend of making nutshells that try to contain the whole nut. - Brian Kendig 15:53, 25 January 2007 (UTC)

I agree that it may look awkward in some cases to have repetition, especially if the repeated text is in close proximity, which makes it look downright ugly. But OTOH I think there may be cases where some repetition is unavoidable, and given that the nut is targeted at a potentially different audience (e.g. those who are following the 'nut trail' for a quick review of WP guidelines/policies), I wouldn't want to handcuff the nut authors too stringently. Perhaps a mere 'recommendation' would make sense there, I am open to phrasing suggestions. Crum375 16:10, 25 January 2007 (UTC)

I've seen repeated reference to this "nut trail" - what do you mean by it, exactly? Is there a page with a collection of all nutshells? If so, then I agree it's useful to make sure a nutshell is comprehensive in representing its guideline, lest people read it out of context and make the wrong assumptions. But if the nutshell only ever appears on its guideline page - then why shouldn't it be a goal to make this nutshell simple and brief enough for a reader to parse it in the time it takes his eyes to flick past it? If the nutshell needs to be longer than just a few words, or if it needs to repeat something verbatim that's already in the guideline, then why not just put that summary into the guideline's first sentence instead? Is there something special about putting text into an infobox? (When I'm in a hurry, my eyes generally skip over infoboxes, having been trained that infoboxes rarely contain information specific to the guideline itself.) I just don't see any usefulness at all in having a nutshell parrot something that is (or should be) right at the top of the guideline itself. - Brian Kendig 21:27, 25 January 2007 (UTC)

Unfortunately we seem to be going around in circles. All one has to do is read this Talk page and see that all these issues have been addressed, several times, in several separate threads. Just to mention a few: the 'nut trail' is just a way of describing the learning path taken by a novice user who wants to quickly obtain a top level understanding of the policies/guidelines. S/he skips from page to page, in each one just taking in the nut verbiage, and if necessary can dig in deeper by reading the intro, the TOC, or individual sections. The nut is guaranteed by definition to included the essential elements of the policy/guideline, while the intro could in principle be 'the first salvo of a long dissertation', and could include history, background, rationale, while the nut would get right to and focus on the core ingredidents. That you, as a seasoned user, may not need or use the nut is fine: you would probably look a the changes that occured since you last looked at a policy/guideline, while the novice often specifically comes to see the nut only, and having it right at the top is the most convenient. We would like WP to welcome new users, and we can go the extra mile to make our policies/guidelines extra friendly for them, even at the minimal cost that the rest of us may need to scroll a few lines lower to get to the intro. In summary, the nut trail is a systematic way to make WP user-friendly by presenting a bite sized form of bare essentials of each policy/guideline inside a standardized neat graphic box. It does not compete with and is separate from the intro which is not guaranteed to serve the same purpose, and the nut gives the new user a secure feeling of having seen the core essentials simply, quickly and efficiently. Crum375 22:37, 25 January 2007 (UTC)

I agree that these issues have been raised often, but I wouldn't say they've been addressed. Just have a look at WP:NPOV for an example of a nutshell that's unnecessarily wordy, verbose, and redundant (well, okay, it's not THAT bad, but I don't see why it has to include three synonyms), and WP:NOR for a nutshell that makes me read through it a couple of times to figure out what it's trying to say - it certainly isn't "friendly". I've tried to address both of these situations, and have had my every attempt reverted by people who feel that these nutshells do already embody what a nutshell is supposed to be. That's why I want to see a clarification agreed upon. If nutshells are supposed to be "bite sized", "bare essentials", and "extra friendly", then I welcome them, but I feel that several of the current nutshells just don't meet this description. - Brian Kendig 22:47, 25 January 2007 (UTC)

Brian, your concerns are certainly legitimate and constructive, and should be addressed individually on each respective Talk page. The current NPOV nut is this: "All Wikipedia articles and other encyclopedic content must be written from a neutral point of view, representing views fairly, proportionately and without bias". I fail to see how this is "wordy, verbose, and redundant". Sure there could be a better way of doing it, so suggest it on the Talk page and get a consensus for the new version. I think that discussing it here is wrong, as this is a specific issue to NPOV and does not taint the nut concept as a whole. I agree with you that the NOR nut can also be improved, but again IMO this is the wrong place to discuss it. I would focus all this critical energy into improving, by consensus, each specific nut. Thanks, Crum375 22:59, 25 January 2007 (UTC)

Good evening, Crum. I think you're missing the point. One way to interpret the conversation is as specific examples that need improvement. The other way to interpret it as general examples that the nutshells are not and quite possibly can not live up to the expectations set for them. They can't be fixed one by one if the underlying concept is unworkable. And that is the core question.
To Brian's point, the issues around nutshells have been raised over and over. And in fairness, you have tried to answer those questions. But I do not consider those problems to have ever been successfully "addressed". You politely copy the same answers each time but I, at least, remain unconvinced that the nutshells are a net benefit to the readers' understanding. Rossami (talk) 23:10, 25 January 2007 (UTC)

Good evening Rossami, I understand your point exactly, as I do Brian's. I agree that there are 2 separate issues: whether we should have nuts at all, and what the specific nut for each policy/guideline page should be if answer #1 is 'yes'. Currently, de facto, the answer is yes, and we should do our best to keep improving the nuts. If there is consensus that the nuts should go, then they should go, and there should be a separate discussion for that. Unfortunately, it seems that we keep arguing the same points over and over. To some people the pro-nut arguments are convincing, to others they are not. Just raising the same points over and over and going around in circles will not get us anywhere. And by the way, I have not 'copied' any of my points, I am just re-iterating them, since the anti-nut arguments seem to be repeated, ignoring the previous responses. I think it's clear some people have a nut allergy, the question is whether the rest of us, and the new users who especially benefit from them, should do without. Crum375 23:22, 25 January 2007 (UTC)

I'd like to point out that Crum is not alone in thinking the nutshells are beneficial. I very much think the concept is a good idea, and have seldom stepped in to give my opinion, only because I think Crum does such a good job explaining the benefits that I think my words aren't needed. Obviously, there are some that will never be convinced, but I support Crum and Brian Kendig's efforts to improve those nutshell summaries that reflect badly on the concept as a whole. -- Renesis (talk) 23:23, 25 January 2007 (UTC)

I agree that this isn't the place to get into specific examples. But just have a look over the 'What Links Here' list for Template:Nutshell, and read several of the Wikipedia:* nutshells, and you'll notice two distinct kinds of nutshells in use: ones that cleverly and simply sum up the purpose of the article, and ones that try to encapsulate the article itself by covering all bases and leaving no ambiguity. There are people who believe that the latter is the proper purpose of nutshells; I disagree, and I'd like to see a clear statement either way. I'd also like to see a clear guideline on whether nutshells are part of a policy and require consensus before they're edited, or whether they're a summary of a policy and can be tweaked for wording without an approval process. - Brian Kendig 23:31, 25 January 2007 (UTC)

I think all your points are valid. IMO, the ideal nut is 'a careful balance between brevity and completeness', and can be tweaked to achieve that magical sweet spot. Nuts both summarize the policy and are in a way part of it, and do require consensus, but not necessarily prior to editing. WP:BOLD does apply to the nuts, and anyone is welcome to try to improve them, but since they typically represent a careful balance, often reached after lots of give and take on the Talk page and discussion of each word, extra careful consideration should be given to not upsetting that balance. Crum375 23:40, 25 January 2007 (UTC)

Nice to see the lively discussion. Yes, although these items have been discussed before, no consensus was documented. So now we have something taking shape on the main page. I did some more housekeeping chores, making the template follow convention with a location section, and stating the obvious there. I moved one bullet up (and reworked it slightly) then added the excellent point about making WP inviting to new users from Crum375. Dhaluza 00:54, 26 January 2007 (UTC)

Template merge

David, nice job on the merge! I was just thinking it was time to suggest completing this, since the Nutshell2 bulleted list usage was stable. You beat me to the punch. Thanks for being WP:BOLD. Dhaluza 23:11, 28 February 2007 (UTC)

You forgot to put the word "is"

Before I changed the mistake, the template read "This page in a nushell". Well I fixed it and put "This page is in a nutshell.--Angel David 21:49, 23 August 2007 (UTC)

Why would we want it to say that? -- Renesis (talk) 23:17, 23 August 2007 (UTC)

Minor change

I changed the image to an svg version. It's not identical but it gets the point across quite clearly...and it's vector graphics (yay). Aar☢n Bruce^Talk/_Contribs 21:51, 20 March 2008 (UTC)

Nutshells are useless. Replace them with better summaries

Nut shells seem to be what summaries should be. If the nutshell is the solution to long summaries, those summaries should be shortened per wikipedia guidelines. This nutshell business is ridiculous. —Preceding unsigned comment added by 74.202.89.125 (talk • contribs)

Personally, I agree. (See the comments in the #Aw, nuts! section above where this was discussed before.) The concerns raised back in 2006 when this template was first drafted have never been successfully addressed. With an extra two years of experience, I am even more convinced that though they are well-intentioned, in aggregate they do more harm than good. Rossami (talk) 16:11, 24 April 2008 (UTC)

SVG

Does anyone else really like the svg version better? The png looks like a brain to me... Aar☢n Bruce^Talk/_Contribs 06:59, 21 March 2008 (UTC)

To me, the PNG resembles a split walnut shell, while the SVG resembles two edible nuts. Conceptually, the former is a better fit. —David Levy 15:18, 21 March 2008 (UTC)

You could have waited for a response before reverting from the longstanding icon, and a change that you know is disputed doesn't qualify as "minor" (not that an edit that significantly altered the template's appearance was minor in the first place). —David Levy 15:29, 21 March 2008 (UTC)

I agree that the PNG looks like more like a brain. Besides that, if a vector image is available, it should be used over the raster version (for obvious reasons), and thus this template should utilize the SVG, IMHO.--Opertinicy (talk) 02:19, 22 May 2008 (UTC)

What are the "obvious reasons"? —David Levy 21:29, 22 May 2008 (UTC)

A request of a dummy

I am new in using wiki and opened my own one. I would like to copy this template, but I have no frickin clue what part of the many brackets the template is…could some one add a simple box at the bottom with the code for the template?? If it depends on something, a small list?? This would be, btw., a general request. More and more dummies like me are trying to get something run and we do not get the complete logic behind the code… Thank you!--Jorgusch (talk) 13:39, 13 June 2008 (UTC)

Ombox time

{{editprotected}}

Talk pages

{{mbox
|image=[[Image:Walnut.svg|40px]]
|text='''{{{title|This page}}} in a nutshell:''' {{#if:{{{2|}}}|*{{{1}}}
*{{{2}}}{{#if:{{{3|}}}|
*{{{3}}}}}|{{{1}}}}}
}}

yes, we're using walnut.svg too. ViperSnake151 16:29, 18 June 2008 (UTC)

Done. Seems every other template in sight is getting standardized, as well, so don't anticipate much objection. – Luna Santin (talk) 03:51, 19 June 2008 (UTC)

I came here since I saw in "what links here" for {{mbox}} that this template used mbox. As far as I understand {{nutshell}} is for "Wikipedia:" pages and not talk pages. And besides {{mbox}} is not even deployed yet since we have not decided on what styles it should use for talk pages yet. So I changed the code to use {{ombox}} directly.

--David Göthberg (talk) 14:26, 12 July 2008 (UTC)

Interwiki

Please remove de and nl interwiki links, those pages do not exist (any more). --Kam Solusar (talk) 00:17, 24 June 2008 (UTC)

Y Done - I know template stuff is tricky, but next time you can update the interwikis yourself, since /doc pages are not protected. That is, if you click the [edit] button on the green doc box you can edit the interwikis at the bottom of the /doc page. --David Göthberg (talk) 14:45, 12 July 2008 (UTC)

PNG -> SVG

Could an admin update the image from Nutshell.png to Walnut.svg at the same resolution? 99.239.58.44 (talk) 15:34, 22 June 2008 (UTC)

Why? The SVG isn't an exact duplicate of the PNG and doesn't look as good at that size; in particular, the former has inferior anti-aliasing and an overwhelming shadow: —David Levy 15:45, 22 June 2008 (UTC)

I agree with David Levy. The current PNG image looks much better than the two SVG images that have been suggested on this talk page so far.

--David Göthberg (talk) 14:34, 12 July 2008 (UTC)

After reading David Levy's statement, I now believe the PNG looks much better than the SVG. Mythdon (talk) 10:14, 8 October 2008 (UTC)

Other than policy or guideline

Is this template allowed to be used for any page other than policy or guidelines?. Mythdon (talk) 10:13, 8 October 2008 (UTC)

Yes of course. You can use it on any non-article page. For instance we often use it on how-to guides, see for instance Wikipedia:Line break handling#Preventing and controlling word wraps.

Oh, I see now that the template documentation sounds like any other usage is discouraged. Which is untrue. I'll fix the documentation right away.

--David Göthberg (talk) 13:37, 8 October 2008 (UTC)

Can it be used in the userspace?. Mythdon (talk) 13:52, 8 October 2008 (UTC)

Sure, in user space you have very much freedom. Well, you shouldn't turn your user page into your blog or similar. I can imagine using this box something like this on my user page: "David Göthberg in a nutshell: I am from Sweden and I mainly program templates and edit articles about cryptography. You can contact me on my talk page."

Of course with proper wiki links on the relevant words. :))

--David Göthberg (talk) 14:19, 8 October 2008 (UTC)

Style tweaks

{{editprotected}}

I've reworked the sandbox to bring the template styling into line with the general mbox defaults. Just needs synced. Chris Cunningham (not at work) - talk 13:17, 7 December 2008 (UTC)

Done — {{Nihiltres|talk|log}} 07:35, 8 December 2008 (UTC)

Err, I set the image size back to 30px as the original PNG is only 30×30px to begin with—pixelation is not pretty. {{Nihiltres|talk|log}} 07:40, 8 December 2008 (UTC)

And I reverted it all, sorry.

• This template is used in several namespaces, such as talk pages. So it needs to use the {{mbox}} which detects namespace and automatically changes style accordingly.
• We usually put the {{pp-template}} on the template page itself, not in the /doc subpage. (Mostly so that beginner editors don't try to add or remove the {{pp-template}} to try to protect or unprotect the page. Not that it helps much, since I have also seen beginner admins that thought that adding {{pp-template}} protects a page! :))
• I think the image should continue to be 30x30px. Since this box should look smaller and not dominate over other boxes such as the "This is a guideline" boxes that usually comes above it.

--David Göthberg (talk) 19:12, 6 April 2009 (UTC)

Nutshells not only for policies

I really like the nutshell idea, and only realized recently that it is limited to wikipedia policy pages. Wouldn't it be an interesting suggestion to use them in any kind of article ? XApple 21:11, 11 February 2007 (UTC)

They are already used for guidelines and other types in Wikipedia space, but I would think that their use would not make sense for article space, for example. Can you give an example where you think they would be useful outside their current domain? Crum375 21:22, 11 February 2007 (UTC)

That purpose is served by the introduction. —Centrx→talk • 16:57, 17 February 2007 (UTC)

For instance, I was going to put on on the Dolly Zoom article before I found out you're not supposed to use them on articles. You have to read the whole first paragraph to really understand what it's about, but Dolly Zoom could be summarised into one sentence, for someone who was just wondering what it meant. I'm kinda new here, so I'm not sure how things work. Humphreys7 (talk) 03:06, 27 October 2010 (UTC)

That's an excellent indicator that the article lead needs a rewrite. Be bold and fix the article. Clumsy and ugly infoboxes at the top of the page, however, are a distraction to the reader and a disruption to the proper flow of the article. Rossami (talk) 13:15, 27 October 2010 (UTC)

Edit request from Hiuby, 20 May 2011

{{edit protected}} I have noticed the wiki tag "{{{1}}}" on the template. Please let me change the text from "{{{1}}}" to "{{{text}}}" (if you can). Thank you. --ヒウビ 私に話しかけて！User:Hiuby/Templates/HiubyTime

This cannot be done, as it would break the template. --Diannaa ^(Talk) 03:37, 21 May 2011 (UTC)

That's okay. --ヒウビ 私に話しかけて！ User:Hiuby/Templates/HiubyTime

It would be possible to make both {{{1}}} and {{{text}}} work, however, I don't see a strong reason to do so. Thanks! Plastikspork _―Œ^(talk) 22:51, 21 May 2011 (UTC)

Accessibility improvement for visually-impaired readers

{{editprotected}} For WP:ACCESSIBILITY to visually-impaired readers, WP:ALT #When to specify suggests omitting links from purely-decorative icons, so that screen readers don't burden the visually-impaired users with useless verbiage. I created a patch into the sandbox that does this by adding "|link=" in the obvious place. Please install this into the main version. For licensing reasons it has been argued that icons used in this way must not have licenses that require attribution; I don't agree with this argument, but to forestall any objections on these grounds the patch substitutes a public-domain icon. Thanks. Eubulides (talk) 21:09, 18 July 2009 (UTC)

Partially done. I was going to wait a bit to see if there was any objections to changing the image, considering the discussion above. I have no problem with it, but I thought I would wait for any additional feedback. Plastikspork (talk) 22:19, 18 July 2009 (UTC)

I object to the proposed image change. That's an acorn, not a nutshell. —David Levy 23:51, 18 July 2009 (UTC)

The change that Plastikspork installed suffices to fix the WP:ACCESSIBILITY problem; thanks. I suppose some might object to adding |link= with that image, but it's fine with me to leave it just as it is. Perhaps, if someone objects, we can ask them to come up with an image that they'd prefer. Eubulides (talk) 04:54, 19 July 2009 (UTC)

Yes, that seems sensible. —David Levy 05:11, 19 July 2009 (UTC)

Now needs "alt=" too

{{editprotected}} As a result of a recent change to MediaWiki we must now say both "|link=|alt=" to mark the nutshell as purely decorative; "|link=" by itself no longer suffices. This is documented in WP:ALT #Purely decorative images. Please install this obvious sandbox patch to do this. Thanks. Eubulides (talk) 04:54, 6 October 2009 (UTC)

Done; please update the documentation accordingly. Cheers,  Skomorokh, barbarian  07:40, 6 October 2009 (UTC)

Undone

I have reverted the above. The image currently being used is licensed as CC-BY-SA-1.0, which requires attribution, which we provide by linking the image to the file description page. Anomie⚔ 21:56, 23 November 2011 (UTC)

Question

How do you put multiple shortcuts on the template? 71.146.26.8 (talk) 01:54, 9 January 2012 (UTC)

Link

I request that where it says "nutshell" we should make a link to Wikipedia:Nutshell. It just seemed like something that wouldm't hurt anybody and I always thought would make sense.

--Walex03. Talking, working, friending. 23:58, 20 March 2012 (UTC)

Link

I request that where it says "nutshell" we should make a link to Wikipedia:Nutshell. It just seemed like something that wouldm't hurt anybody and I always thought would make sense.

--Walex03. Talking, working, friending. 23:58, 20 March 2012 (UTC)

Width

How to reduce the width of the template and float it to right? Why there is no parameter for that specified in the documentation?Aravind V R (talk) 07:52, 7 May 2012 (UTC)

Image size

Please can we increase the image size to 40px, in line with other message boxes. That way the text lines up better when using multiple mboxes. No need to reply (I'm not going to watch this page), just make the change or don't. It's only a small matter. nagualdesign (talk) 17:49, 29 February 2012 (UTC)

I swapped the {{nutshell}} on my user page for a customized {{mbox}} that uses the larger nut, if anyone's interested in seeing how it looks. The text lines up rather nicely. Regards, nagualdesign (talk) 10:29, 2 March 2012 (UTC)

Personally, I like the small icon. It encourages people to keep the text concise. Kaldari (talk) 02:51, 13 May 2012 (UTC)

Editprotected

Img replace to File:Walnut.svg .thx --Olli (talk) 18:21, 25 June 2012 (UTC)

Not done: Let's see if there is consensus for this change. Note that the current image may be used without a link to the file page, while the proposed replacement must retain the file link. Anomie⚔ 18:49, 25 June 2012 (UTC)

Why the SVG needs file link? And if it needs, why it would be unacceptable to have file link? --Olli (talk) 08:18, 1 July 2012 (UTC)

File:Walnut.svg needs the file link because the CC-BY-SA-1.0 license used requires that redistribution include a notice that the work is licensed under the CC-BY-SA-1.0 license, including a link to the license itself. It is considered that our linking of the file back to the file description page satisfies this requirement. Links to the file page on "decorative" images like this are opposed by some on accessibility grounds, as the information about the useless-to-blind-people image and link will still be read out by screen readers; see WP:ALT#Links and attribution for details. Anomie⚔ 14:25, 1 July 2012 (UTC)

Current	Proposed

Edit request

I was trying to list more than one shortcut in this template on a page utilizing this template, and was trying to figure out what it was not working. And then I realized why; this template looks like it is built to only allow 1 shortcut to be listed in it. In order to allow more than one shortcut to be listed in this template, without breaking the shortcuts already utilizing this template, could this line:

| imageright = {{#if:{{{shortcut|}}} | {{Ombox/Shortcut|{{{shortcut}}} }} }}

... be replaced with this:

| imageright = {{#if:{{{shortcut|}}} | {{Ombox/shortcut|{{{shortcut|}}}|{{{shortcut2|}}}|{{{shortcut3|}}}|{{{shortcut4|}}}|{{{shortcut5|}}} }} }}

...If so, please inform me of the changes, and I will be more than willing to update Template:Nutshell/doc accordingly. Thanks in advance! Steel1943 (talk) 02:56, 23 April 2013 (UTC)

• Also, please refer to my recent edit on Template:Nutshell/sandbox for my edit request tested. Steel1943 (talk) 03:11, 23 April 2013 (UTC)

  Done. Thanks for the suggestion. I also added a "shortcut1" alias for "shortcut", as I thought that would make more sense for people using multiple shortcuts. And yes, please update the documentation. :) Best — Mr. Stradivarius ^{♪ talk ♪} 10:17, 23 April 2013 (UTC)

Template-protected edit request on 5 March 2015

Nest the template, please. Like this:

<<< SOME GADGET GEEK >>> (talk) 16:43, 5 March 2015 (UTC)

Not done: it's not clear what changes you want to be made. Please mention the specific changes in a "change X to Y" format. — {{U|Technical 13}} (e • t • c) 16:52, 5 March 2015 (UTC)

I would like the templates to be nested, with one template appearing inside of another, as shown in the above example. Here is a further example: <<< SOME GADGET GEEK >>> (talk) 17:11, 5 March 2015 (UTC)

Why? — Martin (MSGJ · talk) 17:31, 5 March 2015 (UTC)

Because it makes the key point of the article stand out, reducing the amount of time needed to identify the purpose of the article itself. <<< SOME GADGET GEEK >>> (talk) 17:57, 5 March 2015 (UTC)

Not done: please establish a consensus for this alteration before using the {{edit template-protected}} template. Not only is your broken example a perfectly valid reason why this shouldn't be done, but common sense (which I have little of) demands it won't be done without a consensus to do so. — {{U|Technical 13}} (e • t • c) 19:17, 5 March 2015 (UTC)

Section parameter?

Having created a bit of a wall of text at Wikipedia:Village_pump_(idea_lab)#Easier_access_to_biography_articles_via_subject_surname.3F, I decided to add a "Nutshell" - but the only way to make it refer to a section was to subst and edit, which I've done. It would be useful, for talk pages, if there was a "Section" parameter to add to create this text? Any thoughts? PamD 18:40, 16 November 2015 (UTC)

There is already a documented |title= parameter to replace the "This page" text, if that's what you're referring to:

{{Nutshell|Lorem ipsum dolor sit amet|title=This section}} →

SiBr₄ (talk) 19:06, 16 November 2015 (UTC)

Change template

The {{unordered list}} template is used in the {{nutshell}} template; however, the {{unordered list}} template is merely a redirect to the {{bulleted list}} template. Whilst it mayn’t be a very significant change, I think that the template should be changed to {{bulleted list}} in this template.
―PapíDimmi (talk | contribs) 18:21, 13 July 2016 (UTC)

Template-protected edit request on 22 April 2017

Please add |alt=Nutshell icon or a similar phrase per MOS:ACCESS#Images. —Sangdeboeuf (talk) 01:50, 22 April 2017 (UTC)

Not done: The image is an icon, not a stand-alone image, and doesn't actually add anything to the content of the message. The bolded text of the message serves the same purpose and conveys the same essential information as the image. It is there as a visual reference to catch the reader's eye, and to someone using a screen reader it would actually make it more difficult to understand the message as there would be extra unnecessary text to read, and no information or functionality is lost by it not being there. See the last example at Wikipedia:Alternative text for images#Examples. Ahecht (TALK
PAGE) 03:03, 22 April 2017 (UTC)

This page...

"This page..." is a bit a tedious intro for something that's intended to be a friendly summary. How about making the default intro just "In a nutshell"?

Atón (talk) 14:28, 14 May 2017 (UTC)

Template-protected edit request on 22 July 2017

Please add the line break and the 90% font-size per this discussion.

In other words, change {{mbox
| image = [[File:Walnut.png|30px|link=|alt=]]
| text = '''{{{title|This page}}} in a nutshell:''' {{#if:{{{2|}}}
| {{unordered list|{{{1|}}}|{{{2|}}}|{{{3|}}}|{{{4|}}}}}
| {{{1}}}
}}
| imageright = {{#if:{{{shortcut|{{{shortcut1|}}}}}} | {{Ombox/shortcut|{{{shortcut|{{{shortcut1|}}}}}}|{{{shortcut2|}}}|{{{shortcut3|}}}|{{{shortcut4|}}}|{{{shortcut5|}}} }} }}
}}
to {{mbox
| image = [[File:Walnut.png|30px|link=|alt=]]
| text = '''{{{title|This page}}} in a nutshell:''' <br><div style="font-size:90%">{{#if:{{{2|}}}
| {{unordered list|{{{1|}}}|{{{2|}}}|{{{3|}}}|{{{4|}}}}}
| {{{1}}}
}}</div>
| imageright = {{#if:{{{shortcut|{{{shortcut1|}}}}}} | {{Ombox/shortcut|{{{shortcut|{{{shortcut1|}}}}}}|{{{shortcut2|}}}|{{{shortcut3|}}}|{{{shortcut4|}}}|{{{shortcut5|}}} }} }}
}}
UpsandDowns1234 (🗨) 05:23, 22 July 2017 (UTC)

Done Primefac (talk) 12:46, 22 July 2017 (UTC)

Template-protected edit request on 6 May 2020

Change the file to the SVG version not the PNG version. UnLeashedWolfie (talk) 08:04, 6 May 2020 (UTC)

 Done – Jonesey95 (talk) 13:23, 6 May 2020 (UTC)

Self-revert after reading the talk page comments above. Get consensus for this change. – Jonesey95 (talk) 13:25, 6 May 2020 (UTC)

Template-protected edit request on 27 September 2020

I suggest adding a nutshell CSS class to the template, like this:

{{mbox
| class = nutshell
| image = [[File:Walnut.png|30px|link=|alt=]]

This would have semantic benefits, such as facilitating selecting it using a custom CSS browser add-on. 79.249.159.246 (talk) 08:38, 27 September 2020 (UTC)

 Done * Pppery * _{it has begun...} 16:15, 27 September 2020 (UTC)

Template-protected edit request on 10 January 2021

Please replace the PNG with the SVG version. I have no idea why this requires consensus, given that this will not in the least change the way it works/looks/renders. SVG is clearly a better alternative for illustrations. 119.82.84.240 (talk) 21:10, 10 January 2021 (UTC)

 Not done: Multiple discussions in the archives have determined that the image currently in use is acceptable. See this and that (which was a request that never achieved consensus to implement, hence why I'm considering it as a "no consensus" result). Primefac (talk) 21:19, 10 January 2021 (UTC)

Avoid and remove per WP:IDIOM

I propose discontinuing the usage of this template and removing it from all pages as the phrase in a nutshell is a idiom. According to WP:IDIOM, idioms are generally to be avoided in favor of direct, literal expressions Additionally, this bars users who speak English as a second or foreign language who may not understand the idiom. Shooshosha (talk) 22:13, 22 September 2017 (UTC)

Shooshosha, if you wish to nominate the template for deletion, please follow the steps at WP:TFDHOWTO. Primefac (talk) 15:04, 23 September 2017 (UTC)

Primefac, due to the activity and its proliferation in the Wikipedia namespace, I consider it a better approach to gather a general consensus before nominating a frequently used template for deletion. I fear that this template was created to circumvent the necessity of the lead section of an article. I also believe simply being bold and renaming it the template to something like in as few words, tldr;, or simply speaking would address the idiom issue (save for the second example), but will undermine the MOS. I believe there are more problems with this template that need discussion first, before a nomination is put forward. Shooshosha (talk) 16:09, 25 September 2017 (UTC)

Fair enough. For the record, though, it is being used on zero articles at present. Primefac (talk) 16:33, 25 September 2017 (UTC)

@Shooshosha: I think this template is very useful, but that you make a good point about WP:IDIOM. How about changing the language from "in a nutshell" to just "in summary"? {{u|Sdkb}} ^talk 04:22, 4 June 2020 (UTC)

User:Shooshosha User:Primefac User:Sdkb
Would "Concise explanation of this page" work as replacement wording? Also, what image could be used instead of the current one? Perhaps simply the default information icon? Does anyone have any other suggestions? See my example below. DesertPipeline (talk) 10:04, 22 June 2021 (UTC)

Example

I find myself thinking two things: first, a change to a template that is used on 3600+ pages (2500 of which are WP-space) should have slightly more consensus than three editors. Second, I find nothing problematic with having an English idiom on the English Wikipedia. Maybe that makes me insensitive to the ESL speakers that edit here, but those are my thoughts. Primefac (talk) 13:16, 22 June 2021 (UTC)

User:Primefac: Because the manual of style recommends avoiding idiomatic language, do you think it would be fair to apply that to project-space too? Inconsistently applying it may cause problems and make people believe that idiomatic language is okay in articles because of its use in project-space. Of course, there are some cases where idiomatic language is fine in project-space, but it probably depends on the context – essays, for instance. What do you think? Thanks, DesertPipeline (talk) 10:13, 13 July 2021 (UTC)

The MOS is for articles, excepting in the case of accessibility in which it should be followed site-wide. I also feel like this is one of the more well-known idioms (after all, there is an entire YouTube channel that uses the German version of "in a nutshell"). Again, I have zero issue in changing or removing the idiom if there is consensus to do so, but given the age and widespread use of the template the consensus is currently trending toward "is perfectly fine to use in the project space". Primefac (talk) 17:33, 13 July 2021 (UTC)

User:Primefac: Would the best way to get wider input be to put an RFC on this page? DesertPipeline (talk) 03:37, 14 July 2021 (UTC)

Technically WP:TFD would be the first place to get input (the D is for "discussion" after all), and with Shooshosha's initial proposal it would not be unreasonable to say "we should delete this or change the message". An RFC for something like this would probably be option #3. Primefac (talk) 10:05, 14 July 2021 (UTC)

User:Primefac: I don't think there's a case for deletion personally; but can templates be listed there specifically for the purpose of getting input on a change? DesertPipeline (talk) 11:38, 14 July 2021 (UTC)

It's not done often, and the more I think about it the more I think that the nominator will get yelled at. A cross-post to one of the Village Pumps with a "hey we need more input" would probably help. Primefac (talk) 14:23, 14 July 2021 (UTC)

User:Primefac: Sorry for the slow reply. Which village pump page should it be posted to? Whenever I want to do so, I often can't really figure out which is suitable. DesertPipeline (talk) 13:09, 21 July 2021 (UTC)

 Done. Primefac (talk) 15:15, 21 July 2021 (UTC)

• No. WP:IDIOM is a guideline concerning articles. This is not Simple Wikipedia and anyone who doesn't understand "in a nutshell" should regard it as an opportunity to do some searching and improve their English skills so they can better handle the English Wikipedia. Johnuniq (talk) 02:31, 22 July 2021 (UTC)

  User:Johnuniq: While it is a guideline concerning articles, I think it is a good suggestion. Project pages are generally professional in tone; this template's wording, however, is not. Also, I don't feel that understanding idioms has anything to do with English skills. Essentially an idiom is something where people know what it means because it is often-used; even though they often make little sense, repetition in the correct context allows people to understand what they mean. However, I think that clear and literal writing is a positive thing, because it allows anyone who understands English to understand a sentence without having to determine the meaning of a non-literal phrase. DesertPipeline (talk) 04:43, 22 July 2021 (UTC)

• MOS:IDIOM exists for articles and not project pages because our readership is much more diverse than our editor base; reading English (especially in the days of digital translation) is a more widespread skill than writing English. Project pages do not need to be to the same standards as articles because the audiences are very different. The proposal seems like rearranging deck chairs on the titanic. The accessibility of our policies to global English speakers is a huge problem because of their number and complexity; changing "in a nutshell" will not make our policies any easier to understand. If a reader can neither understand nor be bothered to look up that idiom, it is unlikely that they will get much use out of the policy as a whole. That should be fixed, of course, but I seriously doubt the proposed change will have any measurable impact on either editor recruitment or policy compliance. That said, I'd be fine with changing the text to "Short summary" or just "Summary", but I'd prefer we spend our time on more important tasks. — Wug·a·po·des​ 20:22, 22 July 2021 (UTC)

  Agree; well put. {{u|Sdkb}} ^talk 00:11, 23 July 2021 (UTC)

  User:Wugapodes: I would be fine with "Summary"; or perhaps "Page summary". However, considering the low effort required to make this change, I don't think we should discount fixing it simply because we have other problems to solve; the best solution is to solve all our problems. DesertPipeline (talk) 05:36, 23 July 2021 (UTC)

  The effort is measured in opportunity cost, not lines of code. Changing a template used on thousands of pages takes considerable consensus which requires many editors spend time to read and write a response---time that could be spent fixing typos or reverting vandalism. The best solution is to improve the encyclopedia after all, and cosmetic changes to project pages rarely do that. Few people have commented probably because they don't think it's worth the time, and those who did think it's worth the time have generally fallen on the critical side. If you want to spend your time marshaling editors in support of this change, go for it, but imo the cost-benefit ratio just isn't worth it given the opposition above. — Wug·a·po·des​ 05:47, 23 July 2021 (UTC)