Re: Developer manual "tutorials" section?

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.

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



> 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 :)


-----

http://twitter.com/moo9000 Follow me in Twitter 



mFabrik News – 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