Line 2: | Line 2: | ||
<html> | <html> | ||
− | <div class="header-img hide-on-med-and-down"> | + | <div class="clickable"> |
+ | <div class="header-img hide-on-med-and-down"> | ||
<img src="https://static.igem.org/mediawiki/2018/f/f5/T--NTNU_Trondheim--greenpartsheader.png"> | <img src="https://static.igem.org/mediawiki/2018/f/f5/T--NTNU_Trondheim--greenpartsheader.png"> | ||
+ | <div class="centered floating hide-on-med-and-down"> | ||
+ | <i class="fas fa-angle-down fa-2x"></i> | ||
+ | </div> | ||
+ | </div> | ||
</div> | </div> | ||
− | <div class="header-img hide-on-large-only "> | + | <div class="clickable"> |
+ | <div class="header-img hide-on-large-only "> | ||
<img src="https://static.igem.org/mediawiki/2018/archive/b/b0/20180802073404%21T--NTNU_Trondheim--partsheadermobile.png"> | <img src="https://static.igem.org/mediawiki/2018/archive/b/b0/20180802073404%21T--NTNU_Trondheim--partsheadermobile.png"> | ||
+ | <div class="centered-mobile floating hide-on-large-only"> | ||
+ | <i class="fas fa-angle-down fa-2x"></i> | ||
+ | </div> | ||
+ | </div> | ||
</div> | </div> | ||
Line 46: | Line 56: | ||
</div> | </div> | ||
+ | |||
+ | <script type="text/javascript"> | ||
+ | $('.clickable').click(function() { | ||
+ | $('html, body').animate({ scrollTop: $('.container').offset().top-20}, 'slow'); | ||
+ | }); | ||
+ | </script> | ||
</html> | </html> |
Revision as of 18:38, 6 August 2018
Medal | Part name | Type | Description | Length (bp) |
---|---|---|---|---|
1.1 | 195 | 6 | 1 | 1 |
1.2 | 185 | 2 | 0 | 1 |
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.
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.