Difference between revisions of "Team:TUDelft/Parts"

(Prototype team page)
 
Line 1: Line 1:
{{TUDelft}}
+
{{:Team:TUDelft/Header}}
 +
{{:Team:TUDelft/Banner}}
 +
{{:Team:TUDelft/Head}}
 +
 
 
<html>
 
<html>
 +
<style>
 +
@import url('https://fonts.googleapis.com/css?family=Pacifico|Open+Sans:300,400,600');
  
  
<div class="column full_size">
+
a {
<h1>Parts</h1>
+
text-decoration: none;
<p>Each team will make new parts during iGEM and will add them to the Registry of Standard Biological Parts. The iGEM 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>
+
color: inherit;
<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>
+
}
</div>
+
  
<div class="column full_size">
 
<div class="highlight decoration_background">
 
<h3>Note</h3>
 
<p>Note that parts must be well documented on each part's <a href="http://parts.igem.org/Main_Page">Main Page on the Registry</a>. This documentation includes all of the characterization data for your parts. <b>The part's data MUST be on the part's Main Page on the Registry for your team to be eligible for medals and special prizes pertaining to parts.</b> <br><br>
 
This page serves to <i>showcase</i> the parts you have made and should include links to the Registry pages for your parts. 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>
 
</div>
 
  
<div class="clear extra_space"></div>
+
div .protocols {
<div class="line_divider"></div>
+
width: 100%;
<div class="clear extra_space"></div>
+
min-width: 300px;
 +
max-width: 800px;
 +
margin: 1.5em auto;
 +
color: #333;
 +
box-sizing: border-box;
 +
}
  
 +
ul {
 +
list-style: none;
 +
padding: 0;
 +
}
 +
ul .inner {
  
 +
padding-left: 50px;
 +
padding-top: 10px;
 +
overflow: hidden;
 +
display: none;
 +
}
  
  
 +
ul li {
 +
margin: .5em 0;
 +
font-weight: 300;
 +
}
  
<div class="column two_thirds_size">
+
ul li a.toggle {
<div class="highlight decoration_B_full">
+
  
<h3>Adding parts to the registry</h3>
+
display: block;
<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>
+
background: rgba(0, 166, 214, 1);
 +
color: #fefefe;
 +
padding: .75em;
 +
padding-left: 50px;
 +
border-radius: 0.5em;
 +
transition: background .3s ease;
 +
text-decoration: none;
 +
}
  
<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. Documentation includes the characterization data of your parts.</p>
+
ul li a.toggle:hover {
<div class="button_link">
+
background: rgba(0, 166, 214, 0.65);
<a href="http://parts.igem.org/Add_a_Part_to_the_Registry">
+
ADD PARTS
+
</a>
+
</div>
+
  
</div>
+
}
</div>
+
  
  
  
<div class="column third_size">
+
</style>
<div class="highlight decoration_A_full">
+
<script src="https://ajax.googleapis.com/ajax/libs/jquery/2.1.0/jquery.min.js"></script>
<h3>Inspiration</h3>
+
<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>
+
  
<p> You can also take a look at how other teams have documented their parts in their wiki:</p>
+
<body>
 +
    <br>
 +
        <div class="Banner container-fluid text-center mb-0 align-items-center ">
 +
 
 +
            <div class="display-2 mb-0">
 +
                <br>
 +
                <br>
 +
                <img src = "https://static.igem.org/mediawiki/2019/0/03/T--TUDelft--Modeling_logo.png" alt="Protocol Experiments" style="width:60%"; >
 +
            </div>           
 +
        </div>
 +
  <div class= "protocol centerjustify">
 +
 
 +
</p>
 +
 +
    <h2>Controllable expression</h2>
 
<ul>
 
<ul>
<li><a href="https://2014.igem.org/Team:MIT/Parts"> 2014 MIT </a></li>
+
<li>
<li><a href="https://2014.igem.org/Team:Heidelberg/Parts"> 2014 Heidelberg</a></li>
+
<a class="toggle" href="javascript:void(0);" ><b>Promoters</b></a>
<li><a href="https://2014.igem.org/Team:Tokyo_Tech/Parts">2014 Tokyo Tech</a></li>
+
<div class="inner">
</ul>
+
<p>  
</div>
+
 
 +
</p>
 
</div>
 
</div>
 +
</li>
  
 +
<li>
 +
<a class="toggle" href="javascript:void(0);" ><b>Ribosome Binding Site</b></a>
 +
<div class="inner">
 +
<p>
  
<div class="clear extra_space"></div>
+
</p>
 +
</div>
 +
</li>
  
 +
<li>
 +
<a class="toggle" href="javascript:void(0);" ><b>Coding Sequence</b></a>
 +
<div class="inner">
 +
<p>
  
 +
</p>
 +
</div>
 +
</li>
  
 +
<li>
 +
<a class="toggle" href="javascript:void(0);" ><b>Terminators?</b></a>
 +
<div class="inner">
 +
  <h2>Orthogonal Transcription</h2>
 +
<ul>
 +
<li>
 +
<a class="toggle" href="javascript:void(0);" ><b>Promoters</b></a>
 +
<div class="inner">
 +
<p>
  
<div class="column full_size">
+
</p>
 +
</div>
 +
</li>
  
<h3>What information do I need to start putting my parts on the Registry?</h3>
+
<li>
<p>The information needed to initially create a part on the Registry is:</p>
+
<a class="toggle" href="javascript:void(0);" ><b>Ribosome Binding Site</b></a>
<ul>
+
<div class="inner">
<li>Part Name</li>
+
<p>  
<li>Part type</li>
+
 
<li>Creator</li>
+
</p>
<li>Sequence</li>
+
</div>
<li>Short Description (60 characters on what the DNA does)</li>
+
</li>
<li>Long Description (Longer description of what the DNA does)</li>
+
<li>Design considerations</li>
+
</ul>
+
  
<p>
+
<li>
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, you must also put it up on the part page. </p>
+
<a class="toggle" href="javascript:void(0);" ><b>Coding Sequence</b></a>
 +
<div class="inner">
 +
<p>  
  
 +
</p>
 
</div>
 
</div>
 +
</li>
  
 +
<li>
 +
<a class="toggle" href="javascript:void(0);" ><b>Terminators?</b></a>
 +
<div class="inner">
  
<div class="clear extra_space"></div>
+
</div>
<div class="line_divider"></div>
+
</li>
<div class="clear extra_space"></div>
+
</ul>
  
<div class="column full_size">
 
<h3>Part Table </h3>
 
  
<p>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. </p>
 
  
</html>
+
<script> $('.toggle').click(function(e) {
<groupparts>iGEM19 TUDelft</groupparts>
+
e.preventDefault();
<html>
+
</div>
+
  
 +
var $this = $(this);
  
 +
if ($this.next().hasClass('show')) {
 +
$this.next().removeClass('show');
 +
$this.next().slideUp(350);
 +
} else {
 +
$this.parent().parent().find('li .inner').removeClass('show');
 +
$this.parent().parent().find('li .inner').slideUp(350);
 +
$this.next().toggleClass('show');
 +
$this.next().slideToggle(350);
 +
}
 +
});
 +
</script>
  
 +
</div>
 +
    </body>
  
 
</html>
 
</html>
 +
 +
 +
{{:Team:TUDelft/Footer}}

Revision as of 08:00, 9 September 2019

Sci-Phi 29


Controllable expression

  • Promoters

  • Ribosome Binding Site

  • Coding Sequence

  • Terminators?

    Orthogonal Transcription