<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
	<id>https://fanverse.click/index.php?action=history&amp;feed=atom&amp;title=Fanverse_Wiki%3ASplitting_articles</id>
	<title>Fanverse Wiki:Splitting articles - Revision history</title>
	<link rel="self" type="application/atom+xml" href="https://fanverse.click/index.php?action=history&amp;feed=atom&amp;title=Fanverse_Wiki%3ASplitting_articles"/>
	<link rel="alternate" type="text/html" href="https://fanverse.click/index.php?title=Fanverse_Wiki:Splitting_articles&amp;action=history"/>
	<updated>2026-05-15T10:32:47Z</updated>
	<subtitle>Revision history for this page on the wiki</subtitle>
	<generator>MediaWiki 1.41.0</generator>
	<entry>
		<id>https://fanverse.click/index.php?title=Fanverse_Wiki:Splitting_articles&amp;diff=6748&amp;oldid=prev</id>
		<title>Mob: Created page with &quot;{{Short description|Fanverse Wiki guideline on article splitting}} {{Fanverse policy}} {{Notice|Page splitting on Fanverse Wiki is an uncommon and deliberate process. Editors should only propose splits when absolutely necessary to preserve clarity, tone, and readability.}}  == Overview == On &#039;&#039;&#039;Fanverse Wiki&#039;&#039;&#039;, splitting articles is a rare editorial measure, only used when the size, scope, or structure of a page severely hinders navigation, storytelling clarity, or usab...&quot;</title>
		<link rel="alternate" type="text/html" href="https://fanverse.click/index.php?title=Fanverse_Wiki:Splitting_articles&amp;diff=6748&amp;oldid=prev"/>
		<updated>2025-07-05T09:14:55Z</updated>

		<summary type="html">&lt;p&gt;Created page with &amp;quot;{{Short description|Fanverse Wiki guideline on article splitting}} {{Fanverse policy}} {{Notice|Page splitting on Fanverse Wiki is an uncommon and deliberate process. Editors should only propose splits when absolutely necessary to preserve clarity, tone, and readability.}}  == Overview == On &amp;#039;&amp;#039;&amp;#039;Fanverse Wiki&amp;#039;&amp;#039;&amp;#039;, splitting articles is a rare editorial measure, only used when the size, scope, or structure of a page severely hinders navigation, storytelling clarity, or usab...&amp;quot;&lt;/p&gt;
&lt;p&gt;&lt;b&gt;New page&lt;/b&gt;&lt;/p&gt;&lt;div&gt;{{Short description|Fanverse Wiki guideline on article splitting}}&lt;br /&gt;
{{Fanverse policy}}&lt;br /&gt;
{{Notice|Page splitting on Fanverse Wiki is an uncommon and deliberate process. Editors should only propose splits when absolutely necessary to preserve clarity, tone, and readability.}}&lt;br /&gt;
&lt;br /&gt;
== Overview ==&lt;br /&gt;
On &amp;#039;&amp;#039;&amp;#039;Fanverse Wiki&amp;#039;&amp;#039;&amp;#039;, splitting articles is a rare editorial measure, only used when the size, scope, or structure of a page severely hinders navigation, storytelling clarity, or usability. Unlike wikis with thousands of micro-articles, Fanverse values cohesion, context, and presentation above page count. The emphasis is on keeping articles comprehensive, cinematic, and well-structured — not fragmented.&lt;br /&gt;
&lt;br /&gt;
Split proposals should not be made casually or due to temporary growth. Instead, splits must reflect long-term editorial need, narrative integrity, and layout cohesion.&lt;br /&gt;
&lt;br /&gt;
== General philosophy ==&lt;br /&gt;
* Article splitting is the exception, not the rule.&lt;br /&gt;
* Splits should preserve in-universe immersion and out-of-universe professionalism.&lt;br /&gt;
* Every split must improve readability, organization, or narrative flow.&lt;br /&gt;
* Do not split articles to remove &amp;quot;unwanted&amp;quot; sections or to bury controversial material.&lt;br /&gt;
&lt;br /&gt;
== When to consider a split ==&lt;br /&gt;
{{Anchor|When to split}}&lt;br /&gt;
Fanverse Wiki recommends article splitting only under the following conditions:&lt;br /&gt;
&lt;br /&gt;
* The article has grown beyond &amp;#039;&amp;#039;&amp;#039;15,000–20,000 words of readable prose&amp;#039;&amp;#039;&amp;#039;, making it difficult to read or maintain.&lt;br /&gt;
* A specific section has expanded into a fully distinct subtopic that cannot be effectively summarized (e.g., a character biography overshadowing a team article).&lt;br /&gt;
* A film, character, or season article is serving double-duty for unrelated subjects (e.g., combining lore and production in a chaotic structure).&lt;br /&gt;
* The article contains extensive list material (e.g., episodes, cast credits, in-universe events) better handled in a dedicated subpage.&lt;br /&gt;
&lt;br /&gt;
== When &amp;#039;&amp;#039;not&amp;#039;&amp;#039; to split ==&lt;br /&gt;
Avoid splitting if:&lt;br /&gt;
&lt;br /&gt;
* The reason is purely aesthetic or preference-based.&lt;br /&gt;
* The resulting subarticle would lack sufficient standalone content.&lt;br /&gt;
* The content is trivial or easily summarized in a paragraph or two.&lt;br /&gt;
* The page in question is not under strain (length, layout, technical size, or confusion).&lt;br /&gt;
&lt;br /&gt;
=== Specific DON&amp;#039;Ts ===&lt;br /&gt;
* Don’t split because a section receives heavy editing traffic.&lt;br /&gt;
* Don’t split for temporary formatting issues that could be solved with better layout.&lt;br /&gt;
* Don’t split development and lore unless absolutely unmanageable.&lt;br /&gt;
&lt;br /&gt;
== Summary style usage ==&lt;br /&gt;
If a split is justified, the best approach is to use the &amp;#039;&amp;#039;&amp;#039;summary style&amp;#039;&amp;#039;&amp;#039; method. This involves:&lt;br /&gt;
&lt;br /&gt;
* Creating a clean, titled section in the main article with a short summary of the content.&lt;br /&gt;
* Moving the full version of that content to a new standalone article.&lt;br /&gt;
* Using {{tl|Main}} or a hatnote at the top of the summary to point to the full article.&lt;br /&gt;
* Ensuring both pages remain logically and narratively linked.&lt;br /&gt;
&lt;br /&gt;
=== Example ===&lt;br /&gt;
If an article like &amp;#039;&amp;#039;Spider-Verse: Miles&amp;#039;&amp;#039; includes a sprawling 3,000-word breakdown of Miles’s abilities, that section may be summarized into a few paragraphs, with the detailed breakdown moved to &amp;#039;&amp;#039;&amp;#039;[[Powers of Miles Morales]]&amp;#039;&amp;#039;&amp;#039;.&lt;br /&gt;
&lt;br /&gt;
== Attribution requirements ==&lt;br /&gt;
Whenever content is moved from one page to another, proper attribution is required per site policy. You must:&lt;br /&gt;
&lt;br /&gt;
* Leave an edit summary in the new article stating the origin (e.g., “Split from [[Spider-Verse: Miles]]”).&lt;br /&gt;
* Use the {{tl|Split attribution}} template if necessary.&lt;br /&gt;
* Maintain the page history in both locations if under dispute.&lt;br /&gt;
&lt;br /&gt;
== How to propose a split ==&lt;br /&gt;
Splits should always go through a transparent process:&lt;br /&gt;
&lt;br /&gt;
# Start a new section on the article’s talk page titled: &amp;lt;code&amp;gt;== Split proposal: [Subarticle name] ==&amp;lt;/code&amp;gt;&lt;br /&gt;
# Clearly explain your rationale, including article size, structural issues, and long-term value.&lt;br /&gt;
# Wait for feedback. If there is no response within 7 days and the split is uncontroversial, proceed with caution.&lt;br /&gt;
# If objections arise, build consensus through discussion.&lt;br /&gt;
# Use {{tl|Under discussion}} on the main article until the proposal is resolved.&lt;br /&gt;
&lt;br /&gt;
== Executing the split ==&lt;br /&gt;
Once consensus is reached:&lt;br /&gt;
&lt;br /&gt;
* Move the content to the new article using standard wiki markup.&lt;br /&gt;
* Add appropriate templates: {{tl|Main}}, {{tl|Split from}}, {{tl|Split attribution}}, or {{tl|Summary style}} where needed.&lt;br /&gt;
* Clean up references and navboxes.&lt;br /&gt;
* Update the original article’s structure so it no longer feels “empty” or disjointed.&lt;br /&gt;
&lt;br /&gt;
== Naming split pages ==&lt;br /&gt;
Follow these conventions for naming split pages:&lt;br /&gt;
&lt;br /&gt;
* Use precise, natural titles: e.g., &amp;#039;&amp;#039;&amp;#039;Miles Morales (biography)&amp;#039;&amp;#039;&amp;#039; or &amp;#039;&amp;#039;&amp;#039;Doctor Doom (development)&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
* Avoid awkward suffixes like “/Details” or “/Extended”&lt;br /&gt;
* Ensure consistency with other articles in the same group or category.&lt;br /&gt;
&lt;br /&gt;
== Alternative solutions to splitting ==&lt;br /&gt;
Before initiating a split, consider:&lt;br /&gt;
&lt;br /&gt;
* &amp;#039;&amp;#039;&amp;#039;Collapsing content&amp;#039;&amp;#039;&amp;#039; using {{tl|Collapsible section}} for long lists or minor subtopics.&lt;br /&gt;
* &amp;#039;&amp;#039;&amp;#039;Transclusion&amp;#039;&amp;#039;&amp;#039; if content is used in multiple places (especially navboxes or timelines).&lt;br /&gt;
* &amp;#039;&amp;#039;&amp;#039;Subpage usage&amp;#039;&amp;#039;&amp;#039; for navigation-heavy tables or appendices (e.g., timelines or credits).&lt;br /&gt;
&lt;br /&gt;
== Marking for potential split ==&lt;br /&gt;
If you&amp;#039;re unsure whether a split is needed:&lt;br /&gt;
&lt;br /&gt;
* Use {{tl|Split needed}} at the top of the article or section.&lt;br /&gt;
* Add a brief note on the talk page with reasoning.&lt;br /&gt;
* Do not perform a bold split without discussion unless it’s a clear formatting rescue.&lt;br /&gt;
&lt;br /&gt;
== Final note ==&lt;br /&gt;
Fanverse Wiki values structure, not sprawl. Articles are meant to be cinematic, readable, and immersive. Before splitting, always ask: &lt;br /&gt;
&lt;br /&gt;
&amp;gt; “Will this improve the experience of someone reading this article from start to finish?”&lt;br /&gt;
&lt;br /&gt;
If not, don’t split. Refactor, summarize, or reorganize instead.&lt;br /&gt;
&lt;br /&gt;
== See also ==&lt;br /&gt;
* [[Fanverse Wiki:Manual of Style]]&lt;br /&gt;
* [[Fanverse Wiki:Stub policy]]&lt;br /&gt;
* [[Fanverse Wiki:Summary style]]&lt;br /&gt;
* [[Fanverse Wiki:Article size]]&lt;br /&gt;
* [[Fanverse Wiki:Content policy]]&lt;br /&gt;
* [[Help:Splitting a page]]&lt;br /&gt;
&lt;br /&gt;
[[Category:Fanverse Wiki policies]]&lt;br /&gt;
[[Category:Fanverse Wiki style guidelines]]&lt;/div&gt;</summary>
		<author><name>Mob</name></author>
	</entry>
</feed>