Re: Developer manual "tutorials" section?

Dylan Jay <dylan-Q+/Sk2sTzaxWk0Htik3J/[email protected]> Fri, 18 Feb 2011 00:38:27 +1100
Newsgroups gmane.comp.web.zope.plone.documentation
Message-ID <[email protected]>
On 17/02/2011, at 10:06 PM, Mikko Ohtamaa wrote:

>
>
> Dylan Jay-4 wrote:
>>
>>
>>> On Feb 16, 2011, at 2:47 AM, Dylan Jay wrote:
>>>> Is it just me or does the "tutorials" section of the community
>>>> developer manual feel out of place?
>>
>
> It is no planned very well, so putting things to proper places is  
> maybe a
> topic for upcoming sprints.

fair enough. Along with merging the two manuals + deleting any KB  
articles with content already covered in the manual.

>
> I'd suggest the section is renamed to "Tools, technologies and  
> processes".

Isn't the whole document about tools, technologies and processes?
Are you trying to say that things like ArchGenXML and buildout are  
external to Plone so should be in it's own section?
If so I disagree. I think it's more helpful to organise things by how  
it helps the developers. ArchGenXML helps you create content types.  
Buildout helps you configure plone. Paster is about creating plugins/ 
packages.

>
>> I've been thinking hard on how to do this but no answers yet.
>> For those not aware the community manual on plone.org is actually the
>> result of a conversion process from svn -> sphinx -> funnelweb ->
>> plone. The information on where items used to be isn't available to
>> sphinx from svn so it's not possible automate this yet so any  
>> renaming
>> in svn won't result in redirects in plone :( Unless someone can think
>> of a clever way to get svn to produce a list of previous paths for
>> each piece of content.
>> The only solution would be to manually reproduce the moves in plone
>> first and then reupload the content overtop.
>>
>
> The conversion process is already little fragile, so I suggest let's  
> not try
> to make it more complicate and we'll just rely on Plone's automatic  
> "Page
> not found - suggestions" feature :)

Tell me what's going wrong and I'll fix it.

>
>
> -----
>
> http://twitter.com/moo9000 Follow me in Twitter
>
>
>
> mFabrik News &ndash; download now for iPhone and Android
>
>
>
> http://bit.ly/mfabrikitunessignaturemoo
> http://blog.mfabrik.com/wp-content/uploads/2011/01/iPhoneFooter.png
>
>
> http://bit.ly/mfabrikandroidsignaturemoo
> http://blog.mfabrik.com/wp-content/uploads/2011/01/AndroidFooter.png
>
>
>
> -- 
> View this message in context: http://plone.293351.n2.nabble.com/Developer-manual-tutorials-section-tp6030918p6035464.html
> Sent from the Documentation Team mailing list archive at Nabble.com.
>
> ------------------------------------------------------------------------------
> The ultimate all-in-one performance toolkit: Intel(R) Parallel  
> Studio XE:
> Pinpoint memory and threading errors before they happen.
> Find and fix more than 250 security defects in the development cycle.
> Locate bottlenecks in serial and parallel code that limit performance.
> http://p.sf.net/sfu/intel-dev2devfeb
> _______________________________________________
> Plone-docs mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/plone-docs


------------------------------------------------------------------------------
The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE:
Pinpoint memory and threading errors before they happen.
Find and fix more than 250 security defects in the development cycle.
Locate bottlenecks in serial and parallel code that limit performance.
http://p.sf.net/sfu/intel-dev2devfeb