User:Xurizuri/Resources

WP:MERGE
Other information drawn from WP:MERGETEXT (which is based on WP:MERGE but has some flair) on WP:WPMERGE.

Reasons for merger
WP:MERGEREASON (good reasons to merge; from info page) WP:NOTMERGE (reasons to avoid merging; from info page)
 * 1) Duplicate (exactly the same scope)
 * 2) Overlap (basically the same scope)
 * 3) Short text (an absurdly short article that is highly unlikely to be expanded and would fit within another)
 * 4) Context (if one requires the other for it to make sense)
 * 1) Result would be too long and/or clunky
 * 2) The articles could be expanded into longer, separate, cross-linked articles
 * 3) The subjects are discrete and notable.

I'll add other reasons that may be relevant in conjunction with the above as I encounter them. To do: deletion, summary, WP:NOT

WP:PAGEDECIDE (whether to create a standalone pages; from notability guideline)
 * 1) Sometimes, the more complete context of a larger page allows a notable topic to be covered better.
 * 2) Remember to consider if it is WP:UNDUE within a larger page, especially for fringe theories.
 * 3) Several related notable topics can be collected into a single page if the result wouldn't be too unwieldy. This allows the relationships between them to be better appreciated (especially where the related topics provide needed context).
 * 4) Some notable topics aren't likely to ever be more than just a stub. It's often better to include it in a larger article than to create/keep a permanent stub.

WP:NOT (policy) still need to flesh out Note: these aren't all of the NOTs. They're the ones which have relevance to merging and aren't essentially sub-points of OR or notability policies.
 * 1) WP:NOT - not a dictionary
 * 2) WP:NOTSCANDAL - don't scandal monger.
 * 3) WP:SOAPBOX - don't merge articles away just because I don't like it, and vice versa.
 * 4) WP:PROMO and WP:NOTCV
 * 5) WP:NOTCATALOG
 * 6) WP:NOTDIRECTORY
 * 7) WP:NOTGENEALOGY
 * 8) WP:NOTHOWTO
 * 9) WP:CRYSTALBALL - if science hasn't decided yet, then neither have we
 * 10) WP:NOTCENSORED - don't merge an article just to get rid of objectionable content

Propose
1. Create a discussion on the appropriate page.
 * Notify on the other talk page/s.
 * Consider informing other parties. For example, a particularly involved WikiProject, the main article if the merge involves a sub-article, the creators of the page or other particularly involved editors.

2. Tag the page that's proposed to remain

3. Tag the page that's proposed for redirecting

4. Discuss

Perform
5. Close the discussion (not always necessary)
 * At the top of the section, put
 * At the bottom of the section, put Discussion bottom
 * If very contentious, and I was either involved or I'm unsure, go to requests for closure (RFCL).

5.1. If you don't want to do any of the below for an article with agreement to merge, add the article(s) to Proposed article mergers/Holding cell.

6. On article that will remain:
 * Remove merge tag
 * Copy over the content
 * Check categories, see also, further reading, navboxes, cleanup templates that aren't inline.
 * Edit summary needs to be: Merged content from PAGE THAT WILL REDIRECT .

7. On article that will redirect:
 * Replace everything with: #REDIRECT ARTICLE THAT WILL REMAIN R from merge
 * Add R to section if all content is in a particular section.
 * Edit summary should be: Redirected and merged content to ARTICLE THAT WILL REMAIN .

8. On talk page of the redirect:
 * Update the notification of proposal
 * Remove class from wikiprojects
 * Add copied at the top.

9. On talk page of the remaining article:
 * If not already done, close the discussion as described in
 * Add any wikiproject banners from the talk page of the redirect
 * Add any copied or similar attribution templates from the talk page of the redirect. If there are multiple of copied, then merge them into one template (it can handle any number of items). If there are multiple different types of banner, put them all into
 * Most important one is the copied for this merge
 * OPTIONAL: Comment with Merge done -- ~ at the bottom of the discussion (after the Discussion bottom).

10. OPTIONAL: copy-edit the material merged across or add cleanup merge

WP:SPLIT
Currently some rough notes, pulled entirely from WP:SPLIT
 * should also probably grab some info from WP:SUMMARY

Reasons to split
To do

Propose
To do (but very similar to merge)

Perform
WP:PROPERSPLIT Rough draft, needs some reworking

1. Close the discussion (TO DO: EXPAND THIS)

2. Prepare to split
 * If the material to split is dispersed throughout the source article, then group the content to be split together
 * Use an edit summary like "preparing to split article".

Note: a fair amount of the details of the next few items can be replaced by adding cleanup split to the articles.

3. Create the new article:
 * Copy the material to be split into the new article
 * Remember to copy over:
 * Bibliography items
 * Navboxes
 * Categories
 * Other end matter
 * Original citation for defined citations
 * Add a references section
 * Use an edit summary such as "Contents WP:SPLIT from SOURCE ARTICLE; please see its history for attribution."

4. On the source article:
 * Remove the material from the source article.
 * Consider whether to remove any:
 * Bibliography items
 * Navboxes
 * Categories
 * Other end matter
 * Check if any defined citations need to be added back in
 * TO DO: NEED TO WRITE EDIT SUMMARY

5. Tidy up the new article:
 * Create sections
 * Create lead, including:
 * Bolding name of new article
 * Adding background information about the source article
 * Adding wikilink to source article

6. Summarise new article in the source article:
 * Add main tag to the new article
 * Add one or two paragraphs summarising the new article OR add excerpt. If using excerpt:
 * It may involve adding some html to the lead of the new article. Make sure to add an invisible comment explaining the html. TO DO: DRAFT NOTE
 * Add invisible comment in the source article to tell people about WP:SUMMARY. TO DO: DRAFT NOTE
 * Add invisible comment in the lead of the new article to tell people about WP:SUMMARY. TO DO: DRAFT NOTE
 * TO DO: I'm pretty sure there are templates that can be added to talk pages.

7. On the talk page of the new article:
 * TO DO: EXPAND
 * Wikiprojects
 * copied

8. On the talk page of the source article:
 * TO DO: EXPAND
 * Wikiprojects
 * copied or split article

9. Other tidying up
 * links from other articles (TO DO: EXPAND THIS ITEM)
 * Add shortdesc
 * Add new article to wikidata item.

WP:TDOC
At this point, taken exclusively from WP:TDOC
 * Need to add content from WP:TDATA/T for TemplateData

What to include
I'll include useful templates as subpoints


 * Basic purpose
 * Limitations (e.g. navbox visibility)
 * Navbox visibility - explains that navboxes aren't visible on mobile
 * Parameters
 * Citation Style documentation (aka csdoc)
 * To generate a list of parameters for people to copy-paste, use
 * Usage examples
 * To generate examples of the template, use Markup2
 * To generate an example of the template populated with it's own property names, use
 * Apparently xpd helps somehow? Something to do with not calling the template twice?
 * TemplateData
 * Related templates
 * Categories (WP:CAT, WP:TDOC). The container category is Category:Wikipedia templates.

How to create
Need to summarise the process for manual creation, and for creation within a template itself/movement out of the template.

Add the documentation into the template (or use doc-code), and save it. [--last line of your template code--]

Then it can be manually or automatically created. To automatically create the documentation, hit the  link at the end of the empty documentation box; it'll trigger a templated creation which already has a bunch of the stuff in.

Sometimes it's included within the template itself via a content parameter.

Policies etc I always lose
Explanatory supplement
 * WP:Silence and consensus - if no one says has indicated disagreement and its been quite a while, consensus can be tentatively assumed. This doesn't mean that someone that disagreed but hasn't spoken in ages is "silent". Silence means that no one has voiced any disagreement at all. Shortcuts: WP:SILENCE, WP:SILENT. This supplement relates to the policy WP:Consensus.

Essays
 * WP:CSECTION - Avoid sections and articles focusing on criticisms or controversies, because they often get a bit POV and increase maintenance burden. From the essay WP:Criticism.
 * This is related to WP:Article size (guideline)

Useful templates
source assess table - for assessing sources in AfDs Specialpageslist - list of special pages Classification bar - for categories, its used to show its parents/ancestors