Title: Manage your project web site
Notice:    Licensed to the Apache Software Foundation (ASF) under one
           or more contributor license agreements.  See the NOTICE file
           distributed with this work for additional information
           regarding copyright ownership.  The ASF licenses this file
           to you under the Apache License, Version 2.0 (the
           "License"); you may not use this file except in compliance
           with the License.  You may obtain a copy of the License at
           .
             http://www.apache.org/licenses/LICENSE-2.0
           .
           Unless required by applicable law or agreed to in writing,
           software distributed under the License is distributed on an
           "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
           KIND, either express or implied.  See the License for the
           specific language governing permissions and limitations
           under the License.

[TOC]

# Manage your project web site # {#intro}

Some notes moved from various documents - please help to
[enhance](infra-site.html)...

Please see the instructions of your project or ask the relevant dev@ list
for details on how and where your project web site is managed.

It is up to your projects how the website is maintained and what software
is used as long as it results in static files that can be served by the
our public web servers (limited support for .htaccess files and CGI
scripts is also available). The basic requirements for site management
are that only committers should be able to modify the site and that
notifications of all site changes should be sent to the relevant
project mailing lists.

The infrastructure team currently supports two main mechanisms for
publishing and maintaining project sites:

  - **svnpubsub**, which allows the static contents of a designated svn
    folder ([example](http://svn.apache.org/repos/asf/ant/site/ant/production/)) to automatically published
    as the project web site at `http://project.apache.org/`. The project
    team can use any site build mechanism it wants as long as the above
    requirements are met.
  - **Apache CMS**, which provides a simple browser-based user interface
    for editing, staging and publishing site content in Markdown, HTML
    or any other source format for which support has been added. See
    the [CMS reference](cmsref) and [adoption](cmsadoption) for more details. The Apache CMS
    uses svnpubsub as the underlying mechanism for publishing a site.

Some projects still use a deprecated site deployment system based
on periodic synchronization of static files from people.apache.org to
the live web servers. This mechanism will be discontinued at the end of
2012, by which time all projects should have migrated to one of the above
site publishing mechanisms.

# How do I preview my project website? # {#preview}

For svnpubsub sites, review the local files in your svn checkout before
committing them. The changes will be published immediately after you
commit them.

For CMS sites, just commit the changes (without "publish"-ing them) and browse
to `http://TLP.staging.apache.org/`.  (For example, [the staging version of
this page](http://www.staging.apache.org/dev/project-site).)

# Can I control the configuration of my project website? # {#configure}

Yes, the central config file allows you to use `.htaccess` files in your
website directories to control configuration. Of course, reading and
parsing an `.htaccess` file on each request can slow down the server, so
you should consider requesting an adjustment in the central config file for
permanent configuration changes.

# How does logging work? # {#logging}

Each day's error and access logs are kept in
`www.apache.org:/x1/logs/www/`. They are shuffled off each night to a
directory under `people.apache.org:/x1/logarchive/` and are then
periodically archived to other media.

No formal log analysis is performed, but you are free to grab the logs and
do whatever analysis you would like.

# Do project sites have to use [the CMS](cms)? # {#use-cms}

No.  It's recommended but not required.  ([More information](cms) and
[reference](cmsref) about the Apache CMS.)

# Do project sites have to use svnpubsub? # {#svnpubsub}

Yes.  Infrastructure will mandate transition to svnpubsub over this year.
(svnpubsub [requires](#intro) the generated site files to be in a Subversion
tree somewhere.  For CMS users this tree will be the CMS build output tree.)

# Can my project site use its own favicon?  We're seeing an Apache Feather. # {#feather}

Yes, just add a `favicon.ico` file to your site's root.  The feather is only
used for project sites that don't have a `favicon.ico` file.