Your story sounds very familiar to me, but at my office there is a significant difference: I am not alone, a small team is maintaining the network.
So our first choice for documentation was a wiki (MediaWiki in this case). In addition to the known benefits
Ease of use, even for non-techies
Change history
Simple backup (tar of directory and SQL dump)
PDF export through plugins
there are some ways to display the content clearly arranged. For example take the wiki page of a network switch. A little picture lets you identify the model easily and a tabular contains one entry for each port and a link to the component which is connected.
We also put server racks into tables and linked the machines at the specified positions.
Of course we tried some other software packages for this task, but none was as flexible as the wiki solution.
Slashdot Mirror
Your story sounds very familiar to me, but at my office there is a significant difference: I am not alone, a small team is maintaining the network.
So our first choice for documentation was a wiki (MediaWiki in this case). In addition to the known benefits
there are some ways to display the content clearly arranged. For example take the wiki page of a network switch. A little picture lets you identify the model easily and a tabular contains one entry for each port and a link to the component which is connected.
We also put server racks into tables and linked the machines at the specified positions.
Of course we tried some other software packages for this task, but none was as flexible as the wiki solution.