Difference between revisions of "Team:Macquarie Australia/Description"

(Prototype team page)
 
(Added some initial text and referenced template)
Line 1: Line 1:
{{Macquarie_Australia}}
+
{{Macquarie_Australia/DescriptionCSS}}
<html>
+
<html lang="en-AU">
 +
<title>Project Description</title>
 +
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
  
<h2> Project Description </h2>
+
<body>
  
<p>Tell us about your project, describe what moves you and why this is something important for your team.</p>
+
<div class="contentContainer">
<br />
+
<h2>Project Description</h2>
 +
<p>Our project has its focus on photosynthesis - the natural process where plants and algae convert sunlight into useable energy. By developing artificial photosynthesis in a biological system we can better harvest the unlimited supply of solar energy. The long-term goal is to engineer bacteria that can produce hydrogen gas on an industrial scale.</p>
 +
<p>This year the aim of our team is to engineer bacteria to manufacture chlorophyll, the primary molecule of photosynthesis. Chlorophyll harvests light and is involved in the excitation transfer of energy. Chlorophyll-<i>a</i> can be synthesised via a pathway from the protoporphyrin-IX molecule. By placing 13 genes into 3 biobrick vectors we can recreate the pathway in <i>Escherichia coli</i>.</p>
 +
</div> <!-- contentContainer end -->
  
<h5>What should this page contain?</h5>
+
</body>
<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>
+
 
+
 
+
<br />
+
<h4>Advice on writing your Project Description</h4>
+
 
+
<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>
+
 
+
 
+
<br />
+
<h4>References</h4>
+
<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 though about your project and what works inspired you.</p>
+
 
+
 
+
 
+
<h4>Inspiration</h4>
+
<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>
+
 
</html>
 
</html>

Revision as of 15:08, 14 July 2015