Team:Kent

From 2014.igem.org

(Difference between revisions)
Line 1: Line 1:
-
<!doctype html>
 
<html>
<html>
<head>
<head>
<meta charset="utf-8">
<meta charset="utf-8">
-
<title>Untitled Document</title>
+
<title>Univeristy of Kent iGEM </title>
-
<LINK REL=StyleSheet HREF="Kent_igem_CSS.css" TYPE="text/css" MEDIA=screen>
+
<style type="text/css">
-
 
+
</style>
</style>
<link rel="stylesheet" href="https://2014.igem.org/Team:Kent/CSS?action=raw&ctype=text/css" type="text/css" />
<link rel="stylesheet" href="https://2014.igem.org/Team:Kent/CSS?action=raw&ctype=text/css" type="text/css" />
-
<!--[if lt IE 9]>
+
<link rel="stylesheet" href="https://2014.igem.org/Team:Kent/navbar_css?action=raw&ctype=text/css" type="text/css" />
-
<script src="http://html5shiv.googlecode.com/svn/trunk/html5.js"></script>
+
<link rel="stylesheet" href="https://2014.igem.org/Team:Kent/menu_bar?action=raw&ctype=text/css" type="text/css" />
 +
 
 +
<!--[if lte IE 7]>
 +
<style>
 +
.content { margin-right: -1px; } /* this 1px negative margin can be placed on any of the columns in this layout with the same corrective effect. */
 +
ul.nav a { zoom: 1; }  /* the zoom property gives IE the hasLayout trigger it needs to correct extra whiltespace between the links */
 +
</style>
<![endif]--></head>
<![endif]--></head>
Line 15: Line 19:
<div class="container">
<div class="container">
-
   <header>
+
   <div class="header"><a href="#"><img src="https://2014.igem.org/File:KENT_Standard_heade_final.jpg" alt="Insert Logo Here" name="Insert_logo" width="1261" height="213" id="Insert_logo" style="background-color: #8090AB; display:block;" /></a>  
-
    <a href="#"><img src="" alt="Insert Logo Here" width="961" height="90" id="Insert_logo" style="background-color: #C6D580; display:block;" /></a>
+
    <!-- end .header --></div>
-
  </header>
+
 
   <div class="sidebar1">
   <div class="sidebar1">
-
    <ul class="nav">
+
<ul><li>Home</li>
-
      <li><a href="#">Link one</a></li>
+
  <li>About</li>
-
      <li><a href="#">Link two</a></li>
+
  <li>
-
       <li><a href="#">Link three</a></li>
+
    NoteBook
-
       <li><a href="#">Link four</a></li>
+
    <ul>
 +
      <li>Lab Book</li>
 +
       <li>Protocols</li>
 +
       <li>Saftey</li>
     </ul>
     </ul>
-
    <aside>
+
  </li>
-
      <p> The above links demonstrate a basic navigational structure using an unordered list styled with CSS. Use this as a starting point and modify the properties to produce your own unique look. If you require flyout menus, create your own using a Spry menu, a menu widget from Adobe's Exchange or a variety of other javascript or CSS solutions.</p>
+
  <li>Human Outreach</li>
-
      <p>If you would like the navigation along the top, simply move the ul to the top of the page and recreate the styling.</p>
+
  <li>Contact</li>
-
    </aside>
+
</ul>
-
  <!-- end .sidebar1 --></div>
+
 
-
   <article class="content">
+
    <!-- end .sidebar1 --></div>
-
    <h1>Instructions</h1>
+
   <div class="content">
-
     <section>
+
 
-
    <h2>How to use this document</h2>
+
     <p><img src="https://static.igem.org/mediawiki/2014/d/d7/Team_photo_Kent.jpg" alt="Team Photo" >  
-
      <p>Be aware that the CSS for these layouts is heavily commented. If you do most of your work in Design view, have a peek at the code to get tips on working with the CSS for the fixed layouts. You can remove these comments before you launch your site. To learn more about the techniques used in these CSS Layouts, read this article at Adobe's Developer Center - <a href="http://www.adobe.com/go/adc_css_layouts">http://www.adobe.com/go/adc_css_layouts</a>.</p>
+
</p>
-
    </section>
+
     <p>&nbsp; </p>
-
     <section>
+
    <p><align="justify">Perfume production is constantly threatened by the destruction of ecological systems, human practices such as deforestation and excessive over cropping constantly deplete supplies of natural resources so demand always exceeds supply. This dilemma is what brings up the cost of quality perfumes and this is what we aim to tackle in our project. By engineering E. Coli to produce scents that are hard to come across naturally, we aim to make perfume accessible for all. This principle can be used to create a database of scents that can be ordered to consumer demand, by using E. Coli to generate these scents we aim to reduce the cost of these scents and improve yield in a more sustainable and less destructive manner. Our Biobricks are aimed at scent production and this we hope, can later be compartmentalised to improve yield and efficiency.</p>
-
      <h2>Clearing Method</h2>
+
    <p>&nbsp;</p>
-
      <p>Because all the columns are floated, this layout uses a clear:both declaration in the footer rule. This clearing technique forces the .container to understand where the columns end in order to show any borders or background colors you place on the .container. If your design requires you to remove the footer from the .container, you'll need to use a different clearing method. The most reliable will be to add a &lt;br class=&quot;clearfloat&quot; /&gt; or &lt;div  class=&quot;clearfloat&quot;&gt;&lt;/div&gt; after your final floated column (but before the .container closes). This will have the same clearing effect. </p>
+
    <p><img src="https://static.igem.org/mediawiki/2014/8/8f/Smell-Ya_later_kent.jpg" ="Team Photo" > </p>
-
    </section>
+
   <!-- end .content --></div>
-
    <section>
+
   <div class="footer">
-
      <h2>Logo Replacement</h2>
+
     <p>&nbsp;</p>
-
      <p>An image placeholder was used in this layout in the header where you'll likely want to place  a logo. It is recommended that you remove the placeholder and replace it with your own linked logo. </p>
+
   <!-- end .footer --></div>
-
      <p> Be aware that if you use the Property inspector to navigate to your logo image using the SRC field (instead of removing and replacing the placeholder), you should remove the inline background and display properties. These inline styles are only used to make the logo placeholder show up in browsers for demonstration purposes. </p>
+
-
      <p>To remove the inline styles, make sure your CSS Styles panel is set to Current. Select the image, and in the Properties pane of the CSS Styles panel, right click and delete the display and background properties. (Of course, you can always go directly into the code and delete the inline styles from the image or placeholder there.)</p>
+
-
    </section>
+
-
   <!-- end .content --></article>
+
-
   <aside>
+
-
    <h4>Backgrounds</h4>
+
-
     <p>By nature, the background color on any block element will only show for the length of the content. If you'd like a dividing line instead of a color, place a border on the side of the .content block (but only if it will always contain more content).</p>
+
-
   </aside>
+
-
  <footer>
+
-
    <p>This footer contains the declaration position:relative; to give Internet Explorer 6 hasLayout for the footer and cause it to clear correctly. If you're not required to support IE6, you may remove it.</p>
+
-
    <address>
+
-
      Address Content
+
-
    </address>
+
-
  </footer>
+
   <!-- end .container --></div>
   <!-- end .container --></div>
</body>
</body>
</html>
</html>

Revision as of 17:59, 6 August 2014

Univeristy of Kent iGEM

  • Home
  • About
  • NoteBook
    • Lab Book
    • Protocols
    • Saftey
  • Human Outreach
  • Contact

Team Photo

 

Perfume production is constantly threatened by the destruction of ecological systems, human practices such as deforestation and excessive over cropping constantly deplete supplies of natural resources so demand always exceeds supply. This dilemma is what brings up the cost of quality perfumes and this is what we aim to tackle in our project. By engineering E. Coli to produce scents that are hard to come across naturally, we aim to make perfume accessible for all. This principle can be used to create a database of scents that can be ordered to consumer demand, by using E. Coli to generate these scents we aim to reduce the cost of these scents and improve yield in a more sustainable and less destructive manner. Our Biobricks are aimed at scent production and this we hope, can later be compartmentalised to improve yield and efficiency.

 

 

Retrieved from "http://2014.igem.org/Team:Kent"