Date: 08/28/00
- Next message: Stig S. Bakken: "Re: [PHP-DOC] Re: [PHP-DEV] "waldschrotts guide to niftyreferences" - manualpage draft, version 0.9b"
- Previous message: Lars Torben Wilson: "Re: [PHP-DOC] cvs: phpdoc /en/functions info.xml"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
rasmus <email protected> wrote:
>
> > Why do it? Other sites invest tons of time (and sometimes money) to do
> > just that. There's no reason to compete with them, because you can't
> > invest as much time into this, and you shouldn't have to. Invest time at
> > what you're good at, which is an accurate description of the
> > language. Link other sites for tutorials. Why not leverage the power of
> > hyperlinks?
>
> We have a bigger documentation team now than any of the other sites out
> there. We have the resources and the structure to do a very good job on
> this. The more examples we can put into the documentation, the better,
> and if somebody wants to write some full tutorials, I see no reason for
> not including them as long as they don't get in the way. That is, they
> would be put into the appendix or into a separate chapter so as to not
> interfere with the concise function reference.
I agree. Make a tutorials/ directory, a tutorials chapter and start
putting tutorials in there. If we feel the manual becomes way too
bloated because of it, move the tutorial chapter(s) to a new book. The
FAQ could be dealt with the same way. I don't understand why some
people have to make problems out of everything. *grumble*
- Stig
- Next message: Stig S. Bakken: "Re: [PHP-DOC] Re: [PHP-DEV] "waldschrotts guide to niftyreferences" - manualpage draft, version 0.9b"
- Previous message: Lars Torben Wilson: "Re: [PHP-DOC] cvs: phpdoc /en/functions info.xml"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

