|
|
| Line 87: |
Line 87: |
| | <div class="span3 bs-docs-sidebar"> | | <div class="span3 bs-docs-sidebar"> |
| | <ul class="nav nav-list" data-spy="affix" data-offset-top="200"> | | <ul class="nav nav-list" data-spy="affix" data-offset-top="200"> |
| - | <li class="nav-header">Circuit Registry</li> | + | <li class="nav-header">Tutorial</li> |
| - | <li class="active"><a href="#introduction">Introduction</a></li>
| + | <li class="active"><a href="#mindroad">Mind Road</a></li> |
| - | <li><a href="#mindroad">Mind Road</a></li> | + | |
| | <li><a href="#lgd">LGD</a></li> | | <li><a href="#lgd">LGD</a></li> |
| - | <li><a href="#tutorial">Tutorail</a></li> | + | <li><a href="#ttec">TTEC</a></li> |
| - | <li><a href="#future">Future Plan</a></li>
| + | <li><a href="#circuit">Circuit List</a></li> |
| - | <li><a href="#feedback">Feedback</a></li> | + | |
| | </ul> | | </ul> |
| | </div> | | </div> |
| | <div class="span9"> | | <div class="span9"> |
| - | <h2 id="introduction">Introduction</h2>
| + | <h1>Tutorial</h1> |
| | + | <div id="mindroad"> |
| | <h3>Mind Road</h3> | | <h3>Mind Road</h3> |
| - | <p>A useful net structural mind map to help users know what the existing synthetic biology projects and what else they can do.</p> | + | <h4></h4> |
| | + | </h4><a href="https://static.igem.org/mediawiki/2013/6/6e/Tutorial_circuit_registry.pdf">Download the Tutorial</a></h4> |
| | + | </div> |
| | + | <div id="lgd"> |
| | <h3>LGD</h3> | | <h3>LGD</h3> |
| - | <p>Short for logical genetic designer, LGD is a genetic circuit CAD that can present the detail information of the engineering bacteria and “calculate” the relationship of related parts based on our database.</p> | + | <h4></h4> |
| | + | </h4><a href="">Download the Tutorial</a></h4> |
| | + | </div> |
| | + | <div id="ttec"> |
| | <h3>TTEC</h3> | | <h3>TTEC</h3> |
| - | <p>TTEC is the abbreviation of Transcriptional Terminator Efficiency Calculator. It is the last year’s project of SUSTC and can calculate the efficiency of a terminator. TTEC plays an important role of building up our synthetic biology community in the future.</p> | + | <h4></h4> |
| - | | + | </h4><a href="https://static.igem.org/mediawiki/2013/1/10/Tutorial_TTEC_clotho.pdf">Download the Tutorial</a></h4> |
| - | <h2 id="circuit">Circuit Registry</h2>
| + | </div> |
| - | <h4>Mind Road</h4> | + | <div id="circuit"> |
| - | <p>We want to establish a user-friendly web2.0 platform which can function as both a handy tool kit and a community. There are mainly 3 reasons that we choose a webpage instead of a native application. First, current software need to users don’t need to download our software. Second, a webpage is not limited with the system, which means users can log in our webpage wherever they can reach the internet. And the last, all the information can be stored by the cloud, so users don’t have to worry about their information being lost.</p>
| + | <h3>Circuit List</h3> |
| - | <h4>Circuit List</h4>
| + | <h4></h4> |
| - | <p>We want to establish a user-friendly web2.0 platform which can function as both a handy tool kit and a community. There are mainly 3 reasons that we choose a webpage instead of a native application. First, current software need to users don’t need to download our software. Second, a webpage is not limited with the system, which means users can log in our webpage wherever they can reach the internet. And the last, all the information can be stored by the cloud, so users don’t have to worry about their information being lost.</p>
| + | </h4><a href="https://static.igem.org/mediawiki/2013/7/7b/Tutorial_circuit_list_clotho.pdf">Download the Tutorial</a></h4> |
| - | <h2 id="lgd">LGD</h2>
| + | </div> |
| - | <p>We want to establish a user-friendly web2.0 platform which can function as both a handy tool kit and a community. There are mainly 3 reasons that we choose a webpage instead of a native application. First, current software need to users don’t need to download our software. Second, a webpage is not limited with the system, which means users can log in our webpage wherever they can reach the internet. And the last, all the information can be stored by the cloud, so users don’t have to worry about their information being lost.</p> | + | |
| - | <h2 id="ttec">TTEC on Clotho</h2> | + | |
| - | <p>We want to establish a user-friendly web2.0 platform which can function as both a handy tool kit and a community. There are mainly 3 reasons that we choose a webpage instead of a native application. First, current software need to users don’t need to download our software. Second, a webpage is not limited with the system, which means users can log in our webpage wherever they can reach the internet. And the last, all the information can be stored by the cloud, so users don’t have to worry about their information being lost.</p>
| + | |
| - | <h2 id="tutorial">Tutorial</h2>
| + | |
| - | <p>We want to establish a user-friendly web2.0 platform which can function as both a handy tool kit and a community. There are mainly 3 reasons that we choose a webpage instead of a native application. First, current software need to users don’t need to download our software. Second, a webpage is not limited with the system, which means users can log in our webpage wherever they can reach the internet. And the last, all the information can be stored by the cloud, so users don’t have to worry about their information being lost.</p>
| + | |
| - | <h2 id="feedback">Feedback</h2>
| + | |
| - | <p>We want to establish a user-friendly web2.0 platform which can function as both a handy tool kit and a community. There are mainly 3 reasons that we choose a webpage instead of a native application. First, current software need to users don’t need to download our software. Second, a webpage is not limited with the system, which means users can log in our webpage wherever they can reach the internet. And the last, all the information can be stored by the cloud, so users don’t have to worry about their information being lost.</p>
| + | |
| - | <h2 id="safety">Safety Form</h2>
| + | |
| - | <p>We want to establish a user-friendly web2.0 platform which can function as both a handy tool kit and a community. There are mainly 3 reasons that we choose a webpage instead of a native application. First, current software need to users don’t need to download our software. Second, a webpage is not limited with the system, which means users can log in our webpage wherever they can reach the internet. And the last, all the information can be stored by the cloud, so users don’t have to worry about their information being lost.</p>
| + | |
| - | <h2 id="achievement">Achievement</h2>
| + | |
| - | <p>We want to establish a user-friendly web2.0 platform which can function as both a handy tool kit and a community. There are mainly 3 reasons that we choose a webpage instead of a native application. First, current software need to users don’t need to download our software. Second, a webpage is not limited with the system, which means users can log in our webpage wherever they can reach the internet. And the last, all the information can be stored by the cloud, so users don’t have to worry about their information being lost.</p>
| + | |
| | </div> | | </div> |
| | </div> | | </div> |
"
