More clean up.

Remove unused files.
diff --git a/main.html b/main.html
deleted file mode 100644
index 3585780..0000000
--- a/main.html
+++ /dev/null
@@ -1,8 +0,0 @@
-<html>
-   <head>
-      <meta http-equiv="refresh" content="5; url=index.php" />
-   </head>
-   <body>
-      <a href="index.php">This page has moved. Please update your links and bookmarks.</a>
-   </body>
-</html>
\ No newline at end of file
diff --git a/nav.html b/nav.html
deleted file mode 100644
index 9cb3724..0000000
--- a/nav.html
+++ /dev/null
@@ -1,33 +0,0 @@
-<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
-<html>
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<title>Eclipse Technology navigator</title>
-<base target="main">
-<link rel="stylesheet" href="../nav_style.css" type="text/css">
-</head>
-<body text="#000000" bgcolor="#6699CC" link="#FFFFCC" vlink="#551A8B" alink="#FF0000">
-<table BORDER=0 CELLSPACING=0 CELLPADDING=0 COLS=1 WIDTH="100%" BGCOLOR="#90C8FF" height="63" >
-  <tr> 
-    <td VALIGN=CENTER HEIGHT="21" BGCOLOR="#0080C0">&nbsp;<a href="../technology/index.html" target="_top" class="navhead">eclipse 
-      technology</a></td>
-  </tr>
-  
-  <tr valign=CENTER> 
-    <td valign=CENTER height="21"> 
-      <p>&nbsp; <a href="http://www.eclipse.org/proposals/" class="nav" target="_top">Proposals</a></p>
-    </td>
-  </tr>
-  <tr> 
-    <td BGCOLOR="#CFFFFF"><img SRC="../projects/images/c.gif" height=1 width=1></td>
-  </tr>
-    <tr valign=CENTER> 
-    <td valign=CENTER height="21"> 
-      <p>&nbsp; <a href="research.html" class="nav">Research &nbsp;&nbsp;Community</a></p>
-    </td>
-  </tr>
-  <tr> 
-    <td BGCOLOR="#CFFFFF"><img SRC="../projects/images/c.gif" height=1 width=1></td>
-  </tr>
-</table>
-</body>
\ No newline at end of file
diff --git a/new-research-charter.html b/new-research-charter.html
deleted file mode 100644
index 3b62449..0000000
--- a/new-research-charter.html
+++ /dev/null
@@ -1,107 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html>
-<head>
-<title>Eclipse Standard Top-Level Charter v1.0</title>
-<link type="text/css" rel="stylesheet" href="
-http://www.eclipse.org/default_style.css">
-<title>Eclipse Research Project Top-Level</title>
-</head>
-<body text="#000000" bgcolor="#ffffff" link="#0000EE" vlink="
-#551A8B" alink="#ff0000">
-
-<table cellspacing="5" cellpadding="2" width="100%" border="0">
-
-<tbody>
-<tr>
-<td valign="top" align="left" bgcolor="#0080C0" colspan="3">
-<b><span style="font-size:10.0pt;font-family:Arial;
-mso-fareast-font-family:&quot;Times New Roman&quot;;color:white;mso-ansi-language:EN-US;
-mso-fareast-language:KO;mso-bidi-language:AR-SA">The Eclipse Research Project –
-Top-Level Project Charter – The Eclipse Foundation</span></b></td>
-</tr>
-
-<tr>
-<td colspan="3">
-<p><b>Overview<br>
-</b>The Eclipse Research Top Level Project (the &quot;Eclipse Research
-Project&quot;) is an open source software research project, which encapsulates
-two related activity streams, each of which is based on or uses the Eclipse
-Platform and/or code from other Eclipse Top Line Projects:&nbsp;</p>
-<ol>
-  <li>
-    <p>research projects sponsored by universities, public and private research
-    institutes, and other exploratory investigations (&quot;Research
-    Stream&quot;);&nbsp;</p>
-  </li>
-  <li>
-    <p>development of educational materials, teaching aids and courseware
-    (&quot;Education Stream&quot;)</p>
-  </li>
-</ol>
-<p><b>Mission</b><br>
-The mission of the Eclipse Research Project is to foster greater community
-awareness and understanding of Eclipse (Education Stream), and to encourage the
-use of Eclipse software as a platform for research, especially in domains such
-as programming languages, tools, and development environments that are relevant
-to other Eclipse Top Line Projects (Research Stream). By so doing, the Eclipse
-Research Project will create opportunities for researchers, academics, and
-educators to play a significant role within the Eclipse community.</p>
-<p><b>Scope</b><br>
-The scope of the Eclipse Research Project will encompass a wide variety of small
-projects, rather than a few large ones. While anticipating enormous diversity in
-the content of these activities, from a process-oriented viewpoint they will all
-share important common characteristics, which argues for a common approach to
-management:</p>
-<ul>
-  <li>Focus on pre-competitive development and research</li>
-  <li>Use of informal development processes</li>
-  <li>Fluid project tracking due to frequent plan changes</li>
-  <li>Flexible milestones which adapt based on partial results</li>
-  <li>Small teams</li>
-  <li>Resource commitments tentative, due to volunteer labor or lack of sponsor
-    funding</li>
-  <li>Development often cross-cuts the scope of several other Eclipse Foundation
-    Projects</li>
-  <li>Limited lifespan due to intent to explore and validate an idea, then
-    graduate or disband</li>
-</ul>
-<p>The Eclipse Research Project serves as a single point of focus for such
-teams, and provides them with a home within the Eclipse community, to encourage
-communication, and where appropriate, collaboration and coordination. Providing
-common management for these Projects facilitates maximum sharing and creation of
-common components, and avoids redundant efforts. In many cases successful
-Research Projects will evolve into incubators in Eclipse Technology Project. </p>
-<p>The Education Stream plays a vital role in promoting the use of the Eclipse
-Platform. By making high quality educational materials freely available, we both
-enable self-education by individual users, and facilitate the incorporation of
-Eclipse-related materials into university courses and commercial educational
-offerings.</p>
-<p><b>Other Terms<br>
-</b>This Charter inherits all terms not otherwise defined herein from the &quot;<a href="http://www.eclipse.org/org/processes/Eclipse_Standard_TopLevel_Charter_v1.0.html">Eclipse
-Standard Charter v1.0</a>&quot;. This includes, but is not limited to, sections
-on the Program Management Committee, Roles, Project Organization, The
-Development Process, and Licensing.</p>
-<p><b>Project Management Committee <br>
-</b>Changes from the &quot;<a href="http://www.eclipse.org/org/processes/Eclipse_Standard_TopLevel_Charter_v1.0.html">Eclipse
-Standard Charter v1.0</a>&quot; are:</p>
-<ul>
-  <li>Providing the leadership and vision to guide the Project's overall
-    direction in a manner consistent with the <strike>Eclipse Foundation
-    Architectural Roadmap</strike> Eclipse Foundation's goals. </li>
-</ul>
-<p><b>The Development Process <br>
-</b>Changes from the &quot;<a href="http://www.eclipse.org/org/processes/Eclipse_Standard_TopLevel_Charter_v1.0.html">Eclipse
-Standard Charter v1.0</a>&quot; are: </p>
-<p>Research projects typically do not have as well-defined development plans as
-product projects do. However, it is still important that Projects under the
-Research Top-Level Project have a defined and publicly available release plan so
-as to help interested parties track the progress of the research.
-</td>
-</tr>
-</tbody>
-</table>
-
-</body>
-</html>
-
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
diff --git a/new-technology-charter.html b/new-technology-charter.html
deleted file mode 100644
index 3bb701a..0000000
--- a/new-technology-charter.html
+++ /dev/null
@@ -1,87 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html>
-<head>
-<title>Eclipse Technology Project Top-Level Charter</title>
-<link type="text/css" rel="stylesheet" href="
-http://www.eclipse.org/default_style.css">
-<title>Eclipse Research Project Top-Level</title>
-</head>
-<body text="#000000" bgcolor="#ffffff" link="#0000EE" vlink="
-#551A8B" alink="#ff0000">
-
-<table cellspacing="5" cellpadding="2" width="100%" border="0">
-
-<tbody>
-<tr>
-<td valign="top" align="left" bgcolor="#0080C0" colspan="3">
-<b><span style="font-size:10.0pt;font-family:Arial;
-mso-fareast-font-family:&quot;Times New Roman&quot;;color:white;mso-ansi-language:EN-US;
-mso-fareast-language:KO;mso-bidi-language:AR-SA">The Eclipse Technology Project –
-Top-Level Project Charter – The Eclipse Foundation</span></b></td>
-</tr>
-
-<tr>
-<td colspan="3">
-<p><b>Overview<br>
-</b>The Eclipse Technology Top Level Project (the &quot;Eclipse Technology
-Project&quot;) is an open source software project for the incubation of
-small-scale, innovative platform and tools projects.</p>
-<p><b>Mission</b><br>
-The mission of the Eclipse Technology Project is to provide a temporary home
-within the Eclipse Foundation for small, newer, early adopter-type Projects
-which add new capabilities to the Eclipse software base. The Eclipse Technology
-Project is intended to provide the open source community with a lighter weight
-alternative to the larger scale, more structured development activities carried
-out by other PMCs until the new projects are ready to join their destination PMC.</p>
-<p><b>Scope</b><br>
-The scope of the Eclipse Technology Project will encompass a wide variety of
-small early-stage Projects, rather than a few large ones. While anticipating
-enormous diversity in the content of these activities, from a process-oriented
-viewpoint they will all share important common characteristics, which argues for
-a common management envelope:</p>
-<ul>
-  <li>Use of lighter weight, but still formal development processes&nbsp;</li>
-  <li>Fluid Project tracking due to frequent plan changes&nbsp;</li>
-  <li>Flexible milestones which adapt based on partial results&nbsp;</li>
-  <li>Small teams, relatively inexperienced in open-source software
-    development&nbsp;</li>
-  <li>Definitive plans to move to mature the project and then move it to the
-    appropriate Top-Level Project.</li>
-</ul>
-<p>The Eclipse Technology Project serves as a single point of focus for such
-teams, and provides them with a home within the Eclipse community, to encourage
-communication, and where appropriate, collaboration and coordination. Providing
-common management for these Projects facilitates maximum sharing and creation of
-common components, and avoids redundant efforts. The goal of successful projects
-is to migrate to other PMCs, either by merging into an existing Project, or by
-forming the basis for a new one.</p>
-<p><b>Other Terms<br>
-</b>This Charter inherits all terms not otherwise defined herein from the &quot;<a href="http://www.eclipse.org/org/processes/Eclipse_Standard_TopLevel_Charter_v1.0.html">Eclipse
-Standard Charter v1.0</a>&quot;. This includes, but is not limited to, sections
-on the Program Management Committee, Roles, Project Organization, The
-Development Process, and Licensing.</p>
-<p><b>Project Management Committee <br>
-</b>Changes from the &quot;<a href="http://www.eclipse.org/org/processes/Eclipse_Standard_TopLevel_Charter_v1.0.html">Eclipse
-Standard Charter v1.0</a>&quot; are:</p>
-<ul>
-  <li>Providing the leadership and vision to guide the Project's overall
-    direction in a manner consistent with the <strike>Eclipse Foundation
-    Architectural Roadmap</strike> Eclipse Foundation's goals. </li>
-</ul>
-<p><b>Projects <br>
-</b>Changes from the &quot;<a href="http://www.eclipse.org/org/processes/Eclipse_Standard_TopLevel_Charter_v1.0.html">Eclipse
-Standard Charter v1.0</a>&quot; are: </p>
-<p>The work under this Top Level Project is further organized into Projects. New
-Projects must be consistent with the mission of the Top Level Project, <b>have
-an explicit plan for reaching their destination top-level project, </b>be
-recommended by the PMC, and confirmed by the EMO. Projects can be discontinued
-by decision of the Board.
-</td>
-</tr>
-</tbody>
-</table>
-
-</body>
-</html>
-
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
diff --git a/standard-project-nav.class.php b/standard-project-nav.class.php
deleted file mode 100644
index 21b0482..0000000
--- a/standard-project-nav.class.php
+++ /dev/null
@@ -1,40 +0,0 @@
-<?php
-class StandardProjectNav {
-	// About
-	var $description;
-	var $project_plan;
-	var $leadership;
-	var $committers;
-	var $contributors;
-	// Downloads
-	var $downloads;
-	// Getting Started
-	var $getting_started;
-	// Development
-	var $development_plan;
-	var $mailing_lists;
-	var $cvs;
-	var $bugs;
-	
-	function generate_nav( ) {
-		// need to turn off the standard four items to replace with these
-		// need to have blank URLs render in gray
-		$Nav->addCustomNav("Test Test", "test.html", "", 1);
-		echo "in generate nav" . $Nav . "nav";
-		$Nav->addCustomNav("Description", $description, "", 1);
-			$Nav->addCustomNav("Project Plan", $project_plan, "", 2);
-			$Nav->addCustomNav("Leadership", $leadership, "", 2);
-			$Nav->addCustomNav("Committers", $committers, "", 2);
-			$Nav->addCustomNav("Contributors", $contributors, "", 2);
-		$Nav->addCustomNav("Downloads", $downloads, "", 1);
-		$Nav->addCustomNav("Getting Started", $getting_started, "", 1);
-		$Nav->addCustomNav("Development", $development, "", 1);
-			$Nav->addCustomNav("Project Plan", $development_plan, "", 2);
-			$Nav->addCustomNav("Mailing Lists", $mailing_lists, "", 2);
-			$Nav->addCustomNav("CVS", $cvs, "", 2);
-			$Nav->addCustomNav("Bugs", $bugs, "", 2);
-	}
-}
-
-$Nav->addCustomNav("Test Test 3", "test.html", "", 1);
-?>
diff --git a/test b/test
deleted file mode 100644
index 7109fcf..0000000
--- a/test
+++ /dev/null
@@ -1 +0,0 @@
-asasasasasdfasdfasdfasdf
\ No newline at end of file