diff --git a/www/html/index.html b/www/html/index.html
index 0cdd0cc9..e4769be2 100644
--- a/www/html/index.html
+++ b/www/html/index.html
@@ -1,19 +1,34 @@
 <h1>Project Overview</h1>
 <p>
-The SELinux Reference Policy project (refpolicy) is creating a complete SELinux policy as an alternative to the existing strict and targeted policies available from <a href="http://selinux.sf.net>selinux.sf.net</a>. What will set refpolicy apart?
+The SELinux Reference Policy project (refpolicy) is creating a complete SELinux policy as an alternative to the existing strict and targeted policies available from <a href="http://selinux.sf.net">http://selinux.sf.net</a>. Once complete this policy will be able to be used as the system policy for a variety of systems and used as the basis for creating other policies. Refpolicy is based on the current strict and targeted policies, but aims to accomplish many additional <a href="index.php?page=goals">goals</a>.
 </p>
+<br/>
+<p>
+Refpolicy is under active development, with support and full time development staff from <a href="http://www.tresys.com">Tresys Technology</a>. The first release is available from the <a href="index.php?page=download">download</a> page. This release is far from complete and is not usable as a drop in replacement for the existing policies. It is for interested policy developers and community members to examine and comment upon. The  <a href="index.php?page=status">status</a> page has more details on what is included in the current release. This project is just getting started and we are looking for policy developers interested in <a href="contributing.html">contributing</a>.
+</p>
+
+<h1>Project Goals</h1>
+<h2>Security</h2>
+<p>Security is the reason for existence for SELinux policies and must, therefore, always be the first priority. The security of operating systems and applications is often presented as a binary state: software is either secure or not secure. In reality, that view of security is inadequate. What is a fundamental security flaw on one system might be the acceptable, or even the primary functionality, of another. The challenge for a system policies like the current strict or targeted policy and refpolicy is to support all of these differring security goals. To accomplish this refpolicy will provide:
+</p>
+
+<ul>
+	<li><b>Security Goals:</b> clearly stated security goals will for each component of the policy. This will allow policy developers to determine if a given component meets their security needs.</li>
+	<LI><b>Flexible Base Policy:</b> a base policy that protects the basic operating system and serves as a foundation to the rest of the policy. This base policy should be able to support a variety of application policies with differing security goals.</LI>
+	<li><b>Application Policy Variations:</b> application policy variations that make different security tradeoffs. For example, two apache policies might be created. One that is for serving read-only, static content that is severely restricted and another that is appropriate for dynamic content.</li>
+	<li><b>Configuration Tools:</b> configuration tools that allow the policy developer to make important security decisions including defining roles, configuring networking, and trading legacy compatibility for increased security.</li>
+	<li><b>Multi-Level Security</b>: MLS will be supported out-of-the-box without requiring destructive changes to the policy. It will be possible to compile and MLS and non-MLS policy from the same policy files by switching a configuration option.</li>
+
+</ul>
+<h2>Usability and Documentation</h2>
 <ul>
 	<li>Security: refpolicy has a mandate to develop security goals that are clear and rigoursly applied</li>
 	<li>Usability: refpolicy will be easier to understand and use.</li>
 	<li>Documentation: refpolicy has a structure that makes it possible to create in-depth documentation.
 	<li>Flexibility: refpolicy will support source, loadable, and MLS modules with simple configuration.</li>
 </ul>
-<p>
-Refpolicy is under active development, with support and full time development staff from <a href="http://www.tresys.com">Tresys Technology</a>. We are looking for policy developers interested in <a href="contributing.html">contributing</a>.
-</p>
-<h2>Background</h2>
 
-<h2>Roadmap</h2>
+<h1>Roadmap</h1>
 
 <table border="1" cellspacing="0" cellpadding="3">
 <tr>
@@ -42,3 +57,4 @@ Refpolicy is under active development, with support and full time development st
 <tr>
 <td>0.6</td><td>December 2005</td><td>Additional modules and module variations</td>
 </tr>
+
diff --git a/www/html/menu.html b/www/html/menu.html
index 38fa64bd..c0812377 100644
--- a/www/html/menu.html
+++ b/www/html/menu.html
@@ -1,7 +1,9 @@
-   <a href="index.php">Reference Policy</a><br />
-   <a href="index.php?page=documentation">Documentation</a> - <br />
-   <a href="index.php?page=status">Status</a> - <br />
-   <a href="index.php?page=contributing">Contributing</a> - <br />
-   <a href="http://sourceforge.net/project/showfiles.php?group_id=???">Download</a> - <br />
-   <a href="http://sourceforge.net"><IMG src="http://sourceforge.net/sflogo.php?group_id=???&amp;type=1" w
-idth="88" height="31" border="0" alt="SourceForge.net Logo" /></A>
+   <a href="index.php">Reference Policy Home</a><br />
+   <a href="index.php?page=documentation">Documentation</a><br/>
+   - <a href="index.php?page=goals">Goals and Roadmap</a><br/>
+   - <a href="index.php?page=goals">Getting started</a><br/>
+   <a href="index.php?page=status">Status</a><br />
+   <a href="index.php?page=contributing">Contributing</a><br />
+   <a href="http://sourceforge.net/project/showfiles.php?group_id=???">Download</a><br />
+   <!--<IMG src="http://sourceforge.net/sflogo.php?group_id=???&amp;type=1" w
+idth="88" height="31" border="0" alt="SourceForge.net Logo" /></A>-->
diff --git a/www/index.php b/www/index.php
index 1d7721de..0297ccb0 100644
--- a/www/index.php
+++ b/www/index.php
@@ -1,10 +1,11 @@
 <?php
   require_once ("./libs.inc.php");
  
-  if (!$_GET['page'])
-	$page == "index";
-  else 
-	$page == $_GET['page'];
+  $page = "index";
+  if ($_GET['page'])
+	$page = $_GET['page'];
+  
+  #echo "page is $page";
 /* Meh! this is a stupid hack because the stupid template system 
    doesn't like the { } in policy statements */
   $smarty->left_delimiter = '<!--{';
diff --git a/www/libs.inc.php b/www/libs.inc.php
index 1d1e3d0e..fb708755 100644
--- a/www/libs.inc.php
+++ b/www/libs.inc.php
@@ -9,12 +9,12 @@
 
   require_once (SMARTY_DIR."Smarty.class.php");
   $smarty = new Smarty;
-  $smarty->compile_dir = "/home/groups/s/se/serefpolicy/t_c";
+  $smarty->compile_dir = "/home/kmacmillan/public_html/t_c";
+  #$smarty->compile_dir = "/home/groups/s/se/serefpolicy/t_c";
   $smarty->template_dir = "$fixpath/html";
 
   $smarty->assign("border", "0");
 
-/*
   $menu = array (
 	array("name" => "Home", "url" => "index.php?page=home"),
 	array("name" => "Modules", "url" => "index.php?page=modules"),
@@ -22,8 +22,8 @@
 	array("name" => "Tutorial", "url"  => "index.php?page=howto")
   );
 
+
   $smarty->assign("menuitems", $menu);
-*/
 
 
   
diff --git a/www/publish.sh b/www/publish.sh
index 1e525f61..288f8f9c 100755
--- a/www/publish.sh
+++ b/www/publish.sh
@@ -2,4 +2,4 @@
 
 # This will 'publish' the reference policy website.
 
-rsync -r . shell.sf.net:/home/groups/s/se/serefpolicy/htdocs
+rsync -r . shell.sf.net:/home/groups/s/se/serefpolicy/htdocs/pre
diff --git a/www/style.css b/www/style.css
index 9f1b9b16..1215b890 100644
--- a/www/style.css
+++ b/www/style.css
@@ -11,7 +11,7 @@ h1 {
 	font-size:28px;
 	line-height:28px;
 	font-weight:900;
-	color:#ccc;
+	color:#aaa;
 	}
 h2 {
 	font-size:100%;
@@ -26,7 +26,7 @@ li {
 	font:11px/20px verdana, arial, helvetica, sans-serif;
 	margin:0px 0px 0px 0px;
 	padding:0px;
-	}
+}
 p {
 	/* normal */
 	font:11px/20px verdana, arial, helvetica, sans-serif;
@@ -138,7 +138,7 @@ body>#Header {height:14px;}
 	background-color:#eee;
 	border:1px dashed #999;
 	line-height:17px;
-	text-align:right;	
+	text-align:left;	
 	voice-family: "\"}\"";
 	voice-family:inherit;
 	width:160px;