Editor's information

From Valve Cut Content
Revision as of 19:39, 22 January 2018 by oldwiki>Livelong2 (cleanup, separate refpaes)
Jump to: navigation, search

What is the VCC Wiki?

VCC Wiki is a wiki dedicated to the documentation of Valve's Cut Content. It was created in response to a perceived absence of this documentation in the more "generalist" Valve wikis.

As a result of this, our primary focus is on Valve's cut content, and the community surrounding it.

Why Not Edit?

Notice a factual error somewhere? See a formatting issue that nobody seems to have noticed? Try your hand at editing it!

Even if you don't do the job correctly, all that will happen is that someone will come over and fix it, perhaps telling you how to do it correctly the next time.

Don't be afraid to edit. Nobody blames an editor with good intentions.

Page Philosophy

Let's face it - we're not going to have a universal set of standards for everything, considering our weird and varied subject matter.

When doing something new, don't approach it with a bunch of pre-thought-out header structures in mind. Think to yourself, what would work best? Often, that's the way that gets the best results.

Subpages

Should Reads

It's helpful to look over these pages before editing:

  • Neutral Point of View
    • A quick overview of Neutral Point of View, and how to use it.
  • Formatting Conventions
    • A (relatively short) list of formatting conventions. Getting familiar now will save you time later.
  • Useful Stuff
    • An index of files and programs that are extremely useful to have when editing on this wiki.
  • Template Guide
    • A guide on how to use templates, and a list of the templates VCC Wiki makes usage of.

Can Reads

They aren't necessary, but are definitely worth looking at.

Page Structures

A list of semi-standardized page structures. They might fit with what you are trying to write. The bullet point levels are representative of the header levels.

"Evolution" Structure

Overview:

  • Second-level headers are used to divide into "sections" of the particular thing's evolution.
    • Third-level headers are used after, to show what we have of that particular revision.
  • Including final versions is optional, but usually beneficial.

Works best with:

Articles with a long and notable history. Otherwise, an early version might fit better as a "notable aspect" header.

Examples:

"Timeline" Structure

Headers:

  • Major events (or years) serve as level 1 headers, dividing events.
    • Individual days where events occur serve as level 2 headers.
    • Individual events are laid out below the days with bullet points.
  • At the very end, a header for references is included.

Works best with:

Large, multi-month events, with smaller bits scattered over multiple days.

Examples:

"Weapon" Structure

Headers:

  • First, a brief description of what the weapon is, with the weapon name in bold. I.E.:

The XM29 OICW is the effective predecessor to the OSPIR. It is still in use in the leak, and thus fully present.

  • Two level two headers:
    • Overview
    • Tactics
    • Further case-by-case headers, documenting notable aspects of the weapon. I.E.:
      • Older Texture
      • Cut Grenade Launching Function
      • Facepunch Leaks
  • Another level-two header gallery, with dividing subheaders something like this:
    • Screenshots
    • Renders
    • Textures
  • A header for references. (If used!)

Works best with:

  • Articles documenting weapons. The general idea of it can be applied elsewhere, though.

Examples: