A large client is very invested in system documentation and solution architecture docs (& other artifacts). Those in my opinion are the representation of non-DRY, cumbersome and obsolete approach to technical communication.<p>I'm wondering what others have used or at least thought of (Tools, Processes, etc...)
My favourite approach to them tends to be scotch.<p>More seriously consider something like <a href="http://sphinx-doc.org/" rel="nofollow">http://sphinx-doc.org/</a>
Code is not static,your documentation should not be either.