Difference between revisions of "Team:Vanderbilt/Description"

Line 1: Line 1:
−
{{Vanderbilt}}
+
{{Team:Vanderbilt/css/assets.css}}
−
<html>
+
{{Team:Vanderbilt/css/style.css}}
−
 
+
{{Team:Vanderbilt/js/jquery.js}}
−
 
+
{{Team:Vanderbilt/js/assets.js}}
−
<div class="column full_size">
+
{{Team:Vanderbilt/js/scripts.js}}
−
 
+
{{Team:Vanderbilt/header}}
−
<p>Tell us about your project, describe what moves you and why this is something important for your team.</p>
+
<html>
−
 
+
<style>
−
 
+
−
<h5>What should this page contain?</h5>
+
−
<ul>
+
−
<li> A clear and concise description of your project.</li>
+
−
<li>A detailed explanation of why your team chose to work on this particular project.</li>
+
−
<li>References and sources to document your research.</li>
+
−
<li>Use illustrations and other visual resources to explain your project.</li>
+
−
</ul>
+
−
 
+
−
 
+
−
</div>
+
−
 
+
−
<div class="column full_size" >
+
−
 
+
−
<h5>Advice on writing your Project Description</h5>
+
−
 
+
−
<p>
+
−
We encourage you to put up a lot of information and content on your wiki, but we also encourage you to include summaries as much as possible. If you think of the sections in your project description as the sections in a publication, you should try to be consist, accurate and unambiguous in your achievements.  
+
−
</p>
+
−
 
+
−
<p>
+
−
Judges like to read your wiki and know exactly what you have achieved. This is how you should think about these sections; from the point of view of the judge evaluating you at the end of the year.
+
−
</p>
+
−
 
+
−
</div>
+
−
 
+
−
 
+
−
<div class="column half_size" >
+
−
 
+
−
<h5>References</h5>
+
−
<p>iGEM teams are encouraged to record references you use during the course of your research. They should be posted somewhere on your wiki so that judges and other visitors can see how you thought about your project and what works inspired you.</p>
+
−
 
+
−
</div>
+
−
 
+
−
 
+
−
<div class="column half_size" >
+
−
<h5>Inspiration</h5>
+
−
<p>See how other teams have described and presented their projects: </p>
+
−
 
+
−
<ul>
+
−
<li><a href="https://2014.igem.org/Team:Imperial/Project"> Imperial</a></li>
+
−
<li><a href="https://2014.igem.org/Team:UC_Davis/Project_Overview"> UC Davis</a></li>
+
−
<li><a href="https://2014.igem.org/Team:SYSU-Software/Overview">SYSU Software</a></li>
+
−
</ul>
+
−
</div>
+
−
 
+
−
 
+
  
 +
#sideMenu, #top_title {display:none;}
 +
body {background-color:white; }
 +
#content { padding:0px; width:100%; margin-top: -125px; margin-left:0px;}
 +
#bodyContent h1, #bodyContent h2, #bodyContent h3, #bodyContent h4, #bodyContent h5 { margin-bottom: 0px; }
 +
</style>
 +
     
 +
     
 +
          <section class="experience bg-midnight-blue">
 +
            <div class="container">
 +
                <div class="row">
 +
                    <div class="col-sm-10">
 +
                        <h3>Part Improvement</h3>
 +
<p> RFP-UV (K1673101) had improved characterization in terms of UV irradiation. It was tested through qPCR and immunoblotting, which showed significant decreases in mutation levels in comparison to E1010. Please see the registry page for this part for full characterization and creation. </p>
 
</html>
 
</html>

Revision as of 03:56, 20 October 2016

Part Improvement

RFP-UV (K1673101) had improved characterization in terms of UV irradiation. It was tested through qPCR and immunoblotting, which showed significant decreases in mutation levels in comparison to E1010. Please see the registry page for this part for full characterization and creation.