have projects be able to contribute to the website, including docbook results, using maven site:deploy

Currently, updating the project website is a manual process. Automate this, with support for "staging" so the release review can include the website. The imagined release process would be:
1) Stage the release for a vote (using release:perform)
2) Simultaneously stage the website updates for review (using site:deploy)
3) When everything checks out, do some manual steps to finish release, and to copy the staged data on p.a.o/www/uima.apache.org to the right (non-staged) dir.

Suggested details:
1) use maven naming convention for website: site-url/artifactId/stuff.
2) for staging, replace with site-url/staging-version/artifactId/stuff with no links to it (reviewers type in the extra bit of url word by hand).

• Have the staging spot have mostly symbolic links or htaccess equivalents to the real data; only the changed items would be here as real data
• When review is complete, update the base by copying, or (insert better idea hear ).

3) To make the site:deploy goal work, change the output dir for docbx processing to target/site/d/html or pdf etc.
4) Have common POM info for the individual projects with target/site that are deploying
5) For docbook olink, update the site info for this proposed layout (new layer of dir = artifactId)
6) Update main website to link to new project pages and docbooks