list of broken links about documentation HOT 8 CLOSED

what we do with howtos which are old but not really best practices anymore, for example downloading nginx-sticky module to compile your own nginx, but these module is now already in nginc-core ?

from documentation.

update the howto, or in the worst case delete the link. We don't want to link to non-current practices (at least not for the 4.3 version of the docs. If they only occur in the 3.3. version, they can stay, as that will be 'frozen in time'.

from documentation.

links for 'manage' are done !

from documentation.

@polyester could you update the list ?

from documentation.

updated list: https://github.com/plone/documentation/blob/master/broken-links-nov2014.txt

from documentation.

I found this issue when I was looking for what to do about this broken link, which is on develop/plone/security/sandboxing.rst.

I checked this file and could not find it: https://github.com/plone/documentation/blob/5.0/broken-20140331.txt

But it is in https://github.com/plone/documentation/blob/4.3/broken-links-nov2014.txt
(notice 4.3 vs 5.0)

So the question is: has anyone decided what to do about the kb articles?

from documentation.

at the Stroopwafel and Munich doc-sprints, people looked through the kb and decided to scrap the whole thing. There may still be some valid nuggets of information in there, but the ratio of valid versus outdated-to-plain-dangerous is not favorable, to say the least.

So links to the kb should be removed. If you happen to find one that contains sane, still-valid info, the content of the kb-article should go into the docs.

from documentation.

closing this we know that we have lots of broken links, they are fixed step by step on the way and will included into the coming docs test framework

:)

from documentation.