diff --git a/doc/boinc_dev.php b/doc/boinc_dev.php
index a6fe0681b9..25b15f6088 100644
--- a/doc/boinc_dev.php
+++ b/doc/boinc_dev.php
@@ -1,42 +1,26 @@
 <?php
-   require_once("docutil.php");
-   page_head("Development and debugging");
+require_once("docutil.php");
+page_head("Development and debugging");
 
-   echo "
-<p>
-<h2>Source code</h2>
-You can get the BOINC source code in several ways:
-<ul>
-<li>
-<a href=source/>Download</a> a tarball or .zip file
-(generated nightly).
-<li>
-Browse the CVS repository via a
-<a href=http://boinc.berkeley.edu/cgi-bin/cvsweb.cgi/>web-based interface</a>.
-<li>
-Access the CVS repository directly, e.g. with a command like
-<pre>
-cvs -d :pserver:anonymous@alien.ssl.berkeley.edu:/home/cvs/cvsroot checkout boinc
-<pre>
-</ul>
-<p>
-Source code for a typical BOINC application,
-SETI@home, is <a href=http://boinc.berkeley.edu/seti_source/>here</a>.
+echo "
 <p>
 If you are an experienced C++ system programmer you may be able
 to help us maintain and enhance BOINC.
 In any case, you are welcome to browse the source code and
 give us feedback.
 <p>
-You should understand exactly how BOINC is supposed to work
+You should understand how BOINC works
 (for both <a href=participate.php>participants</a>
-and <a href=create_project.php>developers</a>)
+and <a href=create_project.php>projects</a>)
 before getting into the source code.
 
-<h2>Bug database</h2>
 <p>
-<a href=http://setiathome.berkeley.edu/taskbase>View database of bugs and feature requests</a>
+Read about:
+<ul>
+<li> <a href=compile.php>Compiling BOINC software</a>
+</ul>
 <p>
+Various implementation notes:
 <h2>Core client</h2>
 <ul>
 <li> <a href=client_files.php>File structure</a>
@@ -81,6 +65,6 @@ between two versions of an executable</a>.
 </ul>
 
 ";
-   page_tail();
+page_tail();
 ?>
 
diff --git a/doc/build.php b/doc/build.php
index e1511ec71e..fbdbac016e 100644
--- a/doc/build.php
+++ b/doc/build.php
@@ -23,8 +23,10 @@ Other Unix-like systems should work without too much configuration.
 <tr>
     <td>GNU tools:
         <br>GCC 3.0.4+
-        <br>autoconf 2.59+
-        <br>automake 1.9.3+
+        <br> <a href=http://www.gnu.org/software/autoconf/>
+        autoconf 2.59+</a>
+        <br> <a href=http://www.gnu.org/software/automake/automake.html>
+        automake 1.9.3+</a>
     </td>
     <td>X</td>
     <td>X</td>
diff --git a/doc/community.php b/doc/community.php
index 66265cf14f..2e6c37cd43 100644
--- a/doc/community.php
+++ b/doc/community.php
@@ -52,39 +52,12 @@ list_item("<a href=http://www.ssl.berkeley.edu/mailman/listinfo/boinc_opt>boinc_
     "For people porting and optimizing BOINC applications."
 );
 list_end();
+
 echo "
-<h2>Getting source code</h2>
-<p>
-At any given point there are two different versions
-of the BOINC source code (maintained as separate CVS projects):
+<h2>Programming</h2>
 <ul>
-<li> <b>boinc</b> is the development version.
-It may be unstable, and it may not be compatible with public BOINC projects.
-<li> <b>boinc_public</b> is the stable version.
-It generally is the version being used
-(on both client and server) by public BOINC projects.
+<li> <a href=compile.php>Compile BOINC software</a>
 </ul>
-You can get the BOINC source code in several ways:
-<ul>
-<li>
-<a href=source/>Download</a> a tarball or .zip file
-(generated nightly).
-<li>
-Browse the CVS repository via a
-<a href=http://boinc.berkeley.edu/cgi-bin/cvsweb.cgi/>web-based interface</a>.
-<li>
-Access the CVS repository directly, e.g. with a command like
-<pre>
-cvs -d :pserver:anonymous@alien.ssl.berkeley.edu:/home/cvs/cvsroot checkout boinc
-<pre>
-</ul>
-<p>
-Source code for a typical BOINC application,
-SETI@home, is <a href=http://boinc.berkeley.edu/seti_source/>here</a>.
-<h2>Bug database</h2>
-<p>
-You can browse the BOINC
-<a href=http://setiathome.ssl.berkeley.edu/taskbase/database.cgi>bug-tracking database</a>.
 
 <h2>News feeds</h2>
 <p>
diff --git a/doc/compile.php b/doc/compile.php
new file mode 100644
index 0000000000..cb946f4355
--- /dev/null
+++ b/doc/compile.php
@@ -0,0 +1,20 @@
+<?php
+require_once("docutil.php");
+
+page_head("Compiling BOINC software");
+echo "
+<ul>
+<li> <a href=source_code.php>Getting the source code</a>
+<li> <a href=build.php>Software prerequisites</a>
+<li> <a href=road_map.php>Road map of the BOINC software</a>
+<li> <a href=build_system.php>Build system</a>
+<li> <a href=build_server.php>Building server components</a>
+<li> <a href=build_client.php>Building the core client</a>
+<li> <a href=test.php>Test applications and scripts</a>
+<li> <a href=http://noether.vassar.edu/~myers/help/boinc/boinc-on-redhat.html>Compiling BOINC on Red Hat Linux 7.x</a> (by Eric Myers)
+<li> <a href=ssl_build.txt>Build instructions for SSL (Secure Socket Layer) client</a>
+</ul>
+";
+page_tail();
+
+?>
diff --git a/doc/create_project.php b/doc/create_project.php
index f57d9d3a28..207926c627 100644
--- a/doc/create_project.php
+++ b/doc/create_project.php
@@ -52,24 +52,6 @@ How to develop or port an application program for use with BOINC.
 <li><a href=myers.txt>App development cookbook</a> (courtesy of Eric Myers from Vassar)
 </ul>
 
-<font size=+1><b>
-Compiling BOINC software
-</b></font>
-<br> &nbsp; &nbsp; &nbsp;
-<font size=-1>
-How to configure and compile the BOINC software.
-</font>
-<ul>
-<li> <a href=build.php>Software prerequisites</a>
-<li> <a href=road_map.php>Road map of the BOINC software</a>
-<li> <a href=build_system.php>Build system</a>
-<li> <a href=build_server.php>Building server components</a>
-<li> <a href=build_client.php>Building the core client</a>
-<li> <a href=test.php>Test applications and scripts</a>
-<li> <a href=http://noether.vassar.edu/~myers/help/boinc/boinc-on-redhat.html>Compiling BOINC on Red Hat Linux 7.x</a> (by Eric Myers)
-<li> <a href=ssl_build.txt>Build instructions for SSL (Secure Socket Layer) client</a>
-</ul>
-
 <font size=+1><b>
 Creating a BOINC project
 </b></font>
@@ -78,6 +60,7 @@ Creating a BOINC project
 The components of a BOINC project, and how to create them.
 </font>
 <ul>
+<li> <a href=compile.php>Compile BOINC Software</a>
 <li> <a href=project_cookbook.php>Project creation cookbook</a>
 <li> <a href=server_components.php>What is a project?</a>
 <li> <a href=database.php>The BOINC database</a>
diff --git a/doc/source_code.php b/doc/source_code.php
new file mode 100644
index 0000000000..bff2683872
--- /dev/null
+++ b/doc/source_code.php
@@ -0,0 +1,46 @@
+<?php
+require_once("docutil.php");
+
+page_head("Getting source code");
+echo "
+
+<h2>CVS branches</h2>
+<p>
+There are two different versions of the BOINC source code
+(maintained as separate CVS projects):
+<ul>
+<li> <b>boinc</b> is the development version.
+The client code may be unstable
+and may be incompatible with public BOINC projects.
+The server code is almost always stable - use this if you
+are setting up a server.
+<li> <b>boinc_public</b> is the stable version of the client,
+used for making bug-fix releases.
+</ul>
+<h2>Source code</h2>
+You can get the BOINC source code in several ways:
+<ul>
+<li>
+Access the CVS repository directly, e.g. with a command like
+<pre>
+cvs -d :pserver:anonymous@alien.ssl.berkeley.edu:/home/cvs/cvsroot checkout boinc
+</pre>
+<li>
+Browse the CVS repository via a
+<a href=http://boinc.berkeley.edu/cgi-bin/cvsweb.cgi/>web-based interface</a>.
+<li>
+<a href=source/>Download</a> a tarball or .zip file
+(generated nightly).
+</ul>
+<p>
+Source code for a typical BOINC application,
+SETI@home, is <a href=http://setiweb.ssl.berkeley.edu/sah/sah_porting.php>here</a>.
+<h2>Bug database</h2>
+<p>
+<a href=http://setiathome.berkeley.edu/taskbase>View database of bugs and feature requests</a>
+<p>
+
+";
+
+page_tail();
+?>
diff --git a/doc/stats_rpc.php b/doc/stats_rpc.php
new file mode 100644
index 0000000000..802ea30bd9
--- /dev/null
+++ b/doc/stats_rpc.php
@@ -0,0 +1,30 @@
+<?php
+
+require_once("docutil.php");
+
+page_head("Web services for statistics sites");
+
+echo "
+The following 'web service' is available for statistics sites.
+";
+list_start();
+list_item("URL", "WEBSITE_URL/verify_cpid.php?authenticator=x&cpid=y");
+list_item("inputs", "x=authenticator (also known as 'account key');
+    <br> y=user cross-project ID, as listed in XML stats file
+    or user account page"
+);
+list_item("output",
+    "XML: enclosing &lt;reply> tag, and either
+    <ul>
+    <li> &lt;success>&lt;/success>
+    if authenticator is correct for that user
+    (viewed in a browser, this may be displayed as &lt;success/>).
+    <li> &lt;error>error_message&lt;/error>
+    otherwise.
+    </ul>
+    "
+);
+list_end();
+
+page_tail();
+?>
diff --git a/doc/test.php b/doc/test.php
index a86cf8d0a3..dabbf00731 100644
--- a/doc/test.php
+++ b/doc/test.php
@@ -1,6 +1,6 @@
 <?php
-   require_once("docutil.php");
-   page_head("Testing BOINC");
+require_once("docutil.php");
+page_head("Test framework for BOINC developers (not intended for general use)");
 echo "
 See the section on testing in <a href=build.php>Software Prerequisites</a>.
 Note that a web server with PHP is required for