[drupal-docs] Handbook 2

[Anisa]

Boris Mann wrote:

>On 4/15/05, Djun Kim <puregin at puregin.org> wrote:
>
>  
>
>>    I have certain reservations about inflicting technical
>>typesetting on the general population, though.  Seeing naked
>>XML or LaTex may be scare away potential contributors.
>>    
>>
>
>Djun, if you look back at the archives, that's pretty much where
>things stalled. I *know* that I can't contribute significantly if I
>have to make a mode-switch to using an offline tool to do docs.
>
>I believe there are tools available to go HTML -> DocBook.
>
>  
>
It took me *forever* to find that docbooks wiki link.  >.<

>>>I have two ideas.
>>>1. We go ahead with making new books, along the lines suggested in
>>>the wiki set up for handbook 2.  Establish style guidelines.  We set
>>>up a wiki appropriate for documentation that is easy to use so that
>>>people can rewrite and revise old handbook pages.  No automatic
>>>updating, but updating wouldn't be so bad.
>>>      
>>>
>
>I'm all for #1. FYI, the new structure for the handbook has been
>discussed here: http://dev.bryght.com/t/wiki/HandbookVersionTwo
>
>  
>
Really?  No crying over the inability to edit outlines?  :)

>For, #2, I think we have style guidelines: http://drupal.org/node/15289
>
>  
>
In the interests of brevity, I believe I have previously explained what 
I mean by serious style guide lines and given examples as well.

>As much as I point to the wiki for ad-hoc work, I don't think we need
>it for changing the handbook -- that's what book pages are for, after
>all: everyone on the doc team has permission to edit all book pages.
>
>  
>
I am told everyone who is a site maintainer has permission to edit all 
book pages, which is not equivalent.  ^.^

I think making the handbook the site for that kind of change is part of 
what makes it so messy.  You turn the handbook into a kind of wiki that 
way, and I don't know that it's particularly equipped to do that.

>>>2. This may be totally yokei, but could we make a better handbook if
>>>we made it through a tightly controlled taxonomy with pages/special
>>>node type instead of using the book module? Anisa.
>>>      
>>>
>
>I think this needs more fleshing out. I think the book module is
>appropriate for documentation. Is there a way that a cross-index could
>be applied with taxonomy terms? Perhaps, can't quite think how that
>would work at this point. Also, more stalling while this gets
>developed...
>
>  
>
yokei means unnecessary, potentially in 
an-interfering-with-the-business-at-hand sort of way.

^.^

I am not particularly strong in taxonomy, but I do think a cross index 
might be interesting.  All pages with Example Code, for example.

>One thing I'd like is the use of path-aliasing in a new handbook.
>
>  
>
What happens when you want to change the page title?

Anisa.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://drupal3.drupal.org/pipermail/documentation/attachments/20050416/19ddd867/attachment.htm