|
|
Line 1: |
Line 1: |
| {{CSS/Main}} | | {{CSS/Main}} |
| + | {{:Team:UNC-Chapel_Hill/practicemenu}} |
| <html> | | <html> |
| <head> | | <head> |
| <link href="https://2014.igem.org/Team:UNC-Chapel_Hill/StyleSheets/HomePage?action=raw&ctype=text/css" rel="stylesheet"> | | <link href="https://2014.igem.org/Team:UNC-Chapel_Hill/StyleSheets/HomePage?action=raw&ctype=text/css" rel="stylesheet"> |
| </head> | | </head> |
- | <style>
| |
- | #contentSub, #footer-box, #catlinks, #search-controls, #p-logo, .printfooter, .firstHeading,.visualClear {display: none;} /*-- hides default wiki settings --*/
| |
- | </style>
| |
| | | |
- | <!-- here ends the section that changes the default wiki template to a white full width background -->
| |
- |
| |
- |
| |
- | <!-- beginning of your page -->
| |
- |
| |
- | <!-- menu -->
| |
- | <table id="menu" width="100%" cellspacing="0" height="135px">
| |
- | <tr>
| |
- | <td bgColor="#FFFFFF"></td>
| |
- | <td valign="bottom" width="975px" align="center" bgColor="#FFFFFF">
| |
- |
| |
- | <table align="center">
| |
- | <tr height="50px">
| |
- | <td width="162px" align="center" onMouseOver="this.bgColor='#A1DBB2'" onMouseOut="this.bgColor='#56A0D3'" bgColor=#56A0D3>
| |
- | <a href="https://2014.igem.org/Team:UNC-Chapel_Hill"style="text-decoration:none;color:#ffffff">HOME </a> </td>
| |
- |
| |
- | <td width="162px" align="center" onMouseOver="this.bgColor='#A1DBB2'" onMouseOut="this.bgColor='#56A0D3'" bgColor=#56A0D3>
| |
- | <a href="https://2014.igem.org/Team:UNC-Chapel_Hill/Project" style="text-decoration:none;color:#ffffff">PROJECT</a> </td>
| |
- |
| |
- | <td width="162px" align="center" onMouseOver="this.bgColor='#A1DBB2'" onMouseOut="this.bgColor='#56A0D3'" bgColor=#56A0D3>
| |
- | <a href="https://2014.igem.org/Team:UNC-Chapel_Hill/Parts" style="text-decoration:none;color:#ffffff">PARTS</a></td>
| |
- |
| |
- | <td width="162px" align="center" onMouseOver="this.bgColor='#A1DBB2'" onMouseOut="this.bgColor='#56A0D3'" bgColor=#56A0D3>
| |
- | <a href="https://2014.igem.org/Team:UNC-Chapel_Hill/Team" style="text-decoration:none;color:#ffffff">TEAM </a> </td>
| |
- |
| |
- | <td width="162px" align="center" onMouseOver="this.bgColor='#A1DBB2'" onMouseOut="this.bgColor='#56A0D3'" bgColor=#56A0D3>
| |
- | <a href="https://2014.igem.org/Team:UNC-Chapel_Hill/Notebook" style="text-decoration:none;color:#ffffff">NOTEBOOK </a> </td>
| |
- |
| |
- | <td width="162px" align="center" onMouseOver="this.bgColor='#A1DBB2'" onMouseOut="this.bgColor='#56A0D3'" bgColor=#56A0D3>
| |
- | <a href="https://2014.igem.org/Team:UNC-Chapel_Hill/Safety" style="text-decoration:none;color:#ffffff">SAFETY </a></td>
| |
- |
| |
- | <td width="162px" align="center" onMouseOver="this.bgColor='#A1DBB2'" onMouseOut="this.bgColor='#56A0D3'" bgColor=#56A0D3>
| |
- | <a href="https://2014.igem.org/Team:UNC-Chapel_Hill/Attributions" style="text-decoration:none;color:#ffffff">ATTRIBUTIONS</a></td>
| |
- |
| |
- | </tr>
| |
- |
| |
- | <tr> <td colspan="6"></td>
| |
- | <td align="center" width="162px"><a href="https://igem.org/Main_Page"> <img src="https://static.igem.org/mediawiki/igem.org/6/60/Igemlogo_300px.png" width="55px"></a></td>
| |
- |
| |
- | </tr>
| |
- | </table>
| |
- |
| |
- | </td>
| |
- | <td bgColor="#FFFFFF"></td>
| |
- | </tr>
| |
- | </table>
| |
- | <!-- end of menu -->
| |
| | | |
| | | |
|
Parts Submitted to the Registry
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 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 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 Registry, not on your team wiki. Future teams and other users and are much more likely to find parts on the Registry than on your team wiki.
Remember that the goal of proper part documentation is to describe and define a part, so that it can be used without a need 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.
|
|
Parts
- Part 1 - Lorem ipsum ad his scripta blandit partiendo, eum fastidii accumsan euripidis in, eum liber hendrerit an.
- Part 2 - Lorem ipsum ad his scripta blandit partiendo, eum fastidii accumsan euripidis in, eum liber hendrerit an.
- Part 3 - Lorem ipsum ad his scripta blandit partiendo, eum fastidii accumsan euripidis in, eum liber hendrerit an.
When should you put parts into the Registry?
As soon as possible! We encourage teams to start completing documentation for their parts on the Registry as soon as you have it available. The sooner you put up your parts, the better recall you will have of all details surrounding your parts. Remember you don't need to send us the DNA to create an entry for a part on the Registry. However, you must send us the sample/DNA before the Jamboree. Only parts for which you have sent us samples/DNA are eligible for awards and medal requirements.
|
|