"
Team:UChicago/Parts
From 2013.igem.org
| Line 1: | Line 1: | ||
{{:Team:UChicago/Templates/Standard_header|}} | {{:Team:UChicago/Templates/Standard_header|}} | ||
| + | |||
| + | |||
<html> | <html> | ||
| + | <div id="" class="subNav"> | ||
| + | <ul> | ||
| + | <li class=""> | ||
| + | <a href="/Team:UChicago/Project">Return to Project Details</a> | ||
| + | </li> | ||
| + | </ul> | ||
| + | </div> | ||
| + | |||
<style type="text/css"> | <style type="text/css"> | ||
.navProject a { | .navProject a { | ||
border-bottom: 2px solid #800000; } | border-bottom: 2px solid #800000; } | ||
</style> | </style> | ||
| - | |||
| - | |||
| + | <!-- Thanks to DTU 2011 https://2011.igem.org/Team:DTU-Denmark/How_to_customize_an_iGEM_wiki --> | ||
| + | <!-- ************************************************************************************** --> | ||
| - | + | <div class="subContent"> | |
| - | + | </html> | |
| - | + | <!-- insert your text between these two 'html' tags --> | |
BELOW IS TEXT FORM IGEM HQ | BELOW IS TEXT FORM IGEM HQ | ||
| Line 26: | Line 36: | ||
| + | <html> | ||
| + | </div> | ||
| + | |||
| + | <div class="button wrapperContent"> | ||
| + | <h3><a href="/Team:UChicago/Sponsor_Us">Sponsor Us for Next Year's Competition!</a></h3> | ||
| + | </div> | ||
| + | |||
| + | </html> | ||
{{:Team:UChicago/Templates/Standard_footer}} | {{:Team:UChicago/Templates/Standard_footer}} | ||
Revision as of 00:48, 27 September 2013
BELOW IS TEXT FORM IGEM HQ
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.
<groupparts>iGEM013 UChicago</groupparts>
