Team:HebrewU/Parts

/* I-GEM original picture and page frame disabling */ 

           #sideMenu, #top_title {display:none;}
           #sideMenu, #sideMenu *, #top_menu_inside, #top_menu_inside *{box-sizing: initial; -webkit-box-sizing: initial;}
           #content { padding:0px; width:100%; margin-top:-7px; margin-left:0px;}
           body {background-color:white; }
           #bodyContent h1, #bodyContent h2, #bodyContent h3, #bodyContent h4, #bodyContent h5 { margin-bottom: 0px; }

/* Responsive layout - makes the three columns stack on top of each other instead of next to each other */ @media screen and (max-width: 600px) { 

   .columnhuji.side, .columnhuji.middle {
       width: 100%;
   }

}


  1. ddmenu_hebrewu {
   background:#262d2e;
   margin: 0;
   padding: 0;
   height:35px;
   font: 15px Calibri, Calibri;}
  1. ddmenu_hebrewu li { 
   float: left;
   list-style: none;
   font: 20px Calibri, Calibri;}
  1. ddmenu_hebrewu li a { 
   background:#262d2e;
   display: block;
   padding: 5px 20px;
   text-decoration: none;
   color: white;

}


  1. ddmenu_hebrewu li a:hover { 
   background: #2c3635;

}

  1. ddmenu_hebrewu li ul { 
   margin: 3px 0 0 10px;
   padding: 0;
   position: absolute;
   visibility: hidden;

}

  1. ddmenu_hebrewu li ul li { 
   display:inline;

}

  1. ddmenu_hebrewu li ul li a {
   width: auto;    
   background: none;
   display: inline;
   color: black; 
   font: 20px Calibri, Calibri;
   padding: 2px 10px;

}

  1. ddmenu_hebrewu li ul li a:hover { 
   background: none;
   color: #106375; 
   padding: 2px 10px;

}

/* Homebutton 10% space */ .huji_homebutton { 

   float: left;
   width: 13%;

}


.columnhuji { 

   float: left;
   padding: 10px;

}

.columnhuji.side { 

   width: 12%;

}

/* Middle column */ .columnhuji.middle { 

   width: 70%;
   background-color:#edeadc;
   padding: 10px;

}

/* Clear floats after the columns */ .rowhuji:after { 

   content: "";
   display: table;
   clear: both;

}

/* content style */


h2.ahuji { 

   font: 30px Calibri, Calibri;
   text-align: center;

}

h2.chuji { 

   font: 20px Calibri, Calibri;
   text-align: center;

}

p.ahuji { 

   font: 18px Calibri, Calibri;

margin-left:5%; margin-right:5%; text-align:justify; }

p.bhuji { 

   font: 18px Calibri, Calibri;

text-align:center; }

/* button1 style */

.buttonhuji { font: 18px Calibri, Calibri; 

   border: none;
   color: white;
   padding: 10px 32px;
   text-align: center;
   display: inline-block;
   font-size: 15px;
   margin: 2px 2px;
   -webkit-transition-duration: 0.4s; /* Safari */
   transition-duration: 0.4s;
   cursor: pointer;

}

.buttonhuji1 { 

   background-color: #fdfaf2;
   color: black;
   border: 2px solid #829c8c;

}

.buttonhuji1:hover { 

   background-color: #829c8c;
   color: white;

}

/* Group image style style */

.centerhujiimg { 

   margin: auto;
   width: 60%;

text-align: center; }

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

ADD PARTS

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:

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.

Part Table

Please include a table of all the parts your team has made during your project on this page. Remember part characterization and measurement data must go on your team part pages on the Registry.

<groupparts>iGEM18 HebrewU</groupparts>