You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@forrest.apache.org by Cyriaque Dupoirieux <Cy...@pcotech.fr> on 2005/03/24 10:28:45 UTC

Broken link in forrest site

Hi,

    In the page http://forrest.apache.org/contrib.html, the following 
links are broken because "site" is not declared :

    *     Chapter :"How to prepare and contribute patches"

          o "It is always a good idea to check the Forrest issue tracker
            <http://issues.cocoondev.org/secure/BrowseProject.jspa?id=10000>
            and to do list <site:todo>  <<Bad Link>> before diving in."
    * Chapter : "Contribution Notes and Tips"
          o When making changes to XML documentation, or any XML
            document for that matter, use a validating XML editor. Here
            is some assistance with editor configuration <site:catalog>.
            <<Bad Link>>


-- 

Regards,
Cyriaque,


Re: Broken link in forrest site

Posted by David Crossley <cr...@apache.org>.
Cyriaque Dupoirieux wrote:
>    In the page http://forrest.apache.org/contrib.html, the following 
> links are broken because "site" is not declared :
> 
>    *     Chapter :"How to prepare and contribute patches"
> 
>          o "It is always a good idea to check the Forrest issue tracker
>            <http://issues.cocoondev.org/secure/BrowseProject.jspa?id=10000>
>            and to do list <site:todo>  <<Bad Link>> before diving in."
>    * Chapter : "Contribution Notes and Tips"
>          o When making changes to XML documentation, or any XML
>            document for that matter, use a validating XML editor. Here
>            is some assistance with editor configuration <site:catalog>.
>            <<Bad Link>>

Thanks, there are many such issues in the Forrest docs. A while ago
we had to hurriedly split them into top-level docs and technical docs
specific to each version. Remnants such as this need to be fixed.

That is one of the main reasons for the upcoming 0.7 release.
To finalise the re-arangement of the documentation. It would
be grand if people would help to track down issues such as this.

--David