Re: Amsterdam meeting agenda
| From: | Martin Jansen | Date: | Sat, 10 Apr 2004 10:55:33 +0000 |
| Subject: | Re: Amsterdam meeting agenda | ||
| References: | 1 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-27383@lists.php.net to get a copy of this message | ||
On Sat Apr 10, 2004 at 11:1013AM +0200, Bertrand Mansion wrote:
> - Online documentation system
> I am thinking about some sort of automatic inline doc extractor that would
> create the API documentation, using PHPDocumentor, and add it to PEARDoc
> automatically. All this would be done on PEAR web. The process will be the
> same as with the new release upload. Actually, it could even be made at the
> same time.
We have been discussing about this on the documentation mailing list
some time ago. Back then we came to the conclusion that it is wise
to *not* merge the documentation from PHPDocumentor into the manual,
because it would then take literally days to build it. Instead we might
provide automatically generated API documentation separately from the
"main" documentation.
> I think we also need some sort of CMS for the documentation system so that
> we could easily add tutorials and class description.
>
> And the process should also be possible in the other way, I mean you provide
> your class and the API doc is copied from the PEAR site to your class. You
> get a fully commented and updated class back.
>
> The goal is to get rid as much as possible of Docbook, which is in my
> opinion the biggest mistake made by PEAR. I think we should also discuss the
> adoption of another format like reSt to replace it.
I do not think we should drop Docbook. Instead I like the idea of
having a reST -> Docbook converter with which people can
semi-automatically convert their reST file into proper Docbook, which
will then be added to the manual. The Horde project has been starting
to develop a PHP-based reST parser, which I'm planning to use as well.
--
- Martin Martin Jansen
http://martinjansen.com/