711:
often summarizing highly technical details can improve the readability of the text for general readers and experts alike. For example, a long-winded mathematical proof of some result is unlikely to be read by either a general reader or an expert, but a short summary of the proof and its most important points may convey a sense to a general reader without reducing the usefulness to an expert reader. When trying to decide what amount of technical detail is appropriate to include, it may be helpful to compare with a standard reference work in the particular technical field to which the subject of the article belongs.
842:) and write the article for readers who are at the previous level. Thus articles on undergraduate topics can be aimed at a reader with a secondary school background, and articles on postgraduate topics can be aimed at readers with some undergraduate background. The lead section should be particularly understandable, but the advice to write one level down can be applied to the entire article, increasing the overall accessibility. Writing one level down also supports our goal to provide a tertiary source on the topic, which readers can use before they begin to read other sources about it.
668:), some subjects naturally attract a more limited audience. A topic that requires many years of specialist education or training prior to being studied or discussed is in general likely to have a more limited audience. For example, a topic in advanced mathematics, specialist law, or industrial engineering may contain material that only knowledgeable readers can appreciate or even understand. On the other hand, many subjects studied at an academically advanced level remain of interest to a wider audience. For example, the
754:
link to another article. Any link to another article should be a supplement to provide more information, and preferably should not be required for understanding text in the lead. For highly specialized topics where it is difficult to give an overview in terms with which a general audience will be familiar, it may be reasonable to assume some background knowledge in the lead while linking to the prerequisites required to understand it. For reference, the lead for a typical
680:
audience. Some topics are intrinsically complex or require much prior knowledge gained through specialized education or training. It is unreasonable to expect a comprehensive article on such subjects to be understandable to all readers. The effort should still be made to make the article as understandable to as many as possible, with particular emphasis on the lead section. The article should be written in simple
English that non-experts can understand properly.
44:
109:
940:
When possible, even for experts it can be helpful to explain in
English why the formula has certain features or is written a certain way. Explaining the "meaning" of a formula helps readers follow along. At a minimum, make sure all the variables in a formula are defined in the article, or have links
796:
are interested in needs to come first. Linked sections of the article should ideally start out at a similar technical level so that if the first, easier paragraph of an article links to a section in the middle of the article, the first part of the section linked to it should also be understandable.
706:
Knowledge strives to be a serious reference resource, and highly technical subject matter still belongs in some
Knowledge articles. Increasing the understandability of technical content is intended to be an improvement to the article for the benefit of the less knowledgeable readers, but this should
679:
Most
Knowledge articles can be written to be fully understandable by the general reader with average reading ability and motivation. Some articles are themselves technical in nature and some articles have technical sections or aspects. Many of these can still be written to be understandable to a wide
1020:
Explain technical terms and expand acronyms when they are first used. In addition, you might consider using them sparingly thereafter, or not at all. Especially if there are many new terms being introduced all at once, substituting a more familiar
English word might help reduce confusion (as long as
753:
In general, the lead should not assume that the reader is well acquainted with the subject of the article. Terminology in the lead section should be understandable on sight to general readers whenever this can be done in a way that still adequately summarizes the article, and should not depend on a
749:
For these reasons, the lead should provide an understandable overview of the article. While the lead is intended to mention all key aspects of the topic in some way, accessibility can be improved by only summarizing the topic in the lead and placing the technical details in the body of the article.
710:
Making articles more understandable does not necessarily mean that detailed technical content should be removed. For instance, an encyclopedia article about a chemical compound is expected to include properties of the compound, even if some of those properties are obscure to a general reader. But
660:
A highly educated, knowledgeable, motivated reader may comfortably read a 5,000-word featured article to the end. Another reader may struggle through the lead and look at the pictures. A good article will grab the interest of all readers and allow them to learn as much about the subject as they are
850:
Many technical articles are not understandable (and more confusing even to expert readers) only because they are abstract. A concrete example can help many readers to put the abstract content in context. Sometimes a contrasting example (counterexample) can also be helpful. For instance, from the
590:
As a free encyclopedia, Knowledge serves readers with a wide range in background, preparation, interests, and goals. Even for articles about the most technically demanding subjects, these readers include students and curious laypeople in addition to experts. While upholding the goals of accuracy,
745:
It is particularly important for the first section (the "lead" section, above the table of contents) to be understandable to a broad readership. Readers need to be able to tell what an article is about and whether they are reading the correct article, even if they don't already know the topic in
1033:
When a less complete or precise explanation is given to improve clarity, preface it with a phrase such as "Generally..." or "With some exceptions..." so the reader knows that there is more complexity behind the explanation. Follow the brief explanatory sentence(s) with more detail, or include a
661:
able and motivated to do. An article may disappoint because it is written well above the reading ability of the reader, because it wrongly assumes the reader is familiar with the subject or field, or because it covers the topic at too basic a level or is not comprehensive.
955:
Visual depictions enable many people to learn more effectively, and allow technical concepts to be communicated in a more concise and clear manner. Diagrams should be related to symbolic or verbal descriptions where appropriate. Some templates that might be useful:
598:
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
750:
The lead of the article should tell a general reader the field of study of the topic, the place the topic holds in its field of study, what (if anything) the topic is good for, and what needs to be learned first in order to understand the article.
1046:
Comprehension decreases when sentence length exceeds about 12 words. However, using too many short sentences in a row becomes monotonous and stilted; vary sentence length to maintain reader interest. Similarly, split long paragraphs into smaller
591:
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. It is especially important to make the
1542:
298:
746:
detail. Those who are only looking for a summary or general definition may stop reading at the end of the lead. An understandable lead encourages readers to continue reading into the body of the article.
1226:
595:
understandable using plain language, and it is often helpful to begin with more common and accessible subtopics, then proceed to those requiring advanced knowledge or addressing niche specialties.
1789:
1382:
1395:
1255:
aims to provide full explanations using a limited subset of
English. It is a resource both for examples (articles) and advice (guidelines) on using simpler language without dumbing down.
1704:
187:
1154:
For topics which are unavoidably technical but, at the same time, of significant interest to non-technical readers, one solution may be a separate introductory article. An example is
792:
It's perfectly fine for later sections to be more technical, if necessary. Those who are not interested in details will simply stop reading at some point, which is why the material
2036:
368:
67:
1140:
1065:
to describe a subject in everyday terms. Avoid far-out analogies. The best analogies can make all the difference between incomprehension and full understanding. However,
1535:
274:
445:
1375:
1185:
Following the advice given in the preceding sections, can the article be made sufficiently understandable as a whole, without the need for a separate introduction?
1163:
454:
1995:
117:
Strive to make each part of every article as understandable as possible to the widest audience of readers who are likely to be interested in that material.
1053:
You can replace many technical adjectives with verbs. For example, instead of saying "Method X is the best one" say, instead: "Method X improves results".
1719:
1368:
182:
2195:
1231:
1059:
Many people use more technical language when writing articles and speaking at conferences, but try to use more understandable prose in conversation.
722:
570:
149:
1990:
1729:
1471:
1211:
1201:
797:
Further, even more-technical sections can often be improved upon by summarizing the main ideas in the first paragraph before going into details.
603:", but they should also be self-contained when possible, and should not take prerequisite knowledge for granted or gratuitously use unexplained
2010:
1796:
1665:
1206:
426:
2256:
645:
On reading ability. Various free online tools can automatically grade the readability of text or highlight complex sentence structures, like
322:
250:
51:
1341:
1221:
33:
2093:
468:
391:
1983:
626:
has no advanced education in the topic's field, is largely unfamiliar with the topic itself, and may even be unsure what the topic is.
405:
800:
Avoid circular explanations: don't define A in terms of B, and B in terms of A. Check to make sure that technical terms are not used
2015:
1392:
1323:
1216:
1139:. Templates added without explanation are likely to be either ignored or removed. Articles containing this template can be found in
359:
1137:
You should put an explanation on the talk page with comments on why you believe it is too technical, or suggestions for improvement
2005:
2000:
981:
415:
2020:
1957:
1466:
1461:
410:
1112:
It is important not to oversimplify material in the effort to make it more understandable. Encyclopedia articles should not "
2261:
1734:
1694:
1635:
1552:
1480:
1456:
1159:
303:
232:
167:
1146:
This tag should be used only on articles which you feel could be improved by someone following the guidelines listed above.
664:
While a member of any of the audience groups may stumble upon an article and decide to read it (for example, by clicking on
830:
A general technique for increasing accessibility is to consider the typical level where the topic is studied (for example,
1630:
223:
126:
2225:
2172:
2046:
1724:
1699:
1645:
563:
520:
515:
506:
475:
350:
313:
293:
209:
177:
172:
135:
2088:
1864:
1811:
1784:
1714:
1689:
755:
650:
463:
199:
162:
607:
or advanced technical notation: shortcuts which save time and effort for experts can be barriers to the uninitiated.
2210:
1660:
1655:
1625:
1530:
1486:
1414:
972:
435:
286:
269:
140:
59:
214:
1978:
1859:
1779:
1562:
1557:
1178:
1010:
1006:
640:
knows the topic but wants to learn more or be reminded about some fact, or is curious about
Knowledge's coverage.
400:
308:
281:
1181:, the number of separate introductory articles should be kept to a minimum. Before you start one, ask yourself
537:
2041:
1947:
1902:
1854:
1849:
1567:
1525:
1491:
1124:
Various templates are available for labeling articles that do not meet agreed standards of understandability.
378:
373:
264:
259:
1311:
1116:" in the sense of giving readers an easy path to the feeling that they understand something when they don't.
2167:
1935:
1520:
1451:
1246:
1155:
835:
556:
1930:
1650:
1640:
1582:
1407:
839:
335:
1801:
1066:
962:
545:
440:
1428:
673:
2234:
2100:
1739:
1615:
1547:
1515:
1476:
1270:
990:
480:
237:
204:
541:
2105:
1806:
1709:
1620:
1610:
1188:
Given the degree of general interest in the topic at hand, might a well-written lead be sufficient?
831:
485:
194:
2117:
2112:
1756:
1605:
1353:
1241:
1130:
1095:
813:
775:
728:
689:
584:
497:
492:
76:
63:
2177:
1952:
1942:
1320:
1282:
340:
1360:
950:
539:
1300:
1291:
2157:
1113:
1082:
600:
1192:
You may start an "Introduction to..." article if the answer to these questions is "no".
1236:
1174:
877:
665:
592:
529:
758:
includes about 20 links to other articles (with a mean lead length around 300 words).
2250:
1826:
1278:
1170:
1078:
929:
17:
2134:
1027:. Substitute technical terms with common terms where they are completely equivalent.
1074:
1034:"robust definition" section so that the article as a whole is complete and precise.
766:
Here are some more ideas for dealing with moderately or highly technical subjects:
2162:
1879:
1070:
633:
has an education in the topic's field but wants to learn about the topic itself.
707:
be done without reducing the value to readers with more technical background.
1266:
1135:
template should be inserted at the top of the corresponding discussion page.
1158:. A complete list of current "Introduction to..." articles can be found in
977:: to overlay many image-symbols + labels onto a map/image (up to 9 markers);
1349:
881:
604:
1025:
If no precision is lost, use common terms instead of technical terms
1319:. U.S. Department of Health & Human Services. August 15, 2006.
1077:. Extensive explanations without a specific source may constitute
864:
1333:
1252:
615:
Knowledge has a varied audience who can be graded in three ways:
1227:
Knowledge:WikiProject
Anatomy/Simplifying anatomical terminology
1069:, so analogies need to be written in an encyclopedic way and be
873:
852:
1364:
543:
669:
646:
546:
103:
38:
1057:
Use language similar to what you would use in a conversation.
995:: to overlay onto an unbordered image, such as open diagrams.
723:
Knowledge:Manual of Style (lead section) § Introductory text
2065:
1127:
For articles that are not sufficiently understandable, the
985:: has examples for any image as a 100-by-100 overlay grid;
62:
may apply. Substantive edits to this page should reflect
1103:
967:: to overlay one image-symbol + label onto a map/image;
821:
783:
736:
697:
91:
84:
1031:
Consider prefacing explanatory sentences with caveats.
1342:"Guidelines for preparing patient education handouts"
1162:, while a list of main articles thus supplemented is
1313:
2142:
2130:
2073:
2063:
2029:
1971:
1911:
1887:
1877:
1834:
1824:
1764:
1754:
1674:
1590:
1580:
1500:
1436:
1426:
32:"WP:TECHNICAL" redirects here. For other uses, see
1141:Category:Knowledge articles that are too technical
672:is of interest to more than just astronomers, and
928:Examples must still meet the same requirement of
1543:Do not include copies of lengthy primary sources
1334:"Plain Language Action and Information Network"
1705:Do not disrupt Knowledge to illustrate a point
1301:"Plain Language Is for Everyone, Even Experts"
1290:Hoa Loranger and Kate Meyer (April 23, 2017).
1044:Use some short sentences and short paragraphs.
1376:
1164:Category:Articles with separate introductions
583:Knowledge articles should be written for the
564:
8:
2131:
770:Put the easier parts of the article up front
2037:Categories, lists, and navigation templates
1346:Center for Professional Practice of Nursing
867:
58:Editors should generally follow it, though
2139:
2070:
1923:
1884:
1831:
1761:
1587:
1433:
1383:
1369:
1361:
1169:In keeping with the spirit of Knowledge's
571:
557:
329:
156:
122:
1292:"Writing Digital Copy for Domain Experts"
676:will interest more than just physicians.
50:This page documents an English Knowledge
1232:Knowledge:WikiProject Mathematics/Proofs
1120:Labeling articles that are too technical
1212:Knowledge:List of Introductory Articles
1207:Knowledge:US government technical terms
1202:Knowledge:Manual of Style/Accessibility
656:By motivation to learn about the topic.
528:
505:
453:
425:
390:
358:
321:
249:
222:
148:
125:
1051:Use more verbs to improve readability.
446:Deletion guidelines for administrators
7:
1222:Knowledge:Many things to many people
1040:, particularly technical adjectives.
1038:Eliminate long strings of adjectives
1018:Use jargon and acronyms judiciously.
2196:List of all policies and guidelines
2235:Summaries of values and principles
2076:
1914:
1677:
1503:
932:that other content is subject to.
66:. When in doubt, discuss first on
25:
1217:Knowledge:Writing better articles
619:On familiarity with the subject.
2145:
1890:
1837:
1767:
1720:Please do not bite the newcomers
1593:
1439:
1299:Hoa Loranger (October 8, 2017).
982:Module:Location map/data/100x100
585:widest possible general audience
107:
42:
1000:Avoid overly technical language
941:to articles that explain them.
1160:Category:Introductory articles
1083:original research by synthesis
1:
1730:Responding to threats of harm
1472:Biographies of living persons
1150:"Introduction to..." articles
189:Don't disrupt to make a point
34:WP:TECHNICAL (disambiguation)
2257:Knowledge editing guidelines
1797:Criteria for speedy deletion
1666:Paid-contribution disclosure
1267:"Topic: Writing for the Web"
1177:guideline, and guideline on
1089:
1021:accuracy is not sacrificed).
684:Technical content assistance
369:Categories, lists, templates
1283:"How Users Read on the Web"
1067:Knowledge is not a textbook
936:Explain formulae in English
651:automated readability index
647:http://www.hemingwayapp.com
210:Other behavioral guidelines
27:Knowledge editing guideline
2278:
1336:. U.S. Federal Government.
1310:"15–Writing Web Content".
1093:
948:
811:
773:
726:
720:
687:
74:
68:this guideline's talk page
31:
2190:
1926:
1402:
1011:Knowledge:Manual of Style
215:WMF friendly space policy
1253:Simple English Knowledge
912:), or a state of being (
351:Other editing guidelines
314:Other content guidelines
183:Don't bite the newcomers
115:This page in a nutshell:
2173:Licensing and copyright
1393:policies and guidelines
1247:Template:Over-explained
1156:Introduction to viruses
868:
846:Add a concrete example
2262:WikiProject Usability
2168:Friendly space policy
1958:Broad-concept article
1467:What Knowledge is not
1462:Neutral point of view
1114:tell lies to children
949:Further information:
872:meaning 'word', is a
721:Further information:
299:Don't copy long texts
18:Knowledge:EXPLAINLEAD
1735:Talk page guidelines
1695:Conflict of interest
1636:Ownership of content
1481:Copyright violations
1457:No original research
1271:Nielsen Norman Group
930:no original research
808:Write one level down
631:knowledgeable reader
233:Talk page guidelines
168:Conflict of interest
127:Knowledge guidelines
1631:No personal attacks
1553:Don't create hoaxes
1281:(October 1, 1997).
884:conveys an action (
674:Alzheimer's disease
304:Don't create hoaxes
2226:List of guidelines
2047:Template namespace
1725:Courtesy vanishing
1700:Disruptive editing
1646:Dispute resolution
1242:Template:Technical
1237:Meta:Reading level
1090:Don't oversimplify
1007:Technical language
904:), an occurrence (
804:they are defined.
516:Naming conventions
294:Offensive material
178:Disruptive editing
173:Courtesy vanishing
2244:
2243:
2186:
2185:
2126:
2125:
2089:Project namespace
2059:
2058:
2055:
2054:
1996:Dates and numbers
1963:Understandability
1873:
1872:
1820:
1819:
1812:Revision deletion
1785:Proposed deletion
1750:
1749:
1715:Gaming the system
1690:Assume good faith
1576:
1575:
1079:original research
973:Location map many
581:
580:
386:
385:
346:Understandability
245:
244:
200:Gaming the system
163:Assume good faith
121:
120:
102:
101:
52:editing guideline
16:(Redirected from
2269:
2221:
2220:
2211:List of policies
2206:
2205:
2163:List of policies
2150:
2149:
2148:
2140:
2136:
2133:
2081:
2080:
2079:
2071:
2067:
2064:Project content
1924:
1919:
1918:
1917:
1895:
1894:
1893:
1885:
1881:
1842:
1841:
1840:
1832:
1828:
1772:
1771:
1770:
1762:
1758:
1682:
1681:
1680:
1661:Child protection
1656:No legal threats
1626:Ignore all rules
1598:
1597:
1596:
1588:
1584:
1531:Reliable sources
1508:
1507:
1506:
1444:
1443:
1442:
1434:
1430:
1415:Ignore all rules
1397:
1385:
1378:
1371:
1362:
1357:
1352:. Archived from
1337:
1329:
1318:
1304:
1295:
1286:
1274:
1134:
1106:
1075:reliable sources
1005:Main guideline:
994:
984:
976:
966:
951:Knowledge:Graphs
871:
824:
786:
756:Featured Article
739:
717:
700:
601:lies-to-children
573:
566:
559:
547:
436:Deletion process
330:
289:
288:Non-free content
270:Reliable sources
190:
157:
123:
111:
110:
104:
94:
87:
46:
45:
39:
21:
2277:
2276:
2272:
2271:
2270:
2268:
2267:
2266:
2247:
2246:
2245:
2240:
2218:
2217:
2203:
2202:
2182:
2146:
2144:
2122:
2077:
2075:
2051:
2025:
1979:Manual of Style
1967:
1915:
1913:
1907:
1891:
1889:
1869:
1865:Page protection
1838:
1836:
1816:
1780:Deletion policy
1768:
1766:
1746:
1678:
1676:
1670:
1594:
1592:
1572:
1563:Patent nonsense
1558:Fringe theories
1504:
1502:
1496:
1440:
1438:
1422:
1398:
1389:
1340:
1332:
1326:
1316:
1309:
1298:
1289:
1277:
1265:
1262:
1198:
1179:content forking
1152:
1128:
1122:
1110:
1109:
1104:WP:OVERSIMPLIFY
1102:
1098:
1092:
1002:
988:
980:
970:
960:
953:
947:
938:
848:
828:
827:
820:
816:
810:
790:
789:
782:
778:
772:
764:
743:
742:
735:
731:
725:
719:
715:
704:
703:
698:WP:TECH-CONTENT
696:
692:
686:
613:
577:
548:
540:
455:Project content
401:Manual of Style
309:Patent nonsense
287:
282:Fringe theories
188:
136:Guidelines list
108:
98:
97:
90:
83:
79:
71:
43:
37:
28:
23:
22:
15:
12:
11:
5:
2275:
2273:
2265:
2264:
2259:
2249:
2248:
2242:
2241:
2239:
2238:
2231:
2230:
2229:
2214:
2191:
2188:
2187:
2184:
2183:
2181:
2180:
2178:Privacy policy
2175:
2170:
2165:
2160:
2154:
2152:
2137:
2128:
2127:
2124:
2123:
2121:
2120:
2115:
2110:
2109:
2108:
2098:
2097:
2096:
2085:
2083:
2068:
2061:
2060:
2057:
2056:
2053:
2052:
2050:
2049:
2044:
2042:Categorization
2039:
2033:
2031:
2030:Classification
2027:
2026:
2024:
2023:
2018:
2013:
2008:
2003:
1998:
1993:
1988:
1987:
1986:
1975:
1973:
1969:
1968:
1966:
1965:
1960:
1955:
1950:
1948:Disambiguation
1945:
1940:
1939:
1938:
1927:
1921:
1909:
1908:
1906:
1905:
1903:Editing policy
1899:
1897:
1882:
1875:
1874:
1871:
1870:
1868:
1867:
1862:
1857:
1852:
1850:Administrators
1846:
1844:
1829:
1822:
1821:
1818:
1817:
1815:
1814:
1809:
1804:
1799:
1794:
1793:
1792:
1782:
1776:
1774:
1759:
1752:
1751:
1748:
1747:
1745:
1744:
1743:
1742:
1732:
1727:
1722:
1717:
1712:
1707:
1702:
1697:
1692:
1686:
1684:
1672:
1671:
1669:
1668:
1663:
1658:
1653:
1648:
1643:
1638:
1633:
1628:
1623:
1618:
1613:
1608:
1602:
1600:
1585:
1578:
1577:
1574:
1573:
1571:
1570:
1568:External links
1565:
1560:
1555:
1550:
1545:
1540:
1539:
1538:
1528:
1526:Citing sources
1523:
1518:
1512:
1510:
1498:
1497:
1495:
1494:
1492:Article titles
1489:
1484:
1474:
1469:
1464:
1459:
1454:
1448:
1446:
1431:
1424:
1423:
1421:
1420:
1419:
1418:
1403:
1400:
1399:
1391:Knowledge key
1390:
1388:
1387:
1380:
1373:
1365:
1359:
1358:
1356:on 2013-12-07.
1338:
1330:
1324:
1307:
1306:
1305:
1296:
1287:
1261:
1260:External links
1258:
1257:
1256:
1249:
1244:
1239:
1234:
1229:
1224:
1219:
1214:
1209:
1204:
1197:
1194:
1190:
1189:
1186:
1151:
1148:
1121:
1118:
1108:
1107:
1099:
1094:
1091:
1088:
1087:
1086:
1060:
1054:
1048:
1041:
1035:
1028:
1022:
1001:
998:
997:
996:
986:
978:
968:
946:
943:
937:
934:
926:
925:
878:part of speech
847:
844:
826:
825:
817:
812:
809:
806:
788:
787:
779:
774:
771:
768:
763:
762:Rules of thumb
760:
741:
740:
737:WP:EXPLAINLEAD
732:
727:
718:
713:
702:
701:
693:
688:
685:
682:
666:Special:Random
658:
657:
654:
643:
642:
641:
634:
627:
624:general reader
612:
609:
579:
578:
576:
575:
568:
561:
553:
550:
549:
544:
542:
538:
536:
533:
532:
526:
525:
524:
523:
518:
510:
509:
503:
502:
501:
500:
495:
490:
489:
488:
478:
473:
472:
471:
458:
457:
451:
450:
449:
448:
443:
438:
430:
429:
423:
422:
421:
420:
419:
418:
413:
408:
395:
394:
388:
387:
384:
383:
382:
381:
379:Disambiguation
376:
374:Categorization
371:
363:
362:
360:Categorization
356:
355:
354:
353:
348:
343:
338:
326:
325:
319:
318:
317:
316:
311:
306:
301:
296:
291:
284:
279:
278:
277:
267:
265:External links
262:
260:Citing sources
254:
253:
247:
246:
243:
242:
241:
240:
235:
227:
226:
220:
219:
218:
217:
212:
207:
202:
197:
192:
185:
180:
175:
170:
165:
153:
152:
146:
145:
144:
143:
138:
130:
129:
119:
118:
112:
100:
99:
96:
95:
88:
80:
75:
72:
57:
56:
47:
26:
24:
14:
13:
10:
9:
6:
4:
3:
2:
2274:
2263:
2260:
2258:
2255:
2254:
2252:
2237:
2236:
2232:
2228:
2227:
2222:
2215:
2213:
2212:
2207:
2200:
2199:
2198:
2197:
2193:
2192:
2189:
2179:
2176:
2174:
2171:
2169:
2166:
2164:
2161:
2159:
2156:
2155:
2153:
2151:
2141:
2138:
2129:
2119:
2116:
2114:
2111:
2107:
2104:
2103:
2102:
2099:
2095:
2092:
2091:
2090:
2087:
2086:
2084:
2082:
2072:
2069:
2062:
2048:
2045:
2043:
2040:
2038:
2035:
2034:
2032:
2028:
2022:
2019:
2017:
2014:
2012:
2009:
2007:
2004:
2002:
1999:
1997:
1994:
1992:
1991:Accessibility
1989:
1985:
1982:
1981:
1980:
1977:
1976:
1974:
1970:
1964:
1961:
1959:
1956:
1954:
1951:
1949:
1946:
1944:
1941:
1937:
1936:Summary style
1934:
1933:
1932:
1929:
1928:
1925:
1922:
1920:
1910:
1904:
1901:
1900:
1898:
1896:
1886:
1883:
1876:
1866:
1863:
1861:
1858:
1856:
1853:
1851:
1848:
1847:
1845:
1843:
1833:
1830:
1823:
1813:
1810:
1808:
1805:
1803:
1800:
1798:
1795:
1791:
1788:
1787:
1786:
1783:
1781:
1778:
1777:
1775:
1773:
1763:
1760:
1753:
1741:
1738:
1737:
1736:
1733:
1731:
1728:
1726:
1723:
1721:
1718:
1716:
1713:
1711:
1708:
1706:
1703:
1701:
1698:
1696:
1693:
1691:
1688:
1687:
1685:
1683:
1673:
1667:
1664:
1662:
1659:
1657:
1654:
1652:
1649:
1647:
1644:
1642:
1639:
1637:
1634:
1632:
1629:
1627:
1624:
1622:
1619:
1617:
1614:
1612:
1609:
1607:
1604:
1603:
1601:
1599:
1589:
1586:
1579:
1569:
1566:
1564:
1561:
1559:
1556:
1554:
1551:
1549:
1546:
1544:
1541:
1537:
1534:
1533:
1532:
1529:
1527:
1524:
1522:
1521:Autobiography
1519:
1517:
1514:
1513:
1511:
1509:
1499:
1493:
1490:
1488:
1485:
1482:
1478:
1475:
1473:
1470:
1468:
1465:
1463:
1460:
1458:
1455:
1453:
1452:Verifiability
1450:
1449:
1447:
1445:
1435:
1432:
1425:
1417:
1416:
1412:
1411:
1410:
1409:
1405:
1404:
1401:
1394:
1386:
1381:
1379:
1374:
1372:
1367:
1366:
1363:
1355:
1351:
1347:
1343:
1339:
1335:
1331:
1327:
1325:0-16-076270-7
1322:
1315:
1314:
1308:
1302:
1297:
1293:
1288:
1284:
1280:
1279:Jakob Nielsen
1276:
1275:
1272:
1268:
1264:
1263:
1259:
1254:
1250:
1248:
1245:
1243:
1240:
1238:
1235:
1233:
1230:
1228:
1225:
1223:
1220:
1218:
1215:
1213:
1210:
1208:
1205:
1203:
1200:
1199:
1195:
1193:
1187:
1184:
1183:
1182:
1180:
1176:
1172:
1167:
1165:
1161:
1157:
1149:
1147:
1144:
1142:
1138:
1132:
1125:
1119:
1117:
1115:
1105:
1101:
1100:
1097:
1084:
1080:
1076:
1072:
1068:
1064:
1063:Use analogies
1061:
1058:
1055:
1052:
1049:
1045:
1042:
1039:
1036:
1032:
1029:
1026:
1023:
1019:
1016:
1015:
1014:
1013:
1012:
1008:
999:
992:
987:
983:
979:
974:
969:
964:
959:
958:
957:
952:
945:Add a picture
944:
942:
935:
933:
931:
923:
919:
915:
911:
907:
903:
899:
895:
891:
887:
883:
879:
875:
870:
866:
862:
858:
857:
856:
854:
845:
843:
841:
837:
836:undergraduate
833:
823:
819:
818:
815:
807:
805:
803:
798:
795:
785:
781:
780:
777:
769:
767:
761:
759:
757:
751:
747:
738:
734:
733:
730:
724:
714:
712:
708:
699:
695:
694:
691:
683:
681:
677:
675:
671:
667:
662:
655:
652:
648:
644:
639:
638:expert reader
635:
632:
628:
625:
621:
620:
618:
617:
616:
610:
608:
606:
602:
596:
594:
588:
586:
574:
569:
567:
562:
560:
555:
554:
552:
551:
535:
534:
531:
527:
522:
519:
517:
514:
513:
512:
511:
508:
504:
499:
496:
494:
491:
487:
484:
483:
482:
479:
477:
474:
470:
467:
466:
465:
464:Project pages
462:
461:
460:
459:
456:
452:
447:
444:
442:
439:
437:
434:
433:
432:
431:
428:
424:
417:
414:
412:
409:
407:
404:
403:
402:
399:
398:
397:
396:
393:
389:
380:
377:
375:
372:
370:
367:
366:
365:
364:
361:
357:
352:
349:
347:
344:
342:
339:
337:
334:
333:
332:
331:
328:
327:
324:
320:
315:
312:
310:
307:
305:
302:
300:
297:
295:
292:
290:
285:
283:
280:
276:
273:
272:
271:
268:
266:
263:
261:
258:
257:
256:
255:
252:
248:
239:
236:
234:
231:
230:
229:
228:
225:
221:
216:
213:
211:
208:
206:
203:
201:
198:
196:
193:
191:
186:
184:
181:
179:
176:
174:
171:
169:
166:
164:
161:
160:
159:
158:
155:
154:
151:
147:
142:
141:Policies list
139:
137:
134:
133:
132:
131:
128:
124:
116:
113:
106:
105:
93:
89:
86:
82:
81:
78:
73:
69:
65:
61:
55:
53:
48:
41:
40:
35:
30:
19:
2233:
2224:
2216:
2209:
2201:
2194:
2158:Terms of Use
2143:
2094:WikiProjects
2074:
2011:Lead section
1962:
1931:Article size
1912:
1888:
1835:
1825:Enforcement
1765:
1675:
1651:Sockpuppetry
1641:Edit warring
1591:
1501:
1437:
1413:
1408:Five pillars
1406:
1354:the original
1345:
1312:
1191:
1168:
1153:
1145:
1136:
1126:
1123:
1111:
1071:attributable
1062:
1056:
1050:
1043:
1037:
1030:
1024:
1017:
1004:
1003:
963:Location map
954:
939:
927:
921:
917:
913:
909:
905:
901:
897:
893:
889:
885:
860:
849:
840:postgraduate
829:
801:
799:
793:
791:
765:
752:
748:
744:
716:Lead section
709:
705:
678:
663:
659:
637:
630:
623:
614:
597:
593:lead section
589:
582:
469:WikiProjects
345:
336:Article size
114:
92:WP:TECHNICAL
49:
29:
1802:Attack page
1790:Biographies
991:Superimpose
863:, from the
441:Speedy keep
224:Discussions
2251:Categories
2106:User boxes
2101:User pages
1740:Signatures
1616:Harassment
1548:Plagiarism
1516:Notability
880:) that in
822:WP:ONEDOWN
784:WP:UPFRONT
521:Notability
486:User boxes
481:User pages
238:Signatures
205:User pages
150:Behavioral
60:exceptions
2113:Shortcuts
1807:Oversight
1755:Deletion
1710:Etiquette
1621:Vandalism
1611:Consensus
1487:Image use
1477:Copyright
1131:Technical
832:secondary
493:Shortcuts
476:Templates
195:Etiquette
77:Shortcuts
64:consensus
2118:Subpages
1984:Contents
1953:Hatnotes
1878:Editing
1860:Blocking
1606:Civility
1581:Conduct
1536:Medicine
1427:Content
1350:UC Davis
1196:See also
1173:policy,
1096:Shortcut
851:article
814:Shortcut
776:Shortcut
729:Shortcut
690:Shortcut
611:Audience
498:Subpages
427:Deletion
406:contents
275:medicine
2016:Linking
1943:Be bold
1855:Banning
1175:WP:LEAD
341:Be bold
323:Editing
251:Content
85:WP:MTAU
2006:Layout
2001:Images
1171:WP:NOT
910:become
906:happen
882:syntax
869:verbum
802:before
605:jargon
530:Search
416:tables
2021:Lists
1972:Style
1317:(PDF)
1081:, or
1047:ones.
922:stand
918:exist
902:learn
886:bring
865:Latin
838:, or
507:Other
411:lists
392:Style
1321:ISBN
1251:The
1166:.
894:walk
890:read
874:word
861:verb
853:verb
794:they
636:The
629:The
622:The
2135:(?)
2132:WMF
2066:(?)
1880:(?)
1827:(?)
1757:(?)
1583:(?)
1429:(?)
1396:(?)
1073:to
1009:in
898:run
670:Sun
2253::
2223::
2208::
1348:.
1344:.
1269:.
1143:.
1133:}}
1129:{{
993:}}
989:{{
975:}}
971:{{
965:}}
961:{{
924:).
920:,
916:,
914:be
908:,
900:,
896:,
892:,
888:,
859:A
855::
834:,
587:.
2219:G
2204:P
2147:P
2078:G
1916:G
1892:P
1839:P
1769:P
1679:G
1595:P
1505:G
1483:)
1479:(
1441:P
1384:e
1377:t
1370:v
1328:.
1303:.
1294:.
1285:.
1273:.
1085:.
876:(
653:)
649:(
599:"
572:e
565:t
558:v
70:.
54:.
36:.
20:)
Text is available under the Creative Commons Attribution-ShareAlike License. Additional terms may apply.