Main Page

From HeatherWiki

Jump to: navigation, search

Wiki is currently holding documentation for the game Revenge of the Duzzles for 2D Game Programming at RIT. All information related to Revenge of the Duzzles on this wiki is exclusively owned by Heather Arbiter, Kelley Piering, Michael Ey, Sela Davis. None of it may be used in any way for anything. Nor can be it copied, modified, adapted, stolen, borrowed, sold or distributed. Most content related to Revenge of the Duzzles can be found in Category:DR.

Wiki is currently holding documentation for the game Invasion Cute for Game World Design at RIT. All information related to Invasion Cute on this wiki is exclusively owned by Heather Arbiter, Kelley Piering, Sela Davis, Joe Pietruch, and D. Michael Moore, Kapish Rawat, Jay Austin, Chip Hilseberg, Andrew Kane, David Huynh, and Rushab Shah. None of it may be used in any way for anything. Nor can be it copied, modified, adapted, stolen, borrowed, sold or distributed. Most content related to Invasion Cute can be found in Category:IC.

[–] 0. Giant category
2. Main Page
[+] 1. HeatherWiki
[+] 3. Test

Welcome to HeatherWiki.

Contents

What is HeatherWiki

HeatherWiki is a collection of modifications to the MediaWiki framework to improve it for game design projects. The main goal is to create a system to make it easier to create and maintain game design documents through an easily modifiable wiki interface.

To this end, I am working to make the entire structure of the design document editable and buildable from a single page. Changes to this page, the document index, will propagate to all pages referenced there.

Why use wikis for game projects?

  • Wikis are easy to edit
  • Wikis can be accessed from anywhere
  • Wikis automatically track all updates
  • Wikis are great with organizing because of the categories and name spaces
  • Wiki templates and inclusions are great for the formulaic nature of design docs and their propensity for repeating information throughout them for different purposes
  • Wikis can simultaneously keep data organized in multiple ways by using inclusions to contain the same data for different people without worrying about data being changed one place but not another
  • Wikis are to design and documentation development what svn and cvs are to software development: a solution to concurrent editing and version tracking.

Why MediaWiki in particular?

  • MediaWiki is the software package used by Wikipedia
  • It is open-source
  • It supports most of the desired features
  • It’s relatively easy to add extensions to
  • It’s familiar
  • Game communities usually use MediaWiki for game-related wikis. In the long run, that means content created for internal documentation on the project wiki can more easily be used to seed a public wiki for the game community.

Why does this project need to mod it then?

  • Incredibly difficult to move entire sections and keep things organized for use outside of the wiki.
  • No method of tracking major changes for a design history
  • Could benefit from a simpler way for designers to flag articles with various tags for people’s attention as well as a way to make sure such flags were instantly noticeable by the people who need to see them
  • The conversion between a printable format for external presentation versus the convenience of the online format of the internal presentation can be cumbersome, time-consuming, and cancel out many of the benefits gained by using a wiki in the first place
  • Its still big and scary to those unfamiliar with it (but that could be said of any piece of software too!)
Retrieved from "http://www.heatherarbiter.com/mediawiki/index.php?title=Main_Page"
Personal tools