Valve Developer Community:Wiki To Do

The Valve Developer Community site relies on its members to grow and take care of its contents. The Wiki concept depends on this.

What you'll find on this page are a list of different tasks, large and small, that can be worked on to improve and expand the site. Even small tasks, when added together, can make a big difference in the quality of the community.

Once you've completed a task, you can edit this page to remove it from the list, and add your own ideas for improvements.

Smaller items

These jobs should only take you a little time for each one.

• Document on an important console variable.
• Make sure a page only links to a term the first time it's mentioned unless important
• Proofread the content someone has created in a new page.
• Read a new page and give feedback on the discussion page on how the content can be improved.
• Add wiki tags to a new page someone has created:
  • Add links to other pages.
  • Possibly add a "Related Topics" section at the end.
  • Find pages with no category and put in the proper Category tags.
• Patrol edits to help alleviate possible vandalism and spam.
• Skim over a few random pages to catch any errors or vandalism that may otherwise pass unnoticed.

Medium-sized jobs

These projects will take a little longer.

• Add a list of maps where a specific Half-Life Continuity can be found on their own page
• Create a mini-tutorial, for a simple problem users have.
• Pick an entity in the list of CS:S entities, and transcribe the entity help from inside Hammer.
  • Don't forget to add Category:Counter-Strike: Source Entities to CS:S entity pages.
  • CS:S entity help can be extracted directly from the proper .FGD file or copied and pasted from Hammer.
  • Make sure to include the basic description, keyvalues, flags, as well as all inputs an outputs. Example: env_fire
• Find an existing entity in the list of entities and fix the formatting; here's an entity article template with sample formatting.
• Pick a page in the Hammer Editor documentation, and add links where they are missing. Look for the text "See the topic name section for more information", and make it a link to the proper page. Capitalized words in Bold are also often link candidates (i.e. Entity Report or Object Properties).
  • Some pages under Hammer Toolbars need links.
  • Add links to the Hammer Hotkey Reference page.
• Find one of the dead links in the Hammer Editor documentation that hasn't yet been ported from the old HTML site. You may find it helpful to use an HTML to Wiki converter, such as this.
• Official HL1/2 mods need some work. Only TFC has anything in it.
• The Half-Life High Definition Content is like Mao Zedong. There's about 93 different ways to write it. Add some redirects, like HD Pack.
• Add a couple screenshots or other images to a tutorial that has none, or not enough.
• Take an existing page that is too large and divide it into smaller, more manageable topics.
• Find and extend stub articles, or help clean up articles.

Large Tasks

Extended projects that may take you awhile to do.

• Create a new comprehensive tutorial, complete with screenshots. Include numbered, step-by-step instructions.
• Overhaul an existing tutorial or topic. Clean up the structure, syntax, and add images and other appropriate content.
• Find pages that have more or less identical content. Merge them together cleanly so they don't overlap, or clean up the content of each page so they complement one another instead of duplicating information.
• Start a new page from the wanted page listing.

Wiki Framework

Smaller items

Add [[steam://]] to parseable URLs. (http:// works, eg. http://www.valvesoftware.com, why can't this?)

Medium-sized jobs

Add edit non-existing page prompt to searches returning no pages, like Wikipedia's.

Special:Wantedpages shouldn't list Special:Contributions. Listing users is bad, too.

See also

Category:TODO — a list of pages that have been marked as needing something done