http://2014.igem.org/wiki/index.php?title=Special:Contributions&feed=atom&limit=500&target=Vinoo&year=&month=2014.igem.org - User contributions [en]2024-03-29T07:38:18ZFrom 2014.igem.orgMediaWiki 1.16.5http://2014.igem.org/Template:Nav/CompetitionTemplate:Nav/Competition2014-12-03T20:58:02Z<p>Vinoo: </p>
<hr />
<div>{{CSS/Nav/Grid12}}<br />
<html><br />
<div class="container_12"><br />
<div class="grid_3"><br />
<ul><span class="menuHeader">Getting Started</span><br />
<li><a href="https://2014.igem.org/Start_A_Team">Start a Team</a></li><br />
<li><a href="https://2014.igem.org/Funding">Funding How-To</a></li><br />
<li><a href="https://2014.igem.org/Gender">Gender Balance</a></li> <br />
<li><a href="https://2014.igem.org/Requirements">Requirements</a></li><br />
<li><a href="https://2014.igem.org/Handbook">Handbook</a></li><br />
</ul><br />
</div><br />
<div class="grid_3"><br />
<ul><span class="menuHeader">Participation</span><br />
<li><a href="https://2014.igem.org/Requirements">Requirements</a></li><br />
<li><a href="https://2014.igem.org/Calendar_of_Events">Calendar of Events</a></li><br />
<li><a href="https://igem.org/IGEM_2014_Registration">2014 Team Registration</a></li><br />
<li><a href="https://2014.igem.org/Fees">2014 Fees</a></li><br />
<li><a href="https://2014.igem.org/Sections">Sections: Undergrad & Overgrad</a></li><br />
<li><a href="https://2014.igem.org/Tracks">Tracks</a></li><br />
</ul><br />
</div><br />
<div class="grid_3"><br />
<ul><span class="menuHeader">&nbsp;</span><br />
<li><a href="https://2014.igem.org/Meetups">Team Meetups</a></li><br />
<li><a href="https://2014.igem.org/Community">Community</a></li><br />
<li><a href="https://2014.igem.org/Safety">Safety</a></li><br />
<li><a href="https://igem.org/Security">Security</a></li><br />
<li><a href="https://2014.igem.org/Judging">Judging</a></li><br />
<li><a href="https://2014.igem.org/Giant_Jamboree">Giant Jamboree</a></li><br />
</ul><br />
</div><br />
<div class="grid_3"><br />
<ul><span class="menuHeader">Media</span><br />
<li><a href="https://2014.igem.org/Photo_Gallery">iGEM Photo Gallery</a></li><br />
<li><a href="https://2014.igem.org/IGEM_Publicity">iGEM Publicity</a></li><br />
<li><a href="https://2014.igem.org/IGEM_Publications">Publications</a></li><br />
</ul><br />
</div><br />
</div><br />
</html></div>Vinoohttp://2014.igem.org/Template:Nav/CompetitionTemplate:Nav/Competition2014-12-03T20:54:05Z<p>Vinoo: </p>
<hr />
<div>{{CSS/Nav/Grid12}}<br />
<html><br />
<div class="container_12"><br />
<div class="grid_3"><br />
<ul><span class="menuHeader">Getting Started</span><br />
<li><a href="https://2014.igem.org/Start_A_Team">Start a Team</a></li><br />
<li><a href="https://2014.igem.org/Funding">Funding How-To</a></li><br />
<li><a href="https://2014.igem.org/Gender">Gender Balance</a></li> <br />
<li><a href="https://2014.igem.org/Requirements">Requirements</a></li><br />
<li><a href="https://2014.igem.org/Handbook">Handbook</a></li><br />
</ul><br />
</div><br />
<div class="grid_3"><br />
<ul><span class="menuHeader">Participation</span><br />
<li><a href="https://2014.igem.org/Requirements">Requirements</a></li><br />
<li><a href="https://2014.igem.org/Calendar_of_Events">Calendar of Events</a></li><br />
<li><a href="https://igem.org/IGEM_2014_Registration">2014 Team Registration</a></li><br />
<li><a href="https://2014.igem.org/Fees">2014 Fees</a></li><br />
<li><a href="https://2014.igem.org/Sections">Sections: Undergrad & Overgrad</a></li><br />
<li><a href="https://2014.igem.org/Tracks">Tracks</a></li><br />
<li><a href="https://2014.igem.org/Meetups">Team Meetups</a></li><br />
</ul><br />
</div><br />
<div class="grid_3"><br />
<ul><span class="menuHeader">&nbsp;</span><br />
<li><a href="https://2014.igem.org/Community">Community</a></li><br />
<li><a href="https://2014.igem.org/Safety">Safety</a></li><br />
<li><a href="https://igem.org/Security">Security</a></li><br />
<li><a href="https://2014.igem.org/Judging">Judging</a></li><br />
<li><a href="https://2014.igem.org/Judging_Feedback">2014 Team Judging Feedback</a></li><br />
<li><a href="https://2014.igem.org/Giant_Jamboree">Giant Jamboree</a></li><br />
</ul><br />
</div><br />
<div class="grid_3"><br />
<ul><span class="menuHeader">Media</span><br />
<li><a href="https://2014.igem.org/Photo_Gallery">iGEM Photo Gallery</a></li><br />
<li><a href="https://2014.igem.org/IGEM_Publicity">iGEM Publicity</a></li><br />
<li><a href="https://2014.igem.org/IGEM_Publications">Publications</a></li><br />
</ul><br />
</div><br />
</div><br />
</html></div>Vinoohttp://2014.igem.org/Template:Nav/CompetitionTemplate:Nav/Competition2014-12-03T20:53:42Z<p>Vinoo: </p>
<hr />
<div>{{CSS/Nav/Grid12}}<br />
<html><br />
<div class="container_12"><br />
<div class="grid_3"><br />
<ul><span class="menuHeader">Getting Started</span><br />
<li><a href="https://2014.igem.org/Start_A_Team">Start a Team</a></li><br />
<li><a href="https://2014.igem.org/Funding">Funding How-To</a></li><br />
<li><a href="https://2014.igem.org/Gender">Gender Balance</a></li> <br />
<li><a href="https://2014.igem.org/Requirements">Requirements</a></li><br />
<li><a href="https://2014.igem.org/Handbook">Handbook</a></li><br />
</ul><br />
</div><br />
<div class="grid_3"><br />
<ul><span class="menuHeader">Participation</span><br />
<li><a href="https://2014.igem.org/Requirements">Requirements</a></li><br />
<li><a href="https://2014.igem.org/Calendar_of_Events">Calendar of Events</a></li><br />
<li><a href="https://igem.org/IGEM_2014_Registration">2014 Team Registration</a></li><br />
<li><a href="https://2014.igem.org/Fees">2014 Fees</a></li><br />
<li><a href="https://2014.igem.org/Sections">Sections: Undergrad & Overgrad</a></li><br />
<li><a href="https://2014.igem.org/Tracks">Tracks</a></li><br />
</ul><br />
</div><br />
<div class="grid_3"><br />
<ul><span class="menuHeader">&nbsp;</span><br />
<li><a href="https://2014.igem.org/Meetups">Team Meetups</a></li><br />
<li><a href="https://2014.igem.org/Community">Community</a></li><br />
<li><a href="https://2014.igem.org/Safety">Safety</a></li><br />
<li><a href="https://igem.org/Security">Security</a></li><br />
<li><a href="https://2014.igem.org/Judging">Judging</a></li><br />
<li><a href="https://2014.igem.org/Judging_Feedback">2014 Team Judging Feedback</a></li><br />
<li><a href="https://2014.igem.org/Giant_Jamboree">Giant Jamboree</a></li><br />
</ul><br />
</div><br />
<div class="grid_3"><br />
<ul><span class="menuHeader">Media</span><br />
<li><a href="https://2014.igem.org/Photo_Gallery">iGEM Photo Gallery</a></li><br />
<li><a href="https://2014.igem.org/IGEM_Publicity">iGEM Publicity</a></li><br />
<li><a href="https://2014.igem.org/IGEM_Publications">Publications</a></li><br />
</ul><br />
</div><br />
</div><br />
</html></div>Vinoohttp://2014.igem.org/Template:Nav/TeamsTemplate:Nav/Teams2014-12-03T20:53:02Z<p>Vinoo: </p>
<hr />
<div>{{CSS/Nav/Grid12}}<br />
<html><br />
<div class="container_12"><br />
<div class="grid_3"><br />
<ul><span class="menuHeader">Team Links</span><br />
<li><a href="https://igem.org/Team_List?year=2014">2014 Team List</a></li><br />
<li><a href="https://igem.org/Team_Wikis?year=2014">2014 Team Wikis</a></li><br />
<li><a href="https://igem.org/Team_Parts?year=2014">2014 Team Parts</a></li><br />
<li><a href="https://igem.org/Team_Tracks?year=2014">2014 Team Tracks</a></li><br />
</ul><br />
</div><br />
<div class="grid_3"><br />
<ul><span class="menuHeader">Team Judging</span><br />
<li><a href="https://igem.org/Team_Judging?year=2014">2014 Team Judging Forms</a></li><br />
<li><a href="https://2014.igem.org/Judging_Feedback">2014 Team Judging Feedback</a></li><br />
</ul><br />
</div><br />
</div><br />
</html></div>Vinoohttp://2014.igem.org/Judging_FeedbackJudging Feedback2014-12-03T20:51:37Z<p>Vinoo: Created page with "{{CSS/Main}} {{NavBar}} <html> <div id="contentcontainer"> </div> </html> {{MainPage2014/Footer}}"</p>
<hr />
<div>{{CSS/Main}}<br />
{{NavBar}}<br />
<html><br />
<div id="contentcontainer"><br />
<br />
</div><br />
</html><br />
{{MainPage2014/Footer}}</div>Vinoohttp://2014.igem.org/Template:Nav/TeamsTemplate:Nav/Teams2014-12-03T20:50:32Z<p>Vinoo: </p>
<hr />
<div>{{CSS/Nav/Grid12}}<br />
<html><br />
<div class="container_12"><br />
<div class="grid_3"><br />
<ul><span class="menuHeader">Team Links</span><br />
<li><a href="https://igem.org/Team_List?year=2014">2014 Team List</a></li><br />
<li><a href="https://igem.org/Team_Wikis?year=2014">2014 Team Wikis</a></li><br />
<li><a href="https://igem.org/Team_Parts?year=2014">2014 Team Parts</a></li><br />
<li><a href="https://igem.org/Team_Tracks?year=2014">2014 Team Tracks</a></li><br />
<li><a href="https://igem.org/Team_Judging?year=2014">2014 Team Judging Forms</a></li><br />
<li><a href="https://2014.igem.org/Judging_Feedback">2014 Team Judging Feedback</a></li><br />
</ul><br />
</div><br />
</div><br />
</html></div>Vinoohttp://2014.igem.org/Wiki_How-ToWiki How-To2014-11-12T17:44:14Z<p>Vinoo: </p>
<hr />
<div>{{CSS/Main}}<br />
{{NavBar}}<br />
<html><br />
<div id="contentcontainer"><br />
<br />
</html><br />
{{TOCright}}<br />
===Wiki Freeze - October 17th (11:59 PM -EDT)===<br />
<html><br />
<br />
<p><b><span style="color:red;">Warning: Do not wait till the last minute! There will be a lot of traffic on the iGEM wiki starting as early as Wednesday (October 15th). Upload your content early and avoid issues caused by server load.</span></b></p><br />
<br />
<p>Your team's project must be documented on the iGEM 2014 wiki, the parts used in your project must be documented on the <a href="http://parts.igem.org">Registry of Standard Biological Parts</a>. You have the freedom to be creative, but a few specific rules apply:</p><br />
<br />
<br />
<br /><br />
<br /><br />
<br />
<br />
<style type="text/css"><br />
.simpleTable {<br />
cellspacing: 0;<br />
}<br />
.simpleTable th, .simpleTable td {<br />
padding: 10px 15px;<br />
}<br />
.simpleTable th {<br />
color: #fff;<br />
background-color: #333;<br />
font-style: italic;<br />
font-size: 14pt;<br />
}<br />
.simpleTable tr:nth-child(even) {<br />
background-color: #f0f0f0;<br />
}<br />
</style><br />
</html><br />
<br />
===Wiki Dos and Don'ts===<br />
<html><br />
<table class="simpleTable"><br />
<tr><br />
<th width="250px">Do</th><br />
<th width="250px">Don't</th><br />
<th width="460px">Why?</th><br />
</tr><br />
<tr><br />
<td>Make sure all wiki content, from code and scripts, to files, is hosted on <b>2014.igem.org</b></td><br />
<td>Don't host your wiki or parts of your wiki elsewhere. <!-- It is possible to display contents from another server onto your wiki, using iframes or other methods. Please be aware that this violates the requirement for hosting all content on 2014.igem.org--> </td><br />
<td>iGEM content is preserved on our servers so future teams can learn from what you've done. When content is stored on other sites/servers, links may become broken (<a href="https://static.igem.org/mediawiki/2014/d/d6/Wiki_server_example1.jpg" title="images were stored off-site, and became broken" target="_blank">example</a>), sites may go down, and <b>information will be lost.</b></td><br />
</tr><br />
<tr><br />
<td>Work on your wiki throughout the year and <b>save small edits for last</b></td><br />
<td>Don't wait to add/edit large portions of wiki content the day of the <b>Wiki Freeze</b></td><br />
<td>Just before the Wiki Freeze, iGEM websites experience <b>increased traffic and server loads.</b> This can be a difficult time to make larger changes or additions to your wiki. Don't wait till the last minute!</td><br />
</tr><br />
<tr><br />
<td>Name uploaded files clearly and uniquely (TeamName_Header.png)</td><br />
<td>Don't use generic names for you files (Header.png)</td><br />
<td>Using <b>unique names</b> makes searching/identification of uploaded files easier, and helps prevent files from being overwritten.</td><br />
</tr><br />
<tr><br />
<td>Load your CSS and Javascript into the wiki, either directly into your page or using templates (<a href="https://2014.igem.org/wiki/index.php?title=Wiki_How-To&action=submit#Wiki_Editing">see below</a>)</td><br />
<td>Don't try to host your CSS and Javascript on a third party server</td><br />
<td>You are required to host all content on the iGEM servers (<a href="https://2014.igem.org/wiki/index.php?title=Wiki_How-To&action=submit#Wiki_Requirements">see below</a>)</td><br />
</tr><br />
</table><br />
<br /><br /><br />
<br />
</html><br />
<br />
===Wiki Requirements===<br />
<html><br />
<h4>iGEM Logo</h4><br />
<p>All iGEM Team Wikis must include the iGEM logo at the top of the page and a visible link back to the iGEM 2014 Wiki Main Page in the header (or at the top of the page). All wiki pages must preserve the user editing menu (notifications, username, messages, history, edit). In the case where the user heading is not visible, an automatic heading will be overlaid on top of the wiki page(s) where the heading is missing. </p><br />
<h4>The iGEM Login Bar</h4><br />
<p>The iGEM Login Bar is a 20 pixel high, full-width menu bar that exists on all 2014.igem.org pages. It contains:<br />
<ul><br />
<li>wiki tools (edit, history, watch, etc.)</li><br />
<li>login</li><br />
</ul><br />
All iGEM 2014 Team Wikis are required to have the Login Bar. All wiki pages must preserve the user editing menu (notifications, username, messages, history, edit). Please keep this in mind as you design your wiki.</p><br />
<h4>No Adobe Flash</h4> <br />
<p>Flash is not permitted on the iGEM 2014 wiki. Adobe flash is 100% proprietary and you cannot view the source like you can with our wiki. We chose wikis for teams to build their projects so the source code would be available for future teams, to build on the concept of open source. Flash can also be hosted on external sites and we want 100% of the content of our wikis to be on our wikis. </p> <br />
<h4>Upload to 2014.igem.org server</h4><br />
<p>All team pages, images, documents and <b>code</b> must be hosted on the <b>2014.igem.org</b> server. We preserve all iGEM content on our own servers so future teams can learn from what you have done. When you store content on your own sites or servers, after time, links might become broken, sites might go down, and information will be lost. <br /><br />
Additionally, hosting content outside of 2014.iGEM.org allows teams to change/add information to their wiki after the wiki freeze. Please note, that altering content after the wiki freeze is a <a href="https://2014.igem.org/Responsible_Conduct">form of cheating</a>. <br /><br />
Load your CSS and Javascript into the wiki, either directly into your page or using templates (<a href="https://2014.igem.org/wiki/index.php?title=Wiki_How-To&action=submit#Wiki_Editing">see below</a>)<br />
</p><br />
<h4>No iframes</h4> <br />
<p><b>iframes</b> are not permitted on the iGEM wiki. If an iframe was used to access content outside of <b>2014.igem.org</b>...<br />
<ul><br />
<li>it would break when there was an issue with the outside server</li> <br />
<li>it would allow a team to show change/add content after the wiki freeze. Please note, that altering content after the wiki freeze is a <a href="https://2014.igem.org/Responsible_Conduct">form of cheating</a></li> <br />
</ul><br />
</p><br />
<h4>2014.igem.org/Team:Team_Name</h4><br />
<p>All iGEM 2014 teams are given a namespace on the iGEM 2014 wiki with their team name. Teams are allowed to create and edit pages within their respective team namespace. Teams are <b>not allowed</b> to create or edit pages belonging to another team's namespace.</p><br />
<h4>Wiki Freeze - October 17th</h4><br />
<p>The wiki freeze for the 2014 Giant Jamboree is on <a href="https://2014.igem.org/Calendar_of_Events">October 17th,</a> along with other deadlines. iGEM experiences higher than normal traffic on this day which can lead to strain on our servers and sessions timing out for users. iGEM HQ recommends that users do not wait till the last day to work/finish their wikis. <b>Once the wikis are frozen, users can no longer make any changes until they are unfrozen after the Jamboree.</b></p><br />
<h4>Other deadlines</h4><br />
<p>The team's project description must be documented on their iGEM Team Wiki by the deadline. The project description should be 1-3 paragraphs and only needs to include an up-to-date explanation of the project.</p><br />
<p>The team's wiki must include an attributions section.</p><br />
<h4>Creative Commons</h4><br />
<p>All content on this wiki is available under the Creative Commons <a href="http://creativecommons.org/licenses/by/4.0/">Attribution 4.0</a> license (or any later version).<br />
<img src="http://i.creativecommons.org/l/by/3.0/88x31.png"></p><br />
<br /><br /><br />
<br />
</html><br />
<br />
===Wiki Editing===<br />
<html><br />
<h4>Add a wiki page, change a wiki page, delete a wiki page, etc.</h4><br />
<p>All iGEM wiki sites are powered by Mediawiki. See the <a href="http://www.mediawiki.org/wiki/Help:Contents">Mediawiki Help page</a> for details on how to edit wiki pages and more.</p><br />
<p>Using/editing the wiki is a trial-and-error process. Editing the wiki is a simple, fun thing to do and you definitely get better the more you play around with it. The key is to take a look at other wiki pages and see what you like. Then all you have to do is go to the source (either view source if you're not logged in, or edit if you are logged in), copy it, and modify it to fit your needs. It doesn't have to be perfect before you can take a look at what it looks like. Try things out and see what results they yield.</p><br />
<br />
<h4>Adding a page to your team's namespace?</h4><br />
<p>You must keep your team's pages in your team namespace. For example, take a look at <a href="https://2014.igem.org/Team:Example">2014.igem.org/Team:Example</a></p> <br />
<p>Specifically, when you create a new page, you just have to name it <b>Team</b>:<a href="https://igem.org/Team_List">OFFICIAL team name</a>/PageName. For example, if you were on Team Example and wanted to create a Biosensor project page you would name it <b>Team:Example/Biosensor_project</b>.</p><br />
<br />
<h4>Using html in wiki pages</h4><br />
<p>Instead of using wiki markup, you can use <b>html</b> in the wiki editor. Just put your html code in between <i>&lt;html>&lt;/html></i></p><br />
<br />
<h4>Using CSS and/or Javascript</h4><br />
<p>You can also use <b>CSS</b> and <b>Javascript</b> on the wiki by adding your <i>&lt;style></i> and <i>&lt;script></i> tags into your <i>&lt;html></i> code.</p><br />
<p>If you want to use a CSS stylesheet or Javascript on multiple pages, you can create a <b>wiki template page</b>.</p><br />
<br />
<h4>Using Wiki Templates</h4><br />
<p>If there is standard text/code that you want to add to more than one page, like a CSS style or script, then you can use <a href="http://www.mediawiki.org/wiki/Help:Templates">MediaWiki templates</a></p><br />
<p>You can create a <b>wiki template page</b> to house your HTML/CSS/Javascript, by entering <i>{{Team:YourTeamName/CSS}}</i> into your wiki markup. Saving the page will create a link for a new template page, which you can edit and enter all of your CSS code. You can then call <i>{{Team:YourTeamName/CSS}}</i> on other pages.</p><br />
<p>Take a look at a few 2013 team wikis to see how other teams setup the styling. You can do this by going to a wiki, and looking for <i>view source</i> in the default wiki links at the top of the page. See <a href="https://2013.igem.org/Template:MIT-style">MIT's</a> and <a href="https://2013.igem.org/Team:TU-Munich">TU-Munich's</a> for examples.</p><br />
<br />
<h4>Uploading videos and using HTML 5 to display them</h4><br />
<p>You can upload videos (ogg, mov) to the 2014 wiki by using Mediawiki's <a href="https://2014.igem.org/Special:Upload">Upload tool</a>.</p><br />
<p>You can display videos by using the HTML 5 <i>&lt;video></i> tag, along with <i>&lt;source src="file_url" type="video/mov" /></i>.</p><br />
<p>Take a look at the <a href="https://2013.igem.org/Team:Leeds">2013 Leed's team wiki</a> to see how they displayed their video. You can do this by going to their wiki, and looking for <i>view source</i> in the default wiki links at the top of the page.</p><br />
<br />
<br /><br /><br />
</html><br />
<br />
===Perspectives from an iGEM veteran===<br />
<html><br />
<table cellspacing="10" style="text-align: justify;" width="965px"><br />
<br />
<tr> <br />
<br />
<td width="48%"><br />
Hello iGEMers!<br />
<br><br />
I was also part of an iGEM team!<br />
<br><br />
In 2011 and 2012 my role was to design and create our team’s wiki. So wiki freeze was my major deadline. I am by no means an expert but let me share with you some of the things I learned with two wiki freezes under my belt.<br />
<br><br><br />
<b> 1.- Test your webpage layout: is information easy to find?</b> </br><br />
<p> I made the terrible mistake of not asking for a third party’s opinion about the layout of information on our site. It was obvious for me how things were laid out and organized. It wasn’t for the people evaluating us. <br><br />
Also, stick to the 3 click rule: content must reachable within 3 clicks so the user does not feel lost or confused. If someone wants to read your abstract, their path should be something like this (Menu –> Project –> Project Description -> Abstract)</p><br />
<br><br />
<b> 2.- Look at other teams’ code, see how they documented and what resources they used. </b><br><br />
<p> It is always good to get inspiration from other iGEM teams. See what you liked that they did and strive to improve! </p><br />
<br><br />
<b> 3.- Start working on your documentation early on. </b> <br><br />
<p>This was a good thing that we did; we created a common file that more than one person can edit at a time. Divide the documentation into smaller files and assign a team member to fully document that topic. In the end you will have a printable version of your project that you can share as a pdf file with other people!</p><br />
<br><br />
<br />
</td><br />
<br />
<td width="4%"></td><br />
<br />
<td width="48%" valign="top"><br />
<b> 4.- Name your images according to the project and keep them all in a folder on your computer. </b> <br><br />
<p> Sometimes naming your gel image “gelthingy_whyiamworkingat3am” sounds perfect at 3AM but later it may not be easy to know what or when that photograph was taken or that image created. <br><br />
Also, the iGEM database doesn’t know that you created that file so if someone names their file with the same name it can end up being replaced! Avoid using generic names like “banner.png” or “logo.jpg”.<br><br />
Try using your team’s name and the webpage where the image will appear, this helps you remember where to place it and reduce the risk of another team overwriting. “JoyUniversity_TeamBios_Richard.jpg” </p><br />
<br><br />
<b> 5.- Do not leave everything to the last minute! </b><br />
<br />
<p> Plan ahead. The last thing you want to be doing at 11:30PM the night of wiki freeze is uploading images. It is very stressful to be looking at the clock and hoping some kind of coding miracle helps you fix bugs faster. Plan to have everything online at least one week ahead so you can go enjoy a nice dinner with your team that night! </p><br />
<br />
<br />
<p> I hope this helps and if you have any questions, feel free to email me or send me a tweet! </p><br />
<i> ana at igem dot org </i><br />
<br><br />
<i> <A HREF="https://twitter.com/anita_sifuentes" > @anita_sifuentes </A> </i><br />
<br />
</td><br />
</tr><br />
</table><br />
<br /><br />
<br />
</html><br />
<br />
===Wiki Templates===<br />
<html><br />
<p> This year we have created a set of template pages that you may for your wiki! <BR> Feel free to edit them as much as you want </p><br />
<a href="https://2014.igem.org/WikitemplateA_home ">Wiki Template A </a></br><br />
<a href="https://2014.igem.org/WikitemplateB_home ">Wiki Template B </a><br />
<BR><BR><br />
<br />
</div><br />
</html><br />
{{MainPage2014/Footer}}</div>Vinoohttp://2014.igem.org/User:VinooUser:Vinoo2014-10-22T15:07:07Z<p>Vinoo: </p>
<hr />
<div>[[User:Vinoo/2014Design7]]<br />
[[User:Vinoo/AccordionMenu]]<br />
[[User:Vinoo/MainPage]]<br />
[[User:Vinoo/2015Design1]]<br />
<br />
<html><br />
<style type="text/css"><br />
#nlogin_iframe {<br />
background-color: rgba(0, 0, 0, 0);<br />
border: medium none;<br />
color: #FFFFFF;<br />
display: block;<br />
font-family: ariel,sans-serif;<br />
height: 220px;<br />
margin-top: 10px;<br />
position: relative;<br />
text-align: center;<br />
width: 900px;<br />
}<br />
</style><br />
<br />
<iframe id="nlogin_iframe" frameborder="0" src="https://igem.org/Login2"></iframe><br />
</html></div>Vinoohttp://2014.igem.org/File:Leeds_SummaryVid.mp4File:Leeds SummaryVid.mp42014-10-17T15:22:10Z<p>Vinoo: </p>
<hr />
<div></div>Vinoohttp://2014.igem.org/Wiki_How-ToWiki How-To2014-10-17T14:55:28Z<p>Vinoo: </p>
<hr />
<div>{{CSS/Main}}<br />
{{NavBar}}<br />
<html><br />
<div id="contentcontainer"><br />
<br />
</html><br />
{{TOCright}}<br />
===Wiki Freeze - October 17th (11:59 PM -EDT)===<br />
<html><br />
<br />
<p><b><span style="color:red;">Warning: Do not wait till the last minute! There will be a lot of traffic on the iGEM wiki starting as early as Wednesday (October 15th). Upload your content early and avoid issues caused by server load.</span></b></p><br />
<br />
<p>Your team's project must be documented on the iGEM 2014 wiki, the parts used in your project must be documented on the <a href="http://parts.igem.org">Registry of Standard Biological Parts</a>. You have the freedom to be creative, but a few specific rules apply:</p><br />
<br />
<br />
<br /><br />
<br /><br />
<br />
<br />
<style type="text/css"><br />
.simpleTable {<br />
cellspacing: 0;<br />
}<br />
.simpleTable th, .simpleTable td {<br />
padding: 10px 15px;<br />
}<br />
.simpleTable th {<br />
color: #fff;<br />
background-color: #333;<br />
font-style: italic;<br />
font-size: 14pt;<br />
}<br />
.simpleTable tr:nth-child(even) {<br />
background-color: #f0f0f0;<br />
}<br />
</style><br />
</html><br />
<br />
===Wiki Dos and Don'ts===<br />
<html><br />
<table class="simpleTable"><br />
<tr><br />
<th width="250px">Do</th><br />
<th width="250px">Don't</th><br />
<th width="460px">Why?</th><br />
</tr><br />
<tr><br />
<td>Make sure all wiki content, from code and scripts, to files, is hosted on <b>2014.igem.org</b></td><br />
<td>Don't host your wiki or parts of your wiki elsewhere</td><br />
<td>iGEM content is preserved on our servers so future teams can learn from what you've done. When content is stored on other sites/servers, links may become broken (<a href="https://static.igem.org/mediawiki/2014/d/d6/Wiki_server_example1.jpg" title="images were stored off-site, and became broken" target="_blank">example</a>), sites may go down, and <b>information will be lost.</b></td><br />
</tr><br />
<tr><br />
<td>Work on your wiki throughout the year and <b>save small edits for last</b></td><br />
<td>Don't wait to add/edit large portions of wiki content the day of the <b>Wiki Freeze</b></td><br />
<td>Just before the Wiki Freeze, iGEM websites experience <b>increased traffic and server loads.</b> This can be a difficult time to make larger changes or additions to your wiki. Don't wait till the last minute!</td><br />
</tr><br />
<tr><br />
<td>Name uploaded files clearly and uniquely (TeamName_Header.png)</td><br />
<td>Don't use generic names for you files (Header.png)</td><br />
<td>Using <b>unique names</b> makes searching/identification of uploaded files easier, and helps prevent files from being overwritten.</td><br />
</tr><br />
<tr><br />
<td>Load your CSS and Javascript into the wiki, either directly into your page or using templates (<a href="https://2014.igem.org/wiki/index.php?title=Wiki_How-To&action=submit#Wiki_Editing">see below</a>)</td><br />
<td>Don't try to host your CSS and Javascript on a third party server</td><br />
<td>You are required to host all content on the iGEM servers (<a href="https://2014.igem.org/wiki/index.php?title=Wiki_How-To&action=submit#Wiki_Requirements">see below</a>)</td><br />
</tr><br />
</table><br />
<br /><br /><br />
<br />
</html><br />
<br />
===Wiki Requirements===<br />
<html><br />
<h4>iGEM Logo</h4><br />
<p>All iGEM Team Wikis must include the iGEM logo at the top of the page and a visible link back to the iGEM 2014 Wiki Main Page in the header (or at the top of the page). All wiki pages must preserve the user editing menu (notifications, username, messages, history, edit). In the case where the user heading is not visible, an automatic heading will be overlaid on top of the wiki page(s) where the heading is missing. </p><br />
<h4>The iGEM Login Bar</h4><br />
<p>The iGEM Login Bar is a 20 pixel high, full-width menu bar that exists on all 2014.igem.org pages. It contains:<br />
<ul><br />
<li>wiki tools (edit, history, watch, etc.)</li><br />
<li>login</li><br />
</ul><br />
All iGEM 2014 Team Wikis are required to have the Login Bar. All wiki pages must preserve the user editing menu (notifications, username, messages, history, edit). Please keep this in mind as you design your wiki.</p><br />
<h4>No Adobe Flash</h4> <br />
<p>Flash is not permitted on the iGEM 2014 wiki. Adobe flash is 100% proprietary and you cannot view the source like you can with our wiki. We chose wikis for teams to build their projects so the source code would be available for future teams, to build on the concept of open source. Flash can also be hosted on external sites and we want 100% of the content of our wikis to be on our wikis. </p> <br />
<h4>Upload to 2014.igem.org server</h4><br />
<p>All team pages, images, documents and <b>code</b> must be hosted on the <b>2014.igem.org</b> server. We preserve all iGEM content on our own servers so future teams can learn from what you have done. When you store content on your own sites or servers, after time, links might become broken, sites might go down, and information will be lost. <br /><br />
Additionally, hosting content outside of 2014.iGEM.org allows teams to change/add information to their wiki after the wiki freeze. Please note, that altering content after the wiki freeze is a <a href="https://2014.igem.org/Responsible_Conduct">form of cheating</a>. <br /><br />
Load your CSS and Javascript into the wiki, either directly into your page or using templates (<a href="https://2014.igem.org/wiki/index.php?title=Wiki_How-To&action=submit#Wiki_Editing">see below</a>)<br />
</p><br />
<h4>No iframes</h4> <br />
<p><b>iframes</b> are not permitted on the iGEM wiki. If an iframe was used to access content outside of <b>2014.igem.org</b>...<br />
<ul><br />
<li>it would break when there was an issue with the outside server</li> <br />
<li>it would allow a team to show change/add content after the wiki freeze. Please note, that altering content after the wiki freeze is a <a href="https://2014.igem.org/Responsible_Conduct">form of cheating</a></li> <br />
</ul><br />
</p><br />
<h4>2014.igem.org/Team:Team_Name</h4><br />
<p>All iGEM 2014 teams are given a namespace on the iGEM 2014 wiki with their team name. Teams are allowed to create and edit pages within their respective team namespace. Teams are <b>not allowed</b> to create or edit pages belonging to another team's namespace.</p><br />
<h4>Wiki Freeze - October 17th</h4><br />
<p>The wiki freeze for the 2014 Giant Jamboree is on <a href="https://2014.igem.org/Calendar_of_Events">October 17th,</a> along with other deadlines. iGEM experiences higher than normal traffic on this day which can lead to strain on our servers and sessions timing out for users. iGEM HQ recommends that users do not wait till the last day to work/finish their wikis. <b>Once the wikis are frozen, users can no longer make any changes until they are unfrozen after the Jamboree.</b></p><br />
<h4>Other deadlines</h4><br />
<p>The team's project description must be documented on their iGEM Team Wiki by the deadline. The project description should be 1-3 paragraphs and only needs to include an up-to-date explanation of the project.</p><br />
<p>The team's wiki must include an attributions section.</p><br />
<h4>Creative Commons</h4><br />
<p>All content on this wiki is available under the Creative Commons <a href="http://creativecommons.org/licenses/by/4.0/">Attribution 4.0</a> license (or any later version).<br />
<img src="http://i.creativecommons.org/l/by/3.0/88x31.png"></p><br />
<br /><br /><br />
<br />
</html><br />
<br />
===Wiki Editing===<br />
<html><br />
<h4>Add a wiki page, change a wiki page, delete a wiki page, etc.</h4><br />
<p>All iGEM wiki sites are powered by Mediawiki. See the <a href="http://www.mediawiki.org/wiki/Help:Contents">Mediawiki Help page</a> for details on how to edit wiki pages and more.</p><br />
<p>Using/editing the wiki is a trial-and-error process. Editing the wiki is a simple, fun thing to do and you definitely get better the more you play around with it. The key is to take a look at other wiki pages and see what you like. Then all you have to do is go to the source (either view source if you're not logged in, or edit if you are logged in), copy it, and modify it to fit your needs. It doesn't have to be perfect before you can take a look at what it looks like. Try things out and see what results they yield.</p><br />
<br />
<h4>Adding a page to your team's namespace?</h4><br />
<p>You must keep your team's pages in your team namespace. For example, take a look at <a href="https://2014.igem.org/Team:Example">2014.igem.org/Team:Example</a></p> <br />
<p>Specifically, when you create a new page, you just have to name it <b>Team</b>:<a href="https://igem.org/Team_List">OFFICIAL team name</a>/PageName. For example, if you were on Team Example and wanted to create a Biosensor project page you would name it <b>Team:Example/Biosensor_project</b>.</p><br />
<br />
<h4>Using html in wiki pages</h4><br />
<p>Instead of using wiki markup, you can use <b>html</b> in the wiki editor. Just put your html code in between <i>&lt;html>&lt;/html></i></p><br />
<br />
<h4>Using CSS and/or Javascript</h4><br />
<p>You can also use <b>CSS</b> and <b>Javascript</b> on the wiki by adding your <i>&lt;style></i> and <i>&lt;script></i> tags into your <i>&lt;html></i> code.</p><br />
<p>If you want to use a CSS stylesheet or Javascript on multiple pages, you can create a <b>wiki template page</b>.</p><br />
<br />
<h4>Using Wiki Templates</h4><br />
<p>If there is standard text/code that you want to add to more than one page, like a CSS style or script, then you can use <a href="http://www.mediawiki.org/wiki/Help:Templates">MediaWiki templates</a></p><br />
<p>You can create a <b>wiki template page</b> to house your HTML/CSS/Javascript, by entering <i>{{Team:YourTeamName/CSS}}</i> into your wiki markup. Saving the page will create a link for a new template page, which you can edit and enter all of your CSS code. You can then call <i>{{Team:YourTeamName/CSS}}</i> on other pages.</p><br />
<p>Take a look at a few 2013 team wikis to see how other teams setup the styling. You can do this by going to a wiki, and looking for <i>view source</i> in the default wiki links at the top of the page. See <a href="https://2013.igem.org/Template:MIT-style">MIT's</a> and <a href="https://2013.igem.org/Team:TU-Munich">TU-Munich's</a> for examples.</p><br />
<br />
<h4>Uploading videos and using HTML 5 to display them</h4><br />
<p>You can upload videos (ogg, mov) to the 2014 wiki by using Mediawiki's <a href="https://2014.igem.org/Special:Upload">Upload tool</a>.</p><br />
<p>You can display videos by using the HTML 5 <i>&lt;video></i> tag, along with <i>&lt;source src="file_url" type="video/mov" /></i>.</p><br />
<p>Take a look at the <a href="https://2013.igem.org/Team:Leeds">2013 Leed's team wiki</a> to see how they displayed their video. You can do this by going to their wiki, and looking for <i>view source</i> in the default wiki links at the top of the page.</p><br />
<br />
<br /><br /><br />
</html><br />
<br />
===Perspectives from an iGEM veteran===<br />
<html><br />
<table cellspacing="10" style="text-align: justify;" width="965px"><br />
<br />
<tr> <br />
<br />
<td width="48%"><br />
Hello iGEMers!<br />
<br><br />
I was also part of an iGEM team!<br />
<br><br />
In 2011 and 2012 my role was to design and create our team’s wiki. So wiki freeze was my major deadline. I am by no means an expert but let me share with you some of the things I learned with two wiki freezes under my belt.<br />
<br><br><br />
<b> 1.- Test your webpage layout: is information easy to find?</b> </br><br />
<p> I made the terrible mistake of not asking for a third party’s opinion about the layout of information on our site. It was obvious for me how things were laid out and organized. It wasn’t for the people evaluating us. <br><br />
Also, stick to the 3 click rule: content must reachable within 3 clicks so the user does not feel lost or confused. If someone wants to read your abstract, their path should be something like this (Menu –> Project –> Project Description -> Abstract)</p><br />
<br><br />
<b> 2.- Look at other teams’ code, see how they documented and what resources they used. </b><br><br />
<p> It is always good to get inspiration from other iGEM teams. See what you liked that they did and strive to improve! </p><br />
<br><br />
<b> 3.- Start working on your documentation early on. </b> <br><br />
<p>This was a good thing that we did; we created a common file that more than one person can edit at a time. Divide the documentation into smaller files and assign a team member to fully document that topic. In the end you will have a printable version of your project that you can share as a pdf file with other people!</p><br />
<br><br />
<br />
</td><br />
<br />
<td width="4%"></td><br />
<br />
<td width="48%" valign="top"><br />
<b> 4.- Name your images according to the project and keep them all in a folder on your computer. </b> <br><br />
<p> Sometimes naming your gel image “gelthingy_whyiamworkingat3am” sounds perfect at 3AM but later it may not be easy to know what or when that photograph was taken or that image created. <br><br />
Also, the iGEM database doesn’t know that you created that file so if someone names their file with the same name it can end up being replaced! Avoid using generic names like “banner.png” or “logo.jpg”.<br><br />
Try using your team’s name and the webpage where the image will appear, this helps you remember where to place it and reduce the risk of another team overwriting. “JoyUniversity_TeamBios_Richard.jpg” </p><br />
<br><br />
<b> 5.- Do not leave everything to the last minute! </b><br />
<br />
<p> Plan ahead. The last thing you want to be doing at 11:30PM the night of wiki freeze is uploading images. It is very stressful to be looking at the clock and hoping some kind of coding miracle helps you fix bugs faster. Plan to have everything online at least one week ahead so you can go enjoy a nice dinner with your team that night! </p><br />
<br />
<br />
<p> I hope this helps and if you have any questions, feel free to email me or send me a tweet! </p><br />
<i> ana at igem dot org </i><br />
<br><br />
<i> <A HREF="https://twitter.com/anita_sifuentes" > @anita_sifuentes </A> </i><br />
<br />
</td><br />
</tr><br />
</table><br />
<br /><br />
<br />
</html><br />
<br />
===Wiki Templates===<br />
<html><br />
<p> This year we have created a set of template pages that you may for your wiki! <BR> Feel free to edit them as much as you want </p><br />
<a href="https://2014.igem.org/WikitemplateA_home ">Wiki Template A </a></br><br />
<a href="https://2014.igem.org/WikitemplateB_home ">Wiki Template B </a><br />
<BR><BR><br />
<br />
</div><br />
</html><br />
{{MainPage2014/Footer}}</div>Vinoohttp://2014.igem.org/Wiki_How-ToWiki How-To2014-10-16T22:25:47Z<p>Vinoo: </p>
<hr />
<div>{{CSS/Main}}<br />
{{NavBar}}<br />
<html><br />
<div id="contentcontainer"><br />
<br />
</html><br />
{{TOCright}}<br />
===Wiki Freeze - October 17th (11:59 PM -EDT)===<br />
<html><br />
<br />
<p><b><span style="color:red;">Warning: Do not wait till the last minute! There will be a lot of traffic on the iGEM wiki starting as early as Wednesday (October 15th). Upload your content early and avoid issues caused by server load.</span></b></p><br />
<br />
<p>Your team's project must be documented on the iGEM 2014 wiki, the parts used in your project must be documented on the <a href="http://parts.igem.org">Registry of Standard Biological Parts</a>. You have the freedom to be creative, but a few specific rules apply:</p><br />
<br />
<br />
<br /><br />
<br /><br />
<br />
<br />
<style type="text/css"><br />
.simpleTable {<br />
cellspacing: 0;<br />
}<br />
.simpleTable th, .simpleTable td {<br />
padding: 10px 15px;<br />
}<br />
.simpleTable th {<br />
color: #fff;<br />
background-color: #333;<br />
font-style: italic;<br />
font-size: 14pt;<br />
}<br />
.simpleTable tr:nth-child(even) {<br />
background-color: #f0f0f0;<br />
}<br />
</style><br />
</html><br />
<br />
===Wiki Dos and Don'ts===<br />
<html><br />
<table class="simpleTable"><br />
<tr><br />
<th width="250px">Do</th><br />
<th width="250px">Don't</th><br />
<th width="460px">Why?</th><br />
</tr><br />
<tr><br />
<td>Make sure all wiki content, from code and scripts, to files, is hosted on <b>2014.igem.org</b></td><br />
<td>Don't host your wiki or parts of your wiki elsewhere</td><br />
<td>iGEM content is preserved on our servers so future teams can learn from what you've done. When content is stored on other sites/servers, links may become broken (<a href="https://static.igem.org/mediawiki/2014/d/d6/Wiki_server_example1.jpg" title="images were stored off-site, and became broken" target="_blank">example</a>), sites may go down, and <b>information will be lost.</b></td><br />
</tr><br />
<tr><br />
<td>Work on your wiki throughout the year and <b>save small edits for last</b></td><br />
<td>Don't wait to add/edit large portions of wiki content the day of the <b>Wiki Freeze</b></td><br />
<td>Just before the Wiki Freeze, iGEM websites experience <b>increased traffic and server loads.</b> This can be a difficult time to make larger changes or additions to your wiki. Don't wait till the last minute!</td><br />
</tr><br />
<tr><br />
<td>Name uploaded files clearly and uniquely (TeamName_Header.png)</td><br />
<td>Don't use generic names for you files (Header.png)</td><br />
<td>Using <b>unique names</b> makes searching/identification of uploaded files easier, and helps prevent files from being overwritten.</td><br />
</tr><br />
<tr><br />
<td>Load your CSS and Javascript into the wiki, either directly into your page or using templates (<a href="https://2014.igem.org/wiki/index.php?title=Wiki_How-To&action=submit#Wiki_Editing">see below</a>)</td><br />
<td>Don't try to host your CSS and Javascript on a third party server</td><br />
<td>You are required to host all content on the iGEM servers (<a href="https://2014.igem.org/wiki/index.php?title=Wiki_How-To&action=submit#Wiki_Requirements">see below</a>)</td><br />
</tr><br />
</table><br />
<br /><br /><br />
<br />
</html><br />
<br />
===Wiki Requirements===<br />
<html><br />
<h4>iGEM Logo</h4><br />
<p>All iGEM Team Wikis must include the iGEM logo at the top of the page and a visible link back to the iGEM 2014 Wiki Main Page in the header (or at the top of the page). All wiki pages must preserve the user editing menu (notifications, username, messages, history, edit). In the case where the user heading is not visible, an automatic heading will be overlaid on top of the wiki page(s) where the heading is missing. </p><br />
<h4>The iGEM Login Bar</h4><br />
<p>The iGEM Login Bar is a 20 pixel high, full-width menu bar that exists on all 2014.igem.org pages. It contains:<br />
<ul><br />
<li>wiki tools (edit, history, watch, etc.)</li><br />
<li>login</li><br />
</ul><br />
All iGEM 2014 Team Wikis are required to have the Login Bar. All wiki pages must preserve the user editing menu (notifications, username, messages, history, edit). Please keep this in mind as you design your wiki.</p><br />
<h4>No Adobe Flash</h4> <br />
<p>Flash is not permitted on the iGEM 2014 wiki. Adobe flash is 100% proprietary and you cannot view the source like you can with our wiki. We chose wikis for teams to build their projects so the source code would be available for future teams, to build on the concept of open source. Flash can also be hosted on external sites and we want 100% of the content of our wikis to be on our wikis. </p> <br />
<h4>Upload to 2014.igem.org server</h4><br />
<p>All team pages, images, documents and <b>code</b> must be hosted on the <b>2014.igem.org</b> server. We preserve all iGEM content on our own servers so future teams can learn from what you have done. When you store content on your own sites or servers, after time, links might become broken, sites might go down, and information will be lost. <br /><br />
Additionally, hosting content outside of 2014.iGEM.org allows teams to change/add information to their wiki after the wiki freeze. Please note, that altering content after the wiki freeze is a <a href="https://2014.igem.org/Responsible_Conduct">form of cheating</a>. <br /><br />
Load your CSS and Javascript into the wiki, either directly into your page or using templates (<a href="https://2014.igem.org/wiki/index.php?title=Wiki_How-To&action=submit#Wiki_Editing">see below</a>)<br />
</p><br />
<h4>No iframes</h4> <br />
<p><b>iframes</b> are not permitted on the iGEM wiki. If an iframe was used to access content outside of <b>2014.igem.org</b>...<br />
<ul><br />
<li>it would break when there was an issue with the outside server</li> <br />
<li>it would allow a team to show change/add content after the wiki freeze. Please note, that altering content after the wiki freeze is a <a href="https://2014.igem.org/Responsible_Conduct">form of cheating</a></li> <br />
</ul><br />
</p><br />
<h4>2014.igem.org/Team:Team_Name</h4><br />
<p>All iGEM 2014 teams are given a namespace on the iGEM 2014 wiki with their team name. Teams are allowed to create and edit pages within their respective team namespace. Teams are <b>not allowed</b> to create or edit pages belonging to another team's namespace.</p><br />
<h4>Wiki Freeze - October 17th</h4><br />
<p>The wiki freeze for the 2014 Giant Jamboree is on <a href="https://2014.igem.org/Calendar_of_Events">October 17th,</a> along with other deadlines. iGEM experiences higher than normal traffic on this day which can lead to strain on our servers and sessions timing out for users. iGEM HQ recommends that users do not wait till the last day to work/finish their wikis. <b>Once the wikis are frozen, users can no longer make any changes until they are unfrozen after the Jamboree.</b></p><br />
<h4>Other deadlines</h4><br />
<p>The team's project description must be documented on their iGEM Team Wiki by the deadline. The project description should be 1-3 paragraphs and only needs to include an up-to-date explanation of the project.</p><br />
<p>The team's wiki must include an attributions section.</p><br />
<h4>Creative Commons</h4><br />
<p>All content on this wiki is available under the Creative Commons <a href="http://creativecommons.org/licenses/by/4.0/">Attribution 4.0</a> license (or any later version).<br />
<img src="http://i.creativecommons.org/l/by/3.0/88x31.png"></p><br />
<br /><br /><br />
<br />
</html><br />
<br />
===Wiki Editing===<br />
<html><br />
<h4>Add a wiki page, change a wiki page, delete a wiki page, etc.</h4><br />
<p>All iGEM wiki sites are powered by Mediawiki. See the <a href="http://www.mediawiki.org/wiki/Help:Contents">Mediawiki Help page</a> for details on how to edit wiki pages and more.</p><br />
<p>Using/editing the wiki is a trial-and-error process. Editing the wiki is a simple, fun thing to do and you definitely get better the more you play around with it. The key is to take a look at other wiki pages and see what you like. Then all you have to do is go to the source (either view source if you're not logged in, or edit if you are logged in), copy it, and modify it to fit your needs. It doesn't have to be perfect before you can take a look at what it looks like. Try things out and see what results they yield.</p><br />
<br />
<h4>Adding a page to your team's namespace?</h4><br />
<p>You must keep your team's pages in your team namespace. For example, take a look at <a href="https://2014.igem.org/Team:Example">2014.igem.org/Team:Example</a></p> <br />
<p>Specifically, when you create a new page, you just have to name it <b>Team</b>:<a href="https://igem.org/Team_List">OFFICIAL team name</a>/PageName. For example, if you were on Team Example and wanted to create a Biosensor project page you would name it <b>Team:Example/Biosensor_project</b>.</p><br />
<br />
<h4>Using html in wiki pages</h4><br />
<p>Instead of using wiki markup, you can use <b>html</b> in the wiki editor. Just put your html code in between <i>&lt;html>&lt;/html></i></p><br />
<br />
<h4>Using CSS and/or Javascript</h4><br />
<p>You can also use <b>CSS</b> and <b>Javascript</b> on the wiki by adding your <i>&lt;style></i> and <i>&lt;script></i> tags into your <i>&lt;html></i> code.</p><br />
<p>If you want to use a CSS stylesheet or Javascript on multiple pages, you can create a <b>wiki template page</b>.</p><br />
<br />
<h4>Using Wiki Templates</h4><br />
<p>If there is standard text/code that you want to add to more than one page, like a CSS style or script, then you can use <a href="http://www.mediawiki.org/wiki/Help:Templates">MediaWiki templates</a></p><br />
<p>You can create a <b>wiki template page</b> to house your HTML/CSS/Javascript, by entering <i>{{Team:YourTeamName/CSS}}</i> into your wiki markup. Saving the page will create a link for a new template page, which you can edit and enter all of your CSS code. You can then call <i>{{Team:YourTeamName/CSS}}</i> on other pages.</p><br />
<p>Take a look at a few 2013 team wikis to see how other teams setup the styling. You can do this by going to a wiki, and looking for <i>view source</i> in the default wiki links at the top of the page. See <a href="https://2013.igem.org/Template:MIT-style">MIT's</a> and <a href="https://2013.igem.org/Team:TU-Munich">TU-Munich's</a> for examples.</p><br />
<br />
<h4>Uploading videos and using HTML 5 to display them</h4><br />
<p>You can upload videos (mp4) to the 2014 wiki by using Mediawiki's <a href="https://2014.igem.org/Special:Upload">Upload tool</a>.</p><br />
<p>You can display videos by using the HTML 5 <i>&lt;video></i> tag, along with <i>&lt;source src="file_url" type="video/mp4" /></i>.</p><br />
<p>Take a look at the <a href="https://2013.igem.org/Team:Leeds">2013 Leed's team wiki</a> to see how they displayed their video. You can do this by going to their wiki, and looking for <i>view source</i> in the default wiki links at the top of the page.</p><br />
<br />
<br /><br /><br />
</html><br />
<br />
===Perspectives from an iGEM veteran===<br />
<html><br />
<table cellspacing="10" style="text-align: justify;" width="965px"><br />
<br />
<tr> <br />
<br />
<td width="48%"><br />
Hello iGEMers!<br />
<br><br />
I was also part of an iGEM team!<br />
<br><br />
In 2011 and 2012 my role was to design and create our team’s wiki. So wiki freeze was my major deadline. I am by no means an expert but let me share with you some of the things I learned with two wiki freezes under my belt.<br />
<br><br><br />
<b> 1.- Test your webpage layout: is information easy to find?</b> </br><br />
<p> I made the terrible mistake of not asking for a third party’s opinion about the layout of information on our site. It was obvious for me how things were laid out and organized. It wasn’t for the people evaluating us. <br><br />
Also, stick to the 3 click rule: content must reachable within 3 clicks so the user does not feel lost or confused. If someone wants to read your abstract, their path should be something like this (Menu –> Project –> Project Description -> Abstract)</p><br />
<br><br />
<b> 2.- Look at other teams’ code, see how they documented and what resources they used. </b><br><br />
<p> It is always good to get inspiration from other iGEM teams. See what you liked that they did and strive to improve! </p><br />
<br><br />
<b> 3.- Start working on your documentation early on. </b> <br><br />
<p>This was a good thing that we did; we created a common file that more than one person can edit at a time. Divide the documentation into smaller files and assign a team member to fully document that topic. In the end you will have a printable version of your project that you can share as a pdf file with other people!</p><br />
<br><br />
<br />
</td><br />
<br />
<td width="4%"></td><br />
<br />
<td width="48%" valign="top"><br />
<b> 4.- Name your images according to the project and keep them all in a folder on your computer. </b> <br><br />
<p> Sometimes naming your gel image “gelthingy_whyiamworkingat3am” sounds perfect at 3AM but later it may not be easy to know what or when that photograph was taken or that image created. <br><br />
Also, the iGEM database doesn’t know that you created that file so if someone names their file with the same name it can end up being replaced! Avoid using generic names like “banner.png” or “logo.jpg”.<br><br />
Try using your team’s name and the webpage where the image will appear, this helps you remember where to place it and reduce the risk of another team overwriting. “JoyUniversity_TeamBios_Richard.jpg” </p><br />
<br><br />
<b> 5.- Do not leave everything to the last minute! </b><br />
<br />
<p> Plan ahead. The last thing you want to be doing at 11:30PM the night of wiki freeze is uploading images. It is very stressful to be looking at the clock and hoping some kind of coding miracle helps you fix bugs faster. Plan to have everything online at least one week ahead so you can go enjoy a nice dinner with your team that night! </p><br />
<br />
<br />
<p> I hope this helps and if you have any questions, feel free to email me or send me a tweet! </p><br />
<i> ana at igem dot org </i><br />
<br><br />
<i> <A HREF="https://twitter.com/anita_sifuentes" > @anita_sifuentes </A> </i><br />
<br />
</td><br />
</tr><br />
</table><br />
<br /><br />
<br />
</html><br />
<br />
===Wiki Templates===<br />
<html><br />
<p> This year we have created a set of template pages that you may for your wiki! <BR> Feel free to edit them as much as you want </p><br />
<a href="https://2014.igem.org/WikitemplateA_home ">Wiki Template A </a></br><br />
<a href="https://2014.igem.org/WikitemplateB_home ">Wiki Template B </a><br />
<BR><BR><br />
<br />
</div><br />
</html><br />
{{MainPage2014/Footer}}</div>Vinoohttp://2014.igem.org/Wiki_How-ToWiki How-To2014-10-16T22:24:52Z<p>Vinoo: </p>
<hr />
<div>{{CSS/Main}}<br />
{{NavBar}}<br />
<html><br />
<div id="contentcontainer"><br />
<br />
</html><br />
{{TOCright}}<br />
===Wiki Freeze - October 17th (11:59 PM -EDT)===<br />
<html><br />
<br />
<p><b><span style="color:red;">Warning: Do not wait till the last minute! There will be a lot of traffic on the iGEM wiki starting as early as Wednesday (October 15th). Upload your content early and avoid issues caused by server load.</span></b></p><br />
<br />
<p>Your team's project must be documented on the iGEM 2014 wiki, the parts used in your project must be documented on the <a href="http://parts.igem.org">Registry of Standard Biological Parts</a>. You have the freedom to be creative, but a few specific rules apply:</p><br />
<br />
<br />
<br /><br />
<br /><br />
<br />
<br />
<style type="text/css"><br />
.simpleTable {<br />
cellspacing: 0;<br />
}<br />
.simpleTable th, .simpleTable td {<br />
padding: 10px 15px;<br />
}<br />
.simpleTable th {<br />
color: #fff;<br />
background-color: #333;<br />
font-style: italic;<br />
font-size: 14pt;<br />
}<br />
.simpleTable tr:nth-child(even) {<br />
background-color: #f0f0f0;<br />
}<br />
</style><br />
</html><br />
<br />
===Wiki Dos and Don'ts===<br />
<html><br />
<table class="simpleTable"><br />
<tr><br />
<th width="250px">Do</th><br />
<th width="250px">Don't</th><br />
<th width="460px">Why?</th><br />
</tr><br />
<tr><br />
<td>Make sure all wiki content, from code and scripts, to files, is hosted on <b>2014.igem.org</b></td><br />
<td>Don't host your wiki or parts of your wiki elsewhere</td><br />
<td>iGEM content is preserved on our servers so future teams can learn from what you've done. When content is stored on other sites/servers, links may become broken (<a href="https://static.igem.org/mediawiki/2014/d/d6/Wiki_server_example1.jpg" title="images were stored off-site, and became broken" target="_blank">example</a>), sites may go down, and <b>information will be lost.</b></td><br />
</tr><br />
<tr><br />
<td>Work on your wiki throughout the year and <b>save small edits for last</b></td><br />
<td>Don't wait to add/edit large portions of wiki content the day of the <b>Wiki Freeze</b></td><br />
<td>Just before the Wiki Freeze, iGEM websites experience <b>increased traffic and server loads.</b> This can be a difficult time to make larger changes or additions to your wiki. Don't wait till the last minute!</td><br />
</tr><br />
<tr><br />
<td>Name uploaded files clearly and uniquely (TeamName_Header.png)</td><br />
<td>Don't use generic names for you files (Header.png)</td><br />
<td>Using <b>unique names</b> makes searching/identification of uploaded files easier, and helps prevent files from being overwritten.</td><br />
</tr><br />
<tr><br />
<td>Load your CSS and Javascript into the wiki, either directly into your page or using templates (<a href="https://2014.igem.org/wiki/index.php?title=Wiki_How-To&action=submit#Wiki_Editing">see below</a>)</td><br />
<td>Don't try to host your CSS and Javascript on a third party server</td><br />
<td>You are required to host all content on the iGEM servers (<a href="https://2014.igem.org/wiki/index.php?title=Wiki_How-To&action=submit#Wiki_Requirements">see below</a>)</td><br />
</tr><br />
</table><br />
<br /><br /><br />
<br />
</html><br />
<br />
===Wiki Requirements===<br />
<html><br />
<h4>iGEM Logo</h4><br />
<p>All iGEM Team Wikis must include the iGEM logo at the top of the page and a visible link back to the iGEM 2014 Wiki Main Page in the header (or at the top of the page). All wiki pages must preserve the user editing menu (notifications, username, messages, history, edit). In the case where the user heading is not visible, an automatic heading will be overlaid on top of the wiki page(s) where the heading is missing. </p><br />
<h4>The iGEM Login Bar</h4><br />
<p>The iGEM Login Bar is a 20 pixel high, full-width menu bar that exists on all 2014.igem.org pages. It contains:<br />
<ul><br />
<li>wiki tools (edit, history, watch, etc.)</li><br />
<li>login</li><br />
</ul><br />
All iGEM 2014 Team Wikis are required to have the Login Bar. All wiki pages must preserve the user editing menu (notifications, username, messages, history, edit). Please keep this in mind as you design your wiki.</p><br />
<h4>No Adobe Flash</h4> <br />
<p>Flash is not permitted on the iGEM 2014 wiki. Adobe flash is 100% proprietary and you cannot view the source like you can with our wiki. We chose wikis for teams to build their projects so the source code would be available for future teams, to build on the concept of open source. Flash can also be hosted on external sites and we want 100% of the content of our wikis to be on our wikis. </p> <br />
<h4>Upload to 2014.igem.org server</h4><br />
<p>All team pages, images, documents and <b>code</b> must be hosted on the <b>2014.igem.org</b> server. We preserve all iGEM content on our own servers so future teams can learn from what you have done. When you store content on your own sites or servers, after time, links might become broken, sites might go down, and information will be lost. <br /><br />
Additionally, hosting content outside of 2014.iGEM.org allows teams to change/add information to their wiki after the wiki freeze. Please note, that altering content after the wiki freeze is a <a href="https://2014.igem.org/Responsible_Conduct">form of cheating</a>. <br /><br />
Load your CSS and Javascript into the wiki, either directly into your page or using templates (<a href="https://2014.igem.org/wiki/index.php?title=Wiki_How-To&action=submit#Wiki_Editing">see below</a>)<br />
</p><br />
<h4>No iframes</h4> <br />
<p><b>iframes</b> are not permitted on the iGEM wiki. If an iframe was used to access content outside of <b>2014.igem.org</b>...<br />
<ul><br />
<li>it would break when there was an issue with the outside server</li> <br />
<li>it would allow a team to show change/add content after the wiki freeze. Please note, that altering content after the wiki freeze is a <a href="https://2014.igem.org/Responsible_Conduct">form of cheating</a></li> <br />
</ul><br />
</p><br />
<h4>2014.igem.org/Team:Team_Name</h4><br />
<p>All iGEM 2014 teams are given a namespace on the iGEM 2014 wiki with their team name. Teams are allowed to create and edit pages within their respective team namespace. Teams are <b>not allowed</b> to create or edit pages belonging to another team's namespace.</p><br />
<h4>Wiki Freeze - October 17th</h4><br />
<p>The wiki freeze for the 2014 Giant Jamboree is on <a href="https://2014.igem.org/Calendar_of_Events">October 17th,</a> along with other deadlines. iGEM experiences higher than normal traffic on this day which can lead to strain on our servers and sessions timing out for users. iGEM HQ recommends that users do not wait till the last day to work/finish their wikis. <b>Once the wikis are frozen, users can no longer make any changes until they are unfrozen after the Jamboree.</b></p><br />
<h4>Other deadlines</h4><br />
<p>The team's project description must be documented on their iGEM Team Wiki by the deadline. The project description should be 1-3 paragraphs and only needs to include an up-to-date explanation of the project.</p><br />
<p>The team's wiki must include an attributions section.</p><br />
<h4>Creative Commons</h4><br />
<p>All content on this wiki is available under the Creative Commons <a href="http://creativecommons.org/licenses/by/4.0/">Attribution 4.0</a> license (or any later version).<br />
<img src="http://i.creativecommons.org/l/by/3.0/88x31.png"></p><br />
<br /><br /><br />
<br />
</html><br />
<br />
===Wiki Editing===<br />
<html><br />
<h4>Add a wiki page, change a wiki page, delete a wiki page, etc.</h4><br />
<p>All iGEM wiki sites are powered by Mediawiki. See the <a href="http://www.mediawiki.org/wiki/Help:Contents">Mediawiki Help page</a> for details on how to edit wiki pages and more.</p><br />
<p>Using/editing the wiki is a trial-and-error process. Editing the wiki is a simple, fun thing to do and you definitely get better the more you play around with it. The key is to take a look at other wiki pages and see what you like. Then all you have to do is go to the source (either view source if you're not logged in, or edit if you are logged in), copy it, and modify it to fit your needs. It doesn't have to be perfect before you can take a look at what it looks like. Try things out and see what results they yield.</p><br />
<br />
<h4>Adding a page to your team's namespace?</h4><br />
<p>You must keep your team's pages in your team namespace. For example, take a look at <a href="https://2014.igem.org/Team:Example">2014.igem.org/Team:Example</a></p> <br />
<p>Specifically, when you create a new page, you just have to name it <b>Team</b>:<a href="https://igem.org/Team_List">OFFICIAL team name</a>/PageName. For example, if you were on Team Example and wanted to create a Biosensor project page you would name it <b>Team:Example/Biosensor_project</b>.</p><br />
<br />
<h4>Using html in wiki pages</h4><br />
<p>Instead of using wiki markup, you can use <b>html</b> in the wiki editor. Just put your html code in between <i>&lt;html>&lt;/html></i></p><br />
<br />
<h4>Using CSS and/or Javascript</h4><br />
<p>You can also use <b>CSS</b> and <b>Javascript</b> on the wiki by adding your <i>&lt;style></i> and <i>&lt;script></i> tags into your <i>&lt;html></i> code.</p><br />
<p>If you want to use a CSS stylesheet or Javascript on multiple pages, you can create a <b>wiki template page</b>.</p><br />
<br />
<h4>Using Wiki Templates</h4><br />
<p>If there is standard text/code that you want to add to more than one page, like a CSS style or script, then you can use <a href="http://www.mediawiki.org/wiki/Help:Templates">MediaWiki templates</a></p><br />
<p>You can create a <b>wiki template page</b> to house your HTML/CSS/Javascript, by entering <i>{{Team:YourTeamName/CSS}}</i> into your wiki markup. Saving the page will create a link for a new template page, which you can edit and enter all of your CSS code. You can then call <i>{{Team:YourTeamName/CSS}}</i> on other pages.</p><br />
<p>Take a look at a few 2013 team wikis to see how other teams setup the styling. You can do this by going to a wiki, and looking for <i>view source</i> in the default wiki links at the top of the page. See <a href="https://2013.igem.org/Template:MIT-style">MIT's</a> and <a href="https://2013.igem.org/Team:TU-Munich">TU-Munich's</a> for examples.</p><br />
<br />
<h4>Uploading videos and using HTML 5 to display them</h4><br />
<p>You can upload videos to the 2014 wiki by using Mediawiki's <a href="https://2014.igem.org/Special:Upload">Upload tool</a>.</p><br />
<p>You can display videos by using the HTML 5 <i>&lt;video></i> tag, along with <i>&lt;source src="file url" type="video/file_type" /></i>.</p><br />
<p>Take a look at the <a href="https://2013.igem.org/Team:Leeds">2013 Leed's team wiki</a> to see how they displayed their video. You can do this by going to their wiki, and looking for <i>view source</i> in the default wiki links at the top of the page.</p><br />
<br />
<br /><br /><br />
</html><br />
<br />
===Perspectives from an iGEM veteran===<br />
<html><br />
<table cellspacing="10" style="text-align: justify;" width="965px"><br />
<br />
<tr> <br />
<br />
<td width="48%"><br />
Hello iGEMers!<br />
<br><br />
I was also part of an iGEM team!<br />
<br><br />
In 2011 and 2012 my role was to design and create our team’s wiki. So wiki freeze was my major deadline. I am by no means an expert but let me share with you some of the things I learned with two wiki freezes under my belt.<br />
<br><br><br />
<b> 1.- Test your webpage layout: is information easy to find?</b> </br><br />
<p> I made the terrible mistake of not asking for a third party’s opinion about the layout of information on our site. It was obvious for me how things were laid out and organized. It wasn’t for the people evaluating us. <br><br />
Also, stick to the 3 click rule: content must reachable within 3 clicks so the user does not feel lost or confused. If someone wants to read your abstract, their path should be something like this (Menu –> Project –> Project Description -> Abstract)</p><br />
<br><br />
<b> 2.- Look at other teams’ code, see how they documented and what resources they used. </b><br><br />
<p> It is always good to get inspiration from other iGEM teams. See what you liked that they did and strive to improve! </p><br />
<br><br />
<b> 3.- Start working on your documentation early on. </b> <br><br />
<p>This was a good thing that we did; we created a common file that more than one person can edit at a time. Divide the documentation into smaller files and assign a team member to fully document that topic. In the end you will have a printable version of your project that you can share as a pdf file with other people!</p><br />
<br><br />
<br />
</td><br />
<br />
<td width="4%"></td><br />
<br />
<td width="48%" valign="top"><br />
<b> 4.- Name your images according to the project and keep them all in a folder on your computer. </b> <br><br />
<p> Sometimes naming your gel image “gelthingy_whyiamworkingat3am” sounds perfect at 3AM but later it may not be easy to know what or when that photograph was taken or that image created. <br><br />
Also, the iGEM database doesn’t know that you created that file so if someone names their file with the same name it can end up being replaced! Avoid using generic names like “banner.png” or “logo.jpg”.<br><br />
Try using your team’s name and the webpage where the image will appear, this helps you remember where to place it and reduce the risk of another team overwriting. “JoyUniversity_TeamBios_Richard.jpg” </p><br />
<br><br />
<b> 5.- Do not leave everything to the last minute! </b><br />
<br />
<p> Plan ahead. The last thing you want to be doing at 11:30PM the night of wiki freeze is uploading images. It is very stressful to be looking at the clock and hoping some kind of coding miracle helps you fix bugs faster. Plan to have everything online at least one week ahead so you can go enjoy a nice dinner with your team that night! </p><br />
<br />
<br />
<p> I hope this helps and if you have any questions, feel free to email me or send me a tweet! </p><br />
<i> ana at igem dot org </i><br />
<br><br />
<i> <A HREF="https://twitter.com/anita_sifuentes" > @anita_sifuentes </A> </i><br />
<br />
</td><br />
</tr><br />
</table><br />
<br /><br />
<br />
</html><br />
<br />
===Wiki Templates===<br />
<html><br />
<p> This year we have created a set of template pages that you may for your wiki! <BR> Feel free to edit them as much as you want </p><br />
<a href="https://2014.igem.org/WikitemplateA_home ">Wiki Template A </a></br><br />
<a href="https://2014.igem.org/WikitemplateB_home ">Wiki Template B </a><br />
<BR><BR><br />
<br />
</div><br />
</html><br />
{{MainPage2014/Footer}}</div>Vinoohttp://2014.igem.org/Wiki_How-ToWiki How-To2014-10-16T22:19:53Z<p>Vinoo: </p>
<hr />
<div>{{CSS/Main}}<br />
{{NavBar}}<br />
<html><br />
<div id="contentcontainer"><br />
<br />
</html><br />
{{TOCright}}<br />
===Wiki Freeze - October 17th (11:59 PM -EDT)===<br />
<html><br />
<br />
<p><b><span style="color:red;">Warning: Do not wait till the last minute! There will be a lot of traffic on the iGEM wiki starting as early as Wednesday (October 15th). Upload your content early and avoid issues caused by server load.</span></b></p><br />
<br />
<p>Your team's project must be documented on the iGEM 2014 wiki, the parts used in your project must be documented on the <a href="http://parts.igem.org">Registry of Standard Biological Parts</a>. You have the freedom to be creative, but a few specific rules apply:</p><br />
<br />
<br />
<br /><br />
<br /><br />
<br />
<br />
<style type="text/css"><br />
.simpleTable {<br />
cellspacing: 0;<br />
}<br />
.simpleTable th, .simpleTable td {<br />
padding: 10px 15px;<br />
}<br />
.simpleTable th {<br />
color: #fff;<br />
background-color: #333;<br />
font-style: italic;<br />
font-size: 14pt;<br />
}<br />
.simpleTable tr:nth-child(even) {<br />
background-color: #f0f0f0;<br />
}<br />
</style><br />
</html><br />
<br />
===Wiki Dos and Don'ts===<br />
<html><br />
<table class="simpleTable"><br />
<tr><br />
<th width="250px">Do</th><br />
<th width="250px">Don't</th><br />
<th width="460px">Why?</th><br />
</tr><br />
<tr><br />
<td>Make sure all wiki content, from code and scripts, to files, is hosted on <b>2014.igem.org</b></td><br />
<td>Don't host your wiki or parts of your wiki elsewhere</td><br />
<td>iGEM content is preserved on our servers so future teams can learn from what you've done. When content is stored on other sites/servers, links may become broken (<a href="https://static.igem.org/mediawiki/2014/d/d6/Wiki_server_example1.jpg" title="images were stored off-site, and became broken" target="_blank">example</a>), sites may go down, and <b>information will be lost.</b></td><br />
</tr><br />
<tr><br />
<td>Work on your wiki throughout the year and <b>save small edits for last</b></td><br />
<td>Don't wait to add/edit large portions of wiki content the day of the <b>Wiki Freeze</b></td><br />
<td>Just before the Wiki Freeze, iGEM websites experience <b>increased traffic and server loads.</b> This can be a difficult time to make larger changes or additions to your wiki. Don't wait till the last minute!</td><br />
</tr><br />
<tr><br />
<td>Name uploaded files clearly and uniquely (TeamName_Header.png)</td><br />
<td>Don't use generic names for you files (Header.png)</td><br />
<td>Using <b>unique names</b> makes searching/identification of uploaded files easier, and helps prevent files from being overwritten.</td><br />
</tr><br />
<tr><br />
<td>Load your CSS and Javascript into the wiki, either directly into your page or using templates (<a href="https://2014.igem.org/wiki/index.php?title=Wiki_How-To&action=submit#Wiki_Editing">see below</a>)</td><br />
<td>Don't try to host your CSS and Javascript on a third party server</td><br />
<td>You are required to host all content on the iGEM servers (<a href="https://2014.igem.org/wiki/index.php?title=Wiki_How-To&action=submit#Wiki_Requirements">see below</a>)</td><br />
</tr><br />
</table><br />
<br /><br /><br />
<br />
</html><br />
<br />
===Wiki Requirements===<br />
<html><br />
<h4>iGEM Logo</h4><br />
<p>All iGEM Team Wikis must include the iGEM logo at the top of the page and a visible link back to the iGEM 2014 Wiki Main Page in the header (or at the top of the page). All wiki pages must preserve the user editing menu (notifications, username, messages, history, edit). In the case where the user heading is not visible, an automatic heading will be overlaid on top of the wiki page(s) where the heading is missing. </p><br />
<h4>The iGEM Login Bar</h4><br />
<p>The iGEM Login Bar is a 20 pixel high, full-width menu bar that exists on all 2014.igem.org pages. It contains:<br />
<ul><br />
<li>wiki tools (edit, history, watch, etc.)</li><br />
<li>login</li><br />
</ul><br />
All iGEM 2014 Team Wikis are required to have the Login Bar. All wiki pages must preserve the user editing menu (notifications, username, messages, history, edit). Please keep this in mind as you design your wiki.</p><br />
<h4>No Adobe Flash</h4> <br />
<p>Flash is not permitted on the iGEM 2014 wiki. Adobe flash is 100% proprietary and you cannot view the source like you can with our wiki. We chose wikis for teams to build their projects so the source code would be available for future teams, to build on the concept of open source. Flash can also be hosted on external sites and we want 100% of the content of our wikis to be on our wikis. </p> <br />
<h4>Upload to 2014.igem.org server</h4><br />
<p>All team pages, images, documents and <b>code</b> must be hosted on the <b>2014.igem.org</b> server. We preserve all iGEM content on our own servers so future teams can learn from what you have done. When you store content on your own sites or servers, after time, links might become broken, sites might go down, and information will be lost. <br /><br />
Additionally, hosting content outside of 2014.iGEM.org allows teams to change/add information to their wiki after the wiki freeze. Please note, that altering content after the wiki freeze is a <a href="https://2014.igem.org/Responsible_Conduct">form of cheating</a>. <br /><br />
Load your CSS and Javascript into the wiki, either directly into your page or using templates (<a href="https://2014.igem.org/wiki/index.php?title=Wiki_How-To&action=submit#Wiki_Editing">see below</a>)<br />
</p><br />
<h4>No iframes</h4> <br />
<p><b>iframes</b> are not permitted on the iGEM wiki. If an iframe was used to access content outside of <b>2014.igem.org</b>...<br />
<ul><br />
<li>it would break when there was an issue with the outside server</li> <br />
<li>it would allow a team to show change/add content after the wiki freeze. Please note, that altering content after the wiki freeze is a <a href="https://2014.igem.org/Responsible_Conduct">form of cheating</a></li> <br />
</ul><br />
</p><br />
<h4>2014.igem.org/Team:Team_Name</h4><br />
<p>All iGEM 2014 teams are given a namespace on the iGEM 2014 wiki with their team name. Teams are allowed to create and edit pages within their respective team namespace. Teams are <b>not allowed</b> to create or edit pages belonging to another team's namespace.</p><br />
<h4>Wiki Freeze - October 17th</h4><br />
<p>The wiki freeze for the 2014 Giant Jamboree is on <a href="https://2014.igem.org/Calendar_of_Events">October 17th,</a> along with other deadlines. iGEM experiences higher than normal traffic on this day which can lead to strain on our servers and sessions timing out for users. iGEM HQ recommends that users do not wait till the last day to work/finish their wikis. <b>Once the wikis are frozen, users can no longer make any changes until they are unfrozen after the Jamboree.</b></p><br />
<h4>Other deadlines</h4><br />
<p>The team's project description must be documented on their iGEM Team Wiki by the deadline. The project description should be 1-3 paragraphs and only needs to include an up-to-date explanation of the project.</p><br />
<p>The team's wiki must include an attributions section.</p><br />
<h4>Creative Commons</h4><br />
<p>All content on this wiki is available under the Creative Commons <a href="http://creativecommons.org/licenses/by/4.0/">Attribution 4.0</a> license (or any later version).<br />
<img src="http://i.creativecommons.org/l/by/3.0/88x31.png"></p><br />
<br /><br /><br />
<br />
</html><br />
<br />
===Wiki Editing===<br />
<html><br />
<h4>Add a wiki page, change a wiki page, delete a wiki page, etc.</h4><br />
<p>All iGEM wiki sites are powered by Mediawiki. See the <a href="http://www.mediawiki.org/wiki/Help:Contents">Mediawiki Help page</a> for details on how to edit wiki pages and more.</p><br />
<p>Using/editing the wiki is a trial-and-error process. Editing the wiki is a simple, fun thing to do and you definitely get better the more you play around with it. The key is to take a look at other wiki pages and see what you like. Then all you have to do is go to the source (either view source if you're not logged in, or edit if you are logged in), copy it, and modify it to fit your needs. It doesn't have to be perfect before you can take a look at what it looks like. Try things out and see what results they yield.</p><br />
<br />
<h4>Adding a page to your team's namespace?</h4><br />
<p>You must keep your team's pages in your team namespace. For example, take a look at <a href="https://2014.igem.org/Team:Example">2014.igem.org/Team:Example</a></p> <br />
<p>Specifically, when you create a new page, you just have to name it <b>Team</b>:<a href="https://igem.org/Team_List">OFFICIAL team name</a>/PageName. For example, if you were on Team Example and wanted to create a Biosensor project page you would name it <b>Team:Example/Biosensor_project</b>.</p><br />
<br />
<h4>Using html in wiki pages</h4><br />
<p>Instead of using wiki markup, you can use <b>html</b> in the wiki editor. Just put your html code in between <i>&lt;html>&lt;/html></i></p><br />
<br />
<h4>Using CSS and/or Javascript</h4><br />
<p>You can also use <b>CSS</b> and <b>Javascript</b> on the wiki by adding your <i>&lt;style></i> and <i>&lt;script></i> tags into your <i>&lt;html></i> code.</p><br />
<p>If you want to use a CSS stylesheet or Javascript on multiple pages, you can create a <b>wiki template page</b>.</p><br />
<br />
<h4>Using Wiki Templates</h4><br />
<p>If there is standard text/code that you want to add to more than one page, like a CSS style or script, then you can use <a href="http://www.mediawiki.org/wiki/Help:Templates">MediaWiki templates</a></p><br />
<p>You can create a <b>wiki template page</b> to house your HTML/CSS/Javascript, by entering <i>{{Team:YourTeamName/CSS}}</i> into your wiki markup. Saving the page will create a link for a new template page, which you can edit and enter all of your CSS code. You can then call <i>{{Team:YourTeamName/CSS}}</i> on other pages.</p><br />
<p>Take a look at a few 2013 team wikis to see how other teams setup the styling. You can do this by going to a wiki, and looking for <i>view source</i> in the default wiki links at the top of the page. See <a href="https://2013.igem.org/Template:MIT-style">MIT's</a> and <a href="https://2013.igem.org/Team:TU-Munich">TU-Munich's</a> for examples.</p><br />
<br />
<br /><br /><br />
</html><br />
<br />
===Perspectives from an iGEM veteran===<br />
<html><br />
<table cellspacing="10" style="text-align: justify;" width="965px"><br />
<br />
<tr> <br />
<br />
<td width="48%"><br />
Hello iGEMers!<br />
<br><br />
I was also part of an iGEM team!<br />
<br><br />
In 2011 and 2012 my role was to design and create our team’s wiki. So wiki freeze was my major deadline. I am by no means an expert but let me share with you some of the things I learned with two wiki freezes under my belt.<br />
<br><br><br />
<b> 1.- Test your webpage layout: is information easy to find?</b> </br><br />
<p> I made the terrible mistake of not asking for a third party’s opinion about the layout of information on our site. It was obvious for me how things were laid out and organized. It wasn’t for the people evaluating us. <br><br />
Also, stick to the 3 click rule: content must reachable within 3 clicks so the user does not feel lost or confused. If someone wants to read your abstract, their path should be something like this (Menu –> Project –> Project Description -> Abstract)</p><br />
<br><br />
<b> 2.- Look at other teams’ code, see how they documented and what resources they used. </b><br><br />
<p> It is always good to get inspiration from other iGEM teams. See what you liked that they did and strive to improve! </p><br />
<br><br />
<b> 3.- Start working on your documentation early on. </b> <br><br />
<p>This was a good thing that we did; we created a common file that more than one person can edit at a time. Divide the documentation into smaller files and assign a team member to fully document that topic. In the end you will have a printable version of your project that you can share as a pdf file with other people!</p><br />
<br><br />
<br />
</td><br />
<br />
<td width="4%"></td><br />
<br />
<td width="48%" valign="top"><br />
<b> 4.- Name your images according to the project and keep them all in a folder on your computer. </b> <br><br />
<p> Sometimes naming your gel image “gelthingy_whyiamworkingat3am” sounds perfect at 3AM but later it may not be easy to know what or when that photograph was taken or that image created. <br><br />
Also, the iGEM database doesn’t know that you created that file so if someone names their file with the same name it can end up being replaced! Avoid using generic names like “banner.png” or “logo.jpg”.<br><br />
Try using your team’s name and the webpage where the image will appear, this helps you remember where to place it and reduce the risk of another team overwriting. “JoyUniversity_TeamBios_Richard.jpg” </p><br />
<br><br />
<b> 5.- Do not leave everything to the last minute! </b><br />
<br />
<p> Plan ahead. The last thing you want to be doing at 11:30PM the night of wiki freeze is uploading images. It is very stressful to be looking at the clock and hoping some kind of coding miracle helps you fix bugs faster. Plan to have everything online at least one week ahead so you can go enjoy a nice dinner with your team that night! </p><br />
<br />
<br />
<p> I hope this helps and if you have any questions, feel free to email me or send me a tweet! </p><br />
<i> ana at igem dot org </i><br />
<br><br />
<i> <A HREF="https://twitter.com/anita_sifuentes" > @anita_sifuentes </A> </i><br />
<br />
</td><br />
</tr><br />
</table><br />
<br /><br />
<br />
</html><br />
<br />
===Wiki Templates===<br />
<html><br />
<p> This year we have created a set of template pages that you may for your wiki! <BR> Feel free to edit them as much as you want </p><br />
<a href="https://2014.igem.org/WikitemplateA_home ">Wiki Template A </a></br><br />
<a href="https://2014.igem.org/WikitemplateB_home ">Wiki Template B </a><br />
<BR><BR><br />
<br />
</div><br />
</html><br />
{{MainPage2014/Footer}}</div>Vinoohttp://2014.igem.org/Wiki_How-ToWiki How-To2014-10-16T22:19:24Z<p>Vinoo: Reverted edits by Vinoo (talk) to last revision by Feixia</p>
<hr />
<div>{{CSS/Main}}<br />
{{NavBar}}<br />
<html><br />
<div id="contentcontainer"><br />
<br />
</html><br />
{{TOCright}}<br />
===Wiki Freeze - October 17th (11:59 PM -EDT)===<br />
<html><br />
<br />
<p><b><span style="color:red;">Warning: Do not wait till the last minute! There will be a lot of traffic on the iGEM wiki starting as early as Wednesday (October 15th). Upload your content early and avoid issues caused by server load.</span></b></p><br />
<br />
<p>Your team's project must be documented on the iGEM 2014 wiki, the parts used in your project must be documented on the <a href="http://parts.igem.org">Registry of Standard Biological Parts</a>. You have the freedom to be creative, but a few specific rules apply:</p><br />
<br />
<br />
<br /><br />
<br /><br />
<br />
<br />
<br />
<br />
<style type="text/css"><br />
.simpleTable {<br />
cellspacing: 0;<br />
}<br />
.simpleTable th, .simpleTable td {<br />
padding: 10px 15px;<br />
}<br />
.simpleTable th {<br />
color: #fff;<br />
background-color: #333;<br />
font-style: italic;<br />
font-size: 14pt;<br />
}<br />
.simpleTable tr:nth-child(even) {<br />
background-color: #f0f0f0;<br />
}<br />
</style><br />
</html><br />
<br />
===Wiki Dos and Don'ts===<br />
<html><br />
<table class="simpleTable"><br />
<tr><br />
<th width="250px">Do</th><br />
<th width="250px">Don't</th><br />
<th width="460px">Why?</th><br />
</tr><br />
<tr><br />
<td>Make sure all wiki content, from code and scripts, to files, is hosted on <b>2014.igem.org</b></td><br />
<td>Don't host your wiki or parts of your wiki elsewhere</td><br />
<td>iGEM content is preserved on our servers so future teams can learn from what you've done. When content is stored on other sites/servers, links may become broken (<a href="https://static.igem.org/mediawiki/2014/d/d6/Wiki_server_example1.jpg" title="images were stored off-site, and became broken" target="_blank">example</a>), sites may go down, and <b>information will be lost.</b></td><br />
</tr><br />
<tr><br />
<td>Work on your wiki throughout the year and <b>save small edits for last</b></td><br />
<td>Don't wait to add/edit large portions of wiki content the day of the <b>Wiki Freeze</b></td><br />
<td>Just before the Wiki Freeze, iGEM websites experience <b>increased traffic and server loads.</b> This can be a difficult time to make larger changes or additions to your wiki. Don't wait till the last minute!</td><br />
</tr><br />
<tr><br />
<td>Name uploaded files clearly and uniquely (TeamName_Header.png)</td><br />
<td>Don't use generic names for you files (Header.png)</td><br />
<td>Using <b>unique names</b> makes searching/identification of uploaded files easier, and helps prevent files from being overwritten.</td><br />
</tr><br />
<tr><br />
<td>Load your CSS and Javascript into the wiki, either directly into your page or using templates (<a href="https://2014.igem.org/wiki/index.php?title=Wiki_How-To&action=submit#Wiki_Editing">see below</a>)</td><br />
<td>Don't try to host your CSS and Javascript on a third party server</td><br />
<td>You are required to host all content on the iGEM servers (<a href="https://2014.igem.org/wiki/index.php?title=Wiki_How-To&action=submit#Wiki_Requirements">see below</a>)</td><br />
</tr><br />
</table><br />
<br /><br /><br />
<br />
</html><br />
<br />
===Wiki Requirements===<br />
<html><br />
<h4>iGEM Logo</h4><br />
<p>All iGEM Team Wikis must include the iGEM logo at the top of the page and a visible link back to the iGEM 2014 Wiki Main Page in the header (or at the top of the page). All wiki pages must preserve the user editing menu (notifications, username, messages, history, edit). In the case where the user heading is not visible, an automatic heading will be overlaid on top of the wiki page(s) where the heading is missing. </p><br />
<h4>The iGEM Login Bar</h4><br />
<p>The iGEM Login Bar is a 20 pixel high, full-width menu bar that exists on all 2014.igem.org pages. It contains:<br />
<ul><br />
<li>wiki tools (edit, history, watch, etc.)</li><br />
<li>login</li><br />
</ul><br />
All iGEM 2014 Team Wikis are required to have the Login Bar. All wiki pages must preserve the user editing menu (notifications, username, messages, history, edit). Please keep this in mind as you design your wiki.</p><br />
<h4>No Adobe Flash</h4> <br />
<p>Flash is not permitted on the iGEM 2014 wiki. Adobe flash is 100% proprietary and you cannot view the source like you can with our wiki. We chose wikis for teams to build their projects so the source code would be available for future teams, to build on the concept of open source. Flash can also be hosted on external sites and we want 100% of the content of our wikis to be on our wikis. </p> <br />
<h4>Upload to 2014.igem.org server</h4><br />
<p>All team pages, images, documents and <b>code</b> must be hosted on the <b>2014.igem.org</b> server. We preserve all iGEM content on our own servers so future teams can learn from what you have done. When you store content on your own sites or servers, after time, links might become broken, sites might go down, and information will be lost. <br /><br />
Additionally, hosting content outside of 2014.iGEM.org allows teams to change/add information to their wiki after the wiki freeze. Please note, that altering content after the wiki freeze is a <a href="https://2014.igem.org/Responsible_Conduct">form of cheating</a>. <br /><br />
Load your CSS and Javascript into the wiki, either directly into your page or using templates (<a href="https://2014.igem.org/wiki/index.php?title=Wiki_How-To&action=submit#Wiki_Editing">see below</a>)<br />
</p><br />
<h4>No iframes</h4> <br />
<p><b>iframes</b> are not permitted on the iGEM wiki. If an iframe was used to access content outside of <b>2014.igem.org</b>...<br />
<ul><br />
<li>it would break when there was an issue with the outside server</li> <br />
<li>it would allow a team to show change/add content after the wiki freeze. Please note, that altering content after the wiki freeze is a <a href="https://2014.igem.org/Responsible_Conduct">form of cheating</a></li> <br />
</ul><br />
</p><br />
<h4>2014.igem.org/Team:Team_Name</h4><br />
<p>All iGEM 2014 teams are given a namespace on the iGEM 2014 wiki with their team name. Teams are allowed to create and edit pages within their respective team namespace. Teams are <b>not allowed</b> to create or edit pages belonging to another team's namespace.</p><br />
<h4>Wiki Freeze - October 17th</h4><br />
<p>The wiki freeze for the 2014 Giant Jamboree is on <a href="https://2014.igem.org/Calendar_of_Events">October 17th,</a> along with other deadlines. iGEM experiences higher than normal traffic on this day which can lead to strain on our servers and sessions timing out for users. iGEM HQ recommends that users do not wait till the last day to work/finish their wikis. <b>Once the wikis are frozen, users can no longer make any changes until they are unfrozen after the Jamboree.</b></p><br />
<h4>Other deadlines</h4><br />
<p>The team's project description must be documented on their iGEM Team Wiki by the deadline. The project description should be 1-3 paragraphs and only needs to include an up-to-date explanation of the project.</p><br />
<p>The team's wiki must include an attributions section.</p><br />
<h4>Creative Commons</h4><br />
<p>All content on this wiki is available under the Creative Commons <a href="http://creativecommons.org/licenses/by/4.0/">Attribution 4.0</a> license (or any later version).<br />
<img src="http://i.creativecommons.org/l/by/3.0/88x31.png"></p><br />
<br /><br /><br />
<br />
</html><br />
<br />
===Wiki Editing===<br />
<html><br />
<h4>Add a wiki page, change a wiki page, delete a wiki page, etc.</h4><br />
<p>All iGEM wiki sites are powered by Mediawiki. See the <a href="http://www.mediawiki.org/wiki/Help:Contents">Mediawiki Help page</a> for details on how to edit wiki pages and more.</p><br />
<p>Using/editing the wiki is a trial-and-error process. Editing the wiki is a simple, fun thing to do and you definitely get better the more you play around with it. The key is to take a look at other wiki pages and see what you like. Then all you have to do is go to the source (either view source if you're not logged in, or edit if you are logged in), copy it, and modify it to fit your needs. It doesn't have to be perfect before you can take a look at what it looks like. Try things out and see what results they yield.</p><br />
<br />
<h4>Adding a page to your team's namespace?</h4><br />
<p>You must keep your team's pages in your team namespace. For example, take a look at <a href="https://2014.igem.org/Team:Example">2014.igem.org/Team:Example</a></p> <br />
<p>Specifically, when you create a new page, you just have to name it <b>Team</b>:<a href="https://igem.org/Team_List">OFFICIAL team name</a>/PageName. For example, if you were on Team Example and wanted to create a Biosensor project page you would name it <b>Team:Example/Biosensor_project</b>.</p><br />
<br />
<h4>Using html in wiki pages</h4><br />
<p>Instead of using wiki markup, you can use <b>html</b> in the wiki editor. Just put your html code in between <i>&lt;html>&lt;/html></i></p><br />
<br />
<h4>Using CSS and/or Javascript</h4><br />
<p>You can also use <b>CSS</b> and <b>Javascript</b> on the wiki by adding your <i>&lt;style></i> and <i>&lt;script></i> tags into your <i>&lt;html></i> code.</p><br />
<p>If you want to use a CSS stylesheet or Javascript on multiple pages, you can create a <b>wiki template page</b>.</p><br />
<br />
<h4>Using Wiki Templates</h4><br />
<p>If there is standard text/code that you want to add to more than one page, like a CSS style or script, then you can use <a href="http://www.mediawiki.org/wiki/Help:Templates">MediaWiki templates</a></p><br />
<p>You can create a <b>wiki template page</b> to house your HTML/CSS/Javascript, by entering <i>{{Team:YourTeamName/CSS}}</i> into your wiki markup. Saving the page will create a link for a new template page, which you can edit and enter all of your CSS code. You can then call <i>{{Team:YourTeamName/CSS}}</i> on other pages.</p><br />
<p>Take a look at a few 2013 team wikis to see how other teams setup the styling. You can do this by going to a wiki, and looking for <i>view source</i> in the default wiki links at the top of the page. See <a href="https://2013.igem.org/Template:MIT-style">MIT's</a> and <a href="https://2013.igem.org/Team:TU-Munich">TU-Munich's</a> for examples.</p><br />
<br />
<br /><br /><br />
</html><br />
<br />
===Perspectives from an iGEM veteran===<br />
<html><br />
<table cellspacing="10" style="text-align: justify;" width="965px"><br />
<br />
<tr> <br />
<br />
<td width="48%"><br />
Hello iGEMers!<br />
<br><br />
I was also part of an iGEM team!<br />
<br><br />
In 2011 and 2012 my role was to design and create our team’s wiki. So wiki freeze was my major deadline. I am by no means an expert but let me share with you some of the things I learned with two wiki freezes under my belt.<br />
<br><br><br />
<b> 1.- Test your webpage layout: is information easy to find?</b> </br><br />
<p> I made the terrible mistake of not asking for a third party’s opinion about the layout of information on our site. It was obvious for me how things were laid out and organized. It wasn’t for the people evaluating us. <br><br />
Also, stick to the 3 click rule: content must reachable within 3 clicks so the user does not feel lost or confused. If someone wants to read your abstract, their path should be something like this (Menu –> Project –> Project Description -> Abstract)</p><br />
<br><br />
<b> 2.- Look at other teams’ code, see how they documented and what resources they used. </b><br><br />
<p> It is always good to get inspiration from other iGEM teams. See what you liked that they did and strive to improve! </p><br />
<br><br />
<b> 3.- Start working on your documentation early on. </b> <br><br />
<p>This was a good thing that we did; we created a common file that more than one person can edit at a time. Divide the documentation into smaller files and assign a team member to fully document that topic. In the end you will have a printable version of your project that you can share as a pdf file with other people!</p><br />
<br><br />
<br />
</td><br />
<br />
<td width="4%"></td><br />
<br />
<td width="48%" valign="top"><br />
<b> 4.- Name your images according to the project and keep them all in a folder on your computer. </b> <br><br />
<p> Sometimes naming your gel image “gelthingy_whyiamworkingat3am” sounds perfect at 3AM but later it may not be easy to know what or when that photograph was taken or that image created. <br><br />
Also, the iGEM database doesn’t know that you created that file so if someone names their file with the same name it can end up being replaced! Avoid using generic names like “banner.png” or “logo.jpg”.<br><br />
Try using your team’s name and the webpage where the image will appear, this helps you remember where to place it and reduce the risk of another team overwriting. “JoyUniversity_TeamBios_Richard.jpg” </p><br />
<br><br />
<b> 5.- Do not leave everything to the last minute! </b><br />
<br />
<p> Plan ahead. The last thing you want to be doing at 11:30PM the night of wiki freeze is uploading images. It is very stressful to be looking at the clock and hoping some kind of coding miracle helps you fix bugs faster. Plan to have everything online at least one week ahead so you can go enjoy a nice dinner with your team that night! </p></div>Vinoohttp://2014.igem.org/Wiki_How-ToWiki How-To2014-10-16T22:18:52Z<p>Vinoo: Reverted edits by Feixia (talk) to last revision by Mbrewer</p>
<hr />
<div>{{CSS/Main}}<br />
{{NavBar}}<br />
<html><br />
<div id="contentcontainer"><br />
<br />
</html><br />
{{TOCright}}<br />
===Wiki Freeze - October 17th (11:59 PM -EDT)===<br />
<html><br />
<br />
<p><b><span style="color:red;">Warning: Do not wait till the last minute! There will be a lot of traffic on the iGEM wiki starting as early as Wednesday (October 15th). Upload your content early and avoid issues caused by server load.</span></b></p><br />
<br />
<p>Your team's project must be documented on the iGEM 2014 wiki, the parts used in your project must be documented on the <a href="http://parts.igem.org">Registry of Standard Biological Parts</a>. You have the freedom to be creative, but a few specific rules apply:</p><br />
<br />
<br />
<br /><br />
<br /><br />
<br />
<br />
jkj;lkjlkj;lkjlkjkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkk<br />
<br />
<br />
<style type="text/css"><br />
.simpleTable {<br />
cellspacing: 0;<br />
}<br />
.simpleTable th, .simpleTable td {<br />
padding: 10px 15px;<br />
}<br />
.simpleTable th {<br />
color: #fff;<br />
background-color: #333;<br />
font-style: italic;<br />
font-size: 14pt;<br />
}<br />
.simpleTable tr:nth-child(even) {<br />
background-color: #f0f0f0;<br />
}<br />
</style><br />
</html><br />
<br />
===Wiki Dos and Don'ts===<br />
<html><br />
<table class="simpleTable"><br />
<tr><br />
<th width="250px">Do</th><br />
<th width="250px">Don't</th><br />
<th width="460px">Why?</th><br />
</tr><br />
<tr><br />
<td>Make sure all wiki content, from code and scripts, to files, is hosted on <b>2014.igem.org</b></td><br />
<td>Don't host your wiki or parts of your wiki elsewhere</td><br />
<td>iGEM content is preserved on our servers so future teams can learn from what you've done. When content is stored on other sites/servers, links may become broken (<a href="https://static.igem.org/mediawiki/2014/d/d6/Wiki_server_example1.jpg" title="images were stored off-site, and became broken" target="_blank">example</a>), sites may go down, and <b>information will be lost.</b></td><br />
</tr><br />
<tr><br />
<td>Work on your wiki throughout the year and <b>save small edits for last</b></td><br />
<td>Don't wait to add/edit large portions of wiki content the day of the <b>Wiki Freeze</b></td><br />
<td>Just before the Wiki Freeze, iGEM websites experience <b>increased traffic and server loads.</b> This can be a difficult time to make larger changes or additions to your wiki. Don't wait till the last minute!</td><br />
</tr><br />
<tr><br />
<td>Name uploaded files clearly and uniquely (TeamName_Header.png)</td><br />
<td>Don't use generic names for you files (Header.png)</td><br />
<td>Using <b>unique names</b> makes searching/identification of uploaded files easier, and helps prevent files from being overwritten.</td><br />
</tr><br />
<tr><br />
<td>Load your CSS and Javascript into the wiki, either directly into your page or using templates (<a href="https://2014.igem.org/wiki/index.php?title=Wiki_How-To&action=submit#Wiki_Editing">see below</a>)</td><br />
<td>Don't try to host your CSS and Javascript on a third party server</td><br />
<td>You are required to host all content on the iGEM servers (<a href="https://2014.igem.org/wiki/index.php?title=Wiki_How-To&action=submit#Wiki_Requirements">see below</a>)</td><br />
</tr><br />
</table><br />
<br /><br /><br />
<br />
</html><br />
<br />
===Wiki Requirements===<br />
<html><br />
<h4>iGEM Logo</h4><br />
<p>All iGEM Team Wikis must include the iGEM logo at the top of the page and a visible link back to the iGEM 2014 Wiki Main Page in the header (or at the top of the page). All wiki pages must preserve the user editing menu (notifications, username, messages, history, edit). In the case where the user heading is not visible, an automatic heading will be overlaid on top of the wiki page(s) where the heading is missing. </p><br />
<h4>The iGEM Login Bar</h4><br />
<p>The iGEM Login Bar is a 20 pixel high, full-width menu bar that exists on all 2014.igem.org pages. It contains:<br />
<ul><br />
<li>wiki tools (edit, history, watch, etc.)</li><br />
<li>login</li><br />
</ul><br />
All iGEM 2014 Team Wikis are required to have the Login Bar. All wiki pages must preserve the user editing menu (notifications, username, messages, history, edit). Please keep this in mind as you design your wiki.</p><br />
<h4>No Adobe Flash</h4> <br />
<p>Flash is not permitted on the iGEM 2014 wiki. Adobe flash is 100% proprietary and you cannot view the source like you can with our wiki. We chose wikis for teams to build their projects so the source code would be available for future teams, to build on the concept of open source. Flash can also be hosted on external sites and we want 100% of the content of our wikis to be on our wikis. </p> <br />
<h4>Upload to 2014.igem.org server</h4><br />
<p>All team pages, images, documents and <b>code</b> must be hosted on the <b>2014.igem.org</b> server. We preserve all iGEM content on our own servers so future teams can learn from what you have done. When you store content on your own sites or servers, after time, links might become broken, sites might go down, and information will be lost. <br /><br />
Additionally, hosting content outside of 2014.iGEM.org allows teams to change/add information to their wiki after the wiki freeze. Please note, that altering content after the wiki freeze is a <a href="https://2014.igem.org/Responsible_Conduct">form of cheating</a>. <br /><br />
Load your CSS and Javascript into the wiki, either directly into your page or using templates (<a href="https://2014.igem.org/wiki/index.php?title=Wiki_How-To&action=submit#Wiki_Editing">see below</a>)<br />
</p><br />
<h4>No iframes</h4> <br />
<p><b>iframes</b> are not permitted on the iGEM wiki. If an iframe was used to access content outside of <b>2014.igem.org</b>...<br />
<ul><br />
<li>it would break when there was an issue with the outside server</li> <br />
<li>it would allow a team to show change/add content after the wiki freeze. Please note, that altering content after the wiki freeze is a <a href="https://2014.igem.org/Responsible_Conduct">form of cheating</a></li> <br />
</ul><br />
</p><br />
<h4>2014.igem.org/Team:Team_Name</h4><br />
<p>All iGEM 2014 teams are given a namespace on the iGEM 2014 wiki with their team name. Teams are allowed to create and edit pages within their respective team namespace. Teams are <b>not allowed</b> to create or edit pages belonging to another team's namespace.</p><br />
<h4>Wiki Freeze - October 17th</h4><br />
<p>The wiki freeze for the 2014 Giant Jamboree is on <a href="https://2014.igem.org/Calendar_of_Events">October 17th,</a> along with other deadlines. iGEM experiences higher than normal traffic on this day which can lead to strain on our servers and sessions timing out for users. iGEM HQ recommends that users do not wait till the last day to work/finish their wikis. <b>Once the wikis are frozen, users can no longer make any changes until they are unfrozen after the Jamboree.</b></p><br />
<h4>Other deadlines</h4><br />
<p>The team's project description must be documented on their iGEM Team Wiki by the deadline. The project description should be 1-3 paragraphs and only needs to include an up-to-date explanation of the project.</p><br />
<p>The team's wiki must include an attributions section.</p><br />
<h4>Creative Commons</h4><br />
<p>All content on this wiki is available under the Creative Commons <a href="http://creativecommons.org/licenses/by/4.0/">Attribution 4.0</a> license (or any later version).<br />
<img src="http://i.creativecommons.org/l/by/3.0/88x31.png"></p><br />
<br /><br /><br />
<br />
</html><br />
<br />
===Wiki Editing===<br />
<html><br />
<h4>Add a wiki page, change a wiki page, delete a wiki page, etc.</h4><br />
<p>All iGEM wiki sites are powered by Mediawiki. See the <a href="http://www.mediawiki.org/wiki/Help:Contents">Mediawiki Help page</a> for details on how to edit wiki pages and more.</p><br />
<p>Using/editing the wiki is a trial-and-error process. Editing the wiki is a simple, fun thing to do and you definitely get better the more you play around with it. The key is to take a look at other wiki pages and see what you like. Then all you have to do is go to the source (either view source if you're not logged in, or edit if you are logged in), copy it, and modify it to fit your needs. It doesn't have to be perfect before you can take a look at what it looks like. Try things out and see what results they yield.</p><br />
<br />
<h4>Adding a page to your team's namespace?</h4><br />
<p>You must keep your team's pages in your team namespace. For example, take a look at <a href="https://2014.igem.org/Team:Example">2014.igem.org/Team:Example</a></p> <br />
<p>Specifically, when you create a new page, you just have to name it <b>Team</b>:<a href="https://igem.org/Team_List">OFFICIAL team name</a>/PageName. For example, if you were on Team Example and wanted to create a Biosensor project page you would name it <b>Team:Example/Biosensor_project</b>.</p><br />
<br />
<h4>Using html in wiki pages</h4><br />
<p>Instead of using wiki markup, you can use <b>html</b> in the wiki editor. Just put your html code in between <i>&lt;html>&lt;/html></i></p><br />
<br />
<h4>Using CSS and/or Javascript</h4><br />
<p>You can also use <b>CSS</b> and <b>Javascript</b> on the wiki by adding your <i>&lt;style></i> and <i>&lt;script></i> tags into your <i>&lt;html></i> code.</p><br />
<p>If you want to use a CSS stylesheet or Javascript on multiple pages, you can create a <b>wiki template page</b>.</p><br />
<br />
<h4>Using Wiki Templates</h4><br />
<p>If there is standard text/code that you want to add to more than one page, like a CSS style or script, then you can use <a href="http://www.mediawiki.org/wiki/Help:Templates">MediaWiki templates</a></p><br />
<p>You can create a <b>wiki template page</b> to house your HTML/CSS/Javascript, by entering <i>{{Team:YourTeamName/CSS}}</i> into your wiki markup. Saving the page will create a link for a new template page, which you can edit and enter all of your CSS code. You can then call <i>{{Team:YourTeamName/CSS}}</i> on other pages.</p><br />
<p>Take a look at a few 2013 team wikis to see how other teams setup the styling. You can do this by going to a wiki, and looking for <i>view source</i> in the default wiki links at the top of the page. See <a href="https://2013.igem.org/Template:MIT-style">MIT's</a> and <a href="https://2013.igem.org/Team:TU-Munich">TU-Munich's</a> for examples.</p><br />
<br />
<br /><br /><br />
</html><br />
<br />
===Perspectives from an iGEM veteran===<br />
<html><br />
<table cellspacing="10" style="text-align: justify;" width="965px"><br />
<br />
<tr> <br />
<br />
<td width="48%"><br />
Hello iGEMers!<br />
<br><br />
I was also part of an iGEM team!<br />
<br><br />
In 2011 and 2012 my role was to design and create our team’s wiki. So wiki freeze was my major deadline. I am by no means an expert but let me share with you some of the things I learned with two wiki freezes under my belt.<br />
<br><br><br />
<b> 1.- Test your webpage layout: is information easy to find?</b> </br><br />
<p> I made the terrible mistake of not asking for a third party’s opinion about the layout of information on our site. It was obvious for me how things were laid out and organized. It wasn’t for the people evaluating us. <br><br />
Also, stick to the 3 click rule: content must reachable within 3 clicks so the user does not feel lost or confused. If someone wants to read your abstract, their path should be something like this (Menu –> Project –> Project Description -> Abstract)</p><br />
<br><br />
<b> 2.- Look at other teams’ code, see how they documented and what resources they used. </b><br><br />
<p> It is always good to get inspiration from other iGEM teams. See what you liked that they did and strive to improve! </p><br />
<br><br />
<b> 3.- Start working on your documentation early on. </b> <br><br />
<p>This was a good thing that we did; we created a common file that more than one person can edit at a time. Divide the documentation into smaller files and assign a team member to fully document that topic. In the end you will have a printable version of your project that you can share as a pdf file with other people!</p><br />
<br><br />
<br />
</td><br />
<br />
<td width="4%"></td><br />
<br />
<td width="48%" valign="top"><br />
<b> 4.- Name your images according to the project and keep them all in a folder on your computer. </b> <br><br />
<p> Sometimes naming your gel image “gelthingy_whyiamworkingat3am” sounds perfect at 3AM but later it may not be easy to know what or when that photograph was taken or that image created. <br><br />
Also, the iGEM database doesn’t know that you created that file so if someone names their file with the same name it can end up being replaced! Avoid using generic names like “banner.png” or “logo.jpg”.<br><br />
Try using your team’s name and the webpage where the image will appear, this helps you remember where to place it and reduce the risk of another team overwriting. “JoyUniversity_TeamBios_Richard.jpg” </p><br />
<br><br />
<b> 5.- Do not leave everything to the last minute! </b><br />
<br />
<p> Plan ahead. The last thing you want to be doing at 11:30PM the night of wiki freeze is uploading images. It is very stressful to be looking at the clock and hoping some kind of coding miracle helps you fix bugs faster. Plan to have everything online at least one week ahead so you can go enjoy a nice dinner with your team that night! </p></div>Vinoohttp://2014.igem.org/Wiki_How-ToWiki How-To2014-10-10T17:11:16Z<p>Vinoo: </p>
<hr />
<div>{{CSS/Main}}<br />
{{NavBar}}<br />
<html><br />
<div id="contentcontainer"><br />
<br />
</html><br />
{{TOCright}}<br />
===Wiki Freeze - October 17th (11:59 PM -EDT)===<br />
<html><br />
<br />
<p><b><span style="color:red;">Warning: Do not wait till the last minute! There will be a lot of traffic on the iGEM wiki starting as early as Wednesday (October 15th). Upload your content early and avoid issues caused by server load.</span></b></p><br />
<br />
<p>Your team's project must be documented on the iGEM 2014 wiki, the parts used in your project must be documented on the <a href="http://parts.igem.org">Registry of Standard Biological Parts</a>. You have the freedom to be creative, but a few specific rules apply:</p><br />
<br />
<br />
<br /><br />
<br /><br />
<br />
<br />
<style type="text/css"><br />
.simpleTable {<br />
cellspacing: 0;<br />
}<br />
.simpleTable th, .simpleTable td {<br />
padding: 10px 15px;<br />
}<br />
.simpleTable th {<br />
color: #fff;<br />
background-color: #333;<br />
font-style: italic;<br />
font-size: 14pt;<br />
}<br />
.simpleTable tr:nth-child(even) {<br />
background-color: #f0f0f0;<br />
}<br />
</style><br />
</html><br />
<br />
===Wiki Dos and Don'ts===<br />
<html><br />
<table class="simpleTable"><br />
<tr><br />
<th width="250px">Do</th><br />
<th width="250px">Don't</th><br />
<th width="460px">Why?</th><br />
</tr><br />
<tr><br />
<td>Make sure all wiki content, from code and scripts, to files, is hosted on <b>2014.igem.org</b></td><br />
<td>Don't host your wiki or parts of your wiki elsewhere</td><br />
<td>iGEM content is preserved on our servers so future teams can learn from what you've done. When content is stored on other sites/servers, links may become broken (<a href="https://static.igem.org/mediawiki/2014/d/d6/Wiki_server_example1.jpg" title="images were stored off-site, and became broken" target="_blank">example</a>), sites may go down, and <b>information will be lost.</b></td><br />
</tr><br />
<tr><br />
<td>Work on your wiki throughout the year and <b>save small edits for last</b></td><br />
<td>Don't wait to add/edit large portions of wiki content the day of the <b>Wiki Freeze</b></td><br />
<td>Just before the Wiki Freeze, iGEM websites experience <b>increased traffic and server loads.</b> This can be a difficult time to make larger changes or additions to your wiki. Don't wait till the last minute!</td><br />
</tr><br />
<tr><br />
<td>Name uploaded files clearly and uniquely (TeamName_Header.png)</td><br />
<td>Don't use generic names for you files (Header.png)</td><br />
<td>Using <b>unique names</b> makes searching/identification of uploaded files easier, and helps prevent files from being overwritten.</td><br />
</tr><br />
<tr><br />
<td>Load your CSS and Javascript into the wiki, either directly into your page or using templates (<a href="https://2014.igem.org/wiki/index.php?title=Wiki_How-To&action=submit#Wiki_Editing">see below</a>)</td><br />
<td>Don't try to host your CSS and Javascript on a third party server</td><br />
<td>You are required to host all content on the iGEM servers (<a href="https://2014.igem.org/wiki/index.php?title=Wiki_How-To&action=submit#Wiki_Requirements">see below</a>)</td><br />
</tr><br />
</table><br />
<br /><br /><br />
<br />
</html><br />
<br />
===Wiki Requirements===<br />
<html><br />
<h4>iGEM Logo</h4><br />
<p>All iGEM Team Wikis must include the iGEM logo at the top of the page and a visible link back to the iGEM 2014 Wiki Main Page in the header (or at the top of the page). All wiki pages must preserve the user editing menu (notifications, username, messages, history, edit). In the case where the user heading is not visible, an automatic heading will be overlaid on top of the wiki page(s) where the heading is missing. </p><br />
<h4>The iGEM Login Bar</h4><br />
<p>The iGEM Login Bar is a 20 pixel high, full-width menu bar that exists on all 2014.igem.org pages. It contains:<br />
<ul><br />
<li>wiki tools (edit, history, watch, etc.)</li><br />
<li>login</li><br />
</ul><br />
All iGEM 2014 Team Wikis are required to have the Login Bar. All wiki pages must preserve the user editing menu (notifications, username, messages, history, edit). Please keep this in mind as you design your wiki.</p><br />
<h4>No Adobe Flash</h4> <br />
<p>Flash is not permitted on the iGEM 2014 wiki. Adobe flash is 100% proprietary and you cannot view the source like you can with our wiki. We chose wikis for teams to build their projects so the source code would be available for future teams, to build on the concept of open source. Flash can also be hosted on external sites and we want 100% of the content of our wikis to be on our wikis. </p> <br />
<h4>Upload to 2014.igem.org server</h4><br />
<p>All team pages, images, documents and <b>code</b> must be hosted on the <b>2014.igem.org</b> server. We preserve all iGEM content on our own servers so future teams can learn from what you have done. When you store content on your own sites or servers, after time, links might become broken, sites might go down, and information will be lost. <br /><br />
Additionally, hosting content outside of 2014.iGEM.org allows teams to change/add information to their wiki after the wiki freeze. Please note, that altering content after the wiki freeze is a <a href="https://2014.igem.org/Responsible_Conduct">form of cheating</a>. <br /><br />
Load your CSS and Javascript into the wiki, either directly into your page or using templates (<a href="https://2014.igem.org/wiki/index.php?title=Wiki_How-To&action=submit#Wiki_Editing">see below</a>)<br />
</p><br />
<h4>No iframes</h4> <br />
<p><b>iframes</b> are not permitted on the iGEM wiki. If an iframe was used to access content outside of <b>2014.igem.org</b>...<br />
<ul><br />
<li>it would break when there was an issue with the outside server</li> <br />
<li>it would allow a team to show change/add content after the wiki freeze. Please note, that altering content after the wiki freeze is a <a href="https://2014.igem.org/Responsible_Conduct">form of cheating</a></li> <br />
</ul><br />
</p><br />
<h4>2014.igem.org/Team:Team_Name</h4><br />
<p>All iGEM 2014 teams are given a namespace on the iGEM 2014 wiki with their team name. Teams are allowed to create and edit pages within their respective team namespace. Teams are <b>not allowed</b> to create or edit pages belonging to another team's namespace.</p><br />
<h4>Wiki Freeze - October 17th</h4><br />
<p>The wiki freeze for the 2014 Giant Jamboree is on <a href="https://2014.igem.org/Calendar_of_Events">October 17th,</a> along with other deadlines. iGEM experiences higher than normal traffic on this day which can lead to strain on our servers and sessions timing out for users. iGEM HQ recommends that users do not wait till the last day to work/finish their wikis. <b>Once the wikis are frozen, users can no longer make any changes until they are unfrozen after the Jamboree.</b></p><br />
<h4>Other deadlines</h4><br />
<p>The team's project description must be documented on their iGEM Team Wiki by the deadline. The project description should be 1-3 paragraphs and only needs to include an up-to-date explanation of the project.</p><br />
<p>The team's wiki must include an attributions section.</p><br />
<h4>Creative Commons</h4><br />
<p>All content on this wiki is available under the Creative Commons <a href="http://creativecommons.org/licenses/by/4.0/">Attribution 4.0</a> license (or any later version).<br />
<img src="http://i.creativecommons.org/l/by/3.0/88x31.png"></p><br />
<br /><br /><br />
<br />
</html><br />
<br />
===Wiki Editing===<br />
<html><br />
<h4>Add a wiki page, change a wiki page, delete a wiki page, etc.</h4><br />
<p>All iGEM wiki sites are powered by Mediawiki. See the <a href="http://www.mediawiki.org/wiki/Help:Contents">Mediawiki Help page</a> for details on how to edit wiki pages and more.</p><br />
<p>Using/editing the wiki is a trial-and-error process. Editing the wiki is a simple, fun thing to do and you definitely get better the more you play around with it. The key is to take a look at other wiki pages and see what you like. Then all you have to do is go to the source (either view source if you're not logged in, or edit if you are logged in), copy it, and modify it to fit your needs. It doesn't have to be perfect before you can take a look at what it looks like. Try things out and see what results they yield.</p><br />
<br />
<h4>Adding a page to your team's namespace?</h4><br />
<p>You must keep your team's pages in your team namespace. For example, take a look at <a href="https://2014.igem.org/Team:Example">2014.igem.org/Team:Example</a></p> <br />
<p>Specifically, when you create a new page, you just have to name it <b>Team</b>:<a href="https://igem.org/Team_List">OFFICIAL team name</a>/PageName. For example, if you were on Team Example and wanted to create a Biosensor project page you would name it <b>Team:Example/Biosensor_project</b>.</p><br />
<br />
<h4>Using html in wiki pages</h4><br />
<p>Instead of using wiki markup, you can use <b>html</b> in the wiki editor. Just put your html code in between <i>&lt;html>&lt;/html></i></p><br />
<br />
<h4>Using CSS and/or Javascript</h4><br />
<p>You can also use <b>CSS</b> and <b>Javascript</b> on the wiki by adding your <i>&lt;style></i> and <i>&lt;script></i> tags into your <i>&lt;html></i> code.</p><br />
<p>If you want to use a CSS stylesheet or Javascript on multiple pages, you can create a <b>wiki template page</b>.</p><br />
<br />
<h4>Using Wiki Templates</h4><br />
<p>If there is standard text/code that you want to add to more than one page, like a CSS style or script, then you can use <a href="http://www.mediawiki.org/wiki/Help:Templates">MediaWiki templates</a></p><br />
<p>You can create a <b>wiki template page</b> to house your HTML/CSS/Javascript, by entering <i>{{Team:YourTeamName/CSS}}</i> into your wiki markup. Saving the page will create a link for a new template page, which you can edit and enter all of your CSS code. You can then call <i>{{Team:YourTeamName/CSS}}</i> on other pages.</p><br />
<p>Take a look at a few 2013 team wikis to see how other teams setup the styling. You can do this by going to a wiki, and looking for <i>view source</i> in the default wiki links at the top of the page. See <a href="https://2013.igem.org/Template:MIT-style">MIT's</a> and <a href="https://2013.igem.org/Team:TU-Munich">TU-Munich's</a> for examples.</p><br />
<br />
<br /><br /><br />
</html><br />
<br />
===Perspectives from an iGEM veteran===<br />
<html><br />
<table cellspacing="10" style="text-align: justify;" width="965px"><br />
<br />
<tr> <br />
<br />
<td width="48%"><br />
Hello iGEMers!<br />
<br><br />
I was also part of an iGEM team!<br />
<br><br />
In 2011 and 2012 my role was to design and create our team’s wiki. So wiki freeze was my major deadline. I am by no means an expert but let me share with you some of the things I learned with two wiki freezes under my belt.<br />
<br><br><br />
<b> 1.- Test your webpage layout: is information easy to find?</b> </br><br />
<p> I made the terrible mistake of not asking for a third party’s opinion about the layout of information on our site. It was obvious for me how things were laid out and organized. It wasn’t for the people evaluating us. <br><br />
Also, stick to the 3 click rule: content must reachable within 3 clicks so the user does not feel lost or confused. If someone wants to read your abstract, their path should be something like this (Menu –> Project –> Project Description -> Abstract)</p><br />
<br><br />
<b> 2.- Look at other teams’ code, see how they documented and what resources they used. </b><br><br />
<p> It is always good to get inspiration from other iGEM teams. See what you liked that they did and strive to improve! </p><br />
<br><br />
<b> 3.- Start working on your documentation early on. </b> <br><br />
<p>This was a good thing that we did; we created a common file that more than one person can edit at a time. Divide the documentation into smaller files and assign a team member to fully document that topic. In the end you will have a printable version of your project that you can share as a pdf file with other people!</p><br />
<br><br />
<br />
</td><br />
<br />
<td width="4%"></td><br />
<br />
<td width="48%" valign="top"><br />
<b> 4.- Name your images according to the project and keep them all in a folder on your computer. </b> <br><br />
<p> Sometimes naming your gel image “gelthingy_whyiamworkingat3am” sounds perfect at 3AM but later it may not be easy to know what or when that photograph was taken or that image created. <br><br />
Also, the iGEM database doesn’t know that you created that file so if someone names their file with the same name it can end up being replaced! Avoid using generic names like “banner.png” or “logo.jpg”.<br><br />
Try using your team’s name and the webpage where the image will appear, this helps you remember where to place it and reduce the risk of another team overwriting. “JoyUniversity_TeamBios_Richard.jpg” </p><br />
<br><br />
<b> 5.- Do not leave everything to the last minute! </b><br />
<br />
<p> Plan ahead. The last thing you want to be doing at 11:30PM the night of wiki freeze is uploading images. It is very stressful to be looking at the clock and hoping some kind of coding miracle helps you fix bugs faster. Plan to have everything online at least one week ahead so you can go enjoy a nice dinner with your team that night! </p><br />
<br />
<br />
<p> I hope this helps and if you have any questions, feel free to email me or send me a tweet! </p><br />
<i> ana at igem dot org </i><br />
<br><br />
<i> <A HREF="https://twitter.com/anita_sifuentes" > @anita_sifuentes </A> </i><br />
<br />
</td><br />
</tr><br />
</table><br />
<br /><br />
<br />
</html><br />
<br />
===Wiki Templates===<br />
<html><br />
<p> This year we have created a set of template pages that you may for your wiki! <BR> Feel free to edit them as much as you want </p><br />
<a href="https://2014.igem.org/WikitemplateA_home ">Wiki Template A </a></br><br />
<a href="https://2014.igem.org/WikitemplateB_home ">Wiki Template B </a><br />
<BR><BR><br />
<br />
</div><br />
</html><br />
{{MainPage2014/Footer}}</div>Vinoohttp://2014.igem.org/Wiki_How-ToWiki How-To2014-10-10T17:08:56Z<p>Vinoo: </p>
<hr />
<div>{{CSS/Main}}<br />
{{NavBar}}<br />
<html><br />
<div id="contentcontainer"><br />
<br />
</html><br />
{{TOCright}}<br />
===Wiki Freeze - October 17th (11:59 PM -EDT)===<br />
<html><br />
<br />
<p><b><span style="color:red;">Warning: Do not wait till the last minute! There will be a lot of traffic on the iGEM wiki starting as early as Wednesday (October 15th). Upload your content early and avoid issues caused by server load.</span></b></p><br />
<br />
<p>Your team's project must be documented on the iGEM 2014 wiki, the parts used in your project must be documented on the <a href="http://parts.igem.org">Registry of Standard Biological Parts</a>. You have the freedom to be creative, but a few specific rules apply:</p><br />
<br />
<br />
<br /><br />
<br /><br />
<br />
<br />
<style type="text/css"><br />
.simpleTable {<br />
cellspacing: 0;<br />
}<br />
.simpleTable th, .simpleTable td {<br />
padding: 10px 15px;<br />
}<br />
.simpleTable th {<br />
color: #fff;<br />
background-color: #333;<br />
font-style: italic;<br />
font-size: 14pt;<br />
}<br />
.simpleTable tr:nth-child(even) {<br />
background-color: #f0f0f0;<br />
}<br />
</style><br />
</html><br />
<br />
===Wiki Dos and Don'ts===<br />
<html><br />
<table class="simpleTable"><br />
<tr><br />
<th width="250px">Do</th><br />
<th width="250px">Don't</th><br />
<th width="460px">Why?</th><br />
</tr><br />
<tr><br />
<td>Make sure all wiki content, from code and scripts, to files, is hosted on <b>2014.igem.org</b></td><br />
<td>Don't host your wiki or parts of your wiki elsewhere</td><br />
<td>iGEM content is preserved on our servers so future teams can learn from what you've done. When content is stored on other sites/servers, links may become broken (<a href="https://static.igem.org/mediawiki/2014/d/d6/Wiki_server_example1.jpg" title="images were stored off-site, and became broken" target="_blank">example</a>), sites may go down, and <b>information will be lost.</b></td><br />
</tr><br />
<tr><br />
<td>Work on your wiki throughout the year and <b>save small edits for last</b></td><br />
<td>Don't wait to add/edit large portions of wiki content the day of the <b>Wiki Freeze</b></td><br />
<td>Just before the Wiki Freeze, iGEM websites experience <b>increased traffic and server loads.</b> This can be a difficult time to make larger changes or additions to your wiki. Don't wait till the last minute!</td><br />
</tr><br />
<tr><br />
<td>Name uploaded files clearly and uniquely (TeamName_Header.png)</td><br />
<td>Don't use generic names for you files (Header.png)</td><br />
<td>Using <b>unique names</b> makes searching/identification of uploaded files easier, and helps prevent files from being overwritten.</td><br />
</tr><br />
<tr><br />
<td>Load your CSS and Javascript into the wiki, either directly into your page or using templates (<a href="https://2014.igem.org/wiki/index.php?title=Wiki_How-To&action=submit#Wiki_Editing">see below</a>)</td><br />
<td>Don't try to host your CSS and Javascript on a third party server</td><br />
<td>You are required to host all content on the iGEM servers (<a href="https://2014.igem.org/wiki/index.php?title=Wiki_How-To&action=submit#Wiki_Requirements">see below</a>)</td><br />
</tr><br />
</table><br />
<br /><br /><br />
<br />
</html><br />
<br />
===Wiki Requirements===<br />
<html><br />
<h4>iGEM Logo</h4><br />
<p>All iGEM Team Wikis must include the iGEM logo at the top of the page and a visible link back to the iGEM 2014 Wiki Main Page in the header (or at the top of the page). All wiki pages must preserve the user editing menu (notifications, username, messages, history, edit). In the case where the user heading is not visible, an automatic heading will be overlaid on top of the wiki page(s) where the heading is missing. </p><br />
<h4>The iGEM Login Bar</h4><br />
<p>The iGEM Login Bar is a 20 pixel high, full-width menu bar that exists on all 2014.igem.org pages. It contains:<br />
<ul><br />
<li>wiki tools (edit, history, watch, etc.)</li><br />
<li>login</li><br />
</ul><br />
All iGEM 2014 Team Wikis are required to have the Login Bar. All wiki pages must preserve the user editing menu (notifications, username, messages, history, edit). Please keep this in mind as you design your wiki.</p><br />
<h4>No Adobe Flash</h4> <br />
<p>Flash is not permitted on the iGEM 2014 wiki. Adobe flash is 100% proprietary and you cannot view the source like you can with our wiki. We chose wikis for teams to build their projects so the source code would be available for future teams, to build on the concept of open source. Flash can also be hosted on external sites and we want 100% of the content of our wikis to be on our wikis. </p> <br />
<h4>Upload to 2014.igem.org server</h4><br />
<p>All team pages, images, documents and <b>code</b> must be hosted on the <b>2014.igem.org</b> server. We preserve all iGEM content on our own servers so future teams can learn from what you have done. When you store content on your own sites or servers, after time, links might become broken, sites might go down, and information will be lost. <br /><br />
Additionally, hosting content outside of 2014.iGEM.org allows teams to change/add information to their wiki after the wiki freeze. Please note, that altering content after the wiki freeze is a <a href="https://2014.igem.org/Responsible_Conduct">form of cheating</a>. <br /><br />
Additionally, hosting content outside of 2014.iGEM.org allows teams to change/add information to their wiki after the wiki freeze. Please note, that altering content after the wiki freeze is a <a href="https://2014.igem.org/Responsible_Conduct">form of cheating</a>.<br />
</p><br />
<h4>No iframes</h4> <br />
<p><b>iframes</b> are not permitted on the iGEM wiki. If an iframe was used to access content outside of <b>2014.igem.org</b>...<br />
<ul><br />
<li>it would break when there was an issue with the outside server</li> <br />
<li>it would allow a team to show change/add content after the wiki freeze. Please note, that altering content after the wiki freeze is a <a href="https://2014.igem.org/Responsible_Conduct">form of cheating</a></li> <br />
</ul><br />
</p><br />
<h4>2014.igem.org/Team:Team_Name</h4><br />
<p>All iGEM 2014 teams are given a namespace on the iGEM 2014 wiki with their team name. Teams are allowed to create and edit pages within their respective team namespace. Teams are <b>not allowed</b> to create or edit pages belonging to another team's namespace.</p><br />
<h4>Wiki Freeze - October 17th</h4><br />
<p>The wiki freeze for the 2014 Giant Jamboree is on <a href="https://2014.igem.org/Calendar_of_Events">October 17th,</a> along with other deadlines. iGEM experiences higher than normal traffic on this day which can lead to strain on our servers and sessions timing out for users. iGEM HQ recommends that users do not wait till the last day to work/finish their wikis. <b>Once the wikis are frozen, users can no longer make any changes until they are unfrozen after the Jamboree.</b></p><br />
<h4>Other deadlines</h4><br />
<p>The team's project description must be documented on their iGEM Team Wiki by the deadline. The project description should be 1-3 paragraphs and only needs to include an up-to-date explanation of the project.</p><br />
<p>The team's wiki must include an attributions section.</p><br />
<h4>Creative Commons</h4><br />
<p>All content on this wiki is available under the Creative Commons <a href="http://creativecommons.org/licenses/by/4.0/">Attribution 4.0</a> license (or any later version).<br />
<img src="http://i.creativecommons.org/l/by/3.0/88x31.png"></p><br />
<br /><br /><br />
<br />
</html><br />
<br />
===Wiki Editing===<br />
<html><br />
<h4>Add a wiki page, change a wiki page, delete a wiki page, etc.</h4><br />
<p>All iGEM wiki sites are powered by Mediawiki. See the <a href="http://www.mediawiki.org/wiki/Help:Contents">Mediawiki Help page</a> for details on how to edit wiki pages and more.</p><br />
<p>Using/editing the wiki is a trial-and-error process. Editing the wiki is a simple, fun thing to do and you definitely get better the more you play around with it. The key is to take a look at other wiki pages and see what you like. Then all you have to do is go to the source (either view source if you're not logged in, or edit if you are logged in), copy it, and modify it to fit your needs. It doesn't have to be perfect before you can take a look at what it looks like. Try things out and see what results they yield.</p><br />
<br />
<h4>Adding a page to your team's namespace?</h4><br />
<p>You must keep your team's pages in your team namespace. For example, take a look at <a href="https://2014.igem.org/Team:Example">2014.igem.org/Team:Example</a></p> <br />
<p>Specifically, when you create a new page, you just have to name it <b>Team</b>:<a href="https://igem.org/Team_List">OFFICIAL team name</a>/PageName. For example, if you were on Team Example and wanted to create a Biosensor project page you would name it <b>Team:Example/Biosensor_project</b>.</p><br />
<br />
<h4>Using html in wiki pages</h4><br />
<p>Instead of using wiki markup, you can use <b>html</b> in the wiki editor. Just put your html code in between <i>&lt;html>&lt;/html></i></p><br />
<br />
<h4>Using CSS and/or Javascript</h4><br />
<p>You can also use <b>CSS</b> and <b>Javascript</b> on the wiki by adding your <i>&lt;style></i> and <i>&lt;script></i> tags into your <i>&lt;html></i> code.</p><br />
<p>If you want to use a CSS stylesheet or Javascript on multiple pages, you can create a <b>wiki template page</b>.</p><br />
<br />
<h4>Using Wiki Templates</h4><br />
<p>If there is standard text/code that you want to add to more than one page, like a CSS style or script, then you can use <a href="http://www.mediawiki.org/wiki/Help:Templates">MediaWiki templates</a></p><br />
<p>You can create a <b>wiki template page</b> to house your HTML/CSS/Javascript, by entering <i>{{Team:YourTeamName/CSS}}</i> into your wiki markup. Saving the page will create a link for a new template page, which you can edit and enter all of your CSS code. You can then call <i>{{Team:YourTeamName/CSS}}</i> on other pages.</p><br />
<p>Take a look at a few 2013 team wikis to see how other teams setup the styling. You can do this by going to a wiki, and looking for <i>view source</i> in the default wiki links at the top of the page. See <a href="https://2013.igem.org/Template:MIT-style">MIT's</a> and <a href="https://2013.igem.org/Team:TU-Munich">TU-Munich's</a> for examples.</p><br />
<br />
<br /><br /><br />
</html><br />
<br />
===Perspectives from an iGEM veteran===<br />
<html><br />
<table cellspacing="10" style="text-align: justify;" width="965px"><br />
<br />
<tr> <br />
<br />
<td width="48%"><br />
Hello iGEMers!<br />
<br><br />
I was also part of an iGEM team!<br />
<br><br />
In 2011 and 2012 my role was to design and create our team’s wiki. So wiki freeze was my major deadline. I am by no means an expert but let me share with you some of the things I learned with two wiki freezes under my belt.<br />
<br><br><br />
<b> 1.- Test your webpage layout: is information easy to find?</b> </br><br />
<p> I made the terrible mistake of not asking for a third party’s opinion about the layout of information on our site. It was obvious for me how things were laid out and organized. It wasn’t for the people evaluating us. <br><br />
Also, stick to the 3 click rule: content must reachable within 3 clicks so the user does not feel lost or confused. If someone wants to read your abstract, their path should be something like this (Menu –> Project –> Project Description -> Abstract)</p><br />
<br><br />
<b> 2.- Look at other teams’ code, see how they documented and what resources they used. </b><br><br />
<p> It is always good to get inspiration from other iGEM teams. See what you liked that they did and strive to improve! </p><br />
<br><br />
<b> 3.- Start working on your documentation early on. </b> <br><br />
<p>This was a good thing that we did; we created a common file that more than one person can edit at a time. Divide the documentation into smaller files and assign a team member to fully document that topic. In the end you will have a printable version of your project that you can share as a pdf file with other people!</p><br />
<br><br />
<br />
</td><br />
<br />
<td width="4%"></td><br />
<br />
<td width="48%" valign="top"><br />
<b> 4.- Name your images according to the project and keep them all in a folder on your computer. </b> <br><br />
<p> Sometimes naming your gel image “gelthingy_whyiamworkingat3am” sounds perfect at 3AM but later it may not be easy to know what or when that photograph was taken or that image created. <br><br />
Also, the iGEM database doesn’t know that you created that file so if someone names their file with the same name it can end up being replaced! Avoid using generic names like “banner.png” or “logo.jpg”.<br><br />
Try using your team’s name and the webpage where the image will appear, this helps you remember where to place it and reduce the risk of another team overwriting. “JoyUniversity_TeamBios_Richard.jpg” </p><br />
<br><br />
<b> 5.- Do not leave everything to the last minute! </b><br />
<br />
<p> Plan ahead. The last thing you want to be doing at 11:30PM the night of wiki freeze is uploading images. It is very stressful to be looking at the clock and hoping some kind of coding miracle helps you fix bugs faster. Plan to have everything online at least one week ahead so you can go enjoy a nice dinner with your team that night! </p><br />
<br />
<br />
<p> I hope this helps and if you have any questions, feel free to email me or send me a tweet! </p><br />
<i> ana at igem dot org </i><br />
<br><br />
<i> <A HREF="https://twitter.com/anita_sifuentes" > @anita_sifuentes </A> </i><br />
<br />
</td><br />
</tr><br />
</table><br />
<br /><br />
<br />
</html><br />
<br />
===Wiki Templates===<br />
<html><br />
<p> This year we have created a set of template pages that you may for your wiki! <BR> Feel free to edit them as much as you want </p><br />
<a href="https://2014.igem.org/WikitemplateA_home ">Wiki Template A </a></br><br />
<a href="https://2014.igem.org/WikitemplateB_home ">Wiki Template B </a><br />
<BR><BR><br />
<br />
</div><br />
</html><br />
{{MainPage2014/Footer}}</div>Vinoohttp://2014.igem.org/Requirements/WikiRequirements/Wiki2014-10-10T15:40:31Z<p>Vinoo: Redirected page to Wiki How-To#Wiki Requirements</p>
<hr />
<div>#redirect [[Wiki_How-To#Wiki_Requirements]]</div>Vinoohttp://2014.igem.org/Wiki_How-ToWiki How-To2014-10-10T15:39:19Z<p>Vinoo: </p>
<hr />
<div>{{CSS/Main}}<br />
{{NavBar}}<br />
<html><br />
<div id="contentcontainer"><br />
<br />
</html><br />
{{TOCright}}<br />
===Wiki Freeze - October 17th (11:59 PM -EDT)===<br />
<html><br />
<br />
<p>Your team's project must be documented on the iGEM 2014 wiki, the parts used in your project must be documented on the <a href="http://parts.igem.org">Registry of Standard Biological Parts</a>. You have the freedom to be creative, but a few specific rules apply:</p><br />
<br />
<br /><br />
<br /><br />
<br />
<br />
<style type="text/css"><br />
.simpleTable {<br />
cellspacing: 0;<br />
}<br />
.simpleTable th, .simpleTable td {<br />
padding: 10px 15px;<br />
}<br />
.simpleTable th {<br />
color: #fff;<br />
background-color: #333;<br />
font-style: italic;<br />
font-size: 14pt;<br />
}<br />
.simpleTable tr:nth-child(even) {<br />
background-color: #f0f0f0;<br />
}<br />
</style><br />
</html><br />
<br />
===Wiki Dos and Don'ts===<br />
<html><br />
<table class="simpleTable"><br />
<tr><br />
<th width="250px">Do</th><br />
<th width="250px">Don't</th><br />
<th width="460px">Why?</th><br />
</tr><br />
<tr><br />
<td>Make sure all wiki content, from code and scripts, to files, is hosted on <b>2014.igem.org</b></td><br />
<td>Don't host your wiki or parts of your wiki elsewhere</td><br />
<td>iGEM content is preserved on our servers so future teams can learn from what you've done. When content is stored on other sites/servers, links may become broken (<a href="https://static.igem.org/mediawiki/2014/d/d6/Wiki_server_example1.jpg" title="images were stored off-site, and became broken" target="_blank">example</a>), sites may go down, and <b>information will be lost.</b></td><br />
</tr><br />
<tr><br />
<td>Work on your wiki throughout the year and <b>save small edits for last</b></td><br />
<td>Don't wait to add/edit large portions of wiki content the day of the <b>Wiki Freeze</b></td><br />
<td>Just before the Wiki Freeze, iGEM websites experience <b>increased traffic and server loads.</b> This can be a difficult time to make larger changes or additions to your wiki. Don't wait till the last minute!</td><br />
</tr><br />
<tr><br />
<td>Name uploaded files clearly and uniquely (TeamName_Header.png)</td><br />
<td>Don't use generic names for you files (Header.png)</td><br />
<td>Using <b>unique names</b> makes searching/identification of uploaded files easier, and helps prevent files from being overwritten.</td><br />
</tr><br />
</table><br />
<br /><br /><br />
<br />
</html><br />
<br />
===Wiki Requirements===<br />
<html><br />
<h4>iGEM Logo</h4><br />
<p>All iGEM Team Wikis must include the iGEM logo at the top of the page and a visible link back to the iGEM 2014 Wiki Main Page in the header (or at the top of the page). All wiki pages must preserve the user editing menu (notifications, username, messages, history, edit). In the case where the user heading is not visible, an automatic heading will be overlaid on top of the wiki page(s) where the heading is missing. </p><br />
<h4>The iGEM Login Bar</h4><br />
<p>The iGEM Login Bar is a 20 pixel high, full-width menu bar that exists on all 2014.igem.org pages. It contains:<br />
<ul><br />
<li>wiki tools (edit, history, watch, etc.)</li><br />
<li>login</li><br />
</ul><br />
All iGEM 2014 Team Wikis are required to have the Login Bar. All wiki pages must preserve the user editing menu (notifications, username, messages, history, edit). Please keep this in mind as you design your wiki.</p><br />
<h4>No Adobe Flash</h4> <br />
<p>Flash is not permitted on the iGEM 2014 wiki. Adobe flash is 100% proprietary and you cannot view the source like you can with our wiki. We chose wikis for teams to build their projects so the source code would be available for future teams, to build on the concept of open source. Flash can also be hosted on external sites and we want 100% of the content of our wikis to be on our wikis. </p> <br />
<h4>Upload to 2014.igem.org server</h4><br />
<p>All team pages, images, documents and <b>code</b> must be hosted on the <b>2014.igem.org</b> server. We preserve all iGEM content on our own servers so future teams can learn from what you have done. When you store content on your own sites or servers, after time, links might become broken, sites might go down, and information will be lost. <br /><br />
Additionally, hosting content outside of 2014.iGEM.org allows teams to change/add information to their wiki after the wiki freeze. Please note, that altering content after the wiki freeze is a <a href="https://2014.igem.org/Responsible_Conduct">form of cheating</a>.<br />
</p><br />
<h4>No iframes</h4> <br />
<p><b>iframes</b> are not permitted on the iGEM wiki. If an iframe was used to access content outside of <b>2014.igem.org</b>...<br />
<ul><br />
<li>it would break when there was an issue with the outside server</li> <br />
<li>it would allow a team to show change/add content after the wiki freeze. Please note, that altering content after the wiki freeze is a <a href="https://2014.igem.org/Responsible_Conduct">form of cheating</a></li> <br />
</ul><br />
</p><br />
<h4>2014.igem.org/Team:Team_Name</h4><br />
<p>All iGEM 2014 teams are given a namespace on the iGEM 2014 wiki with their team name. Teams are allowed to create and edit pages within their respective team namespace. Teams are <b>not allowed</b> to create or edit pages belonging to another team's namespace.</p><br />
<h4>Wiki Freeze - October 17th</h4><br />
<p>The wiki freeze for the 2014 Giant Jamboree is on <a href="https://2014.igem.org/Calendar_of_Events">October 17th,</a> along with other deadlines. iGEM experiences higher than normal traffic on this day which can lead to strain on our servers and sessions timing out for users. iGEM HQ recommends that users do not wait till the last day to work/finish their wikis. <b>Once the wikis are frozen, users can no longer make any changes until they are unfrozen after the Jamboree.</b></p><br />
<h4>Other deadlines</h4><br />
<p>The team's project description must be documented on their iGEM Team Wiki by the deadline. The project description should be 1-3 paragraphs and only needs to include an up-to-date explanation of the project.</p><br />
<p>The team's wiki must include an attributions section.</p><br />
<h4>Creative Commons</h4><br />
<p>All content on this wiki is available under the Creative Commons <a href="http://creativecommons.org/licenses/by-sa/3.0/">Attribution-ShareAlike 3.0 Unported</a> license (or any later version).<br />
<img src="http://i.creativecommons.org/l/by/3.0/88x31.png"></p><br />
<br /><br /><br />
<br />
</html><br />
<br />
===Wiki Editing===<br />
<html><br />
<h4>Add a wiki page, change a wiki page, delete a wiki page, etc.</h4><br />
<p>All iGEM wiki sites are powered by Mediawiki. See the <a href="http://www.mediawiki.org/wiki/Help:Contents">Mediawiki Help page</a> for details on how to edit wiki pages and more.</p><br />
<p>Using/editing the wiki is a trial-and-error process. Editing the wiki is a simple, fun thing to do and you definitely get better the more you play around with it. The key is to take a look at other wiki pages and see what you like. Then all you have to do is go to the source (either view source if you're not logged in, or edit if you are logged in), copy it, and modify it to fit your needs. It doesn't have to be perfect before you can take a look at what it looks like. Try things out and see what results they yield.</p><br />
<br />
<h4>Adding a page to your team's namespace?</h4><br />
<p>You must keep your team's pages in your team namespace. For example, take a look at <a href="https://2014.igem.org/Team:Example">2014.igem.org/Team:Example</a></p> <br />
<p>Specifically, when you create a new page, you just have to name it <b>Team</b>:<a href="https://igem.org/Team_List">OFFICIAL team name</a>/PageName. For example, if you were on Team Example and wanted to create a Biosensor project page you would name it <b>Team:Example/Biosensor_project</b>.</p><br />
<br />
<h4>Using html in wiki pages</h4><br />
<p>Instead of using wiki markup, you can use <b>html</b> in the wiki editor. Just put your html code in between <i>&lt;html>&lt;/html></i></p><br />
<br />
<h4>Using CSS and/or Javascript</h4><br />
<p>You can also use <b>CSS</b> and <b>Javascript</b> on the wiki by adding your <i>&lt;style></i> and <i>&lt;script></i> tags into your <i>&lt;html></i> code.</p><br />
<p>If you want to have an external CSS stylesheet or Javascript, you can create a <b>wiki template page</b>.</p><br />
<br />
<h4>Using Wiki Templates</h4><br />
<p>If there is standard text/code that you want to add to more than one page, like a CSS style or script, then you can use <a href="http://www.mediawiki.org/wiki/Help:Templates">MediaWiki templates</a></p><br />
<p>You can create a <b>wiki template page</b> to house your HTML/CSS/Javascript, by entering <i>{{Team:YourTeamName/CSS}}</i> into your wiki markup. Saving the page will create a link for a new template page, which you can edit and enter all of your CSS code. You can then call <i>{{Team:YourTeamName/CSS}}</i> on other pages.</p><br />
<p>Take a look at a few 2013 team wikis to see how other teams setup the styling. You can do this by going to a wiki, and looking for <i>view source</i> in the default wiki links at the top of the page. See <a href="https://2013.igem.org/Template:MIT-style">MIT's</a> and <a href="https://2013.igem.org/Team:TU-Munich">TU-Munich's</a> for examples.</p><br />
<br />
<br /><br /><br />
</html><br />
<br />
===Perspectives from an iGEM veteran===<br />
<html><br />
<table cellspacing="10" style="text-align: justify;" width="965px"><br />
<br />
<tr> <br />
<br />
<td width="48%"><br />
Hello iGEMers!<br />
<br><br />
I was also part of an iGEM team!<br />
<br><br />
In 2011 and 2012 my role was to design and create our team’s wiki. So wiki freeze was my major deadline. I am by no means an expert but let me share with you some of the things I learned with two wiki freezes under my belt.<br />
<br><br><br />
<b> 1.- Test your webpage layout: is information easy to find?</b> </br><br />
<p> I made the terrible mistake of not asking for a third party’s opinion about the layout of information on our site. It was obvious for me how things were laid out and organized. It wasn’t for the people evaluating us. <br><br />
Also, stick to the 3 click rule: content must reachable within 3 clicks so the user does not feel lost or confused. If someone wants to read your abstract, their path should be something like this (Menu –> Project –> Project Description -> Abstract)</p><br />
<br><br />
<b> 2.- Look at other teams’ code, see how they documented and what resources they used. </b><br><br />
<p> It is always good to get inspiration from other iGEM teams. See what you liked that they did and strive to improve! </p><br />
<br><br />
<b> 3.- Start working on your documentation early on. </b> <br><br />
<p>This was a good thing that we did; we created a common file that more than one person can edit at a time. Divide the documentation into smaller files and assign a team member to fully document that topic. In the end you will have a printable version of your project that you can share as a pdf file with other people!</p><br />
<br><br />
<br />
</td><br />
<br />
<td width="4%"></td><br />
<br />
<td width="48%" valign="top"><br />
<b> 4.- Name your images according to the project and keep them all in a folder on your computer. </b> <br><br />
<p> Sometimes naming your gel image “gelthingy_whyiamworkingat3am” sounds perfect at 3AM but later it may not be easy to know what or when that photograph was taken or that image created. <br><br />
Also, the iGEM database doesn’t know that you created that file so if someone names their file with the same name it can end up being replaced! Avoid using generic names like “banner.png” or “logo.jpg”.<br><br />
Try using your team’s name and the webpage where the image will appear, this helps you remember where to place it and reduce the risk of another team overwriting. “JoyUniversity_TeamBios_Richard.jpg” </p><br />
<br><br />
<b> 5.- Do not leave everything to the last minute! </b><br />
<br />
<p> Plan ahead. The last thing you want to be doing at 11:30PM the night of wiki freeze is uploading images. It is very stressful to be looking at the clock and hoping some kind of coding miracle helps you fix bugs faster. Plan to have everything online at least one week ahead so you can go enjoy a nice dinner with your team that night! </p><br />
<br />
<br />
<p> I hope this helps and if you have any questions, feel free to email me or send me a tweet! </p><br />
<i> ana at igem dot org </i><br />
<br><br />
<i> <A HREF="https://twitter.com/anita_sifuentes" > @anita_sifuentes </A> </i><br />
<br />
</td><br />
</tr><br />
</table><br />
<br /><br />
<br />
</html><br />
<br />
===Wiki Templates===<br />
<html><br />
<p> This year we have created a set of template pages that you may for your wiki! <BR> Feel free to edit them as much as you want </p><br />
<a href="https://2014.igem.org/WikitemplateA_home ">Wiki Template A </a></br><br />
<a href="https://2014.igem.org/WikitemplateB_home ">Wiki Template B </a><br />
<BR><BR><br />
<br />
</div><br />
</html><br />
{{MainPage2014/Footer}}</div>Vinoohttp://2014.igem.org/Wiki_How-ToWiki How-To2014-10-10T14:34:14Z<p>Vinoo: </p>
<hr />
<div>{{CSS/Main}}<br />
{{NavBar}}<br />
<html><br />
<div id="contentcontainer"><br />
<br />
</html><br />
{{TOCright}}<br />
===Wiki Freeze - October 17th (11:59 PM -EDT)===<br />
<html><br />
<br />
<p>Your team's project must be documented on the iGEM 2014 wiki, the parts used in your project must be documented on the <a href="http://parts.igem.org">Registry of Standard Biological Parts</a>. You have the freedom to be creative, but a few specific rules apply:</p><br />
<br />
<br /><br />
<br /><br />
<br />
<br />
<style type="text/css"><br />
.simpleTable {<br />
cellspacing: 0;<br />
}<br />
.simpleTable th, .simpleTable td {<br />
padding: 10px 15px;<br />
}<br />
.simpleTable th {<br />
color: #fff;<br />
background-color: #333;<br />
font-style: italic;<br />
font-size: 14pt;<br />
}<br />
.simpleTable tr:nth-child(even) {<br />
background-color: #f0f0f0;<br />
}<br />
</style><br />
</html><br />
<br />
===Wiki Dos and Don'ts===<br />
<html><br />
<table class="simpleTable"><br />
<tr><br />
<th width="250px">Do</th><br />
<th width="250px">Don't</th><br />
<th width="460px">Why?</th><br />
</tr><br />
<tr><br />
<td>Make sure all wiki content, from code and scripts, to files, is hosted on <b>2014.igem.org</b></td><br />
<td>Don't host your wiki or parts of your wiki elsewhere</td><br />
<td>iGEM content is preserved on our servers so future teams can learn from what you've done. When content is stored on other sites/servers, links may become broken (<a href="https://static.igem.org/mediawiki/2014/d/d6/Wiki_server_example1.jpg" title="images were stored off-site, and became broken" target="_blank">example</a>), sites may go down, and <b>information will be lost.</b></td><br />
</tr><br />
<tr><br />
<td>Work on your wiki throughout the year and <b>save small edits for last</b></td><br />
<td>Don't wait to add/edit large portions of wiki content the day of the <b>Wiki Freeze</b></td><br />
<td>Just before the Wiki Freeze, iGEM websites experience <b>increased traffic and server loads.</b> This can be a difficult time to make larger changes or additions to your wiki. Don't wait till the last minute!</td><br />
</tr><br />
<tr><br />
<td>Name uploaded files clearly and uniquely (TeamName_Header.png)</td><br />
<td>Don't use generic names for you files (Header.png)</td><br />
<td>Using <b>unique names</b> makes searching/identification of uploaded files easier, and helps prevent files from being overwritten.</td><br />
</tr><br />
</table><br />
<br /><br /><br />
<br />
</html><br />
<br />
===Wiki Requirements===<br />
<html><br />
<h4>iGEM Logo</h4><br />
<p>All iGEM Team Wikis must include the iGEM logo at the top of the page and a visible link back to the iGEM 2014 Wiki Main Page in the header (or at the top of the page). All wiki pages must preserve the user editing menu (notifications, username, messages, history, edit). In the case where the user heading is not visible, an automatic heading will be overlaid on top of the wiki page(s) where the heading is missing. </p><br />
<h4>The iGEM Login Bar</h4><br />
<p>The iGEM Login Bar is a 20 pixel high, full-width menu bar that exists on all 2014.igem.org pages. It contains:<br />
<ul><br />
<li>wiki tools (edit, history, watch, etc.)</li><br />
<li>login</li><br />
</ul><br />
All iGEM 2014 Team Wikis are required to have the Login Bar. All wiki pages must preserve the user editing menu (notifications, username, messages, history, edit). Please keep this in mind as you design your wiki.</p><br />
<h4>No Adobe Flash</h4> <br />
<p>Flash is not permitted on the iGEM 2014 wiki. Adobe flash is 100% proprietary and you cannot view the source like you can with our wiki. We chose wikis for teams to build their projects so the source code would be available for future teams, to build on the concept of open source. Flash can also be hosted on external sites and we want 100% of the content of our wikis to be on our wikis. </p> <br />
<h4>Upload to 2014.igem.org server</h4><br />
<p>All team pages, images, documents and <b>code</b> must be hosted on the <b>2014.igem.org</b> server. We preserve all iGEM content on our own servers so future teams can learn from what you have done. When you store content on your own sites or servers, after time, links might become broken, sites might go down, and information will be lost. <br /><br />
Additionally, hosting content outside of 2014.iGEM.org allows teams to change/add information to their wiki after the wiki freeze. Please note, that altering content after the wiki freeze is a <a href="https://2014.igem.org/Responsible_Conduct">form of cheating</a>.<br />
</p><br />
<h4>No iframes</h4> <br />
<p><b>iframes</b> are not permitted on the iGEM wiki. If an iframe was used to access content outside of <b>2014.igem.org</b>...<br />
<ul><br />
<li>it would break when there was an issue with the outside server</li> <br />
<li>it would allow a team to show change/add content after the wiki freeze. Please note, that altering content after the wiki freeze is a <a href="https://2014.igem.org/Responsible_Conduct">form of cheating</a></li> <br />
</ul><br />
</p><br />
<h4>2014.igem.org/Team:Team_Name</h4><br />
<p>All iGEM 2014 teams are given a namespace on the iGEM 2014 wiki with their team name. Teams are allowed to create and edit pages within their respective team namespace. Teams are <b>not allowed</b> to create or edit pages belonging to another team's namespace.</p><br />
<h4>Wiki Freeze - October 17th</h4><br />
<p>The wiki freeze for the 2014 Giant Jamboree is on <a href="https://2014.igem.org/Calendar_of_Events">October 17th,</a> along with other deadlines. iGEM experiences higher than normal traffic on this day which can lead to strain on our servers and sessions timing out for users. iGEM HQ recommends that users do not wait till the last day to work/finish their wikis. <b>Once the wikis are frozen, users can no longer make any changes until they are unfrozen after the Jamboree.</b></p><br />
<h4>Other deadlines</h4><br />
<p>The team's project description must be documented on their iGEM Team Wiki by the deadline. The project description should be 1-3 paragraphs and only needs to include an up-to-date explanation of the project.</p><br />
<p>The team's wiki must include an attributions section.</p><br />
<h4>Creative Commons</h4><br />
<p>All content on this wiki is available under the Creative Commons <a href="http://creativecommons.org/licenses/by-sa/3.0/">Attribution-ShareAlike 3.0 Unported</a> license (or any later version).<br />
<img src="http://i.creativecommons.org/l/by/3.0/88x31.png"></p><br />
<br /><br /><br />
<br />
</html><br />
<br />
===Perspectives from an iGEM veteran===<br />
<html><br />
<table cellspacing="10" style="text-align: justify;" width="965px"><br />
<br />
<tr> <br />
<br />
<td width="48%"><br />
Hello iGEMers!<br />
<br><br />
I was also part of an iGEM team!<br />
<br><br />
In 2011 and 2012 my role was to design and create our team’s wiki. So wiki freeze was my major deadline. I am by no means an expert but let me share with you some of the things I learned with two wiki freezes under my belt.<br />
<br><br><br />
<b> 1.- Test your webpage layout: is information easy to find?</b> </br><br />
<p> I made the terrible mistake of not asking for a third party’s opinion about the layout of information on our site. It was obvious for me how things were laid out and organized. It wasn’t for the people evaluating us. <br><br />
Also, stick to the 3 click rule: content must reachable within 3 clicks so the user does not feel lost or confused. If someone wants to read your abstract, their path should be something like this (Menu –> Project –> Project Description -> Abstract)</p><br />
<br><br />
<b> 2.- Look at other teams’ code, see how they documented and what resources they used. </b><br><br />
<p> It is always good to get inspiration from other iGEM teams. See what you liked that they did and strive to improve! </p><br />
<br><br />
<b> 3.- Start working on your documentation early on. </b> <br><br />
<p>This was a good thing that we did; we created a common file that more than one person can edit at a time. Divide the documentation into smaller files and assign a team member to fully document that topic. In the end you will have a printable version of your project that you can share as a pdf file with other people!</p><br />
<br><br />
<br />
</td><br />
<br />
<td width="4%"></td><br />
<br />
<td width="48%" valign="top"><br />
<b> 4.- Name your images according to the project and keep them all in a folder on your computer. </b> <br><br />
<p> Sometimes naming your gel image “gelthingy_whyiamworkingat3am” sounds perfect at 3AM but later it may not be easy to know what or when that photograph was taken or that image created. <br><br />
Also, the iGEM database doesn’t know that you created that file so if someone names their file with the same name it can end up being replaced! Avoid using generic names like “banner.png” or “logo.jpg”.<br><br />
Try using your team’s name and the webpage where the image will appear, this helps you remember where to place it and reduce the risk of another team overwriting. “JoyUniversity_TeamBios_Richard.jpg” </p><br />
<br><br />
<b> 5.- Do not leave everything to the last minute! </b><br />
<br />
<p> Plan ahead. The last thing you want to be doing at 11:30PM the night of wiki freeze is uploading images. It is very stressful to be looking at the clock and hoping some kind of coding miracle helps you fix bugs faster. Plan to have everything online at least one week ahead so you can go enjoy a nice dinner with your team that night! </p><br />
<br />
<br />
<p> I hope this helps and if you have any questions, feel free to email me or send me a tweet! </p><br />
<i> ana at igem dot org </i><br />
<br><br />
<i> <A HREF="https://twitter.com/anita_sifuentes" > @anita_sifuentes </A> </i><br />
<br />
</td><br />
</tr><br />
</table><br />
<br /><br />
<br />
</html><br />
<br />
===Wiki Templates===<br />
<html><br />
<p> This year we have created a set of template pages that you may for your wiki! <BR> Feel free to edit them as much as you want </p><br />
<a href="https://2014.igem.org/WikitemplateA_home ">Wiki Template A </a></br><br />
<a href="https://2014.igem.org/WikitemplateB_home ">Wiki Template B </a><br />
<BR><BR><br />
<br />
</div><br />
</html><br />
{{MainPage2014/Footer}}</div>Vinoohttp://2014.igem.org/Wiki_How-ToWiki How-To2014-10-10T14:31:38Z<p>Vinoo: /* Wiki Dos and Don'ts */</p>
<hr />
<div>{{CSS/Main}}<br />
{{NavBar}}<br />
<html><br />
<div id="contentcontainer"><br />
<br />
</html><br />
{{TOCright}}<br />
===Wiki Freeze - October 17th (11:59 PM -EDT)===<br />
<html><br />
<br />
<p>Your team's project must be documented on the iGEM 2014 wiki, the parts used in your project must be documented on the <a href="http://parts.igem.org">Registry of Standard Biological Parts</a>. You have the freedom to be creative, but a few specific rules apply:</p><br />
<br />
<br /><br />
<br /><br />
<br />
<br />
<style type="text/css"><br />
.simpleTable {<br />
cellspacing: 0;<br />
}<br />
.simpleTable th, .simpleTable td {<br />
padding: 10px 15px;<br />
}<br />
.simpleTable th {<br />
color: #fff;<br />
background-color: #333;<br />
font-style: italic;<br />
font-size: 14pt;<br />
}<br />
.simpleTable tr:nth-child(even) {<br />
background-color: #f0f0f0;<br />
}<br />
</style><br />
</html><br />
<br />
===Wiki Dos and Don'ts===<br />
<html><br />
<table class="simpleTable"><br />
<tr><br />
<th width="250px">Do</th><br />
<th width="250px">Don't</th><br />
<th width="460px">Why?</th><br />
</tr><br />
<tr><br />
<td>Make sure all wiki content, from code and scripts, to files, is hosted on <b>2014.igem.org</b></td><br />
<td>Don't host your wiki or parts of your wiki elsewhere</td><br />
<td>iGEM content is preserved on our servers so future teams can learn from what you've done. When content is stored on other sites/servers, links may become broken (<a href="https://static.igem.org/mediawiki/2014/d/d6/Wiki_server_example1.jpg" title="images were stored off-site, and became broken" target="_blank">example</a>), sites may go down, and <b>information will be lost.</b></td><br />
</tr><br />
<tr><br />
<td>Work on your wiki throughout the year and <b>save small edits for last</b></td><br />
<td>Don't wait to add/edit large portions of wiki content the day of the <b>Wiki Freeze</b></td><br />
<td>Just before the Wiki Freeze, iGEM websites experience <b>increased traffic and server loads.</b> This can be a difficult time to make larger changes or additions to your wiki. Don't wait till the last minute!</td><br />
</tr><br />
<tr><br />
<td>Name uploaded files clearly and uniquely (TeamName_Header.png)</td><br />
<td>Don't use generic names for you files (Header.png)</td><br />
<td>Using <b>unique names</b> makes searching/identification of uploaded files easier, and helps prevent files from being overwritten.</td><br />
</tr><br />
</table><br />
<br /><br /><br />
<br />
</html><br />
<br />
===Perspectives from an iGEM veteran===<br />
<html><br />
<table cellspacing="10" style="text-align: justify;" width="965px"><br />
<br />
<tr> <br />
<br />
<td width="48%"><br />
Hello iGEMers!<br />
<br><br />
I was also part of an iGEM team!<br />
<br><br />
In 2011 and 2012 my role was to design and create our team’s wiki. So wiki freeze was my major deadline. I am by no means an expert but let me share with you some of the things I learned with two wiki freezes under my belt.<br />
<br><br><br />
<b> 1.- Test your webpage layout: is information easy to find?</b> </br><br />
<p> I made the terrible mistake of not asking for a third party’s opinion about the layout of information on our site. It was obvious for me how things were laid out and organized. It wasn’t for the people evaluating us. <br><br />
Also, stick to the 3 click rule: content must reachable within 3 clicks so the user does not feel lost or confused. If someone wants to read your abstract, their path should be something like this (Menu –> Project –> Project Description -> Abstract)</p><br />
<br><br />
<b> 2.- Look at other teams’ code, see how they documented and what resources they used. </b><br><br />
<p> It is always good to get inspiration from other iGEM teams. See what you liked that they did and strive to improve! </p><br />
<br><br />
<b> 3.- Start working on your documentation early on. </b> <br><br />
<p>This was a good thing that we did; we created a common file that more than one person can edit at a time. Divide the documentation into smaller files and assign a team member to fully document that topic. In the end you will have a printable version of your project that you can share as a pdf file with other people!</p><br />
<br><br />
<br />
</td><br />
<br />
<td width="4%"></td><br />
<br />
<td width="48%" valign="top"><br />
<b> 4.- Name your images according to the project and keep them all in a folder on your computer. </b> <br><br />
<p> Sometimes naming your gel image “gelthingy_whyiamworkingat3am” sounds perfect at 3AM but later it may not be easy to know what or when that photograph was taken or that image created. <br><br />
Also, the iGEM database doesn’t know that you created that file so if someone names their file with the same name it can end up being replaced! Avoid using generic names like “banner.png” or “logo.jpg”.<br><br />
Try using your team’s name and the webpage where the image will appear, this helps you remember where to place it and reduce the risk of another team overwriting. “JoyUniversity_TeamBios_Richard.jpg” </p><br />
<br><br />
<b> 5.- Do not leave everything to the last minute! </b><br />
<br />
<p> Plan ahead. The last thing you want to be doing at 11:30PM the night of wiki freeze is uploading images. It is very stressful to be looking at the clock and hoping some kind of coding miracle helps you fix bugs faster. Plan to have everything online at least one week ahead so you can go enjoy a nice dinner with your team that night! </p><br />
<br />
<br />
<p> I hope this helps and if you have any questions, feel free to email me or send me a tweet! </p><br />
<i> ana at igem dot org </i><br />
<br><br />
<i> <A HREF="https://twitter.com/anita_sifuentes" > @anita_sifuentes </A> </i><br />
<br />
</td><br />
</tr><br />
</table><br />
<br /><br />
<br />
</html><br />
===Wiki Requirements===<br />
<html><br />
<h4>iGEM Logo</h4><br />
<p>All iGEM Team Wikis must include the iGEM logo at the top of the page and a visible link back to the iGEM 2014 Wiki Main Page in the header (or at the top of the page). All wiki pages must preserve the user editing menu (notifications, username, messages, history, edit). In the case where the user heading is not visible, an automatic heading will be overlaid on top of the wiki page(s) where the heading is missing. </p><br />
<h4>The iGEM Login Bar</h4><br />
<p>The iGEM Login Bar is a 20 pixel high, full-width menu bar that exists on all 2014.igem.org pages. It contains:<br />
<ul><br />
<li>wiki tools (edit, history, watch, etc.)</li><br />
<li>login</li><br />
</ul><br />
All iGEM 2014 Team Wikis are required to have the Login Bar. All wiki pages must preserve the user editing menu (notifications, username, messages, history, edit). Please keep this in mind as you design your wiki.</p><br />
<h4>No Adobe Flash</h4> <br />
<p>Flash is not permitted on the iGEM 2014 wiki. Adobe flash is 100% proprietary and you cannot view the source like you can with our wiki. We chose wikis for teams to build their projects so the source code would be available for future teams, to build on the concept of open source. Flash can also be hosted on external sites and we want 100% of the content of our wikis to be on our wikis. </p> <br />
<h4>Upload to 2014.igem.org server</h4><br />
<p>All team pages, images, documents and <b>code</b> must be hosted on the <b>2014.igem.org</b> server. We preserve all iGEM content on our own servers so future teams can learn from what you have done. When you store content on your own sites or servers, after time, links might become broken, sites might go down, and information will be lost. <br /><br />
Additionally, hosting content outside of 2014.iGEM.org allows teams to change/add information to their wiki after the wiki freeze. Please note, that altering content after the wiki freeze is a <a href="https://2014.igem.org/Responsible_Conduct">form of cheating</a>.<br />
</p><br />
<h4>No iframes</h4> <br />
<p><b>iframes</b> are not permitted on the iGEM wiki. <br />
<ul>if an iframe was used to access content outside of <b>2014.igem.org</b><br />
<li>it would break when there was an issue with the outside server</li> <br />
<li>it would allow a team to show change/add content after the wiki freeze. Please note, that altering content after the wiki freeze is a <a href="https://2014.igem.org/Responsible_Conduct">form of cheating</a></li> <br />
</ul></p><br />
<h4>2014.igem.org/Team:Team_Name</h4><br />
<p>All iGEM 2014 teams are given a namespace on the iGEM 2014 wiki with their team name. Teams are allowed to create and edit pages within their respective team namespace. Teams are <b>not allowed</b> to create or edit pages belonging to another team's namespace.</p><br />
<h4>Wiki Freeze - October 17th</h4><br />
<p>The wiki freeze for the 2014 Giant Jamboree is on <a href="https://2014.igem.org/Calendar_of_Events">October 17th,</a> along with other deadlines. iGEM experiences higher than normal traffic on this day which can lead to strain on our servers and sessions timing out for users. iGEM HQ recommends that users do not wait till the last day to work/finish their wikis. <b>Once the wikis are frozen, users can no longer make any changes until they are unfrozen after the Jamboree.</b></p><br />
<h4>Other deadlines</h4><br />
<p>The team's project description must be documented on their iGEM Team Wiki by the deadline. The project description should be 1-3 paragraphs and only needs to include an up-to-date explanation of the project.</p><br />
<p>The team's wiki must include an attributions section.</p><br />
<h4>Creative Commons</h4><br />
<p>All content on this wiki is available under the Creative Commons <a href="http://creativecommons.org/licenses/by-sa/3.0/">Attribution-ShareAlike 3.0 Unported</a> license (or any later version).<br />
<img src="http://i.creativecommons.org/l/by/3.0/88x31.png"></p><br />
<br /><br /><br />
<br />
</html><br />
<br />
===Wiki Templates===<br />
<html><br />
<p> This year we have created a set of template pages that you may for your wiki! <BR> Feel free to edit them as much as you want </p><br />
<a href="https://2014.igem.org/WikitemplateA_home ">Wiki Template A </a></br><br />
<a href="https://2014.igem.org/WikitemplateB_home ">Wiki Template B </a><br />
<BR><BR><br />
<br />
<br />
<!--<br />
<br />
<h3>Wiki Freeze - October 17th</h3><br />
<p>The wiki freeze for the 2014 Giant Jamboree is on <a href="https://2014.igem.org/Calendar_of_Events">October 17th,</a> along with other deadlines. iGEM experiences higher than normal traffic on this day which can lead to strain on our servers and sessions timing out for users. <b>iGEM HQ recommends that users do not wait till the last day to work/finish their wikis.</b> Once the wikis are frozen, users can no longer make any changes until they are unfrozen after the Jamboree.</p><br />
<br />
<br /><br />
<br />
<h3>2014.igem.org/Team:Team_Name</h3><br />
<p>All iGEM 2014 teams are given a namespace on the iGEM 2014 wiki with their team name. Teams are allowed to create and edit pages within their respective team namespace. Teams are <b>not allowed</b> to create or edit pages belonging to another team's namespace.</p><br />
<br />
<br /><br />
<br />
<h3>Upload to 2014.igem.org server</h3><br />
<p>All team pages, images, documents and code must be hosted on the <b>2014.igem.org</b> server. We preserve all iGEM content on our own servers so future teams can learn from what you have done. When you store content on your own sites or servers, after time, links might become broken, sites might go down, and information will be lost.<br />
</p><br />
<br />
<ul>Use the <a href="https://2014.igem.org/Special:Upload">wiki upload tool</a> to upload your files. <br />
<li>Make sure to name your files clearly and uniquely: <i>File:</i><b>Team_Name_Flow_Cytometry_01.png</b>, instead of <i>File:</i><b>1.png</b></li><br />
</ul><br />
<br />
<h4>Upload to 2014.igem.org server</h4><br />
<p>When you store content on your own sites or servers, after time, links might become broken, sites might go down, and information will be lost.</p><br />
<br />
<br /><br />
<br />
<br />
<br />
<h3>No Adobe Flash</h3> <br />
<p>Flash is not permitted on the iGEM 2014 wiki. Adobe flash is 100% proprietary and you cannot view the source like you can with our wiki. We chose wikis for teams to build their projects so the source code would be available for future teams, to build on the concept of open source. Flash can also be hosted on external sites and we want 100% of the content of our wikis to be on our wikis. </p> <br />
<br />
<h3>Deadlines and the Wiki Freeze</h3><br />
<p>The team's project description must be documented on their iGEM Team Wiki by the deadline. The project description should be 1-3 paragraphs and only needs to include an up-to-date explanation of the project.</p><br />
<p>The team's wiki must include a link to the completed Safety form and an attributions section.</p><br />
<br />
<h3>iGEM Logo</h3><br />
<p>All iGEM Team Wikis must include the iGEM logo at the top of the page and a visible link back to the iGEM 2014 Wiki Main Page in the header (or at the top of the page). All wiki pages must preserve the user editing menu (notifications, username, messages, history, edit). In the case where the user heading is not visible, an automatic heading will be overlaid on top of the wiki page(s) where the heading is missing. </p><br />
<br />
<h3>The iGEM Login Bar</h3><br />
<p>The iGEM Login Bar is a 20 pixel high, full-width menu bar that exists on all 2014.igem.org pages. It contains:<br />
<ul><br />
<li>wiki tools (edit, history, watch, etc.)</li><br />
<li>login</li><br />
</ul><br />
All iGEM 2014 Team Wikis are required to have the Login Bar. Please keep this in mind as you design your wiki.</p><br />
<br />
--><br />
<br />
<br />
<br />
</div><br />
</html><br />
{{MainPage2014/Footer}}</div>Vinoohttp://2014.igem.org/Wiki_How-ToWiki How-To2014-10-10T14:30:48Z<p>Vinoo: /* Wiki Requirements */</p>
<hr />
<div>{{CSS/Main}}<br />
{{NavBar}}<br />
<html><br />
<div id="contentcontainer"><br />
<br />
</html><br />
{{TOCright}}<br />
===Wiki Freeze - October 17th (11:59 PM -EDT)===<br />
<html><br />
<br />
<p>Your team's project must be documented on the iGEM 2014 wiki, the parts used in your project must be documented on the <a href="http://parts.igem.org">Registry of Standard Biological Parts</a>. You have the freedom to be creative, but a few specific rules apply:</p><br />
<br />
<br /><br />
<br /><br />
<br />
<br />
<style type="text/css"><br />
.simpleTable {<br />
cellspacing: 0;<br />
}<br />
.simpleTable th, .simpleTable td {<br />
padding: 10px 15px;<br />
}<br />
.simpleTable th {<br />
color: #fff;<br />
background-color: #333;<br />
font-style: italic;<br />
font-size: 14pt;<br />
}<br />
.simpleTable tr:nth-child(even) {<br />
background-color: #f0f0f0;<br />
}<br />
</style><br />
</html><br />
<br />
===Wiki Dos and Don'ts===<br />
<html><br />
<table class="simpleTable"><br />
<tr><br />
<th width="250px">Do</th><br />
<th width="250px">Don't</th><br />
<th width="460px">Why?</th><br />
</tr><br />
<tr><br />
<td>Make sure all wiki content, from pages to files, is hosted on <b>2014.igem.org</b></td><br />
<td>Don't host your wiki or parts of your wiki elsewhere</td><br />
<td>iGEM content is preserved on our servers so future teams can learn from what you've done. When content is stored on other sites/servers, links may become broken (<a href="https://static.igem.org/mediawiki/2014/d/d6/Wiki_server_example1.jpg" title="images were stored off-site, and became broken" target="_blank">example</a>), sites may go down, and <b>information will be lost.</b></td><br />
</tr><br />
<tr><br />
<td>Work on your wiki throughout the year and <b>save small edits for last</b></td><br />
<td>Don't wait to add/edit large portions of wiki content the day of the <b>Wiki Freeze</b></td><br />
<td>Just before the Wiki Freeze, iGEM websites experience <b>increased traffic and server loads.</b> This can be a difficult time to make larger changes or additions to your wiki. Don't wait till the last minute!</td><br />
</tr><br />
<tr><br />
<td>Name uploaded files clearly and uniquely (TeamName_Header.png)</td><br />
<td>Don't use generic names for you files (Header.png)</td><br />
<td>Using <b>unique names</b> makes searching/identification of uploaded files easier, and helps prevent files from being overwritten.</td><br />
</tr><br />
</table><br />
<br /><br /><br />
<br />
</html><br />
===Perspectives from an iGEM veteran===<br />
<html><br />
<table cellspacing="10" style="text-align: justify;" width="965px"><br />
<br />
<tr> <br />
<br />
<td width="48%"><br />
Hello iGEMers!<br />
<br><br />
I was also part of an iGEM team!<br />
<br><br />
In 2011 and 2012 my role was to design and create our team’s wiki. So wiki freeze was my major deadline. I am by no means an expert but let me share with you some of the things I learned with two wiki freezes under my belt.<br />
<br><br><br />
<b> 1.- Test your webpage layout: is information easy to find?</b> </br><br />
<p> I made the terrible mistake of not asking for a third party’s opinion about the layout of information on our site. It was obvious for me how things were laid out and organized. It wasn’t for the people evaluating us. <br><br />
Also, stick to the 3 click rule: content must reachable within 3 clicks so the user does not feel lost or confused. If someone wants to read your abstract, their path should be something like this (Menu –> Project –> Project Description -> Abstract)</p><br />
<br><br />
<b> 2.- Look at other teams’ code, see how they documented and what resources they used. </b><br><br />
<p> It is always good to get inspiration from other iGEM teams. See what you liked that they did and strive to improve! </p><br />
<br><br />
<b> 3.- Start working on your documentation early on. </b> <br><br />
<p>This was a good thing that we did; we created a common file that more than one person can edit at a time. Divide the documentation into smaller files and assign a team member to fully document that topic. In the end you will have a printable version of your project that you can share as a pdf file with other people!</p><br />
<br><br />
<br />
</td><br />
<br />
<td width="4%"></td><br />
<br />
<td width="48%" valign="top"><br />
<b> 4.- Name your images according to the project and keep them all in a folder on your computer. </b> <br><br />
<p> Sometimes naming your gel image “gelthingy_whyiamworkingat3am” sounds perfect at 3AM but later it may not be easy to know what or when that photograph was taken or that image created. <br><br />
Also, the iGEM database doesn’t know that you created that file so if someone names their file with the same name it can end up being replaced! Avoid using generic names like “banner.png” or “logo.jpg”.<br><br />
Try using your team’s name and the webpage where the image will appear, this helps you remember where to place it and reduce the risk of another team overwriting. “JoyUniversity_TeamBios_Richard.jpg” </p><br />
<br><br />
<b> 5.- Do not leave everything to the last minute! </b><br />
<br />
<p> Plan ahead. The last thing you want to be doing at 11:30PM the night of wiki freeze is uploading images. It is very stressful to be looking at the clock and hoping some kind of coding miracle helps you fix bugs faster. Plan to have everything online at least one week ahead so you can go enjoy a nice dinner with your team that night! </p><br />
<br />
<br />
<p> I hope this helps and if you have any questions, feel free to email me or send me a tweet! </p><br />
<i> ana at igem dot org </i><br />
<br><br />
<i> <A HREF="https://twitter.com/anita_sifuentes" > @anita_sifuentes </A> </i><br />
<br />
</td><br />
</tr><br />
</table><br />
<br /><br />
<br />
</html><br />
===Wiki Requirements===<br />
<html><br />
<h4>iGEM Logo</h4><br />
<p>All iGEM Team Wikis must include the iGEM logo at the top of the page and a visible link back to the iGEM 2014 Wiki Main Page in the header (or at the top of the page). All wiki pages must preserve the user editing menu (notifications, username, messages, history, edit). In the case where the user heading is not visible, an automatic heading will be overlaid on top of the wiki page(s) where the heading is missing. </p><br />
<h4>The iGEM Login Bar</h4><br />
<p>The iGEM Login Bar is a 20 pixel high, full-width menu bar that exists on all 2014.igem.org pages. It contains:<br />
<ul><br />
<li>wiki tools (edit, history, watch, etc.)</li><br />
<li>login</li><br />
</ul><br />
All iGEM 2014 Team Wikis are required to have the Login Bar. All wiki pages must preserve the user editing menu (notifications, username, messages, history, edit). Please keep this in mind as you design your wiki.</p><br />
<h4>No Adobe Flash</h4> <br />
<p>Flash is not permitted on the iGEM 2014 wiki. Adobe flash is 100% proprietary and you cannot view the source like you can with our wiki. We chose wikis for teams to build their projects so the source code would be available for future teams, to build on the concept of open source. Flash can also be hosted on external sites and we want 100% of the content of our wikis to be on our wikis. </p> <br />
<h4>Upload to 2014.igem.org server</h4><br />
<p>All team pages, images, documents and <b>code</b> must be hosted on the <b>2014.igem.org</b> server. We preserve all iGEM content on our own servers so future teams can learn from what you have done. When you store content on your own sites or servers, after time, links might become broken, sites might go down, and information will be lost. <br /><br />
Additionally, hosting content outside of 2014.iGEM.org allows teams to change/add information to their wiki after the wiki freeze. Please note, that altering content after the wiki freeze is a <a href="https://2014.igem.org/Responsible_Conduct">form of cheating</a>.<br />
</p><br />
<h4>No iframes</h4> <br />
<p><b>iframes</b> are not permitted on the iGEM wiki. <br />
<ul>if an iframe was used to access content outside of <b>2014.igem.org</b><br />
<li>it would break when there was an issue with the outside server</li> <br />
<li>it would allow a team to show change/add content after the wiki freeze. Please note, that altering content after the wiki freeze is a <a href="https://2014.igem.org/Responsible_Conduct">form of cheating</a></li> <br />
</ul></p><br />
<h4>2014.igem.org/Team:Team_Name</h4><br />
<p>All iGEM 2014 teams are given a namespace on the iGEM 2014 wiki with their team name. Teams are allowed to create and edit pages within their respective team namespace. Teams are <b>not allowed</b> to create or edit pages belonging to another team's namespace.</p><br />
<h4>Wiki Freeze - October 17th</h4><br />
<p>The wiki freeze for the 2014 Giant Jamboree is on <a href="https://2014.igem.org/Calendar_of_Events">October 17th,</a> along with other deadlines. iGEM experiences higher than normal traffic on this day which can lead to strain on our servers and sessions timing out for users. iGEM HQ recommends that users do not wait till the last day to work/finish their wikis. <b>Once the wikis are frozen, users can no longer make any changes until they are unfrozen after the Jamboree.</b></p><br />
<h4>Other deadlines</h4><br />
<p>The team's project description must be documented on their iGEM Team Wiki by the deadline. The project description should be 1-3 paragraphs and only needs to include an up-to-date explanation of the project.</p><br />
<p>The team's wiki must include an attributions section.</p><br />
<h4>Creative Commons</h4><br />
<p>All content on this wiki is available under the Creative Commons <a href="http://creativecommons.org/licenses/by-sa/3.0/">Attribution-ShareAlike 3.0 Unported</a> license (or any later version).<br />
<img src="http://i.creativecommons.org/l/by/3.0/88x31.png"></p><br />
<br /><br /><br />
<br />
</html><br />
<br />
===Wiki Templates===<br />
<html><br />
<p> This year we have created a set of template pages that you may for your wiki! <BR> Feel free to edit them as much as you want </p><br />
<a href="https://2014.igem.org/WikitemplateA_home ">Wiki Template A </a></br><br />
<a href="https://2014.igem.org/WikitemplateB_home ">Wiki Template B </a><br />
<BR><BR><br />
<br />
<br />
<!--<br />
<br />
<h3>Wiki Freeze - October 17th</h3><br />
<p>The wiki freeze for the 2014 Giant Jamboree is on <a href="https://2014.igem.org/Calendar_of_Events">October 17th,</a> along with other deadlines. iGEM experiences higher than normal traffic on this day which can lead to strain on our servers and sessions timing out for users. <b>iGEM HQ recommends that users do not wait till the last day to work/finish their wikis.</b> Once the wikis are frozen, users can no longer make any changes until they are unfrozen after the Jamboree.</p><br />
<br />
<br /><br />
<br />
<h3>2014.igem.org/Team:Team_Name</h3><br />
<p>All iGEM 2014 teams are given a namespace on the iGEM 2014 wiki with their team name. Teams are allowed to create and edit pages within their respective team namespace. Teams are <b>not allowed</b> to create or edit pages belonging to another team's namespace.</p><br />
<br />
<br /><br />
<br />
<h3>Upload to 2014.igem.org server</h3><br />
<p>All team pages, images, documents and code must be hosted on the <b>2014.igem.org</b> server. We preserve all iGEM content on our own servers so future teams can learn from what you have done. When you store content on your own sites or servers, after time, links might become broken, sites might go down, and information will be lost.<br />
</p><br />
<br />
<ul>Use the <a href="https://2014.igem.org/Special:Upload">wiki upload tool</a> to upload your files. <br />
<li>Make sure to name your files clearly and uniquely: <i>File:</i><b>Team_Name_Flow_Cytometry_01.png</b>, instead of <i>File:</i><b>1.png</b></li><br />
</ul><br />
<br />
<h4>Upload to 2014.igem.org server</h4><br />
<p>When you store content on your own sites or servers, after time, links might become broken, sites might go down, and information will be lost.</p><br />
<br />
<br /><br />
<br />
<br />
<br />
<h3>No Adobe Flash</h3> <br />
<p>Flash is not permitted on the iGEM 2014 wiki. Adobe flash is 100% proprietary and you cannot view the source like you can with our wiki. We chose wikis for teams to build their projects so the source code would be available for future teams, to build on the concept of open source. Flash can also be hosted on external sites and we want 100% of the content of our wikis to be on our wikis. </p> <br />
<br />
<h3>Deadlines and the Wiki Freeze</h3><br />
<p>The team's project description must be documented on their iGEM Team Wiki by the deadline. The project description should be 1-3 paragraphs and only needs to include an up-to-date explanation of the project.</p><br />
<p>The team's wiki must include a link to the completed Safety form and an attributions section.</p><br />
<br />
<h3>iGEM Logo</h3><br />
<p>All iGEM Team Wikis must include the iGEM logo at the top of the page and a visible link back to the iGEM 2014 Wiki Main Page in the header (or at the top of the page). All wiki pages must preserve the user editing menu (notifications, username, messages, history, edit). In the case where the user heading is not visible, an automatic heading will be overlaid on top of the wiki page(s) where the heading is missing. </p><br />
<br />
<h3>The iGEM Login Bar</h3><br />
<p>The iGEM Login Bar is a 20 pixel high, full-width menu bar that exists on all 2014.igem.org pages. It contains:<br />
<ul><br />
<li>wiki tools (edit, history, watch, etc.)</li><br />
<li>login</li><br />
</ul><br />
All iGEM 2014 Team Wikis are required to have the Login Bar. Please keep this in mind as you design your wiki.</p><br />
<br />
--><br />
<br />
<br />
<br />
</div><br />
</html><br />
{{MainPage2014/Footer}}</div>Vinoohttp://2014.igem.org/Wiki_How-ToWiki How-To2014-10-10T14:23:34Z<p>Vinoo: </p>
<hr />
<div>{{CSS/Main}}<br />
{{NavBar}}<br />
<html><br />
<div id="contentcontainer"><br />
<br />
</html><br />
{{TOCright}}<br />
===Wiki Freeze - October 17th (11:59 PM -EDT)===<br />
<html><br />
<br />
<p>Your team's project must be documented on the iGEM 2014 wiki, the parts used in your project must be documented on the <a href="http://parts.igem.org">Registry of Standard Biological Parts</a>. You have the freedom to be creative, but a few specific rules apply:</p><br />
<br />
<br /><br />
<br /><br />
<br />
<br />
<style type="text/css"><br />
.simpleTable {<br />
cellspacing: 0;<br />
}<br />
.simpleTable th, .simpleTable td {<br />
padding: 10px 15px;<br />
}<br />
.simpleTable th {<br />
color: #fff;<br />
background-color: #333;<br />
font-style: italic;<br />
font-size: 14pt;<br />
}<br />
.simpleTable tr:nth-child(even) {<br />
background-color: #f0f0f0;<br />
}<br />
</style><br />
</html><br />
<br />
===Wiki Dos and Don'ts===<br />
<html><br />
<table class="simpleTable"><br />
<tr><br />
<th width="250px">Do</th><br />
<th width="250px">Don't</th><br />
<th width="460px">Why?</th><br />
</tr><br />
<tr><br />
<td>Make sure all wiki content, from pages to files, is hosted on <b>2014.igem.org</b></td><br />
<td>Don't host your wiki or parts of your wiki elsewhere</td><br />
<td>iGEM content is preserved on our servers so future teams can learn from what you've done. When content is stored on other sites/servers, links may become broken (<a href="https://static.igem.org/mediawiki/2014/d/d6/Wiki_server_example1.jpg" title="images were stored off-site, and became broken" target="_blank">example</a>), sites may go down, and <b>information will be lost.</b></td><br />
</tr><br />
<tr><br />
<td>Work on your wiki throughout the year and <b>save small edits for last</b></td><br />
<td>Don't wait to add/edit large portions of wiki content the day of the <b>Wiki Freeze</b></td><br />
<td>Just before the Wiki Freeze, iGEM websites experience <b>increased traffic and server loads.</b> This can be a difficult time to make larger changes or additions to your wiki. Don't wait till the last minute!</td><br />
</tr><br />
<tr><br />
<td>Name uploaded files clearly and uniquely (TeamName_Header.png)</td><br />
<td>Don't use generic names for you files (Header.png)</td><br />
<td>Using <b>unique names</b> makes searching/identification of uploaded files easier, and helps prevent files from being overwritten.</td><br />
</tr><br />
</table><br />
<br /><br /><br />
<br />
</html><br />
===Perspectives from an iGEM veteran===<br />
<html><br />
<table cellspacing="10" style="text-align: justify;" width="965px"><br />
<br />
<tr> <br />
<br />
<td width="48%"><br />
Hello iGEMers!<br />
<br><br />
I was also part of an iGEM team!<br />
<br><br />
In 2011 and 2012 my role was to design and create our team’s wiki. So wiki freeze was my major deadline. I am by no means an expert but let me share with you some of the things I learned with two wiki freezes under my belt.<br />
<br><br><br />
<b> 1.- Test your webpage layout: is information easy to find?</b> </br><br />
<p> I made the terrible mistake of not asking for a third party’s opinion about the layout of information on our site. It was obvious for me how things were laid out and organized. It wasn’t for the people evaluating us. <br><br />
Also, stick to the 3 click rule: content must reachable within 3 clicks so the user does not feel lost or confused. If someone wants to read your abstract, their path should be something like this (Menu –> Project –> Project Description -> Abstract)</p><br />
<br><br />
<b> 2.- Look at other teams’ code, see how they documented and what resources they used. </b><br><br />
<p> It is always good to get inspiration from other iGEM teams. See what you liked that they did and strive to improve! </p><br />
<br><br />
<b> 3.- Start working on your documentation early on. </b> <br><br />
<p>This was a good thing that we did; we created a common file that more than one person can edit at a time. Divide the documentation into smaller files and assign a team member to fully document that topic. In the end you will have a printable version of your project that you can share as a pdf file with other people!</p><br />
<br><br />
<br />
</td><br />
<br />
<td width="4%"></td><br />
<br />
<td width="48%" valign="top"><br />
<b> 4.- Name your images according to the project and keep them all in a folder on your computer. </b> <br><br />
<p> Sometimes naming your gel image “gelthingy_whyiamworkingat3am” sounds perfect at 3AM but later it may not be easy to know what or when that photograph was taken or that image created. <br><br />
Also, the iGEM database doesn’t know that you created that file so if someone names their file with the same name it can end up being replaced! Avoid using generic names like “banner.png” or “logo.jpg”.<br><br />
Try using your team’s name and the webpage where the image will appear, this helps you remember where to place it and reduce the risk of another team overwriting. “JoyUniversity_TeamBios_Richard.jpg” </p><br />
<br><br />
<b> 5.- Do not leave everything to the last minute! </b><br />
<br />
<p> Plan ahead. The last thing you want to be doing at 11:30PM the night of wiki freeze is uploading images. It is very stressful to be looking at the clock and hoping some kind of coding miracle helps you fix bugs faster. Plan to have everything online at least one week ahead so you can go enjoy a nice dinner with your team that night! </p><br />
<br />
<br />
<p> I hope this helps and if you have any questions, feel free to email me or send me a tweet! </p><br />
<i> ana at igem dot org </i><br />
<br><br />
<i> <A HREF="https://twitter.com/anita_sifuentes" > @anita_sifuentes </A> </i><br />
<br />
</td><br />
</tr><br />
</table><br />
<br /><br />
<br />
</html><br />
===Wiki Requirements===<br />
<html><br />
<h4>iGEM Logo</h4><br />
<p>All iGEM Team Wikis must include the iGEM logo at the top of the page and a visible link back to the iGEM 2014 Wiki Main Page in the header (or at the top of the page). All wiki pages must preserve the user editing menu (notifications, username, messages, history, edit). In the case where the user heading is not visible, an automatic heading will be overlaid on top of the wiki page(s) where the heading is missing. </p><br />
<h4>The iGEM Login Bar</h4><br />
<p>The iGEM Login Bar is a 20 pixel high, full-width menu bar that exists on all 2014.igem.org pages. It contains:<br />
<ul><br />
<li>wiki tools (edit, history, watch, etc.)</li><br />
<li>login</li><br />
</ul><br />
All iGEM 2014 Team Wikis are required to have the Login Bar. Please keep this in mind as you design your wiki.</p><br />
<h4>No Adobe Flash</h4> <br />
<p>Flash is not permitted on the iGEM 2014 wiki. Adobe flash is 100% proprietary and you cannot view the source like you can with our wiki. We chose wikis for teams to build their projects so the source code would be available for future teams, to build on the concept of open source. Flash can also be hosted on external sites and we want 100% of the content of our wikis to be on our wikis. </p> <br />
<h4>Upload to 2014.igem.org server</h4><br />
<p>All team pages, images, documents and code must be hosted on the <b>2014.igem.org</b> server. We preserve all iGEM content on our own servers so future teams can learn from what you have done. When you store content on your own sites or servers, after time, links might become broken, sites might go down, and information will be lost. <br /><br />
Additionally, hosting content outside of 2014.iGEM.org allows teams to change/add information to their wiki after the wiki freeze. Please note, that altering content after the wiki freeze is a <a href="https://2014.igem.org/Responsible_Conduct">form of cheating</a>.<br />
</p><br />
<h4>No iframes</h4> <br />
<p><b>iframes</b> are not permitted on the iGEM wiki. <br />
<ul>if an iframe was used to access content outside of <b>2014.igem.org</b><br />
<li>it would break when there was an issue with the outside server</li> <br />
<li>it would allow a team to show change/add content after the wiki freeze. Please note, that altering content after the wiki freeze is a <a href="https://2014.igem.org/Responsible_Conduct">form of cheating</a></li> <br />
</ul></p><br />
<h4>2014.igem.org/Team:Team_Name</h4><br />
<p>All iGEM 2014 teams are given a namespace on the iGEM 2014 wiki with their team name. Teams are allowed to create and edit pages within their respective team namespace. Teams are <b>not allowed</b> to create or edit pages belonging to another team's namespace.</p><br />
<h4>Wiki Freeze - October 17th</h4><br />
<p>The wiki freeze for the 2014 Giant Jamboree is on <a href="https://2014.igem.org/Calendar_of_Events">October 17th,</a> along with other deadlines. iGEM experiences higher than normal traffic on this day which can lead to strain on our servers and sessions timing out for users. iGEM HQ recommends that users do not wait till the last day to work/finish their wikis. <b>Once the wikis are frozen, users can no longer make any changes until they are unfrozen after the Jamboree.</b></p><br />
<h4>Other deadlines</h4><br />
<p>The team's project description must be documented on their iGEM Team Wiki by the deadline. The project description should be 1-3 paragraphs and only needs to include an up-to-date explanation of the project.</p><br />
<p>The team's wiki must include an attributions section.</p><br />
<br /><br /><br />
<br />
</html><br />
===Wiki Templates===<br />
<html><br />
<p> This year we have created a set of template pages that you may for your wiki! <BR> Feel free to edit them as much as you want </p><br />
<a href="https://2014.igem.org/WikitemplateA_home ">Wiki Template A </a></br><br />
<a href="https://2014.igem.org/WikitemplateB_home ">Wiki Template B </a><br />
<BR><BR><br />
<br />
<br />
<!--<br />
<br />
<h3>Wiki Freeze - October 17th</h3><br />
<p>The wiki freeze for the 2014 Giant Jamboree is on <a href="https://2014.igem.org/Calendar_of_Events">October 17th,</a> along with other deadlines. iGEM experiences higher than normal traffic on this day which can lead to strain on our servers and sessions timing out for users. <b>iGEM HQ recommends that users do not wait till the last day to work/finish their wikis.</b> Once the wikis are frozen, users can no longer make any changes until they are unfrozen after the Jamboree.</p><br />
<br />
<br /><br />
<br />
<h3>2014.igem.org/Team:Team_Name</h3><br />
<p>All iGEM 2014 teams are given a namespace on the iGEM 2014 wiki with their team name. Teams are allowed to create and edit pages within their respective team namespace. Teams are <b>not allowed</b> to create or edit pages belonging to another team's namespace.</p><br />
<br />
<br /><br />
<br />
<h3>Upload to 2014.igem.org server</h3><br />
<p>All team pages, images, documents and code must be hosted on the <b>2014.igem.org</b> server. We preserve all iGEM content on our own servers so future teams can learn from what you have done. When you store content on your own sites or servers, after time, links might become broken, sites might go down, and information will be lost.<br />
</p><br />
<br />
<ul>Use the <a href="https://2014.igem.org/Special:Upload">wiki upload tool</a> to upload your files. <br />
<li>Make sure to name your files clearly and uniquely: <i>File:</i><b>Team_Name_Flow_Cytometry_01.png</b>, instead of <i>File:</i><b>1.png</b></li><br />
</ul><br />
<br />
<h4>Upload to 2014.igem.org server</h4><br />
<p>When you store content on your own sites or servers, after time, links might become broken, sites might go down, and information will be lost.</p><br />
<br />
<br /><br />
<br />
<br />
<br />
<h3>No Adobe Flash</h3> <br />
<p>Flash is not permitted on the iGEM 2014 wiki. Adobe flash is 100% proprietary and you cannot view the source like you can with our wiki. We chose wikis for teams to build their projects so the source code would be available for future teams, to build on the concept of open source. Flash can also be hosted on external sites and we want 100% of the content of our wikis to be on our wikis. </p> <br />
<br />
<h3>Deadlines and the Wiki Freeze</h3><br />
<p>The team's project description must be documented on their iGEM Team Wiki by the deadline. The project description should be 1-3 paragraphs and only needs to include an up-to-date explanation of the project.</p><br />
<p>The team's wiki must include a link to the completed Safety form and an attributions section.</p><br />
<br />
<h3>iGEM Logo</h3><br />
<p>All iGEM Team Wikis must include the iGEM logo at the top of the page and a visible link back to the iGEM 2014 Wiki Main Page in the header (or at the top of the page). All wiki pages must preserve the user editing menu (notifications, username, messages, history, edit). In the case where the user heading is not visible, an automatic heading will be overlaid on top of the wiki page(s) where the heading is missing. </p><br />
<br />
<h3>The iGEM Login Bar</h3><br />
<p>The iGEM Login Bar is a 20 pixel high, full-width menu bar that exists on all 2014.igem.org pages. It contains:<br />
<ul><br />
<li>wiki tools (edit, history, watch, etc.)</li><br />
<li>login</li><br />
</ul><br />
All iGEM 2014 Team Wikis are required to have the Login Bar. Please keep this in mind as you design your wiki.</p><br />
<br />
--><br />
<br />
<br />
<br />
</div><br />
</html><br />
{{MainPage2014/Footer}}</div>Vinoohttp://2014.igem.org/Wiki_How-ToWiki How-To2014-10-10T14:14:54Z<p>Vinoo: </p>
<hr />
<div>{{CSS/Main}}<br />
{{NavBar}}<br />
<html><br />
<div id="contentcontainer"><br />
<br />
</html><br />
{{TOCright}}<br />
===Wiki Freeze - October 17th (11:59 PM -EDT)===<br />
<html><br />
<br />
<p>Your team's project must be documented on the iGEM 2014 wiki, the parts used in your project must be documented on the <a href="http://parts.igem.org">Registry of Standard Biological Parts</a>. You have the freedom to be creative, but a few specific rules apply:</p><br />
<br />
<br /><br />
<br /><br />
<br />
<br />
<style type="text/css"><br />
.simpleTable {<br />
cellspacing: 0;<br />
}<br />
.simpleTable th, .simpleTable td {<br />
padding: 10px 15px;<br />
}<br />
.simpleTable th {<br />
color: #fff;<br />
background-color: #333;<br />
font-style: italic;<br />
font-size: 14pt;<br />
}<br />
.simpleTable tr:nth-child(even) {<br />
background-color: #f0f0f0;<br />
}<br />
</style><br />
</html><br />
<br />
===Wiki Dos and Don'ts===<br />
<html><br />
<table class="simpleTable"><br />
<tr><br />
<th width="250px">Do</th><br />
<th width="250px">Don't</th><br />
<th width="460px">Why?</th><br />
</tr><br />
<tr><br />
<td>Make sure all wiki content, from pages to files, is hosted on <b>2014.igem.org</b></td><br />
<td>Don't host your wiki or parts of your wiki elsewhere</td><br />
<td>iGEM content is preserved on our servers so future teams can learn from what you've done. When content is stored on other sites/servers, links may become broken (<a href="https://static.igem.org/mediawiki/2014/d/d6/Wiki_server_example1.jpg" title="images were stored off-site, and became broken" target="_blank">example</a>), sites may go down, and <b>information will be lost.</b></td><br />
</tr><br />
<tr><br />
<td>Work on your wiki throughout the year and <b>save small edits for last</b></td><br />
<td>Don't wait to add/edit large portions of wiki content the day of the <b>Wiki Freeze</b></td><br />
<td>Just before the Wiki Freeze, iGEM websites experience <b>increased traffic and server loads.</b> This can be a difficult time to make larger changes or additions to your wiki. Don't wait till the last minute!</td><br />
</tr><br />
<tr><br />
<td>Name uploaded files clearly and uniquely (TeamName_Header.png)</td><br />
<td>Don't use generic names for you files (Header.png)</td><br />
<td>Using <b>unique names</b> makes searching/identification of uploaded files easier, and helps prevent files from being overwritten.</td><br />
</tr><br />
</table><br />
<br /><br /><br />
<br />
</html><br />
===Perspectives from an iGEM veteran===<br />
<html><br />
<table cellspacing="10" style="text-align: justify;" width="965px"><br />
<br />
<tr> <br />
<br />
<td width="48%"><br />
Hello iGEMers!<br />
<br><br />
I was also part of an iGEM team!<br />
<br><br />
In 2011 and 2012 my role was to design and create our team’s wiki. So wiki freeze was my major deadline. I am by no means an expert but let me share with you some of the things I learned with two wiki freezes under my belt.<br />
<br><br><br />
<b> 1.- Test your webpage layout: is information easy to find?</b> </br><br />
<p> I made the terrible mistake of not asking for a third party’s opinion about the layout of information on our site. It was obvious for me how things were laid out and organized. It wasn’t for the people evaluating us. <br><br />
Also, stick to the 3 click rule: content must reachable within 3 clicks so the user does not feel lost or confused. If someone wants to read your abstract, their path should be something like this (Menu –> Project –> Project Description -> Abstract)</p><br />
<br><br />
<b> 2.- Look at other teams’ code, see how they documented and what resources they used. </b><br><br />
<p> It is always good to get inspiration from other iGEM teams. See what you liked that they did and strive to improve! </p><br />
<br><br />
<b> 3.- Start working on your documentation early on. </b> <br><br />
<p>This was a good thing that we did; we created a common file that more than one person can edit at a time. Divide the documentation into smaller files and assign a team member to fully document that topic. In the end you will have a printable version of your project that you can share as a pdf file with other people!</p><br />
<br><br />
<br />
</td><br />
<br />
<td width="4%"></td><br />
<br />
<td width="48%" valign="top"><br />
<b> 4.- Name your images according to the project and keep them all in a folder on your computer. </b> <br><br />
<p> Sometimes naming your gel image “gelthingy_whyiamworkingat3am” sounds perfect at 3AM but later it may not be easy to know what or when that photograph was taken or that image created. <br><br />
Also, the iGEM database doesn’t know that you created that file so if someone names their file with the same name it can end up being replaced! Avoid using generic names like “banner.png” or “logo.jpg”.<br><br />
Try using your team’s name and the webpage where the image will appear, this helps you remember where to place it and reduce the risk of another team overwriting. “JoyUniversity_TeamBios_Richard.jpg” </p><br />
<br><br />
<b> 5.- Do not leave everything to the last minute! </b><br />
<br />
<p> Plan ahead. The last thing you want to be doing at 11:30PM the night of wiki freeze is uploading images. It is very stressful to be looking at the clock and hoping some kind of coding miracle helps you fix bugs faster. Plan to have everything online at least one week ahead so you can go enjoy a nice dinner with your team that night! </p><br />
<br />
<br />
<p> I hope this helps and if you have any questions, feel free to email me or send me a tweet! </p><br />
<i> ana at igem dot org </i><br />
<br><br />
<i> <A HREF="https://twitter.com/anita_sifuentes" > @anita_sifuentes </A> </i><br />
<br />
</td><br />
</tr><br />
</table><br />
<br /><br />
<br />
</html><br />
===Wiki Requirements===<br />
<html><br />
<h4>iGEM Logo</h4><br />
<p>All iGEM Team Wikis must include the iGEM logo at the top of the page and a visible link back to the iGEM 2014 Wiki Main Page in the header (or at the top of the page). All wiki pages must preserve the user editing menu (notifications, username, messages, history, edit). In the case where the user heading is not visible, an automatic heading will be overlaid on top of the wiki page(s) where the heading is missing. </p><br />
<h4>The iGEM Login Bar</h4><br />
<p>The iGEM Login Bar is a 20 pixel high, full-width menu bar that exists on all 2014.igem.org pages. It contains:<br />
<ul><br />
<li>wiki tools (edit, history, watch, etc.)</li><br />
<li>login</li><br />
</ul><br />
All iGEM 2014 Team Wikis are required to have the Login Bar. Please keep this in mind as you design your wiki.</p><br />
<h4>No Adobe Flash</h4> <br />
<p>Flash is not permitted on the iGEM 2014 wiki. Adobe flash is 100% proprietary and you cannot view the source like you can with our wiki. We chose wikis for teams to build their projects so the source code would be available for future teams, to build on the concept of open source. Flash can also be hosted on external sites and we want 100% of the content of our wikis to be on our wikis. </p> <br />
<h4>Upload to 2014.igem.org server</h4><br />
<p>All team pages, images, documents and code must be hosted on the <b>2014.igem.org</b> server. We preserve all iGEM content on our own servers so future teams can learn from what you have done. When you store content on your own sites or servers, after time, links might become broken, sites might go down, and information will be lost.<br />
</p><br />
<h4>No iframes</h4> <br />
<p>iframes are not permitted to access content outside of 2014.igem.org. Remember, all iGEM content must be hosted on 2014.igem.org! <br />
<ul>an iframe that accesses content outside of 2014.igem.org<br />
<li>would break when there was an issue with the outside server</li> <br />
<li>would allow a team to show change/add content after the wiki freeze</li> <br />
</ul></p><br />
<h4>2014.igem.org/Team:Team_Name</h4><br />
<p>All iGEM 2014 teams are given a namespace on the iGEM 2014 wiki with their team name. Teams are allowed to create and edit pages within their respective team namespace. Teams are <b>not allowed</b> to create or edit pages belonging to another team's namespace.</p><br />
<h4>Wiki Freeze - October 17th</h4><br />
<p>The wiki freeze for the 2014 Giant Jamboree is on <a href="https://2014.igem.org/Calendar_of_Events">October 17th,</a> along with other deadlines. iGEM experiences higher than normal traffic on this day which can lead to strain on our servers and sessions timing out for users. iGEM HQ recommends that users do not wait till the last day to work/finish their wikis. <b>Once the wikis are frozen, users can no longer make any changes until they are unfrozen after the Jamboree.</b></p><br />
<h4>Other deadlines</h4><br />
<p>The team's project description must be documented on their iGEM Team Wiki by the deadline. The project description should be 1-3 paragraphs and only needs to include an up-to-date explanation of the project.</p><br />
<p>The team's wiki must include an attributions section.</p><br />
<br /><br /><br />
<br />
</html><br />
===Wiki Templates===<br />
<html><br />
<p> This year we have created a set of template pages that you may for your wiki! <BR> Feel free to edit them as much as you want </p><br />
<a href="https://2014.igem.org/WikitemplateA_home ">Wiki Template A </a></br><br />
<a href="https://2014.igem.org/WikitemplateB_home ">Wiki Template B </a><br />
<BR><BR><br />
<br />
<br />
<!--<br />
<br />
<h3>Wiki Freeze - October 17th</h3><br />
<p>The wiki freeze for the 2014 Giant Jamboree is on <a href="https://2014.igem.org/Calendar_of_Events">October 17th,</a> along with other deadlines. iGEM experiences higher than normal traffic on this day which can lead to strain on our servers and sessions timing out for users. <b>iGEM HQ recommends that users do not wait till the last day to work/finish their wikis.</b> Once the wikis are frozen, users can no longer make any changes until they are unfrozen after the Jamboree.</p><br />
<br />
<br /><br />
<br />
<h3>2014.igem.org/Team:Team_Name</h3><br />
<p>All iGEM 2014 teams are given a namespace on the iGEM 2014 wiki with their team name. Teams are allowed to create and edit pages within their respective team namespace. Teams are <b>not allowed</b> to create or edit pages belonging to another team's namespace.</p><br />
<br />
<br /><br />
<br />
<h3>Upload to 2014.igem.org server</h3><br />
<p>All team pages, images, documents and code must be hosted on the <b>2014.igem.org</b> server. We preserve all iGEM content on our own servers so future teams can learn from what you have done. When you store content on your own sites or servers, after time, links might become broken, sites might go down, and information will be lost.<br />
</p><br />
<br />
<ul>Use the <a href="https://2014.igem.org/Special:Upload">wiki upload tool</a> to upload your files. <br />
<li>Make sure to name your files clearly and uniquely: <i>File:</i><b>Team_Name_Flow_Cytometry_01.png</b>, instead of <i>File:</i><b>1.png</b></li><br />
</ul><br />
<br />
<h4>Upload to 2014.igem.org server</h4><br />
<p>When you store content on your own sites or servers, after time, links might become broken, sites might go down, and information will be lost.</p><br />
<br />
<br /><br />
<br />
<br />
<br />
<h3>No Adobe Flash</h3> <br />
<p>Flash is not permitted on the iGEM 2014 wiki. Adobe flash is 100% proprietary and you cannot view the source like you can with our wiki. We chose wikis for teams to build their projects so the source code would be available for future teams, to build on the concept of open source. Flash can also be hosted on external sites and we want 100% of the content of our wikis to be on our wikis. </p> <br />
<br />
<h3>Deadlines and the Wiki Freeze</h3><br />
<p>The team's project description must be documented on their iGEM Team Wiki by the deadline. The project description should be 1-3 paragraphs and only needs to include an up-to-date explanation of the project.</p><br />
<p>The team's wiki must include a link to the completed Safety form and an attributions section.</p><br />
<br />
<h3>iGEM Logo</h3><br />
<p>All iGEM Team Wikis must include the iGEM logo at the top of the page and a visible link back to the iGEM 2014 Wiki Main Page in the header (or at the top of the page). All wiki pages must preserve the user editing menu (notifications, username, messages, history, edit). In the case where the user heading is not visible, an automatic heading will be overlaid on top of the wiki page(s) where the heading is missing. </p><br />
<br />
<h3>The iGEM Login Bar</h3><br />
<p>The iGEM Login Bar is a 20 pixel high, full-width menu bar that exists on all 2014.igem.org pages. It contains:<br />
<ul><br />
<li>wiki tools (edit, history, watch, etc.)</li><br />
<li>login</li><br />
</ul><br />
All iGEM 2014 Team Wikis are required to have the Login Bar. Please keep this in mind as you design your wiki.</p><br />
<br />
--><br />
<br />
<br />
<br />
</div><br />
</html><br />
{{MainPage2014/Footer}}</div>Vinoohttp://2014.igem.org/Calendar_of_EventsCalendar of Events2014-09-29T17:23:00Z<p>Vinoo: </p>
<hr />
<div>{{CSS/Main}}<br />
{{NavBar}}<br />
<html><br />
<div id="contentcontainer"></html><br />
===iGEM 2014 Calendar of Events===<br />
<br />
<p style="color:red;"> <b> '''Note:''' Make sure to check the calendar periodically for any changes!</b> </p><br />
<br />
{| style='margin-left:50px;' cellpadding='6px'<br />
|- <br />
|'''February 14'''|| iGEM 2014 registration opens<br />
|- <br />
|'''March 31'''|| iGEM 2014 registration closes; Team registration fee due <br />
|-<br />
|'''May'''|| DNA Distribution Kit sent to teams <br />
|-<br />
|'''May 01'''|| iGEM 2014 Late registration closes<br />
|-<br />
|'''May - September'''|| [https://2014.igem.org/Meetups Meet ups] taking place! <br />
|-<br />
|'''June - September'''|| [https://2014.igem.org/Safety_Hub#requirements Check-Ins] due before acquiring or using [https://2014.igem.org/Safety/White_List certain biological materials]<br />
|-<br />
|'''June 19'''|| [https://2014.igem.org/Safety_Hub#vooh Open Office Hours] -- ask safety questions, meet other iGEMers! (More office hours will be scheduled later in summer.)<br />
|-<br />
|'''June 23'''|| [https://2014.igem.org/Safety_Hub#requirements About our Lab form] due<br />
|-<br />
|'''June 28'''|| High School Jamboree<br />
|-<br />
|'''July 18 '''|| [https://2014.igem.org/Giant_Jamboree/Registration Giant Jamboree Registration] Opens<br />
|-<br />
|'''July 21'''||[https://2014.igem.org/Safety_Hub#requirements.safetyform Preliminary Safety forms] due<br />
|-<br />
|'''July 25 '''|| [https://2014.igem.org/Jamboree/Track_Selection Track selection] due<br />
|-<br />
|'''August 15'''|| [https://2014.igem.org/Project_descriptions Team project descriptions] due<br />
|-<br />
|'''August 30 '''|| [https://2014.igem.org/Jamboree/Title_and_Abstract Project titles and abstracts] due<br />
|-<br />
|'''September 01 ''' || [https://2014.igem.org/Safety_Hub#requirements Final Safety forms] due<br />
|-<br />
| || &nbsp;&nbsp;&nbsp;&nbsp;&nbsp; (*optional*) [https://2014.igem.org/Tracks/Measurement/Interlab_study Measurement Interlab Study Signup Deadline] at 11:59PM EDT<br />
|-<br />
|'''September 05'''|| [https://2014.igem.org/Giant_Jamboree/Attending/Registration Giant Jamboree attendance fee] due at 11:59PM EDT<br />
|-<br />
|<span style="color:red;">'''September 05''' </span>|| [https://2014.igem.org/Jamboree/Team_Roster Team rosters] due<br />
|-<br />
|September 19|| &nbsp;&nbsp;&nbsp;&nbsp;&nbsp; (*optional*) [https://2014.igem.org/Tracks/Measurement/Interlab_study Measurement Interlab Study Data] due at 11:59PM EDT<br />
|-<br />
|'''October 1'''|| Submit necessary [https://2014.igem.org/Safety_Hub#requirements.checkin Check-Ins] for materials you used before the Check-In Form was available<br />
|-<br />
|'''October 10 '''|| [http://parts.igem.org/cgi/dna_transfer/index.cgi BioBrick Part DNA due at the Registry] (parts must be received by this date for medal and awards eligibility) '''(Wetlab teams only)'''<br />
|-<br />
| || Project and part documentation due, including documentation for all medal criteria<br />
|- <br />
|'''October 17 '''|| [https://2014.igem.org/Jamboree/Judging_Forms Judging form] due<br />
|-<br />
| || Giant Jamboree wiki FREEZE at 11:59PM EDT<br />
|-<br />
| || Parts.igem.org wiki FREEZE at 11:59PM EDT<br />
|-<br />
| || Additional Part DNA due to the Registry (not required, however parts are not eligible for medals and awards)<br />
|-<br />
| || Judges Assignments distributed<br />
|-<br />
|}<br />
{| style='margin-left:50px;' cellpadding='6px;' <br />
|-<br />
|'''October 30 to Nov 3''' || [https://2014.igem.org/World_Championship_Jamboree iGEM 2014 Giant Jamboree], Hynes Convention Center, Boston, Massachusetts<br />
|-<br />
|}<br />
<br />
''Medal and awards criteria will be determined by the judging committee. When the criteria have been finalized, we will announce it on the main page!''<br />
<br />
<html><br />
</div><br />
</html><br />
<br />
{{MainPage2014/Footer}}</div>Vinoohttp://2014.igem.org/Wiki_How-ToWiki How-To2014-09-22T15:36:51Z<p>Vinoo: </p>
<hr />
<div>{{CSS/Main}}<br />
{{NavBar}}<br />
<html><br />
<div id="contentcontainer"><br />
<br />
</html><br />
{{TOCright}}<br />
===Wiki Freeze - October 17th (11:59 PM - EDT)===<br />
<html><br />
<br />
<p>Your team's project must be documented on the iGEM 2014 wiki, the parts used in your project must be documented on the <a href="http://parts.igem.org">Registry of Standard Biological Parts</a>. You have the freedom to be creative, but a few specific rules apply:</p><br />
<br />
<br /><br />
<br /><br />
<br />
<br />
<style type="text/css"><br />
.simpleTable {<br />
cellspacing: 0;<br />
}<br />
.simpleTable th, .simpleTable td {<br />
padding: 10px 15px;<br />
}<br />
.simpleTable th {<br />
color: #fff;<br />
background-color: #333;<br />
font-style: italic;<br />
font-size: 14pt;<br />
}<br />
.simpleTable tr:nth-child(even) {<br />
background-color: #f0f0f0;<br />
}<br />
</style><br />
</html><br />
===Wiki Dos and Don'ts===<br />
<html><br />
<table class="simpleTable"><br />
<tr><br />
<th width="250px">Do</th><br />
<th width="250px">Don't</th><br />
<th width="460px">Why?</th><br />
</tr><br />
<tr><br />
<td>Make sure all wiki content, from pages to files, is hosted on <b>2014.igem.org</b></td><br />
<td>Don't host your wiki or parts of your wiki elsewhere</td><br />
<td>iGEM content is preserved on our servers so future teams can learn from what you've done. When content is stored on other sites/servers, links may become broken (<a href="https://static.igem.org/mediawiki/2014/d/d6/Wiki_server_example1.jpg" title="images were stored off-site, and became broken" target="_blank">example</a>), sites may go down, and <b>information will be lost.</b></td><br />
</tr><br />
<tr><br />
<td>Work on your wiki throughout the year and <b>save small edits for last</b></td><br />
<td>Don't wait to add/edit large portions of wiki content the day of the <b>Wiki Freeze</b></td><br />
<td>Just before the Wiki Freeze, iGEM websites experience <b>increased traffic and server loads.</b> This can be a difficult time to make larger changes or additions to your wiki. Don't wait till the last minute!</td><br />
</tr><br />
<tr><br />
<td>Name uploaded files clearly and uniquely (TeamName_Header.png)</td><br />
<td>Don't use generic names for you files (Header.png)</td><br />
<td>Using <b>unique names</b> makes searching/identification of uploaded files easier, and helps prevent files from being overwritten.</td><br />
</tr><br />
</table><br />
<br /><br /><br />
<br />
</html><br />
===Perspectives from an iGEM veteran===<br />
<html><br />
<table cellspacing="10" style="text-align: justify;" width="965px"><br />
<br />
<tr> <br />
<br />
<td width="48%"><br />
Hello iGEMers!<br />
<br><br />
I was also part of an iGEM team!<br />
<br><br />
In 2011 and 2012 my role was to design and create our team’s wiki. So wiki freeze was my major deadline. I am by no means an expert but let me share with you some of the things I learned with two wiki freezes under my belt.<br />
<br><br><br />
<b> 1.- Test your webpage layout: is information easy to find?</b> </br><br />
<p> I made the terrible mistake of not asking for a third party’s opinion about the layout of information on our site. It was obvious for me how things were laid out and organized. It wasn’t for the people evaluating us. <br><br />
Also, stick to the 3 click rule: content must reachable within 3 clicks so the user does not feel lost or confused. If someone wants to read your abstract, their path should be something like this (Menu –> Project –> Project Description -> Abstract)</p><br />
<br><br />
<b> 2.- Look at other teams’ code, see how they documented and what resources they used. </b><br><br />
<p> It is always good to get inspiration from other iGEM teams. See what you liked that they did and strive to improve! </p><br />
<br><br />
<b> 3.- Start working on your documentation early on. </b> <br><br />
<p>This was a good thing that we did; we created a common file that more than one person can edit at a time. Divide the documentation into smaller files and assign a team member to fully document that topic. In the end you will have a printable version of your project that you can share as a pdf file with other people!</p><br />
<br><br />
<br />
</td><br />
<br />
<td width="4%"></td><br />
<br />
<td width="48%" valign="top"><br />
<b> 4.- Name your images according to the project and keep them all in a folder on your computer. </b> <br><br />
<p> Sometimes naming your gel image “gelthingy_whyiamworkingat3am” sounds perfect at 3AM but later it may not be easy to know what or when that photograph was taken or that image created. <br><br />
Also, the iGEM database doesn’t know that you created that file so if someone names their file with the same name it can end up being replaced! Avoid using generic names like “banner.png” or “logo.jpg”.<br><br />
Try using your team’s name and the webpage where the image will appear, this helps you remember where to place it and reduce the risk of another team overwriting. “JoyUniversity_TeamBios_Richard.jpg” </p><br />
<br><br />
<b> 5.- Do not leave everything to the last minute! </b><br />
<br />
<p> Plan ahead. The last thing you want to be doing at 11:30PM the night of wiki freeze is uploading images. It is very stressful to be looking at the clock and hoping some kind of coding miracle helps you fix bugs faster. Plan to have everything online at least one week ahead so you can go enjoy a nice dinner with your team that night! </p><br />
<br />
<br />
<p> I hope this helps and if you have any questions, feel free to email me or send me a tweet! </p><br />
<i> ana at igem dot org </i><br />
<br><br />
<i> <A HREF="https://twitter.com/anita_sifuentes" > @anita_sifuentes </A> </i><br />
<br />
</td><br />
</tr><br />
</table><br />
<br /><br />
<br />
</html><br />
===Wiki Requirements===<br />
<html><br />
<h4>iGEM Logo</h4><br />
<p>All iGEM Team Wikis must include the iGEM logo at the top of the page and a visible link back to the iGEM 2014 Wiki Main Page in the header (or at the top of the page). All wiki pages must preserve the user editing menu (notifications, username, messages, history, edit). In the case where the user heading is not visible, an automatic heading will be overlaid on top of the wiki page(s) where the heading is missing. </p><br />
<h4>The iGEM Login Bar</h4><br />
<p>The iGEM Login Bar is a 20 pixel high, full-width menu bar that exists on all 2014.igem.org pages. It contains:<br />
<ul><br />
<li>wiki tools (edit, history, watch, etc.)</li><br />
<li>login</li><br />
</ul><br />
All iGEM 2014 Team Wikis are required to have the Login Bar. Please keep this in mind as you design your wiki.</p><br />
<h4>No Adobe Flash</h4> <br />
<p>Flash is not permitted on the iGEM 2014 wiki. Adobe flash is 100% proprietary and you cannot view the source like you can with our wiki. We chose wikis for teams to build their projects so the source code would be available for future teams, to build on the concept of open source. Flash can also be hosted on external sites and we want 100% of the content of our wikis to be on our wikis. </p> <br />
<h4>Upload to 2014.igem.org server</h4><br />
<p>All team pages, images, documents and code must be hosted on the <b>2014.igem.org</b> server. We preserve all iGEM content on our own servers so future teams can learn from what you have done. When you store content on your own sites or servers, after time, links might become broken, sites might go down, and information will be lost.<br />
</p><br />
<h4>2014.igem.org/Team:Team_Name</h4><br />
<p>All iGEM 2014 teams are given a namespace on the iGEM 2014 wiki with their team name. Teams are allowed to create and edit pages within their respective team namespace. Teams are <b>not allowed</b> to create or edit pages belonging to another team's namespace.</p><br />
<h4>Wiki Freeze - October 17th</h4><br />
<p>The wiki freeze for the 2014 Giant Jamboree is on <a href="https://2014.igem.org/Calendar_of_Events">October 17th,</a> along with other deadlines. iGEM experiences higher than normal traffic on this day which can lead to strain on our servers and sessions timing out for users. iGEM HQ recommends that users do not wait till the last day to work/finish their wikis. <b>Once the wikis are frozen, users can no longer make any changes until they are unfrozen after the Jamboree.</b></p><br />
<h4>Other deadlines</h4><br />
<p>The team's project description must be documented on their iGEM Team Wiki by the deadline. The project description should be 1-3 paragraphs and only needs to include an up-to-date explanation of the project.</p><br />
<p>The team's wiki must include a link to the completed Safety form and an attributions section.</p><br />
<br /><br /><br />
<br />
</html><br />
===Wiki Templates===<br />
<html><br />
<p> This year we have created a set of template pages that you may for your wiki! <BR> Feel free to edit them as much as you want </p><br />
<a href="https://2014.igem.org/WikitemplateA_home ">Wiki Template A </a></br><br />
<a href="https://2014.igem.org/WikitemplateB_home ">Wiki Template B </a><br />
<BR><BR><br />
<br />
<br />
<!--<br />
<br />
<h3>Wiki Freeze - October 17th</h3><br />
<p>The wiki freeze for the 2014 Giant Jamboree is on <a href="https://2014.igem.org/Calendar_of_Events">October 17th,</a> along with other deadlines. iGEM experiences higher than normal traffic on this day which can lead to strain on our servers and sessions timing out for users. <b>iGEM HQ recommends that users do not wait till the last day to work/finish their wikis.</b> Once the wikis are frozen, users can no longer make any changes until they are unfrozen after the Jamboree.</p><br />
<br />
<br /><br />
<br />
<h3>2014.igem.org/Team:Team_Name</h3><br />
<p>All iGEM 2014 teams are given a namespace on the iGEM 2014 wiki with their team name. Teams are allowed to create and edit pages within their respective team namespace. Teams are <b>not allowed</b> to create or edit pages belonging to another team's namespace.</p><br />
<br />
<br /><br />
<br />
<h3>Upload to 2014.igem.org server</h3><br />
<p>All team pages, images, documents and code must be hosted on the <b>2014.igem.org</b> server. We preserve all iGEM content on our own servers so future teams can learn from what you have done. When you store content on your own sites or servers, after time, links might become broken, sites might go down, and information will be lost.<br />
</p><br />
<br />
<ul>Use the <a href="https://2014.igem.org/Special:Upload">wiki upload tool</a> to upload your files. <br />
<li>Make sure to name your files clearly and uniquely: <i>File:</i><b>Team_Name_Flow_Cytometry_01.png</b>, instead of <i>File:</i><b>1.png</b></li><br />
</ul><br />
<br />
<h4>Upload to 2014.igem.org server</h4><br />
<p>When you store content on your own sites or servers, after time, links might become broken, sites might go down, and information will be lost.</p><br />
<br />
<br /><br />
<br />
<h3>No Adobe Flash</h3> <br />
<p>Flash is not permitted on the iGEM 2014 wiki. Adobe flash is 100% proprietary and you cannot view the source like you can with our wiki. We chose wikis for teams to build their projects so the source code would be available for future teams, to build on the concept of open source. Flash can also be hosted on external sites and we want 100% of the content of our wikis to be on our wikis. </p> <br />
<br />
<h3>Deadlines and the Wiki Freeze</h3><br />
<p>The team's project description must be documented on their iGEM Team Wiki by the deadline. The project description should be 1-3 paragraphs and only needs to include an up-to-date explanation of the project.</p><br />
<p>The team's wiki must include a link to the completed Safety form and an attributions section.</p><br />
<br />
<h3>iGEM Logo</h3><br />
<p>All iGEM Team Wikis must include the iGEM logo at the top of the page and a visible link back to the iGEM 2014 Wiki Main Page in the header (or at the top of the page). All wiki pages must preserve the user editing menu (notifications, username, messages, history, edit). In the case where the user heading is not visible, an automatic heading will be overlaid on top of the wiki page(s) where the heading is missing. </p><br />
<br />
<h3>The iGEM Login Bar</h3><br />
<p>The iGEM Login Bar is a 20 pixel high, full-width menu bar that exists on all 2014.igem.org pages. It contains:<br />
<ul><br />
<li>wiki tools (edit, history, watch, etc.)</li><br />
<li>login</li><br />
</ul><br />
All iGEM 2014 Team Wikis are required to have the Login Bar. Please keep this in mind as you design your wiki.</p><br />
<br />
--><br />
<br />
<br />
<br />
</div><br />
</html><br />
{{MainPage2014/Footer}}</div>Vinoohttp://2014.igem.org/Wiki_How-ToWiki How-To2014-09-22T15:07:53Z<p>Vinoo: </p>
<hr />
<div>{{CSS/Main}}<br />
{{NavBar}}<br />
<html><br />
<div id="contentcontainer"><br />
<br />
<h3>Wiki Freeze - October 17th (11:59 PM - EDT) </h3><br />
<br />
<p>Your team's project must be documented on the iGEM 2014 wiki, the parts used in your project must be documented on the <a href="http://parts.igem.org">Registry of Standard Biological Parts</a>. You have the freedom to be creative, but a few specific rules apply:</p><br />
<br />
<br /><br />
<br /><br />
<br />
<br />
<style type="text/css"><br />
.simpleTable {<br />
cellspacing: 0;<br />
}<br />
.simpleTable th, .simpleTable td {<br />
padding: 10px 15px;<br />
}<br />
.simpleTable th {<br />
color: #fff;<br />
background-color: #333;<br />
font-style: italic;<br />
font-size: 14pt;<br />
}<br />
.simpleTable tr:nth-child(even) {<br />
background-color: #f0f0f0;<br />
}<br />
</style><br />
<h3>Wiki Dos and Don'ts</h4><br />
<table class="simpleTable"><br />
<tr><br />
<th width="250px">Do</th><br />
<th width="250px">Don't</th><br />
<th width="460px">Why?</th><br />
</tr><br />
<tr><br />
<td>Make sure all wiki content, from pages to files, is hosted on <b>2014.igem.org</b></td><br />
<td>Don't host your wiki or parts of your wiki elsewhere</td><br />
<td>iGEM content is preserved on our servers so future teams can learn from what you've done. When content is stored on other sites/servers, links may become broken (<a href="https://static.igem.org/mediawiki/2014/d/d6/Wiki_server_example1.jpg" title="images were stored off-site, and became broken" target="_blank">example</a>), sites may go down, and <b>information will be lost.</b></td><br />
</tr><br />
<tr><br />
<td>Work on your wiki throughout the year and <b>save small edits for last</b></td><br />
<td>Don't wait to add/edit large portions of wiki content the day of the <b>Wiki Freeze</b></td><br />
<td>Just before the Wiki Freeze, iGEM websites experience <b>increased traffic and server loads.</b> This can be a difficult time to make larger changes or additions to your wiki. Don't wait till the last minute!</td><br />
</tr><br />
<tr><br />
<td>Name uploaded files clearly and uniquely (TeamName_Header.png)</td><br />
<td>Don't use generic names for you files (Header.png)</td><br />
<td>Using <b>unique names</b> makes searching/identification of uploaded files easier, and helps prevent files from being overwritten.</td><br />
</tr><br />
</table><br />
<br /><br /><br />
<br />
<h3> Perspectives from an iGEM veteran. </h4><br />
<table cellspacing="10" style="text-align: justify;" width="965px"><br />
<br />
<tr> <br />
<br />
<td width="48%"><br />
Hello iGEMers!<br />
<br><br />
I was also part of an iGEM team!<br />
<br><br />
In 2011 and 2012 my role was to design and create our team’s wiki. So wiki freeze was my major deadline. I am by no means an expert but let me share with you some of the things I learned with two wiki freezes under my belt.<br />
<br><br><br />
<b> 1.- Test your webpage layout: is information easy to find?</b> </br><br />
<p> I made the terrible mistake of not asking for a third party’s opinion about the layout of information on our site. It was obvious for me how things were laid out and organized. It wasn’t for the people evaluating us. <br><br />
Also, stick to the 3 click rule: content must reachable within 3 clicks so the user does not feel lost or confused. If someone wants to read your abstract, their path should be something like this (Menu –> Project –> Project Description -> Abstract)</p><br />
<br><br />
<b> 2.- Look at other teams’ code, see how they documented and what resources they used. </b><br><br />
<p> It is always good to get inspiration from other iGEM teams. See what you liked that they did and strive to improve! </p><br />
<br><br />
<b> 3.- Start working on your documentation early on. </b> <br><br />
<p>This was a good thing that we did; we created a common file that more than one person can edit at a time. Divide the documentation into smaller files and assign a team member to fully document that topic. In the end you will have a printable version of your project that you can share as a pdf file with other people!</p><br />
<br><br />
<br />
</td><br />
<br />
<td width="4%"></td><br />
<br />
<td width="48%" valign="top"><br />
<b> 4.- Name your images according to the project and keep them all in a folder on your computer. </b> <br><br />
<p> Sometimes naming your gel image “gelthingy_whyiamworkingat3am” sounds perfect at 3AM but later it may not be easy to know what or when that photograph was taken or that image created. <br><br />
Also, the iGEM database doesn’t know that you created that file so if someone names their file with the same name it can end up being replaced! Avoid using generic names like “banner.png” or “logo.jpg”.<br><br />
Try using your team’s name and the webpage where the image will appear, this helps you remember where to place it and reduce the risk of another team overwriting. “JoyUniversity_TeamBios_Richard.jpg” </p><br />
<br><br />
<b> 5.- Do not leave everything to the last minute! </b><br />
<br />
<p> Plan ahead. The last thing you want to be doing at 11:30PM the night of wiki freeze is uploading images. It is very stressful to be looking at the clock and hoping some kind of coding miracle helps you fix bugs faster. Plan to have everything online at least one week ahead so you can go enjoy a nice dinner with your team that night! </p><br />
<br />
<br />
<p> I hope this helps and if you have any questions, feel free to email me or send me a tweet! </p><br />
<i> ana at igem dot org </i><br />
<br><br />
<i> <A HREF="https://twitter.com/anita_sifuentes" > @anita_sifuentes </A> </i><br />
<br />
</td><br />
</tr><br />
</table><br />
<br /><br />
<br />
<h3>Wiki Requirements</h4><br />
<h4>iGEM Logo</h4><br />
<p>All iGEM Team Wikis must include the iGEM logo at the top of the page and a visible link back to the iGEM 2014 Wiki Main Page in the header (or at the top of the page). All wiki pages must preserve the user editing menu (notifications, username, messages, history, edit). In the case where the user heading is not visible, an automatic heading will be overlaid on top of the wiki page(s) where the heading is missing. </p><br />
<h4>The iGEM Login Bar</h4><br />
<p>The iGEM Login Bar is a 20 pixel high, full-width menu bar that exists on all 2014.igem.org pages. It contains:<br />
<ul><br />
<li>wiki tools (edit, history, watch, etc.)</li><br />
<li>login</li><br />
</ul><br />
All iGEM 2014 Team Wikis are required to have the Login Bar. Please keep this in mind as you design your wiki.</p><br />
<h4>No Adobe Flash</h4> <br />
<p>Flash is not permitted on the iGEM 2014 wiki. Adobe flash is 100% proprietary and you cannot view the source like you can with our wiki. We chose wikis for teams to build their projects so the source code would be available for future teams, to build on the concept of open source. Flash can also be hosted on external sites and we want 100% of the content of our wikis to be on our wikis. </p> <br />
<h4>Upload to 2014.igem.org server</h4><br />
<p>All team pages, images, documents and code must be hosted on the <b>2014.igem.org</b> server. We preserve all iGEM content on our own servers so future teams can learn from what you have done. When you store content on your own sites or servers, after time, links might become broken, sites might go down, and information will be lost.<br />
</p><br />
<h4>2014.igem.org/Team:Team_Name</h4><br />
<p>All iGEM 2014 teams are given a namespace on the iGEM 2014 wiki with their team name. Teams are allowed to create and edit pages within their respective team namespace. Teams are <b>not allowed</b> to create or edit pages belonging to another team's namespace.</p><br />
<h4>Wiki Freeze - October 17th</h4><br />
<p>The wiki freeze for the 2014 Giant Jamboree is on <a href="https://2014.igem.org/Calendar_of_Events">October 17th,</a> along with other deadlines. iGEM experiences higher than normal traffic on this day which can lead to strain on our servers and sessions timing out for users. iGEM HQ recommends that users do not wait till the last day to work/finish their wikis. <b>Once the wikis are frozen, users can no longer make any changes until they are unfrozen after the Jamboree.</b></p><br />
<h4>Other deadlines</h4><br />
<p>The team's project description must be documented on their iGEM Team Wiki by the deadline. The project description should be 1-3 paragraphs and only needs to include an up-to-date explanation of the project.</p><br />
<p>The team's wiki must include a link to the completed Safety form and an attributions section.</p><br />
<br /><br /><br />
<br />
<h3 id="wikitemplates"> Wiki Templates </h4><br />
<p> This year we have created a set of template pages that you may for your wiki! <BR> Feel free to edit them as much as you want </p><br />
<a href="https://2014.igem.org/WikitemplateA_home ">Wiki Template A </a></br><br />
<a href="https://2014.igem.org/WikitemplateB_home ">Wiki Template B </a><br />
<BR><BR><br />
<br />
<br />
<!--<br />
<br />
<h3>Wiki Freeze - October 17th</h3><br />
<p>The wiki freeze for the 2014 Giant Jamboree is on <a href="https://2014.igem.org/Calendar_of_Events">October 17th,</a> along with other deadlines. iGEM experiences higher than normal traffic on this day which can lead to strain on our servers and sessions timing out for users. <b>iGEM HQ recommends that users do not wait till the last day to work/finish their wikis.</b> Once the wikis are frozen, users can no longer make any changes until they are unfrozen after the Jamboree.</p><br />
<br />
<br /><br />
<br />
<h3>2014.igem.org/Team:Team_Name</h3><br />
<p>All iGEM 2014 teams are given a namespace on the iGEM 2014 wiki with their team name. Teams are allowed to create and edit pages within their respective team namespace. Teams are <b>not allowed</b> to create or edit pages belonging to another team's namespace.</p><br />
<br />
<br /><br />
<br />
<h3>Upload to 2014.igem.org server</h3><br />
<p>All team pages, images, documents and code must be hosted on the <b>2014.igem.org</b> server. We preserve all iGEM content on our own servers so future teams can learn from what you have done. When you store content on your own sites or servers, after time, links might become broken, sites might go down, and information will be lost.<br />
</p><br />
<br />
<ul>Use the <a href="https://2014.igem.org/Special:Upload">wiki upload tool</a> to upload your files. <br />
<li>Make sure to name your files clearly and uniquely: <i>File:</i><b>Team_Name_Flow_Cytometry_01.png</b>, instead of <i>File:</i><b>1.png</b></li><br />
</ul><br />
<br />
<h4>Upload to 2014.igem.org server</h4><br />
<p>When you store content on your own sites or servers, after time, links might become broken, sites might go down, and information will be lost.</p><br />
<br />
<br /><br />
<br />
<h3>No Adobe Flash</h3> <br />
<p>Flash is not permitted on the iGEM 2014 wiki. Adobe flash is 100% proprietary and you cannot view the source like you can with our wiki. We chose wikis for teams to build their projects so the source code would be available for future teams, to build on the concept of open source. Flash can also be hosted on external sites and we want 100% of the content of our wikis to be on our wikis. </p> <br />
<br />
<h3>Deadlines and the Wiki Freeze</h3><br />
<p>The team's project description must be documented on their iGEM Team Wiki by the deadline. The project description should be 1-3 paragraphs and only needs to include an up-to-date explanation of the project.</p><br />
<p>The team's wiki must include a link to the completed Safety form and an attributions section.</p><br />
<br />
<h3>iGEM Logo</h3><br />
<p>All iGEM Team Wikis must include the iGEM logo at the top of the page and a visible link back to the iGEM 2014 Wiki Main Page in the header (or at the top of the page). All wiki pages must preserve the user editing menu (notifications, username, messages, history, edit). In the case where the user heading is not visible, an automatic heading will be overlaid on top of the wiki page(s) where the heading is missing. </p><br />
<br />
<h3>The iGEM Login Bar</h3><br />
<p>The iGEM Login Bar is a 20 pixel high, full-width menu bar that exists on all 2014.igem.org pages. It contains:<br />
<ul><br />
<li>wiki tools (edit, history, watch, etc.)</li><br />
<li>login</li><br />
</ul><br />
All iGEM 2014 Team Wikis are required to have the Login Bar. Please keep this in mind as you design your wiki.</p><br />
<br />
--><br />
<br />
<br />
<br />
</div><br />
</html><br />
{{MainPage2014/Footer}}</div>Vinoohttp://2014.igem.org/Wiki_How-ToWiki How-To2014-09-22T14:47:22Z<p>Vinoo: </p>
<hr />
<div>{{CSS/Main}}<br />
{{NavBar}}<br />
<html><br />
<div id="contentcontainer"><br />
<br />
<h3>Wiki Freeze - October 17th (11:59 PM - EDT) </h3><br />
<br />
<p>Your team's project must be documented on the iGEM 2014 wiki, the parts used in your project must be documented on the <a href="http://parts.igem.org">Registry of Standard Biological Parts</a>. You have the freedom to be creative, but a few specific rules apply:</p><br />
<br />
<br /><br />
<br />
<br />
<br />
<br />
<h4 id="wikitemplates"> Wiki Templates </h4><br />
<p> This year we have created a set of template pages that you may for your wiki! <BR> Feel free to edit them as much as you want </p><br />
<a href="https://2014.igem.org/WikitemplateA_home ">Wiki Template A </a></br><br />
<a href="https://2014.igem.org/WikitemplateB_home ">Wiki Template B </a><br />
<BR><BR><br />
<br />
<style type="text/css"><br />
.simpleTable {<br />
cellspacing: 0;<br />
}<br />
.simpleTable th, .simpleTable td {<br />
padding: 10px 15px;<br />
}<br />
.simpleTable th {<br />
color: #fff;<br />
background-color: #333;<br />
font-style: italic;<br />
font-size: 14pt;<br />
}<br />
.simpleTable tr:nth-child(even) {<br />
background-color: #f0f0f0;<br />
}<br />
</style><br />
<h4>Wiki Dos and Don'ts</h4><br />
<table class="simpleTable"><br />
<tr><br />
<th width="250px">Do</th><br />
<th width="250px">Don't</th><br />
<th width="460px">Why?</th><br />
</tr><br />
<tr><br />
<td>Make sure all wiki content, from pages to files, is hosted on <b>2014.igem.org</b></td><br />
<td>Don't host your wiki or parts of your wiki elsewhere</td><br />
<td>iGEM content is preserved on our servers so future teams can learn from what you've done. When content is stored on other sites/servers, links may become broken (<a href="https://static.igem.org/mediawiki/2014/d/d6/Wiki_server_example1.jpg" title="images were stored off-site, and became broken" target="_blank">example</a>), sites may go down, and <b>information will be lost.</b></td><br />
</tr><br />
<tr><br />
<td>Work on your wiki throughout the year and <b>save small edits for last</b></td><br />
<td>Don't wait to add/edit large portions of wiki content the day of the <b>Wiki Freeze</b></td><br />
<td>Just before the Wiki Freeze, iGEM websites experience <b>increased traffic and server loads.</b> This can be a difficult time to make larger changes or additions to your wiki. Don't wait till the last minute!</td><br />
</tr><br />
<tr><br />
<td>Name uploaded files clearly and uniquely (TeamName_Header.png)</td><br />
<td>Don't use generic names for you files (Header.png)</td><br />
<td>Using <b>unique names</b> makes searching/identification of uploaded files easier, and helps prevent files from being overwritten.</td><br />
</tr><br />
</table><br />
<br /><br /><br />
<br />
<h4> Perspectives from an iGEM veteran. </h4><br />
<br />
<br />
<br />
<br />
<table cellspacing="10" style="text-align: justify;" width="965px"><br />
<br />
<tr> <br />
<br />
<td width="48%"><br />
Hello iGEMers!<br />
<br><br />
I was also part of an iGEM team!<br />
<br><br />
In 2011 and 2012 my role was to design and create our team’s wiki. So wiki freeze was my major deadline. I am by no means an expert but let me share with you some of the things I learned with two wiki freezes under my belt.<br />
<br><br><br />
<b> 1.- Test your webpage layout: is information easy to find?</b> </br><br />
<p> I made the terrible mistake of not asking for a third party’s opinion about the layout of information on our site. It was obvious for me how things were laid out and organized. It wasn’t for the people evaluating us. <br><br />
Also, stick to the 3 click rule: content must reachable within 3 clicks so the user does not feel lost or confused. If someone wants to read your abstract, their path should be something like this (Menu –> Project –> Project Description -> Abstract)</p><br />
<br><br />
<b> 2.- Look at other teams’ code, see how they documented and what resources they used. </b><br><br />
<p> It is always good to get inspiration from other iGEM teams. See what you liked that they did and strive to improve! </p><br />
<br><br />
<b> 3.- Start working on your documentation early on. </b> <br><br />
<p>This was a good thing that we did; we created a common file that more than one person can edit at a time. Divide the documentation into smaller files and assign a team member to fully document that topic. In the end you will have a printable version of your project that you can share as a pdf file with other people!</p><br />
<br><br />
<br />
</td><br />
<br />
<td width="4%"></td><br />
<br />
<td width="48%" valign="top"><br />
<b> 4.- Name your images according to the project and keep them all in a folder on your computer. </b> <br><br />
<p> Sometimes naming your gel image “gelthingy_whyiamworkingat3am” sounds perfect at 3AM but later it may not be easy to know what or when that photograph was taken or that image created. <br><br />
Also, the iGEM database doesn’t know that you created that file so if someone names their file with the same name it can end up being replaced! Avoid using generic names like “banner.png” or “logo.jpg”.<br><br />
Try using your team’s name and the webpage where the image will appear, this helps you remember where to place it and reduce the risk of another team overwriting. “JoyUniversity_TeamBios_Richard.jpg” </p><br />
<br><br />
<b> 5.- Do not leave everything to the last minute! </b><br />
<br />
<p> Plan ahead. The last thing you want to be doing at 11:30PM the night of wiki freeze is uploading images. It is very stressful to be looking at the clock and hoping some kind of coding miracle helps you fix bugs faster. Plan to have everything online at least one week ahead so you can go enjoy a nice dinner with your team that night! </p><br />
<br />
<br />
<p> I hope this helps and if you have any questions, feel free to email me or send me a tweet! </p><br />
<i> ana at igem dot org </i><br />
<br><br />
<i> <A HREF="https://twitter.com/anita_sifuentes" > @anita_sifuentes </A> </i><br />
<br />
</td><br />
</tr><br />
</table><br />
<br />
<br />
<!--<br />
<br />
<h3>Wiki Freeze - October 17th</h3><br />
<p>The wiki freeze for the 2014 Giant Jamboree is on <a href="https://2014.igem.org/Calendar_of_Events">October 17th,</a> along with other deadlines. iGEM experiences higher than normal traffic on this day which can lead to strain on our servers and sessions timing out for users. <b>iGEM HQ recommends that users do not wait till the last day to work/finish their wikis.</b> Once the wikis are frozen, users can no longer make any changes until they are unfrozen after the Jamboree.</p><br />
<ul><b>Do not...</b><br />
<li>wait till the last minute</li><br />
<li>try to upload everything at once</li><br />
</ul><br />
<br />
<br /><br />
<br />
<h3>2014.igem.org/Team:Team_Name</h3><br />
<p>All iGEM 2014 teams are given a namespace on the iGEM 2014 wiki with their team name. Teams are allowed to create and edit pages within their respective team namespace. Teams are <b>not allowed</b> to create or edit pages belonging to another team's namespace.</p><br />
<br />
<br /><br />
<br />
<h3>Upload to 2014.igem.org server</h3><br />
<p>All team pages, images, documents and code must be hosted on the <b>2014.igem.org</b> server. We preserve all iGEM content on our own servers so future teams can learn from what you have done. When you store content on your own sites or servers, after time, links might become broken, sites might go down, and information will be lost.<br />
</p><br />
<br />
<ul>Use the <a href="https://2014.igem.org/Special:Upload">wiki upload tool</a> to upload your files. <br />
<li>Make sure to name your files clearly and uniquely: <i>File:</i><b>Team_Name_Flow_Cytometry_01.png</b>, instead of <i>File:</i><b>1.png</b></li><br />
</ul><br />
<br />
<h4>Upload to 2014.igem.org server</h4><br />
<p>When you store content on your own sites or servers, after time, links might become broken, sites might go down, and information will be lost.</p><br />
<br />
<br /><br />
<br />
<h3>No Adobe Flash</h3> <br />
<p>Flash is not permitted on the iGEM 2014 wiki. Adobe flash is 100% proprietary and you cannot view the source like you can with our wiki. We chose wikis for teams to build their projects so the source code would be available for future teams, to build on the concept of open source. Flash can also be hosted on external sites and we want 100% of the content of our wikis to be on our wikis. </p> <br />
<br />
<h3>Deadlines and the Wiki Freeze</h3><br />
<p>The team's project description must be documented on their iGEM Team Wiki by the deadline. The project description should be 1-3 paragraphs and only needs to include an up-to-date explanation of the project.</p><br />
<p>The team's wiki must include a link to the completed Safety form and an attributions section.</p><br />
<br />
<h3>iGEM Logo</h3><br />
<p>All iGEM Team Wikis must include the iGEM logo at the top of the page and a visible link back to the iGEM 2014 Wiki Main Page in the header (or at the top of the page). All wiki pages must preserve the user editing menu (notifications, username, messages, history, edit). In the case where the user heading is not visible, an automatic heading will be overlaid on top of the wiki page(s) where the heading is missing. </p><br />
<br />
<h3>The iGEM Login Bar</h3><br />
<p>The iGEM Login Bar is a 20 pixel high, full-width menu bar that exists on all 2014.igem.org pages. It contains:<br />
<ul><br />
<li>wiki tools (edit, history, watch, etc.)</li><br />
<li>login</li><br />
</ul><br />
All iGEM 2014 Team Wikis are required to have the Login Bar. Please keep this in mind as you design your wiki.</p><br />
<br />
--><br />
<br />
<br />
<br />
</div><br />
</html><br />
{{MainPage2014/Footer}}</div>Vinoohttp://2014.igem.org/Wiki_How-ToWiki How-To2014-09-22T14:46:07Z<p>Vinoo: </p>
<hr />
<div>{{CSS/Main}}<br />
{{NavBar}}<br />
<html><br />
<div id="contentcontainer"><br />
<br />
<h3>Wiki Freeze - October 17th (11:59 PM - EDT) </h3><br />
<br />
<p>Your team's project must be documented on the iGEM 2014 wiki, the parts used in your project must be documented on the <a href="http://parts.igem.org">Registry of Standard Biological Parts</a>. You have the freedom to be creative, but a few specific rules apply:</p><br />
<br />
<br /><br />
<br />
<br />
<br />
<br />
<h4 id="wikitemplates"> Wiki Templates </h4><br />
<p> This year we have created a set of template pages that you may for your wiki! <BR> Feel free to edit them as much as you want </p><br />
<a href="https://2014.igem.org/WikitemplateA_home ">Wiki Template A </a></br><br />
<a href="https://2014.igem.org/WikitemplateB_home ">Wiki Template B </a><br />
<BR><BR><br />
<br />
<style type="text/css"><br />
.simpleTable {<br />
cellspacing: 0;<br />
}<br />
.simpleTable th, .simpleTable td {<br />
padding: 10px 15px;<br />
}<br />
.simpleTable th {<br />
color: #fff;<br />
background-color: #333;<br />
font-style: italic;<br />
font-size: 14pt;<br />
}<br />
.simpleTable tr:nth-child(even) {<br />
background-color: #f0f0f0;<br />
}<br />
</style><br />
<h4>Wiki Dos and Don'ts</h4><br />
<table class="simpleTable"><br />
<tr><br />
<th width="250px">Do</th><br />
<th width="250px">Don't</th><br />
<th width="460px">Why?</th><br />
</tr><br />
<tr><br />
<td>Make sure all wiki content, from pages to files, is hosted on <b>2014.igem.org</b></td><br />
<td>Don't host your wiki or parts of your wiki elsewhere</td><br />
<td>iGEM content is preserved on our servers so future teams can learn from what you've done. When content is stored on other sites/servers, links may become broken (<a href="https://static.igem.org/mediawiki/2014/d/d6/Wiki_server_example1.jpg" target="_blank">example</a>), sites may go down, and <b>information will be lost.</b></td><br />
</tr><br />
<tr><br />
<td>Work on your wiki throughout the year and <b>save small edits for last</b></td><br />
<td>Don't wait to add/edit large portions of wiki content the day of the <b>Wiki Freeze</b></td><br />
<td>Just before the Wiki Freeze, iGEM websites experience <b>increased traffic and server loads.</b> This can be a difficult time to make larger changes or additions to your wiki. Don't wait till the last minute!</td><br />
</tr><br />
<tr><br />
<td>Name uploaded files clearly and uniquely (TeamName_Header.png)</td><br />
<td>Don't use generic names for you files (Header.png)</td><br />
<td>Using <b>unique names</b> makes searching/identification of uploaded files easier, and helps prevent files from being overwritten.</td><br />
</tr><br />
</table><br />
<br /><br /><br />
<br />
<h4> Perspectives from an iGEM veteran. </h4><br />
<br />
<br />
<br />
<br />
<table cellspacing="10" style="text-align: justify;" width="965px"><br />
<br />
<tr> <br />
<br />
<td width="48%"><br />
Hello iGEMers!<br />
<br><br />
I was also part of an iGEM team!<br />
<br><br />
In 2011 and 2012 my role was to design and create our team’s wiki. So wiki freeze was my major deadline. I am by no means an expert but let me share with you some of the things I learned with two wiki freezes under my belt.<br />
<br><br><br />
<b> 1.- Test your webpage layout: is information easy to find?</b> </br><br />
<p> I made the terrible mistake of not asking for a third party’s opinion about the layout of information on our site. It was obvious for me how things were laid out and organized. It wasn’t for the people evaluating us. <br><br />
Also, stick to the 3 click rule: content must reachable within 3 clicks so the user does not feel lost or confused. If someone wants to read your abstract, their path should be something like this (Menu –> Project –> Project Description -> Abstract)</p><br />
<br><br />
<b> 2.- Look at other teams’ code, see how they documented and what resources they used. </b><br><br />
<p> It is always good to get inspiration from other iGEM teams. See what you liked that they did and strive to improve! </p><br />
<br><br />
<b> 3.- Start working on your documentation early on. </b> <br><br />
<p>This was a good thing that we did; we created a common file that more than one person can edit at a time. Divide the documentation into smaller files and assign a team member to fully document that topic. In the end you will have a printable version of your project that you can share as a pdf file with other people!</p><br />
<br><br />
<br />
</td><br />
<br />
<td width="4%"></td><br />
<br />
<td width="48%" valign="top"><br />
<b> 4.- Name your images according to the project and keep them all in a folder on your computer. </b> <br><br />
<p> Sometimes naming your gel image “gelthingy_whyiamworkingat3am” sounds perfect at 3AM but later it may not be easy to know what or when that photograph was taken or that image created. <br><br />
Also, the iGEM database doesn’t know that you created that file so if someone names their file with the same name it can end up being replaced! Avoid using generic names like “banner.png” or “logo.jpg”.<br><br />
Try using your team’s name and the webpage where the image will appear, this helps you remember where to place it and reduce the risk of another team overwriting. “JoyUniversity_TeamBios_Richard.jpg” </p><br />
<br><br />
<b> 5.- Do not leave everything to the last minute! </b><br />
<br />
<p> Plan ahead. The last thing you want to be doing at 11:30PM the night of wiki freeze is uploading images. It is very stressful to be looking at the clock and hoping some kind of coding miracle helps you fix bugs faster. Plan to have everything online at least one week ahead so you can go enjoy a nice dinner with your team that night! </p><br />
<br />
<br />
<p> I hope this helps and if you have any questions, feel free to email me or send me a tweet! </p><br />
<i> ana at igem dot org </i><br />
<br><br />
<i> <A HREF="https://twitter.com/anita_sifuentes" > @anita_sifuentes </A> </i><br />
<br />
</td><br />
</tr><br />
</table><br />
<br />
<br />
<!--<br />
<br />
<h3>Wiki Freeze - October 17th</h3><br />
<p>The wiki freeze for the 2014 Giant Jamboree is on <a href="https://2014.igem.org/Calendar_of_Events">October 17th,</a> along with other deadlines. iGEM experiences higher than normal traffic on this day which can lead to strain on our servers and sessions timing out for users. <b>iGEM HQ recommends that users do not wait till the last day to work/finish their wikis.</b> Once the wikis are frozen, users can no longer make any changes until they are unfrozen after the Jamboree.</p><br />
<ul><b>Do not...</b><br />
<li>wait till the last minute</li><br />
<li>try to upload everything at once</li><br />
</ul><br />
<br />
<br /><br />
<br />
<h3>2014.igem.org/Team:Team_Name</h3><br />
<p>All iGEM 2014 teams are given a namespace on the iGEM 2014 wiki with their team name. Teams are allowed to create and edit pages within their respective team namespace. Teams are <b>not allowed</b> to create or edit pages belonging to another team's namespace.</p><br />
<br />
<br /><br />
<br />
<h3>Upload to 2014.igem.org server</h3><br />
<p>All team pages, images, documents and code must be hosted on the <b>2014.igem.org</b> server. We preserve all iGEM content on our own servers so future teams can learn from what you have done. When you store content on your own sites or servers, after time, links might become broken, sites might go down, and information will be lost.<br />
</p><br />
<br />
<ul>Use the <a href="https://2014.igem.org/Special:Upload">wiki upload tool</a> to upload your files. <br />
<li>Make sure to name your files clearly and uniquely: <i>File:</i><b>Team_Name_Flow_Cytometry_01.png</b>, instead of <i>File:</i><b>1.png</b></li><br />
</ul><br />
<br />
<h4>Upload to 2014.igem.org server</h4><br />
<p>When you store content on your own sites or servers, after time, links might become broken, sites might go down, and information will be lost.</p><br />
<br />
<br /><br />
<br />
<h3>No Adobe Flash</h3> <br />
<p>Flash is not permitted on the iGEM 2014 wiki. Adobe flash is 100% proprietary and you cannot view the source like you can with our wiki. We chose wikis for teams to build their projects so the source code would be available for future teams, to build on the concept of open source. Flash can also be hosted on external sites and we want 100% of the content of our wikis to be on our wikis. </p> <br />
<br />
<h3>Deadlines and the Wiki Freeze</h3><br />
<p>The team's project description must be documented on their iGEM Team Wiki by the deadline. The project description should be 1-3 paragraphs and only needs to include an up-to-date explanation of the project.</p><br />
<p>The team's wiki must include a link to the completed Safety form and an attributions section.</p><br />
<br />
<h3>iGEM Logo</h3><br />
<p>All iGEM Team Wikis must include the iGEM logo at the top of the page and a visible link back to the iGEM 2014 Wiki Main Page in the header (or at the top of the page). All wiki pages must preserve the user editing menu (notifications, username, messages, history, edit). In the case where the user heading is not visible, an automatic heading will be overlaid on top of the wiki page(s) where the heading is missing. </p><br />
<br />
<h3>The iGEM Login Bar</h3><br />
<p>The iGEM Login Bar is a 20 pixel high, full-width menu bar that exists on all 2014.igem.org pages. It contains:<br />
<ul><br />
<li>wiki tools (edit, history, watch, etc.)</li><br />
<li>login</li><br />
</ul><br />
All iGEM 2014 Team Wikis are required to have the Login Bar. Please keep this in mind as you design your wiki.</p><br />
<br />
--><br />
<br />
<br />
<br />
</div><br />
</html><br />
{{MainPage2014/Footer}}</div>Vinoohttp://2014.igem.org/File:Wiki_server_example1.jpgFile:Wiki server example1.jpg2014-09-22T14:43:50Z<p>Vinoo: </p>
<hr />
<div></div>Vinoohttp://2014.igem.org/Wiki_How-ToWiki How-To2014-09-19T18:59:34Z<p>Vinoo: </p>
<hr />
<div>{{CSS/Main}}<br />
{{NavBar}}<br />
<html><br />
<div id="contentcontainer"><br />
<br />
<h3>Wiki Freeze - October 17th (11:59 PM - EDT) </h3><br />
<br />
<p>Your team's project must be documented on the iGEM 2014 wiki, the parts used in your project must be documented on the <a href="http://parts.igem.org">Registry of Standard Biological Parts</a>. You have the freedom to be creative, but a few specific rules apply:</p><br />
<br />
<br /><br />
<br />
<br />
<br />
<br />
<h4 id="wikitemplates"> Wiki Templates </h4><br />
<p> This year we have created a set of template pages that you may for your wiki! <BR> Feel free to edit them as much as you want </p><br />
<a href="https://2014.igem.org/WikitemplateA_home ">Wiki Template A </a></br><br />
<a href="https://2014.igem.org/WikitemplateB_home ">Wiki Template B </a><br />
<BR><BR><br />
<br />
<style type="text/css"><br />
.simpleTable {<br />
cellspacing: 0;<br />
}<br />
.simpleTable th, .simpleTable td {<br />
padding: 10px 15px;<br />
}<br />
.simpleTable th {<br />
color: #fff;<br />
background-color: #333;<br />
font-style: italic;<br />
font-size: 14pt;<br />
}<br />
.simpleTable tr:nth-child(even) {<br />
background-color: #f0f0f0;<br />
}<br />
</style><br />
<h4>Wiki Dos and Don'ts</h4><br />
<table class="simpleTable"><br />
<tr><br />
<th width="250px">Do</th><br />
<th width="250px">Don't</th><br />
<th width="460px">Why?</th><br />
</tr><br />
<tr><br />
<td>Make sure all wiki content, from pages to files, is hosted on <b>2014.igem.org</b></td><br />
<td>Don't host your wiki or parts of your wiki elsewhere</td><br />
<td>iGEM content is preserved on our servers so future teams can learn from what you've done. When content is stored on other sites/servers, links may become broken, sites may go down, and <b>information will be lost.</b></td><br />
</tr><br />
<tr><br />
<td>Work on your wiki throughout the year and <b>save small edits for last</b></td><br />
<td>Don't wait to add/edit large portions of wiki content the day of the <b>Wiki Freeze</b></td><br />
<td>Just before the Wiki Freeze, iGEM websites experience <b>increased traffic and server loads.</b> This can be a difficult time to make larger changes or additions to your wiki. Don't wait till the last minute!</td><br />
</tr><br />
<tr><br />
<td>Name uploaded files clearly and uniquely (TeamName_Header.png)</td><br />
<td>Don't use generic names for you files (Header.png)</td><br />
<td>Using <b>unique names</b> makes searching/identification of uploaded files easier, and helps prevent files from being overwritten.</td><br />
</tr><br />
</table><br />
<br /><br /><br />
<br />
<h4> Perspectives from an iGEM veteran. </h4><br />
<br />
<br />
<br />
<br />
<table cellspacing="10" style="text-align: justify;" width="965px"><br />
<br />
<tr> <br />
<br />
<td width="48%"><br />
Hello iGEMers!<br />
<br><br />
I was also part of an iGEM team!<br />
<br><br />
In 2011 and 2012 my role was to design and create our team’s wiki. So wiki freeze was my major deadline. I am by no means an expert but let me share with you some of the things I learned with two wiki freezes under my belt.<br />
<br><br><br />
<b> 1.- Test your webpage layout: is information easy to find?</b> </br><br />
<p> I made the terrible mistake of not asking for a third party’s opinion about the layout of information on our site. It was obvious for me how things were laid out and organized. It wasn’t for the people evaluating us. <br><br />
Also, stick to the 3 click rule: content must reachable within 3 clicks so the user does not feel lost or confused. If someone wants to read your abstract, their path should be something like this (Menu –> Project –> Project Description -> Abstract)</p><br />
<br><br />
<b> 2.- Look at other teams’ code, see how they documented and what resources they used. </b><br><br />
<p> It is always good to get inspiration from other iGEM teams. See what you liked that they did and strive to improve! </p><br />
<br><br />
<b> 3.- Start working on your documentation early on. </b> <br><br />
<p>This was a good thing that we did; we created a common file that more than one person can edit at a time. Divide the documentation into smaller files and assign a team member to fully document that topic. In the end you will have a printable version of your project that you can share as a pdf file with other people!</p><br />
<br><br />
<br />
</td><br />
<br />
<td width="4%"></td><br />
<br />
<td width="48%" valign="top"><br />
<b> 4.- Name your images according to the project and keep them all in a folder on your computer. </b> <br><br />
<p> Sometimes naming your gel image “gelthingy_whyiamworkingat3am” sounds perfect at 3AM but later it may not be easy to know what or when that photograph was taken or that image created. <br><br />
Also, the iGEM database doesn’t know that you created that file so if someone names their file with the same name it can end up being replaced! Avoid using generic names like “banner.png” or “logo.jpg”.<br><br />
Try using your team’s name and the webpage where the image will appear, this helps you remember where to place it and reduce the risk of another team overwriting. “JoyUniversity_TeamBios_Richard.jpg” </p><br />
<br><br />
<b> 5.- Do not leave everything to the last minute! </b><br />
<br />
<p> Plan ahead. The last thing you want to be doing at 11:30PM the night of wiki freeze is uploading images. It is very stressful to be looking at the clock and hoping some kind of coding miracle helps you fix bugs faster. Plan to have everything online at least one week ahead so you can go enjoy a nice dinner with your team that night! </p><br />
<br />
<br />
<p> I hope this helps and if you have any questions, feel free to email me or send me a tweet! </p><br />
<i> ana at igem dot org </i><br />
<br><br />
<i> <A HREF="https://twitter.com/anita_sifuentes" > @anita_sifuentes </A> </i><br />
<br />
</td><br />
</tr><br />
</table><br />
<br />
<br />
<!--<br />
<br />
<h3>Wiki Freeze - October 17th</h3><br />
<p>The wiki freeze for the 2014 Giant Jamboree is on <a href="https://2014.igem.org/Calendar_of_Events">October 17th,</a> along with other deadlines. iGEM experiences higher than normal traffic on this day which can lead to strain on our servers and sessions timing out for users. <b>iGEM HQ recommends that users do not wait till the last day to work/finish their wikis.</b> Once the wikis are frozen, users can no longer make any changes until they are unfrozen after the Jamboree.</p><br />
<ul><b>Do not...</b><br />
<li>wait till the last minute</li><br />
<li>try to upload everything at once</li><br />
</ul><br />
<br />
<br /><br />
<br />
<h3>2014.igem.org/Team:Team_Name</h3><br />
<p>All iGEM 2014 teams are given a namespace on the iGEM 2014 wiki with their team name. Teams are allowed to create and edit pages within their respective team namespace. Teams are <b>not allowed</b> to create or edit pages belonging to another team's namespace.</p><br />
<br />
<br /><br />
<br />
<h3>Upload to 2014.igem.org server</h3><br />
<p>All team pages, images, documents and code must be hosted on the <b>2014.igem.org</b> server. We preserve all iGEM content on our own servers so future teams can learn from what you have done. When you store content on your own sites or servers, after time, links might become broken, sites might go down, and information will be lost.<br />
</p><br />
<br />
<ul>Use the <a href="https://2014.igem.org/Special:Upload">wiki upload tool</a> to upload your files. <br />
<li>Make sure to name your files clearly and uniquely: <i>File:</i><b>Team_Name_Flow_Cytometry_01.png</b>, instead of <i>File:</i><b>1.png</b></li><br />
</ul><br />
<br />
<h4>Upload to 2014.igem.org server</h4><br />
<p>When you store content on your own sites or servers, after time, links might become broken, sites might go down, and information will be lost.</p><br />
<br />
<br /><br />
<br />
<h3>No Adobe Flash</h3> <br />
<p>Flash is not permitted on the iGEM 2014 wiki. Adobe flash is 100% proprietary and you cannot view the source like you can with our wiki. We chose wikis for teams to build their projects so the source code would be available for future teams, to build on the concept of open source. Flash can also be hosted on external sites and we want 100% of the content of our wikis to be on our wikis. </p> <br />
<br />
<h3>Deadlines and the Wiki Freeze</h3><br />
<p>The team's project description must be documented on their iGEM Team Wiki by the deadline. The project description should be 1-3 paragraphs and only needs to include an up-to-date explanation of the project.</p><br />
<p>The team's wiki must include a link to the completed Safety form and an attributions section.</p><br />
<br />
<h3>iGEM Logo</h3><br />
<p>All iGEM Team Wikis must include the iGEM logo at the top of the page and a visible link back to the iGEM 2014 Wiki Main Page in the header (or at the top of the page). All wiki pages must preserve the user editing menu (notifications, username, messages, history, edit). In the case where the user heading is not visible, an automatic heading will be overlaid on top of the wiki page(s) where the heading is missing. </p><br />
<br />
<h3>The iGEM Login Bar</h3><br />
<p>The iGEM Login Bar is a 20 pixel high, full-width menu bar that exists on all 2014.igem.org pages. It contains:<br />
<ul><br />
<li>wiki tools (edit, history, watch, etc.)</li><br />
<li>login</li><br />
</ul><br />
All iGEM 2014 Team Wikis are required to have the Login Bar. Please keep this in mind as you design your wiki.</p><br />
<br />
--><br />
<br />
<br />
<br />
</div><br />
</html><br />
{{MainPage2014/Footer}}</div>Vinoohttp://2014.igem.org/Wiki_How-ToWiki How-To2014-09-19T18:25:49Z<p>Vinoo: </p>
<hr />
<div>{{CSS/Main}}<br />
{{NavBar}}<br />
<html><br />
<div id="contentcontainer"><br />
<br />
<h3>Wiki Freeze - October 17th (11:59 PM - EDT) </h3><br />
<br />
<p>Your team's project must be documented on the iGEM 2014 wiki, the parts used in your project must be documented on the <a href="http://parts.igem.org">Registry of Standard Biological Parts</a>. You have the freedom to be creative, but a few specific rules apply:</p><br />
<br />
<br /><br />
<br />
<br />
<br />
<br />
<h4 id="wikitemplates"> Wiki Templates </h4><br />
<p> This year we have created a set of template pages that you may for your wiki! <BR> Feel free to edit them as much as you want </p><br />
<a href="https://2014.igem.org/WikitemplateA_home ">Wiki Template A </a></br><br />
<a href="https://2014.igem.org/WikitemplateB_home ">Wiki Template B </a><br />
<BR><BR><br />
<br />
<style type="text/css"><br />
.simpleTable {<br />
cellspacing: 0;<br />
}<br />
.simpleTable th, .simpleTable td {<br />
padding: 10px 15px;<br />
}<br />
.simpleTable th {<br />
color: #fff;<br />
background-color: #333;<br />
font-style: italic;<br />
font-size: 14pt;<br />
}<br />
.simpleTable tr:nth-child(even) {<br />
background-color: #f0f0f0;<br />
}<br />
</style><br />
<h4>Wiki Dos and Don'ts</h4><br />
<table class="simpleTable"><br />
<tr><br />
<th width="250px">Do</th><br />
<th width="250px">Don't</th><br />
<th width="460px">Why?</th><br />
</tr><br />
<tr><br />
<td>Make sure all wiki content, from pages to files, is hosted on <b>2014.igem.org</b></td><br />
<td>Don't host your wiki or parts of your wiki elsewhere</td><br />
<td>iGEM content is preserved on our servers so future teams can learn from what you've done. When content is stored on other sites/servers, links may become broken, sites may go down, and <b>information will be lost.</b></td><br />
</tr><br />
<tr><br />
<td>Work on your wiki throughout the year and <b>save small edits for last</b></td><br />
<td>Don't wait to add/edit large portions of wiki content the day of the <b>Wiki Freeze</b></td><br />
<td>Just before the Wiki Freeze, iGEM websites experience <b>increased traffic and server loads.</b> This can be a difficult time to make larger changes or additions to your wiki. Don't wait till the last minute!</td><br />
</tr><br />
<tr><br />
<td>Name uploaded files uniquely and clearly (TeamName_Header.png)</td><br />
<td>Don't use generic names for you files (Header.png)</td><br />
<td>Using <b>unique names</b> makes searching/identification of uploaded files easier, and helps prevent files from being overwritten.</td><br />
</tr><br />
</table><br />
<br /><br /><br />
<br />
<h4> Perspectives from an iGEM veteran. </h4><br />
<br />
<br />
<br />
<br />
<table cellspacing="10" style="text-align: justify;" width="965px"><br />
<br />
<tr> <br />
<br />
<td width="48%"><br />
Hello iGEMers!<br />
<br><br />
I was also part of an iGEM team!<br />
<br><br />
In 2011 and 2012 my role was to design and create our team’s wiki. So wiki freeze was my major deadline. I am by no means an expert but let me share with you some of the things I learned with two wiki freezes under my belt.<br />
<br><br><br />
<b> 1.- Test your webpage layout: is information easy to find?</b> </br><br />
<p> I made the terrible mistake of not asking for a third party’s opinion about the layout of information on our site. It was obvious for me how things were laid out and organized. It wasn’t for the people evaluating us. <br><br />
Also, stick to the 3 click rule: content must reachable within 3 clicks so the user does not feel lost or confused. If someone wants to read your abstract, their path should be something like this (Menu –> Project –> Project Description -> Abstract)</p><br />
<br><br />
<b> 2.- Look at other teams’ code, see how they documented and what resources they used. </b><br><br />
<p> It is always good to get inspiration from other iGEM teams. See what you liked that they did and strive to improve! </p><br />
<br><br />
<b> 3.- Start working on your documentation early on. </b> <br><br />
<p>This was a good thing that we did; we created a common file that more than one person can edit at a time. Divide the documentation into smaller files and assign a team member to fully document that topic. In the end you will have a printable version of your project that you can share as a pdf file with other people!</p><br />
<br><br />
<br />
</td><br />
<br />
<td width="4%"></td><br />
<br />
<td width="48%" valign="top"><br />
<b> 4.- Name your images according to the project and keep them all in a folder on your computer. </b> <br><br />
<p> Sometimes naming your gel image “gelthingy_whyiamworkingat3am” sounds perfect at 3AM but later it may not be easy to know what or when that photograph was taken or that image created. <br><br />
Also, the iGEM database doesn’t know that you created that file so if someone names their file with the same name it can end up being replaced! Avoid using generic names like “banner.png” or “logo.jpg”.<br><br />
Try using your team’s name and the webpage where the image will appear, this helps you remember where to place it and reduce the risk of another team overwriting. “JoyUniversity_TeamBios_Richard.jpg” </p><br />
<br><br />
<b> 5.- Do not leave everything to the last minute! </b><br />
<br />
<p> Plan ahead. The last thing you want to be doing at 11:30PM the night of wiki freeze is uploading images. It is very stressful to be looking at the clock and hoping some kind of coding miracle helps you fix bugs faster. Plan to have everything online at least one week ahead so you can go enjoy a nice dinner with your team that night! </p><br />
<br />
<br />
<p> I hope this helps and if you have any questions, feel free to email me or send me a tweet! </p><br />
<i> ana at igem dot org </i><br />
<br><br />
<i> <A HREF="https://twitter.com/anita_sifuentes" > @anita_sifuentes </A> </i><br />
<br />
</td><br />
</tr><br />
</table><br />
<br />
<br />
<!--<br />
<br />
<h3>Wiki Freeze - October 17th</h3><br />
<p>The wiki freeze for the 2014 Giant Jamboree is on <a href="https://2014.igem.org/Calendar_of_Events">October 17th,</a> along with other deadlines. iGEM experiences higher than normal traffic on this day which can lead to strain on our servers and sessions timing out for users. <b>iGEM HQ recommends that users do not wait till the last day to work/finish their wikis.</b> Once the wikis are frozen, users can no longer make any changes until they are unfrozen after the Jamboree.</p><br />
<ul><b>Do not...</b><br />
<li>wait till the last minute</li><br />
<li>try to upload everything at once</li><br />
</ul><br />
<br />
<br /><br />
<br />
<h3>2014.igem.org/Team:Team_Name</h3><br />
<p>All iGEM 2014 teams are given a namespace on the iGEM 2014 wiki with their team name. Teams are allowed to create and edit pages within their respective team namespace. Teams are <b>not allowed</b> to create or edit pages belonging to another team's namespace.</p><br />
<br />
<br /><br />
<br />
<h3>Upload to 2014.igem.org server</h3><br />
<p>All team pages, images, documents and code must be hosted on the <b>2014.igem.org</b> server. We preserve all iGEM content on our own servers so future teams can learn from what you have done. When you store content on your own sites or servers, after time, links might become broken, sites might go down, and information will be lost.<br />
</p><br />
<br />
<ul>Use the <a href="https://2014.igem.org/Special:Upload">wiki upload tool</a> to upload your files. <br />
<li>Make sure to name your files clearly and uniquely: <i>File:</i><b>Team_Name_Flow_Cytometry_01.png</b>, instead of <i>File:</i><b>1.png</b></li><br />
</ul><br />
<br />
<h4>Upload to 2014.igem.org server</h4><br />
<p>When you store content on your own sites or servers, after time, links might become broken, sites might go down, and information will be lost.</p><br />
<br />
<br /><br />
<br />
<h3>No Adobe Flash</h3> <br />
<p>Flash is not permitted on the iGEM 2014 wiki. Adobe flash is 100% proprietary and you cannot view the source like you can with our wiki. We chose wikis for teams to build their projects so the source code would be available for future teams, to build on the concept of open source. Flash can also be hosted on external sites and we want 100% of the content of our wikis to be on our wikis. </p> <br />
<br />
<h3>Deadlines and the Wiki Freeze</h3><br />
<p>The team's project description must be documented on their iGEM Team Wiki by the deadline. The project description should be 1-3 paragraphs and only needs to include an up-to-date explanation of the project.</p><br />
<p>The team's wiki must include a link to the completed Safety form and an attributions section.</p><br />
<br />
<h3>iGEM Logo</h3><br />
<p>All iGEM Team Wikis must include the iGEM logo at the top of the page and a visible link back to the iGEM 2014 Wiki Main Page in the header (or at the top of the page). All wiki pages must preserve the user editing menu (notifications, username, messages, history, edit). In the case where the user heading is not visible, an automatic heading will be overlaid on top of the wiki page(s) where the heading is missing. </p><br />
<br />
<h3>The iGEM Login Bar</h3><br />
<p>The iGEM Login Bar is a 20 pixel high, full-width menu bar that exists on all 2014.igem.org pages. It contains:<br />
<ul><br />
<li>wiki tools (edit, history, watch, etc.)</li><br />
<li>login</li><br />
</ul><br />
All iGEM 2014 Team Wikis are required to have the Login Bar. Please keep this in mind as you design your wiki.</p><br />
<br />
--><br />
<br />
<br />
<br />
</div><br />
</html><br />
{{MainPage2014/Footer}}</div>Vinoohttp://2014.igem.org/Wiki_How-ToWiki How-To2014-09-02T15:31:23Z<p>Vinoo: </p>
<hr />
<div>{{CSS/Main}}<br />
{{NavBar}}<br />
<html><br />
<div id="contentcontainer"><br />
<br />
<p> In this page you will find information about:</p><br />
<br />
<ul><br />
<li>Wiki Freeze</li><br />
<li>Wiki Requirements</li><br />
<li>Wiki Restrictions</li><br />
<li>Team Wiki examples</li><br />
<li>Design Tips and suggestions</li><br />
<li><a href= "#wikitemplates"> Wiki templates </a></li><br />
<li>FAQS</li><br />
</ul><br />
<br />
<p>Your team's project must be documented on the iGEM 2014 wiki, the parts used in your project must be documented on the <a href="http://parts.igem.org">Registry of Standard Biological Parts</a>. You have the freedom to be creative, but a few specific rules apply:</p><br />
<br />
<br /><br />
<br />
<h3>Wiki Freeze - October 17th</h3><br />
<p>The wiki freeze for the 2014 Giant Jamboree is on <a href="https://2014.igem.org/Calendar_of_Events">October 17th,</a> along with other deadlines. iGEM experiences higher than normal traffic on this day which can lead to strain on our servers and sessions timing out for users. <b>iGEM HQ recommends that users do not wait till the last day to work/finish their wikis.</b> Once the wikis are frozen, users can no longer make any changes until they are unfrozen after the Jamboree.</p><br />
<ul><b>Do not...</b><br />
<li>wait till the last minute</li><br />
<li>try to upload everything at once</li><br />
</ul><br />
<br />
<br /><br />
<br />
<h3>2014.igem.org/Team:Team_Name</h3><br />
<p>All iGEM 2014 teams are given a namespace on the iGEM 2014 wiki with their team name. Teams are allowed to create and edit pages within their respective team namespace. Teams are <b>not allowed</b> to create or edit pages belonging to another team's namespace.</p><br />
<br />
<br /><br />
<br />
<h3>Upload to 2014.igem.org server</h3><br />
<p>All team pages, images, documents and code must be hosted on the <b>2014.igem.org</b> server. We preserve all iGEM content on our own servers so future teams can learn from what you have done. When you store content on your own sites or servers, after time, links might become broken, sites might go down, and information will be lost.<br />
</p><br />
<br />
<ul>Use the <a href="https://2014.igem.org/Special:Upload">wiki upload tool</a> to upload your files. <br />
<li>Make sure to name your files clearly and uniquely: <i>File:</i><b>Team_Name_Flow_Cytometry_01.png</b>, instead of <i>File:</i><b>1.png</b></li><br />
</ul><br />
<br />
<h4>Upload to 2014.igem.org server</h4><br />
<p>When you store content on your own sites or servers, after time, links might become broken, sites might go down, and information will be lost.</p><br />
<br />
<br /><br />
<br />
<h3>No Adobe Flash</h3> <br />
<p>Flash is not permitted on the iGEM 2014 wiki. Adobe flash is 100% proprietary and you cannot view the source like you can with our wiki. We chose wikis for teams to build their projects so the source code would be available for future teams, to build on the concept of open source. Flash can also be hosted on external sites and we want 100% of the content of our wikis to be on our wikis. </p> <br />
<br />
<h3>Deadlines and the Wiki Freeze</h3><br />
<p>The team's project description must be documented on their iGEM Team Wiki by the deadline. The project description should be 1-3 paragraphs and only needs to include an up-to-date explanation of the project.</p><br />
<p>The team's wiki must include a link to the completed Safety form and an attributions section.</p><br />
<br />
<h3>iGEM Logo</h3><br />
<p>All iGEM Team Wikis must include the iGEM logo at the top of the page and a visible link back to the iGEM 2014 Wiki Main Page in the header (or at the top of the page). All wiki pages must preserve the user editing menu (notifications, username, messages, history, edit). In the case where the user heading is not visible, an automatic heading will be overlaid on top of the wiki page(s) where the heading is missing. </p><br />
<br />
<h3>The iGEM Login Bar</h3><br />
<p>The iGEM Login Bar is a 20 pixel high, full-width menu bar that exists on all 2014.igem.org pages. It contains:<br />
<ul><br />
<li>wiki tools (edit, history, watch, etc.)</li><br />
<li>login</li><br />
</ul><br />
All iGEM 2014 Team Wikis are required to have the Login Bar. Please keep this in mind as you design your wiki.</p><br />
<br />
<br />
<br />
<h3 id="wikitemplates"> Wiki Templates </h3><br />
<p> This year we have created a set of template pages that you may for your wiki! Feel free to edit them as much as you want </p><br />
<a href="https://2014.igem.org/WikitemplateA_home ">Wiki Template A </a></br><br />
<a href="https://2014.igem.org/WikitemplateB_home ">Wiki Template B </a><br />
<br />
</div><br />
</html><br />
{{MainPage2014/Footer}}</div>Vinoohttp://2014.igem.org/Wiki_How-ToWiki How-To2014-09-02T14:59:22Z<p>Vinoo: </p>
<hr />
<div>{{CSS/Main}}<br />
{{NavBar}}<br />
<html><br />
<div id="contentcontainer"><br />
<br />
<p style="color:red;"> <b> Please note that all information on this page is in a draft version. Please check back often for details. </b> </p><br />
<br />
<p> In this page you will find information about:</p><br />
<br />
<ul><br />
<li>Wiki Freeze</li><br />
<li>Wiki Requirements</li><br />
<li>Wiki Restrictions</li><br />
<li>Team Wiki examples</li><br />
<li>Design Tips and suggestions</li><br />
<li><a href= "#wikitemplates"> Wiki templates </a></li><br />
<li>FAQS</li><br />
</ul><br />
<br />
<p>Your team's project must be documented on the iGEM 2014 wiki, the parts used in your project must be documented on the <a href="http://parts.igem.org">Registry of Standard Biological Parts</a>. You have the freedom to be creative, but a few specific rules apply:</p><br />
<br />
<br /><br />
<br />
<h3>Wiki Freeze - October 17th</h3><br />
<p>The wiki freeze for the 2014 Giant Jamboree is on <a href="https://2014.igem.org/Calendar_of_Events">October 17th,</a> along with other deadlines. iGEM experiences higher than normal traffic on this day which can lead to strain on our servers and sessions timing out for users. <b>iGEM HQ recommends that users do not wait till the last day to work/finish their wikis.</b> Once the wikis are frozen, users can no longer make any changes, until they are unfrozen after the Jamboree.</p><br />
<ul><b>Do not...</b><br />
<li>wait till the last minute</li><br />
<li>try to upload everything at once</li><br />
</ul><br />
<br />
<br /><br />
<br />
<h3>2014.igem.org/Team:Team_Name</h3><br />
<p>All iGEM 2014 teams are given a namespace on the iGEM 2014 wiki with their team name. Teams are allowed to create and edit pages within their respective team namespace. Teams are <b>not allowed</b> to create or edit pages belonging to another team's namespace.</p><br />
<br />
<br /><br />
<br />
<h3>Upload to 2014.igem.org server</h3><br />
<p>All team pages, images, documents and code must be hosted on the 2014.igem.org server. We preserve all iGEM content on our own servers so future teams can learn from what you have done. When you store content on your own sites or servers, after time, links might become broken, sites might go down, and information will be lost.<br />
</p><br />
<br />
<ul>Use the <a href="https://2014.igem.org/Special:Upload">wiki upload tool</a> to upload your files. <br />
<li>Please make sure to name your files clearly and uniquely: <i>File:</i><b>Team_Name_Flow_Cytometry_01.png</b>, instead of <i>File:</i><b>1.png</b></li><br />
</ul><br />
<br />
<br />
<br /><br />
<br />
<h3>No Adobe Flash</h3> <br />
<p>Flash is not permitted on the iGEM 2014 wiki. Adobe flash is 100% proprietary and you cannot view the source like you can with our wiki. We chose wikis for teams to build their projects so the source code would be available for future teams, to build on the concept of open source. Flash can also be hosted on external sites and we want 100% of the content of our wikis to be on our wikis. </p> <br />
<br />
<h3>Deadlines and the Wiki Freeze</h3><br />
<p>The team's project description must be documented on their iGEM Team Wiki by the deadline. The project description should be 1-3 paragraphs and only needs to include an up-to-date explanation of the project.</p><br />
<p>The team's wiki must include a link to the completed Safety form and an attributions section.</p><br />
<br />
<h3>iGEM Logo</h3><br />
<p>All iGEM Team Wikis must include the iGEM logo at the top of the page and a visible link back to the iGEM 2014 Wiki Main Page in the header (or at the top of the page). All wiki pages must preserve the user editing menu (notifications, username, messages, history, edit). In the case where the user heading is not visible, an automatic heading will be overlaid on top of the wiki page(s) where the heading is missing. </p><br />
<br />
<h3>The iGEM Login Bar</h3><br />
<p>The iGEM Login Bar is a 20 pixel high, full-width menu bar that exists on all 2014.igem.org pages. It contains:<br />
<ul><br />
<li>wiki tools (edit, history, watch, etc.)</li><br />
<li>login</li><br />
</ul><br />
All iGEM 2014 Team Wikis are required to have the Login Bar. Please keep this in mind as you design your wiki.</p><br />
<br />
<br />
<br />
<h3 id="wikitemplates"> Wiki Templates </h3><br />
<p> This year we have created a set of template pages that you may for your wiki! Feel free to edit them as much as you want </p><br />
<a href="https://2014.igem.org/WikitemplateA_home ">Wiki Template A </a></br><br />
<a href="https://2014.igem.org/WikitemplateB_home ">Wiki Template B </a><br />
<br />
</div><br />
</html><br />
{{MainPage2014/Footer}}</div>Vinoohttp://2014.igem.org/CommunityCommunity2014-08-25T19:24:18Z<p>Vinoo: </p>
<hr />
<div>{{CSS/Main}}<br />
{{NavBar}}<br />
<br />
<html><br />
<style type="text/css"><br />
.firstHeading {display:none;}<br />
#contentcontainer {margin-top: 75px;}<br />
<br />
</style><br />
<div id="contentcontainer"><br />
<br />
<div class="container_12"><br />
<div class="grid_12" id="newsContainer"><br />
<div class="newsTitle" style="border-bottom:0px;">Community Page</div><br />
<br />
<div class="newsItem" style="padding-top:0px;"><br />
<p>The iGEM community page lets you see what some of your fellow iGEM Teams are up to. </p><br />
<p> If you want to add something to this page, send us an email to <b>hq (at) igem . org</b> and we'll add it!</p><br />
</div><br />
<br />
<br />
<div class="newsItem"><br />
<div class="newsDate">August 25, 2014</div><br />
<h3>Team Oxford - DCMation</h3><br />
<a href="https://igem.org/Videos/iGEM_Oxford_2014_Video"><img src="https://static.igem.org/mediawiki/2014/c/c7/2014Oxford_vid_thumb_s.jpg" style="height: px; width:192px"></a><br />
<p><a href="https://2014.igem.org/Team:Oxford">Team Oxford</a> made a <a href="https://igem.org/Videos/iGEM_Oxford_2014_Video">video</a> about their project: DCMation! </p><br />
<br><br><br><br><br><br />
</div><br />
<br />
<br />
<div class="newsItem"><br />
<div class="newsDate">August 18, 2014</div><br />
<h3>Team SF Bay Area DIYbio - Real Vegan Cheese</h3><br />
<a href="https://igem.org/Videos/iGEM_SF_Bay_Area_DIYbio_2014_Video"><img src="https://static.igem.org/mediawiki/2014/c/cb/2014SF_Bay_Area_DIYbio_vid_thumb_s.png" style="height: px; width:192px"></a><br />
<p><a href="https://2014.igem.org/Team:SF_Bay_Area_DIYbio">Team SF Bay Area DIYbio</a> made a <a href="https://igem.org/Videos/iGEM_SF_Bay_Area_DIYbio_2014_Video">video</a> about their real vegan cheese project! You can support them through their <a href="https://www.indiegogo.com/projects/real-vegan-cheese">Indiegogo campaign</a>.</p><br />
<br><br><br><br><br />
</div><br />
<br />
<br />
<div class="newsItem"><br />
<div class="newsDate">August 12, 2014</div><br />
<h3>Team Technion-Israel - Safie</h3><br />
<a href="https://igem.org/Videos/iGEM_Technion-Israel_2014_Video"><img src="https://static.igem.org/mediawiki/2014/9/9c/2014Technion-Israel_vid_thumb_s.png" style="height: px; width:192px"></a><br />
<p>Check out this <a href="https://igem.org/Videos/iGEM_Technion-Israel_2014_Video">video</a> about Team Technion-Israel's project: Safie, the allergen detection system! You can support them through their <a href="http://www.headstart.co.il/project.aspx?id=10603&lan=en-US">Headstart campaign</a>. </p><br />
<br><br><br><br><br />
</div><br />
<br />
<br />
<div class="newsItem"><br />
<div class="newsDate">August 12, 2014</div><br />
<h3>Team Paris Bettencourt - Team Video</h3><br />
<a href="https://igem.org/Videos/iGEM_Paris_Bettencourt_2014_Video"><img src="https://static.igem.org/mediawiki/2014/2/20/2014Paris_Bettencourt_vid_thumb_s.png" style="height: px; width:192px"></a><br />
<p>Team <a href="https://2014.igem.org/Team:Paris_Bettencourt">Paris Bettencourt</a> made a video about their team, iGEM, and their MOOC project this year! Check it out <a href="https://igem.org/Videos/iGEM_Paris_Bettencourt_2014_Video">here</a>!</p><br />
<br><br><br><br><br><br />
</div><br />
<br />
<br />
<div class="newsItem"><br />
<div class="newsDate">August 8, 2014</div><br />
<h3>iGEM High School - Team videos</h3><br />
<a href="https://igem.org/Videos/Community_Videos"><img src="https://static.igem.org/mediawiki/2014hs/b/b4/2014HS-logo.png" style="height: px; width:140px"></a><br />
<p>Check out the awesome videos made by this year's iGEM High School teams!<br />
<ul><br />
<li><a href="https://igem.org/Videos/iGEM_CoBRA_2014_Video">CoBRA 2014 - Team Video</a></li><br />
<li><a href="https://igem.org/Videos/iGEM_GenetiX_Tec_CCM_2014_Video">GenetiX Tec CCM 2014 - Safety in Lab</a></li><br />
<li><a href="https://igem.org/Videos/iGEM_Lambert_GA_2014_Video">Lambert GA 2014 - Let Them Grow</a></li><br />
<li><a href="https://igem.org/Videos/iGEM_Mingdao_2014_Video">Mingdao 2014 - Team Video</a></li><br />
<li><a href="https://igem.org/Videos/iGEM_TAS_Taipei_2014_Video">TAS Taipei 2014 - Taipei Day</a></li><br />
<li><a href="https://igem.org/Videos/iGEM_TP_CC-SanDiego_2014_Video">TP CC-SanDiego 2014 - How to Make an iGEM Team From Scratch</a></li><br />
</ul></p><br />
<p>For more team videos, see the <a href="https://igem.org/Videos/Community_Videos">Community Videos</a> page!</p><br />
<br><br><br><br />
</div><br />
<br />
<br />
<div class="newsItem"><br />
<div class="newsDate">August 7, 2014</div><br />
<h3>Team Pitt - Living Skin Therapeutics</h3><br />
<a href="https://igem.org/Videos/iGEM_Pitt_2014_Video"><img src="https://static.igem.org/mediawiki/2014/5/57/2014Pitt_vid_thumb_s.png" style="height: px; width:192px"></a><br />
<p>"One of the biggest roadblocks to having clear skin is acne, and despite all the available treatment options, the mechanisms of acne are still unclear. The 2014 Pitt iGEM team is improving our understanding of acne by developing a procedure to genetically engineer the skin bacterium, P. acnes, often associated with acne. Learn more about our project and team in this <a href="https://igem.org/Videos/iGEM_Pitt_2014_Video">video</a>!" - <a href="https://2014.igem.org/Team:Pitt">Team Pitt</a></p><br />
<br><br><br><br />
</div><br />
<br />
<br />
<div class="newsItem"><br />
<div class="newsDate">August 5, 2014</div><br />
<h3>Down Into the Test Tube - the art and science workshop from iGEM Berlin</h3><br />
<img src="https://static.igem.org/mediawiki/2014/4/40/Berlin-igemWorkshop_02_xsmall.png" style="height: px; width:300px"><br />
<p>"By what can I identify a BioBrick? How do I synthesize DNA? And why is E.Coli involved in that? In the laboratory, scientist create completely new forms of life to simplify our daily life: Bacterias starting to glow when they come in contact with poisonous water, are remote controlled with magnets or they produce rare earths from common household wastes. Within the two days workshop "Down into the Test Tube“ - we want to motivate you to learn more about synthetic biology and the possibilities, but also dangers. For this, we want to bring together people from different disciplines to work together at new solution for future problems. Collectively we play around with paper, scissors and lasercutter to build an analogue, experimental installation, which can help us to understand synthetic biology and finding new solving. </p><br />
<p>Welcome are interested people from all discipline of art and science - special prior knowledge is not necessary. The workshop will be accompanied from scientist of the Berlin iGEM Team.</p><br />
<p><b>Participants</b>: 15-20 Persons</p><br />
<p><b>Cost</b>: The attendance is free. Except own materials and individual catering. </p><br />
<p><b>When</b>: The workshop takes place at 15th and 16th of august, between 11 am and 6 pm.</p><br />
<p><b>Where</b>: University of Arts, Berlin (Grunewaldstraße 2-5, nearly U-Kleistpark).</p><br />
<p>Available are rapid prototyping tools like lasercutter, 3D printer, and a wood/mechatronic workshop.<br />
Arduinos and different materials are in place, but we´re happy when you also can bring a few of your own thinks.</p><br />
<p>To participate, just write us a mail with your name and a short sentence to your person.<br />
Questions and suggestions are highly welcome.</p><br />
<p>For more informations, please visit our website: <a href="http://igem.berlin/workshop2014.php">http://igem.berlin/workshop2014.php</a>" - <a href="https://2014.igem.org/Team:Berlin">Team Berlin</a></p><br />
</div><br />
<br />
<br />
<div class="newsItem"><br />
<div class="newsDate">July 31, 2014</div><br />
<h3>Team UANL Mty-Mexico - The Reprogrammator</h3><br />
<a href="https://igem.org/Videos/iGEM_UANL_Mty-Mexico_2014_Video"><img src="https://static.igem.org/mediawiki/2014/8/88/2014UANL_vid_thumb_s.png" style="height: px; width:192px"></a><br />
<p>Team <a href="https://2014.igem.org/Team:UANL_Mty-Mexico">UANL Mty-Mexico</a> shares their project, "The Reprogrammator", with us in this <a href="https://igem.org/Videos/iGEM_UANL_Mty-Mexico_2014_Video">video</a>!</p><br />
<br><br><br><br><br><br />
</div><br />
<br />
<br />
<div class="newsItem"><br />
<div class="newsDate">July 30, 2014</div><br />
<h3>Team Stony Brook - Team introduction video</h3><br />
<a href="https://igem.org/Videos/iGEM_Stony_Brook_2014_Video"><img src="https://static.igem.org/mediawiki/2014/0/0a/2014Stony_Brook_vid_thumb_s.png" style="height: px; width:192px"></a><br />
<p>Check out the <a href="https://igem.org/Videos/iGEM_Stony_Brook_2014_Video">video</a> made by <a href="https://2014.igem.org/Team:Stony_Brook">Team Stony Book</a> introducing us to their team via a campus tour!</p><br />
<br><br><br><br><br><br />
</div><br />
<br />
<br />
<div class="newsItem"><br />
<div class="newsDate">July 21, 2014</div><br />
<h3>Team Virginia - Survey update</h3><br />
<p>"Hi iGEM Teams,</p><br />
<p>Earlier this summer we, the University of Virginia iGEM team, emailed you about a collaborative survey we had made to help gauge global awareness and acceptance of synthetic biology for future educational and implementational targeting. This is to remind you about the survey, and to let you know that it’s not too late to participate if you are interested. The survey closes on August 18th, and every team that collects 20 or more responses will receive a web badge to put on their wiki that shows their collaborative efforts. Even if you cannot collect 20 responses, any amount helps.</p><br />
<p>As an update, we currently have 28 teams participating from 11 countries, the survey has been translated into six languages, and six teams have collected over 20 responses for a total of 265 responses. Though you may feel pressed for time to complete the survey, as it closes in a month, keep in mind that it only takes around 4 hours to collect 20 responses, and this data could greatly help the iGEM community in the future.</p><br />
<p>If you are interested in completing the survey, please email us at <b>virginia.igem[at]gmail.com</b> for more information, as well as for instructions on how to distribute the survey.</p><br />
<p>Thank you very much!" - <a href="https://2014.igem.org/Team:Virginia">Team Virginia</a></p><br />
</div><br />
<br />
<br />
<div class="newsItem"><br />
<div class="newsDate">July 11, 2014</div><br />
<h3>Team Linköping -- Survey on Peanut Allergies</h3><br />
<p>"Greetings to all of our fellow iGEMers!</p><br />
<p>We are contacting you to propose collaboration between our teams. We are conducting a survey on peanut allergies and would appreciate it if your team could fill out a simple Google Survey containing seven questions.</p><br />
<p>The purpose of this survey is to examine how aware allergic- and non-allergic people are of peanut allergies and how their society handles and treats the needs of peanut allergic individuals. Please reflect upon the questions before answering them together as a team (no individual surveys, one per team please).</p><br />
<p>Please do not hesitate to contact us if you have any further questions or if you would like to collaborate with us in other ways. We thank you in advance and look forward seeing you in Boston!</p><br />
<p>Email: <span class="email">liuigemgroup AT gmail DOT com</span></p><br />
<p><a href="https://docs.google.com/forms/d/1XthQK-ztKho52C_rjYlW6BUQP1pJz1Z1pLK7TfDy5Gk/viewform">Link to the Survey</a>" - <a href="https://2014.igem.org/Team:Linkoping_Sweden">Team Linkoping Sweden</a></p> <br />
</div><br />
<br />
<br />
<div class="newsItem"><br />
<div class="newsDate">June 25, 2014</div><br />
<h3>Team Aalto-Helsinki - BioBrick Seeker and Team Seeker tools</h3><br />
<img src="https://static.igem.org/mediawiki/2014/a/a7/Aalto_Helsinki_kasi_vectored_light.png" style="height: px; width:150px"><br />
<p>"Hi,<br />
<p>We made a couple of tools to simplify our iGEM research work and we thought that they might be useful for other teams too.</p><br />
<p><b><a href="http://igem-qsf.github.io/BioBrick-Seeker/dist/">BioBrick Seeker</a></b>:<br><br />
BioBrick Seeker is a simple but powerful tool that searches the BioBricks in the 2014 iGEM distribution. This tool shows the part’s name, description, type, location on the 2014 kit plates and includes the link to the part’s official page on the iGEM website. You can filter the BioBricks by brick type and backbone.</p><br />
<p>You can also search BioBricks by using words that are in their description. We were interested in scents, so 'odor' and 'fragrance' found us some useful BioBricks. There's also a search for the part name when you want to see if the BioBrick you found from the Registry is in the 2014 Distribution.</p><br />
<p><b><a href="http://igem-qsf.github.io/iGEM-Team-Seeker/dist/">Team Seeker</a></b>:<br><br />
For searching through previous iGEM teams from 2008 to 2013. You can see what has already been done and how similar projects tackled their problems.</p><br />
<p>Both are work in progress and subject to improvements. If you found our tools useful or have ideas for improvement, contact us via Twitter @AaltoHelsinki or send e-mail to team (at) aaltohelsinki.com"</p><br />
<p><a href="https://2014.igem.org/Team:Aalto-Helsinki">Team Aalto-Helsinki</a></p><br />
<br><br />
</div><br />
<br />
<br />
<div class="newsItem"><br />
<div class="newsDate">June 23, 2014</div><br />
<h3>Teams SYSU-Software and SYSU-China - Biobrick Blast tool</h3><br />
<img src="https://static.igem.org/mediawiki/2014/f/f4/SYSU-software-Biobrick-Blast_screenshot.png" style="height: px; width:300px"><br />
<p>"Have trouble finding biobricks containing or related to a known sequence? Biobrick Blast Online can certainly help you! <br />
Made by SYSU-Software and SYSU-China, Biobrick Blast Online is an online Biobrick alignment and search toolkit. Enter only your sequence, and you will soon get all Biobricks that contain or are related to your sequence, as well as the overall information on those Biobricks. </p><br />
<p>This toolkit not only contains the latest complete iGEM part registry data but also helps you search Biobricks in 2013 or 2014 iGEM DNA Distribution. So move on and have a try!</p><br />
<p>If you need any help or have any suggestion, please don’t hesitate to contact us at <b>sysusoftware (at) 126.com</b>!</p><br />
<p>The <a href="http://biobrickblast.sysusoftware.info/">online version of software</a> has been released, and there is also a <a href="https://www.youtube.com/watch?v=I0IcR2P2_dw">demo video</a> available."</p><br />
<p>-<a href="https://2014.igem.org/Team:SYSU-Software">SYSU-Software</a> and <a href="https://2014.igem.org/Team:SYSU-China">SYSU-China</a></p><br />
<br><br />
</div><br />
<br />
<br />
<div class="newsItem"><br />
<div class="newsDate">June 12, 2014</div><br />
<h3>Automatically generate plans for assembling your genetic constructs</h3><br />
<img src="https://static.igem.org/mediawiki/igem.org/6/68/Ravensoftwareimage.png" style="height: px; width:350px"><br />
<p>"Dear iGEM Community,</p><br />
<p>We would like to introduce a tool for calculating cloning plans for assembling genetic constructs. This tool, Raven, inputs a library of parts and target constructs and determines optimized plans for assembling an arbitrarily large set of target constructs with a selected assembly method.</p><br />
<p>The software is freely available at <a href="http://ravencad.org"><b>ravencad.org</b></a> where there are examples files and user videos to demonstrate how to use the software.</p><br />
<p>The work is also detailed in this month's issue of Nature methods: <a href="http://www.nature.com/nmeth/journal/v11/n6/full/nmeth.2939.html">http://www.nature.com/nmeth/journal/v11/n6/full/nmeth.2939.html</a></p><br />
<p>Thanks,<br />
<br><br>Evan Appleton, Boston University"</p><br />
<br><br />
</div><br />
<br />
<div class="newsItem"><br />
<div class="newsDate">June 9, 2014</div><br />
<h3>Team Virginia - Survey</h3><br />
<img src="" style="height: px; width:250px"><br />
<p>"My name is Tom Moss, and I am a member of the University of <a href="https://2014.igem.org/Team:Virginia">Virginia's 2014 iGEM team</a>. We have designed an online survey to gauge acceptance and understanding of synthetic biology by the general public. We hope that global distribution of and participation in this survey will allow for more targeted public education efforts in the human practices component of the iGEM competition. Participation would involve going to a public place and approaching pedestrians to fill out the short survey. In addition, if your team collects data from at least 20 participants, we will award your team a web badge. This web badge can be displayed on the team’s wiki, and will denote your participation in our study.</p><br />
<p>If you are interested in taking part in the survey, please contact me at <b>virginia.igem (at) gmail.com</b> for further information and instructions.</p><br />
<p>Thank you very much,<br />
<br>Tom Moss<br />
<br>Cara Broshkevitch<br />
<br>Grace Mantus"<br />
</p><br />
<br><br />
</div><br />
<br />
<br />
<div class="newsItem"><br />
<div class="newsDate">June 2, 2014</div><br />
<h3>Participate in the iGEM Interlab Study!</h3><br />
<img src="https://static.igem.org/mediawiki/igem.org/7/7c/IGEM_Measurement_GFP-Histogram.png" style="height: px; width:250px"><br />
<p>"Calling all iGEM teams!</p><br />
<p>Can your team measure fluorescence? Do you care about how well your parts work and whether they'll work the same for other people?</p><br />
<p>If so, we invite you to participate in <a href="https://2014.igem.org/Tracks/Measurement/Interlab_study"><b>the first iGEM interlab study</b></a>! The interlab study is part of the new iGEM <a href="https://2014.igem.org/Tracks/Measurement"><b>Measurement Track</b></a>, but teams from every track are invited and encouraged to participate.</p><br />
<p>Participating is simple: you just need to build and measure three simple constructs. The goal is to find out how these measurements compare between different teams in different labs all over the world. If you want to get a little more in depth, there are extra credit studies to do as well.</p><br />
<p>Can you help us make this the biggest international interlab study ever performed in synthetic biology?</p><br />
<p>Email measurement (at) igem.org to sign up to participate (deadline: July 1st) or if you have questions.</p><br />
<p>iGEM 2014 Measurement Track Organizers<br />
<br>Jacob Beal - BBN Technologies<br />
<br>Traci Haddock - Boston University<br />
<br>Jim Hollenhorst - Agilent"<br />
</p><br />
<br><br />
</div><br />
<br />
<br />
<div class="newsItem"><br />
<div class="newsDate">May 14, 2014</div><br />
<h3>Synthetic Biology: Engineering Complexity - Invitation to Participate in a Special Topic</h3><br />
<p>"Dear iGEM Community,<br><br>Francesca Ceroni (former iGEM judge), Pablo Carbonell, and Karmella Haynes (current iGEM Head Judge) are organizing a new Special Topic issue for the journal <b><a href="http://www.frontiersin.org/synthetic_biology">Frontiers in Bioengineering and Biotechnology: Synthetic Biology</a></b>. Frontiers articles are rigorously peer-reviewed, can be disseminated freely and are widely read by your colleagues and by the broader scientific and medical research communities.<br><br>Please, see the link below for the full description of the topic:<br><br />
<a href="http://www.frontiersin.org/Synthetic_Biology/researchtopics/Synthetic_Biology_engineering_/2866">http://www.frontiersin.org/Synthetic_Biology/researchtopics/Synthetic_Biology_engineering_/2866</a><br><br>The aim of the topic “Synthetic Biology: engineering complexity” is to gather views from specialists in the field about reconciling the inherent complexity of natural systems with traditional engineering principles. We are particularly interested in context-dependent behaviors of synthetic systems, and emergent behaviors of synthetic and semi-synthetic systems.<br><br>We would like to include a broad range of contributions - they can be reviews, research articles, opinion articles, etc.<br><br>Thus, we are writing to kindly ask if you will be able to contribute a manuscript to the topic. Please note that the deadline for manuscript submission is September 15, 2014. Author submission guidelines can be found here: <a href="http://www.frontiersin.org/about/AuthorGuidelines">http://www.frontiersin.org/about/AuthorGuidelines</a><br><br>Please contact Karmella Haynes to express your interest in contributing a manuscript. After you respond, you will receive a second automatic invitation for participation from the Frontiers website. If you have any questions, please contact karmella dot haynes at asu dot edu and we will do our best to assist you.<br><br>Kind regards,<br><br>Karmella Haynes – Arizona State University<br>Francesca Ceroni – Imperial College<br>Pablo Carbonell – University of Evry"<br />
</p><br />
<br><br />
</div><br />
<br />
<br />
<div class="newsItem"><br />
<div class="newsDate">May 13, 2014</div><br />
<h3>Team Uppsala - "Synthetic Biology: A Lab Manual"</h3><br />
<img src="https://static.igem.org/mediawiki/2014/b/b8/SynBio-lab-manual-final-cover.png" style="height: 100px; width:100px"><br />
<p>"This is the first manual for lab work in SynBio. It is aimed at non-specialists and includes practical material for the iGEM competition. Sample book chapters and George Church's inspiring foreword are available free, and ordering information for the book and eBook version from just GBP19.00 are available at <a href="http://www.worldscientific.com/worldscibooks/10.1142/9061#t=aboutBook"><b>this link</b></a>." - <a href="https://2014.igem.org/Team:Uppsala">Team Uppsala</a></p><br />
<p>You can contact them at igemuppsala (at) gmail.com!</p><br />
<br><br><br />
</div><br />
<br />
<div class="newsItem"><br />
<div class="newsDate">May 13, 2014</div><br />
<h3>Team NTNU Trondheim - iGEM Matchmaker tool</h3><br />
<p>"Looking for another team to collaborate with? Try the iGEM Matchmaker tool <a href="http://folk.ntnu.no/oyas/igem/igem_matchmaker/"><b>here</b></a> and find other teams to give or receive help!" - <a href="https://2014.igem.org/Team:NTNU_Trondheim">Team NTNU Trondheim</a></p><br />
</div><br />
<br />
</div><br />
</div><br />
<br />
<br />
<br />
</div><br />
</html><br />
<br />
<br />
{{MainPage2014/Footer}}</div>Vinoohttp://2014.igem.org/CommunityCommunity2014-08-25T19:23:57Z<p>Vinoo: </p>
<hr />
<div>{{CSS/Main}}<br />
{{NavBar}}<br />
<br />
<html><br />
<style type="text/css"><br />
.firstHeading {display:none;}<br />
#contentcontainer {margin-top: 75px;}<br />
<br />
</style><br />
<div id="contentcontainer"><br />
<br />
<div class="container_12"><br />
<div class="grid_12" id="newsContainer"><br />
<div class="newsTitle" style="border-bottom:0px;">Community Page</div><br />
<br />
<div class="newsItem" style="padding-top:0px;"><br />
<p>The iGEM community page lets you see what some of your fellow iGEM Teams are up to. </p><br />
<p> If you want to add something to this page, send us an email to <b>hq (at) igem . org</b> and we'll add it!</p><br />
</div><br />
<br />
<br />
<div class="newsItem"><br />
<div class="newsDate">August 25, 2014</div><br />
<h3>Team Oxford -DCMation</h3><br />
<a href="https://igem.org/Videos/iGEM_Oxford_2014_Video"><img src="https://static.igem.org/mediawiki/2014/c/c7/2014Oxford_vid_thumb_s.jpg" style="height: px; width:192px"></a><br />
<p><a href="https://2014.igem.org/Team:Oxford">Team Oxford</a> made a <a href="https://igem.org/Videos/iGEM_Oxford_2014_Video">video</a> about their project! </p><br />
<br><br><br><br><br><br />
</div><br />
<br />
<br />
<div class="newsItem"><br />
<div class="newsDate">August 18, 2014</div><br />
<h3>Team SF Bay Area DIYbio - Real Vegan Cheese</h3><br />
<a href="https://igem.org/Videos/iGEM_SF_Bay_Area_DIYbio_2014_Video"><img src="https://static.igem.org/mediawiki/2014/c/cb/2014SF_Bay_Area_DIYbio_vid_thumb_s.png" style="height: px; width:192px"></a><br />
<p><a href="https://2014.igem.org/Team:SF_Bay_Area_DIYbio">Team SF Bay Area DIYbio</a> made a <a href="https://igem.org/Videos/iGEM_SF_Bay_Area_DIYbio_2014_Video">video</a> about their real vegan cheese project! You can support them through their <a href="https://www.indiegogo.com/projects/real-vegan-cheese">Indiegogo campaign</a>.</p><br />
<br><br><br><br><br />
</div><br />
<br />
<br />
<div class="newsItem"><br />
<div class="newsDate">August 12, 2014</div><br />
<h3>Team Technion-Israel - Safie</h3><br />
<a href="https://igem.org/Videos/iGEM_Technion-Israel_2014_Video"><img src="https://static.igem.org/mediawiki/2014/9/9c/2014Technion-Israel_vid_thumb_s.png" style="height: px; width:192px"></a><br />
<p>Check out this <a href="https://igem.org/Videos/iGEM_Technion-Israel_2014_Video">video</a> about Team Technion-Israel's project: Safie, the allergen detection system! You can support them through their <a href="http://www.headstart.co.il/project.aspx?id=10603&lan=en-US">Headstart campaign</a>. </p><br />
<br><br><br><br><br />
</div><br />
<br />
<br />
<div class="newsItem"><br />
<div class="newsDate">August 12, 2014</div><br />
<h3>Team Paris Bettencourt - Team Video</h3><br />
<a href="https://igem.org/Videos/iGEM_Paris_Bettencourt_2014_Video"><img src="https://static.igem.org/mediawiki/2014/2/20/2014Paris_Bettencourt_vid_thumb_s.png" style="height: px; width:192px"></a><br />
<p>Team <a href="https://2014.igem.org/Team:Paris_Bettencourt">Paris Bettencourt</a> made a video about their team, iGEM, and their MOOC project this year! Check it out <a href="https://igem.org/Videos/iGEM_Paris_Bettencourt_2014_Video">here</a>!</p><br />
<br><br><br><br><br><br />
</div><br />
<br />
<br />
<div class="newsItem"><br />
<div class="newsDate">August 8, 2014</div><br />
<h3>iGEM High School - Team videos</h3><br />
<a href="https://igem.org/Videos/Community_Videos"><img src="https://static.igem.org/mediawiki/2014hs/b/b4/2014HS-logo.png" style="height: px; width:140px"></a><br />
<p>Check out the awesome videos made by this year's iGEM High School teams!<br />
<ul><br />
<li><a href="https://igem.org/Videos/iGEM_CoBRA_2014_Video">CoBRA 2014 - Team Video</a></li><br />
<li><a href="https://igem.org/Videos/iGEM_GenetiX_Tec_CCM_2014_Video">GenetiX Tec CCM 2014 - Safety in Lab</a></li><br />
<li><a href="https://igem.org/Videos/iGEM_Lambert_GA_2014_Video">Lambert GA 2014 - Let Them Grow</a></li><br />
<li><a href="https://igem.org/Videos/iGEM_Mingdao_2014_Video">Mingdao 2014 - Team Video</a></li><br />
<li><a href="https://igem.org/Videos/iGEM_TAS_Taipei_2014_Video">TAS Taipei 2014 - Taipei Day</a></li><br />
<li><a href="https://igem.org/Videos/iGEM_TP_CC-SanDiego_2014_Video">TP CC-SanDiego 2014 - How to Make an iGEM Team From Scratch</a></li><br />
</ul></p><br />
<p>For more team videos, see the <a href="https://igem.org/Videos/Community_Videos">Community Videos</a> page!</p><br />
<br><br><br><br />
</div><br />
<br />
<br />
<div class="newsItem"><br />
<div class="newsDate">August 7, 2014</div><br />
<h3>Team Pitt - Living Skin Therapeutics</h3><br />
<a href="https://igem.org/Videos/iGEM_Pitt_2014_Video"><img src="https://static.igem.org/mediawiki/2014/5/57/2014Pitt_vid_thumb_s.png" style="height: px; width:192px"></a><br />
<p>"One of the biggest roadblocks to having clear skin is acne, and despite all the available treatment options, the mechanisms of acne are still unclear. The 2014 Pitt iGEM team is improving our understanding of acne by developing a procedure to genetically engineer the skin bacterium, P. acnes, often associated with acne. Learn more about our project and team in this <a href="https://igem.org/Videos/iGEM_Pitt_2014_Video">video</a>!" - <a href="https://2014.igem.org/Team:Pitt">Team Pitt</a></p><br />
<br><br><br><br />
</div><br />
<br />
<br />
<div class="newsItem"><br />
<div class="newsDate">August 5, 2014</div><br />
<h3>Down Into the Test Tube - the art and science workshop from iGEM Berlin</h3><br />
<img src="https://static.igem.org/mediawiki/2014/4/40/Berlin-igemWorkshop_02_xsmall.png" style="height: px; width:300px"><br />
<p>"By what can I identify a BioBrick? How do I synthesize DNA? And why is E.Coli involved in that? In the laboratory, scientist create completely new forms of life to simplify our daily life: Bacterias starting to glow when they come in contact with poisonous water, are remote controlled with magnets or they produce rare earths from common household wastes. Within the two days workshop "Down into the Test Tube“ - we want to motivate you to learn more about synthetic biology and the possibilities, but also dangers. For this, we want to bring together people from different disciplines to work together at new solution for future problems. Collectively we play around with paper, scissors and lasercutter to build an analogue, experimental installation, which can help us to understand synthetic biology and finding new solving. </p><br />
<p>Welcome are interested people from all discipline of art and science - special prior knowledge is not necessary. The workshop will be accompanied from scientist of the Berlin iGEM Team.</p><br />
<p><b>Participants</b>: 15-20 Persons</p><br />
<p><b>Cost</b>: The attendance is free. Except own materials and individual catering. </p><br />
<p><b>When</b>: The workshop takes place at 15th and 16th of august, between 11 am and 6 pm.</p><br />
<p><b>Where</b>: University of Arts, Berlin (Grunewaldstraße 2-5, nearly U-Kleistpark).</p><br />
<p>Available are rapid prototyping tools like lasercutter, 3D printer, and a wood/mechatronic workshop.<br />
Arduinos and different materials are in place, but we´re happy when you also can bring a few of your own thinks.</p><br />
<p>To participate, just write us a mail with your name and a short sentence to your person.<br />
Questions and suggestions are highly welcome.</p><br />
<p>For more informations, please visit our website: <a href="http://igem.berlin/workshop2014.php">http://igem.berlin/workshop2014.php</a>" - <a href="https://2014.igem.org/Team:Berlin">Team Berlin</a></p><br />
</div><br />
<br />
<br />
<div class="newsItem"><br />
<div class="newsDate">July 31, 2014</div><br />
<h3>Team UANL Mty-Mexico - The Reprogrammator</h3><br />
<a href="https://igem.org/Videos/iGEM_UANL_Mty-Mexico_2014_Video"><img src="https://static.igem.org/mediawiki/2014/8/88/2014UANL_vid_thumb_s.png" style="height: px; width:192px"></a><br />
<p>Team <a href="https://2014.igem.org/Team:UANL_Mty-Mexico">UANL Mty-Mexico</a> shares their project, "The Reprogrammator", with us in this <a href="https://igem.org/Videos/iGEM_UANL_Mty-Mexico_2014_Video">video</a>!</p><br />
<br><br><br><br><br><br />
</div><br />
<br />
<br />
<div class="newsItem"><br />
<div class="newsDate">July 30, 2014</div><br />
<h3>Team Stony Brook - Team introduction video</h3><br />
<a href="https://igem.org/Videos/iGEM_Stony_Brook_2014_Video"><img src="https://static.igem.org/mediawiki/2014/0/0a/2014Stony_Brook_vid_thumb_s.png" style="height: px; width:192px"></a><br />
<p>Check out the <a href="https://igem.org/Videos/iGEM_Stony_Brook_2014_Video">video</a> made by <a href="https://2014.igem.org/Team:Stony_Brook">Team Stony Book</a> introducing us to their team via a campus tour!</p><br />
<br><br><br><br><br><br />
</div><br />
<br />
<br />
<div class="newsItem"><br />
<div class="newsDate">July 21, 2014</div><br />
<h3>Team Virginia - Survey update</h3><br />
<p>"Hi iGEM Teams,</p><br />
<p>Earlier this summer we, the University of Virginia iGEM team, emailed you about a collaborative survey we had made to help gauge global awareness and acceptance of synthetic biology for future educational and implementational targeting. This is to remind you about the survey, and to let you know that it’s not too late to participate if you are interested. The survey closes on August 18th, and every team that collects 20 or more responses will receive a web badge to put on their wiki that shows their collaborative efforts. Even if you cannot collect 20 responses, any amount helps.</p><br />
<p>As an update, we currently have 28 teams participating from 11 countries, the survey has been translated into six languages, and six teams have collected over 20 responses for a total of 265 responses. Though you may feel pressed for time to complete the survey, as it closes in a month, keep in mind that it only takes around 4 hours to collect 20 responses, and this data could greatly help the iGEM community in the future.</p><br />
<p>If you are interested in completing the survey, please email us at <b>virginia.igem[at]gmail.com</b> for more information, as well as for instructions on how to distribute the survey.</p><br />
<p>Thank you very much!" - <a href="https://2014.igem.org/Team:Virginia">Team Virginia</a></p><br />
</div><br />
<br />
<br />
<div class="newsItem"><br />
<div class="newsDate">July 11, 2014</div><br />
<h3>Team Linköping -- Survey on Peanut Allergies</h3><br />
<p>"Greetings to all of our fellow iGEMers!</p><br />
<p>We are contacting you to propose collaboration between our teams. We are conducting a survey on peanut allergies and would appreciate it if your team could fill out a simple Google Survey containing seven questions.</p><br />
<p>The purpose of this survey is to examine how aware allergic- and non-allergic people are of peanut allergies and how their society handles and treats the needs of peanut allergic individuals. Please reflect upon the questions before answering them together as a team (no individual surveys, one per team please).</p><br />
<p>Please do not hesitate to contact us if you have any further questions or if you would like to collaborate with us in other ways. We thank you in advance and look forward seeing you in Boston!</p><br />
<p>Email: <span class="email">liuigemgroup AT gmail DOT com</span></p><br />
<p><a href="https://docs.google.com/forms/d/1XthQK-ztKho52C_rjYlW6BUQP1pJz1Z1pLK7TfDy5Gk/viewform">Link to the Survey</a>" - <a href="https://2014.igem.org/Team:Linkoping_Sweden">Team Linkoping Sweden</a></p> <br />
</div><br />
<br />
<br />
<div class="newsItem"><br />
<div class="newsDate">June 25, 2014</div><br />
<h3>Team Aalto-Helsinki - BioBrick Seeker and Team Seeker tools</h3><br />
<img src="https://static.igem.org/mediawiki/2014/a/a7/Aalto_Helsinki_kasi_vectored_light.png" style="height: px; width:150px"><br />
<p>"Hi,<br />
<p>We made a couple of tools to simplify our iGEM research work and we thought that they might be useful for other teams too.</p><br />
<p><b><a href="http://igem-qsf.github.io/BioBrick-Seeker/dist/">BioBrick Seeker</a></b>:<br><br />
BioBrick Seeker is a simple but powerful tool that searches the BioBricks in the 2014 iGEM distribution. This tool shows the part’s name, description, type, location on the 2014 kit plates and includes the link to the part’s official page on the iGEM website. You can filter the BioBricks by brick type and backbone.</p><br />
<p>You can also search BioBricks by using words that are in their description. We were interested in scents, so 'odor' and 'fragrance' found us some useful BioBricks. There's also a search for the part name when you want to see if the BioBrick you found from the Registry is in the 2014 Distribution.</p><br />
<p><b><a href="http://igem-qsf.github.io/iGEM-Team-Seeker/dist/">Team Seeker</a></b>:<br><br />
For searching through previous iGEM teams from 2008 to 2013. You can see what has already been done and how similar projects tackled their problems.</p><br />
<p>Both are work in progress and subject to improvements. If you found our tools useful or have ideas for improvement, contact us via Twitter @AaltoHelsinki or send e-mail to team (at) aaltohelsinki.com"</p><br />
<p><a href="https://2014.igem.org/Team:Aalto-Helsinki">Team Aalto-Helsinki</a></p><br />
<br><br />
</div><br />
<br />
<br />
<div class="newsItem"><br />
<div class="newsDate">June 23, 2014</div><br />
<h3>Teams SYSU-Software and SYSU-China - Biobrick Blast tool</h3><br />
<img src="https://static.igem.org/mediawiki/2014/f/f4/SYSU-software-Biobrick-Blast_screenshot.png" style="height: px; width:300px"><br />
<p>"Have trouble finding biobricks containing or related to a known sequence? Biobrick Blast Online can certainly help you! <br />
Made by SYSU-Software and SYSU-China, Biobrick Blast Online is an online Biobrick alignment and search toolkit. Enter only your sequence, and you will soon get all Biobricks that contain or are related to your sequence, as well as the overall information on those Biobricks. </p><br />
<p>This toolkit not only contains the latest complete iGEM part registry data but also helps you search Biobricks in 2013 or 2014 iGEM DNA Distribution. So move on and have a try!</p><br />
<p>If you need any help or have any suggestion, please don’t hesitate to contact us at <b>sysusoftware (at) 126.com</b>!</p><br />
<p>The <a href="http://biobrickblast.sysusoftware.info/">online version of software</a> has been released, and there is also a <a href="https://www.youtube.com/watch?v=I0IcR2P2_dw">demo video</a> available."</p><br />
<p>-<a href="https://2014.igem.org/Team:SYSU-Software">SYSU-Software</a> and <a href="https://2014.igem.org/Team:SYSU-China">SYSU-China</a></p><br />
<br><br />
</div><br />
<br />
<br />
<div class="newsItem"><br />
<div class="newsDate">June 12, 2014</div><br />
<h3>Automatically generate plans for assembling your genetic constructs</h3><br />
<img src="https://static.igem.org/mediawiki/igem.org/6/68/Ravensoftwareimage.png" style="height: px; width:350px"><br />
<p>"Dear iGEM Community,</p><br />
<p>We would like to introduce a tool for calculating cloning plans for assembling genetic constructs. This tool, Raven, inputs a library of parts and target constructs and determines optimized plans for assembling an arbitrarily large set of target constructs with a selected assembly method.</p><br />
<p>The software is freely available at <a href="http://ravencad.org"><b>ravencad.org</b></a> where there are examples files and user videos to demonstrate how to use the software.</p><br />
<p>The work is also detailed in this month's issue of Nature methods: <a href="http://www.nature.com/nmeth/journal/v11/n6/full/nmeth.2939.html">http://www.nature.com/nmeth/journal/v11/n6/full/nmeth.2939.html</a></p><br />
<p>Thanks,<br />
<br><br>Evan Appleton, Boston University"</p><br />
<br><br />
</div><br />
<br />
<div class="newsItem"><br />
<div class="newsDate">June 9, 2014</div><br />
<h3>Team Virginia - Survey</h3><br />
<img src="" style="height: px; width:250px"><br />
<p>"My name is Tom Moss, and I am a member of the University of <a href="https://2014.igem.org/Team:Virginia">Virginia's 2014 iGEM team</a>. We have designed an online survey to gauge acceptance and understanding of synthetic biology by the general public. We hope that global distribution of and participation in this survey will allow for more targeted public education efforts in the human practices component of the iGEM competition. Participation would involve going to a public place and approaching pedestrians to fill out the short survey. In addition, if your team collects data from at least 20 participants, we will award your team a web badge. This web badge can be displayed on the team’s wiki, and will denote your participation in our study.</p><br />
<p>If you are interested in taking part in the survey, please contact me at <b>virginia.igem (at) gmail.com</b> for further information and instructions.</p><br />
<p>Thank you very much,<br />
<br>Tom Moss<br />
<br>Cara Broshkevitch<br />
<br>Grace Mantus"<br />
</p><br />
<br><br />
</div><br />
<br />
<br />
<div class="newsItem"><br />
<div class="newsDate">June 2, 2014</div><br />
<h3>Participate in the iGEM Interlab Study!</h3><br />
<img src="https://static.igem.org/mediawiki/igem.org/7/7c/IGEM_Measurement_GFP-Histogram.png" style="height: px; width:250px"><br />
<p>"Calling all iGEM teams!</p><br />
<p>Can your team measure fluorescence? Do you care about how well your parts work and whether they'll work the same for other people?</p><br />
<p>If so, we invite you to participate in <a href="https://2014.igem.org/Tracks/Measurement/Interlab_study"><b>the first iGEM interlab study</b></a>! The interlab study is part of the new iGEM <a href="https://2014.igem.org/Tracks/Measurement"><b>Measurement Track</b></a>, but teams from every track are invited and encouraged to participate.</p><br />
<p>Participating is simple: you just need to build and measure three simple constructs. The goal is to find out how these measurements compare between different teams in different labs all over the world. If you want to get a little more in depth, there are extra credit studies to do as well.</p><br />
<p>Can you help us make this the biggest international interlab study ever performed in synthetic biology?</p><br />
<p>Email measurement (at) igem.org to sign up to participate (deadline: July 1st) or if you have questions.</p><br />
<p>iGEM 2014 Measurement Track Organizers<br />
<br>Jacob Beal - BBN Technologies<br />
<br>Traci Haddock - Boston University<br />
<br>Jim Hollenhorst - Agilent"<br />
</p><br />
<br><br />
</div><br />
<br />
<br />
<div class="newsItem"><br />
<div class="newsDate">May 14, 2014</div><br />
<h3>Synthetic Biology: Engineering Complexity - Invitation to Participate in a Special Topic</h3><br />
<p>"Dear iGEM Community,<br><br>Francesca Ceroni (former iGEM judge), Pablo Carbonell, and Karmella Haynes (current iGEM Head Judge) are organizing a new Special Topic issue for the journal <b><a href="http://www.frontiersin.org/synthetic_biology">Frontiers in Bioengineering and Biotechnology: Synthetic Biology</a></b>. Frontiers articles are rigorously peer-reviewed, can be disseminated freely and are widely read by your colleagues and by the broader scientific and medical research communities.<br><br>Please, see the link below for the full description of the topic:<br><br />
<a href="http://www.frontiersin.org/Synthetic_Biology/researchtopics/Synthetic_Biology_engineering_/2866">http://www.frontiersin.org/Synthetic_Biology/researchtopics/Synthetic_Biology_engineering_/2866</a><br><br>The aim of the topic “Synthetic Biology: engineering complexity” is to gather views from specialists in the field about reconciling the inherent complexity of natural systems with traditional engineering principles. We are particularly interested in context-dependent behaviors of synthetic systems, and emergent behaviors of synthetic and semi-synthetic systems.<br><br>We would like to include a broad range of contributions - they can be reviews, research articles, opinion articles, etc.<br><br>Thus, we are writing to kindly ask if you will be able to contribute a manuscript to the topic. Please note that the deadline for manuscript submission is September 15, 2014. Author submission guidelines can be found here: <a href="http://www.frontiersin.org/about/AuthorGuidelines">http://www.frontiersin.org/about/AuthorGuidelines</a><br><br>Please contact Karmella Haynes to express your interest in contributing a manuscript. After you respond, you will receive a second automatic invitation for participation from the Frontiers website. If you have any questions, please contact karmella dot haynes at asu dot edu and we will do our best to assist you.<br><br>Kind regards,<br><br>Karmella Haynes – Arizona State University<br>Francesca Ceroni – Imperial College<br>Pablo Carbonell – University of Evry"<br />
</p><br />
<br><br />
</div><br />
<br />
<br />
<div class="newsItem"><br />
<div class="newsDate">May 13, 2014</div><br />
<h3>Team Uppsala - "Synthetic Biology: A Lab Manual"</h3><br />
<img src="https://static.igem.org/mediawiki/2014/b/b8/SynBio-lab-manual-final-cover.png" style="height: 100px; width:100px"><br />
<p>"This is the first manual for lab work in SynBio. It is aimed at non-specialists and includes practical material for the iGEM competition. Sample book chapters and George Church's inspiring foreword are available free, and ordering information for the book and eBook version from just GBP19.00 are available at <a href="http://www.worldscientific.com/worldscibooks/10.1142/9061#t=aboutBook"><b>this link</b></a>." - <a href="https://2014.igem.org/Team:Uppsala">Team Uppsala</a></p><br />
<p>You can contact them at igemuppsala (at) gmail.com!</p><br />
<br><br><br />
</div><br />
<br />
<div class="newsItem"><br />
<div class="newsDate">May 13, 2014</div><br />
<h3>Team NTNU Trondheim - iGEM Matchmaker tool</h3><br />
<p>"Looking for another team to collaborate with? Try the iGEM Matchmaker tool <a href="http://folk.ntnu.no/oyas/igem/igem_matchmaker/"><b>here</b></a> and find other teams to give or receive help!" - <a href="https://2014.igem.org/Team:NTNU_Trondheim">Team NTNU Trondheim</a></p><br />
</div><br />
<br />
</div><br />
</div><br />
<br />
<br />
<br />
</div><br />
</html><br />
<br />
<br />
{{MainPage2014/Footer}}</div>Vinoohttp://2014.igem.org/File:2014Oxford_vid_thumb_s.jpgFile:2014Oxford vid thumb s.jpg2014-08-25T19:22:12Z<p>Vinoo: </p>
<hr />
<div></div>Vinoohttp://2014.igem.org/Judging/AwardsJudging/Awards2014-07-21T14:05:32Z<p>Vinoo: </p>
<hr />
<div>{{CSS/Main}}<br />
{{NavBar}}<br />
<html><br />
<div id="contentcontainer"><br />
<br />
<!--<p style="color:red;"> <b> Please note that all information on this page is currently in a draft version. Please check back often for details. </b> </p>--><br />
<br />
<p>The following is a list of Awards given by the iGEM Judges and some general information about how Award decisions are made. For examples of award-winning work, see <br />
<a href="https://igem.org/Results?year=2013&region=All&division=igem">the 2013 Jamboree Results</a>. </p><br />
<br />
<br />
<h3>iGEM Medals</h3> <br />
<p><i><br />
<strong>New Track teams must meet medal criteria specific to their track. Please see your <a href="https://2014.igem.org/Tracks#New_Tracks">New Track pages </a> for more details on what you need to accomplish to be awarded a medal. </strong><br />
</p></i><br />
<br />
<p><br />
All teams can earn medals. Teams must nominate themselves using the Judging Form, which will be available later. The three levels of medals, from lowest to highest are Bronze, Silver, and Gold. Requirements for each medal are:<br><br />
</p><br />
<br />
<p><br />
<b>Bronze. </b>The following 5 goals must be achieved:<br><br />
<ol id="criterialist"><br />
<li>Team registration.</li><br />
<li>Complete Judging form.</li><br />
<li>Team Wiki.</li><br />
<li>Present a poster and a talk at the iGEM Jamboree.</li><br />
<li>Document at least one new standard BioBrick Part or Device used in your project/central to your project and submit this part to the iGEM Registry (submissions must adhere to the iGEM Registry guidelines). Please note you must submit this new part to the iGEM Parts Registry. A new application of and outstanding documentation (quantitative data showing the Part’s/ Device’s function) of a previously existing BioBrick part also counts. Please see the <a href="http://parts.igem.org/Help:Contributions">Registry help page</a> on how to document your contributions. To fulfill this criteria, you will also need to submit the part with its original part name to the Registry, following the <a href="http://parts.igem.org/cgi/dna_transfer/index.cgi">submission guidelines</a>.</li></ol><br />
</p><br />
<br />
<p><br />
<b>Silver</b>: In addition to the Bronze Medal requirements, the following 4 goals must be achieved:<br><br />
<ol id="criterialist"><br />
<li>Experimentally validate that at least one new BioBrick Part or Device of your own design and construction works as expected.</li><br />
<li>Document the characterization of this part in the “Main Page” section of that Part’s/Device’s Registry entry.</li><br />
<li>Submit this new part to the iGEM Parts Registry (submissions must adhere to the iGEM Registry guidelines).</li><br />
<li>Your project may have implications for the environment, security, safety and ethics and/or ownership and sharing. Describe one or more ways in which these or other broader implications have been taken into consideration in the design and execution of your project.</li></ol><br />
</p><br />
<br />
<p><br />
<b>Gold</b>: In addition to the Bronze and Silver Medal requirements, any one or more of the following: <br><br />
<ol id="criterialist"><br />
<li>Improve the <b>function</b> OR <b>characterization</b> of an existing BioBrick Part or Device (created by another team or your own institution in a previous year), enter this information in the Registry. Please see the <a href="http://parts.igem.org/Help:Contributions">Registry help page</a> on how to document a contribution to an existing part. <br><i>The growth of the Registry depends on having a broad base of reliable parts. This is why the improvement of an existing part is just as important as the creation and documentation of a new part. An "improvement" is anything that improves the functionality and ease-of-use of a part, so that it is more likely to be used by the community. For instance: strengthening the expression of a part by mutating the DNA sequence; modifying one or a few parts in construct (Device) so that it performs its intended job better; improving a cloning or expression vector that can be easily used by the entire community; and of course, troubleshooting and fixing a part reported to be non-functional. Data from an experimental comparison between the original and improved part/ device is strongly recommended.</i></li><br />
<li>Help any registered iGEM team from another school or institution by, for example, characterizing a part, debugging a construct, or modeling or simulating their system.</li><br />
<li>Your project may have implications for the environment, security, safety and ethics and/or ownership and sharing. Describe a <b><i>novel</b></i> approach that your team has used to help you and others consider these aspects of the design and outcomes of synthetic biology efforts. Please justify its novelty and how this approach might be adapted and scaled for others to use.</li></ol><br />
</p><br />
<br />
<p> <h3> Special Prizes</h3> </p><br />
<p>Special prizes are awarded to honor specific innovative and unique contributions to iGEM. The iGEM 2014 judging committee hopes to award the following Special prizes, conditional on the accomplishments presented by the teams.</p><br />
<br />
<br />
<p>For the following special prizes, teams must nominate themselves using the online Judging Form.</p><br />
<br />
<ol><br />
<li><b>Best Human Practices Advance</b>: Will the world be a safe place if we make biology easy to engineer? How do the lessons of the past inform the discussion going forward? Think beyond just convincing people that “synthetic biology is good.” Find a new way to help human civilization consider, guide, and address the impacts of ongoing advances in biotechnology.</li><br />
<li><b>Best BioBrick Measurement Approach</b>: There are a lot of exciting Parts in the Registry, but many Parts have still not been characterized. Designing great measurement approaches for characterizing new parts or developing and implementing an efficient new method for characterizing thousands of parts are good examples. Teams interested in competed for the Measurement prize are <b><i>strongly</i></b> encouraged to participate in the <a href ="https://2014.igem.org/Tracks/Measurement/Interlab_study">measurement interlab study</a>.</li><br />
<li><b>Best Model</b>: Mathematical models and computer simulations provide a great way to describe the functioning and operation of BioBrick Parts and Devices. </li><br />
<!--<li><br />
<b>Best New Standard</b>: Standards help to make sharing biological parts easier. For example, the BioBrick DNA assembly standard makes it easier to construct parts from pre-existing parts created by the entire BioBrick community. What other sorts of standards can you create? How about a standard system for measuring promoter activity, a standard method for reporting compatible/ incompatible parts, a standard to help describe and control post-translational modifications (such as phosphorylation), or chassis-specific standards (for instance, a system for describing and sharing transgenic yeast)?<br></li><br />
<i>Your New Standard should be clearly presented and easy to find in your <b>Wiki</b>.</i></li>--><br />
</ol><br />
<br />
<p>The following prizes will be awarded at the discretion of the judges:</p><br />
<p><br />
<ol start="4" id="criterialist"><br />
<li><b>Best New BioBrick Part, Natural</b>: Most genetically-encoded functions have not yet been converted to BioBrick parts. In fact, most genes in the natural environment have likely not ever been sequenced. Thus, there are *many* opportunities to find new, cool, and important genetically encoded functions, and refine and convert the DNA encoding these functions into BioBrick standard biological parts.<br><br />
<i>Your best natural BioBrick Part(s) should be visible on your Wiki’s <b>Data Page</b> (see <a href="https://igem.org/Sample_Data_Page">https://igem.org/Sample_Data_Page</a>).</i></li><br />
<li><b>Best New BioBrick Part or Device, Engineered</b>: New BioBrick Devices can be made by combining existing BioBrick Parts. For example, Inverters, Amplifiers, Smell Generators, Protein Balloon Generators, Senders, Receivers, Actuators, and so on.<br><br />
<i>Your best new BioBrick Device(s) should be visible on your Wiki’s <b>Data Page</b>.</i></li><br />
<li><b>Best Wiki</b>: The team Wiki is the “face” of your iGEM project. The team Wikis serve as the main project information resource for future iGEM students and teams, as well as the rest of the world. This award honors the “model” Wiki page, which exemplifies what the following year’s Wikis should strive for.</li><br />
<li><b>Best Poster</b>: Posters should be attractive, clear, and concisely present your team's work.</li><br />
<li><b>Best Presentation</b>: Presentations should be clear, engaging, and communicate your project to a broad audience.</li><br />
<li><b>Best Two-Page Summary</b>: We're introducing a new requirement in 2014. Teams are required to make a two page summary of their project in the style of a lab report. </li><br />
</ol></p><br />
<br />
<p>Additional special prizes that may be awarded if the quality of work is sufficiently high: </p><br />
<br />
<ol start="10" id="criterialist"><br />
<li><b>Best Parts Collection</b>: Did your team make a lot of great parts? Is there a team that ties all your parts together? Do you have more than 10 parts in this collection? Did you make a CRISPR collection, a MoClo collection or a collection of awesome pigment parts? Tell the judges you should be evaluated for the Best Parts Collection award!</li><br />
<!--<li><b>Most Improved Registry Part</b></li>--><br />
</ol><br />
<br />
<br />
<p> <h3> Grand Prizes</h3> </p><br />
<p>A small number of iGEM teams will be selected by the judges as iGEM Finalists. These teams will be selected based on the overall excellence of their entire project, from choice of project, to new Parts and Devices, to the quality of the Project Description, Poster, and Presentation, to the success and impact of the project, to consideration of issues of Human Practices, and so on. There will be three finalists from both the undergraduate section and the overgraduate section.</p><br />
<br />
<p><br />
<ol id="criterialist"><br />
<li><b>Grand Prize Undergraduate</b>: also known as the aluminum BioBrick Trophy; best overall undergraduate team project</li><br />
<li><b>First Runner-up Undergraduate</b>: the next highest ranking undergraduate team project</li><br />
<li><b>Second Runner-up Undergraduate</b>: the next highest ranking undergraduate team project</li></ol><br />
</p><br />
<br />
<p><br />
<ol id="criterialist"><br />
<li><b>Grand Prize Overgraduate</b>: also known as the aluminum BioBrick Trophy; best overall overgraduate team project</li><br />
<li><b>First Runner-up Overgraduate</b>: the next highest ranking overgraduate team project</li><br />
<li><b>Second Runner-up Overgraduate</b>: the next highest ranking overgraduate team project</li></ol><br />
</p><br />
<br />
<p> <h3>Track Prizes</h3> </p><br />
<br />
<p>The iGEM 2014 judging committee hopes to award the following Area prizes, conditional on the accomplishments presented by the teams. Each prize will be awarded at the discretion of the judges. Below are brief descriptions for each Area prize:</p><br />
<br />
<p><br />
<ol id="criterialist"><br />
<br />
<li><b>Best <a href="https://2014.igem.org/Tracks/Energy">Energy</a> Project</b>: World energy consumption has increased by roughly a factor of six since 1950. In May 2013, atmospheric C02 readings taken at the Mauna Loa Observatory in Hawaii surpassed 400 ppm for the first time in recorded history. Can we use synthetic biology to sustainably generate energy or create technologies that can tackle anthropogenic climate change? </li><br />
<br />
<li><b>Best <a href="https://2014.igem.org/Tracks/Environment">Environment</a> Project</b>: The quality of the air, water, and land, both on Earth and other heavenly bodies, limits the happiness of humans and other creatures. Can biotechnology be used to help clean the air, provide fresh drinking water, restore or enhance soil quality, terraform a near-Earth asteroid, or protect, preserve, or enhance natural biological diversity?</li><br />
<br />
<li><b>Best <a href="https://2014.igem.org/Tracks/Food_Nutrition">Food & Nutrition</a> Project</b>: People need to eat. Can biotechnology be responsibly used to produce food or nutritional molecules without causing widespread shortages of either, and without harming the environment that future generations will inherit?</li><br />
<br />
<li><b>Best <a href="https://2014.igem.org/Tracks/Foundational_Advance">Foundational Advance</a> Project</b>: Just thirty-five years ago, scientists could not cut and paste pre-existing fragments of genetic material like we can today. The discovery and application of DNA recombination allowed us to assemble new genes. The synthetic biology community needs other enabling technologies that help to make new accomplishments possible. What are other types of basic tricks does nature use? Have you discovered and applied one that could revolutionize synthetic biology?</li><br />
<br />
<li><b>Best <a href="https://2014.igem.org/Tracks/Health_Medicine">Health & Medicine</a> Project</b>: Many health and medical problems might best be addressed by improved biological technologies. What can synthetic biology do?</li><br />
<br />
<li><b>Best <a href="https://2014.igem.org/Tracks/Information_Processing">Information Procressing</a> Project</b>: The diversity and abundance of biological properties, behaviors, and parts presents a huge information processing challenge. Has your project led to an innovative system that allows us to navigate and use lots of information quickly and effectively?</li><br />
<br />
<li><b>Best <a href="https://2014.igem.org/Tracks/Manufacturing">Manufacturing</a> Project</b>: Have you ever heard of nanotechnology? Well, biology is a nanotechnology that already exists, and that actually works. The ribosome is a programmable nanoassembler embedded within a reproducing machine. Could we responsibly use biology to manufacture useful products, from the nanoscale (atoms) to the decascale (buildings and bridges)? What can biology be programmed to manufacture?</li><br />
<br />
<li><b>Best <a href="https://2014.igem.org/Tracks/New_Application">New Application</a> Project</b>: We're guessing that you have great ideas that nobody has ever thought about, or if they have they forgot to tell somebody else. Can you imagine an entirely new application area for biological technology?</li><br />
</ol><br />
<br />
<p> <h3>New Track Prizes</h3> </p><br />
<br />
<p><br />
We are introducing seven new tracks to the iGEM 2014 competition. On top of our regular tracks such as Foundational Advance and Health and Medicine, we also have the new tracks listed below. Each of the following new tracks is eligible for a best in track award.<br />
</p><br />
<br />
<ol><br />
<li><b>Best <a href="https://2014.igem.org/Tracks/Art_Design">Art and Design</a> Project</b>: Teams of art and design students with input from scientific advisors can use art to drive their iGEM projects, while also making scientific contributions. We are looking for projects that use art and design to consider and explore current and future implications of synthetic biology (including stakeholders, communication, pedagogy, thinking outwards).<br />
</li><br />
<li><b>Best <a href="https://2014.igem.org/Tracks/Community_Labs">Community Labs</a> Project</b>: The Community Lab Track will have the same focus on bench research as the traditional iGEM track, however we are also looking for projects that increase the accessibility of synthetic biology. These might include kits such as Genomikon, or equipment hacks such as the Open PCR. We especially want to encourage teams that may not be able to conduct genetic engineering experiments within their labs due to local regulations, but who might innovate in the areas of equipment, software, outreach, education, etc...</li><br />
<li><b>Best <a href="https://2014.igem.org/Tracks/Entrepreneurship">Entrepreneurship</a> Project</b>: Entrepreneurship in iGEM is about fostering the development of a new industry where Synthetic Biology is the underlying technological platform. As with any new industry, it is not clear which business plans will be the most successful. But, there are also more fundamental questions: What Business models will succeed, how will intellectual property affect company formation and funding, what skills are required at each stage of company’s life cycle, how will government policies promote or hinder new companies, what will be the social contract with Synthetic Biology companies?</li><br />
<li><b>Best <a href="https://2014.igem.org/Tracks/Measurement">Measurement</a> Project</b>: With all the instruments in our laboratories, why isn't measurement a solved problem in synthetic biology? Part of the problem is knowing what to measure and in what context. The iGEM Measurement Track will aim to address some of these problems.</li><br />
<li><b>Best <a href="https://2014.igem.org/Tracks/Microfluidics">Microfluidics</a> Project</b>: Microfluidic, or “lab-on-a-chip” technology, is a maturing field of research involving miniaturized systems where fluids are manipulated on the scale of nanoliters and picoliters. With microfluidics it is possible to perform high-throughput biological experiments integrating multiple functions in devices no larger than a postage stamp. </li><br />
<li><b>Best <a href="https://2014.igem.org/Tracks/Policy_Practices">Policy and Practices</a> Project</b>: In previous years, iGEM teams that have made significant contributions to integrating broader social considerations into the design of their synthetic biology devices, have been awarded with the Special Prize for Best Human Practices Advance. This year we are introducing a dedicated ‘Policy & Practices’ track for teams looking to contribute detailed work grounded in the humanities and social sciences. The new name of ‘Policy & Practices’ is intended to reflect a broadened and matured vision for activities in this track - and across iGEM as a whole - that has evolved from the strong track record of Human Practices at iGEM.</li><br />
<li><b>Best <a href="https://2014.igem.org/Tracks/Software">Software</a> Project</b>: Computers have been around for a long time. How come we don't have more, great software tools for helping everything engineering synthetic biological systems based on standard biological parts?<br><br />
See the <a href="https://2014.igem.org/Tracks/Software">Software Track Page</a> for details.<br><br />
</ol><br />
<br />
<p> <h3>Cross-Track Prizes</h3> </p><br />
<p><br />
Awards as they relate to the new tracks in 2014 are taking on a new dimension. For example: while you will be able to compete in the Policy and Practices track for the P&P track award, there will also be a Policy and Practices prize available across all tracks. <br />
</p><br />
<br />
<p><br />
New Track teams have the same eligibility for awards as all other iGEM teams, pending confirmation from the judging committee. For example, this makes them eligible for (but not limited to) the Best Poster, Best Presentation, Best Wiki, Best New Part (Natural) awards as well as the Undergraduate and Overgraduate BioBrick Trophies. <br />
</p><br />
<br />
<p><br />
There are four New Cross-Track prizes that all iGEM teams are eligible to win. These are:<br />
</p><br />
<ul><br />
<li>Art and Design</li><br />
<li>Measurement</li><br />
<li>Policy and Practices (Formerly Human Practices)</li><br />
<li>Software</li><br />
</ul><br />
<br />
<p><br />
This allows us to reward teams who do excellent work in areas beyond their core track. If you make an excellent piece of software, for example, you will now be able to select your team for the software prize, even if you're not in the software track. Another way to explain this is the awards cover the depth of work in the tracks, while the prizes cover the breadth of all tracks in the competition. This new mechanism allows us to reward more great work by iGEM teams. The graphic below shows award and prize eligibility in more detail:<br />
</p><br />
<br />
<img src="https://static.igem.org/mediawiki/2014/1/15/New_Track_Award-Prize_graphic.png" width = "700px"><br />
<br />
<br />
<p>Please send us any comments or suggestions for awards and judging by email to the judging committee at judging AT igem DOT org. </p><br />
<br />
<br><br />
<br><br />
<br />
</div><br />
</body><br />
</html></div>Vinoohttp://2014.igem.org/Judging/AwardsJudging/Awards2014-07-21T14:01:04Z<p>Vinoo: </p>
<hr />
<div>{{CSS/Main}}<br />
{{NavBar}}<br />
<html><br />
<div id="contentcontainer"><br />
<br />
<!--<p style="color:red;"> <b> Please note that all information on this page is currently in a draft version. Please check back often for details. </b> </p>--><br />
<br />
<p>The following is a list of Awards given by the iGEM Judges and some general information about how Award decisions are made. For examples of award-winning work, see <br />
<a href="https://igem.org/Results?year=2013&region=All&division=igem">the 2013 Jamboree Results</a>. </p><br />
<br />
<br />
<h3>iGEM Medals</h3> <br />
<p><i><br />
<strong>New Track teams must meet medal criteria specific to their track. Please see your <a href="https://2014.igem.org/Tracks#New_Tracks">New Track pages </a> for more details on what you need to accomplish to be awarded a medal. </strong><br />
</p></i><br />
<br />
<p><br />
All teams can earn medals. Teams must nominate themselves using the Judging Form, which will be available later. The three levels of medals, from lowest to highest are Bronze, Silver, and Gold. Requirements for each medal are:<br><br />
</p><br />
<br />
<p><br />
<b>Bronze. </b>The following 5 goals must be achieved:<br><br />
<ol id="criterialist"><br />
<li>Team registration.</li><br />
<li>Complete Judging form.</li><br />
<li>Team Wiki.</li><br />
<li>Present a poster and a talk at the iGEM Jamboree.</li><br />
<li>Document at least one new standard BioBrick Part or Device used in your project/central to your project and submit this part to the iGEM Registry (submissions must adhere to the iGEM Registry guidelines). Please note you must submit this new part to the iGEM Parts Registry. A new application of and outstanding documentation (quantitative data showing the Part’s/ Device’s function) of a previously existing BioBrick part also counts. Please see the <a href="http://parts.igem.org/Help:Contributions">Registry help page</a> on how to document your contributions.</li></ol><br />
</p><br />
<br />
<p><br />
<b>Silver</b>: In addition to the Bronze Medal requirements, the following 4 goals must be achieved:<br><br />
<ol id="criterialist"><br />
<li>Experimentally validate that at least one new BioBrick Part or Device of your own design and construction works as expected.</li><br />
<li>Document the characterization of this part in the “Main Page” section of that Part’s/Device’s Registry entry.</li><br />
<li>Submit this new part to the iGEM Parts Registry (submissions must adhere to the iGEM Registry guidelines).</li><br />
<li>Your project may have implications for the environment, security, safety and ethics and/or ownership and sharing. Describe one or more ways in which these or other broader implications have been taken into consideration in the design and execution of your project.</li></ol><br />
</p><br />
<br />
<p><br />
<b>Gold</b>: In addition to the Bronze and Silver Medal requirements, any one or more of the following: <br><br />
<ol id="criterialist"><br />
<li>Improve the <b>function</b> OR <b>characterization</b> of an existing BioBrick Part or Device (created by another team or your own institution in a previous year), enter this information in the Registry. Please see the <a href="http://parts.igem.org/Help:Contributions">Registry help page</a> on how to document your contributions. <br><i>The growth of the Registry depends on having a broad base of reliable parts. This is why the improvement of an existing part is just as important as the creation and documentation of a new part. An "improvement" is anything that improves the functionality and ease-of-use of a part, so that it is more likely to be used by the community. For instance: strengthening the expression of a part by mutating the DNA sequence; modifying one or a few parts in construct (Device) so that it performs its intended job better; improving a cloning or expression vector that can be easily used by the entire community; and of course, troubleshooting and fixing a part reported to be non-functional. Data from an experimental comparison between the original and improved part/ device is strongly recommended.</i></li><br />
<li>Help any registered iGEM team from another school or institution by, for example, characterizing a part, debugging a construct, or modeling or simulating their system.</li><br />
<li>Your project may have implications for the environment, security, safety and ethics and/or ownership and sharing. Describe a <b><i>novel</b></i> approach that your team has used to help you and others consider these aspects of the design and outcomes of synthetic biology efforts. Please justify its novelty and how this approach might be adapted and scaled for others to use.</li></ol><br />
</p><br />
<br />
<p> <h3> Special Prizes</h3> </p><br />
<p>Special prizes are awarded to honor specific innovative and unique contributions to iGEM. The iGEM 2014 judging committee hopes to award the following Special prizes, conditional on the accomplishments presented by the teams.</p><br />
<br />
<br />
<p>For the following special prizes, teams must nominate themselves using the online Judging Form.</p><br />
<br />
<ol><br />
<li><b>Best Human Practices Advance</b>: Will the world be a safe place if we make biology easy to engineer? How do the lessons of the past inform the discussion going forward? Think beyond just convincing people that “synthetic biology is good.” Find a new way to help human civilization consider, guide, and address the impacts of ongoing advances in biotechnology.</li><br />
<li><b>Best BioBrick Measurement Approach</b>: There are a lot of exciting Parts in the Registry, but many Parts have still not been characterized. Designing great measurement approaches for characterizing new parts or developing and implementing an efficient new method for characterizing thousands of parts are good examples. Teams interested in competed for the Measurement prize are <b><i>strongly</i></b> encouraged to participate in the <a href ="https://2014.igem.org/Tracks/Measurement/Interlab_study">measurement interlab study</a>.</li><br />
<li><b>Best Model</b>: Mathematical models and computer simulations provide a great way to describe the functioning and operation of BioBrick Parts and Devices. </li><br />
<!--<li><br />
<b>Best New Standard</b>: Standards help to make sharing biological parts easier. For example, the BioBrick DNA assembly standard makes it easier to construct parts from pre-existing parts created by the entire BioBrick community. What other sorts of standards can you create? How about a standard system for measuring promoter activity, a standard method for reporting compatible/ incompatible parts, a standard to help describe and control post-translational modifications (such as phosphorylation), or chassis-specific standards (for instance, a system for describing and sharing transgenic yeast)?<br></li><br />
<i>Your New Standard should be clearly presented and easy to find in your <b>Wiki</b>.</i></li>--><br />
</ol><br />
<br />
<p>The following prizes will be awarded at the discretion of the judges:</p><br />
<p><br />
<ol start="4" id="criterialist"><br />
<li><b>Best New BioBrick Part, Natural</b>: Most genetically-encoded functions have not yet been converted to BioBrick parts. In fact, most genes in the natural environment have likely not ever been sequenced. Thus, there are *many* opportunities to find new, cool, and important genetically encoded functions, and refine and convert the DNA encoding these functions into BioBrick standard biological parts.<br><br />
<i>Your best natural BioBrick Part(s) should be visible on your Wiki’s <b>Data Page</b> (see <a href="https://igem.org/Sample_Data_Page">https://igem.org/Sample_Data_Page</a>).</i></li><br />
<li><b>Best New BioBrick Part or Device, Engineered</b>: New BioBrick Devices can be made by combining existing BioBrick Parts. For example, Inverters, Amplifiers, Smell Generators, Protein Balloon Generators, Senders, Receivers, Actuators, and so on.<br><br />
<i>Your best new BioBrick Device(s) should be visible on your Wiki’s <b>Data Page</b>.</i></li><br />
<li><b>Best Wiki</b>: The team Wiki is the “face” of your iGEM project. The team Wikis serve as the main project information resource for future iGEM students and teams, as well as the rest of the world. This award honors the “model” Wiki page, which exemplifies what the following year’s Wikis should strive for.</li><br />
<li><b>Best Poster</b>: Posters should be attractive, clear, and concisely present your team's work.</li><br />
<li><b>Best Presentation</b>: Presentations should be clear, engaging, and communicate your project to a broad audience.</li><br />
<li><b>Best Two-Page Summary</b>: We're introducing a new requirement in 2014. Teams are required to make a two page summary of their project in the style of a lab report. </li><br />
</ol></p><br />
<br />
<p>Additional special prizes that may be awarded if the quality of work is sufficiently high: </p><br />
<br />
<ol start="10" id="criterialist"><br />
<li><b>Best Parts Collection</b>: Did your team make a lot of great parts? Is there a team that ties all your parts together? Do you have more than 10 parts in this collection? Did you make a CRISPR collection, a MoClo collection or a collection of awesome pigment parts? Tell the judges you should be evaluated for the Best Parts Collection award!</li><br />
<!--<li><b>Most Improved Registry Part</b></li>--><br />
</ol><br />
<br />
<br />
<p> <h3> Grand Prizes</h3> </p><br />
<p>A small number of iGEM teams will be selected by the judges as iGEM Finalists. These teams will be selected based on the overall excellence of their entire project, from choice of project, to new Parts and Devices, to the quality of the Project Description, Poster, and Presentation, to the success and impact of the project, to consideration of issues of Human Practices, and so on. There will be three finalists from both the undergraduate section and the overgraduate section.</p><br />
<br />
<p><br />
<ol id="criterialist"><br />
<li><b>Grand Prize Undergraduate</b>: also known as the aluminum BioBrick Trophy; best overall undergraduate team project</li><br />
<li><b>First Runner-up Undergraduate</b>: the next highest ranking undergraduate team project</li><br />
<li><b>Second Runner-up Undergraduate</b>: the next highest ranking undergraduate team project</li></ol><br />
</p><br />
<br />
<p><br />
<ol id="criterialist"><br />
<li><b>Grand Prize Overgraduate</b>: also known as the aluminum BioBrick Trophy; best overall overgraduate team project</li><br />
<li><b>First Runner-up Overgraduate</b>: the next highest ranking overgraduate team project</li><br />
<li><b>Second Runner-up Overgraduate</b>: the next highest ranking overgraduate team project</li></ol><br />
</p><br />
<br />
<p> <h3>Track Prizes</h3> </p><br />
<br />
<p>The iGEM 2014 judging committee hopes to award the following Area prizes, conditional on the accomplishments presented by the teams. Each prize will be awarded at the discretion of the judges. Below are brief descriptions for each Area prize:</p><br />
<br />
<p><br />
<ol id="criterialist"><br />
<br />
<li><b>Best <a href="https://2014.igem.org/Tracks/Energy">Energy</a> Project</b>: World energy consumption has increased by roughly a factor of six since 1950. In May 2013, atmospheric C02 readings taken at the Mauna Loa Observatory in Hawaii surpassed 400 ppm for the first time in recorded history. Can we use synthetic biology to sustainably generate energy or create technologies that can tackle anthropogenic climate change? </li><br />
<br />
<li><b>Best <a href="https://2014.igem.org/Tracks/Environment">Environment</a> Project</b>: The quality of the air, water, and land, both on Earth and other heavenly bodies, limits the happiness of humans and other creatures. Can biotechnology be used to help clean the air, provide fresh drinking water, restore or enhance soil quality, terraform a near-Earth asteroid, or protect, preserve, or enhance natural biological diversity?</li><br />
<br />
<li><b>Best <a href="https://2014.igem.org/Tracks/Food_Nutrition">Food & Nutrition</a> Project</b>: People need to eat. Can biotechnology be responsibly used to produce food or nutritional molecules without causing widespread shortages of either, and without harming the environment that future generations will inherit?</li><br />
<br />
<li><b>Best <a href="https://2014.igem.org/Tracks/Foundational_Advance">Foundational Advance</a> Project</b>: Just thirty-five years ago, scientists could not cut and paste pre-existing fragments of genetic material like we can today. The discovery and application of DNA recombination allowed us to assemble new genes. The synthetic biology community needs other enabling technologies that help to make new accomplishments possible. What are other types of basic tricks does nature use? Have you discovered and applied one that could revolutionize synthetic biology?</li><br />
<br />
<li><b>Best <a href="https://2014.igem.org/Tracks/Health_Medicine">Health & Medicine</a> Project</b>: Many health and medical problems might best be addressed by improved biological technologies. What can synthetic biology do?</li><br />
<br />
<li><b>Best <a href="https://2014.igem.org/Tracks/Information_Processing">Information Procressing</a> Project</b>: The diversity and abundance of biological properties, behaviors, and parts presents a huge information processing challenge. Has your project led to an innovative system that allows us to navigate and use lots of information quickly and effectively?</li><br />
<br />
<li><b>Best <a href="https://2014.igem.org/Tracks/Manufacturing">Manufacturing</a> Project</b>: Have you ever heard of nanotechnology? Well, biology is a nanotechnology that already exists, and that actually works. The ribosome is a programmable nanoassembler embedded within a reproducing machine. Could we responsibly use biology to manufacture useful products, from the nanoscale (atoms) to the decascale (buildings and bridges)? What can biology be programmed to manufacture?</li><br />
<br />
<li><b>Best <a href="https://2014.igem.org/Tracks/New_Application">New Application</a> Project</b>: We're guessing that you have great ideas that nobody has ever thought about, or if they have they forgot to tell somebody else. Can you imagine an entirely new application area for biological technology?</li><br />
</ol><br />
<br />
<p> <h3>New Track Prizes</h3> </p><br />
<br />
<p><br />
We are introducing seven new tracks to the iGEM 2014 competition. On top of our regular tracks such as Foundational Advance and Health and Medicine, we also have the new tracks listed below. Each of the following new tracks is eligible for a best in track award.<br />
</p><br />
<br />
<ol><br />
<li><b>Best <a href="https://2014.igem.org/Tracks/Art_Design">Art and Design</a> Project</b>: Teams of art and design students with input from scientific advisors can use art to drive their iGEM projects, while also making scientific contributions. We are looking for projects that use art and design to consider and explore current and future implications of synthetic biology (including stakeholders, communication, pedagogy, thinking outwards).<br />
</li><br />
<li><b>Best <a href="https://2014.igem.org/Tracks/Community_Labs">Community Labs</a> Project</b>: The Community Lab Track will have the same focus on bench research as the traditional iGEM track, however we are also looking for projects that increase the accessibility of synthetic biology. These might include kits such as Genomikon, or equipment hacks such as the Open PCR. We especially want to encourage teams that may not be able to conduct genetic engineering experiments within their labs due to local regulations, but who might innovate in the areas of equipment, software, outreach, education, etc...</li><br />
<li><b>Best <a href="https://2014.igem.org/Tracks/Entrepreneurship">Entrepreneurship</a> Project</b>: Entrepreneurship in iGEM is about fostering the development of a new industry where Synthetic Biology is the underlying technological platform. As with any new industry, it is not clear which business plans will be the most successful. But, there are also more fundamental questions: What Business models will succeed, how will intellectual property affect company formation and funding, what skills are required at each stage of company’s life cycle, how will government policies promote or hinder new companies, what will be the social contract with Synthetic Biology companies?</li><br />
<li><b>Best <a href="https://2014.igem.org/Tracks/Measurement">Measurement</a> Project</b>: With all the instruments in our laboratories, why isn't measurement a solved problem in synthetic biology? Part of the problem is knowing what to measure and in what context. The iGEM Measurement Track will aim to address some of these problems.</li><br />
<li><b>Best <a href="https://2014.igem.org/Tracks/Microfluidics">Microfluidics</a> Project</b>: Microfluidic, or “lab-on-a-chip” technology, is a maturing field of research involving miniaturized systems where fluids are manipulated on the scale of nanoliters and picoliters. With microfluidics it is possible to perform high-throughput biological experiments integrating multiple functions in devices no larger than a postage stamp. </li><br />
<li><b>Best <a href="https://2014.igem.org/Tracks/Policy_Practices">Policy and Practices</a> Project</b>: In previous years, iGEM teams that have made significant contributions to integrating broader social considerations into the design of their synthetic biology devices, have been awarded with the Special Prize for Best Human Practices Advance. This year we are introducing a dedicated ‘Policy & Practices’ track for teams looking to contribute detailed work grounded in the humanities and social sciences. The new name of ‘Policy & Practices’ is intended to reflect a broadened and matured vision for activities in this track - and across iGEM as a whole - that has evolved from the strong track record of Human Practices at iGEM.</li><br />
<li><b>Best <a href="https://2014.igem.org/Tracks/Software">Software</a> Project</b>: Computers have been around for a long time. How come we don't have more, great software tools for helping everything engineering synthetic biological systems based on standard biological parts?<br><br />
See the <a href="https://2014.igem.org/Tracks/Software">Software Track Page</a> for details.<br><br />
</ol><br />
<br />
<p> <h3>Cross-Track Prizes</h3> </p><br />
<p><br />
Awards as they relate to the new tracks in 2014 are taking on a new dimension. For example: while you will be able to compete in the Policy and Practices track for the P&P track award, there will also be a Policy and Practices prize available across all tracks. <br />
</p><br />
<br />
<p><br />
New Track teams have the same eligibility for awards as all other iGEM teams, pending confirmation from the judging committee. For example, this makes them eligible for (but not limited to) the Best Poster, Best Presentation, Best Wiki, Best New Part (Natural) awards as well as the Undergraduate and Overgraduate BioBrick Trophies. <br />
</p><br />
<br />
<p><br />
There are four New Cross-Track prizes that all iGEM teams are eligible to win. These are:<br />
</p><br />
<ul><br />
<li>Art and Design</li><br />
<li>Measurement</li><br />
<li>Policy and Practices (Formerly Human Practices)</li><br />
<li>Software</li><br />
</ul><br />
<br />
<p><br />
This allows us to reward teams who do excellent work in areas beyond their core track. If you make an excellent piece of software, for example, you will now be able to select your team for the software prize, even if you're not in the software track. Another way to explain this is the awards cover the depth of work in the tracks, while the prizes cover the breadth of all tracks in the competition. This new mechanism allows us to reward more great work by iGEM teams. The graphic below shows award and prize eligibility in more detail:<br />
</p><br />
<br />
<img src="https://static.igem.org/mediawiki/2014/1/15/New_Track_Award-Prize_graphic.png" width = "700px"><br />
<br />
<br />
<p>Please send us any comments or suggestions for awards and judging by email to the judging committee at judging AT igem DOT org. </p><br />
<br />
<br><br />
<br><br />
<br />
</div><br />
</body><br />
</html></div>Vinoohttp://2014.igem.org/Template:HTML/JudgingMenuTemplate:HTML/JudgingMenu2014-07-11T21:04:14Z<p>Vinoo: </p>
<hr />
<div><html><br />
<style type="text/css"><br />
<br />
</style><br />
<ul class="sidemenu"><br />
<li><a href="https://2014.igem.org/Judging/judging_in_2014"><b>JUDGING IN 2014:</b></a> </li><br />
<li><a href="https://2014.igem.org/Judging#awards_eligibility">AWARDS AND ELIGIBILITY</a></li><br />
<ul id="new_tracks" class="sub-sidemenu"><br />
<li><a href="https://2014.igem.org/Judging#medals">Medals</a></li><br />
<li><a href="https://2014.igem.org/Judging#track_awards">Track Awards</a></li><br />
<li><a href="https://2014.igem.org/Judging#special_prizes">Special Prizes</a></li><br />
<li><a href="https://2014.igem.org/Judging#grand_prize">Grank Prize</a></li><br />
</ul><br />
<li><a href="https://2014.igem.org/Judging/judging_in_2014">JUDGING IN 2014?</a></li><br />
<ul id="new_tracks" class="sub-sidemenu"><br />
<li><a href="https://2014.igem.org/Judging/judging_in_2014/new_teams">For New Teams</a></li><br />
<li><a href="https://2014.igem.org/Judging/judging_in_2014/experienced_teams">For Experienced Teams</a></li><br />
</ul><br />
<li><a href="https://2014.igem.org/Judging/important_dates">IMPORTANT DATES</a></li><br />
<li><a href="https://2014.igem.org/Judging/other_information">OTHER INFORMATION</a></li><br />
<ul id="new_tracks" class="sub-sidemenu"><br />
<li><a href="https://2014.igem.org/Judging/Judging_Forms">Judging Forms</a></li><br />
<li><a href="https://2014.igem.org/Judging/Wiki_Freezes">Wiki Freezes</a></li><br />
<li><a href="https://2014.igem.org/Judging/two_page_summary">Two Page Summary</a></li><br />
<li><a href="https://2014.igem.org/Judging/part_improvement">Part Improvement</a></li><br />
</ul><br />
<li><a href="https://2014.igem.org/Judging/for_judges">FOR JUDGES</a></li><br />
<ul id="new_tracks" class="sub-sidemenu"><br />
<li><a href="https://2014.igem.org/Judging/info_for_judges">Info For Judges</a></li><br />
<li><a href="https://2014.igem.org/Judging/judges_dashboard">Judges Dashboard</a></li><br />
<li><a href="https://2014.igem.org/Judging/2013_judges_handbook">2013 Judges Handbook</a></li><br />
</ul><br />
</html></div>Vinoohttp://2014.igem.org/JudgingJudging2014-07-11T21:03:42Z<p>Vinoo: </p>
<hr />
<div>{{CSS/Main}}<br />
{{NavBar}}<br />
<html><br />
<br />
<style type="text/css"><br />
#new_tracks {display: block;}<br />
</style><br />
<br />
<div id="contentcontainer"><br />
<br />
<div class="container_12"><br />
<br />
<div class="grid_3"><br />
</html><br />
{{HTML/JudgingMenu}}<br />
<html><br />
<div class="contentpara" style="margin-top: 60px;"><br />
<p style="width: 160px; margin: auto; color:#7d7d7d; font-size:80%;"></p><br />
</div> <br />
</div><br />
<br />
<div class="grid_9"><br />
<br />
<h1>Intro to judging in 2014</h1><br />
<br />
<p><br />
Welcome to judging in iGEM in 2014! If you’re new to iGEM, you’re probably working hard on your project, trying to make sense of all the requirements, medal criteria, part submission guidelines and other facets of iGEM so that you can present a great project at the Jamboree later this year. <br />
</p><br />
<br />
<p><br />
I’m going to try and clearly explain all the different parts of judging in iGEM so that you can get a sense of what you need to do to meet all our criteria for awesome work!<br />
</p><br />
<br />
<h2><a class="anchor" id="awards_eligibility"></a>Awards and award eligibility</h2><br />
<br />
<p><br />
In iGEM, you can win a medal, an award, a track prize and our grand prize, the BioBrick trophy. For each of these prizes, you are competing with different groups or requirements. Full details can be found on the<a href="https://2014.igem.org/Judging/Awards"> awards page </a>, but here is a summary of awards this year: <br />
</p><br />
<br />
<h3><a class="anchor" id="medals"></a>Medals:</h3> <br />
<br />
<p><br />
All iGEM teams are eligible for medals. Every team can win a gold medal, if they meet the gold medal criteria. You are competing against yourself with medals. We have updated the medal criteria for iGEM’s tracks this year. We have also added new criteria for our new tracks to help focus your work more on your chosen subject area.<br />
New in 2014: New Track teams have their own specific medal criteria so check out your track page for more information!<br />
</p><br />
<br />
<br />
<br />
<h3><a class="anchor" id="track_awards"></a>Track Awards: </h3><br />
<br />
<p><br />
There are awards for the best team in each track. You will be competing against all other teams in your track. Your team can only be in one track in iGEM, so you can only win a single track award. <br />
New in 2014: there are now 15 track awards including our New Tracks. There are now two tracks for “Food and Nutrition” and “Energy”. <br />
</p><br />
<br />
<h3><a class="anchor" id="special_prizes"></a>Special Prizes: </h3><br />
<br />
<p>We have special prizes to reward the best wiki, poster, parts, etc. There is one prize for each special area and many of these prizes have criteria associated with them. For example, if you want to win any of the part awards, your part must be RFC #10 compatible, you must send us the DNA and the part must be in the shipping plasmid PSB1C3, or you won’t be eligible for the part award. <br />
New in 2014: We are working on introducing a new special prize for the two page summary this year. There will not be a “best new standard award” in 2014.<br />
</p><br />
<br />
<h3><a class="anchor" id="grand_prize"></a>Grand BioBrick Trophy: </h3><br />
<br />
<p><br />
Any team can win these trophies, but you are competing with every other team in your section (Undergrad or Overgrad), so competition will be strong. <br />
</p><br />
<br />
<p><br />
The judging system in iGEM has evolved over the last 10 years to meet the challenges of evaluating the incredibly diverse scope of work we see in the competition. We have medals so that teams can learn what milestones they should strive to achieve. We have awards to reward excellence in many areas of our diverse competition. And we have the Grand Prize to pick the best team. <br />
</p><br />
<br />
<h2>So how should we think about judging this year?</h2><br />
<br />
<p><br />
Everyone should strive for excellence in iGEM and we have many, many opportunities to reward excellent work. Only one team will win each section, but participating in our competition will enrich the lives of all iGEMers. <br />
</p><br />
<br />
<p><br />
Our philosophy is “Synthetic Biology based on Standard Parts” and this philosophy is very much embodied in our requirements and medal criteria. Looking at the medal criteria, it’s clear we emphasize making, sending, sharing and characterizing standard parts a key part of the judging. There is a bronze medal criterion to create, characterize and send us a BioBrick part. The silver medal criteria as well as the first gold medal criterion were written to emphasize the creation of new, well characterized BioBrick parts so that we can continue to grow the Registry of Standard Biological Parts. <br />
</p><br />
<br />
<br />
<p><br />
If you don’t know about RFC #10 and you can’t name the four illegal restriction sites, please check out our page on standards. All parts that you send to iGEM HQ must adhere to one of our supported standards. <br />
</p><br />
<br />
<h3>How should we think about judging if we are a new team in 2014?</h3><br />
<br />
<p><br />
If you’re participating in iGEM for the first time in 2014, a lot of the evaluation could seem a little confusing. We care a lot about parts, and we have some very specific requirements about creating, documenting and sending them to us. Check out our pages on assembly standards and RFC #10 to learn more. <br />
</p><br />
<br />
<p><br />
It is important to understand about synthetic biology, parts and why characterization and documentation on the Registry is so important. We also have a calendar of events, so check it out for all our deadlines in 2014.<br />
</p><br />
<br />
<br />
<h3>How should we think about judging this year if we have participated many times?</h3><br />
<br />
<p><br />
There are a few differences in terms of the evaluation this year. We will be evaluating the medals, track prizes and special prizes at the Giant Jamboree this year, instead of separating out awards at the Regions. With a single event and no regions, there will only be one of each award per section in 2014. <br />
</p><br />
<br />
<p><br />
Medal requirements have been slightly modified this year, so please read over them again. We will also require teams to submit a two page summary on what they have achieved. Requirements for this document will be released later in the year. <br />
</p><br />
<br />
<p><br />
To make judging easier this year, we’re also going to freeze the Registry at the same time as the wikis. You’ll need to have your parts be ready to go at the same time as your wiki. <br />
</p><br />
<br />
<h2>Important Dates</h2><br />
<br />
<p><br />
We have a series of deadlines this year that apply to all teams and regions simultaneously. There will only be one wiki freeze and there will also be a freeze on the Registry to aid judges in their evaluations this year. Be sure to study the official iGEM Calendar of Events to find out the final dates for different judging requirements.<br />
Other Requirements and Information<br />
</p><br />
<br />
<br />
<h3>Judging Forms</h3><br />
<br />
<p><br />
Teams will be required to submit a judging form that outlines their accomplishments according to the Judging Criteria. Details on where/how/when to fill out this form will be provided when they are available.<br />
</p><br />
<br />
<br />
<h3>Wiki and Parts.igem.org freeze</h3><br />
<br />
<p><br />
Experienced teams will be familiar with the wiki freeze, the time in the iGEM calendar when we disable editing to allow judges to work without changes. This date will now be two weeks before the Jamboree and for the first time, we will freeze the parts Registry. <br />
</p><br />
<br />
<br />
<h3>Two page summary</h3><br />
<br />
<p><br />
We’re introducing a new requirement for teams to submit a two page summary. This document will be a single page of text with an additional page of images and references. It won’t be about what you were hoping to do, but what your team achieved over the summer. Watch our for more information later in the year.<br />
</p><br />
<br />
<br />
<h3>Part Characterization, Measurement and Improvement</h3><br />
<br />
<p><br />
This year, we’re changing the medal requirements for characterizing, measuring and improving a part. We’re introducing a contribution system, instead of the experience page, that you can read more about on our page. <br />
</p><br />
<br />
<h2>For Judges<br />
<br />
<h3>Information for Judges page</h3><br />
<br />
<p><br />
The 2014 World Championship Jamboree Information for Judges page contains information on how to cast your ballot on teams, where the room locations can be found and where to find all the posters. This page will be updated closer to the 2014 World Championship Jamboree.<br />
</p><br />
<br />
<h3>Judges Dashboard</h3><br />
<br />
<p><br />
Please login to your Judges Dashboards to see the teams you have been assigned.<br />
</p><br />
<br />
<h3>2013 Judging Handbook</h3><br />
<br />
<p><br />
We have not yet updated the judging handbook in 2014. Please see the 2013 version if you’re interested in learning more about what we tell our judges. Please note the content will be updated this year, so not everything in our 2013 version will apply. <br />
</p><br />
<br />
<br />
</div><br />
</div></div><br />
</html><br />
<br />
{{MainPage2014/Footer}}</div>Vinoohttp://2014.igem.org/Template:HTML/JudgingMenuTemplate:HTML/JudgingMenu2014-07-11T21:01:38Z<p>Vinoo: </p>
<hr />
<div><html><br />
<style type="text/css"><br />
<br />
</style><br />
<ul class="sidemenu"><br />
<li><a href="https://2014.igem.org/Judging/judging_in_2014"><b>JUDGING IN 2014:</b></a> </li><br />
<li><a href="https://2014.igem.org/Judging#awards_eligibility">AWARDS AND ELIGIBILITY</a></li><br />
<ul id="new_tracks" class="sub-sidemenu"><br />
<li><a href="https://2014.igem.org/Judging#Medals">Medals</a></li><br />
<li><a href="https://2014.igem.org/Judging#track_awards">Track Awards</a></li><br />
<li><a href="https://2014.igem.org/Judging#special_prizes">Special Prizes</a></li><br />
<li><a href="https://2014.igem.org/Judging#grand_prize">Grank Prize</a></li><br />
</ul><br />
<li><a href="https://2014.igem.org/Judging/judging_in_2014">JUDGING IN 2014?</a></li><br />
<ul id="new_tracks" class="sub-sidemenu"><br />
<li><a href="https://2014.igem.org/Judging/judging_in_2014/new_teams">For New Teams</a></li><br />
<li><a href="https://2014.igem.org/Judging/judging_in_2014/experienced_teams">For Experienced Teams</a></li><br />
</ul><br />
<li><a href="https://2014.igem.org/Judging/important_dates">IMPORTANT DATES</a></li><br />
<li><a href="https://2014.igem.org/Judging/other_information">OTHER INFORMATION</a></li><br />
<ul id="new_tracks" class="sub-sidemenu"><br />
<li><a href="https://2014.igem.org/Judging/Judging_Forms">Judging Forms</a></li><br />
<li><a href="https://2014.igem.org/Judging/Wiki_Freezes">Wiki Freezes</a></li><br />
<li><a href="https://2014.igem.org/Judging/two_page_summary">Two Page Summary</a></li><br />
<li><a href="https://2014.igem.org/Judging/part_improvement">Part Improvement</a></li><br />
</ul><br />
<li><a href="https://2014.igem.org/Judging/for_judges">FOR JUDGES</a></li><br />
<ul id="new_tracks" class="sub-sidemenu"><br />
<li><a href="https://2014.igem.org/Judging/info_for_judges">Info For Judges</a></li><br />
<li><a href="https://2014.igem.org/Judging/judges_dashboard">Judges Dashboard</a></li><br />
<li><a href="https://2014.igem.org/Judging/2013_judges_handbook">2013 Judges Handbook</a></li><br />
</ul><br />
</html></div>Vinoohttp://2014.igem.org/JudgingJudging2014-07-11T19:58:57Z<p>Vinoo: </p>
<hr />
<div>{{CSS/Main}}<br />
{{NavBar}}<br />
<html><br />
<br />
<style type="text/css"><br />
#new_tracks {display: block;}<br />
</style><br />
<br />
<div id="contentcontainer"><br />
<br />
<div class="container_12"><br />
<br />
<div class="grid_3"><br />
</html><br />
{{HTML/JudgingMenu}}<br />
<html><br />
<div class="contentpara" style="margin-top: 60px;"><br />
<p style="width: 160px; margin: auto; color:#7d7d7d; font-size:80%;"></p><br />
</div> <br />
</div><br />
<br />
<div class="grid_9"><br />
<h1>iGEM 2014 Judging</h1><br />
<br />
<p style="color:red;"> <b> Please note that all information on this page is in a draft version. Please check back often for details. </b> </p><br />
<br />
<a href="https://2014.igem.org/Judging/Evaluation_at_iGEM"> <h3>A note to iGEMers on Evaluation at iGEM </h3></a><br />
<br />
<br />
<br />
<br />
<p>We have written a short statement for the 2014 season explaining a little more on evaluations at iGEM. </p><br />
<br />
<br />
<br />
<a href="https://2014.igem.org/Judging/Transparency_at_iGEM"> <h3> A note on transparency, the judging process, and judge affiliations</h3> </a><br />
<br />
<p>There have been concerns on transparency in recent weeks, so we have written a statement to address some of the issues. We are also providing a list of judges in all regions. </p><br />
<br />
<br />
<h3>Important Dates </h3><br />
<p>Be sure to study the official iGEM <a href="https://2014.igem.org/Calendar_of_Events">Calendar of Events </a> to find out the final dates for different judging requirements. </p><br />
<br />
<br />
<a href="https://2014.igem.org/Judging/Awards"> <h3>Judging/Awards 2014 Awards</h3></a><br />
<p>Awards at iGEM are divided into medals and special awards. All teams are eligible for a medal if they meet the 2014 medal criteria. We have updated the medal criteria this year, so please read over the new requirements for silver and gold medals. </p><br />
<p><br />
While we can hand out medals to all teams, there is only one special award per Jamboree. Teams are competing with each other for special awards at iGEM. Please read over the <a href=" https://2014.igem.org/Judging/Awards"> Judging Awards</a> page for a detailed list of medal requirements and award details.</p><br />
<br />
<br />
<h3>Judging Forms</h3><br />
<p>Teams will be required to submit a judging form that outlines their accomplishments according to the <a href= "https://2014.igem.org/Judging/Judging_Criteria"> Judging Criteria </a>. Details on where/how/when to fill out this form will be provided as they are available. </p><br />
<br />
<br />
<h3>Poster judging guidelines</h3><br />
<p>It is important that your poster convey all of the information necessary without the need for verbal explanation. Please read over the <a href="https://2014.igem.org/Judging/Poster_Guidelines"> Poster Judging Guidelines </a> for more information on how we are assessing the posters.</p><br />
<br />
<h3>Complaints</h3><br />
<br />
<p>To file an official complaint regarding iGEM 2014 judging you must send an email to complaints AT igem DOT org. Your email should include your real name, the real name of your school and team, and the real name and email address of your faculty advisor. Your email must also be copied to your faculty advisor. In your email please clearly state your complaint and what you hope will happen as a result of filing your official complaint. The iGEM judging committee will work diligently to respond to all complaints as quickly as possible. Complaints that are sent to other email addresses, or that do not include the requested information will be ignored. All decisions by the judges regarding complaints are final.</p><br />
<br />
<br />
<br />
<h2>Information for Judges</h2><br />
<br />
<h3>Information for Judges page</h3><br />
<br />
<p>The 2014 World Champinoship Jamboree <a href="https://2014.igem.org/Information_for_Judges">Information for Judges</a> page contains information on how to cast your ballot on teams, where the room locations can be found and where to find all the posters. This page will be updated closer to the 2014 World Championship Jamboree. </p><br />
<br />
<h3>Judges Dashboard</h3><br />
Please login to your <a href=" https://igem.org/Judge_List.cgi?year=2014&region=All&division=igem">Judges Dashboards</a> to see the teams you have been assigned.<br />
<br />
<h3>2013 Judging Handbook</h3><br />
<br />
<p>We have re-written the judging handbook for 2013. Please see the new version <a href="https://static.igem.org/mediawiki/2013/d/d9/IGEM_2013_Judging_Handbook.pdf"> Judging Handbook</a> here.</p><br />
</div><br />
</div></div><br />
</html><br />
<br />
{{MainPage2014/Footer}}</div>Vinoohttp://2014.igem.org/JudgingJudging2014-07-11T19:57:26Z<p>Vinoo: </p>
<hr />
<div>{{CSS/Main}}<br />
{{NavBar}}<br />
<html><br />
<br />
<style type="text/css"><br />
#new_tracks {display: block;}<br />
</style><br />
<br />
<div id="contentcontainer"><br />
<br />
<div class="container_12"><br />
<br />
<div class="grid_3"><br />
</html><br />
{{HTML/JudgingMenu}}<br />
<html><br />
<div class="contentpara" style="margin-top: 60px;"><br />
<p style="width: 160px; margin: auto; color:#7d7d7d; font-size:80%;"></p><br />
</div> <br />
</div><br />
<br />
<div class="grid_9"><br />
<br />
<p style="color:red;"> <b> Please note that all information on this page is in a draft version. Please check back often for details. </b> </p><br />
<br />
<a href="https://2014.igem.org/Judging/Evaluation_at_iGEM"> <h3>A note to iGEMers on Evaluation at iGEM </h3></a><br />
<br />
<br />
<br />
<br />
<p>We have written a short statement for the 2014 season explaining a little more on evaluations at iGEM. </p><br />
<br />
<br />
<br />
<a href="https://2014.igem.org/Judging/Transparency_at_iGEM"> <h3> A note on transparency, the judging process, and judge affiliations</h3> </a><br />
<br />
<p>There have been concerns on transparency in recent weeks, so we have written a statement to address some of the issues. We are also providing a list of judges in all regions. </p><br />
<br />
<br />
<h3>Important Dates </h3><br />
<p>Be sure to study the official iGEM <a href="https://2014.igem.org/Calendar_of_Events">Calendar of Events </a> to find out the final dates for different judging requirements. </p><br />
<br />
<br />
<a href="https://2014.igem.org/Judging/Awards"> <h3>Judging/Awards 2014 Awards</h3></a><br />
<p>Awards at iGEM are divided into medals and special awards. All teams are eligible for a medal if they meet the 2014 medal criteria. We have updated the medal criteria this year, so please read over the new requirements for silver and gold medals. </p><br />
<p><br />
While we can hand out medals to all teams, there is only one special award per Jamboree. Teams are competing with each other for special awards at iGEM. Please read over the <a href=" https://2014.igem.org/Judging/Awards"> Judging Awards</a> page for a detailed list of medal requirements and award details.</p><br />
<br />
<br />
<h3>Judging Forms</h3><br />
<p>Teams will be required to submit a judging form that outlines their accomplishments according to the <a href= "https://2014.igem.org/Judging/Judging_Criteria"> Judging Criteria </a>. Details on where/how/when to fill out this form will be provided as they are available. </p><br />
<br />
<br />
<h3>Poster judging guidelines</h3><br />
<p>It is important that your poster convey all of the information necessary without the need for verbal explanation. Please read over the <a href="https://2014.igem.org/Judging/Poster_Guidelines"> Poster Judging Guidelines </a> for more information on how we are assessing the posters.</p><br />
<br />
<h3>Complaints</h3><br />
<br />
<p>To file an official complaint regarding iGEM 2014 judging you must send an email to complaints AT igem DOT org. Your email should include your real name, the real name of your school and team, and the real name and email address of your faculty advisor. Your email must also be copied to your faculty advisor. In your email please clearly state your complaint and what you hope will happen as a result of filing your official complaint. The iGEM judging committee will work diligently to respond to all complaints as quickly as possible. Complaints that are sent to other email addresses, or that do not include the requested information will be ignored. All decisions by the judges regarding complaints are final.</p><br />
<br />
<br />
<br />
<h2>Information for Judges</h2><br />
<br />
<h3>Information for Judges page</h3><br />
<br />
<p>The 2014 World Champinoship Jamboree <a href="https://2014.igem.org/Information_for_Judges">Information for Judges</a> page contains information on how to cast your ballot on teams, where the room locations can be found and where to find all the posters. This page will be updated closer to the 2014 World Championship Jamboree. </p><br />
<br />
<h3>Judges Dashboard</h3><br />
Please login to your <a href=" https://igem.org/Judge_List.cgi?year=2014&region=All&division=igem">Judges Dashboards</a> to see the teams you have been assigned.<br />
<br />
<h3>2013 Judging Handbook</h3><br />
<br />
<p>We have re-written the judging handbook for 2013. Please see the new version <a href="https://static.igem.org/mediawiki/2013/d/d9/IGEM_2013_Judging_Handbook.pdf"> Judging Handbook</a> here.</p><br />
</div><br />
</div></div><br />
</html><br />
<br />
{{MainPage2014/Footer}}</div>Vinoohttp://2014.igem.org/Template:Nav/ResourcesTemplate:Nav/Resources2014-06-19T17:06:58Z<p>Vinoo: </p>
<hr />
<div>{{CSS/Nav/Grid12}}<br />
<html><br />
<div class="container_12"><br />
<div class="grid_3"><br />
<ul><span class="menuHeader">General</span><br />
<li><a href="https://igem.org/Previous_iGEM_Competitions">Previous iGEM Competitions</a></li><br />
<li><a href="https://2014.igem.org/Wiki_How-To">Wiki How-To</a></li><br />
<li><a href="https://igem.org/Videos">Videos</a></li><br />
<li><a href="https://igem.org/Forum">Forums</a></li><br />
<li><a href="https://igem.org/FAQ">FAQ</a></li><br />
</ul><br />
</div><br />
<div class="grid_3"><br />
<ul><span class="menuHeader">Lab Resources</span><br />
<li><a href="http://parts.igem.org">Registry of Standard Biological Parts</a></li><br />
<li><a href="http://parts.igem.org/Help:Registry-at-a-Glance">The Registry at a Glance</a></li><br />
<li><a href="http://parts.igem.org">Protocols</a></li><br />
</ul><br />
</div><br />
<div class="grid_3"><br />
<ul><span class="menuHeader">Affiliated</span><br />
<li><a href="https://2014.igem.org/Partner_Offers">Partner Offers</a></li><br />
<li><a href="https://2014.igem.org/Funding">Funding Opportunities</a></li><br />
</ul><br />
</div><br />
</div><br />
</html></div>Vinoohttp://2014.igem.org/Template:NavBarTemplate:NavBar2014-06-19T17:05:23Z<p>Vinoo: </p>
<hr />
<div><html><br />
<head><br />
<style type="text/css"><br />
#topNav { /*-- creates styled 100% width fixed navigation bar --*/<br />
width: 100%; <br />
position: fixed; <br />
top: 14px; <br />
height: 50px; <br />
background-color: #f0f0f0; <br />
border-bottom: 1px solid #ccc; <br />
z-index: 1000;<br />
}<br />
<br />
#navContainer { /*-- creates centered container for nav bar --*/<br />
width: 975px; <br />
height: 100%; <br />
margin: 0px auto; <br />
position: relative; <br />
font-family: Arial, sans-serif;<br />
}<br />
<br />
.navLinks { /*-- clears style for nav bar ul --*/<br />
margin: 0px; <br />
height: 100%; <br />
}<br />
<br />
.navLinks li { /*-- styles nav bar li, the nav bar elements --*/<br />
display: inline-block;<br />
float: left;<br />
font-size: 12px;<br />
height: 49px;<br />
padding: 0px; <br />
margin: 0px; <br />
border: 1px solid transparent;<br />
}<br />
<br />
.navLinks li:hover { <br />
background-color: #fff;<br />
border: 1px solid #ccc;<br />
border-bottom: 1px solid #fff;<br />
}<br />
<br />
.navLinks > .navSingleLink:hover { <br />
border-bottom: 1px solid #ccc;<br />
}<br />
<br />
.navLinks li > a { /*-- styles the links within the nav bar li --*/<br />
text-decoration: none; <br />
line-height: 50px;<br />
color: #000;<br />
padding-left: 30px;<br />
padding-right: 30px;<br />
display: block;<br />
height: 100%;<br />
}<br />
<br />
.navlinks li > a:hover {<br />
color: #fff;<br />
<br />
} <br />
.navDropMenu { /*-- the drop down box --*/<br />
width: 100%;<br />
position: absolute;<br />
top: 50px;<br />
left: 0px;<br />
display: none;<br />
background-color: #fff; <br />
border-bottom: 1px solid #ccc; <br />
z-index: -100;<br />
padding: 20px 0px;<br />
border: 1px solid #ccc;<br />
}<br />
<br />
.navDropMenu li { /*-- the drop down box --*/<br />
display: block;<br />
float: none;<br />
list-style: none;<br />
height: auto;<br />
padding: 3px 6px; <br />
margin: 0px;<br />
border: 0px;<br />
}<br />
.navDropMenu li:hover { <br />
border: 0px;<br />
}<br />
<br />
.navDropMenu li a { /*-- styles the links within the nav bar li --*/<br />
text-decoration: none; <br />
color: #333;<br />
display: block;<br />
height: auto;<br />
line-height: normal;<br />
padding: 4px 0px 4px 6px;<br />
}<br />
<br />
.navDropMenu li a:hover { /*-- styles the links within the nav bar li --*/<br />
background-color: #f0f0f0;<br />
color: #484848;<br />
}<br />
<br />
.navLinks > li:hover > .navDropMenu {<br />
display: block;<br />
}<br />
<br />
.menuHeader { border-bottom: 1px solid #ccc; display: block; font-weight: bold; font-family: Georgia, Times, "Times New Roman", serif; }<br />
</style><br />
<br />
<style type="text/css" media="print"><br />
#topNav { display: none;}<br />
</style><br />
</head><br />
<div id="top-section-bar"></div><br />
<header id="topNav"><br />
<nav id="navContainer"><br />
<ul class="navLinks"><br />
<li class="navSingleLink"><br />
<a href="https://2014.igem.org" style="padding-left: 10px; padding-right: 10px;"><img src="https://static.igem.org/mediawiki/2014/2/22/Logo2014v2.png" /></a><br />
</li><br />
<li><br />
<a href="#">ABOUT</a><br />
<div class="navDropMenu"><br />
</html>{{Nav/About}}<html><br />
</div><br />
</li><br />
<li><br />
<a href="#" class="dropToggle">COMPETITION</a><br />
<div class="navDropMenu"><br />
</html>{{Nav/Competition}}<html><br />
</div><br />
</li><br />
<li><br />
<a href="#">TEAMS</a><br />
<div class="navDropMenu"><br />
</html>{{Nav/Teams}}<html><br />
</div><br />
</li><br />
<li><br />
<a href="#">RESOURCES</a><br />
<div class="navDropMenu"><br />
</html>{{Nav/Resources}}<html><br />
</div><br />
</li><br />
<li class="navSingleLink"><br />
<a href="https://igem.org/Contact">CONTACT</a><br />
</li><br />
</ul><br />
</nav><br />
</header><br />
<html></div>Vinoohttp://2014.igem.org/Template:Nav/ResourcesTemplate:Nav/Resources2014-06-19T17:05:17Z<p>Vinoo: </p>
<hr />
<div>{{CSS/Nav/Grid12}}<br />
<html><br />
<div class="container_12"><br />
<div class="grid_3"><br />
<ul><span class="menuHeader">General</span><br />
<li><a href="https://igem.org/Previous_iGEM_Competitions">Previous iGEM Competitions</a></li><br />
<li><a href="https://2014.igem.org/Wiki_How-To">Wiki How-To</a></li><br />
<li><a href="https://igem.org/Videos">Videos</a></li><br />
<li><a href="https://igem.org/Forum">Forums</a></li><br />
<li><a href="https://igem.org/FAQ">FAQ</a></li><br />
</ul><br />
</div><br />
<div class="grid_3"><br />
<ul><span class="menuHeader">Lab Resources</span><br />
<li><a href="http://parts.igem.org">Registry of Standard Biological Parts</a></li><br />
<li><a href="http://parts.igem.org">Protocols</a></li><br />
</ul><br />
</div><br />
<div class="grid_3"><br />
<ul><span class="menuHeader">Affiliated</span><br />
<li><a href="https://2014.igem.org/Partner_Offers">Partner Offers</a></li><br />
<li><a href="https://2014.igem.org/Funding">Funding Opportunities</a></li><br />
</ul><br />
</div><br />
</div><br />
</html></div>Vinoohttp://2014.igem.org/Template:Nav/TeamsTemplate:Nav/Teams2014-06-19T17:04:57Z<p>Vinoo: Created page with "{{CSS/Nav/Grid12}} <html> <div class="container_12"> <div class="grid_3"> <ul><span class="menuHeader">Team Links</span> <li><a href="https://igem.org/Team_List?year=2014">2..."</p>
<hr />
<div>{{CSS/Nav/Grid12}}<br />
<html><br />
<div class="container_12"><br />
<div class="grid_3"><br />
<ul><span class="menuHeader">Team Links</span><br />
<li><a href="https://igem.org/Team_List?year=2014">2014 Team List</a></li><br />
<li><a href="https://igem.org/Team_Wikis?year=2014">2014 Team Wikis</a></li><br />
<li><a href="https://igem.org/Team_Parts?year=2014">2014 Team Parts</a></li><br />
<li><a href="https://igem.org/Team_Tracks?year=2014">2014 Team Tracks</a></li><br />
<li><a href="https://igem.org/Team_Judging?year=2014">2014 Team Judging Forms</a></li><br />
</ul><br />
</div><br />
</div><br />
</html></div>Vinoohttp://2014.igem.org/Template:CSS/MainTemplate:CSS/Main2014-05-22T19:36:19Z<p>Vinoo: </p>
<hr />
<div><html><br />
<head><br />
<style type="text/css"><br />
<br />
#contentSub, #footer-box, #catlinks, #search-controls, #p-logo, .printfooter, .visualClear {display: none;} /*-- hides default wiki settings --*/<br />
<br />
.firstHeading {<br />
width: 975px; <br />
margin: 0px auto;<br />
padding-top: 100px;<br />
margin-bottom: 20px;<br />
font-family: Georgia, Times, "Times New Roman", serif; <br />
}<br />
<br />
h1, h2, h3, h4, h5 { font-family: Georgia, Times, "Times New Roman", serif;}<br />
<br />
#top-section { /*-- styling for default menu bar (edit, page, history, etc.) --*/<br />
background-color: #383838;<br />
border: 0 none;<br />
height: 14px;<br />
z-index: 100;<br />
top: 0;<br />
position: fixed;<br />
width: 975px; <br />
left: 50%; <br />
margin-left: -487px;<br />
}<br />
<br />
#top-section-bar { /*-- styling full width bar which hides behind default menu bar (edit, page, history, etc.) --*/<br />
background-color: #383838;<br />
height: 14px;<br />
display: block;<br />
z-index: 10;<br />
position: fixed;<br />
width: 100%;<br />
top: 0;<br />
}<br />
<br />
#menubar a:link, #menubar a:active, #menubar a:visited, #menubar a:hover, #menubar:hover { /*-- styling for default menu bar links (edit, page, history, etc.) --*/<br />
color: #727272; <br />
text-decoration: none; <br />
background-color: transparent;<br />
}<br />
<br />
body { <br />
background-color: #fff;<br />
}<br />
<br />
#globalWrapper, #content { /*-- changes default wiki settings --*/<br />
width: 100%; <br />
height: 100%;<br />
border: 0px;<br />
background-color: transparent;<br />
margin: 0px;<br />
padding: 0px;<br />
}<br />
<br />
html, body, .wrapper { /*-- changes default wiki settings --*/<br />
width: 100%; <br />
height: 100%; <br />
background-color: transparent; <br />
}<br />
<br />
#contentcontainer { /*-- creates container for all content on page --*/<br />
font-family: Arial, Helvetica, sans-serif; <br />
font-weight: normal; <br />
font-size: 14px; <br />
color: #414141;<br />
width: 960px; <br />
margin-left: auto; <br />
margin-right: auto; <br />
background-color: #transparent; <br />
margin-top: 0px; <br />
}<br />
<br />
.sidemenu, .sidemenu li { <br />
list-style-type: none; <br />
list-style-image: none; <br />
font-family: verdana; <br />
text-decoration: none; <br />
color:#000; <br />
font-size: 14px;<br />
}<br />
<br />
.sidemenu li {display: block;}<br />
<br />
.sidemenu a {<br />
text-decoration:none; <br />
color: #000;<br />
display: block; <br />
width: 180px; <br />
height: 100%; <br />
padding: 3px 5px; <br />
transition: .25s ease-in-out;<br />
-moz-transition: .25s ease-in-out;<br />
-webkit-transition: .25s ease-in-out;<br />
} <br />
<br />
.sidemenu a.greyout { color: #909090; }<br />
<br />
.sidemenu a:hover {<br />
color:#666; <br />
background-color: #d9f5aa;<br />
}<br />
<br />
.sub-sidemenu {font-size: 10px; margin-bottom: 20px; color: #666; display: none;}<br />
.sub-sidemenu a {color: #666;}<br />
<br />
div.underconst<br />
{<br />
padding:10px;<br />
border-radius:5px;<br />
background-color:pink;<br />
text-align:center;<br />
}<br />
<br />
a.anchor{display: block; position: relative; top: -80px; visibility: hidden;}<br />
<br />
.contentpara {margin-bottom: 30px;}<br />
<br />
span.email{font-family: monospace; font-weight: normal;}<br />
<br />
fieldset {border: 1px solid #337f53;}<br />
<br />
.greyout {color: #A0A0A0;}<br />
.highlightme {background-color: #FFFF00;}<br />
<br />
#alertContainer {border: 2px solid red; margin-bottom: 10px; width: 936px;}<br />
#annContainer {margin-left: 8px;}<br />
#newsContainer {border: 1px solid #ccc;}<br />
<br />
.newsTitle {<br />
display: block; <br />
color: #414141;<br />
font-size: 25px; <br />
font-family: Georgia, Times, "Times New Roman", serif;<br />
padding: 10px 15px 5px 10px; <br />
border-bottom: 1px solid #ccc; <br />
margin-bottom: 0px; <br />
}<br />
<br />
.newsItem {<br />
border-bottom: 1px solid #ccc; <br />
display: block; <br />
padding: 5px 15px 0px 10px; <br />
margin-bottom: 0px; <br />
}<br />
<br />
.newsItem h3 {<br />
width: auto; <br />
display: inline; <br />
font-size: 14px; <br />
font-family: Arial, Helvetica, sans-serif; <br />
padding: 0px; <br />
margin: 0px;<br />
}<br />
<br />
.newsItem img {<br />
float: right; <br />
clear: right; <br />
width: 80px; <br />
padding-left: 15px;<br />
display: inline-block; <br />
}<br />
<br />
.newsItem .newsDate {<br />
font-style: italic; <br />
font-size: 14px; <br />
display: inline-block; <br />
color: #999; <br />
float: right; <br />
padding: 0px 0px 10px 15px;<br />
}<br />
<br />
.newsItem p, .newsItem ul, .newsItem li {<br />
padding: 0px; <br />
margin-left: 20px; <br />
font-size: 12px; <br />
line-height: 1.2;<br />
}<br />
<br />
.newsItem p {margin-top: 10px;}<br />
<br />
.annItem {<br />
border: 2px solid #96d359; <br />
display: block; <br />
padding: 0px 15px 10px 10px; <br />
margin-bottom: 18px; <br />
position: relative; <br />
height: 160px; <br />
vertical-align: middle;<br />
}<br />
<br />
.annItem .annCentered {<br />
display: table-cell; <br />
vertical-align: middle; <br />
height: 160px;<br />
}<br />
<br />
.annCentered h3 {<br />
padding: 0px;<br />
display: block; <br />
margin-left: auto; <br />
margin-right: auto; <br />
text-align: center;<br />
}<br />
<br />
.annItem ul, .annItem li {padding: 0px; margin: 0px;}<br />
.annItem li {list-style: none; margin: 5px}<br />
<br />
</style><br />
</style><br />
</html></div>Vinoohttp://2014.igem.org/Template:NavBarTemplate:NavBar2014-05-20T20:40:40Z<p>Vinoo: </p>
<hr />
<div><html><br />
<head><br />
<style type="text/css"><br />
#topNav { /*-- creates styled 100% width fixed navigation bar --*/<br />
width: 100%; <br />
position: fixed; <br />
top: 14px; <br />
height: 50px; <br />
background-color: #f0f0f0; <br />
border-bottom: 1px solid #ccc; <br />
z-index: 1000;<br />
}<br />
<br />
#navContainer { /*-- creates centered container for nav bar --*/<br />
width: 975px; <br />
height: 100%; <br />
margin: 0px auto; <br />
position: relative; <br />
font-family: Arial, sans-serif;<br />
}<br />
<br />
.navLinks { /*-- clears style for nav bar ul --*/<br />
margin: 0px; <br />
height: 100%; <br />
}<br />
<br />
.navLinks li { /*-- styles nav bar li, the nav bar elements --*/<br />
display: inline-block;<br />
float: left;<br />
font-size: 12px;<br />
height: 49px;<br />
padding: 0px; <br />
margin: 0px; <br />
border: 1px solid transparent;<br />
}<br />
<br />
.navLinks li:hover { <br />
background-color: #fff;<br />
border: 1px solid #ccc;<br />
border-bottom: 1px solid #fff;<br />
}<br />
<br />
.navLinks > .navSingleLink:hover { <br />
border-bottom: 1px solid #ccc;<br />
}<br />
<br />
.navLinks li > a { /*-- styles the links within the nav bar li --*/<br />
text-decoration: none; <br />
line-height: 50px;<br />
color: #000;<br />
padding-left: 30px;<br />
padding-right: 30px;<br />
display: block;<br />
height: 100%;<br />
}<br />
<br />
.navlinks li > a:hover {<br />
color: #fff;<br />
<br />
} <br />
.navDropMenu { /*-- the drop down box --*/<br />
width: 100%;<br />
position: absolute;<br />
top: 50px;<br />
left: 0px;<br />
display: none;<br />
background-color: #fff; <br />
border-bottom: 1px solid #ccc; <br />
z-index: -100;<br />
padding: 20px 0px;<br />
border: 1px solid #ccc;<br />
}<br />
<br />
.navDropMenu li { /*-- the drop down box --*/<br />
display: block;<br />
float: none;<br />
list-style: none;<br />
height: auto;<br />
padding: 3px 6px; <br />
margin: 0px;<br />
border: 0px;<br />
}<br />
.navDropMenu li:hover { <br />
border: 0px;<br />
}<br />
<br />
.navDropMenu li a { /*-- styles the links within the nav bar li --*/<br />
text-decoration: none; <br />
color: #333;<br />
display: block;<br />
height: auto;<br />
line-height: normal;<br />
padding: 4px 0px 4px 6px;<br />
}<br />
<br />
.navDropMenu li a:hover { /*-- styles the links within the nav bar li --*/<br />
background-color: #f0f0f0;<br />
color: #484848;<br />
}<br />
<br />
.navLinks > li:hover > .navDropMenu {<br />
display: block;<br />
}<br />
<br />
.menuHeader { border-bottom: 1px solid #ccc; display: block; font-weight: bold; font-family: Georgia, Times, "Times New Roman", serif; }<br />
</style><br />
<br />
<style type="text/css" media="print"><br />
#topNav { display: none;}<br />
</style><br />
</head><br />
<div id="top-section-bar"></div><br />
<header id="topNav"><br />
<nav id="navContainer"><br />
<ul class="navLinks"><br />
<li class="navSingleLink"><br />
<a href="https://2014.igem.org" style="padding-left: 10px; padding-right: 10px;"><img src="https://static.igem.org/mediawiki/2014/2/22/Logo2014v2.png" /></a><br />
</li><br />
<li><br />
<a href="#">ABOUT</a><br />
<div class="navDropMenu"><br />
</html>{{Nav/About}}<html><br />
</div><br />
</li><br />
<li><br />
<a href="#" class="dropToggle">COMPETITION</a><br />
<div class="navDropMenu"><br />
</html>{{Nav/Competition}}<html><br />
</div><br />
</li><br />
<li><br />
<a href="#">RESOURCES</a><br />
<div class="navDropMenu"><br />
</html>{{Nav/Resources}}<html><br />
</div><br />
</li><br />
<li class="navSingleLink"><br />
<a href="https://igem.org/Contact">CONTACT</a><br />
</li><br />
</ul><br />
</nav><br />
</header><br />
<html></div>Vinoohttp://2014.igem.org/Template:NavBarTemplate:NavBar2014-05-20T20:39:18Z<p>Vinoo: </p>
<hr />
<div><html><br />
<head><br />
<style type="text/css"><br />
#topNav { /*-- creates styled 100% width fixed navigation bar --*/<br />
width: 100%; <br />
position: fixed; <br />
top: 14px; <br />
height: 50px; <br />
background-color: #f0f0f0; <br />
border-bottom: 1px solid #ccc; <br />
z-index: 1000;<br />
}<br />
<br />
#navContainer { /*-- creates centered container for nav bar --*/<br />
width: 975px; <br />
height: 100%; <br />
margin: 0px auto; <br />
position: relative; <br />
font-family: Arial, sans-serif;<br />
}<br />
<br />
.navLinks { /*-- clears style for nav bar ul --*/<br />
margin: 0px; <br />
height: 100%; <br />
}<br />
<br />
.navLinks li { /*-- styles nav bar li, the nav bar elements --*/<br />
display: inline-block;<br />
float: left;<br />
font-size: 12px;<br />
height: 49px;<br />
padding: 0px; <br />
margin: 0px; <br />
border: 1px solid transparent;<br />
}<br />
<br />
.navLinks li:hover { <br />
background-color: #fff;<br />
border: 1px solid #ccc;<br />
border-bottom: 1px solid #fff;<br />
}<br />
<br />
.navLinks > .navSingleLink:hover { <br />
border-bottom: 1px solid #ccc;<br />
}<br />
<br />
.navLinks li > a { /*-- styles the links within the nav bar li --*/<br />
text-decoration: none; <br />
line-height: 50px;<br />
color: #000;<br />
padding-left: 30px;<br />
padding-right: 30px;<br />
display: block;<br />
height: 100%;<br />
}<br />
<br />
.navlinks li > a:hover {<br />
color: #fff;<br />
<br />
} <br />
.navDropMenu { /*-- the drop down box --*/<br />
width: 100%;<br />
position: absolute;<br />
top: 50px;<br />
left: 0px;<br />
display: none;<br />
background-color: #fff; <br />
border-bottom: 1px solid #ccc; <br />
z-index: -100;<br />
padding: 20px 0px;<br />
border: 1px solid #ccc;<br />
}<br />
<br />
.navDropMenu li { /*-- the drop down box --*/<br />
display: block;<br />
float: none;<br />
list-style: none;<br />
height: auto;<br />
padding: 3px 6px; <br />
margin: 0px;<br />
border: 0px;<br />
}<br />
.navDropMenu li:hover { <br />
border: 0px;<br />
}<br />
<br />
.navDropMenu li a { /*-- styles the links within the nav bar li --*/<br />
text-decoration: none; <br />
color: #333;<br />
display: block;<br />
height: auto;<br />
line-height: normal;<br />
padding: 4px 0px 4px 6px;<br />
}<br />
<br />
.navDropMenu li a:hover { /*-- styles the links within the nav bar li --*/<br />
background-color: #f0f0f0;<br />
color: #484848;<br />
}<br />
<br />
.navLinks > li:hover > .navDropMenu {<br />
display: block;<br />
}<br />
<br />
.menuHeader { border-bottom: 1px solid #ccc; display: block; font-weight: bold; font-family: Georgia, Times, "Times New Roman", serif; }<br />
</style><br />
<br />
<style type="text/css" media="print"><br />
#topNav { position: relative;}<br />
</style><br />
</head><br />
<div id="top-section-bar"></div><br />
<header id="topNav"><br />
<nav id="navContainer"><br />
<ul class="navLinks"><br />
<li class="navSingleLink"><br />
<a href="https://2014.igem.org" style="padding-left: 10px; padding-right: 10px;"><img src="https://static.igem.org/mediawiki/2014/2/22/Logo2014v2.png" /></a><br />
</li><br />
<li><br />
<a href="#">ABOUT</a><br />
<div class="navDropMenu"><br />
</html>{{Nav/About}}<html><br />
</div><br />
</li><br />
<li><br />
<a href="#" class="dropToggle">COMPETITION</a><br />
<div class="navDropMenu"><br />
</html>{{Nav/Competition}}<html><br />
</div><br />
</li><br />
<li><br />
<a href="#">RESOURCES</a><br />
<div class="navDropMenu"><br />
</html>{{Nav/Resources}}<html><br />
</div><br />
</li><br />
<li class="navSingleLink"><br />
<a href="https://igem.org/Contact">CONTACT</a><br />
</li><br />
</ul><br />
</nav><br />
</header><br />
<html></div>Vinoo