Re: "waldschrotts guide to nifty references" - manualpage draft, version 0.9b

One major advantage of keeping the tutorials and other supplementary materials with the manual is that the PHP team will have control over the quality, presentation and licensing of the resources. This is important because 3rd party sites are often not reliable - they go down, change their content and revenue model, become member only, are abandoned by their maintainer, etc... - zak At 11:27 AM 8/21/00 -0700, Rasmus Lerdorf wrote:

At 21:15 21-08-00, rasmus@lerdorf.on.ca wrote:

We have a bigger documentation team now than any of the other sites out there.

How would you know that? Because I have talked to most of them and am helping a couple of them.

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 see no reason to step into something that's already covered by so many other sites. Link them. Keep the manual elite in what it is. This whole business sounds as if we're competing with other sites, when we really aren't. What does it matter whether it's it on php.net or on another site? This isn't competition. This is additional information. There is no such thing as too much documentation as long as it is well organized. And often it does matter as people look at php.net first, then ask. Cutting down on the number of questions is a good thing. -Rasmus -- PHP Development Mailing List <http://www.php.net/> To unsubscribe, e-mail: php-dev-unsubscribe@lists.php.net For additional commands, e-mail: php-dev-help@lists.php.net To contact the list administrators, e-mail: php-list-admin@lists.php.net