[
https://issues.apache.org/jira/browse/JENA-392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13575423#comment-13575423
]
Andy Seaborne commented on JENA-392:
------------------------------------
There is no robots.txt on the live site. I think it is added by the CMS system
to staging - it's not in the jena-site content SVN. The live site is mirrored
and replicated and so a linkchecker should be OK within reason.
Alternatively, you could build the site locally (see the CMS documentation for
details and setup) and then link check it.
> Are there any tools to improve the documentation
> ------------------------------------------------
>
> Key: JENA-392
> URL: https://issues.apache.org/jira/browse/JENA-392
> Project: Apache Jena
> Issue Type: Question
> Reporter: Claude Warren
> Labels: documentation
>
> This task is here to discuss how we might improve the documentation.
> I recently ran linkcheck from my home system on the production site. There
> were a number of links with issues. I tried to run against the staging site
> but the robots.txt prohibited that.
> I am wondering if there is a way to have the build system run a link check
> after the docs are generated to ensure that there are no broken links.
> I think there are maven tools that will do some other testing (e.g. license
> checks, java doc checks) but much of the documentation is in markdown not
> html so testing may have to be done on the site after staging deployment.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
