"
Team:NCTU Formosa
From 2014.igem.org
(Difference between revisions)
| Line 16: | Line 16: | ||
<div id="sec2" class="seclink"><a href="https://2014.igem.org/Team:NCTU_Formosa/results"><i class="fa fa-smile-o"></i><p class="smalltitle">Results</p><p>The current progress of our project, including detailed information of the experimental data and the overall evaluation of the practicability of this project. </p></a></div> | <div id="sec2" class="seclink"><a href="https://2014.igem.org/Team:NCTU_Formosa/results"><i class="fa fa-smile-o"></i><p class="smalltitle">Results</p><p>The current progress of our project, including detailed information of the experimental data and the overall evaluation of the practicability of this project. </p></a></div> | ||
<div id="sec3" class="seclink"><a href="https://2014.igem.org/Team:NCTU_Formosa/modeling"><i class="icon-bar-chart"></i><p class="smalltitle">Modeling</p><p>Modeling was our first step forward. When validated with our experimental data, modeling is also a verification of the accuracy of our experiments. </p></a></div> | <div id="sec3" class="seclink"><a href="https://2014.igem.org/Team:NCTU_Formosa/modeling"><i class="icon-bar-chart"></i><p class="smalltitle">Modeling</p><p>Modeling was our first step forward. When validated with our experimental data, modeling is also a verification of the accuracy of our experiments. </p></a></div> | ||
| - | <div id="sec4" class="seclink"><a href="https:// | + | <div id="sec4" class="seclink"><a href="https://2014.igem.org/Team:NCTU_Formosa/biobricks"><i class="icon-puzzle-piece"></i><p class="smalltitle">Biobricks</p><p>To strive for the best results, we made a number of experiment. Our team always hang together in spite of many losses.</p></a></div> |
<div id="sec5" class="seclink"><a href="https://2014.igem.org/Team:NCTU_Formosa/notes"><i class="icon-pencil"></i><p class="smalltitle">Notes</p><p>The experimental log that records down the purpose, method, result and date of each experiment that we have conducted.</p></a></div> | <div id="sec5" class="seclink"><a href="https://2014.igem.org/Team:NCTU_Formosa/notes"><i class="icon-pencil"></i><p class="smalltitle">Notes</p><p>The experimental log that records down the purpose, method, result and date of each experiment that we have conducted.</p></a></div> | ||
<div id="sec6" class="seclink"><a href="https://2014.igem.org/Team:NCTU_Formosa/human_practice"><i class="icon-magnet"></i><p class="smalltitle">Human Practice</p><p>This summer, we hosted a summer camp for high school students and held a conference for iGEMers. With these efforts, we have passed on our enthusiasm of synthetic biology to our peers and raise their interests on the topic. </p></a></div> | <div id="sec6" class="seclink"><a href="https://2014.igem.org/Team:NCTU_Formosa/human_practice"><i class="icon-magnet"></i><p class="smalltitle">Human Practice</p><p>This summer, we hosted a summer camp for high school students and held a conference for iGEMers. With these efforts, we have passed on our enthusiasm of synthetic biology to our peers and raise their interests on the topic. </p></a></div> | ||
| Line 43: | Line 43: | ||
<div class="cphoto"><img src="https://static.igem.org/mediawiki/2014/1/13/Nctu-wm3.png" width="420px"></div> | <div class="cphoto"><img src="https://static.igem.org/mediawiki/2014/1/13/Nctu-wm3.png" width="420px"></div> | ||
<p class="smalltitle">Contents in wiki are easily editable</p> | <p class="smalltitle">Contents in wiki are easily editable</p> | ||
| - | <p>When iGEMers log into 2014.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:// | + | <p>When iGEMers log into 2014.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://2014.igem.org/wiki/index.php?title=Team:NCTU_Formosa/project&action=history">the history log of our project page</a>.</p> |
</div> | </div> | ||
<div class="merit"> | <div class="merit"> | ||
| Line 58: | Line 58: | ||
<div class="merit"> | <div class="merit"> | ||
<div class="cphoto"><img src="https://static.igem.org/mediawiki/2014/5/56/Nctu-wm6.png" width="420px"></div> | <div class="cphoto"><img src="https://static.igem.org/mediawiki/2014/5/56/Nctu-wm6.png" width="420px"></div> | ||
| - | <p class="smalltitle">Following wiki requirements for iGEM | + | <p class="smalltitle">Following wiki requirements for iGEM 2014</p> |
<p>Our wiki follows <a href="https://2014.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 2014.igem.org server to prevent from data losing.</p> | <p>Our wiki follows <a href="https://2014.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 2014.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, because these are useful information that shouldn't be hidden.</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, because these are useful information that shouldn't be hidden.</p> | ||
| Line 80: | Line 80: | ||
<div id="footer-wrapper"> | <div id="footer-wrapper"> | ||
<div id="footer"> <div id="footer-text"> | <div id="footer"> <div id="footer-text"> | ||
| - | <p> | + | <p>2014 NCTU_Formosa</p> |
<p class="author">Website designed by Calvin Hue.</p> | <p class="author">Website designed by Calvin Hue.</p> | ||
<p>Cover image credit: <a href="http://www.dvq.co.nz/" target="_blank">DVQ</a>, <a href="http://www.apple.com/" target="_blank">Apple Inc.</a></p> | <p>Cover image credit: <a href="http://www.dvq.co.nz/" target="_blank">DVQ</a>, <a href="http://www.apple.com/" target="_blank">Apple Inc.</a></p> | ||
Revision as of 04:06, 14 August 2014
NCTU_Formosa
E.colightunera regulation system that does multitasking.
This year, We found the simple act of expressing the DNA sequence of PBAN (Pheromone Biosynthesis Activating Neuropeptide) to be equally, if not more, efficient and effective. Just like pheromones, PBAN is species-specific. Once our target species comes in contact with the PBAN produced by our E. coli, its pheromone glands will be stimulated and thus attract more of its own kind into our capturing device.
So far, We have already collected sequences of a few common species of harmful insects. Hopefully this model can be widely used in the future when PBANs of more insects are found.
See our project
Sitemap
Our wiki has 10 pages in total and each page contains several sections. There's a navigation bar sticking on the top of the page. When you want to get back to the top of the page, don't panic! Feel free to click the button on the left-bottom corner of the page anytime.
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 2014.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 2014
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 2014.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, because these are useful information that shouldn't be hidden.