Infrastructure Software

Greetings everyone,
I am creating Disaster Recovery documentation/process and I am kicking around various ideas. I would like to have the documentation available on the server at all times. We are a small shop, so it has to be in form that a contractor can use (I would like to take a vacation). Any feedback or experience would be appreciated.

Method 1 - Lowest common denominator
Create a vi text document that can be opened in a putty session.
Good points: Available when the server is up.
Command line instructions in document can be cut and pasted without extra characters or formatting commands added
Problems: Single screen makes is difficult to add if/then logic.
Adding too much detail/information make the document large, difficult to navigate and difficult to find specific information

Method 2 - 1 step up from Lowest common denominator
Create a vim template
Good points: Available when the server is up.
Syntax and other highlighting options make the document much more readable
Document structures can be added to hide or display data, add checklists, timestamps and other bells and whistles.
Problems: Requires familiarity with vim and its advanced options

Method 3 - html based
Good points: Document structures can be added to hide or display data
Problems: Requires X-Windows and Browser (increased connection bandwith)

Method 4 - html wiki based (tiddlywiki)
Good points: A very impressive single html file based wiki (works via java script)
Problems: Requires X-Windows and a java script enabled browser (increased connection bandwith)
Off the beaten path

Method 5 - MS based documents (Word or Excel)
Good points: Standard documentation tools
Problems: Requires X-Windows and OpenOffice on the server