hepabolu wrote:
Ross Gardler wrote:
In this way people only see what either we want them to see, or they
choose to see. This is akin to users only having access to the bundled
docs in a release, but devs having access to the development docs in SVN.
True, but if we point the users to the co
Ross Gardler wrote:
In this way people only see what either we want them to see, or they
choose to see. This is akin to users only having access to the bundled
docs in a release, but devs having access to the development docs in SVN.
True, but if we point the users to the cocoon.zones site the
hepabolu wrote:
Ross Gardler wrote:
...
For __future__ releases, we will have a third option:
c) include the forrest block and cocoon docs configuration files
-1 for this, although it should be moved to another thread.
I don't think it's a good idea to give "all" users access to the s
