On 10/22/07, Xavier Hanin <[EMAIL PROTECTED]> wrote:
>
> On 10/21/07, Jacob Grydholt Jensen <[EMAIL PROTECTED]> wrote:
> >
> > Hi,
> >
> > On 21/10/2007, Xavier Hanin <[EMAIL PROTECTED]> wrote:
> > > I've worked on this tutorial, the update is now available in svn
> > trunk, I'll
> > > upload it to the site in a moment. Feel free to give feedback or
> > improve it!
> >
> > I have opened IVY-626 with a few changes to the start.html page. Is
> > the "using ivyrep" tutorial still alive? My understanding is that the
> > quick start-tutorial supersedes that tutorial, but there is still a
> > link to the "using ivyrep" tutorial on the website.
>
>
> Indeed, the "using ivyrep" is not supposed to be still there... I'll have
> a look to check why we still see it in the menu.
>

It seems I just forgot to generate all the site from scratch again: after
generation the menu is stored in each page, so we need to make a "ant clean
publish-site" whenever  we change the TOC.

Xavier

I used Emacs to modify the HTML pages directly rather than using the
> > clever edit button embedded on the page. The howto on contributing
> > documentation only mentions the edit button, but I assume that I can
> > use any old editor as long as I am nice to xooki.
>
>
> Indeed, any text editor is just fine. The advantage of the edit button is
> that if you get accustomed to browse the doc from a svn checkout, whenever
> you see something to fix or improve in the doc while you're reading it, you
> can very easily edit the page and contribute the patch, without having to
> locate corresponding file on your file system and open it in your favorite
> text editor. And it's also a good way to have an immediate overview of how
> the page looks like after the edit.
>
> Xavier
>
> /grydholt
> >
>
>
>
> --
> Xavier Hanin - Independent Java Consultant
> http://xhab.blogspot.com/
> http://ant.apache.org/ivy/
> http://www.xoocode.org/
>



-- 
Xavier Hanin - Independent Java Consultant
http://xhab.blogspot.com/
http://ant.apache.org/ivy/
http://www.xoocode.org/

Reply via email to