Difference between revisions of "Team:CU-Boulder"

 
(129 intermediate revisions by the same user not shown)
Line 1: Line 1:
−
 
 
{{Team:CU-Boulder/Templates/Navigation}}
 
{{Team:CU-Boulder/Templates/Navigation}}
  
 
<html>
 
<html>
 +
 +
<style>
 +
 +
@media(max-width: 1200px) {
 +
 +
section > titleImageOne { display: none; }
 +
section > titleSmallImageTwo { display: none; }
 +
section > titleSmallImageTwoFlipped { display: none; }
 +
 +
}
 +
 +
@media (max-width: 800px) {
 +
section { flex-wrap: wrap; }
 +
 +
}
 +
 +
body{
 +
  background-color: black;
 +
}
 +
 +
@keyframes fade-in{
 +
  from{ border: solid rgba(255,255,255,0);}
 +
  to{border: solid rgba(255,255,255,1);}
 +
}
 +
 +
background, html{
 +
  background-color: black;
 +
}
 +
 +
section {
 +
  height:100vh;
 +
  position:relative;
 +
  justify-content: center;
 +
  display: flex;
 +
  flex-wrap: nowrap;
 +
  align-items: center;
 +
  background-color: black;
 +
}
 +
 +
section > divOne {
 +
 +
  padding-left: 30px;
 +
  padding-right: 30px;
 +
  padding-bottom: 50px;
 +
  padding-top: 50px;
 +
  font-size: 60px;
 +
  font-family: inconsolata, sans-serif;
 +
  font-weight:bold;
 +
  border: solid;
 +
  border-color: white;
 +
  color: white;
 +
  text-align:center;
 +
  animation-name: fade-in;
 +
  animation-duration: 1s;
 +
  animation-direction: alternate;
 +
  animation-iteration-count: infinite;
 +
}
 +
 +
section > titleImageOne img{
 +
    max-width: 400px;
 +
    transform: scaleX(-1);
 +
    filter: FlipV;
 +
 +
}
 +
section > titleImageTwo img{
 +
    max-width: 250px;
 +
    margin-right: 50px;
 +
    margin-bottom: 80px;
 +
 +
}
 +
 +
section > titleSmallImageTwo img{
 +
    max-width: 100px;
 +
    margin-top: 150px;
 +
    transform: scaleX(-1);
 +
    filter: FlipH;
 +
  overflow: hidden;
 +
 +
}
 +
 +
section > titleSmallImageTwoFlipped img{
 +
    max-width: 100px;
 +
    margin-bottom: 150px;
 +
    overflow: hidden;
 +
 +
}
 +
 +
section > titleImageTwoFlipped img{
 +
    max-width: 250px;
 +
    margin-left: 50px;
 +
    margin-top: 80px;
 +
    transform: scaleX(-1);
 +
    filter: FlipH;
  
  
−
<div class="column full_size" >
+
}
−
<img src="http://placehold.it/2000x300/d3d3d3/f2f2f2">
+
section > titleImageThree img{
−
</div>
+
    max-width: 700px;
  
 +
}
  
 +
section > titleImageThreeFlipped img {
 +
    max-width: 700px;
 +
    transform: scaleX(-1);
 +
    filter: FlipH;
 +
}
  
−
<div class="column full_size" >
+
section > twoCells{
−
<h1> Project Description </h1>
+
    background: radial-gradient(red, yellow, green);
−
<p>Bacterial Micro-compartments (BMCs) exist naturally in cells as protein “cages” which encapsulate different chemical reactions within bacteria. BMCs have many potential research and medical applications including concentrating reactions within cells and novel drug delivery. In order to apply BMCs in a functional way, they need to be opened and closed on command. To achieve this, we have integrated a non-canonical “light activated” photo switching amino acid, name AzoPhe, into the ethanolamine utilization (Eut) BMC.  AzoPhe contains a photo switching molecule called azobenzene that when exposed to certain wavelengths of light will change its physical conformation. Depending on its cis and trans conformation, Azobenzene may be able to offer steric hindrance in core locations of the Eut BMC. Through modeling and site directed mutagenesis, potential sites for azobenzene can be tested to open and close the Eut compartment. We are continuing our previous research to improve the stability of the compartments and adjust fluorescent cargo so that it does not interfere with the AzoPhe activation.  </p>
+
    max-width: 600px;
−
</div>
+
  
−
<div class="clear"></div>
+
}
  
−
<div class="column half_size" >
 
−
<h5>Before you start: </h5>
 
−
<p> Please read the following pages:</p>
 
−
<ul>
 
−
<li>  <a href="https://2017.igem.org/Competition">Competition Hub</a> </li>
 
−
<li> <a href="https://2017.igem.org/Competition/Deliverables/Wiki">Wiki Requirements page</a></li>
 
−
<li> <a href="https://2017.igem.org/Resources/Template_Documentation">Template documentation</a></li>
 
−
</ul>
 
−
</div>
 
  
−
<div class="column half_size" >
+
@keyframes scrollUp{
−
<div class="highlight">
+
  from{opacity: 0; }
−
<h5> Styling your wiki </h5>
+
  to{opacity: 1; }
−
<p>You may style this page as you like or you can simply leave the style as it is. You can easily keep the styling and edit the content of these default wiki pages with your project information and completely fulfill the requirement to document your project.</p>
+
}
−
<p>While you may not win Best Wiki with this styling, your team is still eligible for all other awards. This default wiki meets the requirements, it improves navigability and ease of use for visitors, and you should not feel it is necessary to style beyond what has been provided.</p>
+
−
</div>
+
−
</div>
+
  
−
<div class="column full_size" >
+
.testLeft{
−
<h5> Wiki template information </h5>
+
  visibility: visible;
−
<p>We have created these wiki template pages to help you get started and to help you think about how your team will be evaluated. You can find a list of all the pages tied to awards here at the <a href="https://2017.igem.org/Judging/Pages_for_Awards">Pages for awards</a> link. You must edit these pages to be evaluated for medals and awards, but ultimately the design, layout, style and all other elements of your team wiki is up to you!</p>
+
  animation-name: scrollUp;
 +
  animation-duration: 1s;
 +
}
  
−
</div>
+
.testFinal{
 +
  animation-name: scrollUp;
 +
  animation-duration: 1s;
  
 +
}
  
 +
section > bodyHead{
 +
  text-align: justify;
 +
  font-family: inconsolata, sans-serif;
 +
  line-height: 60px;
 +
  font-size: 30px;
 +
  max-width: 750px;
 +
  color: white;
 +
  padding-bottom: 15px;
 +
  padding-top: 15px;
 +
  border-top: 2px solid white;
 +
  border-bottom: 2px solid white;
 +
  margin-right: 30px;
 +
}
  
 +
section > floatLeft{
 +
  float: left;
 +
  font-family: inconsolata, sans-serif;
 +
  font-size: 25px;
 +
  max-width: 350px;
 +
  clear: right;
 +
  color: white;
 +
  text-align: justify;
 +
  margin-right: 150px;
  
−
<div class="column half_size" >
+
}
−
<h5> Editing your wiki </h5>
+
−
<p>On this page you can document your project, introduce your team members, document your progress and share your iGEM experience with the rest of the world! </p>
+
−
<p> <a href="https://2017.igem.org/wiki/index.php?title=Team:Example&action=edit"> </a>Use WikiTools - Edit in the black menu bar to edit this page</p>
+
  
−
</div>
+
section > floatRight{
 +
  margin-left: 150px;
 +
  float: right;
 +
  font-family: inconsolata, sans-serif;
 +
  font-size: 25px;
 +
  max-width: 400px;
 +
  clear: left;
 +
  color: white;
 +
  text-align: justify;
 +
}
  
 +
section > floatLast{
 +
  float: left;
 +
  font-family: inconsolata, sans-serif;
 +
  font-size: 25px;
 +
  max-width: 400px;
 +
  text-align: justify;
 +
  clear: left;
 +
  color: white;
 +
}
  
−
<div class="column half_size" >
+
</style>
−
<h5>Tips</h5>
+
<head>
−
<p>This wiki will be your team’s first interaction with the rest of the world, so here are a few tips to help you get started: </p>
+
</head>
−
<ul>
+
<body>
−
<li>State your accomplishments! Tell people what you have achieved from the start. </li>
+
−
<li>Be clear about what you are doing and how you plan to do this.</li>
+
−
<li>You have a global audience! Consider the different backgrounds that your users come from.</li>
+
−
<li>Make sure information is easy to find; nothing should be more than 3 clicks away.  </li>
+
−
<li>Avoid using very small fonts and low contrast colors; information should be easy to read.  </li>
+
−
<li>Start documenting your project as early as possible; don’t leave anything to the last minute before the Wiki Freeze. For a complete list of deadlines visit the <a href="https://2017.igem.org/Calendar">iGEM 2017 calendar</a> </li>
+
−
<li>Have lots of fun! </li>
+
−
</ul>
+
−
</div>
+
  
  
−
<div class="column half_size" >
+
<section>
−
<h5>Inspiration</h5>
+
  <titleImageThree><img src = "https://static.igem.org/mediawiki/2017/5/5a/T-CU-Boulder--CellThree.gif"></titleImageThree>  
−
<p> You can also view other team wikis for inspiration! Here are some examples:</p>
+
−
<ul>
+
−
<li> <a href="https://2014.igem.org/Team:SDU-Denmark/"> 2014 SDU Denmark </a> </li>
+
−
<li> <a href="https://2014.igem.org/Team:Aalto-Helsinki">2014 Aalto-Helsinki</a> </li>
+
−
<li> <a href="https://2014.igem.org/Team:LMU-Munich">2014 LMU-Munich</a> </li>
+
−
<li> <a href="https://2014.igem.org/Team:Michigan"> 2014 Michigan</a></li>
+
−
<li> <a href="https://2014.igem.org/Team:ITESM-Guadalajara">2014 ITESM-Guadalajara </a></li>
+
−
<li> <a href="https://2014.igem.org/Team:SCU-China"> 2014 SCU-China </a></li>
+
−
</ul>
+
−
</div>
+
  
−
<div class="column half_size" >
+
</section>
−
<h5> Uploading pictures and files </h5>
+
  <section>
−
<p> You can upload your pictures and files to the iGEM 2017 server. Remember to keep all your pictures and files within your team's namespace or at least include your team's name in the file name. <br />
+
<divOne>  
−
When you upload, set the "Destination Filename" to <br><code>T--YourOfficialTeamName--NameOfFile.jpg</code>. (If you don't do this, someone else might upload a different file with the same "Destination Filename", and your file would be erased!)<br><br>
+
      <span style="color: red"><b>&mu;</b></span>
 +
      s t o r a g e
 +
    </divOne>
 +
</section>
  
−
<a href="https://2017.igem.org/Special:Upload">
+
<section>
−
UPLOAD FILES
+
  <bodyHead> <p id = "blah">
−
</a>
+
    Bacterial microcompartments are subcellular structures naturally produced by certain microbial populations...
−
</p>
+
    </p>
−
</div>
+
  </bodyhead>
 +
<titleImageOne><img src = "https://static.igem.org/mediawiki/2017/2/2f/T-CU-Boulder--CellOne.gif"></titleImageOne>
  
 +
</section>
 +
<section>
 +
<twoCells><img src = "https://static.igem.org/mediawiki/2017/1/12/T-CU-Boulder--TwoCells.gif"></twoCells>
 +
    <floatRight>
 +
  <p id = "blahTwo">
 +
    These compartments act in nature to either localize and concentrate substrates, or to sequester harmful metabolic intermediates...
 +
    </p>
 +
</floatRight>
 +
</section>
 +
<section>
 +
    <floatLeft>
 +
  <p id = "blahThree">
 +
    Our group has designed recombinant compartments in order to achieve remote control over the rapid assembly and dissasembly of the structures...
 +
      </p>
 +
</floatLeft>
 +
<img src = "https://static.igem.org/mediawiki/2017/4/48/T-CU-Boulder--Splosion.gif">
 +
</section>
 +
<section>
 +
<titleSmallImageTwo><img src = "https://static.igem.org/mediawiki/2017/b/b8/T-CU-Boulder--CellTwo.gif"></titleSmallImageTwo>
 +
<titleImageTwo><img src = "https://static.igem.org/mediawiki/2017/b/b8/T-CU-Boulder--CellTwo.gif"></titleImageTwo>
 +
<floatLast>
 +
  <p id = "blahFour">
 +
    Using this method...</br></br> Our compartments could potentially act as next-generation drug delivery systems, biosensors, or as a solution to sequester diffuse and harmful environmental toxins.</br></br> Continue to our project description to learn more...  </p></floatLast>
 +
<titleImageTwoFlipped><img src = "https://static.igem.org/mediawiki/2017/b/b8/T-CU-Boulder--CellTwo.gif"></titleImageTwoFlipped>
 +
<titleSmallImageTwoFlipped><img src = "https://static.igem.org/mediawiki/2017/b/b8/T-CU-Boulder--CellTwo.gif"></titleSmallImageTwoFlipped>
 +
</section>
 +
</body>
  
 
</html>
 
</html>

Latest revision as of 08:31, 20 October 2017

μ s t o r a g e

Bacterial microcompartments are subcellular structures naturally produced by certain microbial populations...

These compartments act in nature to either localize and concentrate substrates, or to sequester harmful metabolic intermediates...

Our group has designed recombinant compartments in order to achieve remote control over the rapid assembly and dissasembly of the structures...

Using this method...

Our compartments could potentially act as next-generation drug delivery systems, biosensors, or as a solution to sequester diffuse and harmful environmental toxins.

Continue to our project description to learn more...