|
|
| Line 1: |
Line 1: |
| − | {{Tianjin}} | + | {{:Team:Tianjin/Templates/leftbar}} |
| | <html> | | <html> |
| | + | <head> |
| | + | <link href="https://2017.igem.org/Team:Tianjin/Resources/CSS:maincss?action=raw&ctype=text/css |
| | + | " rel="stylesheet"> |
| | | | |
| | + | </head> |
| | + | <body> |
| | | | |
| | + | <div class="page-template-default page page-id-441 group-blog"> |
| | | | |
| − | <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>
| |
| | | | |
| | | | |
| − | <h5>What should this page contain?</h5> | + | <div id="page" class="hfeed site"> |
| − | <ul> | + | <a class="skip-link screen-reader-text" href="#content">Skip to content</a> |
| − | <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> | + | |
| | | | |
| | + | |
| | + | <div id="primary" class="content-area"> |
| | + | <main id="main" class="about-main" role="main"> |
| | | | |
| − | </div> | + | <article class="process"> |
| | + | <h1>Process</h1> |
| | + | <hr /> |
| | + | <p>Creativity can be enigmatic, making it all the more important to stay focused. A clear process makes for efficient use of time, and ensures that the end product delivers value.<br /> |
| | + | <div class='content-column full_width'><div style="padding-top:1em;padding-bottom:3em;"><img class="aligncenter wp-image-594 size-full" src="picture/aboutpage_bars_6.gif" alt="AboutPage_bars_6" width="68" height="73" /></div></div><div class='content-column one_fourth'><div style="padding-right:1em;"><h2>1</h2> |
| | + | <h3>Define</h3> |
| | + | <p>We always begin by looking closely at the problem that needs solving. Tapping into your knowledge we establish clear and measurable objectives.</div></div><div class='content-column one_fourth'><div style="padding-right:1em;padding-left:1em;"><h2>2</h2> |
| | + | <h3>Explore</h3> |
| | + | <p>With clear goals set we explore lots of ideas in an organic and playful way. This is when unexpected things happen and how we find a fresh angle.</div></div><div class='content-column one_fourth'><div style="padding-right:1em;padding-left:1em;"><h2>3</h2> |
| | + | <h3>Refine</h3> |
| | + | <p>Through critique and discussion we evaluate the ideas until one starts to stand out. It is then refined and rigorously tested across all contexts.<br /></div></div><div class='content-column one_fourth last_column'><div style="padding-left:1em;"><h2>4</h2> |
| | + | <h3>Deliver</h3> |
| | + | <p>Delivering on time and on budget is as important to us as every lovely pixel we place. That means going to every length to provide what you need, when you need it.<br /></div></div> |
| | + | <div class='clear_column'></div></p> |
| | + | </article> |
| | | | |
| − | <div class="column full_size" >
| |
| | | | |
| − | <h5>Advice on writing your Project Description</h5>
| |
| | | | |
| − | <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> | + | |
| | + | </main><!-- #main --> |
| | + | </div><!-- #primary --> |
| | | | |
| − | <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>
| |
| − |
| |
| − |
| |
| − | <div class="column half_size" >
| |
| − |
| |
| − | <h5>References</h5>
| |
| − | <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>
| |
| − |
| |
| − |
| |
| − | <div class="column half_size" >
| |
| − | <h5>Inspiration</h5>
| |
| − | <p>See how other teams have described and presented their projects: </p>
| |
| − |
| |
| − | <ul>
| |
| − | <li><a href="https://2016.igem.org/Team:Imperial_College/Description">2016 Imperial College</a></li>
| |
| − | <li><a href="https://2016.igem.org/Team:Wageningen_UR/Description">2016 Wageningen UR</a></li>
| |
| − | <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>
| |
| | | | |
| | | | |
| | | | |
| | </html> | | </html> |
