Wikipedia:Talk page guidelines

This page is about talk page etiquette. For general information about talk pages, seeHelp:Talk pages.For guidelines aboutuser talkpages, seeWikipedia:User pages.

"WP:TALK" redirects here. For the page for general discussing, seeWikipedia:Village pump.

The purpose of a page's associatedtalk page(accessible via thetalkordiscussiontab) is to provide space for editors to discuss editing that page. Article talk pages should not be used by editors as platforms for their personal views on a subject. When talk pages in othernamespaces(includinguserspace) are used for discussion and communication between users, discussion should be directed solely toward the improvement of the encyclopedia.

The names of talk pages associated with articles begin withTalk:.For example, the talk page for the articleAustraliais namedTalk:Australia.

The guidelines below reinforce the prime values of talk pages: communication,courtesy,and consideration. They apply not only to article discussion pages but everywhere editors interact, such asdeletion discussionsand noticeboards.

Central points

Maintain Wikipedia policy

There is reasonable allowance for speculation, suggestion, and personal knowledge on talk pages, with a view to prompting further investigation, but it is usually a misuse of a talk page to continue to argue any point that has not metpolicy requirements.Pay particular attention toWikipedia:Biographies of living persons,which applies to talk pages as well as to articles: "Editors must take particular care addinginformation about living personstoanyWikipedia page. "

Creating talk pages

See also:Wikipedia:Welcoming committee/Welcome templates

Talk pages are generally created by clicking a red "Talk" tab and creating the page, like any other page.

Do not create an empty talk page simply so that one will exist for future use. There is no need to add discussion warning templates to every talk page, or even to every talk page that contains a discussion.

How to use article talk pages

For the how-to guide, seeHelp:Talk pages.

Although this section is specific to article talk pages, many of the general themes apply to all discussion pages that are used for collaboration.

• Communicate:If in doubt, make the extra effort so that other people understand you. Being friendly is a great help. It is always a good idea to explain your views; it is less helpful for you to voice an opinion on something butnotexplainwhyyou hold it. Explainingwhyyou have a certain opinion helps to demonstrate its validity to others and reach consensus.
• Stay on topic:Talk pages are for discussing thearticle,not for general conversation about the article's subject (much lessothersubjects). Keep discussions focused on how to improve the article. Comments that are plainly irrelevant are subject toarchivingor removal.
• No meta:Extended meta-discussions about editing belong on noticeboards, in Wikipedia-talk, or in User-talk namespaces, not in Article-talk namespace.
• Be positive:Article talk pages should be used to discuss ways to improve an article; not to criticize, pick apart, or vent about the current status of an article or its subject. This is especially true on the talk pages ofbiographies of living people.However, if you're not sure how to fix something, feel free to draw attention to this and ask for suggestions.
• Be polite:Article talk pages are at the end of the day civil discussions between users who have lives outside ofWikipedia,that influences their behaviors and manners. In serious discussions it is key to remain calm, respectful and patient with the other user. If afallacy(seelist of fallacies) is noticed when debating Wikipedia’s general guidelines, remain civil and above all do not use this to anger the other user. Respectful arguments are rela xing!
• Stay objective:Talk pages are not a place for editors to argue theirpersonal point of viewabout a controversial issue. They are a place to discuss how the points of view of reliable sources should be included in the article, so that the end result isneutral.The best way to present a case is to find properly referenced material.
• Deal with facts:The talk page is the ideal place for issues relating toverification,such as asking for help finding sources, discussing conflicts or inconsistencies among sources, and examining the reliability of references. Asking for a verifiable reference supporting a statement is often better than arguing against it.
• Share material:The talk page can be used to "park" material removed from the article due to verification or other concerns, while references are sought or concerns discussed. New material can be prepared on the talk page until it is ready to be put into the article; this is an especially good idea if the new material (or topic as a whole) is controversial.
• Discuss edits:The talk page is particularly useful to talk about edits. If one of your edits has been reverted, and you change it back again, it is good practice to leave an explanation on the talk page and a note in the edit summary that you have done so. The talk page is also the place to ask about another editor's changes. If someone questions one of your edits, make sure you reply with a full, helpful rationale.
• Make proposals:Proposals for improving the article can be put forward for discussion by other editors. Such proposals might include changes to specific points, page moves, mergers or making a section of a long article into a separate article.

Good practices for talk pages

These guidelines apply specifically to discussion pages which are used for collaboration, which includes just about all talk pages other thanuser talk pages.The application of these guidelines to user talk pages should be governed by common sense and should not supersede guidelines and policies specific to those pages.

• Check whether there's already a discussion on the same topic.Duplicate discussions (on a single page, or on multiple pages) areconfusing and time-wasting,and may be interpreted asforum shopping.If the subject is a controversial or popular one, considerchecking the talk-page archivesbefore opening a new thread. (Many talk pages have aSearch archivesbox near the top.)
• Read before commenting:Familiarizing yourself with a discussion before participating makes it easier to build consensus.
• Commenton content,noton the contributororIt's the edits that matter, not the editor:Keep the discussions focused on the topic of thetalk page,rather thanon the editorsparticipating.
• Use English:This is the English-language Wikipedia; discussions should normally be conducted in English. If using another language is unavoidable, try to provide a translation, or get help atWikipedia:Embassy.Do not expect readers to translate your content themselves, not even when modern browsers have machine translation built-in.
• Be concise:Long posts risk being ignored or misunderstood. Talk pages with a goodsignal-to-noise ratiotend to attract continued participation. If youreallyneed to make a detailed, point-by-point post, seebelowfor tips.
• Keep discussions focused:Discussions naturally should finalize by agreement, not by exhaustion.
• Avoid repeating your posts:Your fellow editors can read your prior posts, so repeating them wastes time and space and may be consideredbludgeoningthe discussion.
• Avoid starting the same discussion on multiple pages,which fragments discussion. Instead, start the discussion in one location and, if appropriate, advertise it elsewhere via a link. If you find a fragmented discussion, consider moving all posts to one location and linking from the old locations to the new. State clearly in edit summaries and on talk pages what you have done and why.(SeeWikipedia:Content forking/Internal § Discussion forks.)
• Do not bite the newcomers:If someone does something against custom,assume it was an unwitting mistake;gentlypoint out their mistake (referencing relevant policies and guidelines) and suggest a better approach.
• Link abbreviations:To assist newbies, consider linking toWikipedia abbreviationsand terms of art when they first appear in a thread.
• Avoid excessive emphasis:ALL CAPS andenlarged fontsmay be consideredshoutingand are rarely appropriate.Boldingmay be used to highlight key words or phrases but should be used judiciously.Italicsare often used for emphasis or clarity but should be avoided for long passages.Exclamation markssimilarly should be used judiciously.Overuseof emphasis canundermineits impact! If adding emphasis to quoted text, say so.
• Keep the layout clear:Use standard formatting andthreading.If you include references, add{{reflist-talk}}or{{sources-talk}}after your comment, to keep citations within your thread. SeeTalk page layout.
• Use separate subsection headings to discuss multiple changes:If you arrive at the "discussion" part of the"bold, revert, discuss"(BRD) cycle, and the subject involves a number of separate changes you would like to see, try to break down the different changes, and your reasons andreliable sourcesfor each one, under separate subsection headings (===Example===). Mi xing it all into one long post complicates discussion.
• Sign your posts.When you have the "Enable quick topic adding"preference enabled and use the" Add topic "link to create a new discussion, or reply to a comment using the" reply "link, then your posts will be automatically signed.Otherwise, you can sign manually using four tildes (~~~~), which turn into your username and a timestamp, like this:ExampleUser14:07, 15 July 2024 (UTC).
• Theminorflagis only for typographical corrections, formatting fixes, and similar changes that do not substantively change content.

Behavior that is unacceptable

Stay in the top three sections of this pyramid.

Please note that some of the following are of sufficient importance to be official Wikipedia policy. Violations (and especially repeated violations) may lead to the offender beingblockedorbannedfrom editing Wikipedia.

• No personal attacks.This includes:
  • Insults:Do not makead hominemattacks, such as calling someone anidiotor afascist.Instead, explain what is wrong with an edit and how to fix it.
  • Personal threats:For example, threatening people with "admins [you] know" or with having them banned for disagreeing with you. However, explaining to an editor the consequences of violating Wikipedia policies, like being blocked for vandalism, is not considered a threat.
  • Legal threats:Threatening a lawsuit is highly disruptive to Wikipedia for reasons given at the linked page.
  • Posting other editors' personal details:A user who maliciously posts what they believe are the personal details of another user without that user's consent may be blocked for any length of time, including indefinitely.
• Misrepresentation of other people:The record should accurately show significant exchanges that have taken place and in the correct context. This usually means:
  • Beingprecisein quoting others.
  • When referencing other people's contributions or edits,use "diffs".The advantage of diffs in referring to a comment is that the diff will always remain the same, even when a talk page getsarchivedor a comment gets changed.
  • Generally,do not alter others' comments, including signatures.Exceptionsto this are described in thenext section.
• Do not ask for another's personal details.
• Do not attempt toimpersonate another editor.
• Do notclaim to be an administratoror to have anaccess levelthat you do not have. User access levels can always be verified atSpecial:ListUsers.
• Do not use the talk page as a forumfor discussing the topic, nor as asoapboxfor promoting your views. The talk page is for discussing how toimprovethe article, not venting your feelings about it.

Editing others' comments

"WP:TPO" redirects here. For talk page order, seeWP:TALKORDER.

It is not necessary to bring talk pages to publishing standards, so there is no need tocopy editothers' posts. Doing so can be irritating. The basic rule, with exceptions outlined below, is to not edit or delete others' posts without their permission.

Neveredit or move someone's comment to change its meaning,even on your own talk page.

Striking out text with<s>...</s>or{{strike}}or marking text as deleted with<del>...</del>constitutes a change in meaning. It should be done only by the user who wrote it, or as otherwise provided in this talk page guideline.

Generally, you should not break up another editor's text by interleaving or interpolating your own replies to individual points. This causes confusion with who said what and obscures the original editor's intent.

In your own posts, you may wish to use the{{Talk quotation}}or{{Talkquote}}templates to quote others' posts.

Cautiously editing or removing another editor's comments is sometimes allowed, but normally you should stop if there is any objection. If you make anything more than minor changes, it is good practice to leave a short explanatory note such as "[potential libel removed by ~~~~]".

Examples of appropriately editing others' comments

• If you have theirpermission,e.g. by invocation ofWP:MUTUAL.
• Restoration:to restore comments vandalized or accidentally edited or deleted by others.
• Personal talk page cleanup:See the section§ User talk pagesfor more details.
• Removing prohibited materialsuch aslibel;legal threats;personal details;content that is illegal under US law; or violations ofcopyright,living persons,oranti-promotionalpolicies. (See alsobelowfor removing comments by banned or blocked users.)
• Removing harmful posts,includingpersonal attacks,trolling,andvandalism.This generallydoesnotextendto messages that are merelyuncivil;deletions of simple invectiveare controversial.Posts that may be considereddisruptivein various ways are another borderline case and are usually best left as-is orarchived.

• Off-topic posts:Your idea of what is off topic may differ from what others think is off topic, so be sure to err on the side of caution.
  • Collapse.If a discussion goes off topic (per the above subsection§ How to use article talk pages), editors may hide it using{{Collapse top}}/{{Collapse bottom}}or similar templates. This normally has the effect of ending the off-topic discussion while allowing people to read it by pressing the "show" link. Involved parties must not use these templates to end a discussion over the objections of other editors.
  • Move.At times, it may make sense to move off-topic posts to a more appropriate talk page. Another form ofrefactoringis to move a thread of entirely personal commentary between two editors to the talk page of the editor who started the off-topic discussion. The template {{subst:Rf}} can be used to denote the original source page of the content.
  • Delete.It is common to simply delete gibberish, test edits, harmful or prohibited material (as described above), and comments or discussion clearly about the article's subject itself (as opposed to comments and discussion about the treatment of the subject in the article).
• Moving edits to closed discussions:A discussion which has been closed with the {{subst:Archive}} or similar template is intended to be preserved as-is and should not be edited. Subsequent edits inside of an archive box should not be removed for this sole reason, but may be moved below the box to preserve the integrity of the closed discussion.
• Attributing unsigned comments:If a comment is unsigned you can find out, from the page history, who posted it and append attribution to it, typically using {{subst:Unsigned}}:{{subst:Unsigned|USER NAME OR IP|DATE AND TIME}}.The date and time parameter is optional.
• Signature cleanup:If a signature violates theguidelines for signatures,or is an attempt to fake a signature, you may edit the signature to the standard form with correct information—{{subst:User|USERNAME}}TIMESTAMP OF EDIT(UTC)or some even simpler variant. Do not modify the signature on others' posts for any other reason. If the user's signature contains a coding error, ask the user to fix the problem in their preferences (but see "Fi xing layout errors",below).
• Fi xing format errorsthat render material difficult to read. In this case, restrict the edits to formatting changesonlyand preserve the content as much as possible. Examples include:
  • Fi xing indentation levels
  • Removing bullets from discussions that are notconsensus pollsorrequests for comment (RfC)
  • Fi xing list markup (toavoid disruptionofscreen readers,for instance)
  • Using<code>,<nowiki>and other technical markup to fix code samples
  • Providing wikilinks if it helps in better navigation
  • Adding{{Reflist-talk}}so that<ref>...</ref>-type material is emitted immediately instead of at the end of the entire page.{{Sources-talk}}does the same while collapsing the references to reduce vertical scrolling.
• Fi xing layout errors,which could include:
  • Moving a new discussion from the top of a page to the bottom
  • Moving a comment for chronological order within a reply sequence
  • Adding a heading to a comment not having one
  • Repairing accidental damage by one party to another's comments
  • Correcting unclosed markup tags that mess up the entire page's formatting
  • Accurately replacing HTML table code with a wikitable
• Sectioning:If a thread has developed new subjects, it may be desirable to split it into separate discussions with their own headings or subheadings. When a topic is split into two topics, rather than sub-sectioned, it is often useful for there to be a link from the new topic to the original and vice versa. A common way of doing this is noting the change at the [then-]end of the original thread, and adding an unobtrusive note under the new heading, e.g.,:<small>This topic was split off from [[#FOOBAR]], above.</small>.Some reformatting may be necessary to maintain the sense of the discussion to date and to preserve attribution. It is essential that splitting does not inadvertently alter the meaning of any comments. Very long discussions may also be divided into sub-sections.
• IDs:Where sectioning is not appropriate, adding{{Anchor}}or{{Visible anchor}}for deep linking.

• Section headings:Because threads are shared by multiple editors (regardless of how many have posted so far), no one, including the original poster, "owns" a talk page discussion or its heading. It is generally acceptable to change headings when a better heading is appropriate, e.g., one more accurately describing the content of the discussion or the issue discussed, less one-sided, more appropriate foraccessibility reasons,etc. Whenever a change is likely to be controversial, avoid disputes by discussing a heading change with the editor who started the thread, if possible. It can also sometimes be appropriate to merge entire sections under one heading (often preserving the later one as a subheading) if their discussions are redundant.
  In order to ensure links to the previous section heading (including automatically generated links in watchlists and histories) continue to work, one should use one of the following templates toanchorthe old title:{{Thread retitled}},{{Visible anchor}},{{Anchor}}.Link markup may be removed from section headings, but the link should be re-created at the first use of the term, or in a hatnote. Template markup should be removed, as this is likely to break links to the heading.
• Removing duplicate sections:Where an editor has inadvertently saved the same new section or comment twice. Note: this does not mean people who repeat a point deliberately.
• Fi xing links:if the linked-to page has moved, a talk page section has been archived, the link is simply broken by a typographical error, or it unintentionally points to a disambiguation page etc. Do not change links in others' posts to go to entirely different pages. If in doubt, ask the editor in question to update their own post, or add a follow-up comment of your own suggesting the alternative link. Only fix a link to a template that has been replaced or deprecated if the effect of the new template is essentially the same as what the poster used (otherwise, simply allow the post tored linkto the old template, as a broken post is preferable to one with altered meaning). Internal links made using full URLs may be converted to wikilinks or protocol-relative URLs (by dropping the part before the "//" ), so that they will work across protocols (http:// vs. https://) and between our desktop and mobile sites.
• Hiding or resizing images:You may hide an image (e.g., change[[File:Foo.jpg|...details...]]to[[:File:Foo.jpg|...details...]]by adding a colon)once discussion of it has ended.This is especially appropriate for "warning" and "alert" icons included in bot-posted notices which are usually quickly resolved. It's OK to re-size images to a smaller size if they take too much space on a talk page.
• Non-free images:Non-free imagesmust not be displayed on talk pages.If they are being discussed, they must be hidden by linking them with a colon—as described in "Hiding or resizing images", above. If they are included for decorative purposes, they must be removed.
• Deactivating templates, categories, and interlanguage links:You may prevent templates from being transcluded (e.g., change{{Template name}}to{{tl|Template name}}) if the poster clearly intended to discuss the template rather than use it. You may deactivate category links (e.g., change[[Category:Foobar]]to[[:Category:Foobar]]by inserting a colon) to prevent the page being inappropriately added to a discussed category. You may deactivate interlanguage links (e.g., change[[it:Foobar]]to[[:it:Foobar]]by inserting a colon) when the link to a page on another language's Wikipedia is meant to appear inline rather than to serve as an interlanguage link for the page.
• Hiding old code samples:You may redact (replace with a note, orcollapse) large code samplesonce discussion of the sample has ended;for instance fulfilled{{Edit fully-protected}}requests.
• Review pages:Peer reviews,good article reviews,andfeatured article candidatesare collaborative processes in which a reviewer may provide a list of comments on an article; most editors expect the responses to be interspersed among these comments. An example ishere;note that you should not modify the comments themselves in any way.
• Removingorstriking throughcomments made by blockedsock puppetsof users editing in violation of a block or ban. Comments made by a sock with no replies may simply be removed with an appropriate edit summary. If comments are part of an active discussion, they should be struck instead of removed, along with a short explanation following the stricken text or at the bottom of the thread. There is not typically a need to strike comments in discussions that have been closed or archived.
• Empty edit requests.If considered necessary, it is acceptable to remove from a Talk page an edit request that does not include a description of the requested change. Consider placing{{subst:empty edit request}}on the User Talk page of a user who has posted an empty edit request.

In the past,it was standard practice to "summarize" talk page comments, but this practice has fallen out of use. On regular wikis with no "talk" tab, the summary would end up as the final page content. Wikipedia has separate tabs for article content and discussion pages.Refactoringandarchivingare still appropriate, but should be done with courtesy and reversed on protest.

Editing own comments

"WP:REDACT" redirects here. For information about redaction from logs or page history, seeWikipedia:Revision deletionandWikipedia:Oversight.

"Wikipedia:Edit comment" redirects here. Not to be confused withHelp:Edit summary.

So long as no one has yet responded to your comment, it's accepted and common practice that you may continue to edit your remarks for a short while to correct mistakes, add links or otherwise improve them. If you've accidentally posted to the wrong page or section or if you've simply changed your mind, it's been only a short while and no one has yet responded, you may remove your comment entirely.

But if anyone has already replied to or quoted your original comment, changing your comment may deprive any replies of their original context, and this should be avoided. Once others have replied, or even if no one's replied but it's been more than a short while, if you wish to change or delete your comment, it is commonly best practice to indicate your changes. An exception to this rule may be permitted if there is only one reply and it invokesWP:MUTUAL.

• Any deleted text should be marked with<del>...</del>,which renders in most browsers as struck-through text, e.g.,deleted.
• Any inserted text should be marked with<ins>...</ins>,which renders in most browsers as underlined text, e.g.,inserted.
• Inserting text without deleting any text is ambiguous, since some editors useunderscorefor emphasis (despite guidance to useitalics). For example: "You commentedin Aprilafter the previous discussion. "Is that insertion, or emphasis? This problem can be avoided by deleting one word and then re-inserting it, as:
  You <del>commented</del> <ins>commented in April</ins> after the previous discussion.
  Thus: "Youcommentedcommented in Aprilafter the previous discussion. "
• Best practice is to add a new timestamp, e.g.,<ins>; edited ~~~~~</ins>,using five tildes, immediately following the original timestamp at the end of your post.
• To add an explanation of your change, you may add a new comment directly below your original or elsewhere in discussion as may be most appropriate; insert a comment in square brackets, e.g.,"the default width is100px120px[the default changed last month] ",or use[[WP:CURRENTSECTION#New section|<sup>[corrected]</sup>]]to insert a superscript note, e.g.^[corrected],linking to a later subsection for a detailed explanation.

Non-compliance

Persistently formatting your comments on a talk page in a non-compliant manner, after friendly notification by other editors, is a mild form of disruption. After you have been alerted to specific aspects of these guidelines (such as indentation, sectioning, and signatures), you are expected to make a reasonable effort to follow those conventions. Other editors may simply ignore additional posts that flagrantly disregard the talk page formatting standards. You can also expect to have your mis-formatted postsrefactoredto comply.

Disputes

If you have a disagreement or a problem with someone's behavior, please readWikipedia:Dispute resolution.

Closing discussions

Main page:Wikipedia:Closing discussions

Closing a discussion means summarizing the results, and identifying any consensus that has been achieved. A rule of thumb is that discussions should be kept open at least a week before closing, although there aresomeexceptions to this.

Anyuninvolvededitor may write a closing statement for most discussions, not just admins. However, if the discussion is particularly contentious or the results are especially unclear, then a request specifically for a closing statement from anuninvolved administratormay be preferable.

Requesting a close

Any participant in a discussion may request that anuninvolvededitor or admin formally close any type of discussion (not just RFCs), if any one or more of the following criteria are true:

• the consensus remains unclear to the participants,
• the issue is a contentious one, or
• there are wiki-wide implications to the decision.

Please do not request a closing statement from anuninvolvededitor unless one of these three criteria have been met.

You may request that an uninvolved editor formally close a discussion by placing a note atWikipedia:Closure requests.Please ensure that any request there seeking a close is neutrally worded, and do not use that board to continue the discussion in question. If you are requesting attention specifically from an admin, then please state that clearly in your request.

Marking a closed discussion

When an issue has been resolved without controversy, this may be marked simply by adding the{{Resolved}}template at the top of the thread, adding a brief statement ofhowthe issue was dealt with. If you took action yourself to resolve the issue you may instead use the{{Done}}template in your own final comment stating what you did. Adding one of these templates will help future readers to spot more quickly those issues that remain unresolved.

When a more complex discussion has been closed, to discourage any further comments you may optionally use the{{Archive top}}and{{Archive bottom}}templates (although some particular types of discussion, such as those which concern whether to delete or rename a page, have their own specialized templates) —{{Archive top}}and{{Archive bottom}}templates should not be used by involved parties to end a discussion over the objections of other editors. For example:

{{Archive top|result=Consensus below is in favor of this proposal. (detailed explanation) ~~~~}}
Discussion text...
{{Archive bottom}}

... which produces:

The following discussion is closed.Please do not modify it.Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.

---

Discussion text...

The discussion above is closed.Please do not modify it.Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.

If a discussion has been so disruptive or pointless that it is better for editors to waste no further time even looking at it, the alternative templates{{Hidden archive top}}and{{Hidden archive bottom}}can be used instead, to produces a similar "closure box" around it, but collapsed to hide the content, as withoff-topic threads.If a particular unconstructive block of an otherwise useful discussion should be hidden, use{{Collapse top}}and{{Collapse bottom}}.

Technical and format standards

Layout

See also:Wikipedia:Talk page layout

• Start new topics at the bottom of the page:If you put a post at the top of the page, it is confusing and can easily be overlooked. The latest topic should be the one at the bottom of the page, then the next post will go underneath yours and so on. This makes it easy to see the chronological order of posts. A quick way to do this is to use the "New section" tab next to the "Edit" button on the talk page you are on.
• Avoid excessive use of color and other font gimmicks:The advice atWikipedia:Manual of Style/Accessibility § Coloris as applicable to talk pages as it is anywhere else. And your post is not more important than anyone else's, so it should not be in huge, purple text.
• Separate multiple paragraphs with whitespace:If a single post has several points, it makes it clearer to separate them with a paragraph break (i.e. a blank line). Exception: Do not use blank lines between lines starting with asterisks (*), colons (:), semicolons (;), or number/hash signs (#). (See section below.) An alternative is using the{{pb}}( "paragraph break" ) template inline in the text without manually linebreaking on either side of it:Lorem ipsum dolor sit amet, consectetur adipiscing elit.{{pb}}Ut enim ad minim veniam, quis nostrud exercitation.

Indentation and screen readers

Summary:WP:LISTGAPfixes: don't change list type, don't skip indentation levels, no extra spaces between replies.

• Avoid adding blank lines betweenanylines that begin with wikitext symbols for lists, because this increases the complexity of the generated HTML code and createsaccessibility problemsfor people usingscreen readers.These symbols include:
  • asterisks (*), which make bulleted lists;
  • hash symbols (#), which make numbered lists;
  • semi-colons (;), which make the first half of an HTML association list (rendered as bold-faced text); and
  • colons (:), which make the second half of an HTML association list, but which are popularly used for the resulting visual indentation effect.
• Thread your post:Use indentation as shown inHelp:Using talk pages § Indentation,to clearly indicate to whom you are replying, as with usualthreaded discussions.Normally colons are used, not bullet points (although the latter are commonly used atAfD,CfD,etc.).

New topics and headings on talk pages

• Start new topics at the bottom of the page:If you put a post at the top of the page, it is confusing and can also get easily overlooked. The latest topic should be the one at the bottom of the page.
• Make a new heading for a new topic:It will then be clearly separated into its ownsectionand will also appear in theTOC(table of contents) at the top of the page. A heading is easy to create with == on either side of the words, as in ==Heading==. The "Post a comment" feature can be used to do this automatically. (If you are using the defaultskin,you can use the "New section"tab next to the" Edit this page "tab instead.) Enter a subject/heading in the resulting edit page, and it will automatically become the section heading.
• Don't create a new heading that duplicates an existing heading:If you are responding to a comment or adding to a discussion on a particular topic, respond after the comment or at the bottom of the existing section.
• Make the heading clear and specific as to the article topic discussed:It should be clear from the heading which aspect of the article (template, etc.) you wish to discuss. Don't write"This article is wrong"but address the specific issue you want to discuss. A related article Edit, actual or potential, should be traceable to that Talk-page heading.
• Keep headings neutral:A heading should indicate what the topic is, but not communicate a specific view about it.
  • Don't praise in headings:You might wish to commend a particular edit, but this could be seen in a different light by someone who disagrees with the edit.
  • Don't criticize in headings:This includes being critical about details of the article. Those details were written by individual editors, who may interpret the heading as an attack on them.
  • Don't address other users in a heading:Headings invite all users to comment. Headings may beaboutspecific edits but not specificallyabout the user.(Some exceptions are made at administrative noticeboards, where reporting problems by name is normal.)
  • Never use headings to attack other users:Whileno personal attacksandassuming good faithapply everywhere at Wikipedia, using headings to attack other users by naming them in the heading is especiallyegregious,as it places their names prominently in the Table of Contents, and can thus enter that heading in the edit summary of the page's edit history. As edit summaries and edit histories are not normally subject to revision, that wording can then haunt them and damage their credibility for an indefinite time period, even though edit histories areexcluded from search engines.Reporting on another user's edits from aneutral point of viewis an exception, especially reportingedit warringorother incidentsto administrators.
• Create subsections if helpful:Talk page discussions should be concise, so if a single discussion becomes particularly long, it may then become helpful to start a subsection (to facilitate the involvement of editors with a slower computer or Internet connection). Since the main section title will no longer appear in edit summaries, choose a connotative title; for example, in the sectionReferences used more than once,the subsection titleReferences: arbitrary breakmight be used. If creating arbitrary breaks, ensure that sections end with a clear indication of the poster. (This method is preferable to using templates like{{Hidden}}.)

Links, time, and page name

• Make links freely:Links to articles are as useful on talk pages as anywhere else, and links to non-existent articles can help get them onto themost-wanted articleslist.
• UseCoordinated Universal Time,when referring to a time,e.g., the time of an edit or page move.
• When mentioning the name of the page, cite the current name:This applies when a page is moved (i.e. retitled). In such a case, the Talk page is usually also moved. If you continue to use the old name, it will be confusing, especially for new editors to the article.

Archiving

For the guideline on user talk pages, seeWP:OWNTALK.

Large talk pages are difficult to read and load slowly over slow connections. As a rule of thumb, archive closed discussions when a talk page exceeds 75 KB in wikitext or has numerous resolved or stale discussions – seeHelp:Archiving a talk page.Apart from the exception described inWP:OWNTALK,discussions should be archived, not blanked.

If a thread has been archived prematurely, such as when it is still relevant to current work or was not concluded, unarchive it by copying it back to the talk page from the archive, and deleting it from the archive. Do not unarchive a thread that was effectively closed; instead, start a new discussion and link to the archived prior discussion.

Centralized talk pages

Not to be confused withWikipedia:Centralized discussion.

For the advice to keep discussions centralized, seeWikipedia:Content forking/Internal § Discussion forks.

Often, there are a number of related pages that would benefit from one single talk page for discussions. For example, a list article may have grown too large and was split Alpha betically. Or there may be a set of templates that are used together or interrelated MediaWiki interface pages.

Before implementing a centralized talk page, consider first gaining consensus for your proposal. The main discussion would usually be on the proposed centralized talk page with notices on the pages to be redirected. Notices may be placed on related pages as needed; for example, a relevant WikiProject page orWikipedia:Village pump (proposals).{{Centralize notice}}may be used to note the proposal.

If consensus is gained, then:

1. Archive current discussions on all the talk pages to be centralized; seeHelp:Archiving a talk page
2. Check each talk page for subpages. These are usually archived discussions, but other subpages are sometimes created, such as drafts or reviews. SeeWikipedia:Subpages#Finding subpages.
3. On the centralized talk page, list the redirected pages.{{Central}}is useful for this.
4. On the centralized talk page, list all of the archived talk pages.{{Archive banner}}is useful for this.
5. Redirect each talk page to the desired talk page; seeWikipedia:Redirect.It is recommended that an editnotice be created for the redirected talk pages; seeWikipedia:Editnotice.{{Editnotice central redirected}}is useful for this.
6. It is recommended that an editnotice be created for the centralized talk page.{{Editnotice central}}is useful for this.
7. Ensure that involved editors realize that they need to add the centralized talk page to their watchlist.

Examples of centralized talk pages:Talk:List of aircraft,Help talk:Cite errors,Help talk:Footnotes,andMediaWiki talk:Common.css.

User talk pages

See also:Wikipedia:User pages § Ownership and editing of user pages

User talk pages are subject to the general userpage guidelines on handling inappropriate content (seeUser pages § Handling inappropriate content).

While the purpose of article talk pages is to discuss the content of articles, the purpose of user talk pages is to draw the attention or discuss the edits of a user.Wikipedia is not a social networking site,and all discussion should ultimately be directed solely toward the improvement of the encyclopedia. User talk pages must serve their primary purpose, which is to make communication and collaboration among editors easier. Editors who refuse to use their talk page for these purposes are violating the spirit of the talk page guidelines, and are not acting collaboratively.

Personal talk page cleanup

See also:Wikipedia:User pages § Removal of comments, notices, and warnings

The length of user talk pages, and the need for archiving, is left up to each editor's own discretion.

Althougharchivingis preferred, users may freely remove comments fromtheir owntalk pages. Users may also remove some content in archiving. The removal of a warning is taken as evidence that the warning has been read by the user; this is true whether the removal was manual or automatic, and includes both registered and unregistered users. Some new users believe they can hide critical comments by deleting them. This is not true: Such comments can always be retrieved from the page history.

There are certain types of notices that users may not remove from their own talk pages, such as declined unblock requests and speedy deletion tags (seeUser pages § Removal of comments, notices, and warningsfor full details).

User talk pages arealmost never deleted,although acourtesy blankingmay be requested.

Talk page search

You can use theSpecial:Searchbox below to locate Talk pages. SeeHelp:Searchingfor more information.

See also

• Etiquette(how to be nice)
• Mutual withdrawal(essay regarding a method which two editors can agree to withdraw their recent comments)
• Responding to threats of harm(treat all claims seriously)
• Revision deletion(removing content from page history)
• Talk dos and don'ts(summary of policies of guidelines)
• Talk page layout(lead "bannerspace", table of contents, and discussions)
• Talk page templates(how to use the banners)
• User pages(what you can and can't have on your user pages)
• Using talk pages(how talk pages work)
• Wikipedia is not a blog
• Wikipedia is not a forum
• OrphanTalk(find orphaned talk pages)