Wiki How-To

{{CSS/Main}}
{{NavBar}}
<html>
<div id="contentcontainer">

<h3>Wiki Freeze - October 17th  (11:59 PM - EDT) </h3>

<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 />




<h4 id="wikitemplates"> Wiki Templates </h4>
<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>
<a href="https://2014.igem.org/WikitemplateA_home ">Wiki Template A </a></br>
<a href="https://2014.igem.org/WikitemplateB_home ">Wiki Template B </a>
<BR><BR>




<h4> Perspectives from an iGEM veteran. </h4>




<table cellspacing="10" style="text-align: justify;" width="965px">

<tr> 

<td width="48%">
Hello iGEMers!
<br>
I was also part of an iGEM team!
<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>
<b> 1.- Test your webpage layout: is information easy to find?</b> </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>
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>
<b> 2.- Look at other teams’ code, see how they documented and what resources they used. </b><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>
<b> 3.- Start working on your documentation early on.  </b> <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>

</td>

<td width="4%"></td>

<td width="48%" valign="top">
<b> 4.- Name your images according to the project and keep them all in a folder on your computer. </b> <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>
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>
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>
<b> 5.- Do not leave everything to the last minute! </b>

<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>


<p> I hope this helps and if you have any questions, feel free to email me or send me a tweet! </p>
<i> ana at igem dot org </i>
<br>
<i> <A HREF="https://twitter.com/anita_sifuentes" > @anita_sifuentes </A> </i>

</td>
</tr>
</table>


<!--

	<h3>Wiki Freeze - October 17th</h3>
	<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>
	<ul><b>Do not...</b>
		<li>wait till the last minute</li>
		<li>try to upload everything at once</li>
	</ul>

<br />

	<h3>2014.igem.org/Team:Team_Name</h3>
	<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 />

	<h3>Upload to 2014.igem.org server</h3>
	<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.
	</p>

	<ul>Use the <a href="https://2014.igem.org/Special:Upload">wiki upload tool</a> to upload your files. 
		<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>
	</ul>

		<h4>Upload to 2014.igem.org server</h4>
		<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 />

	<h3>No Adobe Flash</h3>	
	<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> 

	<h3>Deadlines and the Wiki Freeze</h3>
	<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>
	<p>The team's wiki must include a link to the completed Safety form and an attributions section.</p>

	<h3>iGEM Logo</h3>
	<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>

	<h3>The iGEM Login Bar</h3>
	<p>The iGEM Login Bar is a 20 pixel high, full-width menu bar that exists on all 2014.igem.org pages. It contains:
		<ul>
			<li>wiki tools (edit, history, watch, etc.)</li>
			<li>login</li>
		</ul>
	All iGEM 2014 Team Wikis are required to have the Login Bar. Please keep this in mind as you design your wiki.</p>

-->



</div>
</html>
{{MainPage2014/Footer}}