Team:NCTU Formosa

From 2013.igem.org

(Difference between revisions)

Revision as of 07:24, 26 September 2013

E.colightuner

by NCTU_Formosa

Like a tuner, we wanted to construct a E.coli which can produce different products as environment changes. By using factors like small RNA, light and temperature, a multiple regulated-system can be achieved.

First, we have proven that a sRNA we designed is an effective and competent way for regulating gene expressions.

Second, a light-regulated system have been built by a new biobrick called P_red. In the presence of red light, it can turn on the downstream gene and vice verso.

Third, by using the characteristic of RNA thermometer, we constructed a temperature-regulated system. It is an RBS which is able to detect certain temperature and change its mRNA secondary structure.

In conclusion, combining these three regulated-system, a multitask machine — a manipulatable system, which is capable of expressing four different genes under different conditions — is available.

Bringing back wiki the way what it was meant to be.

The core value of wiki are the openness and its coeditable property. As people tried to beautify the pages, too often that the wiki becomes merely a work handled by one person. It digresses from the core value of wiki. Therefore, to bring back its role, we build a system not only more user-friendly and eye-pleasing but also coeditable and smart.

We believe that wiki is a platform for the iGEMers and the future iGEMers. It stands for sharing. It is meant for cooperation. It ought to be a stage that brings people together for knowledge and the value that lies with people.

Utilizing wiki markup language and BioBricks registry

To layout the pages, the wiki site is often completely written by HTML rather than the expected wiki markup language. We believe that wiki language encourages users to be more involved into the project since it's easy to use. Thus, we build a website letting users to edit contents by wiki language but at the same time have a cleaner layout by HTML.

What's more, for the Biobricks page, the table is directly fetched from the Biobrick Registry website. Not only it gets timely updates when new parts are registered, but it intertwines wiki and part wiki into a unique iGEM-centric system.

Responsible design that re-layouts for different resolution

Our wiki site implements a more modern method to create the layout. As the window size changes, text reflows and layout rearranges accordingly. It supports various screen size down from smartphones and up to computers. To be future-proof, it's touch-friendly and can even support large-width devices such as 4KTV!

Contents in wiki are easily editable

When iGEMers log into 2013.igem.org, "Edit" link for each sections appears automatically. Users can click into specific section to modify it. The history log of the page (link located at the top of the screen) can show the section modified and the user who modified it. Since editing contents becomes so straight-forward, our team members edit it spontaneously. We believe the coeditability suggests the spirit of cooperating and sharing, which are what wiki ought to be and the reason why iGEM lets us show our project upon wiki. Please check out the history log of our project page.

User-friendly functions

To elevate the user experience, we introduce a submenu that fix on the screen when scrolling though the page. It serves as a normal menu that links to each section. So what's special about it? It is so smart that it shows the place we're currently browsing, and the links to sub-section that collapsed at first will expand automatically.

We also introduce buttons for changing the font size and a button that can back to the top of the page when page is scrolled down. This wiki is also friendly for blind and visually impaired people that use screen reading softwares.

Auto-generated menu that powered by wiki system

The submenus in our wiki are auto-generated by the Mediawiki system. Since we use the wiki markup language to make our content a hierarchic structure, the system can read our structure and generate a menu correspondingly. We took a step forward and made the menu even smarter. It can now collapse and expand according to our mouse and the place we're browsing. We believe that this is what a good customization should be.

Following wiki requirements for iGEM 2013

Our wiki follows the requirements announced by iGEM. We understand that wiki serves as a resource for current and future iGEMers, so our code, images and files are all hosted on the 2013.igem.org server to prevent from data losing.

Plus, we not only put the user editing menu on the top of the screen, we also place the footer box on the bottom of every page, including creative commons logo, mediawiki logo and some links. Since these are useful information for wiki that shouldn't be hidden.

E.colightuner

Using sRNA, temperature and light, we want to construct a complicated regulation system. First, we took advantage of a powerful regulated molecules, sRNA. Bacterial small RNAs(sRNA) are small non-coding molecules, and they are highly structured and contain several stem-loops. sRNAs can either bind to protein targets, and modify the function of the bound protein , or bind to mRNA targets and regulate gene expression. Second, we used a Ribosome binding site which can sense change of temperature, 37oC RBS. Because this sequence has a unique secondary structure, it can’t function in room temperature. When temperature increasing, the secondary structure would change and can function. Third, we designed a new promoter, Pred. It is activated by red light. When removing the red light, it would be turned off, so we use this promoter to strengthen our project. By these important factors, we can achieve the pathway regulation and do more applications.

@@ Line 29: / Line 29: @@
 		<div id="social" class="page" data-stellar-background-ratio="0.5">
 <p class="bigtitle">Bringing back <span class="em">wiki</span> <span class="em2">the way what it was meant to be.</span></p>
-<p>The core value of wiki are the openness and its coeditable property. As people tried to beautify the pages, too often that the wiki becomes merely a work handled by one person. It digresses from the core value of iGEM. Therefore, to bring back its role, we build a system not only <b>more user-friendly</b> and <b>eye-pleasing</b> but also <b>coeditable</b> and <b>smart</b>.</p>
+<p>The core value of wiki are the openness and its coeditable property. As people tried to beautify the pages, too often that the wiki becomes merely a work handled by one person. It digresses from the core value of wiki. Therefore, to bring back its role, we build a system not only <b>more user-friendly</b> and <b>eye-pleasing</b> but also <b>coeditable</b> and <b>smart</b>.</p>
 <p>We believe that wiki is a platform for the iGEMers and the future iGEMers.  It stands for sharing. It is meant for cooperation. It ought to be a stage that brings people together for knowledge and the value that lies with people.</p><div id="meritw" class="js-masonry" data-masonry-options='{ "columnWidth": 440, "itemSelector": ".merit" }'>
 <div class="merit">
 <div class="cphoto"><img src="https://static.igem.org/mediawiki/2013/4/40/Nctu-wm1.png" width="420px" height="177px"></div>
 <p class="smalltitle">Utilizing wiki markup language and BioBricks registry</p>
-<p>To layout the pages, the wiki site is often completely written by HTML rather than the originally expected wiki markup language. We believe that wiki language encourages users to be more involved into the project since it's easy to use. Thus, we build a website <b>letting users to edit contents by wiki language</b> but at the same time have a cleaner layout by HTML.</p>
+<p>To layout the pages, the wiki site is often completely written by HTML rather than the expected wiki markup language. We believe that wiki language encourages users to be more involved into the project since it's easy to use. Thus, we build a website <b>letting users to edit contents by wiki language</b> but at the same time have a cleaner layout by HTML.</p>
 <p>What's more, for the <a href="https://2013.igem.org/Team:NCTU_Formosa/biobricks">Biobricks page</a>, the table is <b>directly fetched from the Biobrick Registry website</b>. Not only it gets timely updates when new parts are registered, but it intertwines wiki and part wiki into a unique iGEM-centric system.</p>
 </div>
@@ Line 40: / Line 40: @@
 <div class="cphoto"><img src="https://static.igem.org/mediawiki/2013/c/ce/Nctu-wm2.png" width="420px" height="300px"></div>
 <p class="smalltitle">Responsible design that re-layouts for different resolution</p>
-<p>Our wiki site implements a more modern method to create the layout. As the window size changes, <b>text reflows and layout rearranges accordingly</b>. It supports various screen size down from smartphones and up to computers. To be future-proof, it's <b>touch-friendly</b> and can even support large width devices such as 4KTV!</p>
+<p>Our wiki site implements a more modern method to create the layout. As the window size changes, <b>text reflows and layout rearranges accordingly</b>. It supports various screen size down from smartphones and up to computers. To be future-proof, it's <b>touch-friendly</b> and can even support large-width devices such as 4KTV!</p>
 </div>
 <div class="merit">
 <div class="cphoto"><img src="https://static.igem.org/mediawiki/2013/1/13/Nctu-wm3.png" width="420px" height="185px"></div>
 <p class="smalltitle">Contents in wiki are easily editable</p>
-<p>When iGEMers log into 2013.igem.org, <b>"Edit" link for each sections appears automatically</b>. Users can click into specific section to modify it. The history log of the page (link located at the top of the screen) can <b>show the section modified and the user who modified it</b>. Since editing contents becomes so straight-forward, our team members edit it spontaneously. We believe the <b>coeditability suggests the spirit of cooperating and sharing</b>, which are what wiki ought to be. Please check out <a href="https://2013.igem.org/wiki/index.php?title=Team:NCTU_Formosa/project&action=history">the history log of our project page</a>.</p>
+<p>When iGEMers log into 2013.igem.org, <b>"Edit" link for each sections appears automatically</b>. Users can click into specific section to modify it. The history log of the page (link located at the top of the screen) can <b>show the section modified and the user who modified it</b>. Since editing contents becomes so straight-forward, our team members edit it spontaneously. We believe the <b>coeditability suggests the spirit of cooperating and sharing</b>, which are what wiki ought to be and the reason why iGEM lets us show our project upon wiki. Please check out <a href="https://2013.igem.org/wiki/index.php?title=Team:NCTU_Formosa/project&action=history">the history log of our project page</a>.</p>
 </div>
 <div class="merit">
@@ Line 56: / Line 56: @@
 <div class="cphoto"><img src="https://static.igem.org/mediawiki/2013/0/0e/Nctu-wm5.png" width="420px" height="185px"></div>
 <p class="smalltitle">Auto-generated menu that powered by wiki system</p>
-<p>The sub-menus in our wiki are auto-generated by the Mediawiki system. Since we use the wiki markup language to <b>make our content a hierarchic structure</b>, the system can read our structure and generate a menu. We took a step forward and made the menu even smarter. It can now collapse and expand <b>according to our mouse and the place we're browsing</b>. We believe that this is what a good customization should be.</p>
+<p>The submenus in our wiki are auto-generated by the Mediawiki system. Since we use the wiki markup language to <b>make our content a hierarchic structure</b>, the system can read our structure and generate a menu correspondingly. We took a step forward and made the menu even smarter. It can now collapse and expand <b>according to our mouse and the place we're browsing</b>. We believe that this is what a good customization should be.</p>
 </div>
 <div class="merit">
 <div class="cphoto"><img src="https://static.igem.org/mediawiki/2013/5/56/Nctu-wm6.png" width="420px" height="185px"></div>
 <p class="smalltitle">Following wiki requirements for iGEM 2013</p>
-<p>Our wiki follows <a href="https://2013.igem.org/Requirements/Wiki">the requirements</a> announced by iGEM. We understand that wiki serves as a resource for current and future iGEMers, so our code, images and files are all hosted on the 2013.igem.org server.</p>
+<p>Our wiki follows <a href="https://2013.igem.org/Requirements/Wiki">the requirements</a> announced by iGEM. We understand that wiki serves as a resource for current and future iGEMers, so our code, images and files are all hosted on the 2013.igem.org server to prevent from data losing.</p>
-<p>Plus, we not only put the user editing menu on the top of the screen, <b>we also place the footer box</b> on the bottom of every page, including creative commons logo, mediawiki logo and some links.
+<p>Plus, we not only put the user editing menu on the top of the screen, <b>we also place the footer box</b> on the bottom of every page, including creative commons logo, mediawiki logo and some links. Since these are useful information for wiki that shouldn't be hidden.</p>
 </div>
 </div>