Difference between revisions of "Team:Macquarie Australia/parts.html"

(Created page with "{{Macquarie_Australia/CSStemplate}} {{Macquarie_Australia/JavaTemplate}} <!-- DOCTYPE html --> <html class="html" lang="en-US"> <head> <script type="text/javascript"> if(type...")
 
Line 147: Line 147:
 
<div style="position: absolute; top:550px; left:28px; width:400px; height:400px"><!-- content -->
 
<div style="position: absolute; top:550px; left:28px; width:400px; height:400px"><!-- content -->
  
−
<p id="u146-2">Modelling</p>
+
<p id="u146-2">Part Documentation</p>
  
 
<p id="u146-3">&nbsp;</p>
 
<p id="u146-3">&nbsp;</p>
  
−
<p id="u146-5">Our modelling is investigating the pathway between ALA and Protoporphyrin-IX.</p>
+
<p id="u146-5">Each team will make new parts during iGEM and will submit them to the Registry of Standard Biological Parts. The iGEM software provides an easy way to present the parts your team has created. The <groupparts> tag (see below) will generate a table with all of the parts that your team adds to your team sandbox.
−
</style>
+
Remember that the goal of proper part documentation is to describe and define a part, so that it can be used without needing to refer to the primary literature. Registry users in future years 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>
 
</div>
 
</div>
  

Revision as of 01:26, 27 August 2015

Part Documentation

 

Each team will make new parts during iGEM and will submit them to the Registry of Standard Biological Parts. The iGEM software provides an easy way to present the parts your team has created. The tag (see below) will generate a table with all of the parts that your team adds to your team sandbox. Remember that the goal of proper part documentation is to describe and define a part, so that it can be used without needing to refer to the primary literature. Registry users in future years 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..