30 ms·
TL;DR? Seems interesting and worth keeping in mind for other types of documentation.
by dpc_01234 2y ago
TL;DR? Seems interesting and worth keeping in mind for other types of documentation.
- readthenotes1 2y agoTldr: it's tl, didn't even load the 32mb pdf before my patience ran out (I'm in a slow connection and have a fair amount of disdain or something that's probably 20 x the size it needs to be)
- JeremyBarbosa 2y agoThere is really too much here to summarize. It's a 150 page guide to technical writing, as in the writing of technical manuals, using a variety of board game rulebooks the author wrote as examples. I am only 15 pages in, but so far I have to say the boardgame approach with all its images makes this a much more fun read then any other guide I have seen for writing manuals. It is just about writing though. I don't think you'd gain much if you are just a general boardgame fan looking for a behind-the-scenes look at rulebook creation (if that is even something people look for??)
- yifanl 2y agoFor accuracy, it's a 100 page guide to technical writing, followed by a 50 page sample rulebook for Stardew Valley implementing all the ideas :)
- crdrost 2y agoIronically these two comments seem to indicate a guide to technical writing, that did not view technical writing itself as a technology which they were writing about? Like, should start with a "quick start overview" about here's how the process looks, etc.?
- yifanl 2y agoBoard game rulebooks are documents that need to cater to multiple audiences including both new players learning from the rulebook and experienced players looking to skim through for very specific interactions they have forgotten. They also often refer to a system where there's a high degree of infomational dependence. Intelligent sequencing of rules and breaking apart chunks with good leading words and provided diagrams allows the second set of users to speed through their skimming while reducing cognitive load to new players.