Re: Let's turn off api.plone.org.

Alex Clark wrote:
> Hi all, 
> 
> [...]
> However, we'll need to be very careful about that as Hanno points out:
>     11:33 <@hannosch> the Zope2 looks nice, but it tells you to develop Zope2 
>         in the 1990-style. I wouldn't want to point anyone to it
>     11:33 <@hannosch> some of the stuff about security and the catalog is still
>         the same, but dtml, python scripts, the OFS nah
> 
> Maybe something like:
>     Please see the relevant Zope 2 Sphinx docs here: http://docs.zope.org/zope2/zdgbook/source/
>     including:
>         - TAL
>         - Security
>         - Catalog
>     But you can ignore:
>         - DTML
>         - OFS
>     and then look in http://plone.org/documentation for help with:
>         - Installing add-ons
>         - Writing filesystem products
>         - Etc.
> would do it? Anyway, let me know! My feeling is that anything is better than outdated 
> and useless docs at this point (looking for a flurry of +1s here please ;-).

I'm +1 on removing the current api.plone.org.

Since some people use it as a grep-like tool, I'd place some ideas here 
about how to find the source of a certain method, like using grep (with 
an example if possible), collective.recipe.omelette and DocFinderTab.

I'd also provide a link to plone.org/documentation, but no link to the 
zope 2 documentation to avoid having to explain which part is updated 
and which one isn't.

-- israel


------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
trial. Simplify your report design, integration and deployment - and focus on 
what you do best, core application coding. Discover what's new with 
Crystal Reports now.  http://p.sf.net/sfu/bobj-july