river-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Tom Hobbs <tvho...@googlemail.com>
Subject Re: svn commit: r780269 - /websites/staging/river/trunk/content/river/docs/index.html
Date Wed, 08 Dec 2010 14:47:44 GMT
It is big.  Also very boring.

A link check when I'm done would be great, as I know already that some
of the links are broken.

I'm dropping some content as I go along because we have better docs
elsewhere (e.g. the build instructions) but other things, like the
activation.html and I'm sure others, I will make sure get linked to
from somewhere.

If anyone one wants to help I've started in the parent docs directory.
 There are the release-notes and specs directories that also need

On Wed, Dec 8, 2010 at 1:38 PM, Sim IJskes - QCG <sim@qcg.nl> wrote:
> On 08-12-10 13:26, Tom Hobbs wrote:
>> This is not fun work and i've not sorted the formatting out yet.  Also
>> I image that many of the links are broken.
>> We certainly need to fix the "original Jini wiki" links, and probably
>> put a link to the specs on the front page.  I think it's more
>> intuitive to have them there than on the "Documentation" sub-page, I
>> can't explain my reasoning other than gut feel.
>> I'd like to leave the link broken for now until I've got the specs in
>> better order.  I think that it's going to take a while...
> It curtainly looks like an huge job. We have to do the release notes for
> every release. How do we do this in the future? We should give the release
> notes their own directory, so we can keep a online archive of them for later
> use. We could also give them their own style and sidebar.
> Do you want a linklint (link check) once in a while?
> Gr. Sim
> --
> QCG, Software voor het MKB, 071-5890970, http://www.qcg.nl
> Quality Consultancy Group b.v., Leiderdorp, Kvk Den Haag: 28088397

View raw message