Re: Documenting Packages for Future Developers

Hi Israel,

I realise a big manual is more work and harder to comprehend than  
keeping them small but I think its worth the extra effort.
I'm sure it will all work in the wash and I'll have a go organising  
the documentation list you've compiled into some kind of chapter  
structure and see how it looks.

We need a place to put the goals of plone code and where all the  
details fit in. We need to glue all the different bits of developer/ 
integrator documentation to make it make sense.
The reason a bigger manual is better is to make that explanation of  
plone is as cohesive as possible. so any change is reviewed against  
the whole manual.

don't you think its how all the pieces of plone fit togeather that we  
are missing?


On 06/01/2009, at 10:17 AM, Israel Saeta Pérez wrote:

> On Mon, Jan 5, 2009 at 11:39 PM, Dylan Jay wrote:
> Hi Israel,
>
> I had a look at your current list of development manuals. Perhaps  
> I'm missing something here but is there a good reason not to make  
> them chapters of one big manual? I can see lots benefits in one  
> development manual and not many downsides but I must be missing  
> something.
>
> What benefits do you see in creating a mega-manual with several  
> chapters instead of several manuals under the "development" topic?
>
> -- israel
>
> ------------------------------------------------------------------------------
> _______________________________________________
> Plone-docs mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/plone-docs


------------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It is the best place to buy or sell services for
just about anything Open Source.
http://p.sf.net/sfu/Xq1LFB