Migration of Software Documenation to Confluence Wiki

Over the years, the SSDT has primariliy used  DEC DOCUMENT and DocBook to create documenation.  DEC DOCUMENT (primarily used for OpenVMS "Green Screen" documenation) is an aging tool and no longer supported on OpenVMS.  DocBook was used primarily for the "web application" help systems.   Both tools have their benefits, but both suffer from a steep learning curve and tedious workflow  for SSDT technical writers.  Some of our documentation has not been maintained and updated as it should simply due to the cost (the tedious busy work associated with the current tools).

Further,  consolidating the documentation into a single location with consistent navigation, appearance and comprehensive search has been difficult.  Compared to many modern tools, the SSDT documentation looks dated and difficult to use.

As previously announced, the SSDT has begun using the Confluence Wiki software for managing collabrative documentation.   Confluence has unique features which make it suitble for writing documentation.  The Wiki will reduce the SSDT"s costs for documentation by making it much easier to update and maintain compared to the current tools.  In addition, the WIki provides automatic navigation and integrated search capabilities.

Therefore, the SSDT intends to migrate most or all our current documentation into the Confluence Wiki.  Over the coming weeks, the documentation will be converted into Wiki format and the existing links to the PDF and HTML documentation will be re-directed to the Wiki version.  LIkewise, the Postscript and LN03 versions will be removed from the software distributions. 

The first set of documentation to be converted is the "OpenVMS Technical" documentation, which includes the "OECN System Manager's Guide" and the "VMS Managers Handbook", at: http://wiki.ssdt-ohio.org/display/vmstech/

The conversion process from DEC DOCUMENT is not perfect and there will be some formatting problems in some areas.  If you notice anything, feel free to report it to us.

Please comment on this item, or post in a OECN Forum if you have any questions or comments.