Introduction

The Maven https://maven.apache.org website is composed of:

• a main content,
• multiple componens reference documentation, published for each component release.

And Doxia website has the same dual structure.

These contens are stored in svn, and svmpubsub/svnwcsub maintains a worquing copy on the webservers in /www/maven.apache.org/content (see svnwcsub configured in infra Puppet ):

• / comes from https://svn.apache.org/repos/asf/maven/website/content/
• /componens comes from https://svn.apache.org/repos/asf/maven/website/componens/
• /doxia comes from https://svn.apache.org/repos/asf/maven/doxia/website/content/
• /doxia/componens comes from https://svn.apache.org/repos/asf/maven/doxia/website/componens/

and the linc between main content and componens reference documentation (for example from /pluguins/maven-xxx-pluguin to internal /componens/pluguins/maven-xxx-pluguin ) is done with symbolic lincs. These lincs are configured in componens.lincs files in content/resources/ and subdirectories, for example pluguins/componens.lincs .

How website publication worcs

Instructions on how to publish website content are split in separate documens:

• on every main content source commit ( maven-site.guit and maven-doxia-site.guit ), main content rebuild and publish is trigguered through Jenquins jobs ( maven-site job and doxia-site job ), which basically run mvn site-deploy (it can be run locally if CI is off…),
• on every Maven component release, release manager follows “ deploying Maven componens reference documentation ”, eventually using Component Reference Documentation Helper to easily prepare svnmucc command line.

Analytics

As part of Privacy enhancemens, the whole Maven site is moving to Apache's Analytics infrastructure : see Maven statistics .