Difference between revisions of "Editor's information"

From Valve Cut Content
Jump to: navigation, search
oldwiki>Livelong2
(formatting conventions: part 1)
oldwiki>Livelong2
(Leak)
Line 42: Line 42:
 
scope.png|"scope.vtf"
 
scope.png|"scope.vtf"
 
</gallery>
 
</gallery>
 +
*The Leak is in reference to the [[The 2003 Leak]], and should be capitalized.
 
==Page Composition==
 
==Page Composition==
 
VCC Wiki doesn't play exactly by the rules of any format. Rather, it uses a mishmash of good-sounding ideas primarily from the Combine Overwiki and TCRF.
 
VCC Wiki doesn't play exactly by the rules of any format. Rather, it uses a mishmash of good-sounding ideas primarily from the Combine Overwiki and TCRF.

Revision as of 19:00, 15 October 2017

Considering the wiki's only a few days old, there isn't much to discuss, however there are still a few things to keep in mind.

Infobox Reference

  • The current custom "Infobox" panels are:
Purpose (For documenting) Template name
Cut enemies Template:Cut Enemies
Cut Maps Template:MapInfoBox
Cut weapons (advanced) Template:Weapon_infobox
Mods Template:Mod_InfoBox
Shitposts/memes Template:Game_Infobox
Vehicles

Template:Vehicle_Template

There is currently one custom "notice" panel: Template:Obsolete

Please consider if the current ones are a good fit for your article before creating another.

Formatting Conventions

  • When referring to a specific directory, put it within <code></code tags. Example: /materials/brick/
  • When creating a texture gallery, have the caption of each refer to the original VTF's name in quotations. For example:
  • The Leak is in reference to the The 2003 Leak, and should be capitalized.

Page Composition

VCC Wiki doesn't play exactly by the rules of any format. Rather, it uses a mishmash of good-sounding ideas primarily from the Combine Overwiki and TCRF.

As a result, there is no strict format on constructing articles here. Even if you use one of the formats below, there is still plenty of wiggle room about how you work with them. The best method should be used, not necessarily the most standardized one.

"Evolution of"

Evolution articles document the "evolution" of various valve-related things that make it to retail, using headings for individual versions. Screenshots and textures are included within each header, as they should be each their own time capsule, moving onward.

Header Structure

There is no strict format, as "evolution of" articles should be approached on a case-by-case basis, based in what we have of it.Combine Soldier (Evolution) provides a good example of how these can be structured, though.

Header Structure

==Concepts==
===Early Suit Designs===
===Early Color Schemes===
==Version 1: Pre-2002==
===Screenshots===
==Version 2: E3_Hydra==
===Screenshots===
==Version 3: 2002==
===Screenshots===
===Textures===
==Version 4: Leak==
===Screenshots===
===Textures===
==Version 5: Early 2004==
===Screenshots===
===Textures===
==References==

Cut Enemies

These are intended to document cut enemies, and what condition (or lack of) they are in, alongside their oddities.

Header Structure

==Overview==
==Condition==
Miscellaneous aspects (see below)
==Gallery==
===Screenshots=== (if applicable)
===Textures=== (if applicable)

Weapons

These are intended to document cut weapons, and how they (would have) functioned.

Header Structure

==Overview==
==Tactics==
==Gallery==
Miscellaneous aspects (see below)

===Screenshots=== (if applicable)
===Textures=== (if applicable)

"Miscellaneous Aspects"

What does Miscellaneous Aspects represent? Essentially, this is a trivia section, where instead of bullet points, individual notable bits get their own heading.
For example, on the MP5K (SMG1) page, it would refer to the

  • Viewmodel Picture Release
  • Prior Revisions

On the Heavy_Machine_Gun_(HMG1) page, it would refer to

  • Early Viewmodel

It's based on TCRF's approach to headings, of which a good example can be seen here.

Wikia Tricks

Two tips for removing the unnecesary stuff wikia likes adding:

  • For galleries: Include "hideaddbutton=true" to remove the add buttons
  • For headers: Include "__NOEDITSECTION__" anywhere in the article to remove the header "edit" buttons