Difference between revisions of "Team:Duke/Description"
m |
|||
| Line 26: | Line 26: | ||
</p> | </p> | ||
</div> | </div> | ||
| + | <div class="column full_size"> | ||
<h2>References</h2> | <h2>References</h2> | ||
<p>Our project aims to engineer E. coli to produce Taxol. Mention building on the work of the 2016 Duke iGEM team. </p> | <p>Our project aims to engineer E. coli to produce Taxol. Mention building on the work of the 2016 Duke iGEM team. </p> | ||
Revision as of 16:00, 25 June 2018
Description
Tell us about your project, describe what moves you and why this is something important for your team.
Why is Taxol important?
Taxol is...
Why is biosynthesis of Taxol necessary?
Taxol is currently produced...the problem with this is...
What are we doing?
Our project aims to engineer E. coli to produce Taxol. Mention building on the work of the 2016 Duke iGEM team.
References
Our project aims to engineer E. coli to produce Taxol. Mention building on the work of the 2016 Duke iGEM team.
What should this page contain?
- A clear and concise description of your project.
- A detailed explanation of why your team chose to work on this particular project.
- References and sources to document your research.
- Use illustrations and other visual resources to explain your project.
Inspiration
See how other teams have described and presented their projects:
Advice on writing your Project Description
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 concise, accurate, and unambiguous in your achievements.
References
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.