Thread:VT2Dancougar/@comment-27075564-20180228003215/@comment-30128802-20180301033953

A separate page like that isn't a bad idea, as well.

In general, I think it would be most ideal if the Wiki is organized in a way that clearly distinguishes between the following types of contents:

Each of the above has a different functional purpose and a vastly different manner of presentation. They are also important to different types readers, so it'd be best if they do not compromise the effectiveness of one another, and it'd be best if the wiki is organized so that the reader can easily find what they're looking for. WIth this considered, it is sometimes better to separate one or more of the above categories from the rest, although separate headings might alone be sufficient. The Witcher wiki is interesting is that it places (2) directly inside articles, whereas this wiki keeps (2) separate from (1).
 * 1. User-compiled lore articles (example: Biography of Adam Jensen)
 * 2. In-game lore text (ebooks, emails, and pocket secretaries)
 * 3. In-game gameplay information (description of augmentations/items)
 * 4. User-complied gameplay references (list of passwords, loot lists, gameplay maps)
 * 5. Strategy guides
 * 6. Real world information (information on games, trivia)

I think the problem with the aug articles was that they mixed (2), (3), and (5) together in the same article in a disorganized manner. The reformatted Titan article (with a separte heading for (5)) is much better. Does having too much of (3) detract from (5) or vice versa? Something to consider, of course.

P.S.: (4) and (5) are not the same thing. To me, (4) is the most functionally important part of the wiki, given that keycodes and passwords are consistently among the most read articles on the wiki (during the PS pro free month, the page hits for DXMD keycodes went to 25k views per week; nothing even came close to that). I support having more of (5), as long as it does not exhibit any bias toward a particular gameplay style, and does not reduce the organizational efficiency of the wiki.