Re: Feature Request: deeper TOC for pear.php.net manual

Greg Beaver wrote:

It would no problem to write, but this is the best way to confuse users.

I don't follow you. As a user, I would automatically search for a number manipulation package under "Math." I would look for a number text manipulation package under "Text." I would never think to look for a template engine under "HTML," that is completely illogical. Template This is not a doc problem - the peardoc categories follows the categories of the package browser.

I think you has two problems of understanding: 1.) rendering vs logical structure, as proposed in an early mail, we can provide a toc with a simple package overview 2.) the categories are given by the pear community - if a Template category would exists, it will exists in the manual too.