[Product-Developers] Re: Plone Developer Cheatsheet (Was: Re: Where does it hurt?)

Tim Knapp duffyd at kokorice.org
Thu May 29 04:48:05 UTC 2008


On Wed, 2008-05-28 at 21:37 -0700, Jon Stahl wrote:
> Hi Dylan!
> 
> I think this is a great start, and a very useful effort.  It resonates 
> strongly with the documentation team's idea of "trails" that lead you to 
> the key resources for each major topic. 

Yes, definitely a +1

I've joined up and encourage everyone else to add their 2c/euros to the
list on the project-home.

Thanks,
Tim

> 
> :jon
> 
> Dylan Jay wrote:
> >
> >
> > Hi Guys
> >
> > Following on from the "Where does it hurt?" discussion. I've come up
> > with an idea that I think could help reduce the learning curve but I
> > need your help.
> >
> > I've created a Plone Developers Cheatsheet.
> > http://www.openplans.org/projects/plonecheatsheet
> >
> > The idea is a complete list of what you need to learn reduced down to
> > just best practice, not the extraneous stuff.
> >
> > It's an open project and I like you all to be the first members and help
> > get it to a suitably complete state that we can link it from plone.org
> > documentation. It's very empty right now. Please be the first add and 
> > edit.
> >
> > It's my hope that it becomes useful enough to each of us for keeping
> > tabs on what what is best practice and whats the current best tutorial
> > for something. At the same time remains simple enough to help guide a
> > newbie developer into plone.
> >
> > I fully expect that some decisions on what is best practice will be
> > controversial. Hopefully this is a good place to record the results of
> > those debates and perhaps the associated mailing list is good place to
> > have those debates. or on here.
> >
> > Also you can be brutally honest and tell me if you think this won't work
> > and why.
> >
> > Dylan.
> >
> > Martin Aspeli wrote:
> > > Hi guys,
> > >
> > > Following a long discussion with Dylan Jay (buried in another thread on
> > > Devilstick terminology), I thought I'd conduct an informal poll.
> > >
> > > ==> As a customiser of Plone, or as someone wanting to build bespoke
> > > components that extend Plone, what do you find most confusing?
> > >
> > > I think this could fall into a few categories:
> > >
> > > - Areas where there's insufficient/poor documentation, but once you
> > > learn how to do something, it's clear how to proceed.
> > >
> > > - Areas where there appears to be more than one approach, and it's not
> > > clear which one to choose
> > >
> > > - Areas where Plone doesn't appear to have a good way to do something
> > >
> > > Please keep replies as succinct and factual as possible. I'm really not
> > > interested in a winge fest by people who've been frustrated in the past.
> > > I'd much rather have constructive feedback on where the pain is and, if
> > > possible, suggestions for how to improve things.
> > >
> > > Cheers,
> > > Martin
> > >
> >
> >
> 
> 
> _______________________________________________
> Product-Developers mailing list
> Product-Developers at lists.plone.org
> http://lists.plone.org/mailman/listinfo/product-developers





More information about the Product-Developers mailing list