User:JackVibe/Sandbox: Difference between revisions

From Halopedia, the Halo wiki

No edit summary
No edit summary
Line 1: Line 1:
==List of battle pages to be reworked==
Work-in-progress
 
=Reworking battle lore articles=
==The problem==
As a wiki, Halopedia strives to uphold high-quality writing. Our articles should be easily accessible and readable for all visitors; this can be accomplished by using language that is simple and concise, structuring the main text with appropriate subheadings, and enriching articles with images or formats that help present information clearly. The purpose of the wiki is to be informative and cover topics with relevant details—hence the notability policy, which helps determine what topics we should cover and at what level of detail.
 
Note the important balance between "informative" and "relevant details". At the moment, some of our pages on battles—especially ones based on battles depicted in the ''Halo'' games—are overly detailed; the articles present large amount of details that are not relevant to the overall battle, and the main points of the battle are lost. In some cases, the article is just a direct retellings of the source material, rather than summarised into the key points.
 
For example:
 
{{Quote|Thel 'Vadamee arrived on a cliff overlooking Installation 05's control room. He immediately located a plasma rifle lying on ground smeared with Sangheili blood. As he moved towards a downed Sangheili Minor, he heard and saw distant plasma fire as Jiralhanae troops killed off the last remaining Sangheili on the cliffs. In his final breath, the Minor warned Thel of the massacre of the Sangheili Councilors by the Jiralhanae. Taking the fallen warrior's energy sword, the Arbiter slew a trio of Jiralhanae that were pondering what to do with the Sangheili corpses. The captain in command of the Jiralhanae pack on the cliff ordered his men to find the Brutes that had failed to report in.}}
 
Thel 'Vadam's arrival at Installation 05 was important to the outcome of Battle of Installation 05 and held implications for the larger outcome of the Human-Covenant War; it led to an alliance between the UNSC and the Sangheili, followed by the death of Tartarus and the deactivation of the ring. As such, it was important to note his arrival and what led to the aforementioned outcomes. However, the details (like arriving at a cliff, the plasma rifle, the energy sword, and killing a trio of Jiralhanae) were unnecessary. Rather than describing every single encounter in the level, each with its own paragraph (this would be much more appropriate for the Summary sections for the level pages), the entirety of the ''[[Halo 2]]'' level [[Uprising]] can be summarised with a four-sentence paragraph:
 
{{Quote|The Jiralhanae began killing the Sangheili and the Unggoy under their command. The Councillors were brought to the ring expecting to oversee its activation, instead they were killed by the Jiralhanae. 'Vadamee arrived in the vicinity of Installation 05's control room in the midst of the Great Schism. 'Vadamee then rallied the scattered Sangheili and Unggoy in a consolidated effort to avenge their fallen brethren. As 'Vadamee approached the control room, he was reunited with Rtas 'Vadumee.}}
 
However, more importantly, 'Vadam's arrival is but a single event in the midst of a ''battle'' between dozens of Sangheili, Unggoy, Kig-Yar, Yanme'e and Mgalekgolo. Rather than a focus on the 'Vadamee's perspective, the main text should be a neutral retelling from both (if possible) sides of the battle, and in a chronological order (with reasonable amount of flexibility), hence the first two sentences on the Jiralhanae's betrayal coming first, even if they were revealed to the player (and 'Vadamee) after his arrival at the ring.
 
To summarise, we want to condense these articles (and merging any that can merged) to better present the information in a more analytical and neutral manner, instead of treating these pages as plot synopsis of their source materials.
 
==Guiding questions==
;What makes a battle notable as a page?
The pages for individual ground engagements will depend how much information/detail we may have. Parent pages like [[Harvest campaign]], [[Fall of Reach]], [[Battle of Installation 04]], [[Battle for Earth]], or [[Battle for Zeta Halo]] provide a general overview to the larger campaign on the planetary body, with detailed specific links to ground engagements where necessary. One question would be "Can we cover the details (in the standard set above) in a single section on the parent page?" In those cases, we may consider linking directly to sections on the parent page.
----
;How do we name a battle page?
We always name our articles after their names in official materials. If the battle does not have an official name, we maintain the use of names like:
*Battle of X
**Battle over X: for space battles
*Skirmish of X
**Skirmish over X: for space battles
*Raid on X
*Mission to X
*Outbreak on X: for battles instigated by Flood escaping containment
*Assassination of X: for battles instigated by targeted killing of a high value individual
 
Unless they are named as such in official materials, since all combat involves some kind of assault or defense, we do not accept names like:
*Assault on X
*Attack on X
*Defense of X
 
Other names we do not accept:
*Battle for X: This name implies the battle was fought for the possession of something, but we still tend to name these pages after the location anyway, in which case, "Battle of X" becomes more grammatically correct.
 
Names to be considered
*Ambush at X
*Escape from X
 
 
==Next steps==
Subject to input from rest of staff team
Subject to input from rest of staff team
;Delete
;Delete
Line 20: Line 68:
;Pages that need to be considered
;Pages that need to be considered
*[[Recovery of John-117]]
*[[Recovery of John-117]]
*[[Battle of
Battle of the Silent Auditorium
*[[Battle of the Silent Auditorium]]

Revision as of 11:45, September 29, 2023

Work-in-progress

Reworking battle lore articles

The problem

As a wiki, Halopedia strives to uphold high-quality writing. Our articles should be easily accessible and readable for all visitors; this can be accomplished by using language that is simple and concise, structuring the main text with appropriate subheadings, and enriching articles with images or formats that help present information clearly. The purpose of the wiki is to be informative and cover topics with relevant details—hence the notability policy, which helps determine what topics we should cover and at what level of detail.

Note the important balance between "informative" and "relevant details". At the moment, some of our pages on battles—especially ones based on battles depicted in the Halo games—are overly detailed; the articles present large amount of details that are not relevant to the overall battle, and the main points of the battle are lost. In some cases, the article is just a direct retellings of the source material, rather than summarised into the key points.

For example:

"Thel 'Vadamee arrived on a cliff overlooking Installation 05's control room. He immediately located a plasma rifle lying on ground smeared with Sangheili blood. As he moved towards a downed Sangheili Minor, he heard and saw distant plasma fire as Jiralhanae troops killed off the last remaining Sangheili on the cliffs. In his final breath, the Minor warned Thel of the massacre of the Sangheili Councilors by the Jiralhanae. Taking the fallen warrior's energy sword, the Arbiter slew a trio of Jiralhanae that were pondering what to do with the Sangheili corpses. The captain in command of the Jiralhanae pack on the cliff ordered his men to find the Brutes that had failed to report in."

Thel 'Vadam's arrival at Installation 05 was important to the outcome of Battle of Installation 05 and held implications for the larger outcome of the Human-Covenant War; it led to an alliance between the UNSC and the Sangheili, followed by the death of Tartarus and the deactivation of the ring. As such, it was important to note his arrival and what led to the aforementioned outcomes. However, the details (like arriving at a cliff, the plasma rifle, the energy sword, and killing a trio of Jiralhanae) were unnecessary. Rather than describing every single encounter in the level, each with its own paragraph (this would be much more appropriate for the Summary sections for the level pages), the entirety of the Halo 2 level Uprising can be summarised with a four-sentence paragraph:

"The Jiralhanae began killing the Sangheili and the Unggoy under their command. The Councillors were brought to the ring expecting to oversee its activation, instead they were killed by the Jiralhanae. 'Vadamee arrived in the vicinity of Installation 05's control room in the midst of the Great Schism. 'Vadamee then rallied the scattered Sangheili and Unggoy in a consolidated effort to avenge their fallen brethren. As 'Vadamee approached the control room, he was reunited with Rtas 'Vadumee."

However, more importantly, 'Vadam's arrival is but a single event in the midst of a battle between dozens of Sangheili, Unggoy, Kig-Yar, Yanme'e and Mgalekgolo. Rather than a focus on the 'Vadamee's perspective, the main text should be a neutral retelling from both (if possible) sides of the battle, and in a chronological order (with reasonable amount of flexibility), hence the first two sentences on the Jiralhanae's betrayal coming first, even if they were revealed to the player (and 'Vadamee) after his arrival at the ring.

To summarise, we want to condense these articles (and merging any that can merged) to better present the information in a more analytical and neutral manner, instead of treating these pages as plot synopsis of their source materials.

Guiding questions

What makes a battle notable as a page?

The pages for individual ground engagements will depend how much information/detail we may have. Parent pages like Harvest campaign, Fall of Reach, Battle of Installation 04, Battle for Earth, or Battle for Zeta Halo provide a general overview to the larger campaign on the planetary body, with detailed specific links to ground engagements where necessary. One question would be "Can we cover the details (in the standard set above) in a single section on the parent page?" In those cases, we may consider linking directly to sections on the parent page.


How do we name a battle page?

We always name our articles after their names in official materials. If the battle does not have an official name, we maintain the use of names like:

  • Battle of X
    • Battle over X: for space battles
  • Skirmish of X
    • Skirmish over X: for space battles
  • Raid on X
  • Mission to X
  • Outbreak on X: for battles instigated by Flood escaping containment
  • Assassination of X: for battles instigated by targeted killing of a high value individual

Unless they are named as such in official materials, since all combat involves some kind of assault or defense, we do not accept names like:

  • Assault on X
  • Attack on X
  • Defense of X

Other names we do not accept:

  • Battle for X: This name implies the battle was fought for the possession of something, but we still tend to name these pages after the location anyway, in which case, "Battle of X" becomes more grammatically correct.

Names to be considered

  • Ambush at X
  • Escape from X


Next steps

Subject to input from rest of staff team

Delete

These pages are too long and detailed when the same content (with the same level of details) can be covered by other pages

Condense/rewrite

These pages are notable but they are too long and detailed at the moment. They may require rewrites because the pages are written like a retelling of a level's sequence of events or written from a character's subjective perspective when it should be more neutral

Merge
Pages that need to be considered

Battle of the Silent Auditorium