Why is the Zend Framework API documentation poor?

Question

Is this my browser that doesn’t work with their online API documentation ?

The structure seems to be very poor compared to the Java API online documentation and the Yii API online documentation .

I'm new to the Zend Framework, so I'm wondering if this should be the case?

Answer 1

I think the API is good, the only problem sometimes does not give the real meaning of the arguments

After the API, maybe a little behind some Java examples, but I find the reference guilde quiet impressive and complete. You have 900 pages describing each part of the framework with a short piece of code, which is just wonderful.

Personally, I often use the reference guide, and then the API documentation.

Answer 2

I've been digging into the Zend Framework for two months now. I'm starting to catch, but I have to agree with the original comment. The API documentation, at least what is available, is fierce. What kind of material is Dojo anyway? I would expect the correct standardized API link for something as vast and powerful as the Zend Framework. For an experienced software engineer, the reference guide is really introductory material. After it is digested, all that is really needed is a good API link, which clearly indicates the properties, methods, inheritance tree with brief descriptions, where necessary. Like Java, AS3, etc. I could save about two weeks if I had full access to the API. I do not understand, but I intend to persist with ZF.

Answer 3

For me, the problem is that the reference guide simply lists all the components and has a massive page that talks about the longest uses of each component without any area in which the specified code should appear in your workflow.

I believe that it should be overestimated to be similar to CakePHPs documentation , where each page is designed to receive a specific task, for example, “Saving data”, “Deleting data”, “Checking data”, etc.

Real-life examples with context are much more useful than Zend Docs, where I usually have to guess where certain variables come from (usually $db ), and in full MVC cases don't even apply.