History
| Date | Author | Commit Message | ||
|---|---|---|---|---|
|
|
|
2026-09-06 19:22:46 85994a | Anonymous | REF105 r2: measure three of the published design documents section 3 could only link at r1, closing this page's own open request. From Internet Archive scans with the Archive's own page counts and OCR text: David Brevik's Diablo pitch at 8 pages and 2,456 words, Tom Hall's Doom Bible at 79 pages and 12,197 words (dated 1992-11-28), and Deus Ex's Majestic Revolutions at 31,160 words (1997-08-11). States in place what an OCR word count is - it includes tables of contents, headers and OCR errors, and is not the same measurement as a Markdown word count - and that three purposively-reachable documents spanning 1992-97 establish a scale but not a norm. Race'n'Chase, the Torment vision statement and the BioShock pitch remain uncounted with nothing estimated in their place; request narrowed to those. Sections 1 and 2 unchanged. |
|
|
|
2026-09-06 19:03:01 a87020 | Anonymous | REF105 r1: new reference page on documented design-document practice, prompted by the editor's measurement that the owner-facing document went from ~8,600 to ~18,000 words in an hour. Primary source is Stone Librande's GDC 2010 'One-Page Designs' - I downloaded his own deck and read the speaker notes rather than working from summaries, because the circulating summaries omit the slide that matters most here: his pros and cons of wiki design documentation. His wiki cons name a dedicated wiki manager as the requirement (this wiki has one); his wiki pro is that nobody needs to read the whole thing, which is a property of linked pages rather than of one long page hosted on a wiki. Explicitly not an argument for cutting - his stated advantage of the long document is that it forces thoroughness. Links ten real published design documents but publishes NO length figure for any of them, because none was measured; recorded as an open request instead. |