Team:Bielefeld-Germany/Parts

From 2013.igem.org

(Difference between revisions)
Line 1: Line 1:
{{Team:Bielefeld-Germany/Header2}}
{{Team:Bielefeld-Germany/Header2}}
{{Team:Bielefeld-Germany/css/header_cleanup.css}}
{{Team:Bielefeld-Germany/css/header_cleanup.css}}
 +
{{Team:Bielefeld-Germany/css/button.css}}
 +
 +
__NOTOC__
__NOTOC__
 +
<html>
 +
<style>
 +
h1{padding:10px 0;padding-left:300px; padding-right:350px; margin-top:70px; }
 +
.toc, #toc{width:255px;font-size:85%;}
 +
#globalwrapper ul {padding-left:40px; padding-right:40px;}
 +
#globalwrapper #rightcol ul {padding-left:0px; padding-right:0px;}
-
<div id="globalwrap" style="padding-left:20px; padding-right:20px">
+
h2,h3,h4{clear:both;}
-
<br><br><br>
+
#globalwrapper h4{color:#ff6600; padding-left:20px;}
 +
#globalwrapper div.thumb.tleft{margin-left:20px; margin-right:20px; clear:both;}
-
<h2>Parts</h2>
+
#globalwrapper ul {clear:both;}
 +
#globalwrapper ul ul{clear:both;}
 +
#globalwrapper ul{padding-left:60px; padding-right:40px;}
 +
#globalwrapper ul ul{padding-left:40px; padding-right:40px;}
 +
#globalwrapper p{padding-left:0px; padding-right:40px;}
 +
#globalwrapper .bigbutton p{padding-left:5px; padding-right:5px; padding-top:2px;}
 +
 +
.bigbutton{width:150px; height:50px; line-height:50px; font-size:1.2em; margin-right:10px; display:table;}
 +
.bigbutton a{display:block; height:100%;}
 +
 +
.rightcol{
 +
width:140px;
 +
height:450px;
 +
margin-left:800px;
 +
float:right;
 +
position:fixed;
 +
margin-top:0px;
 +
overflow-y:scroll; 
 +
box-shadow:0px 0px 2px 0px grey;
 +
padding:0px 20px;
 +
 +
</style>
 +
</html>
 +
 +
<div id=globalwrapper style="padding-left:20px; padding-right:20px">
 +
<div id="leftcol" style="width:750px; float:left; overflow:auto;">
 +
 +
<html>
 +
<h1>Parts</h1>
 +
<div id="buttonrow" style="padding-top:30px; padding-bottom:70px; padding-left:45px; clear:both;">
 +
 +
<div class="bigbutton">
 +
<a href="https://2013.igem.org/Team:Bielefeld-Germany/Project/Abstract">Projects Overview</a></div>
 +
<div class="bigbutton">
 +
<a href="https://2013.igem.org/Team:Bielefeld-Germany/Project/Nanowires#Theory">Theory</a></div>
 +
<div class="bigbutton">
 +
<a href="https://2013.igem.org/Team:Bielefeld-Germany/Project/Nanowires#Genetic_Approach">Genetic Approach</a></div>
 +
<div class="bigbutton">
 +
<a href="https://2013.igem.org/Team:Bielefeld-Germany/Project/Nanowires#Results">Results</a></div>
 +
 +
</div>
 +
</html>
 +
 +
 +
==Overview==
 +
 +
<p align="justify">
An important aspect of the iGEM competition is the use and creation of standard  biological parts. Each team will make new parts during iGEM and will place them in the [http://partsregistry.org Registry of Standard Biological Parts]. The iGEM software provides an easy way to present the parts your team has created . The "groupparts" tag will generate a table with all of the parts that your team adds to your team sandbox.  Note that if you want to document a part you need to document it on the [http://partsregistry.org Registry], not on your team wiki.
An important aspect of the iGEM competition is the use and creation of standard  biological parts. Each team will make new parts during iGEM and will place them in the [http://partsregistry.org Registry of Standard Biological Parts]. The iGEM software provides an easy way to present the parts your team has created . The "groupparts" tag will generate a table with all of the parts that your team adds to your team sandbox.  Note that if you want to document a part you need to document it on the [http://partsregistry.org Registry], not on your team wiki.
Remember that the goal of proper part documentation is to describe and define a part such that it can be used without a need to refer to the primary literature. The next iGEM team should be able to read your documentation and be able to use the part successfully. Also, you should provide proper references to acknowledge previous authors and to provide for  users who wish to know more.
Remember that the goal of proper part documentation is to describe and define a part such that it can be used without a need to refer to the primary literature. The next iGEM team should be able to read your documentation and be able to use the part successfully. Also, you should provide proper references to acknowledge previous authors and to provide for  users who wish to know more.
 +
</p>
 +
 +
 +
 +
 +
<br><br>
 +
 +
 +
 +
<br><br><br><br>
 +
 +
 +
 +
==Theory==
 +
 +
 +
 +
 +
==Genetic Approach==
 +
 +
 +
 +
 +
==Results==
 +
 +
 +
 +
==References==
 +
 +
 +
 +
 +
 +
<br><br><br><br>
 +
</div>
 +
 +
 +
 +
 +
<div id="rightcol" style="width:210px; height:450px; margin-left:752px; margin-top:33px; float:right; position:fixed; overflow-y:scroll;    box-shadow:0px 0px 2px 0px grey;" padding:0px 20px;>
 +
__TOC__
 +
<div id="spacer" style="height:300px"></div>
 +
</div>
-
<groupparts>iGEM013 Bielefeld-Germany</groupparts>
+
</div>

Revision as of 20:54, 29 September 2013



Parts


Overview

An important aspect of the iGEM competition is the use and creation of standard biological parts. Each team will make new parts during iGEM and will place them in the [http://partsregistry.org Registry of Standard Biological Parts]. The iGEM software provides an easy way to present the parts your team has created . The "groupparts" tag will generate a table with all of the parts that your team adds to your team sandbox. Note that if you want to document a part you need to document it on the [http://partsregistry.org Registry], not on your team wiki. Remember that the goal of proper part documentation is to describe and define a part such that it can be used without a need to refer to the primary literature. The next iGEM team should be able to read your documentation and be able to use the part successfully. Also, you should provide proper references to acknowledge previous authors and to provide for users who wish to know more.











Theory

Genetic Approach

Results

References







Contents

Retrieved from "http://2013.igem.org/Team:Bielefeld-Germany/Parts"