Modifying site landing page. Also the site now lives under the /genome context

7 files changed, 25 insertions, 8 deletions

diff --git a/genome-site.spec b/genome-site.spec
index 2c3176f..5f8806c 100644
--- a/genome-site.spec
+++ b/genome-site.spec
@@ -25,14 +25,17 @@ Basic web site for genome
 rm -rf $RPM_BUILD_ROOT
 
 mkdir -p $RPM_BUILD_ROOT/var/www/genome
+mkdir -p $RPM_BUILD_ROOT/etc/httpd/conf.d
 
-cp -r genome-site/content $RPM_BUILD_ROOT/var/www/genome
+cp -r genome-site/content/* $RPM_BUILD_ROOT/var/www/genome
+cp genome.conf $RPM_BUILD_ROOT/etc/httpd/conf.d
 
 %clean
 rm -rf $RPM_BUILD_ROOT
 
 %files
 %defattr(755,root,root)
+/etc/httpd/conf.d/genome.conf
 /var/www/genome
 
 %changelog
diff --git a/genome-site/content/index.php b/genome-site/content/index.php
index 221bb34..8d09f2f 100644
--- a/genome-site/content/index.php
+++ b/genome-site/content/index.php
@@ -6,14 +6,16 @@
   <div id="content">
       <div id="inner">
 		<h1>Genome: IT Evolved.</h1>
-		<p>The genome is fundamental to the reliable encoding and transfer of both genetic code and data. As the project name suggests, Genome is the equivalence for software systems. The project started formally in early 2008 though the origins can be traced back several years prior to real struggles within Red Hat IT developing and deploying software systems.<br/><br/>
+		<p>Genome is both a set of light weight tools and framework for introducing new server configurations and replicating those server configurations from one environment to another.</p>  
 
-While it may not be the perfect analogy, it is indeed fitting to say that hereditary information is stored within every IT organization. The truth is software systems, like species, face extinction through poor replication of this information. Sadly, the knowledge that is required to maintain and reproduce complex systems often only lives in the form of tangled configuration scripts or, worse still, only in the minds of consulting domain experts. Transfering knowledge in such manners is practically a recipe for building legacy systems.<br/><br/>
+		<p>Changing systems manually in production can be very dangerous. Making changes in a completely different environment then installing those changes in production can be equally risky.  Using Genome to spin up an identical copy of a production system can help mitigate the risk of change.</p>
 
-Taking the biological analogy a little further, briefly imagine a world in which generations of genetic information had to be manually replicated by any number of people. Now try to imagine a different world in which genetic information could only be copied exactly, that is to say, diversity is altogether unattainable. Genome aims to solve both of these problems for IT; that of reproducing exceedingly complicated systems in a world where heterogeneity is always more of the rule than the exception.<br/><br/>
+		<p>Large teams of developers struggle to move code and configuration into production without having a staging area that reflects the true state of production. The Genome framework can be used to manage the delta between staging and development environments by using consistent provisioning and configuration.</p>
 
-As you begin to tackle these problems for your organization it cannot be emphasized enough that the collaboration amongst teams enabled by Genome is more important than any particular tool implementation. Feel free to <i>mutate</i> Genome into any shape or form to solve your problems. The truth is, we readily await your patches and enjoy seeing the best ideas rise to the top.</p>
-		</p>
+		<p>Once a system has been installed into production, it's important to maintain that system over time.  This can be very difficult if there is no reliable way to re-create that system outside of the environment it's installed in.  Using Genome can provide visibility to both system administrators and developers into how systems are deployed.  If you create configuration manifests for a system, you can reliably rebuild the system in an isolated environment, or you can even use it to rebuild the system in production.</p>
+
+		<p>In addition to cataloging system configurations, Genome also provides a basic cloud-based computing solution.  The Genome Cloud is a service that can deploy virtual machines across 1-to-many physical hosts.  Genome wires together some of the best open source infrastructure management projects.</p>
+		<p><img src="./styles/genome_stack.png" border="0" alt="Genome uses cobbler, puppet, func, kvm, and xen" /></p>
      </div>  
   </div>
 </div>
diff --git a/genome-site/content/menu.php b/genome-site/content/menu.php
index e15ade8..15e8069 100644
--- a/genome-site/content/menu.php
+++ b/genome-site/content/menu.php
@@ -20,7 +20,7 @@
 	<li><div>         <a class="<?php echo $home ?>" title="Home" href="./index.php">Home</a>        </div></li>
 	<li><div>         <a class="<?php echo $download ?>" title="Get the latest releases" href="./download.php?trk=g">Download</a>        </div></li>
 	<li><div>         <a class="<?php echo $contribute ?>" title="Information about design/development process" href="./contribute.php?trk=c">Contribute</a>      </div></li>
-	<li><div>         <a class="inactive" title="Project documentation" href="docs/genome">Documentation</a>       </div></li>
+	<li><div>         <a class="inactive" title="Project documentation" href="../docs/genome">Documentation</a>       </div></li>
 	<li><div>         <a class="<?php echo $overview ?>" title="Overview" href="./overview.php?trk=o">Overview</a>       </div></li>
 	<li><div>         <a class="inactive" title="Quickstart" href="https://fedorahosted.org/genome/wiki/QuickStart">Quickstart</a>       </div></li>
 	<li><div>         <a class="<?php echo $screenshots ?>" title="Screenshots" href="./screenshots.php?trk=s">Screenshots</a>       </div></li>
diff --git a/genome-site/content/overview.php b/genome-site/content/overview.php
index 05bd5e7..f75ae36 100644
--- a/genome-site/content/overview.php
+++ b/genome-site/content/overview.php
@@ -8,7 +8,7 @@
 		<h2>Genome overview:</h2>
 		<p>Genome at a high level is just a set of tools that allow you to provision an Genome repository machine, which in turn maintains the configuration of cloud based infrastructure machines.
 			Whether you need a cluster of JBoss Applications Servers, replicated MySQL databases, or an Apache proxy tier, the Genome project allows you to consistently provision and configure entire IT system tiers.
-			Get started with building an Genome based infrastructure! Read the <a href="/docs/genome">Genome Documentation</a>.</p>
+			Get started with building an Genome based infrastructure! Read the <a href="../docs/genome">Genome Documentation</a>.</p>
 		<h3>Create an isolated infrastructure using the Genome tools</h3>
                 <p>Use the genome tools to create an Genome Repository machine and a cloud of machines to build out an entire IT infrastructure.</p>
 		<p><img src="./styles/genome-high-level.png" border="0" alt="genome high level diagram" /></p>
diff --git a/genome-site/content/styles/genome.css b/genome-site/content/styles/genome.css
index dcdd7ce..0f3a440 100644
--- a/genome-site/content/styles/genome.css
+++ b/genome-site/content/styles/genome.css
@@ -341,3 +341,7 @@ dd {
 .screenshot-desc{
     display: block;
 }
+
+#content a{
+    text-decoration: underline;
+}
diff --git a/genome-site/content/styles/genome_stack.png b/genome-site/content/styles/genome_stack.png
new file mode 100644
index 0000000..e74f58e
--- /dev/null
+++ b/genome-site/content/styles/genome_stack.png
diff --git a/genome.conf b/genome.conf
new file mode 100644
index 0000000..1c09d08
--- /dev/null
+++ b/genome.conf
@@ -0,0 +1,8 @@
+# These aliases are order dependent
+Alias /genome "/var/www/genome"
+<Directory "/var/www/genome">
+    Options Indexes FollowSymLinks Includes
+    AllowOverride None
+    Order allow,deny
+    Allow from all
+</Directory>