Ask HN: What's your approach to System & Design Documentations?

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.

I'm wondering what others have used or at least thought of (Tools, Processes, etc...)