On 11/24/2011 01:42 PM, Ioan Eugen Stan wrote:
Pe 23.11.2011 11:14, Felix Knecht a scris:
Hi
What should be the way of deploy new documentation to the James website
and where should this actual deployment goto?
The website navigation has been defined as
<snip />
but the in the distributionManagement section of the project pom.xml's
(trunk) are different url's defined like e.g.
- people.apache.org/www/james.apache.org/server/3/
- people.apache.org/www/james.apache.org/protocols/trunk/
- others are matching the navigation structure
Can all be fix in the way that deploying the generated site via "mvn
site-deploy" is going into the actual navigation place?
A full update of the whole James website could be (wishfully) done
then by
$ svn co http://svn.apache.org/repos/asf/james/current current-james
$ cd current-james
$ mvn clean site-deploy
wdot?
Regards
Felix
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
To answer Felix's question: I don't know, but something should be possible.
I discussed the website state with Eric when we met at ApacheCon and
agreed that we can do better, but I'm still a noob regarding how things
are organized. I think there is room for improvement and we can make the
site more user-friendly.
One thing that I noticed is that we have no consistency in and the
website is kind of crowded. Maybe we can switch to something template
based?
Do you have already something in mind?
When thinking about a redesign of the whole site it should also be
discussed if we want to stay the way it is done now having the
documentation content in in each project on it's own, create a
documentation project and merge all documention into ( both maven
generated documentation using xdoc and apt, deploy to p.a.o) or e.g. to
switch to the ASF Content Management System
(http://www.apache.org/dev/cms.html)
Regards
Felix
--
Ioan Eugen Stan
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
