Team:UT Dallas/Parts
From 2013.igem.org
(Prototype team page) |
|||
Line 1: | Line 1: | ||
- | + | ||
+ | |||
+ | |||
+ | {{:Team:UT_Dallas/Templates/Main}} | ||
<html> | <html> | ||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | < | + | <head> |
+ | <style> | ||
+ | #content { | ||
+ | background: none; | ||
+ | box-shadow: 0px 0px 0px 0px; | ||
- | { | + | #bodyContent { |
- | + | margin-left: -1px; | |
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
+ | #footer-box { | ||
+ | width: 965px; | ||
+ | padding: 5px; | ||
+ | background-color: white; | ||
+ | margin: 0 auto; | ||
+ | border: 0px; | ||
+ | border-radius: 5px 5px 5px 5px; | ||
+ | box-shadow: 0px 2px 6px 2px #222; | ||
+ | } | ||
+ | </style> | ||
+ | </head> | ||
- | 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. | + | <body class="space"> |
+ | <div id="bottom-panel"> | ||
+ | <table> | ||
+ | <tr> | ||
+ | <td> | ||
+ | <div style="width: 580px; margin-top:0px;"> | ||
+ | <span id="abs-title">PARTS</span> | ||
+ | <span style="float: left;"> | ||
+ | <p id="abs-text"> | ||
+ | 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. </br></br> | ||
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. | ||
+ | </span> | ||
+ | </div> | ||
+ | </td> | ||
+ | <td> | ||
+ | </div> | ||
+ | </td> | ||
+ | </tr> | ||
+ | </table> | ||
+ | </div> | ||
- | + | ||
- | < | + | </div> |
+ | |||
+ | </body> | ||
+ | </html> |
Revision as of 03:34, 23 August 2013
PARTS
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. |