[drupal-docs] Handbook 2
Boris Mann
borismann at gmail.com
Sat Apr 16 17:35:48 UTC 2005
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.
> > 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
For, #2, I think we have style guidelines: http://drupal.org/node/15289
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.
> > 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...
One thing I'd like is the use of path-aliasing in a new handbook.
--
Boris Mann
http://www.bryght.com
More information about the drupal-docs
mailing list