Re: developer.plone.org deeplink redirects?

Dylan Jay <djay-n0pU0XVUApFWk0Htik3J/[email protected]> Tue, 6 May 2014 14:52:54 +1000
Newsgroups	gmane.comp.web.zope.plone.devel
Message-ID	<[email protected]>
On 6 May 2014, at 3:42 am, Héctor Velarde <[email protected]> wrote:

> On 29-04-2014 05:45, sven wrote:
>> I am open for suggestions, I am just not sure that it is so clever to
>> spend now lots of days to check every link and make it a proper 301, is
>> there maybe something what could be done with google webmaster tools or
>> in another way ?
> 
> HV> the old documentation sucked because it was a bad mixture of a manual and a collection of tips on how to do certain things with no clear order or goal.
> 
> with your work we solved part of the problem but we lost most of the tips and we need to get them back in the form of recipes of a Cookbook; IMO:
> 
> - the Cookbook should be a different documentation

I don't think we should go back to that being maintained on a page by page basis however, ie wiki style. I suspect it is more likely to be maintained inside the current documentation bundle which is going to be versioned as a whole.
OR we leave it to stackoverflow, blogs etc.
I think we need to be realistic about how much documentation our community can realistically maintain. Tips are likely to change more often so harder to maintain.

> - every recipe should be tagged with the Plone versions supported and components involved (i.e.: "3.x", "4.x", "viewlets", "testing")
> - we must start using plone.api on all of our documentation
> 
> what's the best way to accomplish this?
> 
> we will also need an Evaluation Guide for people interested on testing Plone to see if it fits their needs.
> 
> and again: good documentation is the kind of things we should have in order to attract more end users, integrators and developers.
> 
> I have open the Idealware's Consumers Guide to Content Management Systems for Nonprofits and we suck in only 2 things:
> 
> - Ease of Hosting and Installation
> - Learning Curve to Set Up a Complex Site
> 
> we are dedicating too much time and resources on "fixing" things that clearly are not broken, like Ease of Content Editing, on which we rock.
> 
> we need to focus on the real problems we have: your work clearly is on the right path.

Which efforts of fixing ease of content editing are you referring to?

You are basing that on a just one documents opinion? I know they try to do look in depth at each CMS but I suspect they have been a little to kind to Plone. Comments like "Site articles can be placed in one or multiple categories. The platform automatically displays the articles in the appropriate sections based on those categories." aren't accurate.


> 
> thank you and best regards
> 
> Héctor Velarde
> 
> ------------------------------------------------------------------------------
> Is your legacy SCM system holding you back? Join Perforce May 7 to find out:
> &#149; 3 signs your SCM is hindering your productivity
> &#149; Requirements for releasing software faster
> &#149; Expert tips and advice for migrating your SCM now
> http://p.sf.net/sfu/perforce_______________________________________________
> Plone-developers mailing list
> Plone-developers-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
> https://lists.sourceforge.net/lists/listinfo/plone-developers

------------------------------------------------------------------------------
Is your legacy SCM system holding you back? Join Perforce May 7 to find out:
&#149; 3 signs your SCM is hindering your productivity
&#149; Requirements for releasing software faster
&#149; Expert tips and advice for migrating your SCM now
http://p.sf.net/sfu/perforce

_______________________________________________
Plone-developers mailing list
Plone-developers-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
https://lists.sourceforge.net/lists/listinfo/plone-developers
signature.asc (application/pgp-signature, 495 B)