We maintain a technical project whose specifications are in a document of few hundred pages. It's a text document (Word), not a Wiki or a Web-based stuff.
The document contains lots of tables with values (strings, numerical, parameter names) . Some tables are huge (hundreds of data), other are quite small.
I'm looking for good practices/best approaches to get readable and comfy documents, especially data tables, avoiding hard to distinguish rows from content around, and also not some overly colored stuff making it hard to focus on. (As a side note, the specification contains also pseudo-code and code samples, formatted and highlighted with styles in a way like does SE markdown engine.)
I got this article : Web Typography: Designing Tables to be Read, Not Looked At. It's aimed at Web design, It might be good for such documents.
Are there guidelines to write a easy-to-read technical specification? I understand it might be a subjective question... Some people likes colorful documents, others sober ones.