Team:Lethbridge

From 2013.igem.org

(Difference between revisions)
(Prototype team page)
 
(37 intermediate revisions not shown)
Line 1: Line 1:
-
<!-- *** What falls between these lines is the Alert Box!  You can remove it from your pages once you have read and understood the alert *** -->
+
{{TeamLethbridgeHead}}
 +
<div style="background-color:#FFFFFF; color:white">
 +
<html><br>
 +
<center><a href="http://2013.igem.org/Team:Lethbridge/project"><image src="http://2013.igem.org/wiki/images/0/05/ULeth2013iGEM_Mainpage_PKFig.png" width="600px" height="400px"/></a></center>
-
<html>
+
<style>
-
<div id="box" style="width: 700px; margin-left: 137px; padding: 5px; border: 3px solid #000; background-color: #fe2b33;">
+
div
-
<div id="template" style="text-align: center; font-weight: bold; font-size: large; color: #f6f6f6; padding: 5px;">
+
{
-
This is a template page. READ THESE INSTRUCTIONS.
+
text-align:justify;
-
</div>
+
text-justify:inter-word;
-
<div id="instructions" style="text-align: center; font-weight: normal; font-size: small; color: #f6f6f6; padding: 5px;">
+
}
-
You are provided with this team page template with which to start the iGEM season.  You may choose to personalize it to fit your team but keep the same "look." Or you may choose to take your team wiki to a different level and design your own wiki.  You can find some examples <a href="http://2009.igem.org/Help:Template/Examples">HERE</a>.
+
</style>
-
</div>
+
-
<div id="warning" style="text-align: center; font-weight: bold; font-size: small; color: #f6f6f6; padding: 5px;">
+
-
You <strong>MUST</strong> have all of the pages listed in the menu below with the names specified. PLEASE keep all of your pages within your teams namespace. 
+
-
</div>
+
-
</div>
+
-
</html>
+
-
<!-- *** End of the alert box *** -->
 
 +
<BLOCKQUOTE>
 +
<h2>Project Overview</h2>
 +
<p style="color:black">This year, the Lethbridge iGEM team is working to bring a whole new class of parts to the iGEM community: programmed ribosomal frameshifting elements. To do this, we have been working towards standardizing the PK401 pseudoknot for use within the BioBrick system. These RNA secondary structural elements cause the ribosome to switch between translational frames and give another degree of freedom when engineering genetic circuits.</p><br>
-
{|align="justify"
+
<b style="color:black"><u>WHAT?</u></b>
-
|You can write a background of your team here.  Give us a background of your team, the members, etc.  Or tell us more about something of your choosing.
+
<ul style="color:black"><li>Our project is directed towards standardizing pseudoknots to make a new class of parts available to the synthetic biology community</li></ul>
-
|[[Image:Lethbridge_logo.png|200px|right|frame]]
+
-
|-
+
-
|
+
-
''Tell us more about your project.  Give us background.  Use this as the abstract of your project.  Be descriptive but concise (1-2 paragraphs)''
+
-
|[[Image:Lethbridge_team.png|right|frame|Your team picture]]
+
-
|-
+
-
|
+
-
|align="center"|[[Team:Lethbridge | Team Lethbridge]]
+
-
|}
+
-
<!--- The Mission, Experiments --->
+
<br>
 +
<b style="color:black"><u>WHY?</u></b>
 +
<ul style="color:black"><li>As the field of synthetic biology grows, so should its toolset. By introducing a standardized method of implementing programmed ribosomal frameshifts in synthetic gene networks, we could not only enable others to reduce plasmid size and regulate operon expression, but also enable them to come up with new, exciting applications</li></ul>
-
{| style="color:#1b2c8a;background-color:#0c6;" cellpadding="3" cellspacing="1" border="1" bordercolor="#fff" width="62%" align="center"
+
<br>
-
!align="center"|[[Team:Lethbridge|Home]]
+
<b style="color:black"><u>HOW?</b></u>
-
!align="center"|[[Team:Lethbridge/Team|Team]]
+
<ul style="color:black"><li>We have brought pseudoknots to the iGEM community by:
-
!align="center"|[http://igem.org/Team.cgi?year=2013&team_name=Lethbridge Official Team Profile]
+
<ul><li>Characterizing their function in a biobrick system</li>
-
!align="center"|[[Team:Lethbridge/Project|Project]]
+
<li>Designing software that enables others to dual code proteins</li>
-
!align="center"|[[Team:Lethbridge/Parts|Parts Submitted to the Registry]]
+
<li>Ensuring that the release of these tools to the wider public does not pose a significant risk to the rest of the world</li></li></ul></ul><br>
-
!align="center"|[[Team:Lethbridge/Modeling|Modeling]]
+
 
-
!align="center"|[[Team:Lethbridge/Notebook|Notebook]]
+
 
-
!align="center"|[[Team:Lethbridge/Safety|Safety]]
+
<h2>Sponsors</h2>
-
!align="center"|[[Team:Lethbridge/Attributions|Attributions]]
+
<br>
-
|}
+
<p><center><image src="http://2013.igem.org/wiki/images/0/00/ULeth2013_Sponsors_-_Platinum.png"; width="200px"; height="100px" />&nbsp;&nbsp;&nbsp;&nbsp;
 +
 
 +
<image src="http://2013.igem.org/wiki/images/1/1e/ULeth2013_Sponsors_-_Silver.png"; width="200px"; height="100px" />&nbsp;&nbsp;&nbsp;&nbsp;
 +
 
 +
<image src="http://2013.igem.org/wiki/images/4/4c/ULeth2013_Sponsors_-_Bronze.png"; width="300px"; height="100px" /></center></p>&nbsp;&nbsp;&nbsp;&nbsp;
 +
</html>

Latest revision as of 03:35, 28 September 2013


Project Overview

This year, the Lethbridge iGEM team is working to bring a whole new class of parts to the iGEM community: programmed ribosomal frameshifting elements. To do this, we have been working towards standardizing the PK401 pseudoknot for use within the BioBrick system. These RNA secondary structural elements cause the ribosome to switch between translational frames and give another degree of freedom when engineering genetic circuits.


WHAT?
  • Our project is directed towards standardizing pseudoknots to make a new class of parts available to the synthetic biology community

WHY?
  • As the field of synthetic biology grows, so should its toolset. By introducing a standardized method of implementing programmed ribosomal frameshifts in synthetic gene networks, we could not only enable others to reduce plasmid size and regulate operon expression, but also enable them to come up with new, exciting applications

HOW?
  • We have brought pseudoknots to the iGEM community by:
    • Characterizing their function in a biobrick system
    • Designing software that enables others to dual code proteins
    • Ensuring that the release of these tools to the wider public does not pose a significant risk to the rest of the world

Sponsors