View source for Wikipedia talk:Make technical articles understandable

{{User:MiszaBot/config
|archiveheader = {{aan}}
|maxarchivesize = 150K
|counter = 3
|minthreadsleft = 5
|algo = old(730d)
|archive = Wikipedia talk:Make technical articles understandable/Archive %(counter)d
}}
{{Archives |search=yes |bot=MiszaBot II |age=2 |units=years }}
{{see also|Wikipedia talk:Explain jargon}}

==Making articles more understandable does not necessarily mean that detailed technical content should be removed. ==

While some articles can be, in places, difficult to understand without a backing in the topic that they discuss, this often has more to do with the subject matter of the article, than it has to do with the word choice of its authors. In order to be factually robust, many articles '''must''' talk about things that could come off as complicated. In the past, Wikipedians have been known to insert tone tags into articles which contained language they found overly technical. If you are unsatisfied with the article's readability, a better solution would be to tag it as needing help from an expert-- somebody with a backing in the topic, who can re-write portions of it so that they're easier to read, without compromising their educational value. Generally, the tone tag is reserved for articles which fail to meet a basic standard-- articles that are poorly written, needlessly verbose or flowery, or which are clearly biased. As technical articles are typically created by professionals and tend to be of higher quality, the tone tag is not usually appropriate. I encourage Wikipedians who are interested in helping with this project to remove tone tags from articles which do not need them, so as to avoid confusing copyeditors. Many copyeditors will see the tone tag and look for something completely different. [[User:Atomic putty? Rien!|Atomic putty? Rien! (talk) ]] ([[User talk:Atomic putty? Rien!|talk]]) 20:41, 21 June 2022 (UTC)

:Exactly. The idea that people need knowlege pulped and chewed up is a misconception. If one understands everything in a Wikipedia article on a technical subject, that means they know the subject well. Then why bother reading this particular article? It's a waste of time. One of the first books I ever read was an encyclopedia of technology and science. Of course I did not understand, pretty much anything, but I got an overview of how much there is TO learn! Did it bother me? No, of course not. I think there are people who might be bothered by it, and the question is why. Did they get traumatized by someone who did not like answering questions? There are probably plenty such people, but hopefully, they will in time heal. It won't help them heal if we pretend that information is just not there to bother them. I doubt they are visiting technical articles just to feel bad. [[User:Morycm|Morycm]] ([[User talk:Morycm|talk]]) 23:02, 4 February 2023 (UTC)

:{{ping|Atomic putty? Rien!}}  I don't think anyone's suggesting dumbing down articles or removing technical content.  And an "expert needed" tag won't help, because it is the experts who write these incomprehensible articles.  There's a difference between being an expert, and being an expert and a good encyclopedia editor.  --[[User:Chetvorno|Chetvorno]]<sup><small>[[User talk:Chetvorno|<i style="color: Purple;">TALK</i>]]</small></sup> 19:40, 6 February 2023 (UTC)
::@[[User:Chetvorno|Chetvorno]] Then I have an idea: use team approach. Get an expert, a writer, and a Wikipedia stylistic advocate. They will make sure it is technically correct, easy to understand, and reaches the widest possible audience ''for that subject''. But if you expect to ''maximize'' audience, just do what top Youtube channels do: stick to sports, girls, beer, dogs, cats, and comedy. Because for those who look for ''information'', a wikipedia that appeals to an average person from the global crowd would simply be a useless babble. [[User:Morycm|Morycm]] ([[User talk:Morycm|talk]]) 02:17, 13 February 2023 (UTC)
::I agree with @[[User:Chetvorno|Chetvorno]] 100%. Looking back, my opinion's definitely changed. When I wrote the earlier note, about a year ago, I felt strongly that accuracy shouldn't be compromised for readability-- but honestly, just like they said, a good encyclopedia editor can tone down the heavy detail, improve readability, and conserve accuracy. 
::Congrats to all parties for participating in the discussion. When in doubt, let's turn to our already-established best practices. I'm not sure why I felt the need to defend the conservation of detail so strongly before. Looking over the article, it does a really good job of keeping to the consensus with regard to detail and readability. ^-^  [[User:Atomic putty? Rien!|<span style="font-family:cursive;color:Tomato"> Atomic putty? Rien! </span>]] 19:51, 13 February 2023 (UTC)
:::I also agree with Chetvorno. My particular concern is the lede paragraph of technical, or merely semi-technical articles. All too often Wikipedia writers leap instantly into textbook mode in the opening sentences, as if readers could understand arcane jargon, calculus or otherwise advanced mathematics. Such practice violates multiple policies and guidelines that article ledes should be written for the general reader and should not presume the reader is familiar with a technical subject. The "Bessel function" lede that Chetvorno showed is a very good example. When I do a Google search for something, I want a brief comprehensible summary of an unfamiliar word or concept. But frequently in Google results, I'm confronted with a blurb like Bessel function, and I will do exactly what Chetvorno did--I'll look for the Britannica version, because the Wikipedia introduction, though probably accurate, is nevertheless impenetrable, and therefore useless for my purpose. I also oppose the practice, in the lede, of linking jargon to separate articles. I added text to this Guideline to say that "Terminology in the lead section should be understandable on sight to general readers". Loading up a lede with linked terminology forces readers unfamiliar to stop and start multiple times as they hover or click  on the terms, when all they wanted was an accessible summary of the topic which they could read uninterrupted. I don't object when editors include advanced technical material in the body of an article, but doing so in the lede violates policy and is a disservice to readers that should be avoided. [[User:DonFB|DonFB]] ([[User talk:DonFB|talk]]) 11:46, 14 February 2023 (UTC)
::::{{reply|DonFB}} Thanks for the addition to the article.  I have no objection to a lot of links in the lede, as long as it is not overly dependent on links: it should have brief explanations in ordinary language of the jargon used.  
::::I absolutely agree with you about the confusing ledes in our technical articles.  They are often ridiculously abstract and esoteric, when they are the part of the article that should be most widely understandable.  I have rewritten dozens of ledes to be clearer.  I think what happens is technically-minded people progressively expand the definition in the lede to be more abstract and cover more special cases, borderline cases and fields, until the definition becomes completely incomprehensible to ordinary readers. The ironic thing is that it is usually possible to incorporate the advanced stuff they want in the lede and ''still'' have it be adequately comprehensible to general readers, using ordinary good writing techniques.   Most technically-educated Wikipedia editors are used to writing only for others in their specialty.  Writing an encyclopedia requires a slightly different style of writing, but one which any educated person can do.  Our editors just don't want to. --[[User:Chetvorno|Chetvorno]]<sup><small>[[User talk:Chetvorno|<i style="color: Purple;">TALK</i>]]</small></sup> 21:01, 15 May 2023 (UTC)
:::::I prefer to see no linked jargon in a lead, although I recognize that it is possible to show jargon with a useful parenthetical definition. However, I want to see such practice held to a bare minimum. It's also reasonable to link from an ordinary word which has special meaning in the context. An example is the link I made in the Tidal Locking lead from the word "variablity". Originally, "libration" appeared in the lead as a link with no parenthetical explanation, an example of exactly what not to do (link only from jargon, with no other help). Recently, I took a somewhat novel approach to making the case for rewriting a jargon-filled lead in the Femur article. The result was a successful revision with no objections and a small followup tweak by another editor. See the Talk topics beginning with [[Talk:Femur#Turgid_intro|Turgid Intro]] and the next two headings; note the (tl;dr) collapsed Virtual Discussion. [[User:DonFB|DonFB]] ([[User talk:DonFB|talk]]) 04:36, 19 May 2023 (UTC)

== Total rewrite attempt ==

In a [https://en.wikipedia.org/w/index.php?title=Wikipedia%3AMake_technical_articles_understandable&diff=1180603176&oldid=1171605560 sweeping set of changes], {{U|CactiStaccingCrane}} rewrote, in a substantive not copy-editing way, nearly everything in this guideline, and that is of course not how guideline change happens. Each substantive proposed change to the guidance and its meaning should be individually discussed and consensus sought for it, as even seemingly trivial changes to guidelines and policies can affect thousands, even potentially millions, of pages and their content. <span style="white-space:nowrap;font-family:'Trebuchet MS'"> — [[User:SMcCandlish|'''SMcCandlish''']] [[User talk:SMcCandlish|☏]] [[Special:Contributions/SMcCandlish|¢]] 😼 </span> 19:43, 17 October 2023 (UTC)

PS: For the record, I dispute that many of these changes were improvements. Many of them are clumsily, even misleadingly worded, and much of the material is rather emotive and laced with superlatives and over-broad or exaggeratory statements. Perhaps CactiStaccingCrane should consider writing a [[Wikipedia:Essays#User essays|user essay]] on this subject to express their heated opinions. <span style="white-space:nowrap;font-family:'Trebuchet MS'"> — [[User:SMcCandlish|'''SMcCandlish''']] [[User talk:SMcCandlish|☏]] [[Special:Contributions/SMcCandlish|¢]] 😼 </span> 19:48, 17 October 2023 (UTC)

:I think a good rule of thumb when editing guidelines might be: "If you're thinking about/trying to remedy particular editors' particularized classes of mistakes, you shouldn't be writing a guideline right now". [[User:Remsense|<span style="border-radius:3px 0 0 3px;padding:4px 3px;background:#1E816F;color:#fff">'''Remsense'''</span>]][[User talk:Remsense|<span lang="zh" style="border:1px solid #1E816F;border-radius:0 2px 2px 0;padding:2px;color:#000">聊</span>]] 20:02, 17 October 2023 (UTC)
::@[[User:Remsense|Remsense]] Then what should I do instead then? Isn't a guideline all about trying to do just that? [[User:CactiStaccingCrane|CactiStaccingCrane]] ([[User talk:CactiStaccingCrane|talk]]) 17:59, 21 October 2023 (UTC)
:::i would disagree with this actually, a guideline written in language as general as possible is preferable, if you're targeting specific editors, that's a tone much more suited to an essay imo [[User:Remsense|<span style="border-radius:3px 0 0 3px;padding:4px 3px;background:#1E816F;color:#fff">'''Remsense'''</span>]][[User talk:Remsense|<span lang="zh" style="border:1px solid #1E816F;border-radius:0 2px 2px 0;padding:2px;color:#000">聊</span>]] 19:01, 21 October 2023 (UTC)

:Thanks @[[User:SMcCandlish|SMcCandlish]] for the revert. I do think it's worth making changes to this guideline though (with discussion), especially to its "lead" section, which doesn't do a great job introducing or summarizing the rest of the page, in my opinion. I'm not sure quite the right tone we should adopt in this kind of guideline, but I somewhat liked Cacti's idea of boldly leading with an emphasis on readability. I really dislike the current sentence, "When adding content and creating new articles, an encyclopedic style with a formal tone is important.", which seems vague, passive, and generally weak. The current mention of "essay-like, argumentative, or opinionated writing" seems somewhat off topic; the problem this guideline is trying to address is overly technical writing, not overly informal or opinionated writing. Etc. –[[user:jacobolus|jacobolus]] [[User_talk:jacobolus|(t)]] 20:05, 17 October 2023 (UTC)
::Aye, 'encyclopedic' and 'formal' seem a bit like tautologies. There's some way to phrase that, even in the lead, that's actively helpful. [[User:Remsense|<span style="border-radius:3px 0 0 3px;padding:4px 3px;background:#1E816F;color:#fff">'''Remsense'''</span>]][[User talk:Remsense|<span lang="zh" style="border:1px solid #1E816F;border-radius:0 2px 2px 0;padding:2px;color:#000">聊</span>]] 20:10, 17 October 2023 (UTC)
:::I agree that CactiStaccingCrane's edit/rewrite was excessive. Also agree with Jacobolus about the off-topic tone in some wording in the opening section. [[User:DonFB|DonFB]] ([[User talk:DonFB|talk]]) 20:21, 17 October 2023 (UTC)
::::Sure. I actually thought about restoring a copyedited version of some of CactiStaccingCranes lead changes, but I don't want to be acting unilaterally while complaining of someone acting unilaterally. <span style="white-space:nowrap;font-family:'Trebuchet MS'"> — [[User:SMcCandlish|'''SMcCandlish''']] [[User talk:SMcCandlish|☏]] [[Special:Contributions/SMcCandlish|¢]] 😼 </span> 20:29, 17 October 2023 (UTC)
::How about this: Wikipedia articles should be written for the widest possible general audience that the subject matter of those articles will allow. Wikipedia serves readers with a diverse range of backgrounds and covers subjects from the everyday to the arcane. Some articles will naturally be targeted to specialists, while others need to be comprehensible by a wider population, and it can happen that a single article should provide value both for novices and for experts. This affects how we organize articles. The introduction of an article should ideally be comprehensible to a broad readership. When organizing the sections that follow the introduction, it is typically a good idea to put the least technical part of an article first. It can be helpful to consider the stage in a student's education when they are introduced to a subject, and to write with an earlier stage in mind. [[User:XOR&#39;easter|XOR&#39;easter]] ([[User talk:XOR&#39;easter|talk]]) 02:14, 18 October 2023 (UTC)
:::Well-expressed. I would differ, though, on the matter of "targeted". Certain subjects are highly technical, and the article text will reflect as much. I don't think targeting is needed, per se. The text of any article should be written to be as accessible as possible. My overriding concern is article lead sections, excerpts of which appear in Google search results. As a reader and seeker of information, I am all-too-often disappointed and annoyed when I see jargon-laden or needlessly dense text in those results. [[User:DonFB|DonFB]] ([[User talk:DonFB|talk]]) 02:36, 18 October 2023 (UTC)
::::How about, "Some articles will naturally be mostly of interest to specialists"? [[User:XOR&#39;easter|XOR&#39;easter]] ([[User talk:XOR&#39;easter|talk]]) 03:03, 18 October 2023 (UTC)
:::Here's my take (anyone rewriting this page should feel free to chop any bits you like):
:::{{tq|Wikipedia articles should be written for the [[Wikipedia:AUDIENCE|widest possible audience]]. {{pb}} As a free encyclopedia with the goal of democratizing knowledge, Wikipedia serves readers with a wide range in background, preparation, interests, and goals. Even for articles about the most technically demanding subjects, these readers include not only subject experts but also students and curious laypeople. While upholding the goals of accuracy, neutrality, and full coverage of the most important aspects of a topic, every effort should be made to also render articles accessible and pleasant to read for less-prepared readers. {{pb}} It is especially important to make the [[WP:LEAD|lead section]] understandable using plain language, but it can be helpful more generally to begin with more common and accessible subtopics, and proceed later to those requiring advanced knowledge or addressing niche specialties. {{pb}} Articles should be written in encyclopedic style, but this differs from the spare and technically precise style found in scholarly monographs and peer-reviewed papers aimed at specialists. Articles should stay on topic without twisting the truth or telling "[[Lie-to-children|lies-to-children]]", but they should also be self contained when possible, and should not take prerequisite knowledge for granted or gratuitously use unexplained [[jargon]] or advanced technical notation: shortcuts which save time and effort for experts can be barriers to the uninitiated.}}
::: –[[user:jacobolus|jacobolus]] [[User_talk:jacobolus|(t)]] 03:07, 18 October 2023 (UTC)
::::I am generally happy with that. [[User:XOR&#39;easter|XOR&#39;easter]] ([[User talk:XOR&#39;easter|talk]]) 03:15, 18 October 2023 (UTC)
::::Generally works for me, but it could use some trimming for concision. E.g. drop "with the goal of democratizing knowledge", "not only subject experts but also", "but it can be helpful more generally to", etc. There's some redundancy here and there; "proceed later to" &rarr; "proceed to". However, the fact that WP has "the widest possible general audience", in XOR&#39;s original, is valuable, and a point we don't make frequently enough. <span style="white-space:nowrap;font-family:'Trebuchet MS'"> — [[User:SMcCandlish|'''SMcCandlish''']] [[User talk:SMcCandlish|☏]] [[Special:Contributions/SMcCandlish|¢]] 😼 </span> 08:05, 18 October 2023 (UTC)
:::::I don't have any objections to Jacobolus' suggested text. I'm not sure, though, where in the Guideline it would be used, as it seems to reiterate points already present in the current version. My preoccupation with the lead section of an article, to be clear, is not merely due to my own preferences, but is because that's the part of an article that all readers will see, and may be the ''only'' part they see. We owe it to them to make the lead readily comprehensible, even for highly technical subjects, to say nothing of subjects that may be merely semi-technical. I'm frankly not overly concerned about highly technical descriptions deep inside some articles. But I want the Introduction (lead) of every article to be clear, free of jargon, and not dependent on links to ''other'' articles for meaning. [[User:DonFB|DonFB]] ([[User talk:DonFB|talk]]) 18:45, 18 October 2023 (UTC)
::::::Does the current [[Wikipedia:Make_technical_articles_understandable#Lead_section|§ Lead section]] section cover it, or is there more (or something different) we should say? One of [[user:CactiStaccingCrane|CactiStaccingCrane]]'s ideas was to include some examples. Is that something we should try to do here (if so does anyone have recommendations of good examples to look at), or are they a distraction? –[[user:jacobolus|jacobolus]] [[User_talk:jacobolus|(t)]] 19:13, 18 October 2023 (UTC)
:::::::Disclosure: the wording that terminology should be recognizable "on sight" is my contribution. I'm not fond of the last sentence in the section, which undercuts the emphasis I favor, but it was retained in a previous discussion. I'm not averse to including an example; elsewhere, I have pointed to revision of the lead of [[Tidal locking]], which I initiated.  (Before revisions: https://en.m.wikipedia.org/w/index.php?title=Tidal_locking&oldid=904381140)
::::::: [[User:DonFB|DonFB]] ([[User talk:DonFB|talk]]) 19:55, 18 October 2023 (UTC)
:::::::: I'm happy with the section as is. The last sentence accurately describes how highly technical topics are addressed on Wikipedia, so there is nothing wrong with it. The "on sight" claim may actually be a bit too much; we routinely link potentially unfamiliar keywords in the lead section, and as said elsewhere we do not use a "lies-to-children" approach to dumb down the material. There's a fine line between doing that an avoiding unnecessary jargon. Some jargon is actually necessary, and just has to be made explicable in-context one way or another. <span style="white-space:nowrap;font-family:'Trebuchet MS'"> — [[User:SMcCandlish|'''SMcCandlish''']] [[User talk:SMcCandlish|☏]] [[Special:Contributions/SMcCandlish|¢]] 😼 </span> 20:35, 18 October 2023 (UTC)
:::::::::"On sight" is, indeed, rather rigorous, but it can be considered aspirational--a reminder that links should be used to supplement info in the lead, not to explain a term that may unfamiliar or incomprehensible, or both. When I read an introduction, I want to stay on the page, not chase after multiple linked terms to figure out what the text means--I believe that's probably the preference of most readers. Such terms appear too often in lead sections, because editors did not endeavor to explain or define the term in plain English, but simply defaulted to language found in textbooks or technical journals with which they're familiar--language that's often not appropriate, in my view, for the introductory section of an encyclopedia article. You said, "we routinely link potentially unfamiliar keywords in the lead section," which is true and is both symptom and cause of problems evident in too many leads. I think the practice should be much less frequent, rather than routine. Yes, we shouldn't dumb down the text, but the Guideline does suggest writing down one level when appropriate. I think a common reason the problem happens is because people want to put in information they know without much regard whether the text helps general readers or befuddles them. One approach, when possible, is to link a plain English term to an article about the technical term or concept,* or put the linked technical term in parentheses (though I am not a fan of parenthetical stage whispers in lead sections).
:::::::::* An example, from the aforementioned Tidal Locking, was use in the Intro of "variability", linked to the article Libration.
:::::::::[[User:DonFB|DonFB]] ([[User talk:DonFB|talk]]) 23:48, 18 October 2023 (UTC)
::::::::::Guidelines and policies generally don't work where they contain aspirational language that can't really be concretized; it simply provides levers for disruptive wikiawyering. <span style="white-space:nowrap;font-family:'Trebuchet MS'"> — [[User:SMcCandlish|'''SMcCandlish''']] [[User talk:SMcCandlish|☏]] [[Special:Contributions/SMcCandlish|¢]] 😼 </span> 00:33, 19 October 2023 (UTC)
:::::::::::That is why we should not encapsulate a complete definition in a sentence. In the case of tidal-locking:
::::::::::::{{!xt|'''Tidal locking''' between a pair of co-orbiting astronomical bodies occurs when one of the objects reaches a state where there is no longer any net change in its rotation rate over the course of a complete orbit. In the case where a tidally locked body possesses synchronous rotation, the object takes just as long to rotate around its own axis as it does to revolve around its partner.}}
:::::::::::Why don't abstractize the idea of "spin–orbit resonance" in the first sentence and explain what is it in the second sentence?
::::::::::::{{xt|'''Tidal locking''' occurs when one astronomical body has a fixed resonance ratio between its rotational and orbital period. The most common resonance ratio is 1:1, meaning that the tidally locked body completes one rotation around its own axis for every revolution around the parent body. This specific phenomenon is also called ''synchronous rotation''.}}
:::::::::::The first sentence can serve as a formal definition for the topic. It might have a lot of jargon ("resonance ratio", "rotational period", "orbital period") but it is ok when a newcomer to the topic just need to read more to understand what these terms meant. [[User:CactiStaccingCrane|CactiStaccingCrane]] ([[User talk:CactiStaccingCrane|talk]]) 13:37, 21 October 2023 (UTC)
:::::::::Many highly technical topics on Wikipedia would benefit from putting (significantly) more effort into accessibility for a wider audience. It's not always possible to eliminate jargon, formulas, etc., but especially for basic topics of wide interest, we should try try try.
:::::::::As a concrete example, I just stopped by [[Computer programming]], and wow what a mess the lead is there. –[[user:jacobolus|jacobolus]] [[User_talk:jacobolus|(t)]] 15:38, 19 October 2023 (UTC)
::::::::::I tried doing something with the first paragraph, at least. [[User:XOR&#39;easter|XOR&#39;easter]] ([[User talk:XOR&#39;easter|talk]]) 23:12, 19 October 2023 (UTC)
:::::Please feel free to write something more concise! (With or without copying bits from my proposed text above.) –[[user:jacobolus|jacobolus]] [[User_talk:jacobolus|(t)]] 19:12, 18 October 2023 (UTC)
::::{{ping|jacobolus}} "Wikipedia articles should be written for the widest '''possible''' audience." I could agree to that, but if the word "possible" was taken with the proper meaning -- which does not seem to be the case.<br/>I strongly disagree with the view that the lead of every article (much less the whole article) should be made understandable to as many readers as possible, regardless of their previous knowledge.  Wikipedia is not meant to be a giant textbook, or set of textbooks.  It is meant to be a ''reference'' resource, like an encyclopedia, dictionary, or technical manual -- where people come to get answers to specific questions about a topic, such as the precise definition or some basic facts about it.  Not to learn a broad topic like "algebra".  Thus each article should be accessible to the largest possible number of '''such''' readers.<br/>Thus, for example, an article about "polynomial" can ''and should'' assume that the reader has at least a vague idea of what a "function" is, and a minimal knowledge of argebra.  Whereas an article about "eigenvectors" can ''and should'' assume that the reader knows what is a vector space and a linear transformation ''or'' what is matrix multiplication and determinant.  Trying to make the latter readable to people who do not have that basic knowledge is not only futile but renders a disservice to those readers for which the article exists.--[[User:Jorge Stolfi|Jorge Stolfi]] ([[User talk:Jorge Stolfi|talk]]) 14:13, 13 June 2024 (UTC) 
:::::{{ping|Jorge Stolfi}} – People come to Wikipedia for a broad range of reasons, and we should strive to help them meet their needs to the extent we practically can. I hear regular complaints about advanced mathematical articles being inaccessible from such people as math grad students and professionals in physics, economics, or computing, i.e. people who are steeped in and spend their whole careers on math-heavy technical detail. (Among similar complaints about less advanced articles from younger students and laypeople.) Where we can, adding lower-jargon prose about a topic's context, meaning, and uses instead of diving into the deep end not only expands an article's audience tenfold, but also is often quite helpful even to more advanced readers. –[[user:jacobolus|jacobolus]] [[User_talk:jacobolus|(t)]] 15:29, 13 June 2024 (UTC)
:::::{{ping|Jorge Stolfi}} - I disagree with your opinion in which you disagreed that the lead of every article "should be made understandable to as many readers as possible". In contrast to what you said, multiple Wikipedia guidelines/policy (including this one) strongly recommend that lead ("lede") sections should be understandable to a broad audience, without regard to the reader's previous knowledge. (See also: [[MOS:JARGON]], [[WP:NOTTEXTBOOK]] (#7), [[MOS:NOFORCELINK]]) 
:::::I approach this issue as a reader. Countless times in search engine results, I have encountered an unnecessarily difficult introductory sentence or paragraph from a Wikipedia article, when I'm simply looking for a basic explanation of a concept or unfamiliar word. I don't object to highly technical text in the body of articles, and I don't advocate that ''entire'' articles must be made accessible to the broadest audience. But lead sections of articles should be expressed in plain English with very little and preferably no jargon. The first sentence or two of an article should not force the reader to almost immediately jump to another page, or pages, to learn the meaning of those first sentences. I see no conflict between--and no reason to avoid--serving a very broad non-expert audience in the lead of an article and serving more specialized readers in the body of the article. [[User:DonFB|DonFB]] ([[User talk:DonFB|talk]]) 00:52, 14 June 2024 (UTC)
::Oh, and I did write [[User:XOR'easter/So, you've decided to write about physics and/or mathematics on Wikipedia|a user essay of my own]] that I intended to be a one-stop shop for physics and math people wanting to get started on Wikipedia (and for Wikipedia generalists who have to deal with mathematicians and physicists showing up). [[User:XOR&#39;easter|XOR&#39;easter]] ([[User talk:XOR&#39;easter|talk]]) 02:30, 18 October 2023 (UTC)
:::Your essay is the main motivation I want to rewrite this page. When I asked what makes people hates Wikipedia, almost all said that Wikipedia's article is so so unreadable. It triggers me a lot that we are spending all of our time verifying the facts, copyediting, debating about inane things when we are spending so little time actually making the text understandable to the lay reader. If the lay reader could not even understand what are we talking about and expert readers are just skimming Wiki articles for citations, then we are writing encyclopedic articles for no one really. Too many articles start with false balance filler:
::::{{!xt|Criticism of Israel is a subject of journalistic and scholarly commentary and research within the scope of international relations theory, expressed in terms of political science}})
:::or punch the reader eyes with jargons for the sake of technical accuracy:
::::{{!xt|Pharmacology is a branch of medicine, biology, and pharmaceutical sciences concerned with drug or medication action, where a drug may be defined as any artificial, natural, or endogenous (from within the body) molecule which exerts a biochemical or physiological effect on the cell, tissue, organ, or organism (sometimes the word pharmacon is used as a term to encompass these endogenous and exogenous bioactive species).}}
:::Yes, I do agree that my rewrite is a bit opinionated. But I want to show in the how-to very clear that readability should be our number 1 priority and why it trumps all other metrics of quality. In my opinion, how-tos needs clear instructions and concrete examples on what to do, and they can be a bit opinionated because it is not an encyclopedic article. [[User:CactiStaccingCrane|CactiStaccingCrane]] ([[User talk:CactiStaccingCrane|talk]]) 13:19, 21 October 2023 (UTC)
::::Perhaps it would be better to add an additional essay that is more explicitly "how to" / more explicitly opinionated; I agree with @[[User:SMcCandlish|SMcCandlish]] that a page called a "guideline" is prone to being mined for "levers for disruptive wikilawyering". –[[user:jacobolus|jacobolus]] [[User_talk:jacobolus|(t)]] 15:29, 21 October 2023 (UTC)
:::::[ below comment rethreaded after extracting tangential idea –[[user:jacobolus|jacobolus]] ]
:::::However, I still do think that this guide should be made more understandable and be more nuanced. The guideline/policy status is pretty arbitrary, we should not follow instructions in pages with template <nowiki>{{guidelines}}</nowiki> and <nowiki>{{policy}}</nowiki> to the letter anyways, because that is against the spirit of the rule. If a person is Wikilawyering then we should get ban of them and not trying to bend our guideline/policy make it needlessly complicated. [[User:CactiStaccingCrane|CactiStaccingCrane]] ([[User talk:CactiStaccingCrane|talk]]) 16:48, 21 October 2023 (UTC)
::::::Sounds nice in theory, but basically never happens.  People can wikilawyer the living F out of everyone for literally years in this sphere before ANI, ArbCom, or AE will do anything about it.  It is very close to impossible to get anyone topic-banned from doing disruptive things that have anything to do with style or article titles. Anything in a guideline that has to do with writing style has to be very, very carefully crafted to avoid providing wikilawyering leverage. PS: I really don't know why this is categorized as an "editing guideline" instead of part of MoS, since it's entirely about the style of writing technical articles. <span style="white-space:nowrap;font-family:'Trebuchet MS'"> — [[User:SMcCandlish|'''SMcCandlish''']] [[User talk:SMcCandlish|☏]] [[Special:Contributions/SMcCandlish|¢]] 😼 </span> 21:33, 21 October 2023 (UTC)
My basic take is that the lede is supposed to summarize the article, in as accessible a way as possible. But if the article is very technical, it means that the lede will probably be technical too. No telling lies also means that some other concepts ("jargon", broadly) must be used. It's true that making things more accessible is a worthy goal, but it's not the only consideration. [[User:Tito Omburo|Tito Omburo]] ([[User talk:Tito Omburo|talk]]) 10:43, 14 June 2024 (UTC)

== Social organizing efforts ==

Alternately, instead of guideline pages, perhaps it would be better to try to start some kind of WikiProject type social group targeted toward lay accessibility of technical content, which could try to encourage / organize collaboration specifically around roaming around locating and improving gratuitously inaccessible pages (especially lead sections), explicitly reviewing technical articles for accessibility, perhaps starting with Vital articles, and/or working with existing WikiProjects related to technical subjects to help them focus on the same. –[[user:jacobolus|jacobolus]]&nbsp;[[User_talk:jacobolus|(t)]] 15:35, 21 October 2023 (UTC)
:That's a great idea. [[User:CactiStaccingCrane|CactiStaccingCrane]] ([[User talk:CactiStaccingCrane|talk]]) 16:41, 21 October 2023 (UTC)
:The ambitious (but perhaps necessary) thing would be to recruit new editors who are enthusiastic about this kind of improvement. [[User:XOR&#39;easter|XOR&#39;easter]] ([[User talk:XOR&#39;easter|talk]]) 17:38, 21 October 2023 (UTC)
::I also think this idea has merit. I have mulled creating a Signpost article on the topic, but have not summoned the necessary energy. A Project would certainly be more systematic and seems as though it would gain more attention. A project also has the potential of marshaling forces needed to counter the likely resistance among technically-educated  editors who know their stuff, but don't always know how or care to translate their knowledge into comprehensible prose in the Introduction of an article. [[User:DonFB|DonFB]] ([[User talk:DonFB|talk]]) 06:09, 24 October 2023 (UTC)
:@[[User:Jacobolus|Jacobolus]], with my [[Wikipedia:WikiProject Council]] hat on, I implore you not to start another group (yet).  It's far better to join an existing group like [[Wikipedia:WikiProject Guild of Copy Editors]], or, if you can't find a relevant one, to gather up all of your best friends and [[WP:REVIVE]] one.  The important point is that you really do have to have at least half a dozen editors involved, or the group won't be able to sustain itself.  If it's just you and maybe one or two other editors, then the infrastructure (e.g., around tagging articles and describing the group's interest areas) will swamp your actual goal. [[User:WhatamIdoing|WhatamIdoing]] ([[User talk:WhatamIdoing|talk]]) 01:03, 31 October 2023 (UTC)
::I certainly don't want to spend a lot of effort on organizing. Some kind of complicated new bureaucratic system "tagging articles" etc. sounds like a pain. Mostly I just don't know any current page(s) or social structure for people discussing or working on this deliberately. So if such a page doesn't exist, it might be worth making one. But if there are existing relevant pages, leaning on those certainly might be better. My general impression is that the typical WikiProject is over-focused on leaving its tags and ratings around, and not focused enough on discussion and concrete collaboration. YMMV. –[[user:jacobolus|jacobolus]]&nbsp;[[User_talk:jacobolus|(t)]] 01:35, 31 October 2023 (UTC)
:::New WikiProjects, in particular, tend to fall into that trap.  
:::[[User:Dhtwiki|Dhtwiki]] could probably tell us whether GOCE would be willing to host such efforts.  There are a few thousand pages in [[:Category:Wikipedia articles that are too technical]].  [https://petscan.wmflabs.org/?interface_language=en&maxlinks=&page_image=any&ns%5B0%5D=1&output_limit=&min_sitelink_count=&show_redirects=both&langs_labels_yes=&manual_list_wiki=&cb_labels_any_l=1&links_to_no=&langs_labels_no=&project=wikipedia&ns%5B1%5D=1&wpiu=any&depth=3&max_age=&referrer_url=&output_compatability=catscan&labels_any=&sparql=&search_wiki=&language=en&search_max_results=500&templates_yes=&negcats=&outlinks_any=&sitelinks_yes=&edits%5Bflagged%5D=both&labels_yes=&labels_no=&search_filter=&ores_prob_to=&combination=subset&sortorder=ascending&categories=Wikipedia_articles_that_are_too_technical%0D%0AWikipedia+articles+needing+copy+edit&cb_labels_yes_l=1&before=&ores_prob_from=&sortby=ns_title&cb_labels_no_l=1&show_soft_redirects=both&langs_labels_any=&regexp_filter=&doit= These 15 articles] are tagged for general copyediting (=GOCE's main concern) as well as jargon, so that might be an easy place to start. [[User:WhatamIdoing|WhatamIdoing]] ([[User talk:WhatamIdoing|talk]]) 01:59, 31 October 2023 (UTC)
::::I myself would be against suddenly adding potentially thousands of articles to our load, as the GOCE has a year-long backlog already, unless doing so resulted in a flood of new copy editors to our ranks that would more than make up for the increased burden. But I don't speak for the guild, and a talk-page discussion there might yield other opinions. The articles marked as "too technical" are often in need of general copy editing even if not marked as such. So, there's definitely an overlap between our aims.

::::I can't be sure what constitutes a "gratuitously inaccessible" article, but this quote, at [[36 Signal Regiment (Canada)]], is a likely candidate: {{tq|The role of 36 Signal Regiment is to force generate combat capable signallers and Communication Information Service (CIS) capabilities to enable command and control in support of Canadian Forces domestic and expeditionary operations.}} Some articles have the explanatory material but it needs to be made clear. You would expect an article named [[Ahaetulla prasina]] to contain recondite terms. However, the attempt to explain "preocular" there {{tq|...preocular scale in front of the eye...}} adds confusion for not having the explanatory text set off. Then there's the attempt to explain by linking to other articles, some of which seem more technical, without being marked as such (compare [[Transactional memory]], linked from [[Advanced Synchronization Facility]]), which suggests that either the former article is appropriately technical (I belive in the possibility of that being the case) or that people just haven't gotten around to tagging it yet. [[User:Dhtwiki|Dhtwiki]] ([[User talk:Dhtwiki|talk]]) 07:46, 31 October 2023 (UTC) (edited 05:41, 11 November 2023 (UTC))

:::::More examples (they are legion!) of knowledgeable editors simply making no attempt to convert jargon/bureaucratese/tech manual lingo into ordinary English words and syntax that would be recognizable to non-specialist readers. Their lack of effort is not malign; they simply don't have the concept of writing for a general non-technical readership—especially in the opening sentence or two—and thus don't do it. Jargon terms are linked to other articles, in which the ledes are laden with more jargon, linked to still more jargony articles...a reader can easily click/tap three, four or more levels deep with no guarantee of clarity, but only an excursion into a wilderness of techno-babble. [[User:DonFB|DonFB]] ([[User talk:DonFB|talk]]) 08:17, 31 October 2023 (UTC)
::::::I agree with everything [[User:DonFB|DonFB]] says here.  However I don't think the answer is to prohibit Wikilinks in the lead, as he [https://en.wikipedia.org/w/index.php?title=Wikipedia_talk%3AMake_technical_articles_understandable&diff=1155661153&oldid=1155105213 advocated].  Discouraging links in the lead is not going to force jargon-obsessed technical editors to write plain-language explanations for general readers, believe me. 
::::::I also don't think another WikiProject is the answer.  We should rewrite the Introduction guideline here to strengthen the need for plain language explanation of jargon.  I would be willing to bet that 95% of the visitors to most technical articles don't read beyond the introduction. --[[User:Chetvorno|Chetvorno]]<sup><small>[[User talk:Chetvorno|<i style="color: Purple;">TALK</i>]]</small></sup> 21:13, 8 November 2023 (UTC)
:::::::I would be open to strengthening the text in [[Wikipedia:Make technical articles understandable#The lead section]] somehow, though to me it seems rather clear already. Do you have thoughts for new phrasing that could augment or replace what currently stands there? [[User:XOR&#39;easter|XOR&#39;easter]] ([[User talk:XOR&#39;easter|talk]]) 21:36, 8 November 2023 (UTC)
:::::::{{tq|i=yes|95% of the visitors to most technical articles don't read beyond the introduction.}} – My impression is that this is true of ''all'' articles, not just technical articles. Which is why ideally the lead section should be a reasonable summary as well as broadly accessible, especially for articles about fundamental concepts. –[[user:jacobolus|jacobolus]] [[User_talk:jacobolus|(t)]] 21:47, 8 November 2023 (UTC)
::::::::Quite right, and that's why my focus has consistently been on lede sections; I don't fret about highly technical text/jargon/formulae/etc within the body of articles. It's to be expected that material there can be challenging. But most people don't get that far, and we need to serve them much better in article intros. [[User:DonFB|DonFB]] ([[User talk:DonFB|talk]]) 22:52, 8 November 2023 (UTC)
:::::::It may be true that most jargon obsessed editors won't desist, but I think other editors should be encouraged and supported by Policy/Guideline to fix problematic ledes. To me, the biggest problem is unfamiliar or unrecognizable jargon, so discouraging its use would seem to be the approach to take. I don't object to links from things like names of places, events, or people; the basic meaning of the text does not depend on knowing their details; those links are a courtesy to readers who want to know more. [[User:DonFB|DonFB]] ([[User talk:DonFB|talk]]) 23:22, 8 November 2023 (UTC)
::::::::The Introduction section already discourages jargon.  But I think most editors are going to say it is impossible to write introductions to technical articles without using the appropriate terminology (i.e. jargon).  That's my opinion too. So the Introduction section should also strongly suggest that jargon terms that must be used be accompanied by brief plain-language definitions. --[[User:Chetvorno|Chetvorno]]<sup><small>[[User talk:Chetvorno|<i style="color: Purple;">TALK</i>]]</small></sup> 01:32, 9 November 2023 (UTC)
:::::::::Maybe what that section of the guideline needs is an example or two. [[User:XOR&#39;easter|XOR&#39;easter]] ([[User talk:XOR&#39;easter|talk]]) 05:56, 9 November 2023 (UTC)

== Should the section on "Introduction to" articles be deprecated (removed)? ==
{{Archive top}}
: ''Discussion closed: no new consensus reached.'' <span class="nowrap">&nbsp;&nbsp; &mdash; ''[[User talk:The Transhumanist|The&nbsp;Transhumanist]]''&nbsp;&nbsp; </span> 11:59, 2 January 2024 (UTC) 

I cannot locate any discussion which resulted in consensus to allow their creation. The section was discussed only once in the past ([[Wikipedia_talk:Make_technical_articles_understandable/Archive_1#"Introduction"_articles]]). That section is clearly in disagreement with [[Wikipedia:REDUNDANTFORK]] policy. And even our section states "the number of separate introductory articles should be kept to a minimum". Well, 0 is the most miminal number we can get. <sub style="border:1px solid #228B22;padding:1px;">[[User:Piotrus|Piotr Konieczny aka Prokonsul Piotrus]]&#124;[[User talk:Piotrus|<span style="color:#7CFC00;background:#006400;"> reply here</span>]]</sub> 03:29, 8 November 2023 (UTC)

:I don't think there's any harm in having a relatively small number of "Intro To" articles. My thought, however, is that the accessible language in the lede section of such articles could just as easily be used as the lede text in the corresponding regular articles, giving the lie, as it were, to the idea that such subjects are too complex or specialized to be summarized in plain English. [[User:DonFB|DonFB]] ([[User talk:DonFB|talk]]) 06:29, 8 November 2023 (UTC)
::You can judge for yourself by examining the examples: [[Special:AllPages/Introduction to]]. Most have eventually been merged into the main page about the topic. Others are still separate: [[Introduction to general relativity|general relativity]], [[Introduction to the mathematics of general relativity|the mathematics of general relativity]], [[Introduction to electromagnetism|electromagnetism]], [[Introduction to entropy|entropy]], [[Introduction to evolution|evolution]], [[Introduction to genetics|genetics]], [[Introduction to viruses|viruses]], [[Introduction to quantum mechanics|quantum mechanics]], [[Introduction to systolic geometry|systolic geometry]], [[Introduction to M-theory|M-theory]], .... If you think that any of those can be merged into the more technical main article without sacrificing precision or clarity for a technical audience, you are welcome to propose it on the relevant talk pages. –[[user:jacobolus|jacobolus]] [[User_talk:jacobolus|(t)]] 06:52, 8 November 2023 (UTC)
:::I recently proposed one for deletion as a fork, only to be told that their separate existence is allowed by this policy. Hence I think we need to start at the root of the problem. Note that I am not opposed to mergers - DonFB makes good point that some simpler language would improve the main articles (in fact, I am familiar with many scholarly studies who say that Wikipedia's biggest problem is readability and such). In fact, effort to make main articles readable should go to the main articles, not those mostly forgotten and hard to find by readers 'introduction to' articles. <sub style="border:1px solid #228B22;padding:1px;">[[User:Piotrus|Piotr Konieczny aka Prokonsul Piotrus]]&#124;[[User talk:Piotrus|<span style="color:#7CFC00;background:#006400;"> reply here</span>]]</sub> 06:55, 8 November 2023 (UTC)
::::Proposing for deletion seems like a drastic and somewhat hostile first step. I think you should start by making a discussion on the talk page of the relevant "introduction to" page and the relevant main article for the same subject, and maybe directly ping the top few authors of the introduction page so they hopefully notice the conversation. If you want to get rid of these articles altogether, perhaps try opening a discussion somewhere like [[Wikipedia talk:WikiProject Physics]], which I would expect to get more readers than this page. –[[user:jacobolus|jacobolus]] [[User_talk:jacobolus|(t)]] 07:03, 8 November 2023 (UTC)
:::::Yes, it would be drastic/hostile to some, but more to our point here it would be actually destructive in costing us good summary material we can use.  I would suggest following [[WP:PM]] process, and tagging them all for merger into their respective main articles, and opening a discussion (on the merge-to article's talk page, not the merge-from article's talk page) for each, mentioning in particular that the more accessible introductory wording at the merge-from page should be used to improve the readability of the main article's lead (otherwise people will just say that the intro article covers the same material as the main one and thus there is nothing to merge). I agree with the OP point that there is no consensus to have this guideline suggesting the creation of such articles in the first place. <span style="white-space:nowrap;font-family:'Trebuchet MS'"> — [[User:SMcCandlish|'''SMcCandlish''']] [[User talk:SMcCandlish|☏]] [[Special:Contributions/SMcCandlish|¢]] 😼 </span> 14:30, 8 November 2023 (UTC)
::::::Please don't "tag them all for merger". Go start a conversation instead of trying to browbeat people with bureaucratic processes and eyesore banners. Edit: and please do one at a time instead of trying to do this in mass. Note that at least [[Introduction to viruses]] is a featured article, so people are likely to be resistant to breaking it based on one person's personal preference. –[[user:jacobolus|jacobolus]] [[User_talk:jacobolus|(t)]] 14:48, 8 November 2023 (UTC)
:::::::Why do you have to turn everything into a [[WP:BATTLEGROUND]] even when people are mostly agreeing with you?  Your attitude on page after page is out-of-the-blue blowhard hostility like this, directed at anyone who diverges even slightly from your own ideas or preferences, and it's completely corrosive to consensus formation, in every discussion in which I encounter you.{{pb}}We have a process for doing mergers. That process ensures that they are handled consistently and that notices of them appear in a centralized listing for community review. If you don't like merger process (which, {{em|guess what}}, ensures that the conversations you want to see are in fact opened instead of someone proposing a merge a with a tag, doing no discussion, and then making the merge as if they have consensus), then don't participate in it and go find something else to do. <span style="white-space:nowrap;font-family:'Trebuchet MS'"> — [[User:SMcCandlish|'''SMcCandlish''']] [[User talk:SMcCandlish|☏]] [[Special:Contributions/SMcCandlish|¢]] 😼 </span> 15:42, 8 November 2023 (UTC)
::::::::Dude, WTF is your problem? We were all having a polite conversation here. Please keep your gratuitous insults to yourself. –[[user:jacobolus|jacobolus]] [[User_talk:jacobolus|(t)]] 15:52, 8 November 2023 (UTC)
:::::::::Yes, we were having a polite conversation until {{em|you}} turned it on its ear with a rant about browbeating and bureaucracy and eyesores after someone simply recommended actual standard practice.{{pb}}Back to the substance of the matter: There are multiple ways to approach this, but the most practical appears to me to be to identify the intro articles that are least useful as stand-alone articles and propose those mergers first. One article with a title like this being an FA is an unusual outlier, and might need to be approached differently. It might even turn out in the long run that there will emerge a consensus to keep some articles like this separate, but we'll never know until we start going through merge discussions and seeing how they turn out and why. <span style="white-space:nowrap;font-family:'Trebuchet MS'"> — [[User:SMcCandlish|'''SMcCandlish''']] [[User talk:SMcCandlish|☏]] [[Special:Contributions/SMcCandlish|¢]] 😼 </span> 16:07, 8 November 2023 (UTC)
::::::::::If you start by threatening to smash people's articles apart without even bothering to figure out why they exist in the first place or what people like about them, you'll get a lot of resistance, probably even more than the resistance you'll get by diving into other people's conversations and slinging off-topic insults. –[[user:jacobolus|jacobolus]] [[User_talk:jacobolus|(t)]] 16:33, 8 November 2023 (UTC)
:::::::::::Just more battlegroundy ranting. Did you have something constructive to input with regard to this set of articles and how to go about opening the discussions we both clearly want to happen (again, it is not constructive to go off on people who don't actually disagree with you), since you don't find my idea to your liking? <span style="white-space:nowrap;font-family:'Trebuchet MS'"> — [[User:SMcCandlish|'''SMcCandlish''']] [[User talk:SMcCandlish|☏]] [[Special:Contributions/SMcCandlish|¢]] 😼 </span> 17:25, 8 November 2023 (UTC)
::::::::::::Please desist now. Your insults are increasingly tiresome.
::::::::::::{{tq|i=yes|both clearly want to happen}} – No, I think starting aggressive conversations about this is a waste of time, and I personally don't care one way or the other about these "introduction" articles. I was merely advising the [[user:Piotrus]] to take a measured, open-minded, and consensus-seeking approach to whatever conversations they try to start, rather than trying to pick fights. –[[user:jacobolus|jacobolus]] [[User_talk:jacobolus|(t)]] 17:41, 8 November 2023 (UTC)
:::::::::::::And I've advised engaging in the actually prescribed process (which is not "aggressive" in any way, but designed to prevent problems like doing unilateral merges) for opening such consensus-seeking discussions about this sort of case in the first place, about which {{em|you've}} picked an aggressive fight right from the start. I trust Piotrus will figure out what to do. I won't respond to you further on this because I can't see anything constructive coming from it. <span style="white-space:nowrap;font-family:'Trebuchet MS'"> — [[User:SMcCandlish|'''SMcCandlish''']] [[User talk:SMcCandlish|☏]] [[Special:Contributions/SMcCandlish|¢]] 😼 </span> 17:53, 8 November 2023 (UTC)
::::::::::::::Tacking a "I threaten to slash your article up and delete its current page in X days unless you mount an immediate defense" banner across the top of pages is a hostile and incredibly obnoxious first step in dealing with work that other people put a lot of time and effort into. It's not an appropriate use of the merge banners, which are intended for cases where e.g. a few short and mediocre articles duplicate the same content. It would cause much less drama to start a gentle conversation on the talk page (probably of the main article rather than the "introduction to" article, but with a link from both) in a single one of these cases, and explicitly ping whichever editors put the bulk of the work int "introduction to..." article and maybe also some of the top contributors to the main article, providing whatever arguments or evidence for why you think readers would benefit from having a more accessible "main" page and why the content from the "introduction" article would fit well there, and then sit back and see what people have to say when they aren't under threat. For the most convincing proposal, do the content merge yourself and put it in user space somewhere, so that other contributors have something concrete to compare.
::::::::::::::Nobody is trying to fight you buddy. Please cut the crap. –[[user:jacobolus|jacobolus]] [[User_talk:jacobolus|(t)]] 18:11, 8 November 2023 (UTC)
:::::::::::::::I'm trying to follow your discussion here, but I'm not sure what the conflict is. Is it to delete the "Introduction to..." section on this page? or actually propose merging all "Introduction to..." articles?   Maybe we could ask for outside comment? --[[User:Chetvorno|Chetvorno]]<sup><small>[[User talk:Chetvorno|<i style="color: Purple;">TALK</i>]]</small></sup> 18:29, 8 November 2023 (UTC)
::::{{dedent|11}} @[[User:Chetvorno|Chetvorno]]: Looking into this a bit more, [[User:Piotrus|Piotrus]] made a proposed deletion of [[Introduction to M-theory]] with a somewhat unfriendly proposal at [[Wikipedia:Articles for deletion/Introduction to M-theory (2nd nomination)]]. Most of the folks at that discussion were opposed to the deletion, but folks on both sides of the discussion pointed to this [[Wikipedia:Make technical articles understandable]] guideline as a justification. I think Piotrus's idea here is that if they can change the text here, then that will give them an argument to leverage in future similar deletion discussions. It would have been nice if this discussion started with that context though. –[[user:jacobolus|jacobolus]] [[User_talk:jacobolus|(t)]] 18:46, 8 November 2023 (UTC)
:::::More or less. Note that it is perfectly fine to have a deletion discuussion end in a merge verdict, and it takes usually less time and attracts more (and less partisan) comments than many merge discussions do. <sub style="border:1px solid #228B22;padding:1px;">[[User:Piotrus|Piotr Konieczny aka Prokonsul Piotrus]]&#124;[[User talk:Piotrus|<span style="color:#7CFC00;background:#006400;"> reply here</span>]]</sub> 02:30, 9 November 2023 (UTC)
::::::"Taking less time" doesn't seem like a very important criterion to me. The goal should be to get to a result which leaves people satisfied (including whoever put the work into the articles you want to delete/merge) and best helps readers of the encyclopedia to find the information they are looking for and best helps the Wikipedia project as a whole and the specific articles in question to flourish. Not just to most efficiently enforce your own personal preferences. –[[user:jacobolus|jacobolus]] [[User_talk:jacobolus|(t)]] 05:59, 9 November 2023 (UTC)
:::::::[[WP:BEFORE]] says to {{tq|consider merging or redirecting to an existing article}} before starting a deletion discussion, and [[WP:AFDHOWTO]] says to {{tq|Use [[Wikipedia:Proposed mergers]] for discussion of mergers.}} I think starting an AfD when the nominator clearly has merging in mind to begin with is somewhat frowned upon. It can come across as using the wrong venue, and it can seem more confrontational than necessary. {{pb}} In the present case, we're not talking about paid promotions, attack pages about living people, or any of the other kinds of material that we really should remove as quickly as possible. At worst, the pages in question here are cruft. The time pressure for dealing with such things is comparatively low. [[User:XOR&#39;easter|XOR&#39;easter]] ([[User talk:XOR&#39;easter|talk]]) 06:29, 9 November 2023 (UTC)
:There's nothing wrong with the advice currently given in the section in question. Really. It's fine. It doesn't conflict with any policies. [[WP:REDUNDANTFORK]] is a guideline, not a policy; but it doesn't conflict with that, either. A less technical introduction to a topic is not redundant with a fully technical treatment of it. They are not {{tq|about the exact same thing}}: one is about the heavy-duty math, and the other is about the analogies invented to convey something about the heavy-duty math. Having an "Introduction to..." article is morally no different from taking an overlong "History" section in an article and spinning it off into its own "History of..." page. Whether an "Introduction to..." article ''ought'' to exist for any given topic is a thing we can decide on a case-by-case basis. For example, when it comes to pop science about the frontiers of physics, there is a vast amount of technical literature ''and'' a big pile of popularized writing. That makes the existence of a separate "Introduction to..." arguably warranted. Moreover, the {{tq|0 is the most miminal number we can get}} remark is an argument that presumes its own conclusion. If "Introduction to..." articles are helpful ''in any circumstance,'' then having zero of them would not be the minimal number, but an ''insufficient'' number. [[User:XOR&#39;easter|XOR&#39;easter]] ([[User talk:XOR&#39;easter|talk]]) 21:09, 8 November 2023 (UTC)
:I largely agree with XOR'easter on taking these case by case.<br />One way to look at it is this: Most articles of sufficiently length have a lead that is a summary of the longer article. However, if the lead can't capture the "introduction to" aspect due to the level of understanding required to ''introduce'' the topic, and the article would benefit from a "middle level" of summary between lead and full article, one way to solve that problem is with an "Introduction to" style article.<br />Another way to look at this is as the general/specialized idea from [[WP:5P1|the first pillar]]. In some cases the article that would be in a specialist encyclopedia differs vastly from the one that would exist in a general encyclopedia, and that too might sometimes be solved by an "Introduction to" style article. &mdash;[[User:Siroxo|siro]][[User talk:Siroxo|''&chi;'']][[Special:Contributions/Siroxo|o]] 05:50, 9 November 2023 (UTC)
: '''How''' are "Introduction to" articles different from articles over at the Simple English Wikipedia about the root subject? <span class="nowrap">&nbsp;&nbsp; &mdash; ''[[User talk:The Transhumanist|The&nbsp;Transhumanist]]''&nbsp;&nbsp; </span> 00:38, 13 November 2023 (UTC)
::The most obvious difference is that they are not written in "Simple English", and that most of the Simple English articles never saw much serious effort put into them. But there are only a handful of "introduction to" articles, so you can easily compare for yourself the English wiki article, "intro" article, and "simple English" article: {{nobr|[[general relativity]] ([[Introduction to general relativity|intro]], [[:simple:general relativity|simple]]);}} {{nobr|[[mathematics of general relativity]] ([[Introduction to the mathematics of general relativity|intro]]);}} {{nobr|[[electromagnetism]] ([[Introduction to electromagnetism|intro]], [[:simple:electromagnetism|simple]]);}} {{nobr|[[entropy]] ([[Introduction to entropy|intro]], [[:simple:entropy|simple]]);}} {{nobr|[[evolution]] ([[Introduction to evolution|intro]], [[:simple:evolution|simple]]);}} {{nobr|[[genetics]] ([[Introduction to genetics|intro]], [[:simple:genetics|simple]]);}} {{nobr|[[virus]] ([[Introduction to viruses|intro]], [[:simple:virus|simple]]);}} {{nobr|[[quantum mechanics]] ([[Introduction to quantum mechanics|intro]], [[:simple:quantum mechanics|simple]]);}} {{nobr|[[systolic geometry]] ([[Introduction to systolic geometry|intro]]);}} {{nobr|[[M-theory]] ([[Introduction to M-theory|intro]], [[:simple:M-theory|simple]]).}} –[[user:jacobolus|jacobolus]] [[User_talk:jacobolus|(t)]] 02:15, 13 November 2023 (UTC)
:::The very fact that there are so few of them is a strong indicator that the Wikipedia community does not consider them a good idea. That they are confined to a small number of topics strongly suggests they are the product of a small handful of editors who decided on their own they were a good idea. I'm reminded of some other boondoggles of this sort, like that spate of creating unmaintainable thousands of portals for too-narrow topics, which later got mass deleted. This "Introduction to {{var|foo}}" series seems to be loosely inspired by the "Index of {{var|foo}} articles" series, but lacking the community buy-in to develop it that the index series has. This, plus the fact that the easier-reading language in at least several of the introduction articles would be lead improvements at main articles, is why I like the idea of merging them into main articles. <span style="white-space:nowrap;font-family:'Trebuchet MS'"> — [[User:SMcCandlish|'''SMcCandlish''']] [[User talk:SMcCandlish|☏]] [[Special:Contributions/SMcCandlish|¢]] 😼 </span> 05:12, 13 November 2023 (UTC)
::::If you think any one of these in particular would be better merged, nobody's stopping you from putting in the work to write the merged article and then try to convince the rest of "the Wikipedia community" that your version is better. –[[user:jacobolus|jacobolus]] [[User_talk:jacobolus|(t)]] 05:36, 13 November 2023 (UTC)
:::::For someone that professes to no longer want to be in an argument with me, you sure seem to expend a lot of energy trying to bait one. This is a discussion, for everyone one; it's not an "I don't like you, so buzz off until you do busywork to personally satsify me (so I can just crap all over it anyway just to stick it to you)" personal social media page of yours. <span style="white-space:nowrap;font-family:'Trebuchet MS'"> — [[User:SMcCandlish|'''SMcCandlish''']] [[User talk:SMcCandlish|☏]] [[Special:Contributions/SMcCandlish|¢]] 😼 </span> 06:49, 13 November 2023 (UTC)
::::::Your proposal is more or less "I don't like this so someone else should go fix it for me". My proposal is: why don't you try to put your own effort where your mouth is? I'm not just trying to harass you; without actually trying to do this, I think you are entirely misunderstanding what these articles are trying to accomplish and grossly underestimating how much work it would take to re-organize them a different way. The only way to get past that is to actually meaningfully engage with the content, rather than having handwaving meta-discussions from the sideline somewhere. –[[user:jacobolus|jacobolus]] [[User_talk:jacobolus|(t)]] 17:44, 13 November 2023 (UTC)
::::::Also, I never said I didn't like you, or that you should "buzz off", or that anyone should "crap" on anything, and nobody wants to "stick it" to you. I earlier asked you what your problem was when you launched a heap of gratuitous off-topic insults at me. I still don't really understand what your problem is as you continue with the hostile and insulting language. I would again urge you to stop. It's distracting to everyone here, counterproductive, and tiresome. –[[user:jacobolus|jacobolus]] [[User_talk:jacobolus|(t)]] 17:52, 13 November 2023 (UTC)
:::::::Lots more fight-bait, that I will resist. "I don't like this so someone else should go fix it for me" bears no resemblance to anything I've said. What we have is largely redundant articles that are disused by our readers and do not form a coherent set or category, a consistent editorial approach, but which nevertheless have very valuable content that is often better than what is in main articles (or at least could be used as high-level summary in leads, with more detailed/jargony presentations moved down into article bodies; there's not a binary false dilemma here). My "proposal" is that we need to have a discussion to decide what to do with these articles and more importantly the content in them (either as a class, or mostly as a class with some special cases). I happen to lean toward merging them into main articles on the same topic, for reasoning I've already explained quite clearly, and which you have not substantively addressed. But for all I know, we'd instead emerge with a consensus that such articles are ideal and we need more of them, in a systematic way. Hard to be sure until the discussion proceeds without being trainwrecked.{{pb}}{{em|Lots of things at WP are hard}}; that doesn't mean we don't do them when they're the sensible thing to do. I'm entirely aware how difficult a good-quality merge (or split) is with complex material, as I perform them in topics in which I have significant competence. I'm perfectly willing to help in some of these cases, but I'm not certain my attempts to help would be useful to or wanted by people who are actual subject-matter experts in these specialties, and running off to do an amateurish job at one of them as a "demo" would probably do more harm than good. (In the more complex topics at which I am highly competent, I can imagine the poor results of someone "casual" in that subject trying to do merge or split operations, and the picture isn't pretty.) Your suggestion that I should just go off and do it all myself comes off as silly trolling and an attempt to derail a discussion which may have an outcome that isn't the "do nothing" one you favor. So, no, I will not be entertaining that idea, and I'm not going to respond to further fight-picking in that direction (or, if I can help it, any other ones). Your central premise boils down to the idea that my view is irrelevant (or worse) because I'm not likely the one to get the bulk of the job done. But everyone here – including you – knows that's fallacious. So is the idea that we can't look at content A and content B and imagine them merged without someone actually doing the merge. <span style="white-space:nowrap;font-family:'Trebuchet MS'"> — [[User:SMcCandlish|'''SMcCandlish''']] [[User talk:SMcCandlish|☏]] [[Special:Contributions/SMcCandlish|¢]] 😼 </span> 18:29, 13 November 2023 (UTC)
::::::::I'm telling you that these articles are not "largely redundant", which you would quickly see for yourself if you bothered to go look at them. Some of them (maybe all of them) could plausibly be merged, or reorganized and split up some other way, but it's not a priori obvious that the merged article would be an improvement, and abstractly hand-waving about it is thoroughly unconvincing.
::::::::{{tq|i=yes|My "proposal" is that we need to have a discussion to decide what to do with these articles}} – and my counter-claim is that this is a naïve discussion doomed to failure until its proponents try to concretely engage with the content.
::::::::{{tq|i=yes|not certain my attempts to help would be useful to or wanted by people who are actual subject-matter experts in these specialties}} – in that case, the appropriate thing to do is go start a specific discussion on a particular page and try to convince these experts that this is a good idea in at least one specific case, or recruit one of them to concretely try this out.
::::::::Otherwise, the way I'm imagining this discussion to proceed if you get your way is some kind of bureaucratic mandate (if taken to some bigger forum, maybe backed by a drive-by "consensus" of people who don't intend to work on any of the articles in question) that ends up raining down on a bunch of people who never asked for it. I think that would be actively harmful to the project. –[[user:jacobolus|jacobolus]] [[User_talk:jacobolus|(t)]] 18:50, 13 November 2023 (UTC)
:::::::::Thanks for engaging; this is more substantive. Rather than repeat the same thing in two spots, I'll try addressing this with the quantum mechanics example, in reply to XOR'easter below. <span style="white-space:nowrap;font-family:'Trebuchet MS'"> — [[User:SMcCandlish|'''SMcCandlish''']] [[User talk:SMcCandlish|☏]] [[Special:Contributions/SMcCandlish|¢]] 😼 </span> 21:06, 13 November 2023 (UTC)
::::I don't think we can take {{tq|very fact that there are so few of them}} as an indicator of much anything, really. They are ''hard'' to write, and the people with the knowledge to do the job are (in my experience) more inclined to work on niche topics at a higher level. But being a low priority doesn't make them a bad idea or one that the community has rejected. [[User:XOR&#39;easter|XOR&#39;easter]] ([[User talk:XOR&#39;easter|talk]]) 17:14, 13 November 2023 (UTC)
:::::Fair enough, but they don't seem to be something the community is taking up. I'm not sure that's a hair worth splitting very far. Maybe more to the point, these articles are not easy to notice and are disused, so they don't seem to be serving their purpose. The material in them is what is of value, and I would think that the argument to merge that material into the main articles on the topic is pretty compelling, both for getting the material in front of more eyeballs and for making the main articles easier for more readers to parse in the first place. <span style="white-space:nowrap;font-family:'Trebuchet MS'"> — [[User:SMcCandlish|'''SMcCandlish''']] [[User talk:SMcCandlish|☏]] [[Special:Contributions/SMcCandlish|¢]] 😼 </span> 17:29, 13 November 2023 (UTC)
::::::I've advocated for plenty of merges in my day, and I have run into a few different highly-technical corners of the encyclopedia where I thought we'd be better off with fewer and larger articles. But at the same time, I believe that some splits are sensible. To revisit an example I mentioned above: [[Quantum mechanics]] is a hard subject, for instance, and trying to cover all the twists and turns of its historical development while also explaining the subject as taught today is a really big job. Spinning off [[History of quantum mechanics]] while leaving behind a [[Quantum mechanics#History|synopsis in the main article]] makes organizational sense. Of course, the main article gets much more traffic: 1.5 million annual page views versus less than 100,000 [https://pageviews.wmcloud.org/?project=en.wikipedia.org&platform=all-access&agent=user&redirects=0&start=2022-11&end=2023-10&pages=Quantum_mechanics|History_of_quantum_mechanics]. Does that mean we should try attracting more attention to the history spin-off page? Plausibly yes. Does the traffic disparity invalidate the idea of having the spin-off page in the first place? No, I don't think it can. [[User:XOR&#39;easter|XOR&#39;easter]] ([[User talk:XOR&#39;easter|talk]]) 18:07, 13 November 2023 (UTC)
:::::::Sure, but how does that relate to [[Introduction to quantum mechanics]] largely serving the same basic purpose as [[Quantum mechanics]] and covering much of the same ground? All of our top-level articles on all subjects are basically encyclopedic introductions to them, with non-introductory drill-downs like [[History of quantum mechanics]], [[Mathematical formulation of quantum mechanics]], [[Applications of quantum mechanics]], [[Interpretations of quantum mechanics]], broken out to split-off articles. [[Introduction to quantum mechanics]] reads to me like a better-worded version of some of the material in [[Quantum mechanics]], the latter of which could be improved by using much of the wording in the former, without losing the detail in many of the latter's sections. The former even has a history-of section and applications section, etc., while also breaking some of the more technical aspects into easily digestible sections or subsections. Just seems like a tremendous amount of effort to basically produce a [[WP:CFORK]] that in certain ways is superior to what it forked from (though missing a lot), but which would be even better in re-combined form.  When I look at other intro-to articles, I'm seeing a similar pattern.  But, flipping this around, if we become sure that the intro-to articles are a great idea, then why aren't we doing lots more of them, with a systematic approach to it? It doesn't seem very practical to just do this very, very spottily at a handful of subjects.  I'm inclined toward thinking it's either not a good idea, and should result in merges, or that it something that should become a standardized part of our encyclopedic approach, isntead of being a rare and kind or random "mutant". (And, yes, I lean toward the former; I guess that makes me [[meta:Mergist]] in some sense, though this isn't really about "major" versus "minor" topics, more like "comprehensive" versus "basic" approaches to how to write core/introductory material in an encyclopedia.) <span style="white-space:nowrap;font-family:'Trebuchet MS'"> — [[User:SMcCandlish|'''SMcCandlish''']] [[User talk:SMcCandlish|☏]] [[Special:Contributions/SMcCandlish|¢]] 😼 </span> 21:06, 13 November 2023 (UTC)
::::::::I tried to skim both [[introduction to quantum mechanics]] and [[quantum mechanics]] with a medium level of care (definitely not a detailed close read), and my strong impression is that these two articles are almost entirely different, serving different audiences with largely different needs. [[introduction to quantum mechanics|Intro QM]] is entirely non-mathematical and makes up non-technical pseudo-examples to introduce some of the main concepts which have a lot of prerequisites to tackle as found in even the simplest examples in a college textbook, while [[quantum mechanics|QM]] is full of tensor products of Hilbert spaces, the time evolution of quantum states, commutation relations, Fourier transforms, unitary matrices, Gaussian wave packets, etc. If you try to merge the articles, the intended audience for one of the two is going to end up in trouble: either (a) the intended audience of [[introduction to quantum mechanics|intro QM]] is going to be left baffled by an article too full of formulas and advanced concepts for them to follow, or (b) much of the technical content will be stripped out and more expert readers will need to go somewhere else to figure out how to find answers to more technical questions. –[[user:jacobolus|jacobolus]] [[User_talk:jacobolus|(t)]] 22:05, 13 November 2023 (UTC)
::::::::To echo the above reply: [[Quantum mechanics]] and [[Introduction to quantum mechanics]] ''don't'' serve {{tq|the same basic purpose}}. And as to why we don't have more "Introduction to..." articles? Well, quite possibly we ''should,'' but people need to be motivated to do it. I think that improving the main articles on big subjects and judiciously creating less-technical offshoots would both be beneficial. However, the volunteers with the expertise necessary all have a thousand and one other things demanding their time. [[User:XOR&#39;easter|XOR&#39;easter]] ([[User talk:XOR&#39;easter|talk]]) 22:34, 13 November 2023 (UTC)
:::::::::I guess I don't see a problem with writing one paragraph that begins with something like "In simple terms, ..." then gives the non-mathematical analogies, followed by "More technically, ..." and the more proper examples with actual math in them. Readers of both sorts would quickly learn to skip over the parts that don't directly address their needs.  I'm left wondering, if these "Intro to" articles are meant to be extra-basic, even more so than our main articles, then why are they at this project instead of at Simple (with whatever wording tweaks would be needed there), or at Wikiversity as part of an intro to science topics course, or at Wikibooks in an e-book form. It's just weird and counterproductive, to me, for en.WP to be hosting competing articles that serve as topical introductions.  Maybe that's just too bad and there's nothing to to done for it. But I'm skeptical that this is the only answer the community could come up with. <span style="white-space:nowrap;font-family:'Trebuchet MS'"> — [[User:SMcCandlish|'''SMcCandlish''']] [[User talk:SMcCandlish|☏]] [[Special:Contributions/SMcCandlish|¢]] 😼 </span> 22:51, 13 November 2023 (UTC)
::::::::::I don't really know or care anything about the Simple English encyclopedia; I've never found anything there remotely useful, but I'm entirely outside the intended audience. YMMV. Both of these articles seem clearly encyclopedic, and neither really belongs at Wikibooks or wherever. I don't think "extra basic" is a fair summary here; I would say that the [[Introduction to quantum mechanics|intro QM]] article is at about the normal level for Wikipedia, while the [[quantum mechanics]] article is pitched about at the level of a 2nd–3rd year undergraduate physics major. In my opinion these articles are not really "competing". There's definitely ''some'' overlap in topic and duplication of substance, but that's a routine part of any cluster of related Wikipedia articles, and doesn't seem to me like a problem. I think the main problem I have with the "introduction to" articles is that they aren't very well publicized (e.g. they don't get any love from search engines, aren't commonly the target of wikilinks, etc.) and many readers who would benefit probably never come across them. –[[user:jacobolus|jacobolus]] [[User_talk:jacobolus|(t)]] 22:56, 13 November 2023 (UTC)
::::::::::Even at a non-technical level, one paragraph often doesn't cut it. People write whole books trying to explain quantum mechanics, or even just part of quantum mechanics, to the lay audience. {{pb}} Shuffling the "Introduction to..." material off to other projects would just reduce their readership further (30-day page views of Simple English Wikipedia's quantum mechanics article: 1,691) while removing them from the attention of most editors who can improve them. [[User:XOR&#39;easter|XOR&#39;easter]] ([[User talk:XOR&#39;easter|talk]]) 23:00, 13 November 2023 (UTC)
:::::::::::Alright, so why isn't the intro article the main article (perhaps with some additional [[WP:SUMMARY]] bits to account for all the side topics), then what is presently the main article divided out into more technical articles? That is, if the present main article requires one to be a 2nd-year physics undergrad, then it's probably not a properly written main article for WP. I think that comes full-circle back to the original "make technical articles understandable" theme. If the main article is inappropriately technical (and it seems like it is), yet we have a well-written introductory article that isn't, then ... You see where I'm going with this.  Maybe various technical topics naturally attract an "increasing geekery over time" problem at their main articles and need to be rewritten periodically, with more difficult material moved back out to sub-topical articles. If so, these intro articles might serve as good starting points for doing such redrafts.  I'm not really convinced that we're permanently stuck with main articles that can't be understood by people who aren't half-way through university, especially when the "Intro to" articles provide counter-evidence, showing that we can write the material simpler without it being something to push off to Simple.Wikipedia. <span style="white-space:nowrap;font-family:'Trebuchet MS'"> — [[User:SMcCandlish|'''SMcCandlish''']] [[User talk:SMcCandlish|☏]] [[Special:Contributions/SMcCandlish|¢]] 😼 </span> 23:46, 13 November 2023 (UTC)
::::::::::::I don't think it's inappropriately technical overall (though I'm sure improvements could be made to some sections). It's an inherently difficult subject that requires a lot of math to engage with in a real/serious way. –[[user:jacobolus|jacobolus]] [[User_talk:jacobolus|(t)]] 00:52, 14 November 2023 (UTC)
:::::::::::::I guess the "real/serious" part is the sticking point, then. If the "Intro to" articles are not "real/serious", then are they proper encyclopedia articles? I guess I'm just having difficulties with the "have it both ways" thing here. If they are real/serious enough to keep, then they would seem to almost encessarily be real/serious enough to be (or be the basis of) the main articles for their topics, but if they're not real/serious enough for that, then maybe they don't belong here at all. (That may sound deletionist, but I mean it in a mergist way: blend the most basic with the collegiate-level basic). With that, I fear I'm getting repetitive, and I don't want to be one of those people who just recycles the same argument over and over and doesn't seem to be hearing anyone.  I've laid out what I see as concerns and rationales and possibilities, and either they'll have a useful effect or they won't. <span style="white-space:nowrap;font-family:'Trebuchet MS'"> — [[User:SMcCandlish|'''SMcCandlish''']] [[User talk:SMcCandlish|☏]] [[Special:Contributions/SMcCandlish|¢]] 😼 </span> 01:20, 14 November 2023 (UTC)
::::::::::::::The whole point of having 2 separate articles is to try to "have it both ways" so that non-technical readers can learn about the subject without encountering a wall of math but technical readers can still learn the full story. Trying to cram everything together has a high chance of hurting one audience or the other.
::::::::::::::If you think these articles should be merged, I think you'd get a better sense of where the people who deeply care about this stand by starting a discussion at [[talk:quantum mechanics]] or [[Wikipedia talk:WikiProject Physics]] rather than here. I am not a physicist (I took an undergrad QM course, but that's as far as I got), and can't tell you clearly what the take is of people who have worked on writing these pages. –[[user:jacobolus|jacobolus]] [[User_talk:jacobolus|(t)]] 01:46, 14 November 2023 (UTC)
:::::::::::::::It all sounds nice until we realize that what we have are CONTENTFORKS, except that instead of "I will write the article from correct POV" we have "I will write the article in a friendlier, simpler way".  Now, as I said before, I agree our technical articles are often too technical (many studies on quality of Wikipedia say so, noting that readability of Wikipedia is worse than that of our traditional competitors). But creating forks is not the way to do so, and it is self defeating - majority of readers will look at article on quantum mechanics, next to nobody will click through to Introduction (or Simple English wiki). Efforts should be spent on inproving readability of main articles, and frankly, my dislike for the Introduction...and Simple English wiki stems from the fact that well meaning editors, doing importnat stuff (writing stuff in a simple way, which is what we need) are funneled off to those low-visibility articles. We need to direct our efforts to improving the main article, not semi-hidden forks or spin-offs, and if those forks hurt our project by diverting edits, that's a good reason to ensure they don't exist (as they should not, per CONTENTFORK anyway, which is a very good policy). <sub style="border:1px solid #228B22;padding:1px;">[[User:Piotrus|Piotr Konieczny aka Prokonsul Piotrus]]&#124;[[User talk:Piotrus|<span style="color:#7CFC00;background:#006400;"> reply here</span>]]</sub> 03:37, 14 November 2023 (UTC)

{{od}}
I think the issue of whether to have or to merge Intro To articles, which are not very numerous, is a much less pressing matter than fixing the readability-challenged ledes of scads of existing main articles, many on recognizable subjects. I'm not opposed to Intro To, but it does not appear there will be a big increase in their number anytime soon. That's unfortunate, because, in my opinion, they represent the level of information and clarity of language that this or any general readership encyclopedia should offer. Obviously, they are a reaction to the default editing approach that turned many of the so-called main articles on tech/science/math into pseudo-textbook material. Wikipedia, we know, is not supposed to be a [[WP:NOTTEXTBOOK|textbook]] or something like it, but that's what a lot of these articles seem to aspire to. I am not, however, urging a campaign to write more Intro To articles, though if people want to do that, more power to them. 

Meanwhile, the problem of difficult lede sections continues mostly unabated, and that's where I think attention and effort should be focused. I wonder if improving only the lede/intro sections of a lot of articles, especially in science/math/tech, could improve Wikipedia's readability reputation, even without taking on the task of making entire articles more accessible. I hasten to add, though, that clearing up ledes should be done for its own sake, not merely to help the site's reputation, but because doing so will truly serve the readership. As suggested earlier, the language and style of the relatively few Intro To articles can be used to help ameliorate overly dense, jargony ledes in the corresponding main articles. But beyond that relatively small number, there's still a vast corpus of other articles that need plain English revision of their lede sections. [[User:DonFB|DonFB]] ([[User talk:DonFB|talk]]) 05:26, 14 November 2023 (UTC)

:Yes, having the best possible opening paragraph for [[Wikipedia:Vital_articles#Science_(211_articles)|these]] and [[Wikipedia:Vital_articles#Mathematics_(45_articles)|these]] would be a great start. [[User:XOR&#39;easter|XOR&#39;easter]] ([[User talk:XOR&#39;easter|talk]]) 14:04, 14 November 2023 (UTC)

::The idea of having "Intro to ..." articles is fine. There could be more of them. Many existing articles could/should be split: my pet peeve are the articles, the first half of which is some topic presented at a pop-sci level, followed by a "Too technical" banner, followed by the actual meat of the matter that is actually interesting to subject matter experts (e.g. me). A typical variant of this is seen in the comments on the talk pages, where pop-sci readers get into an article, are clearly in over their heads, don't understand basic mathematical notation, and then complain about wikipedia not being understandable. The attempts to fix this result are some pretty schizophrenic articles, trying to simultaneously accommodate both casual readers and technical experts. Compare this to the popular "Explain it like I'm five" youtube videos, which show exactly how different audiences can be addressed. Long term, this seems to be the correct direction; there needs to be a way of serving both sophisticated and unsophisticated audiences. Overall, I agree w/ remarks from XOReaster and jacobolus in discussions above. [[Special:Contributions/67.198.37.16|67.198.37.16]] ([[User talk:67.198.37.16|talk]]) 06:58, 15 November 2023 (UTC)

::: Interesting discussion. Here are my observations and opinions:<br>"Introduction to" articles are included as acceptable content forks at [[WP:CFORK]], buried in the ''[[WP:RELAR|Related articles]]'' section. So, if anyone wants to deprecate intros, it will need to be handled there as well.<br>As long as we have intro articles, the section at [[WP:CFORK]] that includes them should be updated so that they aren't easily missed, such as by giving them their own subheading to make them more easily spotted.<br>The two chronic bashers above should work out a strategy between them to interact while abiding by [[WP:CIVIL]].<br>Introduction articles should remain an acceptable type of content fork, because they serve a definite need amongst WP's readers, but this aspect is best discussed on the talk page of the corresponding guideline.<br>In the intermediate term, in IT development time, say, 2 years, generative AI will likely be available to effectively explain thickly jargonized and complex topics in simpler language.<br>To increase readership of the intro articles, rather than just giving them a hatnote at the top of the root article, or an entry in its ''See also'' section, providing a section along with a {{tl|Main}} link may help to drive traffic to these.<br>One possible solution to the problem of general search engines not driving traffic to articles such as these, would be for the WikiMedia foundation to sponsor a community-driven search engine project, perhaps with a community-edited web-directory/bookmark-library/link-list integrated into it. This is a blatant major gap in its family of projects.<br>Based on the above discussion, it doesn't look like new consensus has been arrived at, and that this discussion should probably be archived.<br>Sincerely, <span class="nowrap">&nbsp;&nbsp; &mdash; ''[[User talk:The Transhumanist|The&nbsp;Transhumanist]]''&nbsp;&nbsp; </span> 11:54, 2 January 2024 (UTC)

{{Archive bottom}}

== Answering editors objections to making articles more understandable ==

I was surprised by all the pushback from expert editors against making articles easier to understand in the thread '''Yes, they are too hard to understand. No, really''' above.  Although most of this stuff is already in the article, maybe it would help to put a list of their objections, and answers, in the guidelines.  Here are some --[[User:Chetvorno|Chetvorno]]<sup><small>[[User talk:Chetvorno|<i style="color: Purple;">TALK</i>]]</small></sup> 06:50, 9 November 2023 (UTC)
*'''"Some articles are about topics too advanced to make them comprehensible to general readers; it is a waste of time to try"'''<br/>Look at the Encyclopedia Britannica entry for the topic: a good encyclopedia writer can explain any topic to general readers.  A concept can always be made ''more'' comprehensible.  And even if the concept can't be fully explained in the introduction, it should include context: What categories does this concept fit in? Does it have any analogies to simpler concepts?  What properties does it have? What are some simple examples? Who discovered it? When? What is it used for? Why is it important? This is a large part of what general readers want to know. Context is a major part of understanding. --[[User:Chetvorno|Chetvorno]]<sup><small>[[User talk:Chetvorno|<i style="color: Purple;">TALK</i>]]</small></sup> 06:50, 9 November 2023 (UTC)
*: It is simply not true that there are some topics that can be made comprehensible to general readers, especially without serious violations of our content policies and guidelines. (E.g., [[Galois cohomology]].) Articles should be written in a way that complies with our content policies and guidelines. If no source exists that explains a topic for general readers, then it is typically the case that a Wikipedia article cannot either, without at the very least engaging in original research, and at worst being completely wrong.  For articles about very abstract mathematical concepts, often the best "introductory" sources available are the AMS Notices "What is..." columns, written by subject experts for a "general mathematical" audience (i.e., graduate students already working in the area or mathematics PhDs who are not specialists.)  That's often the best we can hope for. [[User:Tito Omburo|Tito Omburo]] ([[User talk:Tito Omburo|talk]]) 12:31, 10 November 2023 (UTC)
*::A subject of interest primarily to e.g. math PhDs working on unsolved problems, lawyers working in the corners of inter-state contract law, or industrial chemists trying to eke an extra percent of yield in some obscure reaction can still usually be made accessible to advanced undergraduates or early grad students. I think we can often do better at accessibility than the "What is..." columns for mathematical topics, but those are indeed in many cases more accessible than what we currently have at Wikipedia, so are a good source to take inspiration from and cite. –[[user:jacobolus|jacobolus]] [[User_talk:jacobolus|(t)]] 15:35, 10 November 2023 (UTC)
*::: There are often no sources as good as "What is..." columns, particularly for abstract subjects that are ''only'' of interest to specialists.  Our own coverage should of course aim to be as accessible to as wide a likely audience as possible, but the expectation needs to be tempered.  Firstly, Wikipedia follows sources.  That is policy, and there is a policy against original research.  To some extent, this is relaxed for explanations aimed at making things accessible, but still it is a policy demanding some deference.  You can find examples (like [[homology theory]]) where there are loads of accessible sources out there.  I think the typical editor fails to appreciate that this tends to be the exception rather than the rule, and expectations should be set appropriately.  [[User:Tito Omburo|Tito Omburo]] ([[User talk:Tito Omburo|talk]]) 16:17, 10 November 2023 (UTC)
*::::"Follow the sources" doesn't mean you can't ever put a brief definition of a jargon term inline, can't include examples or pictures, can't describe historical/mathematical context, etc. –[[user:jacobolus|jacobolus]] [[User_talk:jacobolus|(t)]] 17:37, 10 November 2023 (UTC)
*::::: No, but not every subject has a picture that explains it (most don't).  Some jargon terms require still more jargon terms to define them.  The article [[Galois cohomology]] you recently complained about has historical context ''out the wazoo''.  An explanation of cohomology as "cocycles modulo coboundaries" is unlikely to be availing, a Galois group as "group of automorphisms of a field fixing a subfield", etc.  One has to be reasonable, and to communicate with other wikipedians that in many cases an article ''will not be understandable at all'' to someone without a good background in mathematics (and certainly not without doing OR).  I'd like you to at least acknowledge this point.  It seems like it should be pretty uncontroversial.   [[User:Tito Omburo|Tito Omburo]] ([[User talk:Tito Omburo|talk]]) 18:15, 10 November 2023 (UTC)
*: Agree with [[User:jacobolus|jacobolus]] above.  [[User:Tito Omburo|Tito Omburo]]: If you read what I wrote above carefully, you might find there is not as much difference between your position and ours as you think.  I said that a good encyclopedia writer can ''explain'' any topic to general readers; not make it ''comprehensible''. This is the key point that science writers understand but many specialist WP editors miss: there are many levels of "explanation" ([https://www.youtube.com/watch?v=Vp570S6Plt8 Mathematician explains infinity in 5 levels of difficulty, Wired mag], [https://www.youtube.com/watch?v=fkIvmfqX-t0  Harvard professor explains algorithms in 5 levels of difficulty]; I'm not saying these vids are good, just that they illustrate the idea of multiple levels of explanation) --[[User:Chetvorno|Chetvorno]]<sup><small>[[User talk:Chetvorno|<i style="color: Purple;">TALK</i>]]</small></sup> 00:29, 15 November 2023 (UTC)
*:* Sorry, I'm lost on that one.  What does it mean that the good writer can explain the topic, but not necessarily make it comprehensible?  And what good would it do? --[[User:Trovatore|Trovatore]] ([[User talk:Trovatore|talk]]) 00:38, 15 November 2023 (UTC)
::In the [[Galois cohomology]] article, [[user:jacobolus|jacobolus]] and I would like to see more effort to explain the actual concept simply; a diagram or example, say. But for nonmathematical readers an adequate "explanation" could be just its history, and why it is important.  As you said, the article has historical context out the wazoo.  Why is none in simple language in the introduction?  The history and significance of a concept can usually be summarized for general readers without an understanding of the concept; that's what White House briefing books are for.  --[[User:Chetvorno|Chetvorno]]<sup><small>[[User talk:Chetvorno|<i style="color: Purple;">TALK</i>]]</small></sup> 00:29, 15 November 2023 (UTC)           
:::What non-mathematical reader is going to look up Galois cohomology? Or [[Local Euler characteristic formula]]? Or [[Sylvester matroid]], [[Lusternik–Schnirelmann category]], or [[Symplectic spinor bundle]]? These aren't [[pi]] or [[prime number]]. Even the history and motivation of some of these topics is along the lines of, "Take a way of thinking about classical mechanics that nobody learns until at least three years into college, and generalize it to a higher level of abstraction so that even the physicists are lost". Sometimes, ''the best one can do'' is to take a topic that nobody even ''hears about'' until well into their PhD and make the opening lines approachable to a first-year grad student. [[User:XOR&#39;easter|XOR&#39;easter]] ([[User talk:XOR&#39;easter|talk]]) 03:39, 15 November 2023 (UTC)
::::People who ask college students "So, what are you studying at university right now?"
::::I think you're misunderstanding the level of detail we (or at least I) am hoping for.  Something like "'''Incomprehensible''' is a type of abstract algebra related to classical mechanics" would suit me.  I'm looking for "[[Punica granatum|''Punica granatum'']] is a fruit-bearing plant".  You seem to be "But you didn't tell them about the [[Sarcotesta|sarcotestas]] yet!  They don't know ''anything'' if they don't know about the sarcotestas!"  The sarcotestas may well be important (and delicious), but we've first got to establish the basics, like it's not a kind of [[Granite]] and it doesn't have anything to do with the [[Punic Wars]]. [[User:WhatamIdoing|WhatamIdoing]] ([[User talk:WhatamIdoing|talk]]) 03:50, 15 November 2023 (UTC)
:::::As a veteran of many such conversations over the past twenty-odd years, involving first my studies and then my research and teaching, and as a witness of many colleagues having such conversations too, this is how they go:
:::::"So, what are you studying at university right now?"
:::::"Math."
:::::Even if the answer is more specific than that, it will be something like [[topology]] or [[number theory]]. The articles I mentioned above (picked at random out of many similar possibilities) are all much more specialized. And most articles of that sort do tend to establish their context, either with the standard "In mathematics..." opening gambit or by saying what part of mathematics they belong to (combinatorics, differential geometry, etc.). So, they do the job of indicating that they're not talking about Roman coins or Cambodian verb forms. [[User:XOR&#39;easter|XOR&#39;easter]] ([[User talk:XOR&#39;easter|talk]]) 04:03, 15 November 2023 (UTC)
*'''"Explaining things in simple terms is 'dumbing down' the article"'''<br/>Adding simple explanations does not mean removing any of the advanced content. Many expert editors regard any simplified explanation as ‘[[lies to children]]’.  This is probably too extreme (and haughty) a view. Simplified explanations given in introductory-level textbooks should be acceptable, as long as the ways it is inadequate are mentioned. --[[User:Chetvorno|Chetvorno]]<sup><small>[[User talk:Chetvorno|<i style="color: Purple;">TALK</i>]]</small></sup> 06:50, 9 November 2023 (UTC)
*: Many many topics are not covered in "introductory-level textbooks" (and certainly not for textbooks you would consider "introductory": for example, the book "Modular forms and Galois cohomology" is an introductory level textbook on [[Galois cohomology]], but I doubt a non-expert would recognize it as such).  If topics are covered in (what you're thinking of as) introductory textbooks, it is certainly possible to give introductory descriptions of them.  But otherwise, probably not without violation policies at best, and being completely wrong at worst.  [[User:Tito Omburo|Tito Omburo]] ([[User talk:Tito Omburo|talk]]) 12:31, 10 November 2023 (UTC)
*::The article [[Galois cohomology]] makes very little effort to be accessible beyond a trivially tiny audience of specialists. Its accessibility could be dramatically improved without sacrificing any usefulness to a specialist audience. –[[user:jacobolus|jacobolus]] [[User_talk:jacobolus|(t)]] 15:38, 10 November 2023 (UTC)
*::: That's just not true.  The lede and most of the article is perfectly understandable to a non-specialist.  If there are reliable sources that do a better job of introduction, they can be used to improve the presentation.  [[User:Tito Omburo|Tito Omburo]] ([[User talk:Tito Omburo|talk]]) 15:44, 10 November 2023 (UTC)
*::::The lead section consists entirely of jargon. Someone who hasn't yet taken a course in homological algebra is going to be able to make no sense of it whatsoever. Edit from after the following comment: Worse, if someone clicks through to [[group cohomology]], [[homological algebra]], [[Galois module]], [[Galois group]], [[Field extension]], [[Galois representation]] (redirects to [[Galois module]]), or [[Exact functor]], they get an equally inaccessible description. This entire cluster of articles is a mess from an accessibility perspective. The article [[Homology (mathematics)]] stands out for being much better than any of those, but e.g. a curious undergrad physics student arriving at [[Galois cohomology]] is never going to manage to make it there. –[[user:jacobolus|jacobolus]] [[User_talk:jacobolus|(t)]] 15:52, 10 November 2023 (UTC)
*::::: Look, the context-setting in the article is at a more accessible level than Serre's introductory textbook on the subject, and Hida's introductory book, and even the encyclopedia entry at EoM.  In fact, arguably our article should include ''more'' technical detail to be useful to as wide an audience as possible (e.g., transcribed from [https://encyclopediaofmath.org/wiki/Galois_cohomology]).  The problem with a topic like this is that what is one to explain in a short lede section?  All of homological algebra?  All of cohomology theory?  All of Galois theory?  Actions of groups on modules?  The lede even leaves out any discussion of class field theory (which is actually quite essential), so in this way is pitched "one level down" from an intended readership.  At some level it's going to be "turtles all the way down".  Understanding the lede (or even the rest of the article) does not require a detailed understanding of homological algebra, contrary to your contention.  [[User:Tito Omburo|Tito Omburo]] ([[User talk:Tito Omburo|talk]]) 15:57, 10 November 2023 (UTC)
*::::::{{tq|i=yes| arguably our article should include moretechnical detail}} – this would also be fine. These two motivations are not in conflict here. This article has plenty of space to grow to serve all of these audiences. –[[user:jacobolus|jacobolus]] [[User_talk:jacobolus|(t)]] 16:49, 10 November 2023 (UTC)
*::::::What I'd like to see out of all of these articles listed above is for someone who just finished a typical introductory undergraduate abstract algebra course to be able to either directly understand the majority of the lead section, or else be linked within 1 hop to articles about the prerequisite jargon such that those articles' introductory sections are largely understandable.
*::::::My experience is that mathematicians in particular have this problem more than almost anyone else I have run into, that they forget what it's like to not already know the meanings of the technical terms they spent years of toil making sense of, so take it for granted that other people will be able to understand a long string of conceptually sophisticated jargon without any assistance. –[[user:jacobolus|jacobolus]] [[User_talk:jacobolus|(t)]] 17:06, 10 November 2023 (UTC)
*::::::: One hop from a specialist article is a non-specialist, not someone who just finished an undergraduate algebra course.  [[User:Tito Omburo|Tito Omburo]] ([[User talk:Tito Omburo|talk]]) 17:16, 10 November 2023 (UTC)
*::::::::When I say "trivially tiny audience of specialists" above, what I mean is "people with math PhDs", and when I say "general audience", I mean e.g. physicists, economists, computer programmers, and undergraduate math students. Wikipedia's advanced math articles, on the whole, do a very poor job at including a wide audience. They are written largely for people who already know the subjects under discussion in detail, and could in most cases be made at least somewhat legible to a much wider audience (like 100x as many people) without much compromise. –[[user:jacobolus|jacobolus]] [[User_talk:jacobolus|(t)]] 17:19, 10 November 2023 (UTC)
*:::::::::Perhaps the mathematicians, who have spent their lives explaining mathematics to others, might actually be right?  I'd like you to at least entertain this possibility rather than simply dismissing it by saying they are doing a "very poor job".
*:::::::::Regarding the example of the Galois cohomology article, what would you propose we add to the lede to make it more accessible to your hypothetical undergraduate?  Would the following be adequate? "Historically the first, and one of the most basic applications of Galois cohomology is to describe the structure of the group of elements of norm one in a [[cyclic field extension]] of degree <math>n</math>, that is, an extension field where the Galois group <math>G</math> is generated by a single element <math>\sigma</math> of order <math>n</math>.  The cohomology group <math>H^1(G,L^*)</math> with values in the group of non-zero elements of <math>L</math> can be described as the quotient of the cochains by the coboundaries of dimension one.  A cochain is a group homomorphism from <math>G</math> to <math>L^*</math>, which is completely determined by its value on <math>\sigma</math>, say <math>b=f(\sigma)\in L^*</math>, such that the product <math>b\sigma(b)\cdots\sigma^{n-1}(b)=1</math>.  This product is just the [[relative norm]] of the element <math>b</math>.  A coboundary is an element of the form <math>b/\sigma(b)</math>.  [[Hilbert's theorem 90]] states that every such cochain is a coboundary, i.e., <math>H^1(G,L^*)=1</math> is the trivial group.  Therefore, every norm one element of the field <math>L</math> can be expressed as <math>b/\sigma(b)</math>."  [[User:Tito Omburo|Tito Omburo]] ([[User talk:Tito Omburo|talk]]) 17:44, 10 November 2023 (UTC)
*::::::::::My impression is that mathematics teachers (as a broad social group under their current societal constraints; I'm not calling out any specific person here) ''don't'' generally do a good enough job of explaining mathematics: the field is notorious for chasing away promising and interested students by making them feel stupid and not giving them enough support, at every level from primary school up through grad school. It's very much a sink-or-swim go-figure-it-out-for-yourself kind of subject.
*::::::::::My impression is that the world's best mathematical expositors and popularizers are mostly not writing Wikipedia articles (because they are busy doing something else), and most of the people writing math articles on Wikipedia at every level are not in general making legibility to the broadest reasonable audience one of their top priorities. But I think it should be.
*::::::::::Galois cohomology was your example, not mine, and is probably not the best place to start since this is a topic that has a ''lot'' of prerequisite concepts, even in the best case is only going to be vaguely comprehensible to non-mathematicians, and only gets about 20 page views per day. Energy directed at making lower-level topics legible will have better payoff.
*::::::::::But if a hypothetical physics undergrad did want to figure out even roughly what [[Galois cohomology]] was talking about, and they tried clicking through any of the jargon words in the first two sections, the prerequisite articles they'd arrive at are all equally inscrutable, as are the prerequisites to those; our hypothetical student would have to go probably 5+ hops deep in any given direction to get to a page they could make any sense of at all. That's unfortunately pretty exclusionary. Most of our more basic articles like [[field extension]], [[normal subgroup]], [[exact sequence]], [[automorphism group]], etc. etc. etc. are still written in a very spare and inaccessible style.
*::::::::::If you want to figure out if a particular explanation is clear enough, the best people to try it on would be some students who are a few years away from taking the course in question. Ask them if they can figure out what all the jargon roughly means, see if they can restate the main idea in their own words, etc.
*::::::::::{{tq|i=yes|might actually be right?}} – what does this mean? I claim that our articles within 1–2 hops of your original example are almost entirely inaccessible to anyone who isn't at least a math grad student. Is your claim that any other result is impossible? You think this is the best we can do? –[[user:jacobolus|jacobolus]] [[User_talk:jacobolus|(t)]] 19:14, 10 November 2023 (UTC)
*::::::::::: Again, you're dismissing not just mathematics researchers but even mathematics pedagogy as inscrutable.  You start to sound like a classic crank.  I'm just trying to inject some realism into this discussion.  Can we do better?  Certainly.  Can we make everything accessible to everyone?  Absolutely not.  
*::::::::::: Regarding the examples of hops, the articles [[homological algebra]], [[Galois group]], [[field extension]], and even [[group cohomology]] ''do'' include an accessible description in all cases.  Definitely not enough to understand what a Galois group or field extension "really is" (because that requires knowing what a field is, what a group is, what an automorphism is).  But they set their topics in context, and include links for further browsing.  I don't claim that any of these are perfect, but blanket claims that everything is terrible strike me as very overwrought.
*::::::::::: Also, I am still curious whether you think my proposed addition to the [[Galois cohomology]] article enhances its accessibility, which you seem not to have addressed.  [[User:Tito Omburo|Tito Omburo]] ([[User talk:Tito Omburo|talk]]) 19:25, 10 November 2023 (UTC)
*:::::::::::: What you call "accessible description" I call "completely illegible to anyone who isn't already a math grad student". There's a very wide gulf between this state and making "everything accessible to everyone", a straw man which nobody is proposing. I urge you to go hand a printout of the first couple sections of any of these articles to randomly selected undergraduates in technical subjects or technical professionals from other fields (or even advanced math undergrads), and directly ask them whether they can make sense of them. I would expect almost none of them to find these articles legible. This is not just my personal opinion; people complaining about how illegible math articles are on Wikipedia is so common it has become cliché. As for your proposed addition, I'm not the person to ask about this. I don't know or care too much about algebraic number theory, and it's been 15 years since I last spent any time learning about cohomology or Galois theory. –[[user:jacobolus|jacobolus]] [[User_talk:jacobolus|(t)]] 19:55, 10 November 2023 (UTC)
*:::::::::::: I don't have much contact with undergraduates these days. But if I were to compare [[group cohomology|our article]] on group cohomology to [https://encyclopediaofmath.org/wiki/Cohomology_of_groups the entry in the eom], or Serre's book, or, pretty much any other source that discusses the topic, ours is easily more accessibl, informing the reader that it studies groups using methods of topology by regarding groups as spaces.  That's accessible!  Similarly, [[homological algebra|our article]] on homological algebra informs the reader that the subject uses techniques from topology (homology theory, an article you recently praised) to study algebraic structures. That's accessible! (The [https://encyclopediaofmath.org/wiki/Homological_algebra eom article] unhelpfully tells the reader that it is the study of derived functors.)  The article [[Galois group]] appropriately points a reader to the more elementary account in [[Galois theory]], but the first sentence eludes some technical details (without telling lies to children).  You say I am attacking a staw man, but you seem unable to assess an appropriate level of accessibility for a technical article. In my experience, most Wikipedians suffer the same deficiency.  People regularly complain that articles on technical subjects are technical.  If they want to make them less technical, and have the expertise to do so, they are welcome to.  But instead you have collectively dismissed the expertise of those that do have the expertise to do so as doing a "very bad job", or even those responsible for mathematics pedagogy (!), dismissing their expertise in such matters, even when more often than not such people are telling you they're doing the best they can. (Omg cut it out with the stupid templates, is there any evidence that a block of text at the top of a technical article improves its accessibility by obscuring the article contents?)  That attitude is very counterproductive, and often leads to misguided threads like this one. [[User:Tito Omburo|Tito Omburo]] ([[User talk:Tito Omburo|talk]]) 21:21, 10 November 2023 (UTC)
*:::::::::::::I will certainly agree with you that we're less opaque to the uninitiated than Serre's book (wide accessibility was clearly not among Serre's goals), and I will also agree with you that these ''Encyclopedia of Math'' articles by  V.E. Govorov / A.V. Mikhalev and L.V. Kuz'min also don't do a good job at this. But "less inaccessible than some completely inaccessible sources" is not really where anyone should be aiming.
*:::::::::::::Calling people who are frustrated by articles they can't read "deficient" isn't very welcoming. But note that these "deficient" people even include professional mathematicians sometimes: Math is so big that nobody understands every corner of it from top to bottom, it's of general benefit to all of us to make every article as broadly accessible as practical, even if it takes adding a couple extra paragraphs of introductory explanation that seem a bit redundant, or going out of our way to write overview articles that do more hand-holding than any advanced textbook would bother with.
*:::::::::::::I don't doubt page authors are generally "doing their best", but writing for broad legibility takes significant dedicated effort and if it isn't a priority it just won't happen. I don't mean offense, and am not trying to call out anyone specific or "dismiss" anyone's efforts. There's just a significant gap between where we currently are and an encyclopedia that strongly prioritizes helping non-experts make sense of unfamiliar topics.
*:::::::::::::I don't understand what you mean by "block of text" or what templates you are referring to. If you are talking about navigation templates, I typically find those to be space and attention wasters, and never add them to articles. Some people seem to like them though. –[[user:jacobolus|jacobolus]] [[User_talk:jacobolus|(t)]] 22:55, 10 November 2023 (UTC)
*:::::::::::::: It appears to be a widely held belief that templates such as {{tl|technical}} improve the accessibility of technical articles, but I am confused how that is supposed to work. A block of irrelevant text before the lede of an article does not seem to be an improvement for accessibility (or otherwise). [[User:Tito Omburo|Tito Omburo]] ([[User talk:Tito Omburo|talk]]) 23:41, 10 November 2023 (UTC)
*:::::::::::::::I don't think adding banners has ever helped any article. Cf. [[User:Jorge Stolfi/Templates that I sorely miss]]. –[[user:jacobolus|jacobolus]] [[User_talk:jacobolus|(t)]] 23:46, 10 November 2023 (UTC)
*::::::::::::Looking at the [[group cohomology]] article, I'd guess that a third- or fourth-year physics undergraduate would get as far as {{tq|tools used to study groups}} before giving up. There's a parenthetical before the bold text which is at least as obscure as the article name itself. The first sentence ends by mentioning [[algebraic topology]], which just looks like the combination of two math words to make an even mathier word. The second sentence brings in group representations, which are an advanced undergraduate or early graduate topic, then drops in the term [[G-module|''G''-module]]. It could be worse, but it's not easy going. {{pb}} I share the concern voiced above that focusing on articles that get infrequently read and are targeted at the highest levels of education may be misplaced effort. I'd like to see Wikipedia have really top-notch coverage of math topics taught in high school and the first couple years of college. To me, that seems the way to aim for benefiting a wide population (and the people learning things at even younger ages probably aren't looking them up in an encyclopedia). This means [[Pythagorean theorem]], [[quadratic formula]], [[sine and cosine]], [[linear equation]], ..., on up through [[calculus]], [[Matrix (mathematics)]], [[Eigenvalues and eigenvectors]], and the like. [[User:XOR&#39;easter|XOR&#39;easter]] ([[User talk:XOR&#39;easter|talk]]) 02:06, 11 November 2023 (UTC)
*::About the audience:
*::Our general rule of thumb is that we want to write one level down.  That is, a subject that is typical for a PhD in math should be written so that it is understandable to someone who is starting a master's in math; a subject typical for a master's in math should be written so that it is understandable to someone who is starting a bachelor's in math; the subjects in the math classes taken by first-year math majors should be written so that high school students can make sense of them, etc.
*::I suggest, though, that for a more or less sequential study like math, a different way to think about the audience is:  Students in class ''n'', who are looking ahead by a couple of semesters, should be able to understand the articles about classes ''n+2'', for the very simple and obvious reasons that (a) they are likely to read these articles and (b) if they can't understand what the subject is, they may not be interested in taking that class.  [[Galois cohomology]] should be understandable to someone who is currently studying [[Algebraic topology]].  [[Abstract algebra]] should be understandable to someone who has finished the section in calculus on vectors.  Don't think of it as "dumbing down", because it's not.   Think of it as telling math majors why all the cool people pick your favorite subject. [[User:WhatamIdoing|WhatamIdoing]] ([[User talk:WhatamIdoing|talk]]) 20:23, 14 November 2023 (UTC)
*:::XOR'easter makes a good point above that probably applies to me:
*:::"focusing on articles that get infrequently read and are targeted at the highest levels of education may be misplaced effort".
*:::Nevertheless, when I see an introductory section like that for [[Group cohomology]], my blood tends to boil. My view of writing one level down is to apply it, if appropriate, to the body of the article. The introduction, I insist, should be aimed at a broad public audience, without regard for education levels. [[User:DonFB|DonFB]] ([[User talk:DonFB|talk]]) 21:03, 14 November 2023 (UTC)
*::::I'd prefer that it started with something like "It's a way to compare two geometrical objects" (if you can't explain what it ''is'', then explain what it ''does''), but yes, focusing on something that gets 1,000 page views per day might have more value than something that (as this article does) gets 100 page views per day.  OTOH, there are a lot of websites that talk about basic concepts, and we might be one of the only options for really advanced subjects. [[User:WhatamIdoing|WhatamIdoing]] ([[User talk:WhatamIdoing|talk]]) 21:59, 14 November 2023 (UTC)
*:::::"It's a way to compare two geometrical objects" I don't think that's a true description at all, a group isn't a geometrical object at all ([[Group (mathematics)]] actually does imo a pretty good job of explaining what it is) but there's no nontechnical replacement for the term "group" simply because it is such an abstract concept (and the basis of abstract algebra).
*:::::I actually would agree with what you said above about writing for the person taking n-2 class. I searched and group co-homology is taught in the ''second'' grad class on abstract algebra at my undergrad institution (Berkeley) and at Stanford; the prereqs just for the first grad class is two semesters of undergrad abstract algebra. I have taken one semester of abstract algebra, and it could probably be more accessible to people like me (I don't really understand what it's about either), but I don't know why people are so pressed that articles like [[Group cohomology]] are non-understandable to people without the relevant background. There's a ''reason'' why math classes are hard and people don't skip prereqs - advanced math concepts are highly abstract and require knowing the background. Even the examples are going to be complicated math objects (even if [[Group cohomology#Basic examples]] isn't exactly comprehensible, it does look more understandable to me).
*:::::I think maybe non-math people don't appreciate how abstract and complicated certain math concepts are - sometimes a concept is only relevant to a math phd student, and that's fine. There's no way to teach a semester of abstract algebra in the just the lead of an article. [[User:Galobtter|Galobtter]] ([[User talk:Galobtter|talk]]) 00:58, 15 November 2023 (UTC)
*::::::Sure, there's no royal road to mathematics, but there are two considerations:
*::::::# That particular article really ought to be written in a way that you and your classmates can understand it, at least enough to make you think either "Now there's a class I'd really like to take some day" or "Eh, I'd rather do more with combinatorics and set theory".
*::::::# The most important thing is that people can get the information they need.  You can get decent information on some subjects from almost anywhere.  If (and I don't know whether this is true, in this particular instance, but ''if'') Wikipedia is one of the few places that provides freely accessible information on ______, then we should make that information as good as we can ''because'' it's not popular.
*::::::On that last point, the way that I think of articles on rare diseases is this:  If you get a text message from someone you care about, and it says "We're at the hospital with the baby.  The doctors say it's Scaryitis", then you should, with a quick glance at Wikipedia, be able to figure out whether your reply should sound closer to "What a relief" or "I'm so sorry".  The rarer the disease, the ''more'' important it is for us to have something.  You can get information about fevers and ear infections and flu anywhere.  Your options for learning about unusual subjects might be much more limited.  All the deep understanding can come later, but ''anyone'' should be able to get ''something'' out of the article.  The "something" for [[Group cohomology]] might have to be as small as "So, I guess you're a math major?", but we should manage something. [[User:WhatamIdoing|WhatamIdoing]] ([[User talk:WhatamIdoing|talk]]) 02:47, 15 November 2023 (UTC)
*:::::::I think standard "In mathematics" opening is enough for the "So, I guess you're a math major" message. Could the article do more for, e.g., first-year grad students? Probably. Would that benefit come from adding generalities to the opening paragraph? Maybe, but not necessarily. [[User:XOR&#39;easter|XOR&#39;easter]] ([[User talk:XOR&#39;easter|talk]]) 03:53, 15 November 2023 (UTC)
*::::::::Probably, because if the less specialized information isn't in the lead, it won't be read. [[User:WhatamIdoing|WhatamIdoing]] ([[User talk:WhatamIdoing|talk]]) 04:01, 15 November 2023 (UTC)
*:::::::::I mean, when the topic is already hyperspecialized, I'm not sure that "less specialized information" is what its readers want. People who aren't there for the substance can nope out in the opening line; those who stick around might need something other than extra words of generalities. For example, lots of our higher-level math articles are under-referenced. They typically don't need a footnote after every line, but they ought to be brought up to a standard of one per section at least. Knowing that a particular chapter in a particular monograph is a thorough survey of some aspect of a topic is going to help the actual audience more than repeating the summary of the prereq's prereq. [[User:XOR&#39;easter|XOR&#39;easter]] ([[User talk:XOR&#39;easter|talk]]) 04:27, 15 November 2023 (UTC)
*::::::::::It's a relatively common complaint by even people with math degrees (including PhDs sometimes) that a significant proportion of Wikipedia math articles are inscrutable until after the reader already knows quite a lot about the subject. For instance see the ongoing discussion (started after this one) [[Wikipedia talk:WikiProject Mathematics#Making mathematical articles more broadly accessible|WPM talk § Making mathematical articles more broadly accessible]]. –[[user:jacobolus|jacobolus]] [[User_talk:jacobolus|(t)]] 04:33, 15 November 2023 (UTC)
*:::::::::::Yes, I've experienced that myself. But the improvements that often seem necessary in that regard seem orthogonal to the kinds of changes being discussed here. [[User:XOR&#39;easter|XOR&#39;easter]] ([[User talk:XOR&#39;easter|talk]]) 04:37, 15 November 2023 (UTC)
*::::::::::::I don't think so. [[User:WhatamIdoing|WhatamIdoing]] ([[User talk:WhatamIdoing|talk]]) 04:42, 15 November 2023 (UTC)
*:::::::::::: I think they're related, but you're right there's also a lot of work to do beyond making the lead section as accessible as practical. The next step after that is to make sure that someone who has more or less satisfied the expected prerequisites (which might be quite advanced) but is new to the specific topic can make sense of most of the article including all of the most important high-level overview material. –[[user:jacobolus|jacobolus]] [[User_talk:jacobolus|(t)]] 04:45, 15 November 2023 (UTC)
*:::::::::::::My sense of the overall situation is that the top priority for some articles, like short ones on highly specialized upper-level topics, should be to expand, organize, and reference them. A lot of improvement in those corners of the encyclopedia would involve writing at a similar level to what the existing text presumes, but just being less half-ass about it. In other places, the top priority ought to be providing a solid opening. [[User:XOR&#39;easter|XOR&#39;easter]] ([[User talk:XOR&#39;easter|talk]]) 07:38, 15 November 2023 (UTC)
*:::::::::: I definitely agree though that clearly citing clearly written sources in every section of every topic would be extremely helpful. (E.g. the most influential papers, survey papers, relevant textbook chapters, student theses with nice introductory context, historical discussions, ...). For most technical Wikipedia articles I have ever looked at carefully, 20 or 30 minutes of searching turns up better sources (sometimes much, much better) than the ones previously cited. –[[user:jacobolus|jacobolus]] [[User_talk:jacobolus|(t)]] 04:45, 15 November 2023 (UTC)
*:::: DonFB, for a lot of topics, to aim the introduction at a broad public audience is essentially to waste the introduction.  You'd need to write this pro-forma pseudo-introduction for the broad public, and then write a separate one for the people who are actually going to read the article.  Because they still do need an introduction, to summarize the logical plan of the content being presented.  I don't see the point of this.{{pb}}I don't want to minimize the problem of articles being written in a way that they are harder to understand than they need to be.  That really does happen.  But a lot of the content in technical articles is just not even describable to a "broad public audience" without either making it so vague as to be useless, or repeating so much information that the audience that can actually use the article has trouble finding what they're looking for. --[[User:Trovatore|Trovatore]] ([[User talk:Trovatore|talk]]) 22:58, 14 November 2023 (UTC)
*:::::My view, which I believe is supported by policy, is that this an encyclopedia for general readership. It seems to me that students in science/math/med/tech subjects should be getting their knowledge in school/college, and that Wikipedia is not the place for them to do serious learning in those subjects. Yet, many articles in those areas seem to be written as though this is a place that offers educational material, above and beyond information for the public. [[User:DonFB|DonFB]] ([[User talk:DonFB|talk]]) 22:35, 14 November 2023 (UTC)
*::::::There are plenty of subjects where by that standard you'll just entirely eliminate the article from consideration based on too high a level of prerequisite knowledge. That doesn't seem useful to me. Better in my opinion is to do our best to make the articles as broadly accessible as possible, but also try to make them as useful as practical to a specialist audience. –[[user:jacobolus|jacobolus]] [[User_talk:jacobolus|(t)]] 22:55, 14 November 2023 (UTC)
*::::::: Exactly.  The corpus of scientific articles on extremely specialist topics is a very valuable part of Wikipedia's body of knowledge.  Why would you want to get rid of that?  It strikes me as a [[dog in the manger]] attitude.  There are tons of Wikipedia articles that are unreadable to me at my level of background in the subject; I don't assume that means they shouldn't be there. --[[User:Trovatore|Trovatore]] ([[User talk:Trovatore|talk]]) 23:06, 14 November 2023 (UTC)
*::::::::I'm not saying articles should be eliminated, only that they be made comprehensible to more than a narrowly defined segment of the population. That's the challenge in writing about the abstruse in a general readership encyclopedia. On the other hand, there are many articles on more mainstream topics in which the intros are needlessly dense and send readers chasing after numerous links instead of using everyday language, as I've previously belabored. [[User:DonFB|DonFB]] ([[User talk:DonFB|talk]]) 23:21, 14 November 2023 (UTC)
*::::::::: It's just not possible.  Some of these topics, only a narrow segment of the population has any hope of understanding, even in fairly vague terms, what they're about.  Now, we can do better than we're doing at making it a ''less'' narrow segment.  --[[User:Trovatore|Trovatore]] ([[User talk:Trovatore|talk]]) 23:31, 14 November 2023 (UTC)
*::::::::::Even if we accept that this is true ("Some of these topics, only a narrow segment of the population has any hope of understanding, even in fairly vague terms"), I'm not convinced that our articles have done what we can to make even a single sentence understandable in some of our advanced mathematics articles.  Our articles are all "Two bodies are considered equivalent if equal torques will produce equal acceleration", and we need at least a little bit of "discussion about how hard it is to push a door open when you put heavy weights on the outside, compared to when you put them near the hinge". [[User:WhatamIdoing|WhatamIdoing]] ([[User talk:WhatamIdoing|talk]]) 23:50, 14 November 2023 (UTC)
*:::::::::::Yes, and I was getting at the same general idea [https://en.wikipedia.org/w/index.php?title=Wikipedia_talk%3AMake_technical_articles_understandable&diff=1184998466&oldid=1184996583 here]. If we have (or can make) simpler material on the same topic, nothing seems to prevent us combining it with the harder-to-follow but more technical material. <span style="white-space:nowrap;font-family:'Trebuchet MS'"> — [[User:SMcCandlish|'''SMcCandlish''']] [[User talk:SMcCandlish|☏]] [[Special:Contributions/SMcCandlish|¢]] 😼 </span> 00:01, 15 November 2023 (UTC)
*:::::You said {{tq|You'd need to write this pro-forma pseudo-introduction for the broad public, and then write a separate one for the people who are actually going to read the article}}. That's actually not such a bad idea. It sort of combines the Intro To gambit into the main article. [[User:DonFB|DonFB]] ([[User talk:DonFB|talk]]) 23:32, 14 November 2023 (UTC)
*'''"Mathematical articles require equations in the introduction"''':<br/>Even if true, that doesn't mean it should not also include a simple word explanation.  One technique is after giving the equation, to rephrase it in words for nonmathematicians. --[[User:Chetvorno|Chetvorno]]<sup><small>[[User talk:Chetvorno|<i style="color: Purple;">TALK</i>]]</small></sup> 06:50, 9 November 2023 (UTC)
*: For an article about an equation, it is important to include the equation in the lede.  The lede should be a capsule version of the article, as accessible as possible, but also useful to likely readers of the article (which can include experts, graduate students and other researchers, etc, in more technical areas).  [[User:Tito Omburo|Tito Omburo]] ([[User talk:Tito Omburo|talk]]) 12:31, 10 November 2023 (UTC)
*'''"It is essential to use the correct terminology (i.e. jargon) in the introduction"'''<br/>Okay, but a brief plain-language explanation of jargon terms should also be included. --[[User:Chetvorno|Chetvorno]]<sup><small>[[User talk:Chetvorno|<i style="color: Purple;">TALK</i>]]</small></sup> 06:50, 9 November 2023 (UTC)
*: Sometimes that would take many pages of explanation and background. [[User:Tito Omburo|Tito Omburo]] ([[User talk:Tito Omburo|talk]]) 12:31, 10 November 2023 (UTC)

:Studies show that bad readability in technical articles is Wikipedia's biggest problem when compared to competitors (Britannica, etc.). Seriously, folks, is this so hard to understand that our articles should not be hard to read and understand? Writing plainly is not dumbing things down. [[Academese]] and like don't make thinks smarter, just dumber and obsfurcated. <sub style="border:1px solid #228B22;padding:1px;">[[User:Piotrus|Piotr Konieczny aka Prokonsul Piotrus]]&#124;[[User talk:Piotrus|<span style="color:#7CFC00;background:#006400;"> reply here</span>]]</sub> 03:42, 14 November 2023 (UTC)
::Which study are you thinking of? Can you be specific? –[[user:jacobolus|jacobolus]] [[User_talk:jacobolus|(t)]] 05:48, 14 November 2023 (UTC)
:::@[[User:Jacobolus|Jacobolus]] CTRL+F readability in my own article at [[:wikiversity:WikiJournal_of_Medicine/Where_experts_and_amateurs_meet:_the_ideological_hobby_of_medical_volunteering_on_Wikipedia]], where I cite some relevant works. <sub style="border:1px solid #228B22;padding:1px;">[[User:Piotrus|Piotr Konieczny aka Prokonsul Piotrus]]&#124;[[User talk:Piotrus|<span style="color:#7CFC00;background:#006400;"> reply here</span>]]</sub> 06:03, 14 November 2023 (UTC)
::::These references seem to be about some quantified "reading level" scores (based on syllables per word, proportion of uncommon words, grammatical structure, etc.), rather than subjective assessments of the effectiveness or legibility of the articles for any particular audience. Is that what you were thinking of / referring to before, when you called this Wikipedia's biggest problem compared to competitors? –[[user:jacobolus|jacobolus]] [[User_talk:jacobolus|(t)]] 09:16, 15 November 2023 (UTC)
::Much of what I have had to clean out of science articles was incomprehensible ''not'' because it was full of jargon, but because it was written by somebody who didn't have a clue. They got their "knowledge" out of a YouTube video, which got it from a website, which got it from a magazine, which got it from a coffee-table book. Jargon and equations would be a ''net advance'' over that: a presentation that requires a couple years of college to understand would still benefit a nonzero number of readers, rather than benefiting nobody at all &mdash; or worse yet, actively harming the lay audience by instilling the ''illusion'' of understanding. {{pb}} Nobody wants to write articles that are "hard to read and understand". We should of course aim to cover each topic in a way that is as widely comprehensible as feasible... but what ''is'' feasible varies widely. [[User:XOR&#39;easter|XOR&#39;easter]] ([[User talk:XOR&#39;easter|talk]]) 13:39, 14 November 2023 (UTC)
:::I agree that nobody wants to write articles that are "hard to read and understand", but sometimes humans want to show off.  I've worked hard for that jargon; I've been told that this jargon is how True™ Mathematicians talk to other professional mathematicians; I want the world to know that I'm a True™ Mathematician, too, so I've just ''got'' to use the True™ Mathematician jargon.  Using the kind of language that Prof. Matt Math actually uses in front on my own class would be mortally embarrassing, because he explains everything.
:::It reminds me of the prepubescent boys in choir.  They're desperately waiting for their voices to crack and telling the choir director, in their high little-kid voices, that they can't possibly sing notes in the vocal range they use for everyday speech.  Sometimes it's about wanting to feel important and knowledgeable and grown up, rather than anything at all about the effects on other people. [[User:WhatamIdoing|WhatamIdoing]] ([[User talk:WhatamIdoing|talk]]) 20:31, 14 November 2023 (UTC)

I think this is a good point to bring up from time to time. It's not easy to distill one's own expertise into a simple explanation for lay-people. One example in overcoming that, I think we've managed to make a small improvement to the introduction of [[Mandelbrot set]] with a couple lay-person friendly sentences, when it used to [[Special:PermanentLink/1163662666|start very technically]]. I'm a fan of taking the [[WP:IMPERFECT]] approach on such issues in general, working to improve things as we can. &mdash;[[User:Siroxo|siro]][[User talk:Siroxo|''&chi;'']][[Special:Contributions/Siroxo|o]] 08:33, 9 November 2023 (UTC)
: One sentence of context-setting is good.  But two things stand out.  First, there is a vast chasm between being able to set the context for a topic in one sentence, and making the topic accessible to a "general audience" (which is often impossible).  Secondly, the Mandelbrot set (or similar article) is a topic for which there is a superabundance of sources aimed at a general audience.  But this is not the case for most concepts in the mathematical sciences.  I agree that we need to temper our expectations about what is possible, and in particular nip the "everything can be made accessible" fiction in the bud.  [[User:Tito Omburo|Tito Omburo]] ([[User talk:Tito Omburo|talk]]) 12:41, 10 November 2023 (UTC)
::+1, some topics are popular among the general public and have and deserve a more lay person explanation, but most math topics are not like that. [[User:Galobtter|Galobtter]] ([[User talk:Galobtter|talk]]) 01:07, 15 November 2023 (UTC)

Let's look at [[Bijection]]. I assert that the third sentence of the lede, with minor modification, should be the first sentence.
As follows:

"In mathematics, a bijection is a relation between two [[Set (mathematics)|sets]], such that each element of one set is paired with exactly one element of the other set, and vice-versa."

Is that an accurate statement?

Consider the linked terms of jargon currently in the first sentence that are eliminated (they can be introduced later):

function, injective, surjective, codomain, domain of the function.

My revision would retain "set" as a linked term, but the word is recognizable to everyone as an expression for collection of things. Unless my reworking of this lede is completely wrong, I assert that ledes of all mathematical articles can be similarly simplified by removal of much opaque jargon from the first one or two sentences and the substitution of plain English, which is very often found later in the same article. [[User:DonFB|DonFB]] ([[User talk:DonFB|talk]]) 21:59, 10 November 2023 (UTC)

:Whether you call a bijection a "function" or a "relation between sets" doesn't really make much difference in how understandable the concept is, in my opinion. I'll agree that "injective (one-to-one) and surjective (onto)" can probably be deferred by a few sentences. This article would also benefit by putting a couple examples in the lead section, by explaining how a function (or pairing) can fail to be a bijection, and by giving short inline definitions of some of the other terms used. –[[user:jacobolus|jacobolus]] [[User_talk:jacobolus|(t)]] 23:03, 10 November 2023 (UTC)
::My purpose here was to show that an opening sentence with what I believe to be unnecessary jargon can be written to be instantly understandable to everyone. I'm not a mathematician (probably obvious), so I would defer to those who are in matters of accuracy, while urging and trying to demonstrate that more accessible language can be used. In this example, I used "relation between", which seems even more apparent in its meaning than "function". I looked up function and find its opening paragraph to be...difficult. The second paragraph begins with what I've understood the word to mean, although it uses "originally":
::"Functions were originally the idealization of how a varying quantity depends on another quantity."
::For my money, that's how the article should start, (with some adjustments), unless more recent standadization has made it truly obsolete. I offer this as another example of how I think it is possible to use plain English at the very start of an article and defer the techno/jargon/lingo/formula to a position later in the article, or the lede, when that's necessary. [[User:DonFB|DonFB]] ([[User talk:DonFB|talk]]) 00:00, 11 November 2023 (UTC)
:::My impression is that people most commonly think of a bijection as an invertible function. While it's true it can also be thought of as a pairing between two sets, I feel like it's a bit less obvious to put that version first.
:::I'm not really sure if "binary relation" is more likely to be understood than "function". The concept of functions is usually discussed at length in high school while the concept of a binary relation is (while not inherently any more complicated) a bit more obscure I would guess.
:::In the case of "bijection" per se, I don't think the concept of a function as one varying quantity depending on another quantity is really the right concept to think of. The concept of a function as an abstract machine that turns an input into an output is probably more useful here, but the abstract mathematical definition in terms of ordered pairs of set elements is probably also alright. –[[user:jacobolus|jacobolus]] [[User_talk:jacobolus|(t)]] 01:23, 11 November 2023 (UTC)
::::Ok, to show a little more of what I'm getting at, consider the statements:
::::"think of a bijection as an invertible function"
::::"can also be thought of as a pairing between two sets"
::::I submit that the second statement is a lot more accessible than the first. Disclosure: I never heard of bijection until today, hopping among various math articles while reading the discussion above. I'm guessing that "''mathematicians'' most commonly think of a bijection as an invertible function", but most people, like me, don't know the term at all. [[User:DonFB|DonFB]] ([[User talk:DonFB|talk]]) 02:22, 11 November 2023 (UTC)
:I took a crack at rewriting the first couple of paragraphs of [[bijection]]. Does that help? –[[user:jacobolus|jacobolus]] [[User_talk:jacobolus|(t)]] 23:45, 10 November 2023 (UTC)
::With all due respect, no. I'm sure it's accurate, but I believe my first sentence version is immediately understandable to anyone in comparison to the current version, or your offer. With the caveat, of course, that what I wrote is accurate in the broadest sense. But really, I'm not here to debate particular articles; I'm only trying to show how I think the beginning of articles on abstruse topics can be written in plain English. [[User:DonFB|DonFB]] ([[User talk:DonFB|talk]]) 00:22, 11 November 2023 (UTC)
:::This is still not really "plain English" though. The concept of a set in this context is at least a bit tricky (we're talking about potentially infinite collections, e.g. of numbers, lists of numbers, functions, geometric transformations, ...), and a [[binary relation]] is concept that is not usually encountered by students until college (and turning it into the undefined term "relation" just makes it ambiguous rather than particularly more accessible IMO). It probably would be worth trying a few versions on e.g. high school students to see which ones were easiest for them to decipher while giving a correct understanding of the concept.
:::You could well be right that first describing a bijection as a pairing between set elements would be gentler than describing it as a function. –[[user:jacobolus|jacobolus]] [[User_talk:jacobolus|(t)]] 01:38, 11 November 2023 (UTC)
:::@[[User:DonFB|DonFB]] okay, I tried again. How about this version? –[[user:jacobolus|jacobolus]] [[User_talk:jacobolus|(t)]] 02:26, 11 November 2023 (UTC)
::::That (almost) works for me. I would drop "binary pairing" from the first sentence and introduce it later. No need for a speed bump in the first sentence; it doesn't help. Also, some garble seems to exist: "element of each set is paired..." Not "the either set." [[User:DonFB|DonFB]] ([[User talk:DonFB|talk]]) 02:41, 11 November 2023 (UTC)
::::I'm also a little confused by the text example (1,2 etc); does not look consistent with the graphical example. [[User:DonFB|DonFB]] ([[User talk:DonFB|talk]]) 02:47, 11 November 2023 (UTC)
:::::If considered as a pairing per se, the graphical example could be likewise written as {(1, ''D''), (2, ''B''), (3, ''C''), (4, ''A'')}. Thinking of it as a function, you might instead write {1 ↦ ''D'', 2 ↦ ''B'', 3 ↦ ''C'', 4 ↦ ''A''} or {''f''(1) = ''D'', ''f''(2) = ''B'', ''f''(3) = ''C'', ''f''(4) = ''A''}. –[[user:jacobolus|jacobolus]] [[User_talk:jacobolus|(t)]] 03:26, 11 November 2023 (UTC)
::::: I put in a ↦ notation instead, but looking at it I'm not sure it's any better. One issue with it is that general binary relations don't necessarily have a single output for any input. That is, this notation works for bijections but not "pairings" in general. It's also not as common, which might leave some people confused. –[[user:jacobolus|jacobolus]] [[User_talk:jacobolus|(t)]] 03:50, 11 November 2023 (UTC)

=== Articles covering math topics up through early undergrad level ===

@[[User:XOR'easter|XOR'easter]] I wonder if there's a good venue for coordinating on "top-notch coverage of math topics taught in high school and the first couple years of college". I'd also like to see this happen, but it could be nice to organize some group effort rather than individual contributors trying to take each one as a one-off, perhaps something along the lines of the old "collaboration of the month" or the like. I think even aiming for green checks or gold stars shouldn't be the top priority, but just getting all of the most common pages to a consistently decent "B class" kind of standard, with special focus on the lead sections. I feel like the math Wikiproject isn't quite the venue (or rather, it plausibly could be, but I feel people might get annoyed if the traffic there increased a lot discussing a wide set of such articles).

I personally have been trying to put in the research to further improving (or write where they don't yet exist) the articles about spherical geometry and its history, spherical trigonometry, the most common map projections, and more generally some other kinds of geometry topics that could (but typically don't) appear in school. But while these topics have plenty of applications to industry (GIS, attitude control, kinematics, etc.) they're at least somewhat obscure compared to stuff right in the main line of the school curriculum. I wouldn't mind spending some time looking up sources, drawing or redrawing diagrams, etc. for high-value articles. I wonder if there's a good way to e.g. get a page view summary of all articles currently in the math wikiproject and pick out a few that are important and high traffic but currently mediocre. –[[user:jacobolus|jacobolus]] [[User_talk:jacobolus|(t)]] 05:21, 11 November 2023 (UTC)

:To get a sense of where things stand, [[User:XOR'easter/sandbox#Level-3_"Vital"_articles_in_mathematics|I grabbed the list of level-3 "Vital articles" in mathematics and looked up their 30-day page view counts]]. The winner? [[0]], with 241,262. [[User:XOR&#39;easter|XOR&#39;easter]] ([[User talk:XOR&#39;easter|talk]]) 21:01, 11 November 2023 (UTC)
::Thanks. I have a medium-term interest in cleaning up in particular [[polygon]], [[triangle]], [[line (geometry)]], [[circle]], [[angle]], [[area]], [[trigonometry]], and [[complex number]], among various other articles not on your list (most especially [[sphere]], [[spherical geometry]], etc.). If anyone wants to collaborate on any of these, I've been chipping away here and there, figuring out how to draw decent diagrams, gathering sources about several, doing my basic reading, .... –[[user:jacobolus|jacobolus]] [[User_talk:jacobolus|(t)]] 01:36, 12 November 2023 (UTC)

== Policy ==

I'm introducing a new heading just because the previous discussions are now a bit...unwieldy.
So far, I've avoided getting into the weeds of Policy/Guideline, because it's tedious to look up that stuff, and because I think we're all pretty familiar with the rules. However, I feel compelled to quote from policy now, because it directly contradicts some of what's been stated above, and what one can find in many articles. Before quoting, I'll add that I'm aware that Policy is, in theory, not top-down, but bottom up. Somewhere in the site (again, too tedious to find it, but I've seen it), one can find a statement that the reason rules are not hard and fast ("Wikipedia has no firm rules"--Five Pillars) is because they develop from common practices; that's why they can change. So maybe the practices we see in many articles on obscure subject matter (and many not so obscure) are pressuring the community to reconsider the policy text I'm about to quote. But my view is that the policy should be followed:


From: [[wp:NOT|What Wikipedia is Not]]:

Section heading:

"Wikipedia is not a manual, guidebook, textbook, or scientific journal"

"...Wikipedia articles should not read like:"

6) "'''Textbooks and annotated texts''': The purpose of Wikipedia is to summarize accepted knowledge, not to teach subject matter. Articles should not read like textbooks, with leading questions and systematic problem solutions as examples. These belong on our sister projects, such as Wikibooks, Wikisource, and Wikiversity. However, examples intended to ''inform'' rather than to ''instruct'', may be appropriate for inclusion in Wikipedia articles."

(Take special note of the following--Don):

7) "'''Scientific journals''': A Wikipedia article should not be presented on the assumption that the reader is well-versed in the topic's field...Introductory language in the lead (and sometimes the initial sections) of the article should be written in plain terms and concepts that can be understood by any literate reader of Wikipedia without any knowledge in the given field before advancing to more detailed explanations of the topic...."

(Italics in the original in #6)

[[User:DonFB|DonFB]] ([[User talk:DonFB|talk]]) 06:29, 15 November 2023 (UTC)

:The complaints above are not about encyclopedia article that seem like textbook chapters (they don't generally have "leading questions and systematic problem solutions", nor are they especially like textbooks lacking those features). They also are not about articles reading like research journal papers per se. While these are somewhat related issues, I don't think these policies are closely applicable to the concerns under discussion.–[[user:jacobolus|jacobolus]] [[User_talk:jacobolus|(t)]] 07:30, 15 November 2023 (UTC)
:The incomprehensible hyper-specialized math articles that people get so upset about are bad in part because they perfectly comply with point 6: they're not written like textbooks. Those "leading questions" we're not supposed to include can help lead a reader into a subject, providing motivation while giving a notion of the topic's contours before delving into the nitty-gritty. Those "systematic problem solutions" we're not supposed to include can make abstractions more concrete and give readers a means to double-check that they're following what's going on. Now, there are reasons why we shouldn't include those things. I tried to explain some of those reasons [[User:XOR'easter/So,_you've_decided_to_write_about_physics_and/or_mathematics_on_Wikipedia#How_do_we_organize_an_article?|here]]. But if you really don't like the state of Wikipedia's technical coverage, maybe you shouldn't like that policy! [[User:XOR&#39;easter|XOR&#39;easter]] ([[User talk:XOR&#39;easter|talk]]) 07:34, 15 November 2023 (UTC)

::What XOReaster says. [[Special:Contributions/67.198.37.16|67.198.37.16]] ([[User talk:67.198.37.16|talk]])

:I read through the argument above, about the lede to the article on bijections, and I'd like to point out that bijections are not relations, and relations are not functions. The issue here is that the word "relation" has a specific technical meaning in mathematics, and using it in the wrong context results in non-sense. This is one (of many) reasons why writing adequate accessible intros is difficult.

:There's also a converse issue: After many decades of doing physics and math, I understand certain topics well enough to write broad, accurate non-technical intros. I've done so on a number of occasions, and I'm proud of that work. I've sometimes had this work blanked, because (I kid you not) "it's not rigorous enough". From what I can tell, these were college students cramming for a mid-term exam; they'd replace the text with incorrect formulas copied from chapter one of some "intro to..." textbook. It's hard to please everybody all the time, especially when the topic is popular. [[Special:Contributions/67.198.37.16|67.198.37.16]] ([[User talk:67.198.37.16|talk]]) 07:40, 15 November 2023 (UTC)
::{{tq|i=yes| bijections are not relations, and relations are not functions}} – a function is a special case of a binary relation, as those concepts are commonly defined. You can find a wide variety of reliable sources (e.g. textbook chapters from reputable mathematicians and publishers) making this claim; I don't think it's especially controversial. –[[user:jacobolus|jacobolus]] [[User_talk:jacobolus|(t)]] 08:10, 15 November 2023 (UTC)
:::Sigh. Any and every book on model theory goes to great pains to distinguish relations from functions. Topology and set theory and order theory are conventionally defined in terms of relations, not functions. Functions really come into thier own only in analysis and calculus. But whatever, this is not the place to argue. I agree w/98% of your other discussion comments and general outlook, and I have no particular desire to litigate the concept of a [[relation (mathematics)]] vis-a-vis a [[function (mathematics)]]. I only wanted to point out that laymans terms and formal terms often clash, and that this is a problem for writing article intros and surveys. [[Special:Contributions/67.198.37.16|67.198.37.16]] ([[User talk:67.198.37.16|talk]]) 09:30, 15 November 2023 (UTC)
::::Would you mind starting a conversation at [[talk:bijection]]? I'm sure you are more of an expert about this than I am. –[[user:jacobolus|jacobolus]] [[User_talk:jacobolus|(t)]] 15:04, 15 November 2023 (UTC)
:Point 7 is vague, appealing to the subjective standard of "plain terms and concepts" and the illusory general "literate reader". Actually spelling out what vague, aspirational language in a policy means requires a guideline to supplement it, which is just what this guideline is. (If you really want to wiki-lawyer, the policy only talks about "Introductory language", so anyone could riposte that a sufficiently technical article contains ''no'' "introductory language" and thus that item is beside the point.) I would actually say that point 7 is poorly constructed. The real reason that Wikipedia doesn't function as a scientific journal is [[WP:NOR]], not any issue of writing style. Honestly, it almost seems like it was written by somebody who didn't quite know what scientific journals contain. [[User:XOR&#39;easter|XOR&#39;easter]] ([[User talk:XOR&#39;easter|talk]]) 07:53, 15 November 2023 (UTC)
::From what I've seen on the site, I think it's true that technical articles don't give "leading questions and systematic problem solutions as examples". What I've noted, however, from the discussions above is that some editors seem preoccupied with matching their content with the education level of the presumed readers. That's a direct violation of #7 in the policy text I quoted. 
::I'm surprised to hear the opinion that "Point 7 is vague". Rather, it is explicit. Nor is there any reason to describe the idea of "literate reader" as "illusory". Think of any person with more than a primary school education. Any such person can readily see the difference between "plain terms and concepts" and the scientific and technical jargon that appears in many articles. The hypothetical idea that a "sufficiently technical article contains ''no'' 'introductory language'" seems like a suggestion to simply overthrow the standard practice of introducing a subject. So far, the responses seem to wish to invalidate the policy, which perhaps is understandable since it directly contradicts some of the assertions in the discussions above. [[User:DonFB|DonFB]] ([[User talk:DonFB|talk]]) 08:42, 15 November 2023 (UTC)

:::Can you provide an explicit example of an article that you think violates either 6 or 7? (I'm finding this discussion nebulous; there is some general unease, but I've never actually seen an article that violated these. Well, I have, but they were always proded and speedy-deleted.) [[Special:Contributions/67.198.37.16|67.198.37.16]] ([[User talk:67.198.37.16|talk]]) 09:38, 15 November 2023 (UTC)

::::Thanks [[User:DonFB|DonFB]].  I don't see that Point 7 is vague at all.  The introduction should be written in "plain terms and concepts" understandable by "any literate reader of Wikipedia without any knowledge in the given field" before "advancing to more detailed explanations".  This policy removes any remaining rationalization that it's okay to write the introduction just for specialists.  The last clause allows the introduction to include technical definitions and jargon, but they must be accompanied by plain language explanations.--[[User:Chetvorno|Chetvorno]]<sup><small>[[User talk:Chetvorno|<i style="color: Purple;">TALK</i>]]</small></sup> 13:31, 15 November 2023 (UTC)

::::[[Special:Contributions/67.198.37.16|67.198.37.16]]  Although there are examples of incomprehensible WP introductions throughout technical fields, I will confine attention to mathematics.  The problem here is not finding examples of articles that violate #7, but finding articles that don't.  [[Cohomotopy set]] and [[Diffeomorphism]] have as introduction a single lead sentence of solid jargon.  And of course there is [[Galois cohomology]].  None of these have a single sentence in the introduction that attempts to explain the jargon terms in plain language. 

::::Compare these to the introduction to [[Homeomorphism]].  The first paragraph is a jargon-ridden technical introduction that will only be understandable to mathematicians.  That's okay, because the 2nd paragraph is an attempt to explain homeomorphism in plain language for general readers.  It is illustrated by a GIF that shows the famous coffee-cup-transforming-into-a-donut, as an example of homeomorphism.  Any of these introductions could be made more compliant with #7 by including general-interest information like who invented the concept, when, why it is important, any important mathematical or physics problems it is used in, and any practical uses.  Context is an important part of understanding. --[[User:Chetvorno|Chetvorno]]<sup><small>[[User talk:Chetvorno|<i style="color: Purple;">TALK</i>]]</small></sup> 13:31, 15 November 2023 (UTC)

:::::Can you explain what is wrong with any of those ledes? They certainly are not "jargon-filled". They are written in plain, simple terms, using clear and direct language. All four are eminently readable and well-structured articles. My knee-jerk reaction is they're "C-class" or "B-class". Pretty much anyone reading these will sail right on through; none of this is hard. Take [[Cohomotopy set]] for example. It's almost exemplary: the overview introduces the basic notation, chapter one type stuff that anyone/everyone would normally know. It's standard algebraic topology. What's the first concept you're tripping over? Why are we having this discussion here, instead of the article page?   [[Special:Contributions/67.198.37.16|67.198.37.16]] ([[User talk:67.198.37.16|talk]]) 17:31, 15 November 2023 (UTC)

:::::I looked more carefully at [[Cohomotopy set]]. It's a start-class article. The properties are relatively shallow factoids; there's nothing deep here. I suppose the article could be expanded; I'm not sure how. It's providing a basic background definition; that definition would be used in other articles, where assorted theorems and deep results are presented and explained. Think of it as a handy-dandy cheat-sheet one might keep at one's elbow. Whether or not this article should be gummed up with more detailed explanations is a hard call; depends on how it would be written. [[Special:Contributions/67.198.37.16|67.198.37.16]] ([[User talk:67.198.37.16|talk]]) 18:08, 15 November 2023 (UTC)

::::::Do you think "any literate reader of Wikipedia without any knowledge in mathematics" knows what a [[contravariant functor]] is?  How about a [[pointed topological space]]? --[[User:Chetvorno|Chetvorno]]<sup><small>[[User talk:Chetvorno|<i style="color: Purple;">TALK</i>]]</small></sup> 18:42, 15 November 2023 (UTC)

:::::::Do you think any literate reader of russian without any knowledge of Lithuanian can read Lithuanian Wikipedia? [[Special:Contributions/67.198.37.16|67.198.37.16]] ([[User talk:67.198.37.16|talk]]) 19:28, 15 November 2023 (UTC)
::::::::So you're acknowledging that the articles read like a foreign language to English speakers, correct? [[User:DonFB|DonFB]] ([[User talk:DonFB|talk]]) 19:50, 15 November 2023 (UTC)
::::::::Right.  And of course the policy doesn't require the English Wikipedia to be understandable in other languages. --[[User:Chetvorno|Chetvorno]]<sup><small>[[User talk:Chetvorno|<i style="color: Purple;">TALK</i>]]</small></sup> 20:21, 15 November 2023 (UTC)
:::{{tq|Nor is there any reason to describe the idea of "literate reader" as "illusory". Think of any person with more than a primary school education.}} You're replacing a vague standard with a different, much more specific one. That doesn't make the actual language of the policy any less vague. [[User:XOR&#39;easter|XOR&#39;easter]] ([[User talk:XOR&#39;easter|talk]]) 20:25, 15 November 2023 (UTC)
: If the policy keeps us from covering technical material, then it's the policy that must change.  The literal wording of NOTPAPERS has mostly been politely ignored because it's just not workable; the only way of complying with it would be to remove tons of valuable content from WP.  I hope and trust that no one here actually wants that.  --[[User:Trovatore|Trovatore]] ([[User talk:Trovatore|talk]]) 19:34, 15 November 2023 (UTC)
::As I said opening this section, "maybe the practices we see in many articles on obscure subject matter (and many not so obscure) are pressuring the community to reconsider the policy text I'm about to quote." But for any topic that can reasonably be considered non-obscure, the current policy prescription should apply. Otherwise, why bother? And If articles on difficult concepts are written only for those who already understand them, who is the encyclopedia serving? [[User:DonFB|DonFB]] ([[User talk:DonFB|talk]]) 20:07, 15 November 2023 (UTC)
:::The policy you are quoting is "Wikipedia is an encyclopedic reference, not an instruction manual, guidebook, or textbook. Wikipedia articles should not read like [...] Scientific journals"
:::That is ''not'' the question we are dealing with here, which is rather: what compromises should we make so that encyclopedia articles serve all of their plausible audiences as best as is practical. Notice that outside Wikipedia there are encyclopedia articles of a wide variety of levels from the most basic aimed at young children with lots of glossy photos, up through specialist encyclopedias written at a very advanced level. The level of difficulty involved is distinct from whether they read like research papers.
::: Unfortunately the textual elaboration of this policy bullet point is itself poorly worded and somewhat off topic, probably written by someone who wasn't thinking clearly about the fundamental differences between an encyclopedia article vs. a paper. It's confusing to editors reading it for guidance and should probably be changed. –[[user:jacobolus|jacobolus]] [[User_talk:jacobolus|(t)]] 20:24, 15 November 2023 (UTC)
::::Regarding bullet #7: I agree that the comparison to science journal is not too apt. However, the longstanding policy text which follows is explicit in prescribing plain language for ledes. [[User:DonFB|DonFB]] ([[User talk:DonFB|talk]]) 21:03, 15 November 2023 (UTC)
:::::The policy text following there is off topic for the page "what wikipedia is not", and should be clarified and moved somewhere else. –[[user:jacobolus|jacobolus]] [[User_talk:jacobolus|(t)]] 22:16, 15 November 2023 (UTC)
:::{{pb}}There are different threads here, so I'll bullet my responses just to keep them clear (not meant to be aggressive).
:::* "[F]or any topic that can reasonably be considered non-obscure" &mdash; that presumably excludes a lot of the articles we've been talking about, then.  We're no longer talking about [[cohomotopy set]] or [[Galois cohomology]], right?  But we could still be talking about [[bijection]].  In that case, fair enough &mdash; I agree that there's a considerable number of math articles that ''could'' have their intros formulated in understandable language, but don't, and that this is a problem that should be addressed.
:::* On the "written for those who already understand them" point &mdash; this is a recurring complaint, but in fact most of these articles are not written only for those who already understand them.  They're written ''also'' for those who already understand them, as makes sense for a reference work; this is where you come to look stuff up that maybe you already knew but want to make sure you get it right.  But they're also written for those who don't yet understand them but have the background necessary to understand them.  Or at least a lot of them are; this is hard to know when reading articles for which we ''don't'' have the necessary background (and that's all of us, at least sometimes). --[[User:Trovatore|Trovatore]] ([[User talk:Trovatore|talk]]) 20:26, 15 November 2023 (UTC)
:::Even a start-class article on a bizarre math topic that effectively presumes the reader already learned the subject in school can still benefit ''somebody.'' For example, they not infrequently mention where the idea was first published or point to a textbook that covers it. These kinds of details do actually benefit people who already have a grasp on the idea but need an extra datum. Should those articles benefit more people than they currently do? Sure. But the value they already provide ''is'' more than nothing. [[User:XOR&#39;easter|XOR&#39;easter]] ([[User talk:XOR&#39;easter|talk]]) 20:33, 15 November 2023 (UTC)
::::Yes, the articles have some value; I don't disagree, nor do I suggest elimination. But editors should make the effort--in accordance with policy--to introduce the bizarre in normal language, rather than simply falling back on the jargon and equations they're already intimate with, but read like a foreign language to others. [[User:DonFB|DonFB]] ([[User talk:DonFB|talk]]) 21:19, 15 November 2023 (UTC)
:::::Who decides what is "normal language"? You? Me? And what happens when there ''is'' no "normal language"? Do we violate [[WP:NOR]] to invent some? {{pb}} The snippet of policy you point to provides no useful guidance for resolving any situation that is actually difficult. It is confused about what scientific journals are and why Wikipedia can't be one. It's worse than every other item in the list at connecting the bold part to the supposed rationale. Including it in [[WP:NOT]] makes ''suboptimal'' material &mdash; like niche mathematics articles that are too densely written &mdash; sound as bad as ''fundamentally unencyclopedic'' material, like paid advertising and political soapboxing. As written, it's not fit for purpose. [[User:XOR&#39;easter|XOR&#39;easter]] ([[User talk:XOR&#39;easter|talk]]) 21:35, 15 November 2023 (UTC)
::::::Like the rest of Wikipedia, the answer would seem to be "consensus", which is what we're attempting to hash out right now. It seems pretty impossible to look to any standard other than "trying your best as a speaker of language yourself", I don't see how this is any different from any other matter of writing or style guideline onsite. [[User:Remsense|<span style="border-radius:3px 0 0 3px;padding:4px 3px;background:#1E816F;color:#fff">'''Remsense'''</span>]][[User talk:Remsense|<span lang="zh" style="border:1px solid #1E816F;border-radius:0 2px 2px 0;padding:2px;color:#000">聊</span>]] 21:41, 15 November 2023 (UTC)
:::::::It's rather worse than most things that style guides try to provide answers for: at face value, the call to do it everywhere would violate [[WP:NOR]], a bedrock principle. [[User:XOR&#39;easter|XOR&#39;easter]] ([[User talk:XOR&#39;easter|talk]]) 21:55, 15 November 2023 (UTC)
::::::::Do what everywhere? Explain unfamiliar concepts using non-specialist language? Does not strike me as an insurmountable challenge. [[User:DonFB|DonFB]] ([[User talk:DonFB|talk]]) 22:05, 15 November 2023 (UTC)
:::::::::Sometimes it isn't. Sometimes it is. [[User:XOR&#39;easter|XOR&#39;easter]] ([[User talk:XOR&#39;easter|talk]]) 22:08, 15 November 2023 (UTC)
::::::::::Well, that seems a little defeatist. Policy tells us to use non-specialist language in intros. That's what we should consistently endeavor to do. [[User:DonFB|DonFB]] ([[User talk:DonFB|talk]]) 22:15, 15 November 2023 (UTC)
::::::::::: It's not defeatist; it's just reality.  It's not about trying harder.  It's not about being better writers.  Those things can ''help'', but they can never help enough to be able to say anything worth saying about some of these things in truly non-specialist language.  ''Less'' specialist language yes; ''non''-specialist, no.
::::::::::: But there are certainly cases where we can get closer.  Someone called out [[diffeomorphism]] &mdash; that one actually ''is'' something you could say something intuitive about in the first sentence or two, that most people could get some idea about.  It wouldn't be enough to fill up the whole intro, though &mdash; you are going to have to use specialist language before the TOC. --[[User:Trovatore|Trovatore]] ([[User talk:Trovatore|talk]]) 22:21, 15 November 2023 (UTC)
::::::Consensus decides. Let's differentiate: there is a "normal" language in math; in astronomy; in biology; nuclear physics; and on. The disciplines use specialized terms normal to them, but not to everyone. The normal I refer to is the language people use every day apart from specialized or arcane fields of study. This page is filled with such normal language. Use it as a guide. [[User:DonFB|DonFB]] ([[User talk:DonFB|talk]]) 21:55, 15 November 2023 (UTC)
:::::::The difference between everyday language and specialized language is not so clear-cut as that. One spills over into the other; the same word can have connotations in one that are irrelevant to or in contradiction with its use in the other. What kind of word is ''energy,'' technical or everyday? How about ''infinity,'' ''heritability,'' ''linear,'' ''exponential,'' and ''spike protein''? [[User:XOR&#39;easter|XOR&#39;easter]] ([[User talk:XOR&#39;easter|talk]]) 22:04, 15 November 2023 (UTC)
::::::::Sure, that's not news. All the more reason for editors to carefully weigh their words, while making the effort not to default to less accessible lingo in introductions. [[User:DonFB|DonFB]] ([[User talk:DonFB|talk]]) 22:24, 15 November 2023 (UTC)
:::::::It's not possible to use ''only'' lay conversational English in a specialized math article. These are extremely abstract and esoteric objects which are many steps removed anything encountered in daily life. To fully unpack each word all the way to concepts recognized by a high school student would in some cases require dozens to hundreds of pages of elaboration, and wouldn't really be that helpful anyway.
:::::::What we can try to do is make the article as accessible as practical by e.g. providing examples, pictures, historical context, and analogies, and by trying to expand obscure jargon words in terms of more commonly known jargon words which are couple levels below the level of the subject. –[[user:jacobolus|jacobolus]] [[User_talk:jacobolus|(t)]] 22:29, 15 November 2023 (UTC)
:<small>Thanks to XOReaster for cleaning up my mess &mdash; I should work through and understand that merge-conflict tool sometime.  When it pops up I don't know exactly what to do. --[[User:Trovatore|Trovatore]] ([[User talk:Trovatore|talk]]) 20:32, 15 November 2023 (UTC) </small>
:Can I say that having a conversation on this point is always going to be incomplete without concrete examples of what we're talking about? As with the rest of wiki norms, these things are implemented on a per-article basis, and if we're going to craft a better, more helpful policy, we should be doing so based on specific examples so that we don't just argue over the connotations of various adjectives. Are there any articles people would cite as an example either for or against their particular view of what the policy should reflect? [[User:Remsense|<span style="border-radius:3px 0 0 3px;padding:4px 3px;background:#1E816F;color:#fff">'''Remsense'''</span>]][[User talk:Remsense|<span lang="zh" style="border:1px solid #1E816F;border-radius:0 2px 2px 0;padding:2px;color:#000">聊</span>]] 21:57, 15 November 2023 (UTC)

{{od}}
It appears my analogy was mis-understood. All I'm saying is that perhaps the ledes of the articles in Lithuanian Wikipedia should be re-written in russian. This would allow ordinary people, without specialist training in Lithuanian, to at least be able to understand what the article is about. This is a win-win situation. Pretty much everyone in the world can read russian; these articles would become accessible to a broad, generalist audience. Wikipedia would be vastly improved by this one simple step. [[Special:Contributions/67.198.37.16|67.198.37.16]] ([[User talk:67.198.37.16|talk]]) 20:48, 15 November 2023 (UTC)
:Let's try to leave out the sarcasm.  I think we have similar goals.  We all want articles to be as understandable as possible, and I ''hope'' no one wants to remove technical content. --[[User:Trovatore|Trovatore]] ([[User talk:Trovatore|talk]]) 20:51, 15 November 2023 (UTC)

::This is not sarcasm. The problem with the russian proposal is that it is chauvinistic: russians believe that the world should adapt to them, instead of russia adapting to the world. This is the chauvinism I see above. Instead of learning enough math to understand some article, the proposal is that the lede should be re-written so that non-mathematicians can understand it. The chauvinistic attitude that "literate readers" should understand them. The reality is, of course, that the readers are illiterate; they have not taken the effort to understand the language of mathematics. And yes, mathematics is a foreign language. There's no way to make it not-foreign. [[Special:Contributions/67.198.37.16|67.198.37.16]] ([[User talk:67.198.37.16|talk]]) 21:20, 15 November 2023 (UTC)
:::The argument you're making is simply not an argument at all. Instead, it is a rhetorical sleight of hand that breaks down when you try to apply rigor to it. Granted—in a sense, mathematics is its own language. It has its own writing system of vocabulary and syntax. Certain mathematical papers may even manage to be written entirely in it. However, you are plainly making a false equivalence: it is asinine to deliberately overlook that Wikipedia is still being written in a human language, in the context of an existing body of literature in said human language, in this case English.
:::Please stick to making a case instead that it is simply too difficult to make certain technical concepts readable enough for a given standard, because this is an infinitely more compelling argument to make. [[User:Remsense|<span style="border-radius:3px 0 0 3px;padding:4px 3px;background:#1E816F;color:#fff">'''Remsense'''</span>]][[User talk:Remsense|<span lang="zh" style="border:1px solid #1E816F;border-radius:0 2px 2px 0;padding:2px;color:#000">聊</span>]] 21:31, 15 November 2023 (UTC)
::::The above conversation already singled out [[cohomotopy set]] and [[Galois cohomology]]. I believe that they are reasonably well-written and clear, and quite understandable to anyone who has gone through a college course on [[algebraic topology]] and [[Galois theory]]. I don't see any particular way of making them comprehensible to anyone with only high-school math, and yet, it seems like that is the standard being asked for. [[Special:Contributions/67.198.37.16|67.198.37.16]] ([[User talk:67.198.37.16|talk]]) 22:33, 15 November 2023 (UTC)
:::It is not "chauvinist" (aggressively nationalistic) to wish that articles about math topics which are relevant to e.g. computer science or physics or economics should be at least basically accessible to professional computer scientists or physicists or economists, or that articles about math topics encountered in grad school should have at least their first few sentences comprehensible to people with undergraduate math degrees, or that articles about basic topics used throughout science and engineering should if possible have a few sentences accessible to laypeople or first year college students. Examples about algebraic topology etc. are pretty esoteric, so as a concrete lower level example, it would be great if [[Eigenvalues and eigenvectors]] did not require readers to have already gone through two semesters of undergraduate linear algebra coursework to make sense of the first few sections. –[[user:jacobolus|jacobolus]] [[User_talk:jacobolus|(t)]] 22:43, 15 November 2023 (UTC)

::::Algebraic topology is not a course that you will magically evade on your way to an undergrad math degree, so its hardly "esoteric". As we are all in general agreement that articles should be understandable, then what are we arguing about? [[Special:Contributions/67.198.37.16|67.198.37.16]] ([[User talk:67.198.37.16|talk]]) 23:14, 15 November 2023 (UTC)
:::::What I mean is, a bunch of the people discussing here are 3+ years of full-time pure math study away from making sense of [[Galois cohomology]], which makes it hard to use as an example that we can try to get on the same page about. –[[user:jacobolus|jacobolus]] [[User_talk:jacobolus|(t)]] 23:20, 15 November 2023 (UTC)
:::::: I think it would be great to discuss concretely what we might do with the eigenvector article, in the context of this discussion.  Maybe start a new section for that?  The topic is accessible enough that non-mathematicians can potentially contribute, but technical enough to come up against some of the issues we're dealing with.  --[[User:Trovatore|Trovatore]] ([[User talk:Trovatore|talk]]) 23:27, 15 November 2023 (UTC)
:::::::I'm game. [[User:DonFB|DonFB]] ([[User talk:DonFB|talk]]) 23:51, 15 November 2023 (UTC)
:::::::Great idea!  I'll look at it.  Should we start a new thread? --[[User:Chetvorno|Chetvorno]]<sup><small>[[User talk:Chetvorno|<i style="color: Purple;">TALK</i>]]</small></sup> 23:55, 15 November 2023 (UTC)

== Concrete example: Eigenvectors and eigenvalues ==

Our article about [[Eigenvectors and eigenvalues]] (henceforth E&E) has some great material included, and does some things well, but I think its structure and language for the first few sections still make it less accessible than it could be for an audience of laypeople or early students who might plausibly want to know what the word nominally means if they encounter it somewhere, which many people are likely to do as this is a very common tool used throughout science and engineering, one of the most important ideas in linear algebra.

There's been some significant effort put into making accessible material in [[Eigenvalues and eigenvectors#Overview|E&E § Overview]] with some pictures and relatively informal text. However, the lead section and the first following section, [[Eigenvalues and eigenvectors#Definition|E&E § Definition]] are full of jargon, and even the overview section doesn't in my opinion sufficiently prioritize accessibility.

I think this could be yet better if we made the lead section itself less technical, moved material from the overview section into the lead / first section, deferred a formal definition, and tried to unpack any jargon showing up near the top. In my opinion, this article should try to provide an introductory explanation in the first 2–3 sections accessible to someone who does not know the meanings of the jargon words [[field]], [[vector]], [[linear transformation]], [[matrix]], [[scalar multiple]], [[principal axis (mechanics)|principal axis]], [[rigid body]], [[shear mapping]], [[differential operator]], [[matrix decomposition]], [[diagonalizable matrix|diagonalize]], [[coordinate vector]], [[differential operator]], [[quadratic form]], etc.

I think we could fit a short inline explanation of linear transformations, vectors, matrices, lead with some pictures/examples, and then give some clear idea near the top of why this subject is important. We of course also want undergraduate linear algebra students (and more advanced math/technical students, math historians, etc.) to get the full story they are looking for. But this doesn't have to come at the expense of a very quick and basic accessible explanation. –[[user:jacobolus|jacobolus]] [[User_talk:jacobolus|(t)]] 23:52, 15 November 2023 (UTC)

:Mona Lisa illustration and caption are superb; highly informative and helpful. How about putting that in the intro section. It seems like it would be universally understandable. [[User:DonFB|DonFB]] ([[User talk:DonFB|talk]]) 00:07, 16 November 2023 (UTC)
::Agree. I'd like to mention up front that the intro needs context: history of the idea, etymology, importance, mathematicians who developed it, physical problems it applies to, modern uses.  For the many readers who won't be able to comprehend even a simplified explanation, this is what "understanding" the concept consists of. --[[User:Chetvorno|Chetvorno]]<sup><small>[[User talk:Chetvorno|<i style="color: Purple;">TALK</i>]]</small></sup> 00:19, 16 November 2023 (UTC)
::I like the concept of the Mona Lisa picture, but I think it works better with a less busy picture, on which the arrows would show up more clearly. –[[user:jacobolus|jacobolus]] [[User_talk:jacobolus|(t)]] 00:54, 16 November 2023 (UTC)
:::While we're talking about pictures and 2d transformations, the article has a section near the bottom about [[Eigenvalues and eigenvectors#Eigenvalues of geometric transformations|E&E § Eigenvalues of geometric transformations]]; I think it would probably be helpful to move this to the first third of the article instead of relegating it to "applications" near the bottom, and maybe use paragraphs rather than a table, ideally also showing a picture of what each transformation does to the same base image. This material is more accessible than parts about characteristic polynomials and so on. –[[user:jacobolus|jacobolus]] [[User_talk:jacobolus|(t)]] 01:12, 16 November 2023 (UTC)

:Here is a kind of schematic that simplifies the syntax, though does not immediately simplify the terminology:

:"In linear algebra, an eigenvector (/ˈaɪɡənˌvɛktər/) is a nonzero vector that changes at most by a constant factor when a linear transformation is applied to it."

:In short, is it necessary to repeat "linear transformation" twice? Paraphrasing, here's what it seems to say now: "in a transformation this is what happens when you do the transformation". Cutting redundancy can also cut instances of jargon. [[User:DonFB|DonFB]] ([[User talk:DonFB|talk]]) 01:07, 16 November 2023 (UTC)
::I think it is necessary to repeat "linear transformation". An eigenvector is an eigenvector ''of a transformation,'' not by itself. [[User:XOR&#39;easter|XOR&#39;easter]] ([[User talk:XOR&#39;easter|talk]]) 03:46, 16 November 2023 (UTC)
:::Ok, not being a wise-guy here, just want to nail this down. In the Mona Lisa (eg), before it is transformed, are any of the vectors (if they exist) eigenvectors? The article says an eigenvector is a "characteristic vector" of a transformation. That seems to say it is not an eigenvector until the transformation happens, and then the eigenvector becomes "characteristic" of what a transformed vector looks like. Or, to put it another way, the sentence appears to say that a vector (generic) is not an eigenvector until the space is transformed. Is that correct? Stripping away much of the surrounding text, the sentence literally says, "an eigenvector is a vector that changes when that transformation is applied to it." Reduced further, we see "a vector that changes". [[User:DonFB|DonFB]] ([[User talk:DonFB|talk]]) 04:23, 16 November 2023 (UTC)
::::Once you have a mathematical description of the transformation, you can find what its eigenvectors are. Asking whether a vector is an eigenvector before the transformation is applied is kind of a meaningless question. {{pb}} In trying to strip away the surrounding text, you're actually changing the meaning. An eigenvector of a transformation is a vector that changes ''in at most in a specific, very limited way'' when that transformation is applied to it. The italicized part is an essential part of the concept, not an optional one. [[User:XOR&#39;easter|XOR&#39;easter]] ([[User talk:XOR&#39;easter|talk]]) 04:34, 16 November 2023 (UTC)
:::::Yes, I acknowledge that stripping away text can change meaning. So instead of asking if a vector is an eigenvector before transformation, is it correct to say: If there is no transformation, then an eigenvector cannot exist in the specified space (or object, or whatever is the correct term). Is it therefore correct to say an eigenvector can only appear after a transformation.? And going out further on a limb, can we say, in a generalized way, "A vector can become an eigenvector when a linear transformation is applied to it"? I do not mean to imply that ''all'' vectors in a space will become eigen, as Mona Lisa shows. [[User:DonFB|DonFB]] ([[User talk:DonFB|talk]]) 04:50, 16 November 2023 (UTC)
::::::The concept of "eigenvector" is only meaningful with respect to a linear transformation (specifically, a linear transformation of some vector space to itself), for example the vector space of displacements in the 2-dimensional Euclidean plane can be transformed by e.g. stretching every displacement two times taller vertically and then skewing them upward proportionally to the horizontal displacement.
::::::It seems weird to me to say that a vector "becomes" an eigenvector. Like, if I give you the nickname "D" I wouldn't be likely to say "DonFB became a nicknameholder"; it't not wrong exactly, but seems strange.
::::::I would instead say that if you start with a linear transformation, you can find out which vectors didn't change direction under that transformation, but were only scaled. –[[user:jacobolus|jacobolus]] [[User_talk:jacobolus|(t)]] 05:07, 16 November 2023 (UTC)
:::::::I was modifying my text, but got a conflict. My change says, "A vector can be recognized as an eigenvector when (or after?) a linear transformation is applied to it. It is a vector which did not change direction, <s>but only changed its size (magnitude?)</s>" [seems incorrect] Also incorporates Jacobolus comment. As may be seen, I'm attempting to distill the concept into unadorned terms, for use at the very beginning of the article. I recognize that "linear transformation" should have some explanation very close by. [[User:DonFB|DonFB]] ([[User talk:DonFB|talk]]) 05:19, 16 November 2023 (UTC)
::::::::I find the current first sentence's "changes at most by a constant factor" to be confusing and a bit misleading.
::::::::It's probably clearer to say that an eigenvector is a vector to which applying the transformation is equivalent to scaling by a constant factor. I think it's likely clearer in this case to first start with a (moderately) technical definition, and then add 1–2 paragraphs afterward explicitly defining the terms involved such as linear transformation, vector, and scaling. –[[user:jacobolus|jacobolus]] [[User_talk:jacobolus|(t)]] 06:18, 16 November 2023 (UTC)
:::::::::Not to put too fine a point on it, but that whole first sentence is a train wreck. 
:::::::::Try this: 
:::::::::"An eigenvector is a vector that doesn't change direction when a linear transformation is applied."
:::::::::Is it wrong, or is it simply bare bones, with more details to be added in the ensuing sentences, using equally plain language?
:::::::::[[User:DonFB|DonFB]] ([[User talk:DonFB|talk]]) 07:34, 16 November 2023 (UTC)
:::::::::Keep in mind, in this part of the article (the beginning), we are only introducing the concept to a broad public audience, not emulating the type of textbook language a mathematics student would expect to see. [[User:DonFB|DonFB]] ([[User talk:DonFB|talk]]) 13:02, 16 November 2023 (UTC)
::{{dedent|7}} It's not wrong (and you can find sources saying more or less this precise sentence), and this would be a better "short description" than the current "Vectors that map to their scalar multiples", but (a) it still presumes someone knows what "vector" and "linear transformation" mean, (b) it presumes someone can guess that changing magnitude or flipping backwards is allowed and knows knows what it means for a vector to change directions, and (c) I think some people may find "direction" to be insufficient as a description in some more abstract vector spaces (I think that's fine).
::You might want to start be looking at some non-Wikipedia sources. For example, [https://www.youtube.com/watch?v=PFDu9oVAE-g&list=PLZHQObOWTQDPD3MizzM2xVFitgF8hE_ab&index=14 Grant Sanderson's video] about the subject. There's some good meta-discussion in {{citation| author1=Wawro |author2=Watson |author3=Zandieh |year=2019 |title=Student understanding of linear combinations of eigenvectors |journal=ZDM |volume=51 | pages=1111–1123 |url=https://par.nsf.gov/servlets/purl/10385426}}, which e.g. notes that "Hillel (2000) found that instructors often move between geometric, algebraic, and abstract modes of description without explicitly alerting students; although the various ways to think about and symbolize linear algebra ideas are second nature to experts, they often are not within the cognitive reach of students." –[[user:jacobolus|jacobolus]] [[User_talk:jacobolus|(t)]] 14:15, 16 November 2023 (UTC)
:::It does presume foreknowledge of vector and linear transformation. I don't think, however, that articles of this type begin with sub-definitions. So, for the ensuing couple of sentences, try this: 
:::"A vector is a way of representing quantities that have both magnitude and direction. A linear transformation is a way of changing or stretching space, possibly rotating or even flipping it, while maintaining continuous structure that does not have holes or gaps."
:::I would also offer the following as a modification of the first sentence I proposed above:
:::"An eigenvector is a vector that does not change direction when a linear transformation is applied, but its scale may change, either lengthening or shortening." [[User:DonFB|DonFB]] ([[User talk:DonFB|talk]]) 20:08, 16 November 2023 (UTC)
::::This still has the problem that an eigenvector is an eigenvector of a specific linear transformation, not a vector that is somehow immune to change in general. [[User:XOR&#39;easter|XOR&#39;easter]] ([[User talk:XOR&#39;easter|talk]]) 20:39, 16 November 2023 (UTC)
:::::I wonder if putting it in the past tense would address the issue:
:::::"An eigenvector is a vector that did not change direction when a linear transformation was applied, but its scale may have changed, either lengthening or shortening." [[User:DonFB|DonFB]] ([[User talk:DonFB|talk]]) 20:54, 16 November 2023 (UTC)
::::::That's needlessly complicated, introducing unexplained tense shifts back and forth during the opening sentences. And, if anything, it gets in the way of understanding that the eigenvectors and eigenvalues are determined once the transformation is written down. Really, whatever problems the intro has, I don't think repeating "linear transformation" is among them. [[User:XOR&#39;easter|XOR&#39;easter]] ([[User talk:XOR&#39;easter|talk]]) 21:02, 16 November 2023 (UTC)
::::::I think it should say something along the lines of "An eigenvector is a vector whose direction is fixed by a linear transformation" or "The eigenvectors of a linear transformation are those vectors on which the transformation acts by scaling". Then in a following paragraph, the terms vector, linear transformation, scaling, etc. can be (perhaps informally) defined. –[[user:jacobolus|jacobolus]] [[User_talk:jacobolus|(t)]] 21:15, 16 November 2023 (UTC)
:::::::I rather like the second option. [[User:XOR&#39;easter|XOR&#39;easter]] ([[User talk:XOR&#39;easter|talk]]) 21:19, 16 November 2023 (UTC)
:::::::"the transformation acts by scaling" is not clear. It seems appropriate to explicity say length (magnitude?) can change to be greater or lesser/longer or shorter [[User:DonFB|DonFB]] ([[User talk:DonFB|talk]]) 21:27, 16 November 2023 (UTC)
::{{dedent|5}}This would be wikilinked to [[Scaling (geometry)]] or [[Scalar multiplication]], and unpacked at greater length in the following paragraph. It could be extended by a few words inline, for instance:
:::{{tq|The '''eigenvectors''' of a [[linear transformation]] are those [[Euclidean vector|vector]]s on which the transformation acts by [[Scaling (geometry)|scaling]], without change of [[Orientation (geometry)|orientation]]; the '''eigenvalues''' are the corresponding scaling factors. {{pb}} A vector is a multi-[[dimension]]al quantity with an orientation and a magnitude, often pictured as an arrow. [[Vector addition|Adding two vectors]] can be understood geometrically by the parallelogram rule: when two oriented sides of a parallelogram are added together, the result is the parallelogram's diagonal. [[Scalar multiplication|Multiplying a vector by a scalar]] represents the geometric transformation of [[uniform scaling]], which stetches, squishes, or possibly reverses a vector along its line through the origin but does not rotate it away from that line. A linear transformation is a [[function (mathematics)|function]] between [[vector space]]s which preserves the operations of vector addition and scalar multiplication; geometrically, this means that a linear transformation maps any [[Regular grid|regular grid]] of parallelograms in one vector space to a regular grid of parallelograms in the other. {{pb}} For a linear transformation from a vector space to itself, applying the transformation to one of its eigenvectors scales that vector by the corresponding eigenvalue. Whenever an arbitrary vector can be rewritten as a sum of eigenvectors, the operation of the linear transformation can be likewise written as a [[weighted sum]] of the same eigenvectors, using with the eigenvalues as weights. Because scalar multiplication is a simpler operation than general linear transformations, ...}}
::–[[user:jacobolus|jacobolus]] [[User_talk:jacobolus|(t)]] 22:31, 16 November 2023 (UTC)
:::I am certain it will be approved by math specialists, but I think it is much too complicated as an introduction to a lay audience. <s>As I've discussed before, and as multiple rules in Policy and Guideline say, links should not be used in the introduction as a crutch to substitute for an explanation that laypeople can understand. Links in the intro are fine for readily understandable terms where the linked article offers supplementary information, but not because the term itself is obscure or has a highly specialized meaning that is not obvious.</s>
:::May I be so bold to ask you for this: a list, in plainest English you can manage, of the four or five most important things to understand about eigenvectors. 
:::In the meantime, I offer a new revision of my proposed first sentence:
:::"In linear algebra, an eigenvector for a linear transformation is a vector that does not change direction when the transformation is applied, but its scale may change, either lengthening or shortening." [[User:DonFB|DonFB]] ([[User talk:DonFB|talk]]) 23:09, 16 November 2023 (UTC)
:::Striking my comment above; terms you linked look reasonable; but the overall complexity of the suggested intro remains too great. [[User:DonFB|DonFB]] ([[User talk:DonFB|talk]]) 23:16, 16 November 2023 (UTC)
::::The only fundamental thing to understand about eigenvectors and eigenvalues is that they satisfy the equation <math> Av = \lambda v,</math> where <math>A</math> is a linear transformation, <math>v</math> is a vector, and <math>\lambda</math> is a scalar. To make sense of that requires explaining what vectors, scalars, and linear transformations are and how they are related to each-other. –[[user:jacobolus|jacobolus]] [[User_talk:jacobolus|(t)]] 23:55, 16 November 2023 (UTC)
::::{{tq|i=yes|much too complicated as an introduction to a lay audience}} – quite the opposite, I would expect a very technical audience to be annoyed for wasting too much space defining jargon and unpacking the prerequisite ideas. –[[user:jacobolus|jacobolus]] [[User_talk:jacobolus|(t)]] 23:13, 16 November 2023 (UTC)
:::::I agree it's quite possible a very technical audience will be annoyed for wasting space. I submit that's not a consideration for writing introductions. The experts can jump to the main body in an instant. The laypeople are the ones who will be annoyed by the unnecessary complexity of the intro, as drafted. [[User:DonFB|DonFB]] ([[User talk:DonFB|talk]]) 23:20, 16 November 2023 (UTC)
::::::I actually like to read leads of technical topics I'm competent at, to see if they properly summarize the material for a lay audience. It's not an annoyance, especially when the material is done well. If I'm in a hurry for some particular factoid and not interested in the lead, I know how to use the ToC or in-page search to get directly to what I'm looking for. <span style="white-space:nowrap;font-family:'Trebuchet MS'"> — [[User:SMcCandlish|'''SMcCandlish''']] [[User talk:SMcCandlish|☏]] [[Special:Contributions/SMcCandlish|¢]] 😼 </span> 23:32, 16 November 2023 (UTC)
:::::::Sure, if you're knowledgeable in the topic, it can be fun to see if the intro is done well. If you're not well-versed in it, getting through and understanding an unnecessarily techy intro it can be a pain, as innumerable comments over the years have attested. [[User:DonFB|DonFB]] ([[User talk:DonFB|talk]]) 23:49, 16 November 2023 (UTC)
::::::::To clarify, I'm suggesting that a lead that isn't unnecessarily techy is still not an annoyance for readers who could understand a techy version. Some, hunting for something specific, are apt to skip it, but I don't think they'd be {{em|annoyed}} that an accessible intro has been provided, and will understand that it was written by experts not for them. <span style="white-space:nowrap;font-family:'Trebuchet MS'"> — [[User:SMcCandlish|'''SMcCandlish''']] [[User talk:SMcCandlish|☏]] [[Special:Contributions/SMcCandlish|¢]] 😼 </span> 23:54, 16 November 2023 (UTC) 
:::::::::Agreed. [[User:DonFB|DonFB]] ([[User talk:DonFB|talk]]) 00:08, 17 November 2023 (UTC)
:::::::::If the simplification is done well, it's fine. If it isn't, say if it propagates a hoary old confusion by being careless and lazy, it becomes what in technical terms is designated ''annoying as fuck.'' [[User:XOR&#39;easter|XOR&#39;easter]] ([[User talk:XOR&#39;easter|talk]]) 02:31, 17 November 2023 (UTC)
::::::What I mean is, my proposal is ''significantly less technical than anything previously proposed here'', and about as non-technical as reasonably possible (to take it further means further unpacking another couple levels of concepts to the length of a book chapter, which obviously doesn't fit in a lead section anywhere). –[[user:jacobolus|jacobolus]] [[User_talk:jacobolus|(t)]] 23:50, 16 November 2023 (UTC)
::: Here is text from your draft, slightly edited and with a sentence I added, that I think is helpful and readily grasped by the lay readership:
::: "A vector is a multi-dimensional quantity with an orientation and a magnitude, often pictured as an arrow. A linear transformation stretches, squishes, or possibly reverses a vector, but does not rotate it. The amount it gets changed is called the eigenvalue." [[User:DonFB|DonFB]] ([[User talk:DonFB|talk]]) 00:02, 17 November 2023 (UTC)
:::: No, this version is outright incorrect. Linear transformations, as I wrote, are transformations which  preserve scalar multiplication and vector addition (or geometrically, fix the origin and transform regular grids of parallelograms into regular grids of parallelograms). It's only the eigenvectors of a linear transformation which are scaled without a change of direction. –[[user:jacobolus|jacobolus]] [[User_talk:jacobolus|(t)]] 01:09, 17 November 2023 (UTC)
:::::Does this mean a linear transformation is <u>not</u> what "stretches, squishes, or possibly reverses a vector"? [[User:DonFB|DonFB]] ([[User talk:DonFB|talk]]) 01:28, 17 November 2023 (UTC)
:::::I'm sorry to say this, but your current draft is much less accessible than what exists now in the second paragraph of the intro section. From my perspective, the main problem with the section is the first paragraph, for which I've been attempting to create an improved first sentence.[[User:DonFB|DonFB]] ([[User talk:DonFB|talk]])
:::::: No, a linear transformation only (just) scales the eigenvectors. The only restriction on the transformation of arbitrary other vectors is that the linear transformation preserves scalar multiplication and vector addition. In other words, the transform applied to a scalar multiple of one vector is equal to the scalar multiple of the transformed vector – symbolically <math>A(ku) = k\,Au</math> – and the transform applied to the sum of two vectors is equal to the sum of each separately transformed vector – symbolically <math>A(u + v) = Au + Av.</math>
:::::: The part we have so far is clearly insufficient for you as an audience: you don't yet understand the idea. (This is entirely to be expected, and not a personal failing; students usually don't encounter this topic until near the end of a semester-long introductory linear algebra course where they have spent dozens of hours doing practice exercises, and here we have only a few sentences.) This is the problem with taking "accessibility" to just mean "what seems at a glance to make sense"... it's easy to superficially feel like you know what is being said without really following it if you don't have any experience with the prerequisite concepts involved. If we use a word such as "linear transformation" and the audience (in this case you, as a representative uninitiated reader) does not know what that word means, it's not really possible to explain what a linear transformation's eigenvectors are. –[[user:jacobolus|jacobolus]] [[User_talk:jacobolus|(t)]] 02:21, 17 November 2023 (UTC)
::::::To further your point a little: one can't really get far editing mathematical prose just by pushing the words around. One has to understand the mathematics to make sure that nothing breaks. In this case, we're dealing with a concept that a student might meet in their second year of college or thereabouts. (For example, at MIT they teach this stuff in [https://ocw.mit.edu/courses/18-03-differential-equations-spring-2010/ 18.03], which comes after the two semesters of calculus, 18.01 and 18.02. Caltech does it [https://catalog.caltech.edu/current/2023-24/department/Ma/#calculus-of-one-and-several-variables-and-linear-algebra about the same way].) This means that if we manage to say something meaningful for students in their ''first'' year of college math, we're making progress. [[User:XOR&#39;easter|XOR&#39;easter]] ([[User talk:XOR&#39;easter|talk]]) 02:53, 17 November 2023 (UTC)
:::::::I agree with the following; it's a fair comment:
:::::::{{tq|one can't really get far editing mathematical prose just by pushing the words around. One has to understand the mathematics to make sure that nothing breaks}}
:::::::Having said that, I offer:
:::::::Edited Jacobolus draft:
:::::::"The eigenvectors of a linear transformation are those vectors on which the transformation acts by scaling, or sizing, without a change in vector direction. Eigenvalues are the corresponding scaling factors. A vector is a quantity with an orientation and a magnitude, often pictured as an arrow. A vector space is a [[set]] whose elements are vectors. A linear transformation maps any regular grid of parallelograms in one vector space to a regular grid of parallelograms in another. 
:::::::Vectors can be added and multiplied in ways that meet certain requirements. Multiplying a vector represents a geometric transformation which stretches, squishes, or possibly reverses a vector, but does not rotate it. For a linear transformation from a vector space to itself, applying the transformation to one of its eigenvectors scales that vector by the corresponding eigenvalue. 
:::::::The eigenvectors and eigenvalues of a transformation serve to characterize it, and so they play important roles in all the areas where linear algebra is applied, including geology, navigation, electricity, magnetism, physics, and quantum mechanics." [[User:DonFB|DonFB]] ([[User talk:DonFB|talk]]) 05:32, 17 November 2023 (UTC)
::: This proposal suffers a big problem that with three paragraphs it completely fails to summarize the article.  (This is a deficiency of the current lede as well, although less so.)  Your proposal might be more appropriate for a separate introductory ''section'' in the article (e.g., the first few paragraphs of the ''Overview'' section). I think this illustrates a big problem with the current guideline: it's not really possible to give a completely non-technical description of everything ''in the lede'', without breaking it.  The lede is for summarizing the article that exists, with due weight, not the article we wished existed.  [[User:Tito Omburo|Tito Omburo]] ([[User talk:Tito Omburo|talk]]) 10:39, 17 November 2023 (UTC)
::::I like your changes, good work! (I'm not a big fan of the phrasing "changes at most by a constant factor" though, which seems confusing.) I agree that we can probably delay further unpacking these concepts until one of the following sections. I'll try to think about how to make some clear illustrative diagrams, with a particular focus on a single lead section diagram.  –[[user:jacobolus|jacobolus]] [[User_talk:jacobolus|(t)]] 15:56, 17 November 2023 (UTC)
::::(For what it's worth, the proposal above was just for how a lead section could start; I was imagining a few more paragraphs after. But you are probably right that trying to pack enough context into the lead section to make it legible to e.g. high school students in a self contained way is too big a challenge for just the lead section alone.) –[[user:jacobolus|jacobolus]] [[User_talk:jacobolus|(t)]] 16:52, 17 November 2023 (UTC)
::::I wonder if "linear transformation whose outputs are fed as inputs to the same inputs (feedback)" can be made any clearer. –[[user:jacobolus|jacobolus]] [[User_talk:jacobolus|(t)]] 17:13, 17 November 2023 (UTC)
::::I worked a bit more from Tito Omburo's version. Current state: 
::::: {{tq|In [[linear algebra]], it is often important to know which [[vector space|vector]]s have their directions unchanged by a [[linear map|linear transformation]].  An '''eigenvector''' ({{IPAc-en|ˈ|aɪ|g|ə|n|ˌ|v|ɛ|k|t|ər}}) or '''characteristic vector''' is a such a vector.  Thus an eigenvector <math>\mathbf v</math> of a linear transformation <math>T</math> is [[scalar multiplication|scaled by a constant factor]] <math>\lambda</math> when the linear transformation is applied to it: <math>T\mathbf v=\lambda \mathbf v</math>.  The corresponding '''eigenvalue''', '''characteristic value''', or '''characteristic root''' is the multiplying factor <math>\lambda</math>. {{pb}} [[Euclidean vector|Geometrically, vectors]] are multi-[[dimension]]al quantities with magnitude and direction, often pictured as arrows. A linear transformation [[Rotation (geometry)|rotates]], [[Scaling (geometry)|stretches]], or [[Shear mapping|shears]] the vectors it acts upon. Its eigenvectors are those vectors that are only stretched, with no rotation or shear. The corresponding eigenvalue is the factor by which an eigenvector is stretched or squished. If the eigenvalue is negative, the eigenvector's direction is reversed. {{pb}} The eigenvectors and eigenvalues of a transformation serve to characterize it, and so they play important roles in all the areas where linear algebra is applied, from [[geology]] to [[quantum mechanics]]. In particular, it is often the case that a system is represented by a linear transformation whose outputs are fed as inputs to the same inputs ([[feedback]]).  In such an application, the largest eigenvalue is of particular importance, because it governs the long-term behavior of the system, after many applications of the linear transformation, and the associated eigenvector is the [[steady state]] of the system.}}
:::: This is definitely not entirely lay-accessible, but I think we can further introduce/unpack vectors, vector addition and scalar multiplication, linear transformations, etc. in one of the immediately following sections. It would also probably be good to write some more introductory explanations of the effect of a repeatedly (or continuously) applied transformation – does anyone have recommend sources explaining this clearly? –[[user:jacobolus|jacobolus]] [[User_talk:jacobolus|(t)]] 17:36, 17 November 2023 (UTC)
:::::I am very satisfied with the recent revisions by multiple editors to the lede section. The effort shows what's possible for an article on a such a specialized topic that not many people in the general public ever heard of. Thanks. [[User:DonFB|DonFB]] ([[User talk:DonFB|talk]]) 18:54, 17 November 2023 (UTC)
:Just even glancing at this, the ''order'' of the sections alone would be of great help to improve the article, keeping in mind that our articles in general should move from most general to most specific. Having a definition with a mathematical formula front and center is a problem; instead, putting the Overview first (and eliminating mathematics in that) followed by History then delving into the Definition and other sections would do wonders. [[User:Masem|M<span style="font-variant: small-caps">asem</span>]] ([[User Talk:Masem|t]]) 05:12, 16 November 2023 (UTC)
:: Perhaps an unpopular opinion, but an article about a mathematics concept should have a definition of the concept very early in the article, and arguably even part of the lede.  Otherwise it would be less accessible to many likely readers.  And the idea of "eliminating mathematics" from an article about mathematics seems totally misguided.  [[User:Tito Omburo|Tito Omburo]] ([[User talk:Tito Omburo|talk]]) 15:37, 16 November 2023 (UTC)
:::I've attempted, above, to offer a layman's definition as the first sentence. I don't think anyone is suggesting "eliminating mathematics" from this article, not even me. I do strongly urge, though--in accordance with policy--that the introductory section be written for laymen, and should have very little--if any--math symbology or equations. After the introduction, go hog wild with math; that seems appropriate. [[User:DonFB|DonFB]] ([[User talk:DonFB|talk]]) 20:15, 16 November 2023 (UTC)
::::The previous editor suggested "eliminating mathematics".  My basic position on the lede is that it should summarize the article, giving due weight as per reliable sources. In a mathematics article, that means that it will have to summarize the mathematical content of the article, not giving undue weight to introductory matters. It should be accessible when possible, but not at the expense of doing what it's supposed to do.  A separate introductory section is often appropriate, but lots of introductory stuff often doesn't belong in the lead. [[User:Tito Omburo|Tito Omburo]] ([[User talk:Tito Omburo|talk]]) 00:36, 17 November 2023 (UTC)
We should continue this conversation on the article talk page, leaving a little note and link here. [[User:DonFB|DonFB]] ([[User talk:DonFB|talk]]) 01:46, 16 November 2023 (UTC)
:The point is not to fix this one article, but to focus the discussion on something concrete.  Therefore in my opinion the discussion belongs here. --[[User:Trovatore|Trovatore]] ([[User talk:Trovatore|talk]]) 03:09, 16 November 2023 (UTC)
::I'm not gonna make a big deal of it, but really, this page is supposed to be talking about the Guideline, not host extended discussions of specific articles. After the initial talk here about Bijection, I continued the interaction with Jacobolus on that talk page. This page could be used to alert editors to new discussions about specific articles, and the discussions could continue at those specific pages. Does not seem quite proper to hijack this page for long talks about individual articles. But I won't say more. [[User:DonFB|DonFB]] ([[User talk:DonFB|talk]]) 03:25, 16 November 2023 (UTC)
:::The point is that there are many thousands of articles all of which are equally deficient, broken, lackluster, hard-to-understand and need work in general, to bring them into GA-type status. Everyone understands this. How can policy guide this effort? Early parts of this conversation start with a complaint; paraphrasing: "I don't understand this article, therefore it is a bad article." When this statement was challenged, the reply was "Well, I can prove its a bad article because it violates policy 6 & 7". When this is challenged, an experiment is proposed: "Is it possible, in general, to take some popular article, and bring it into conformance with policy?" As can be seen, this becomes surprisingly difficult. Of course, the conversation can be moved to the article talk page, but that doesn't resolve the earlier policy dispute. 
:::WPMath has something like 20K articles, WPPhysics has a similar number. Throw in WP Astronomy, Chemistry, Engineering, you've got maybe 80K or 120K pages all of which violate policy. How did we end up here? How many math/phys/eng editors are there? Maybe 50K? Maybe 100K? How is it that a hundred thousand editors, all working with the best of intentions, created 100K-odd pages that are unacceptable from a policy standpoint? Maybe, if we can understand how we got to here, we can find a way to do things better. Create a policy that is workable and works to change the attitude of a vast ocean of editors. That's my rah-rah go-get-em speech. Privately, I'm not so sure. We haven't reached agreement as to what the problem is, never mind how to fix it. [[Special:Contributions/67.198.37.16|67.198.37.16]] ([[User talk:67.198.37.16|talk]]) 06:23, 16 November 2023 (UTC)
::::I don't think these articles "violate policy", and I frankly don't think trying to solve this problem with a top-down "policy" hat on is that useful. What I would say instead is that these articles need love and attention from people who are explicitly trying to make them more accessible. It's hard work and takes prioritization. Each one has to be taken one at a time, takes days (weeks, months) of dedicated effort (finding sources, synthesizing them, writing clear prose, drawing pictures, debating which version is most useful, etc.), and there are indeed a lot of them.
::::But then if you consider that a wikipedia article about any of these topics is likely to get at least an order of magnitude more readers than the next most popular source, you can see the beneficial impact of even tackling a single article, especially some of the most popular ones. Each time a Wikipedia article is made into a great resource about some topic, a lot of future readers benefit. –[[user:jacobolus|jacobolus]] [[User_talk:jacobolus|(t)]] 06:55, 16 November 2023 (UTC)
:::::Policy drives behavior, and sometimes bad behavior. Fifteen years ago, there was a Category::Proof that contained all math articles that had embedded proofs (embedded proofs were (are?) considered controversial, so the category was a way of tracking those. After 3-4 years, someone put it up on Categories for deletion. There was no policy to notify WP:M, and so there was no rally to defend. Non-math people voted to delete it. Poof, it was gone. Six months later, it was recreated as a category for all of the recordings released by some rap artist called "[[Proof (rapper)]]". Here: [[:Category:Proof]] Oh, well, now its just a redlink, I see. Well, anyway, if there had been some appropriate policy, then maybe this drive-by shooting of a large category would not have happened. [[Special:Contributions/67.198.37.16|67.198.37.16]] ([[User talk:67.198.37.16|talk]]) 07:12, 16 November 2023 (UTC)
:::Just to give a flavor of the scope of work, below is the current assessment table. Note that there are 166 GA-level articles. The Eigenvalue article is assessed as B-class, High priority. Based on the theory of statistical sampling, Eigenvalue is typical of B-class articles. It is safe to assume that they're all like this. All of them, or, precisely, all except 166 out of 27K will be hard to understand, and inaccessible to anyone without a formal education in math. In numbers, that's 99.4% of them. Now what? [[Special:Contributions/67.198.37.16|67.198.37.16]] ([[User talk:67.198.37.16|talk]]) 06:39, 16 November 2023 (UTC)

{{User:WP 1.0 bot/Tables/Project/Mathematics}}

People often say that our math article should follow the model set by the encyclopedia Britannica. I do not agree with this, but it is instructive to compare our article with theirs:
{{Blockquote|1=When studying linear transformations, it is extremely useful to find nonzero vectors whose direction is left unchanged by the transformation. These are called eigenvectors (also known as characteristic vectors). If v is an eigenvector for the linear transformation T, then T(v) = λv for some scalar λ. This scalar is called an eigenvalue. The eigenvalue of greatest absolute value, along with its associated eigenvector, have special significance for many physical applications. This is because whatever process is represented by the linear transformation often acts repeatedly—feeding output from the last transformation back into another transformation—which results in every arbitrary (nonzero) vector converging on the eigenvector associated with the largest eigenvalue, though rescaled by a power of the eigenvalue. In other words, the long-term behaviour of the system is determined by its eigenvectors.}}
Notably, the second sentence of the article includes an equation, the first sentence uses the forbidden term "linear transformation". [[User:Tito Omburo|Tito Omburo]] ([[User talk:Tito Omburo|talk]]) 00:46, 17 November 2023 (UTC)

== A related [[MOS:LEAD]] discussion ==

{{FYI|pointer=y}}
Please see: [[Wikipedia talk:Manual of Style/Lead section#A wording dispute about technical material]]. <span style="white-space:nowrap;font-family:'Trebuchet MS'"> — [[User:SMcCandlish|'''SMcCandlish''']] [[User talk:SMcCandlish|☏]] [[Special:Contributions/SMcCandlish|¢]] 😼 </span> 20:17, 16 November 2023 (UTC)

== Should all articles be understandable? ==

The current scope of this guideline is to make ''technical'' articles understandable. I've been toying with the idea to write an proposed guideline about [[readability]], to apply more broadly, but this would overlap with this guideline. Roughly 70% of the guideline already applies across the board. Non-technical articles (for instance about sport) may have jargon, and even articles without jargon can be made overly difficult when people use unnecessary academic language. 

To do this, I would like reorganise and slightly expand the content related to reading level and [[readability]], in a new section ''Choose the right reading level''. A lot of this content is now collected under "Avoid overly technical language", where it doesn't fit well and has poor examples. In this section, I would like to give better examples of simple writing styles and link to copy-editing exercises such as [[WP:REDEX]], which improve readability without compromising on content..

A possible new name for the guideline is 'Make articles understandable'. How does that sound? Happy to propose new text here if there is some interest. [[User:Femke|—Femke 🐦]] ([[User talk:Femke|talk]]) 10:04, 4 January 2025 (UTC)

:If I understand, you want to include a new section in this Guideline about readability, and also rename (not replace) this Guideline. Would your new Readability section replace the existing section "Avoid overly technical language", or would that section remain as is? [[User:DonFB|DonFB]] ([[User talk:DonFB|talk]]) 10:49, 4 January 2025 (UTC)
::That's mostly right. I would like to split the section "Avoid overly technical language" into two. Keep the bullets points on jargon etc there, but move the bullet points on sentence lenght etc into the new readability section. [[User:Femke|—Femke 🐦]] ([[User talk:Femke|talk]]) 10:56, 4 January 2025 (UTC)
:::Seems reasonable. I'm primarily concerned with the introductory or lead ("lede") section of articles. I have opined at length about the need to write the lede in plain English, with little or no jargon and few or no links to other articles. Too often, editors use jargon and links in the lede as a substitute for basic definitions or brief explanations. This practice derails readers looking for a readable summary of the subject. They're confronted with opaque terms or multiple links to the introduction of other articles, which themselves may be larded with jargon and links to yet more articles. The text in the body of many articles is indeed highly technical, but I'm not overly concerned about that. The introduction, however, may be the only part of an article seen by the majority of readers, most of whom are probably not experts in the subject. I think we, as an encyclopedia-writing community, are obligated to do our best to make the introduction comprehensible to anyone. [[User:DonFB|DonFB]] ([[User talk:DonFB|talk]]) 13:04, 4 January 2025 (UTC)
:::: I strongly agree the lead is the most important bit to get right. I'm not mentioning it explicitly here, as I believe [[WP:explainlead]] is already clear on the topic. In terms of process, I believe there are two steps: 1) see if there is consensus on a readability section and 2) a possible RM to widen the scope of this guideline. [[User:Femke|—Femke 🐦]] ([[User talk:Femke|talk]]) 14:40, 4 January 2025 (UTC)
:I don't think a name/scope change/reorganization seems that useful, and am opposed to changing it without a better reason than this. Technical articles in particular have somewhat different needs and audiences than other types of articles. This page should not be interpreted to mean that "non-technical" articles should be unreadable, but specific advice about how to structure and pitch technical articles to make them useful to the full range of audiences isn't especially applicable to the typical Wikipedia article. –[[user:jacobolus|jacobolus]] [[user_talk:jacobolus|(t)]] 07:51, 5 January 2025 (UTC)

=== Proposed readability section ===
{{tq2|
'''Use the right reading level'''
{{shortcut|WP:READINGLEVEL|WP:READABILITY}}
Each reader has a different [[reading level|reading ability]]. Teenagers and non-native speakers may require plainly written texts, but even professionals prefer plain and clear text over complicated prose. Research shows that text on Wikipedia tends to be overly difficult.<ref>E.g. {{Cite journal |last=Naveed |first=Muhammad Shumail |date=2024-11-25 |title=Readability of wikipedia pages on COVID-19 |url=https://doi.org/10.1007/s10209-024-01180-5 |journal=Universal Access in the Information Society |doi=10.1007/s10209-024-01180-5 |issn=1615-5289}}</ref> To make sure most interested readers can understand the article, use plain but formal English.

* '''Use short sentences and short paragraphs.''' Readers start to struggle when the average sentence is longer than 12 words. However, using too many short sentences in a row becomes dull and awkward; use a mix of sentence lengths to keep the reader engaged.  Similarly, split long paragraphs into smaller ones.
* '''Write [[Wikipedia:TERSE|concisely]]''' and avoid redundancy. For instance, replace "The majority of critics gave the film negative reviews." with "Most critics gave the film negative reviews". [[WP:REDEX|These exercises]] help you recognize redunancy.
* '''Avoid overly difficult words'''. For instance, write "use" rather than "utilise", or "help" rather than "facilitate". 
<s>* '''Use active voice'''. For instance, replace "The cat was chased by the dog" with "the dog chased the cat".</s>
* '''Eliminate long strings of adjectives''', particularly technical adjectives.
* '''Use bullet points when appropriate'''. 

<s>Various online tools give an <u>rough</u> indication of the reading level. For instance, the [https://hemingwayapp.com/ Hemingway App] estimates the [[Educational_stage#United_States|US grade level]] of your text, while [https://www.thefirstword.co.uk/readabilitytest The first word] has a more generic readability score and average sentence length.</s>
{{reflist-talk}}
}}

This draws on text from the {{sl|WP:MTAU#Audience}} and {{sl|WP:MTAU#Avoid overly technical language}}. I've removed the bullet point about using more verbs, as I don't see how this helps understandability. I've added a bullet point on bullet points, conciseness and overly difficult (non-jargon) words. I'm not 100% happy with my proposed section title, so keen to hear others. [[User:Femke|—Femke 🐦]] ([[User talk:Femke|talk]]) 14:40, 4 January 2025 (UTC)
:OK, so this isn't my only or maybe even most important thought, but my eye was grabbed by the bit about active voice.  It may be worth mentioning that, other things being equal, active voice is more easily understood than passive voice.  But there are editors who take it as some sort of rule that passive voice should always be converted to active, which is not true; when the grammatical object of the verb is significantly more relevant than the grammatical subject, other things are ''not'' equal, and it's often a good idea to use passive voice rather than introduce an unimportant verb subject.
:I would be OK with it if it's clarified that it's a point to consider, but that passive voice is often useful and should not be blindly converted to active. --[[User:Trovatore|Trovatore]] ([[User talk:Trovatore|talk]]) 21:10, 4 January 2025 (UTC)
::I don't think this is specific to technical articles, and therefore I think it should be proposed for one of the [[Wikipedia:Manual of Style]] pages.  (I think we need a page that is specific to technical articles, regardless of whether we also have one for (e.g.) pop culture or business articles.)
::Overall, I suggest that you read https://www.uxmatters.com/mt/archives/2019/07/readability-formulas-7-reasons-to-avoid-them-and-what-to-do-instead.php and maybe think about why FACs are supposed to have "brilliant prose" instead of "short sentences". [[User:WhatamIdoing|WhatamIdoing]] ([[User talk:WhatamIdoing|talk]]) 01:21, 5 January 2025 (UTC)
:::Because you mentioned the Hemingway app (which I find valuable when simplifying text for translation), I have written [[Wikipedia:Readability tools]].  To give you an idea of how (un)helpful they are if you don't know what you're doing and how to react to the results, note that the single word <code>Wikipedia</code> scores everything from Kindergarten level all the way up through post-graduate. [[User:WhatamIdoing|WhatamIdoing]] ([[User talk:WhatamIdoing|talk]]) 05:36, 5 January 2025 (UTC)

In terms of passive voice, can you think of a concise way to make this clear? 

Regarding the tools: I've added the word rough to the proposed text. The way I rewrote the advice (Hemingway is already mentioned), was to stress it just gives an impression of reading level. I believe they work well as a "wake-up" tool, and that simplifying text is usually best done without the tools. 

Compared to the current guideline, I've weakened the statement about sentence length. Sentence length is almost always mentioned in readability guidelines elsewhere. I don't think text can be engaging if average sentence lenght is too high, at least not to a wide audience.  I don't see a trade-off there between the FAC criteria and the need for readability. [[User:Femke|—Femke 🐦]] ([[User talk:Femke|talk]]) 08:44, 5 January 2025 (UTC)

:On the passive, I’m not sure how simple you can make it. An encyclopaedia is one place that the passive voice should be more common than it is elsewhere, and I frequently find myself changing a sentence to the passive to help readability. The best way I find to think about it is to consider an article about a person ({{tq| “'''Joe Smith''' invented the foo process in 1991…”}}) compared to an article about a passive thing ({{tq| “The '''foo process''' was invented by Joe Smith…”}}). But in an extended passage, it may work better to switch: {{tq| “By 1987, Smith’s bar process had begun to prove inefficient at scale, and he began work on an alternative. Working with help from Jones again, Smith formulated the foo process using a salt bath instead of…”}}. Really the editor just has to use judgement, and I wouldn’t want to encourage one way or another as a rule. <span style="font-family:Avenir, sans-serif">—&nbsp;<span style="border-radius:5px;padding:.1em .4em;background:#faeded">[[User:HTGS|HTGS]]</span>&nbsp;([[User talk:HTGS|talk]])</span> 10:30, 5 January 2025 (UTC)
:: I've removed it. In practice, I rarely switch voice when I rewrite a Wikipedia article to be understandable. In academic writing, this comes up a lot (people using stilted passive voice to sound more formal), but perhaps less so here? If we go for the more difficult route of a separate guideline, we can put examples where switching from either passive or active makes the sentence easier. [[User:Femke|—Femke 🐦]] ([[User talk:Femke|talk]]) 11:12, 5 January 2025 (UTC)

=== Where should the readability content be ===
(splitting the "where" discussion from the "what")
:This seems somewhat off topic and out of scope for this page. Maybe propose adding such advice at some other page? –[[user:jacobolus|jacobolus]] [[user_talk:jacobolus|(t)]] 07:54, 5 January 2025 (UTC)

@[[User:Jacobolus|Jacobolus]]: What other page do you think the current/expanded guidance can be moved to? [[WP:ACCESSIBILITY]] might make some sense, but would be more surprising than keeping it here, as people rarely connect readability to specific disabilities.

@[[User:WhatamIdoing|WhatamIdoing]]: the reason I'm proposing we create one guideline for understandability is that there is not a clear separation between making technical articles clear, and making articles understandable in general. For instance, adding examples is useful even for less technical articles. Most of the guideline will naturally be about technical articles, as that's where we're failing most with regard to understandability. If you want to explain difficult concepts, readability is one tool in your toolbox. 

From a more practical POV: I think the alternative is to develop an entire new (MOS) page, and try to get consensus for that. I imagine that would be much more difficult than doing a reorganisation and minor expansion on the current readability text in this guideline, even if we decide not to rename the page. I furthermore don't want us to get more P&Gs; it's already tough to become familiar with the current ones. [[User:Femke|—Femke 🐦]] ([[User talk:Femke|talk]]) 08:46, 5 January 2025 (UTC)

:I think your proposal substantially misses the purpose of this current page: giving advice specifically to editors of technical articles about how to make those articles broadly accessible, along with some discussion about why that is important, which also serves as an easy place to point editors when this topic comes up in talk page conversations. I don't think your proposed changes would be particularly helpful at supporting that purpose, and might even harm it via distraction and loss of focus. Personally I don't think recommendations to use the easiest-to-read possible prose are appropriate as a site-wide recommendation for a general encyclopedia, or at least not without extensive discussion of context and qualification, but in any event I don't think they belong here. –[[user:jacobolus|jacobolus]] [[user_talk:jacobolus|(t)]] 10:49, 5 January 2025 (UTC)
::To me, this guideline will be more focussed after the reorganisation, as more general readability advice is separated from the more concrete advice around technical articles. At the moment, it's mixed. 
::I'm not saying we should use the "easiest-to-read" prose. Readability is a function of expected audience, and just like with technical difficulty, should use [[WP:ONEDOWN]] to get the level right. Which again shows the two are heavily interlinked. [[User:Femke|—Femke 🐦]] ([[User talk:Femke|talk]]) 11:08, 5 January 2025 (UTC)
:::Adding more material to the page which is not focused on making technical articles understandable will make it less focused, regardless of how the sections are organized. I tend to agree with {{u|jacobolus}} here; as far as I can tell, it seems like your proposal would make this page less useful for the purpose it currently serves. [[User:XOR&#39;easter|XOR&#39;easter]] ([[User talk:XOR&#39;easter|talk]]) 18:46, 6 January 2025 (UTC)
:[[Wikipedia:Writing better articles]] is a possibility for general advice. [[User:WhatamIdoing|WhatamIdoing]] ([[User talk:WhatamIdoing|talk]]) 07:09, 6 January 2025 (UTC)
:: Hah, that's quite an eclectic explanatory essay, with some sections already related to readability. I've often cited parts of the page, but never really registered it's all on one page. A readability section would fit. The key disadvantage of putting it there is that topics related to understandability (conciseness, know your audience) are interspersed with other topics, which means it works less as a didactic tool compared to a more focussed placement here. [[User:Femke|—Femke 🐦]] ([[User talk:Femke|talk]]) 13:33, 6 January 2025 (UTC)
:::Most of our help pages would benefit from re-organizing and de-duplication. [[User:WhatamIdoing|WhatamIdoing]] ([[User talk:WhatamIdoing|talk]]) 18:48, 6 January 2025 (UTC)
::::Very much so. Our articles can be pretty bad about this, but our documentation is worse. [[User:XOR&#39;easter|XOR&#39;easter]] ([[User talk:XOR&#39;easter|talk]]) 18:52, 6 January 2025 (UTC)

== Readability score pseudo-science ==

Can we please put this American readability grade-score pseudo-science to bed. I see above that WAID has written [[Wikipedia:Readability tools]] which is inspired from discussions I've had with them over the years, and in particular the excellent article [https://www.uxmatters.com/mt/archives/2019/07/readability-formulas-7-reasons-to-avoid-them-and-what-to-do-instead.php Readability Formulas: 7 Reasons to Avoid Them and What to Do Instead]. In short, the scores themselves are bunk and the advice such websites offer is also bunk. Readability isn't something you can measure with a simple tool and score with a grade. The tools encourage mindless editing that produces short choppy sentences and eliminates important terms and facts.

The readability of text can only be measured by involving a human brain. Ask a friend to read your text out loud. What do they stumble on. Ask them which bits they found hard to understand. Did they find it engaging enough that they want to read the rest of the article, or so off-putting that they made excuses to go? Improving the readability of prose is more than word length and sentence length. Having the first clue about the subject one is trying to explain is, in my view, a tad more important. Introducing concepts the reader must learn and avoiding jargon they don't need. Organising it into sections and paragraphs and illustrating it with diagrams and pictures. These tools help not one bit with the ''important'' aspects of brilliant prose.

As a test, I took the NHS Website pages for a complicated condition: https://www.nhs.uk/conditions/tuberous-sclerosis/. The NHS pages are aimed to be highly accessible and highly regarded for such. Let's look at the opening sentence and how one of our student editors, who have been asked to use Hemingway to improve it, might get on.

===Lead===
{{tq|Tuberous sclerosis, also known as tuberous sclerosis complex, is a rare genetic condition that causes mainly non-cancerous (benign) tumours to develop in different parts of the body.}}

Hemingway tells me this is "very hard to read" and colours it angry red. It's like a computer game. I'm encouraged to turn this text background white. It suggests {{tq|This sentence is too long and complex. Use shorter sentences and simpler words.}} This is a defining sentence, giving the reader the name of the condition and a very brief description about what TSC is. The literature uses two names for the condition: the full name tuberous sclerosis complex, and the original shorter name of tuberous sclerosis. Our student takes the scissors to the parenthetical to make two sentences.

{{tq|Tuberous sclerosis is a rare genetic condition that causes mainly non-cancerous (benign) tumours to develop in different parts of the body. Tuberous sclerosis is also known as tuberous sclerosis complex.}}

Hemingway tells me the first sentence is still "very hard to read", with the same problem (length) and solution (chop chop). Let's split the sentence in two.

{{tq|Tuberous sclerosis is a rare genetic condition. It causes mainly non-cancerous (benign) tumours to develop in different parts of the body. Tuberous sclerosis is also known as tuberous sclerosis complex.}}

Hemingway tells me the second sentence is still "hard to read". We explained to the reader that non-cancerous tumours are termed "benign tumours" by professionals. We could eliminate that bit of technical language.

{{tq|Tuberous sclerosis is a rare genetic condition. It causes mainly non-cancerous tumours to develop in different parts of the body. Tuberous sclerosis is also known as tuberous sclerosis complex.}}

Now Hemingway isn't happy about "mainly". It says that's an adverb and I should use a forceful verb instead. Our student editor can't figure out how to forcefully "cause mainly" so just removes the word.

{{tq|Tuberous sclerosis is a rare genetic condition. It causes non-cancerous tumours to develop in different parts of the body. Tuberous sclerosis is also known as tuberous sclerosis complex.}}

Hemingway is happy with the outcome. I am not. We now have a very clunky trailing sentence that verbosely covers an AKA. The lead sentence is no longer a defining sentence. The "that" in the original is key. That the disease is rare or genetic doesn't define it at all: lots of conditions are those. We've sacrificed the moment to teach the reader that non-cancerous tumours are called benign tumours, which is something they'll need to know for this topic. And we've lost the piece of information that sometimes the tumours it causes aren't non-cancerous, though that is rare. The lead paragraph is now choppy and has all the engagement of random bullet points on a PowerPoint slide. One of our brilliant-prose editors ''could'' perhaps rewrite that lead sentence in a way that reads brilliantly ''and'' mostly satisfies Hemingway. But doing that requires talent, writing experience, and a deep knowledge of the subject so you don't screw up. None of which Hemingway thinks necessary.

===A random symptom===
Another example:

{{tq|Abnormal growths or patches of skin do not usually present a serious health problem, but their appearance can affect a person's confidence and self-esteem..}}

This is also highlighted as being "very hard to read". If I chop it in two

{{tq|Abnormal growths or patches of skin do not usually present a serious health problem. Their appearance can affect a person's confidence and self-esteem.}}

it is now magically perfect. That little chop transformed it from being "very hard to read" to "easy to read". Really? But the original contained an important balance between two kinds of health issue, physical and mental, which is now lost. And now the second sentence misleadingly appears to be making a general point about a person's appearance, rather than the appearance of abnormal growths or patches of skin. 

Other issues are mindless simpler word choice suggestions. "however" is replaced with "but", which is indeed simpler, but (see what I did there) not often appropriate. A sentence on children who may "benefit from" attending a special school suggested instead they should "enjoy" attending a special school. The word "monitor", meaning ongoing repeat examination, is replaced with "check" which does not.

===Research pesudoscience===

The text proposed in the section above said "Research shows that text on Wikipedia tends to be overly difficult." That so-called research did not ask people to read our articles and then take a comprehension test on how well they understood it. Instead they used seven different formulaic readability tools. Why choose seven? That's like asking seven people to look at a tall building and tell you its volume in square metres. They'd ''all'' be hopeless at it. The source claims the Coleman–Liau Index says "the text was too hard for most readers and only appropriate for 11th grade and above." The Flesch-Kincaid Grade Level said "the text was challenging and could only be read by professional readers" On the LIX scale "all pages were extremely difficult to read and required a college-level education". But the LIX scale is

* LIX = wordLength + sentenceLength
:where:
:*wordLength = percent of words of more than six letters
:*sentenceLength = average number of words per sentence

You know, during Covid-19 we all laughed when some eejit suggested ingesting bleach as a cure. Working out whether an article on a novel disease requires the reader to have a "college-level education" or be a healthcare "professional" based on that kind of simplistic pseudo-science is laughable too.

What a bummer that '''coronavirus''' has more that six letters. If we'd had a '''flu''' pandemic, we could all pat our selves on the back for writing super-readable articles. -- [[User:Colin|Colin]]°[[User talk:Colin|<sup>Talk</sup>]] 18:51, 5 January 2025 (UTC)

:Yes, this is a problem.  You really shouldn't use these tools that way.  If you understand a given tool, then you might be able to get some value out of it.  (For example, the Hemingwayapp reminds me to omit needless adverbs.)  But "just try to make the computer happy" is a path to bad writing. [[User:WhatamIdoing|WhatamIdoing]] ([[User talk:WhatamIdoing|talk]]) 06:54, 6 January 2025 (UTC)
:I agree. Don't write for the machine. [[User:XOR&#39;easter|XOR&#39;easter]] ([[User talk:XOR&#39;easter|talk]]) 18:41, 6 January 2025 (UTC)
:I've seen people misuse these readability tools like this before on articles. These tools were not made to analyse individual sentences, and if you use them like that, you get choppy text as you argue; The full NHS page you mention scores well. Calling this pseudoscience feels like OR to me however. You create indices, you validate them (e.g. [https://www.proquest.com/docview/302849850?%20Theses&accountid=196403&fromopenview=true&parentSessionId=2UlwOHIj4T6G5RlltGQ1GkorE9g3WJRsjE2DC5AFXzk%3D&parentSessionId=H%2FINzlMj9XZ8efV6jGmxDnlWuA3D9nKEKssmZ16%2FcmM%3D&pq-origsite=gscholar&sourcetype=Dissertations%20]), and in the next step you use them as is. In medicine, this is how loads of questionaires are designed.
:I would love us to emulate the NHS more in this sense. Two of their guideline documents for writing plainly:
:* [https://service-manual.nhs.uk/content/how-we-write How we write], which roughly corresponds to the advice I suggest we add somewhere in the previous section. Use simple wording (not only avoiding jargon), use bullet points, be concise. 
:* [https://library.nhs.uk/wp-content/uploads/sites/4/2020/08/Health-literacy-how-to-guide.pdf Health literacy ‘how to’ guide] (page 17), with similar advice. 
:Curiously, both documents do point to different readability indices, the second one with appropriate caveats. 
:Do you disagree with the conclusion that Wikipedia's (technical) content is too difficult in general? Even in my own fields (maths, climate, energy), I struggle to read many of our articles. [[User:Femke|—Femke 🐦]] ([[User talk:Femke|talk]]) 19:27, 6 January 2025 (UTC)
::I have also struggled with reading articles here in my own field. The article that {{u|David Eppstein}}, {{u|JayBeeEll}}, {{u|Russ Woodroofe}}, and I recently coauthored [https://arxiv.org/abs/2412.20419] discusses the problem. I am unsure of how to make progress on it to any meaningful extent, other than recruiting more editors who know technical subject matter and care about writing clearly. We could perhaps also do better at prioritizing our efforts and improving the reading experience of the most central/frequently visited articles in technical fields. [[User:XOR&#39;easter|XOR&#39;easter]] ([[User talk:XOR&#39;easter|talk]]) 20:17, 6 January 2025 (UTC)
:::Even though I work hard to write clearly, what I write often uses sentence structures and words that are longer than they need to be. When I notice this, I edit my text to use simpler words and simpler grammar. Tools such as the ones described here can provide helpful reminders to do this. I agree that following their recommendations mechanically can lead to mechanical and uninformative prose, but they can still be useful if used with care. —[[User:David Eppstein|David Eppstein]] ([[User talk:David Eppstein|talk]]) 21:27, 6 January 2025 (UTC)
::I don't think our articles are too hard to read because editors can't find resources about how to write more clearly. Indeed, such resources (both on- and especially off-wiki) abound and are easy to locate by web search or just asking. Our articles are hard to read because (a) the material is often complex and difficult, (b) writing clearly for every possible audience from schoolchildren to professionals is damn hard, and (c) Wikipedia doesn't have enough volunteer author–editors who are both subject experts and excellent writers with the time to devote significant attention to each technical article. –[[user:jacobolus|jacobolus]] [[user_talk:jacobolus|(t)]] 21:20, 6 January 2025 (UTC)
:::I don't struggle to read our articles about medical topics.  I frequently find that they are not well written, but not difficult to understand.  I think one of our problems is that we don't [[Wikipedia:Use our own words]] enough.  I think we often mimic the style of the sources we're citing, which are often journal articles and therefore not using an writing style that is appropriate for an encyclopedia. [[User:WhatamIdoing|WhatamIdoing]] ([[User talk:WhatamIdoing|talk]]) 00:39, 7 January 2025 (UTC)
::::Kudos to authors of articles about medical topics who have managed to make them accessible. My impression is that there are more technical barriers (more complicated and more abstract pre-requisite knowledge that takes more effort for learners to make sense of) in mathematics or extremely mathematical subjects than there is in most other fields. I agree that quite a lot of the problem is too terse and spare a style, and we can certainly do better; I'm all in favor of people trying to make highly technical articles more accessible. But it takes a lot of effort and care. If it were easy, it would already have been done. I don't think pointing people at hemingwayapp or urging them to use short sentences and avoid the passive voice is going to help much. –[[user:jacobolus|jacobolus]] [[user_talk:jacobolus|(t)]] 01:20, 7 January 2025 (UTC)
:::::I'm not sure that we've made our medical articles more accessible.  I can only say that I personally don't find them incomprehensible.
:::::I do think that mathematics has a bigger challenge, because it's more specialized.  [[WP:ONEDOWN]] is easy for medical subjects.  In fact, most parts of an article about a disease could be made understandable to 10 year olds.  But I'm not sure that most advanced math articles could be explained that simply.  At a certain point, you have to be able to think abstractly to understand the math. [[User:WhatamIdoing|WhatamIdoing]] ([[User talk:WhatamIdoing|talk]]) 02:26, 7 January 2025 (UTC)
::If you asked someone what the "readability" of a text is, they might say it is whether the text is '''comprehensible, interesting, or enjoyable'''. The NHS page says {{tq|Being mathematically based, readability tests are unable to determine the likelihood that the document is '''comprehensible, interesting, or enjoyable'''. It’s possible to obtain good readability scores with gobbledygook, providing the content contains short sentences made up of monosyllabic words.}} These readability tools (like Hemingway) are promoted as a tool to help you improve the readability your text, which is pseudo-science. Imagine instead they were promoted as a tool to identify and write self-help books that really changed your life, or instruction manuals that really helped fix your washing machine or romance novels that melted your heart. You'd look at this "how many words have more than six letters" logic from the 1950s and scoff. So why would anyone think they'd help identify and encourage encyclopaedic articles that fill your brain with knowledge?
::A guideline called "Make technical articles understandable" has no business linking to them to achieve that purpose. I accept that if someone wants to use such an automated tool, as a first rough sweep at which Wikipedia articles might be hard to understand, I don't have a problem with that. They'll miss a lot that are hard to understand because the writer didn't understand themselves. And they'll unfairly target subjects with longer names than those with short names. But any tool that thinks "playground" and "elephant" are difficult words because they have more than six letters, has no comprehension whatsoever of what really makes a difficult word. The grade score is a crude measure like assuming a child that is taller than another is older, or that a meal that costs £30 will taste better than one that costs £3. But you can't make someone older by making them stand on a box and you can't make your McDonalds taste better by putting a £20 note in the bun. And yet we have student assignments asking classes to use Hemingway to make our articles better. And all they do is chop sentences and remove the words we're trying to teach. The initial way to help our readers understand a topic is for the editor to first understand it well and read a variety of sources of different levels. Then you stand a chance of explaining it to the general reader.  -- [[User:Colin|Colin]]°[[User talk:Colin|<sup>Talk</sup>]] 14:47, 7 January 2025 (UTC)
:::Wrt the NHS, I agree they do a great job at making their pages accessible. But they have a very different purpose than our good or featured articles. Their primary mission is to help you quickly understand if you need to contact the medical services, or what you can do for yourself. They aren't "encyclopaedic". They write about and give advice for "you" all the time. They aren't afraid to lower themselves to talking about poo and farts if it gets the message. Most of their pages are very short and the reader is only expected to spend a short time on them. So you ''can'' get away with short sentences and loads of bullet points. It ''is'' much closer to a PowerPoint than a booklet. -- [[User:Colin|Colin]]°[[User talk:Colin|<sup>Talk</sup>]] 15:02, 7 January 2025 (UTC)
::::I think our technical articles desperately need clarifying, but I can't see the readability tools making much difference.  I agree with most of the arguments against them above.  In addition, the position of most of the offending expert editors is that they '''can't''' simplify; the jargon and multisyllabic words that make the text opaque have to be in the introduction, or it is bogus.  So they will refuse to use the readability tools. Also as mentioned above, many editors are savvy enough to game the tools, write an incomprehensible intro that still passes, and then say "My intro has a low score, end of discussion." --[[User:Chetvorno|Chetvorno]]<sup><small>[[User talk:Chetvorno|<i style="color: Purple;">TALK</i>]]</small></sup> 03:58, 10 January 2025 (UTC)

===Hemingway===
<small>Inspired by the above discussion of the Hemingway app, I gave chatGPT the prompt {{xtg|Rewrite Wikipedia's article on "tuberous sclerosis" in the style of Ernest Hemingway.}}.  I thought y'all might be interested in the results. --[[User:Trovatore|Trovatore]] ([[User talk:Trovatore|talk]]) 23:46, 6 January 2025 (UTC) </small>

{{collapse|There was a disease, a quiet disease. It did not scream, it did not cry out for attention. But it was there, under the skin, in the mind, in the heart of the body. Tuberous sclerosis. A name like a slow, steady wind blowing across a wide, flat plain.

The body, it carried the weight of it. The skin would show bumps, lumps, strange growths. Nodules, cysts. They were benign, they were harmless in a way, but they were there. Inside the brain, they made the person struggle. Seizures, shaking hands, eyes that did not see right. There were no tears, no easy words. Just the work of living, and the fight to keep going.

It didn’t always show itself when a person was born. Sometimes it came early, like a storm on the horizon, but sometimes it stayed hidden for years. It was in the genes, the DNA that made you, passed down from father to son, from mother to daughter. You could inherit it, and not know it, until you saw the marks on your skin or you saw the fight in your eyes.

Doctors knew of it, but there was no cure. They could manage the pain, the shaking, the confusion. They could help with medicine, maybe surgery, to cut out the parts of you that had gone wrong. But it was a constant. It did not go away, and it did not rest. It lived with you, like a shadow.

The world did not stop for it. You did not stop. You kept moving, walking the road. Life was still there, hard and full, despite the disease. That was the way it was. The fight for life, for what you could hold, was constant. Even when you fought against the unknown. Even when the shadows seemed longer than the light.

Tuberous sclerosis was no more than that: part of the struggle. The struggle to live. To hold on.}}

:Great stuff. Bot could nominate itself for a Pulitzer. [[User:DonFB|DonFB]] ([[User talk:DonFB|talk]]) 00:18, 7 January 2025 (UTC)
: Hemingway's modus operandi was to show only the surface and [[Iceberg theory|omit most of the story]], leaving readers to puzzle it out for themselves. I'm not sure Wikipedia should have similar goals. [Edit: I was also amused at the result.] –[[user:jacobolus|jacobolus]] [[user_talk:jacobolus|(t)]] 02:13, 7 January 2025 (UTC)
:: Yeah, that was similar to what I was thinking when I tried this experiment.  Of course just because the app is called "Hemingway" doesn't imply that it really wants you to write like Hemingway.  It's not a serious contribution to the discussion, just a lark.
:: By the way, you might notice that the text doesn't have much to do with our article on [[tuberous sclerosis]].  I don't think it really looked at the WP article at all.  I tried "Rewrite Wikipedia's article on determinacy in the style of Robert Heinlein", and it gave me something that was clearly about [[determinism]], not [[determinacy]]. --[[User:Trovatore|Trovatore]] ([[User talk:Trovatore|talk]]) 02:28, 7 January 2025 (UTC)

== Edited "audience" section ==

The last sentence of the last paragraph of the "audience" section said {{xt|[t]he article should be written in simple English that non-experts can understand properly.}}.  While this is good advice in general, in context it was contradictory to the main burden of the paragraph in which it occurred, which was explaining the situations in which it may not be possible to write the article in such a way that non-experts can understand it. --[[User:Trovatore|Trovatore]] ([[User talk:Trovatore|talk]]) 19:06, 20 March 2025 (UTC) <small>Further info: The sentence appears to have been added first in [https://en.wikipedia.org/w/index.php?title=Wikipedia%3AMake_technical_articles_understandable&diff=prev&oldid=901394785 this edit] in 2019, then later copyedited. --[[User:Trovatore|Trovatore]] ([[User talk:Trovatore|talk]]) 19:23, 20 March 2025 (UTC) </small>