looks like a huge improvement. Maybe the menu should be further to the left and the content further to the right, but that is a minor point.
Good job! /Kent Den 06/05/2012 kl. 09.36 skrev Niclas Hedhman: > Gang, > > Please review http://www2.qi4j.org and provide feedback. A few things > can be pre-empted; > > 1. Yes, the design isn't perfect, but we don't have a design guru > that has enough cycles to throw at it. > > 2. Content. Yes, there are a lot of content that is not written. It > never was, partly due to Sitevision having too high barrier for > someone who wanted to create documentation. > > > So, what is at play here; > > 1. Documents are edited in AsciiDoc format[1], straight into our > source repository, typically in src/docs in parallel to src/main to > point out that the developer should write the documentation as well. > > 2. The Documentation.groovy build tool in buildSrc/ calls the > AsciiDoc, DocBook and DocBook XSL toolchains to create statically > generated web pages. > > 3. There is a script on server that pulls GitHub, builds the website > and copies the result to the mounted URL. This script is activated by > a POST request and could be added to GitHub's hooks, I think. > > > Finally one question; What other excuse(s) can developer now have for > not writing documentation? > > > [1] http://www.methods.co.nz/asciidoc/userguide.html > > > Cheers > -- > Niclas Hedhman, Software Developer > http://www.qi4j.org - New Energy for Java > > I live here; http://tinyurl.com/3xugrbk > I work here; http://tinyurl.com/6a2pl4j > I relax here; http://tinyurl.com/2cgsug > > _______________________________________________ > qi4j-dev mailing list > [email protected] > http://lists.ops4j.org/mailman/listinfo/qi4j-dev > _______________________________________________ qi4j-dev mailing list [email protected] http://lists.ops4j.org/mailman/listinfo/qi4j-dev
