Hi Frank, Thanks for your interest in the latest style guide revision. To answer your questions:
- I can provide PDF of the style guide for download, if folks prefer that. I published the first version in PDF and received no comments, so I thought I'd try the HTML and see if that format got more interest. Let's see if anyone seconds your request. - I intend to include information about writing for Solbook in the style guide, however, there is no plan to open source the Solbook DTD (in short, because Epic is not freely available). I would include the info for those who will eventually want to use Solbook templates for doc development. But, now that you bring it up, this might be flawed thinking. How will Solbook templates be useful without the DTD?? Not sure. Maybe it is more accurate to say that we'll include information about authoring for a DTD in the style guide beta version and leave it at that until we get more feedback. -I've proposed a plan that will open source the Solaris developer and administration documentation XML source files, so that they can be edited with any free editor and validated with DocBook DTD. See the proposal thread here: http://www.opensolaris.org/jive/thread.jspa?messageID=18528#18528 - I am currently starting work on a style guide 'top ten' based on an existing document from the editorial group, so thanks for your thoughts on this, I totally agree that we need a condensed version of the most important information for folks to reference. But, I don't have any evidence that a complete, if lengthy, style guide will alienate anyone. As a writer, more reference information is better when I need answers to a question during development of a piece. - I also agree that concise checklists and procedures will be required to communicate exactly how to get fixes delivered and published, and those will logically follow once we have full-blown source control for the opensolaris.org portal. Right now, in absense of source control, I'm focused on helping to train and create docs and FAQs for those writers who have agreed to act as sponsors. Then I'll derive from those drafts, procedures for all doc contributors that include the source control information. Thanks again, Michelle OpenSolaris Doc Community This message posted from opensolaris.org
