Corporate Document To Be Released As Open Source - Need Comments

[gentoolen]

I have recently began work on an online corporate presence for a 29 year old company I work for.  I chose CMSMS for the website foundation and as a sideline project I've started work on a (very necessary) step-by-step two-section administration guide.

Section one is for the layman, those persons who will perform the frequent task of uploading photos and files, creating and editing pages of content and overall general upkeep.

Section two is for me (for now), the chief adminsitrator who handles overall domain management, email account creation and the technical aspects of site appearance and function, coupled with backups as necessary.

While the two projects are specifically targeted for the company I work for, I've openly discussed with my employer issues dealing with open source and the GPL.  This has not appeared to be any concern whatsoever as they really just want a professional site that is simple to maintain.  They actually appeared thrilled that a large group of "volunteers" are working on the CMSMS foundation and modules.  To them that is equivalent to cheap labor with the emphasis on cheap.

The gist of this and my primary point is, once I've fulfilled my obligations for the company I work for I'd like to edit the documentation to remove the corporate insignia and references, along with anything pertaining to our personal login and administration security, and release everything else as an open source CMSMS documentation project.

I see a problem though.  At present I'm using Microsoft Word 2003 to write the manual/guide.  I've investigated both OpenOffice and AbiWord with the OpenDocument format, but I am currently teetering on top of the "which side is the grass greener on" fence.

I've already written about 45 pages and could undergo a pretty simple converstion to an alternative format, but my basic instinct tells me it would be best to base the bulk of the project on a format from the get-go that is as open and universal as possible.

Oh yeah, my friends keep insisting that the document thus far is so detailed and "good" they would prefer I maintain a copyright on it and offer it up as a manuscript for a book down the road.  I'm not particularly inclined to veer in that direction though as the open source community has given me a great deal over the years.

What are your thoughts on this?

[Dr.CSS]

if you release it as .doc it can still be read with OO.o and abiword right?
well than you might want to use that format, not that i've any overwhelming love of MS, i use OO.o
but it is on more installs so far,,,
or you could save it as both and offer it with an open source common copy right lisence, not sure what it's called but it has diff. ones and diff. levels.
it could also be setup as a wiki or just a web page/s.
or .odf, .doc, wiki, web page/s, book all at the same time... nothing like getting the word out...

  mark

[gentoolen]

You're quite right Mark.  I'd overlooked the fact that most OSS document readers/writers of high caliber will read and write DOC files if the formatting isn't too complicated (as in, using proprietary Microsoft features).

Given my experience with HTML/Web Design, it wouldn't be a great hassle to reformat for the web either.  In fact, now that you mention that, it might be in the user's best interests if I format the manual (at least one version of it) specifically for web-based use as they will most likely need access to it while working on the CMSMS site at the time the manual is needed.

Something to consider...

- Len

[Ted]

A lot of book authors these days are writing in straight xml using the docbook schema.  When you use it, it's pretty much a no brainer to convert it for the web, pdf, print, etc.  I've never used it myself, but a few authors I do know swear by it.

[gentoolen]

Yeah, I learned a while back that the Gentoo Linux Handbook is all done in XML so that it can be easily printed for web and PDF.  I've found it cumbersome trying to figure out how to download the original source and work it out into a meaningful core from which I can build my own handbook of sorts.  It just ain't happening...

I think my block is coming from my lack of expeirence with the format and tools necessary, but from what I've seen, it can definitely present itself as a very good and professional means of cranking out a manual or handbook.

I wonder if there is a way to take a finished (i.e. polished) Word 2003 doc file and convert it to raw XML in such a manner it can be ported over to any format desired, while still retaining the original format and intent of style I wish to convey.  That last thing is why I only provide my resume in PDF format - as it insures without a doubt my resume in all it's formatting (genius) is relayed precisely as I intend it.

Is there a Windows-based XML editor that is simple to use?  I've seen a few but they seemed pretty frightening in my initial experience.