Index: site-author/guides/sites.xml
===================================================================
--- site-author/guides/sites.xml	(revision 0)
+++ site-author/guides/sites.xml	(revision 0)
@@ -0,0 +1,66 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<document>
+  <properties>
+    <title>Podling Web Site Guide</title>
+  </properties>
+  <body>
+  <section>
+  <title>Purpose of this document</title>
+  <p>Podlings need to build a community in Apache in order to be accepted
+  as part of the Apache Software Foundation. One of the tools used to build
+  a community is the web site.</p>
+  </section>
+  
+  <section>
+  <title>Creating a Podling Web Site</title>
+  
+  <p>Apache Project Web Sites typically include several standard pages.
+  Each page is formatted with a navigation bar on the left and a project
+  standard header that includes the Incubator graphic.</p>
+  <p>The Web Site can be established during incubation, and migrated
+  after incubation to a permanent place in the TLP home.</p>
+  <ul><li>Project Home Page: the primary entry point to the site; contains 
+  project description, news, invitation to join the project.
+  </li><li>License Page: usually, the Apache License 2.0
+  </li><li>Downloads: many projects in incubation will release code,
+  and this page describes them and has links to the download pages
+  that redirect to Apache Mirror sites.
+  </li><li>Documentation: this page describes the project documentation,
+  including javadoc for Java projects; guides, tutorials, and links to
+  external documentation.
+  </li><li>Committers: a list of current committers on the project.
+  </li><li>Mailing Lists: there are several mailing lists that the
+  community might be interested in, and this page contains mailto: links
+  that allow easy subscription (and unsubscription) to any of them.
+  </li><li>FAQ: frequently asked questions are answered here.
+  </li><li>Road Map: if the project has a vision of future community
+  or development activities, the road map is published here.
+  </li><li>Source Code: links to the browsable source repository and
+  svn commands to check out the sources.
+  </li><li>Coding Standards: the coding standards for submitted code
+  by the community, along with a description of how strict the project
+  intends to be.
+  </li><li>Issue Tracking: links to the JIRA or other issue tracking
+  tool, possibly including frequently used filters for issue lists.
+  </li><li>Dependencies: other projects that this project depends on.
+  </li></ul>
+  </section>
+  
+  <section id="Tool">
+  <title>Web Site Generation Tool</title>
+  <p>The tool used to generate the web site is the choice of the
+  podling members. If you already have a tool that you are comfortable
+  with, you can continue to use it. If you do not, consider using
+  anakia, a tool that processes xml to produce html.</p>
+  <p>Regardless of which tool you use, the web site should be maintained
+  in the svn repository, and include the site generation tool as a binary
+  file. This simplifies the process of site generation and enables changes
+  to the site to be made by any committer. The generated site should also
+  be checked into svn. This allows the generated site to be relocated
+  to any part of the Apache site after incubation is complete.</p>
+  <p>Since the site is independent of the code, it should exist high in
+  the svn repository, e.g. parallel to the trunk of the source tree.</p>
+  </section>
+
+  </body>
+</document>
