Open Stack

On Tue, Oct 21, 2014 at 3:22 PM, Adam Lawson <alawson at aqorn.com> wrote:

> I wasn't wanting to rule out Word, only to reference it as one possibility.
>
> I was thinking of a template where I can create how-to's that reference
> code, Tips, etc. M$ doesn't have templates that do that that I've found...
>
> basically like those Dummies books.
>
>
What I'm saying is that I'd prefer you look at the outlines for Guides
already on docs.openstack.org and write to that. And then if there's
something that doesn't fit what you need you bring it up here or through
doc bug reporting.

Does that make sense?

The Dummies books, Head First books, are all the result of publishing pros
being really good at their craft. So good it's repeatable.

I think we have a pretty good starting set of Guides, but I really want
your field notes to enhance them. Do you think you can work with us as a
roving field reporter? Let me know your thoughts.

Thanks,
Anne


>
> *Adam Lawson*
>
> AQORN, Inc.
> 427 North Tatnall Street
> Ste. 58461
> Wilmington, Delaware 19801-2230
> Toll-free: (844) 4-AQORN-NOW ext. 101
> International: +1 302-387-4660
> Direct: +1 916-246-2072
>
>
> On Tue, Oct 21, 2014 at 11:36 AM, Anne Gentle <anne at openstack.org> wrote:
>
>>
>>
>> On Tue, Oct 21, 2014 at 1:33 PM, Adam Lawson <alawson at aqorn.com> wrote:
>>
>>> Curious, has anyone had any success with a Word template or something
>>> similar that really works for them? Like highlighting text and applying a
>>> style that formats it to be a tip, as code snippet, as  a warning/gotcha,
>>> etc etc?
>>>
>>>
>> If you really want Word, and I don't think you do, go to
>> http://office.microsoft.com/en-us/templates/ and pick out a template
>> with styles already defined.
>>
>> Remember we're open source so our toolset all the way down to the fonts
>> is open source.
>>
>> For your use case, creating docs for users trying to deploy OpenStack,
>> ideally you'll download the upstream docs from docs.openstack.org, use
>> the heck outta them, and log doc bugs where you're having trouble getting
>> readers to heed your warnings. :)
>>
>> Anne
>>
>>
>>> I'm trying to create documentation for users who are trying to deploy
>>> Openstack and I'd like to re-use the format over and over again where the
>>> content changes significantly but things like code, warning, Note,
>>> Important sections are called out to appear differently than the rest of
>>> the text...
>>>
>>>
>>> *Adam Lawson*
>>>
>>> AQORN, Inc.
>>> 427 North Tatnall Street
>>> Ste. 58461
>>> Wilmington, Delaware 19801-2230
>>> Toll-free: (844) 4-AQORN-NOW ext. 101
>>> International: +1 302-387-4660
>>> Direct: +1 916-246-2072
>>>
>>>
>>> _______________________________________________
>>> OpenStack-docs mailing list
>>> OpenStack-docs at lists.openstack.org
>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs
>>>
>>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-docs/attachments/20141021/1f081d4f/attachment.html>