Hi,
AFAIK the site docs (in thier current form are in the xdocs format),
however it seems that they are also marked up with some
html/xhtml/xdoc meaning that automating the transformation into the
apt format is becoming a hellishly tedious and extremely time
consuming task.
I'm using the doxia
Lewis,
With Maven site, does it mean we are still using the svn pubsub or we could
move to ASF CMS for publishing it?
- Henry
On Fri, Nov 30, 2012 at 3:47 AM, Lewis John Mcgibbney
lewis.mcgibb...@gmail.com wrote:
Hi All,
I'm currently setting about the transition from Forrest to Maven for
Hi Henry,
When I started on this my opinion changed somewhat
The investment required is as follows
1) Maven (svnpubsub) I can grab the maven fluido skin [0] (which looks
OK) and have it up and running reasonably shortly.
2) Apache CMS, this requires someone writing the site however the
Sorry, meant to reply this, but totally fell out of my radar.
The reason why we are doing per-release and release-independent docs is
that there are some docs that document the code (tutorial, javadoc, etc),
and some docs that dont (the main site).
Having said that, I don't think keeping the
I started the Maven transition and can complete tomorrow.
Is everyone happy with the fluido skin that I mentioned?
If so then I will work to get it sorted out tomorrow.
Best
Lewis
On Wed, Dec 5, 2012 at 7:46 PM, Enis Söztutar enis@gmail.com wrote:
Sorry, meant to reply this, but totally
+1 for the Fluido skin. But this is just for the release-independent site,
right?
- Henry
On Wed, Dec 5, 2012 at 12:59 PM, Lewis John Mcgibbney
lewis.mcgibb...@gmail.com wrote:
I started the Maven transition and can complete tomorrow.
Is everyone happy with the fluido skin that I mentioned?
6 matches
Mail list logo
