On 6/27/07, Gilles Scokart <[EMAIL PROTECTED]> wrote:
2007/6/27, Xavier Hanin <[EMAIL PROTECTED]>: > +Home > +Download > + Choose distribution > (no more other items here) > +Documentation (2.1-beta-1) > + Release Notes (with links to download distributions) > + Introduction > + Settings > + ... > +Documentation (2.0) > + Release Notes > + Introduction > + Settings > + ... > + History > + trunk > + Release Notes > + Introduction > + Settings > + ... > + 2.0 alpha 1 > + Release Notes > + Introduction > + Settings > + ... > + ... > I known that make a lot of of + but I will still add : +1 ;-)
lol. So I'll try to see how I can do that with xooki (splitting a menu inseveral json files) and if nobody complains about this layout and separation between doc and site, I'll go ahead and implement it.
I think tutorials should be part of the documentation, and thus we should > provide the history online. For people "installing" Ivy as suggested in the > "go ivy" tutorial, they don't even download the release with the > documentation. So I think that providing tutorials history online is > helpful, because we can't know when people will move to a new version (when > we release a beta for instance). And if tutorials are part of the > documentation, it's no extra work. > I agree that the tutorial must be kept for the 'top level doc' (latest stable release an potential beta release). But for the other, I don't care. It is not a problem if they are there, but they could be also not be there.
Agreed. And I think it will be easier to have them everywhere (at least for upcoming releases) since it will be the same way to do as for top level docs. Xavier --
Gilles SCOKART
-- Xavier Hanin - Independent Java Consultant Manage your dependencies with Ivy! http://incubator.apache.org/ivy/
