diff options
Diffstat (limited to 'docs')
| -rw-r--r-- | docs/tutorials/cmf/index.rst | 19 |
1 files changed, 11 insertions, 8 deletions
diff --git a/docs/tutorials/cmf/index.rst b/docs/tutorials/cmf/index.rst index b9e837a21..09223138c 100644 --- a/docs/tutorials/cmf/index.rst +++ b/docs/tutorials/cmf/index.rst @@ -10,17 +10,20 @@ application to :mod:`repoze.bfg`. The main difference between CMF and :mod:`repoze.bfg` is that :mod:`repoze.bfg` does not advertise itself as a system into which you can plug arbitrary "packages" that extend a system-supplied management -user interface. For those sorts of high-extensibility, -highly-regularized-UI systems, CMF is still the better choice. +user interface. You *could* build a CMF-like layer on top of +:mod:`repoze.bfg` (as CMF is built on Zope) but none currently exists. +For those sorts of high-extensibility, highly-regularized-UI systems, +CMF is still the better choice. -:mod:`repoze.bfg` (and other more lightweight systems) are often a +:mod:`repoze.bfg` (and other more lightweight systems) is often a better choice when you're building the a user interface from scratch, -which often happens when the paradigms of the system-provided user +which often happens when the paradigms of some CMF-provided user interface don't match the requirements of an application very closely. -Despite the mismatch, a good number of developers tend to use CMF even -when the UI requirements aren't a very good fit, because it happens to -provide other helpful services, such as types and skins; this tutorial -is for those sorts of developers. +Even so, a good number of developers tend to use CMF even when they do +start an application for which they need to build a UI from scratch, +because CMF happens to provide other helpful services, such as types, +skins, and workflow; this tutorial is for those sorts of developers +and projects. Missing: |