Difference between revisions of "Team:Edinburgh UG/Description"

(Prototype team page)
 
Line 1: Line 1:
{{Edinburgh_UG}}
 
 
<html>
 
<html>
 +
<head>
 +
<style>
 +
.container {
 +
    overflow: hidden;
 +
    background-color: #0A1E3F;
 +
    font-family: fantasy;
 +
    position: fixed;
 +
    top: 0;
 +
    width: 100%;
 +
    margin-top: 10px;
 +
}
  
 +
.container a {
 +
    float: left;
 +
    font-family: fantasy;
 +
    font-size: 16px;
 +
    color: white;
 +
    text-align: center;
 +
    padding: 18px 16px;
 +
    text-decoration: none;
 +
}
  
 +
.dropdown {
 +
    float: left;
 +
    font-family: fantasy;
 +
    overflow: hidden;
  
<div class="column full_size">
+
}
<h1>Description</h1>
+
  
<p>Tell us about your project, describe what moves you and why this is something important for your team.</p>
+
.dropdown .dropbtn {
 +
    font-size: 16px;   
 +
    border: none;
 +
    outline: none;
 +
    color: white;
 +
    background-color: inherit;
 +
    padding: 16px 16px;
 +
    font-family: fantasy;
 +
}
  
 +
.container a:hover, .dropdown:hover .dropbtn {
 +
    background-color: red;
 +
    font-family: fantasy;
 +
    font-size: 22px;   
 +
}
  
<h5>What should this page contain?</h5>
+
.dropdown-content {
<ul>
+
    display: none;
<li> A clear and concise description of your project.</li>
+
    position: absolute;
<li>A detailed explanation of why your team chose to work on this particular project.</li>
+
    background-color: #f9f9f9;
<li>References and sources to document your research.</li>
+
    min-width: 160px;
<li>Use illustrations and other visual resources to explain your project.</li>
+
    box-shadow: 0px 8px 16px 0px rgba(0,0,0,0.2);
</ul>
+
    z-index: 1;
 +
    position: fixed;
  
 +
}
  
</div>
+
.dropdown-content a {
 +
    float: none;
 +
    color: black;
 +
    padding: 16px 16px;
 +
    text-decoration: none;
 +
    display: block;
 +
    text-align: left;
 +
}
  
<div class="column full_size" >
+
.dropdown-content a:hover {
 +
    background-color: #ddd;
 +
}
  
<h5>Advice on writing your Project Description</h5>
+
.dropdown:hover .dropdown-content {
 +
    display: block;
 +
}
  
<p>
+
p.general {
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.  
+
    font-style: italic;
</p>
+
    font-weight: 50;
 +
    color:#0A1E3F;
 +
    padding-left: 30px;
 +
    padding-right: 30px;
  
<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>
+
p.topic {
 +
    font-style: oblique;
 +
    font-weight: bold;
 +
    color:#0A1E3F;
 +
    padding-top: 50px;
 +
    padding-bottom: 20px;
 +
}
  
 +
/* Clear the default wiki settings */
 +
 +
#home_logo, #sideMenu { display:none; }
 +
#sideMenu, #top_title, .patrollink  {display:none;}
 +
#content { width:100%; padding:0px;  margin-top:-7px; margin-left:0px;}
 +
body {background-color:white; }
 +
#bodyContent h1, #bodyContent h2, #bodyContent h3, #bodyContent h4, #bodyContent h5 { margin-bottom: 0px; }
 +
</style>
 +
</head>
  
<div class="column half_size" >
+
<body>
 
+
<div class="container">
<h5>References</h5>
+
  <a href=/Team:Edinburgh_UG>Home</a>
<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 class="dropdown">
 
+
    <button class="dropbtn">Team</button>
 +
    <div class="dropdown-content">
 +
      <a href=/Team:Edinburgh_UG/Team>Team</a>
 +
      <a href=/Team:Edinburgh_UG/Collaborations>Collaborations</a>
 +
    </div>
 +
  </div>
 +
  <div class="dropdown">
 +
    <button class="dropbtn">Projects</button>
 +
    <div class="dropdown-content">
 +
        <a href=/Team:Edinburgh_UG/Description>Description</a>
 +
        <a href=/Team:Edinburgh_UG/Design>Design</a>
 +
        <a href=/Team:Edinburgh_UG/Experiments>Experiments</a>
 +
        <a href=/Team:Edinburgh_UG/Notebook>Notebook</a>
 +
        <a href=/Team:Edinburgh_UG/InterLab>InterLab</a>
 +
        <a href=/Team:Edinburgh_UG/Contribution>Contribution</a>
 +
        <a href=/Team:Edinburgh_UG/Model>Model</a>
 +
        <a href=/Team:Edinburgh_UG/Results>Results</a>
 +
        <a href=/Team:Edinburgh_UG/Demonstrate>Demonstrate</a>
 +
        <a href=/Team:Edinburgh_UG/Improve>Improve</a>
 +
        <a href=/Team:Edinburgh_UG/Attributions>Attributions</a>
 +
    </div>
 +
  </div>
 +
  <div class="dropdown">
 +
    <button class="dropbtn">Parts</button>
 +
    <div class="dropdown-content">
 +
        <a href=/Team:Edinburgh_UG/Parts>Parts</a>
 +
        <a href=/Team:Edinburgh_UG/Basic_Part>Basic Parts</a>
 +
        <a href=/Team:Edinburgh_UG/Composite_Part>Composite Parts</a>
 +
        <a href=/Team:Edinburgh_UG/Part_Collection>Part Collection</a>
 +
    </div>
 +
  </div>
 +
  <a href=/Team:Edinburgh_UG/Safety>Safety</a>
 +
  <div class="dropdown">
 +
      <button class="dropbtn">Human Practices</button>   
 +
      <div class="dropdown-content">
 +
        <a href=/Team:Edinburgh_UG/HP/Silver>Silver HP</a>
 +
        <a href=/Team:Edinburgh_UG/HP/Gold_Integrated>Integrated and Gold</a>
 +
        <a href=/Team:Edinburgh_UG/HP/Engagement>Public Engagement</a>
 +
      </div>
 +
  </div>
 +
  <div class="dropdown">
 +
      <button class="dropbtn">Awards</button>   
 +
      <div class="dropdown-content">
 +
        <a href=/Team:Edinburgh_UG/Applied_Design>Applied Design</a>
 +
        <a href=/Team:Edinburgh_UG/Entrepreneurship>Entrepreneurship</a>
 +
        <a href=/Team:Edinburgh_UG/Hardware>Hardware</a>
 +
        <a href=/Team:Edinburgh_UG/Measurement>Measurement</a>
 +
        <a href=/Team:Edinburgh_UG/Model>Model</a>
 +
        <a href=/Team:Edinburgh_UG/Plant>Plant</a>
 +
        <a href=/Team:Edinburgh_UG/Software>Software</a>
 +
      </div>
 +
  </div> 
 
</div>
 
</div>
  
  
<div class="column half_size" >
+
<div class="column full_size" >
<h5>Inspiration</h5>
+
<p>See how other teams have described and presented their projects: </p>
+
  
<ul>
+
<p class="topic" style="text-align:center;font-size:350%;font-family:serif">Project Description</p>
<li><a href="https://2016.igem.org/Team:Imperial_College/Description">2016 Imperial College</a></li>
+
<p class="general" style="text-align:center;font-size:170%;font-family:serif;">Many commercially important chemicals are manufactured with the help of microbes. These microbes are often genetically modified so that they are equipped with the necessary enzymes to produce those chemicals. However, there are millions of species in nature, each carrying their own version of enzymes. Which one should we choose to put into the microbes?
<li><a href="https://2016.igem.org/Team:Wageningen_UR/Description">2016 Wageningen UR</a></li>
+
To answer this questions, researchers normally test these enzymes – or combinations of enzymes – one by one to see if they work well in the microbe. As you may imagine, this is very labour-intensive and time-consuming, even with the help of automated systems. Therefore, we, the Homologics team, are developing a highly-adaptable method to speed up this process.</p>
<li><a href="https://2014.igem.org/Team:UC_Davis/Project_Overview"> 2014 UC Davis</a></li>
+
<li><a href="https://2014.igem.org/Team:SYSU-Software/Overview">2014 SYSU Software</a></li>
+
</ul>
+
 
</div>
 
</div>
 
+
</body>
 
+
  
 
</html>
 
</html>

Revision as of 12:31, 27 June 2017

Project Description

Many commercially important chemicals are manufactured with the help of microbes. These microbes are often genetically modified so that they are equipped with the necessary enzymes to produce those chemicals. However, there are millions of species in nature, each carrying their own version of enzymes. Which one should we choose to put into the microbes? To answer this questions, researchers normally test these enzymes – or combinations of enzymes – one by one to see if they work well in the microbe. As you may imagine, this is very labour-intensive and time-consuming, even with the help of automated systems. Therefore, we, the Homologics team, are developing a highly-adaptable method to speed up this process.