Re: Getting Started Guide (was Proposed Process for Documentation)

["Keith N. McKenna" <ke...@comcast.net>]

On 1/30/2021 8:22 PM, marcia wilbur wrote:
> Thanks for the resource!
> I am wondering, I know we use styles etc... within writer, but do we have a style guide or a style cheatsheet?
> 
> Also, was there a determination on options for collaboration?
> For example, I have marked up portions of the taming document - what is the process for sharing?
> The wiki? Gitbox area?  e-mail? 
> 
> Thanks,
> 

The closets thing we have for a Style Guide are the following two links.
They are mainly aimed at the mwiki, much of the information in them is
applicable our use as well.
https://wiki.openoffice.org/wiki/Documentation/Dashboard/Help_Style_Guide#Formats

https://wiki.openoffice.org/wiki/Documentation/Dashboard/Wiki_Editing_Policy

As I remember correctly ODFAuthors used the Chicago Manual of Style, or
we could choose our own. Do you know what LO uses for there style guide?

Regards
Keith



> ----- Original Message -----
> From: "Keith N. McKenna" <ke...@comcast.net>
> To: doc@openoffice.apache.org
> Sent: Saturday, January 30, 2021 4:34:39 PM
> Subject: Re: Getting Started Guide (was Proposed Process for Documentation)
> 
> On 1/28/2021 1:37 PM, F Campos Costero wrote:
>> Another benefit of Marcia writing a Linux guide is that it could be used,
>> with her approval, as a template for other guides. Maybe I am being too
>> optimistic but I expect  most of the topics would be the same among the
>> three guides and the general organization should be the same.
>>
>> Francis
>>
> I have a document template .ott file that is based on the Version 3.3
> OOo documentation. It has all of the styles used there as well as the
> ones in Jeanne's Taming Guide as well as  couple from he later that
> where new and I felt where better than those supplied in the
> original.The use of AOO and its designed in use of templates are, in my
> opinion, important for 2 reasons. First it gives the documentation a
> consistent and professional look and feel. Second it showcases the
> strengths of the product and is in itself a strong marketing tool.
> 
> There may be a few additions or deletions that could be made, but it is
> usable as it stands. It can be copied from:
> https://github.com/knmc/AOO-DocumentationProject/blob/Templates/AOO%20Documentation%20Template.ott.
> Any Questions on its use or suggestions for how to make it better are
> always welcome and can be addressed to this list.
> 
> Regards
> Keith
> 
> <snip>
>