The documentation available is a jumbled up mish mash.
Almost obscene for a product that is so capable of documenting virtually anything in any way.
Kudos to anyone else who is trying. But I am at a loss as to why anyone attempts this in any format other than eZ Publish with eZ Flow.
Use the greatest web communications tool ever devised, to tell how to use the greatest web communications tool ever devised.
Any and all helpful suggestions appreciated, (I already have too many links to count - keep them coming). "Your site is a worse disorganized mess than the documentation" is not a helpful suggestion. You should put x here and y there because ... from more than one person and maybe progress will be in the right direction. Meantime, use the search box.
Too much information is part of the problem, especially for newbies taking their first crack at eZ Publish. Applying meaningful organization to the best available information is the goal.
A few possible explanations for the poor documentation..
A. Experts likely waste very little time reading even the provided documentation package. It is much more straightforward and productive to just dive in to the elegant codebase via doxygen or direct from the downloaded source.
B. Newbies quickly find the parts of the application and documentation that are most useful to them, get the project done, move on.
C. Enthusiastic educational discussions of theory (much of the provided docs) morph too rapidly to remain of practical use for very long.
The aim of this site is to maintain focus on "git er done" solutions-based examples. No theory. In time theorizing, content can be produced. IMHO many drawn to eZ Publish want to produce content above all else, much more fun than learning and theory!
