Re: Fwd: Help document Plone's API

Mikko Ohtamaa wrote:
> I volunteer to have

Cool!

I still need someone to own the overall document/structure. If that's 
Israel, then that's great.

> 1) HTTP request and HTTP response
> 
> 2) Workflows
> 
> 3) Sessions
> 
> 4) Property sheets (portal_properties)
> 
> 5) Overriding site views, viewlets and utilities
> 
> I don't volunteer to have
> 
> 1) traversing (after 5 years I don't understand properly...)
> 
> 2) transactions and Zope persistency (don't understand test layer part
> + some persistency magic)
> 
> 3) CMFFormController and old Python scripts (ugh)

Let's get the structure in place in a Reference Manual on plone.org with 
sections and pages, and then people can just start filling in pages.

> Some open questions:
> 
> 1) how do we relate this to the current Archetypes tutorial?

Just link to it where appropriate. Remember, the goal here is not to 
teach you everything you need to know about Plone. Rather, we're aiming 
to have an easily accessible single place to find the most common/useful 
APIs (and, further down the line, a way for us to "bless" those as 
official and sanction changes to them over time in a controlled manner).

I suspect there'll be a lot of "For more information and background, see 
..." type links.

Martin

-- 
Author of `Professional Plone Development`, a book for developers who
want to work with Plone. See http://martinaspeli.net/plone-book


------------------------------------------------------------------------------
Register Now for Creativity and Technology (CaT), June 3rd, NYC. CaT 
is a gathering of tech-side developers & brand creativity professionals. Meet
the minds behind Google Creative Lab, Visual Complexity, Processing, & 
iPhoneDevCamp as they present alongside digital heavyweights like Barbarian 
Group, R/GA, & Big Spaceship. http://p.sf.net/sfu/creativitycat-com