Programmer's Reference Guide
Guide de référence du programmeur
Sommaire- Introduction au Zend Framework
- Apprendre Zend Framework
- Démarrez rapidement avec Zend Framework
- Chargement automatique avec Zend Framework
- Les plugins dans Zend Framework
- Bien démarrer avec Zend_Layout
- Bien démarrer avec Zend_View
- Bien comprendre et utiliser les décorateurs Zend Form
- Bien démarrer avec Zend_Session, Zend_Auth, et Zend_Acl
- Bien démarrer avec Zend_Search_Lucene
- Bien démarrer avec Zend_Paginator
- Guide de référence Zend Framework
- Zend_Acl
- Zend_Amf
- Zend_Application
- Zend_Auth
- Zend_Barcode
- Zend_Cache
- Zend_Captcha
- Zend_CodeGenerator
- Zend_Config
- Zend_Config_Writer
- Zend_Console_Getopt
- Zend_Controller
- Zend_Currency
- Zend_Date
- Zend_Db
- Zend_Debug
- Zend_Dojo
- Zend_Dom
- Zend_Exception
- Zend_Feed
- Zend_File
- Zend_Filter
- Zend_Form
- Zend_Gdata
- Zend_Http
- Zend_InfoCard
- Zend_Json
- Zend_Layout
- Zend_Ldap
- Zend_Loader
- Zend_Locale
- Zend_Log
- Zend_Mail
- Zend_Markup
- Zend_Measure
- Zend_Memory
- Zend_Mime
- Zend_Navigation
- Zend_Oauth
- Zend_OpenId
- Zend_Paginator
- Zend_Pdf
- Zend_ProgressBar
- Zend_Queue
- Zend_Reflection
- Zend_Registry
- Zend_Rest
- Zend_Search_Lucene
- Zend_Serializer
- Zend_Server
- Zend_Service
- Zend_Session
- Zend_Soap
- Zend_Tag
- Zend_Test
- Zend_Text
- Zend_TimeSync
- Zend_Tool
- Zend_Tool_Framework
- Zend_Tool_Project
- Zend_Translate
- Zend_Uri
- Zend_Validate
- Zend_Version
- Zend_View
- Zend_Wildfire
- Zend_XmlRpc
- ZendX_Console_Process_Unix
- ZendX_JQuery
- Configuration système requise par Zend Framework
- Notes de migration de Zend Framework
- Convention de codage PHP de Zend Framework
- Zend Framework Documentation Standard
- Recommended Project Structure for Zend Framework MVC Applications
- Guide de performance Zend Framework
- Informations de copyright
Guide de référence de Zend Framework destiné au programmeur
©
2005-
Zend Technologies Inc.
(http://www.zend.com)

Comments
( Already logged in and when trying to add comments asking for name and email . Seems like a bug :( . Also its showing logged in as () null value . )
a) thank you for writing a documentation.
b) the downloaded documentation/manual/core/en is full of HTML-Bugs
c) it doesn't contain an index-page
d) none of the html pages validates on http://validator.w3.org/
e) adding a stylesheet instead of putting an invalid STYLE tag in the middle of the code would have been an alternative that is not-so-unusual today
I assume the makers of the Zend Framework made great efforts to produce a high quality framework. The downloadable documentation will need some quality-check too.
best regards
regards
Oliver
There is a lot of content which is good but huge parts aren't written very well. Very little cross-referencing too which makes the long page formats tough to navigate. Better indexes (already mentioned above) and "jump to section" links are desperately needed.
The search is awful. It always has been and it frustrates me to no end by bringing back either no results or barely relevant results. I've put up with it for months but clearly it isn't something that's being worked on as there haven't been any perceived improvements in that time so I have finally snapped and am giving you some feedback!
For example I get no results if I search for "action helper" or "url". Really? No results? At least let me get some bad results so I can adjust my search terms appropriately.
Instead I must always use Google to search your documentation. Not ideal.
Thanks!
Mark
I'm aware that online documentation is a better and easier way to provide up-to-date accurate documentation but, i would love to see also a pdf version of the stable release available for those, who like me, like to do some offline( see before bedtime) reading...
The quickstarts are good, but the main documentation is a big turn off. I'm sure your driving aware newbies.
Maybe incorporating Google Search via API would be a stop gap until search can be improved?
For most components I tried to understand (Layout, Navigation, Auth, Acl) there was two to five examples on how to do exactly the same thing - this is really confusing. And for none of the components, there was really working code.
Examples:
From just the information you get here, try to build a sample app which does:
- Have a website with 3-4 different basic layouts (2-3 frontand and one backend)
- Session handling with user authorization
- Authentication
- Navigation
- MVC with proper sub-view (or partials) encapsulation
The quick start example answered at least some of my questions, but even that was far from enough.
Hope this will be the last Vote !