On Sun, Apr 20, 2008 at 3:10 PM, Nicolas Lalevée <[EMAIL PROTECTED]> wrote:
> > This is an introduction mail to the IvyDE build, but we mostly need a > > > documentation in the web site. So I would like to add a page and also > > > make > > > the IvyDE website have a similar hierarchy to the Ivy one. So we would > > > have > > > a "Documentation" and "Get involved" categories. > > > Currently there is > > > * Home > > > o Editor > > > o Classpath Container > > > o Use with maven poms > > > * Download > > > * Issue Tracking > > > > > > So it would become: > > > * Home > > > * Download > > > * Documentation > > > o Editor > > > o Classpath Container > > > o Use with maven poms > > > * Get Involved > > > o Issue Tracking > > > o Building > > > > > > WDYT ? > > > > > > > +1. We could even add a page called mailing lists, telling that they are > > shared with Ivy core and pointing to the right location. > > > > Yep good idea. > And then about the actual folders layout, why not splitting documentation > and site as Ivy does ? And so introduce history, and keeping the IvyDE 1.2 > doc on the web site. > The folders in svn would look like: > > ivyde/ > site/ > index.html (an new home page which would be "version agnostic") > ... > documentation/ (svn:external to trunk/doc) > history/ > 1.2.0 (svn:external to branches/1.2.0/doc) > trunk/ > org.apache.ivyde.eclipse/ > org.apache.ivyde.feature/ > builder/ > doc/ > branches/ > 1.2.0/ > doc/ > index.html (svn cp of trunk/org.apache.eclipse.ivyde/doc/) > cp_container.html (svn cp) > editor.html (svn cp) > maven.html (svn cp) > > > And then have /ant/ivy/site/ivyde be an svn:externals to > /ant/ivy/ivyde/site > Or maybe we could even avoid that external reference and put directly the > main ivyde pages into /ant/ivy/site/ivyde. > > WDYT ? Sounds fine, I was thinking we could keep it simpler until we actually have the need to split site from doc, but I agree it'd be cleaner to go to splitted site/doc now. > > > And by the way, how the live site is updated ? Does every change in svn is > automatically propagated to the web site ? No, the live site is first generated, and put in ivy/site/target. Then we commit the target dir, and update the live site with a svn up. Automating all of this could be interesting, but it requires ant 1.7 which is not available on people.a.o AFAIK. > > > And finally I have a xooki question. First is there any documentation > > > about > > > xooki apart from these pages ? > > > http://xooki.sourceforge.net/ > > > http://ant.apache.org/ivy/write-doc.html > > > > > > > Nope, nothing else. But I can answer questions :-) > > > > he :) > > And as you spread your knowledge, where could I "serialize" it ? > here : http://ant.apache.org/ivy/write-doc.html ? Yes, I think it's a good place. > > > > > > > > > > <http://ant.apache.org/ivy/write-doc.html> > > > And how do I add a main category ? Should I edit directly the json ? > > > > > > > A Main category is like a page, you can add it using the + button. If > > you > > want to have a node with no content (like Ivy/history/2.x) you have to > > edit > > toc.json by hand and add "isAbstract":true, to the node. > > > > ok. But when I do it, the created page is always under the "Home" > category. And I want to create a root category. Indeed, in this case you have to edit the toc.json by hand. Xavier > > > Nicolas > > > > > > > > > > > > > > > cheers, > > > Nicolas > > > > > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > > > > > -- > > Xavier Hanin - Independent Java Consultant > > http://xhab.blogspot.com/ > > http://ant.apache.org/ivy/ > > http://www.xoocode.org/ > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Xavier Hanin - Independent Java Consultant http://xhab.blogspot.com/ http://ant.apache.org/ivy/ http://www.xoocode.org/
