Difference between revisions of "Team:BroadRun-NorthernVA/Parts"

(Prototype team page)
 
Line 1: Line 1:
 
{{BroadRun-NorthernVA}}
 
{{BroadRun-NorthernVA}}
 
<html>
 
<html>
 +
<!-- Start of CSS-->
 +
<style type="text/css">
  
 +
/* PAGE LAYOUT */
 +
 +
/* Change Background color*/
 +
body {FFCC66
 +
background-color: #FFD699
 +
}
 +
 +
/* Creates a container that will wrap all of the content inside your wiki pages. */
 +
#mainContainer { 
 +
width: 978px;
 +
overflow:hidden;
 +
float:left;
 +
margin-left:20px;
 +
margin-bottom: 10px;
 +
background-color: #FFE680;
 +
border-bottom: 814px solid #FFE680;
 +
border-right: 2px solid #000000;
 +
border-left: 2px solid #000000;
 +
border-top: 5px solid #000000;
 +
font-family: "Trebuchet MS", Helvetica, sans-serif;
 +
}
 +
 +
/* Creates the container for the menu */
 +
#menuContainer  {
 +
float:left;
 +
width: 134px;
 +
padding: 20px 0px;
 +
border-top: 14px solid #7A0000;
 +
background-color: #7A0000;
 +
}
 +
 +
/* Creates the container for the content */
 +
#contentContainer {
 +
padding-top:20px;
 +
padding-right:10px;
 +
margin-bottom: 20px;
 +
width: 814px;
 +
padding-left: 20px;
 +
float: left;
 +
background-color: #FFE680;
 +
border-top: 14px solid #7A0000;
 +
font-family: "Trebuchet MS", Helvetica, sans-serif;
 +
}
 +
 +
/*Set up height place holder for the banner*/
 +
#bannerContainer {
 +
height:200px;
 +
margin:auto;
 +
text-align:center;
 +
color: #FFCC66;
 +
}
 +
 +
/*VISUAL STYLE (TABLES, FONTS, LINKS, IMAGES, UL) */
 +
 +
/*Change the styling of text for everything inside main container*/
 +
#mainContainer p {
 +
font-size: 13px;
 +
color: #000000;
 +
}
 +
 +
/*This changes the color and font family */
 +
#contentContainer h1, h2, h3, h4, h5, h6 {
 +
color: #000000;
 +
border-bottom: none;
 +
font-weight: bold;
 +
font-family: "Trebuchet MS", Helvetica, sans-serif;
 +
margin-top:10px;
 +
}
 +
 +
/*Style of the links - links are different inside the menu */
 +
#contentContainer a {
 +
font-weight: bold;
 +
color: #000000;
 +
}
 +
 +
  /* Styling links on hover- links are different inside the menu */
 +
#contentContainer a:hover {
 +
color: #FFFFFF
 +
}
 +
 +
/*Change the styling of tables */
 +
        #contentContainer table {
 +
    border: 1px solid #000000;
 +
    border-collapse: collapse;
 +
    width: 90%
 +
    margin: auto;
 +
    margin-bottom: 15px;
 +
    margin-top: 15px;
 +
    margin-right: 10px;
 +
    margin-left: 10px;
 +
    }
 +
 +
/*Change the styling of table cells*/
 +
    #contentContainer  td {
 +
    padding: 10px;
 +
    border: 1px solid #00000;
 +
    border-collapse: collapse;
 +
    vertical-align: text-top;
 +
    }
 +
 +
/*Change the styling of table headers */
 +
    #contentContainer th {
 +
    background-color: #000000;
 +
    padding: 10px;
 +
    border: 1px solid #565656;
 +
    border-collapse: collapse;
 +
    vertical-align: text-top;
 +
    }
 +
 +
 +
 +
/*MENU STYLING */
 +
 +
/*Styling for the links in the menu */
 +
#menuContainer a {
 +
color: #FFFFFF;
 +
text-decoration:none;
 +
font-weight: bold;
 +
}
 +
 +
/* Sets the style for lists inside menuContainer  */
 +
#menuContainer ul {
 +
list-style: none;
 +
margin-left:0px;
 +
}
 +
 +
/*Styles the list items to become menu buttons */
 +
#menuContainer ul li {
 +
text-align: center;
 +
display: block;
 +
width: 100%;
 +
height:30px;
 +
padding-top:10px;
 +
}
 +
 +
/*For the menu buttons, changes the color when hovering*/
 +
#menuContainer li:hover {
 +
color:  #FFFFFF;
 +
background-color: #000000;
 +
}
 +
 +
/*Submenus are not displayed as default*/
 +
#menuContainer li ul {
 +
display: none;
 +
padding-top:15px;
 +
margin-left: -19px;
 +
}
 +
 +
/*Submenus are displayed when hovering the menu button */
 +
#menuContainer li:hover ul {
 +
/*display: inline-block; */
 +
display: block;
 +
position: absolute;
 +
float:right;
 +
margin-left: 134px;
 +
margin-top:-42px;
 +
}
 +
 +
/*Style the submenu buttons*/
 +
#menuContainer li ul li{
 +
background-color: #800000;
 +
padding-left:20px;
 +
padding-right:20px;
 +
height:30px;
 +
padding-top:10px;
 +
margin-top:-2px;
 +
color: #FFFFFF;
 +
width: 150px;
 +
}
 +
 +
/*CLASSES */
 +
 +
/*Clear class for all the pages, adds spacing too*/
 +
.clear{
 +
clear:both;
 +
height: 10px;
 +
}
 +
 +
 +
/* highlight box for special messages */
 +
    .highlightBox {
 +
        width:500px;
 +
        margin:auto;
 +
        background-color: #E8E8E9;
 +
margin-bottom: 15px;
 +
margin-top: 15px;
 +
padding: 15px;
 +
padding-top: 5px;
 +
    }
 +
 +
 +
</style>
 +
<!-- End of CSS -->
 
<h2> Part Documentation</h2>
 
<h2> Part Documentation</h2>
  

Revision as of 17:00, 7 September 2015

{{BroadRun-NorthernVA}}



>

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 <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.

Note

Note that parts must be documented on the Registry. This page serves to showcase the parts you have made. Future teams and other users and are much more likely to find parts by looking in the Registry than by looking at your team wiki.

Adding parts to the registry

You can add parts to the Registry at our Add a Part to the Registry link.

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 you will remember all the details about your parts. Remember, you don't need to send us the DNA sample before you create an entry for a part on the Registry. (However, you do need to send us the DNA sample before the Jamboree. If you don't send us a DNA sample of a part, that part will not be eligible for awards and medal criteria.)

What information do I need to start putting my parts on the Registry?

The information needed to initially create a part on the Registry is:

  • Part Name
  • Part type
  • Creator
  • Sequence
  • Short Description (60 characters on what the DNA does)
  • Long Description (Longer description of what the DNA does)
  • Design considerations

We encourage you to put up much more information as you gather it over the summer. If you have images, plots, characterization data and other information, please also put it up on the part page.

Inspiration

We have a created a collection of well documented parts that can help you get started.

You can also take a look at how other teams have documented their parts in their wiki:

Part Table

<groupparts>iGEM015 Example</groupparts>