Ticket #13814 (new Bug)
Plone documentation is mostly based on grok examples
Reported by: | mekell | Owned by: | doc-editors@… |
---|---|---|---|
Priority: | minor | Milestone: | 4.x |
Component: | Documentation | Version: | 4.3 |
Keywords: | grok;documentation | Cc: |
Description
AFIK the Plone Framework team decided that they did not want Grok to become a dependency of Plone. Plone 4.3.2 ships without grok as dependency.
On the other side, in the Plone documentation there are plenty of examples based on grok. The order of the examples, their prominence and their quantity suggest that grok is the favored way to develop in Plone.
IMHO this is a mismatch. I think the documentation should be clear in this issue.
Grok is a nice framework, that really simplifies your developing tasks. But in most projects you cannot only stick to "the easy way" but you must have a real understanding of the component architecture.
I think the Plone Framework Team and the Documentation Team should make a statement on this important issue. i.e. to grok or not to grok.