From: Peter Eisentraut <peter_e@gmx.net>
To: Albert Cervera i Areny <albert@nan-tic.com>
Cc: pgsql-docs@postgresql.org
Subject: Re: Tips needed for contrib doc
Date: Sun, 14 Oct 2007 15:05:14 +0200
Message-ID: <200710141505.14690.peter_e@gmx.net> (raw)
In-Reply-To: <200710122004.44884.albert@nan-tic.com>
References: <200710102315.50067.albert@nan-tic.com>
<200710121947.15037.peter_e@gmx.net>
<200710122004.44884.albert@nan-tic.com>
Albert Cervera i Areny wrote:
> Not that I want to make each module a reference. With previous
> discussions we seemed to agree that:
>
> - It should go into the References part of the documentation (right
> after "III. PostgreSQL Server Applications).
> - Each module docs should be in a single page, mainly because some
> contrib modules have/require very little documentation.
It think you should structure the documentation by content, not by
output format. You could make each module a section or a chapter, as
you choose.
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-docs@postgresql.org
Cc: peter_e@gmx.net, albert@nan-tic.com
Subject: Re: Tips needed for contrib doc
In-Reply-To: <200710141505.14690.peter_e@gmx.net>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox