Difference between revisions of "Team:Berlin/Parts"

(Prototype team page)
 
 
Line 1: Line 1:
{{Berlin}}
 
 
<html>
 
<html>
 +
<style>
 +
/* iGEM Paris Bettencourt 2015 style
 +
* Design by Jérémy Ferrando &amp; Ewen Corre
 +
* It's FREE! But you can send us beer at
 +
* beer@corre.bio :-) */
  
<h2> Part Documentation</h2>
+
/* RESET STYLE
 +
* http://meyerweb.com/eric/tools/css/reset/
 +
* v2.0 | 20110126
 +
* License: none (public domain) */
  
<p>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 <code>&lt;groupparts&gt;</code> tag (see below) will generate a table with all of the parts that your team adds to your team sandbox.</p>
+
html, body, div, span, applet, object, iframe,
<p>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>
+
h1, h2, h3, h4, h5, h6, p, blockquote, pre,
 +
a, abbr, acronym, address, big, cite, code,
 +
del, dfn, em, img, ins, kbd, q, s, samp,
 +
small, strike, strong, sub, sup, tt, var,
 +
b, u, i, center,
 +
dl, dt, dd, ol, ul, li,
 +
fieldset, form, label, legend,
 +
table, caption, tbody, tfoot, thead, tr, th, td,
 +
article, aside, canvas, details, embed,
 +
figure, figcaption, footer, header, hgroup,
 +
menu, nav, output, ruby, section, summary,
 +
time, mark, audio, video {
 +
margin: 0;
 +
padding: 0;
 +
border: 0;
 +
font-size: 100%;
 +
font: inherit;
 +
vertical-align: baseline;
 +
}
 +
/* HTML5 display-role reset for older browsers */
 +
article, aside, details, figcaption, figure,
 +
footer, header, hgroup, menu, nav, section {
 +
display: block;
 +
}
 +
body {
 +
line-height: 1;
 +
        background-color: white;
 +
}
 +
ol, ul {
 +
list-style: none;
 +
}
 +
blockquote, q {
 +
quotes: none;
 +
}
 +
blockquote:before, blockquote:after,
 +
q:before, q:after {
 +
content: '';
 +
content: none;
 +
}
 +
table {
 +
border-collapse: collapse;
 +
border-spacing: 0;
 +
}
 +
/* Destroy the wikimedia style */
 +
html, body, #content, #bodyContent, #globalWrapper, #mainContainer, #mw-content-text {
 +
margin: 0;
 +
padding: 0;
 +
border: 0;
 +
font-size: 100%;
 +
font: inherit;
 +
vertical-align: baseline;
 +
width: 100%;
 +
height: 100%;
 +
        min-width: 400px;
 +
}
 +
/* Repair the menu (offset) */
 +
#top_menu_inside li {
 +
margin: 2px;
 +
}
 +
/* Modify a bit the iGEM bar… Sorry!
 +
#top_menu_14,
 +
#top_menu_inside {
 +
        border: 0;
 +
        background-color: transparent;
 +
}
 +
#top_menu_inside > ul > li > a {
 +
        color: #9A9A9A !important;
 +
        padding: 0;
 +
}
 +
#top_menu_inside > ul > li {
 +
        padding-left: 10px;
 +
        padding-right: 10px;
 +
        border-bottom: 1px solid #EEEEEE;
 +
}
 +
#top_menu_inside > ul > li:hover a {
 +
        color: white !important;
 +
}
 +
#top_menu_inside #bars_item img {
 +
        background-color: #CCCCCC;
 +
}*/
 +
/******************************/
  
 +
.firstHeading{
 +
display: none;
 +
}
  
<div class="highlightBox">
 
<h4>Note</h4>
 
<p>Note that parts must be documented on the <a href="http://parts.igem.org/Main_Page"> Registry</a>. This page serves to <i>showcase</i> 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.</p>
 
</div>
 
  
 +
</style>
 +
</html>
  
 +
{{Berlin/css/bootstrap.css}}
 +
{{Berlin/css/style.css}}
 +
{{Berlin/css/bootstrap-theme.css}}
 +
{{Berlin/css/cover.css}}
 +
{{Berlin/css/jasny-bootstrap.min.css}}
 +
{{Berlin/css/navmenu-push.css}}
 +
<html lang="en">
 +
<body>
  
<h4>Adding parts to the registry</h4>
 
<p>You can add parts to the Registry at our <a href="http://parts.igem.org/Add_a_Part_to_the_Registry">Add a Part to the Registry</a> link.</p>
 
<p>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 <b>do</b> 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.)</p>
 
  
  
<h4>What information do I need to start putting my parts on the Registry?</h4>
+
<!-- Begin Cover -->
<p>The information needed to initially create a part on the Registry is:</p>
+
<div class="site-wrapper-sub-project">
<ul>
+
</html>
<li>Part Name</li>
+
{{Berlin/inc/main-menue.php}}
<li>Part type</li>
+
{{Berlin/inc/burger-menue.php}}
<li>Creator</li>
+
<html>  
<li>Sequence</li>
+
</div> <!-- End Cover -->
<li>Short Description (60 characters on what the DNA does)</li>
+
<li>Long Description (Longer description of what the DNA does)</li>
+
<li>Design considerations</li>
+
</ul>
+
  
<p>
 
We encourage you to put up <em>much more</em> 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. </p>
 
  
 +
<!-- Our Project Row (1) -->
 +
<section data-speed="200" data-type="background" id="section-sub">
 +
  <div class="container-fluid container-blue">
 +
    <div class="row featurette" id="main-featurette-row">
  
 +
    </div>
 +
  </div>
 +
  <div id="subside-content">
 +
<div class="container">
 +
    <div class="row">     
 +
      <div class="col-xs-3 submenue-project" style="text-align:left;">
 +
        <a href="https://2015.igem.org/Team:Berlin/Project" class="sub-link-project"> 1. What's the problem?</a><br/><br/>
 +
      <a href="https://2015.igem.org/Team:Berlin/Project/Strategy" class="sub-link-project"> 2. How does it work?</a><br/><br/>
 +
        <a href="https://2015.igem.org/Team:Berlin/Project/Plant" class="sub-link-project">3. The Wastewater Treatment Plant</a><br/><br/>
 +
        <a href="https://2015.igem.org/Team:Berlin/Project/Implementation" class="sub-link-project">4. Implementation of our Product</a><br/><br/>
 +
        <a href="https://2015.igem.org/Team:Berlin/Project/property" class="sub-link-project">5. Properties of Enzymatic Flagellulose</a><br/><br/>
 +
        <a href="https://2015.igem.org/Team:Berlin/Project/results" class="sub-link-project">6. Results</a><br/><br/>
 +
<a href="https://2015.igem.org/Team:Berlin/Modeling" class="sub-link-project">7. Modeling</a><br/><br/>
 +
      <br/>
 +
      </div>
 +
 +
      <div class="col-xs-11 col-sm-9 blog-text" style="margin-bottom:40px;">
 +
   
 +
      <div class="project-headline-float">
 +
      <h4 class="blue-text project-headline"><font face="Arial">Parts</h4></font>
 +
      </div>
 +
<div>
 +
          </html>
 +
          <groupparts>iGEM015 Berlin</groupparts>
 +
          <html>
 +
          </div>
  
 
+
      <p>    
 
+
        <a name="description">&nbsp;</a>
 
+
       
<h4>Inspiration</h4>
+
                              </p>
<p>We have a created  a <a href="http://parts.igem.org/Well_Documented_Parts">collection of well documented parts</a> that can help you get started.</p>
+
    </div>
 
+
  </div>  
<p> You can also take a look at how other teams have documented their parts in their wiki:</p>
+
</div>
<ul>
+
  </div>
<li><a href="https://2014.igem.org/Team:MIT/Parts"> 2014 MIT </a></li>
+
</section>  
<li><a href="https://2014.igem.org/Team:Heidelberg/Parts"> 2014 Heidelberg</a></li>
+
<!-- Fussabschnitt -->
<li><a href="https://2014.igem.org/Team:Tokyo_Tech/Parts">2014 Tokyo Tech</a></li>
+
</ul>
+
 
+
 
+
 
+
<h4>Part Table </h4>
+
 
</html>
 
</html>
<groupparts>iGEM015 Example</groupparts>
+
{{Berlin/inc/footer.php}}
 
<html>
 
<html>
 
+
</body>
 
+
 
+
</div>
+
 
</html>
 
</html>

Latest revision as of 17:10, 18 September 2015