Re: Documenting Packages for Future Developers

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.

On 06/01/2009, at 4:56 AM, Israel Saeta Pérez wrote:

> On Mon, Jan 5, 2009 at 8:37 AM, Dylan Jay wrote:
> Important thing is to help with the manual. What is it you need us to
> do Israel?
>
> First of all, thanks for volunteering. :-)
>
> I've already completed the assessment chart for the development  
> section, indicating in the 2nd column wheter it should become part  
> of a manual or not. I still have not clear at all what manuals will  
> finally be in our documentation, e.g.:
> 	• Content-types.
> 	• Testing.
> 	• Cataloging and searching (portal_catalog tool).
> 	• Security.
> 	• ...
> I personally really need help in this task so feel free to step in  
> and help to write that list (use openplans). I reccommend looking at  
> the documentation of similar CMS's and frameworks to gather ideas. :-)
>
> -- israel
>
> ------------------------------------------------------------------------------
> _______________________________________________
> Plone-docs mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/plone-docs


------------------------------------------------------------------------------