On 6/21/11 24:19 , Niclas Hedhman wrote:
The current website is kind of
stagnant, and needs a facelift. Apart from design, add more docs (how did it
go with the Javadoc->website idea Niclas?)
Well, there are many aspects of it, right.
1. Generated javadoc, versioned, available online.
2. Extract package.html from sources and embed on pages.
3. Leave SV in favor of more statically generated site, editable and
versioned via Git.
3. Either a Git-thing, or something more wiki-like, such as MediaWiki,
would work. Not sure if there's any good Git-ish CMS's out there though.
Whatever we do needs to be easy to use, and support 1 and 2 as well.
A bunch of the changes that are now flowing through are quite
incompatible. Shall we bump to 2.0 in next release? Does such step
slow us down too much, or shall we simply go for it, and if additional
incompatibilities sail up we are not afraid to call it 3.0 if needed?
I would probably suggest that we bump it to 2.0, both with regard to
incompatibilities and also the Scala support, which is a major milestone
I think.
/Rickard
_______________________________________________
qi4j-dev mailing list
[email protected]
http://lists.ops4j.org/mailman/listinfo/qi4j-dev
