Requirements/Wiki

From 2014.igem.org

(Difference between revisions)
m
Line 10: Line 10:
* 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 the following can happen:
* 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 the following can happen:
<center><img src="https://static.igem.org/mediawiki/2013/3/3b/Flash_fail.png" style="width:500px"></center>
<center><img src="https://static.igem.org/mediawiki/2013/3/3b/Flash_fail.png" style="width:500px"></center>
-
<li> FLASH is not permitted on the iGEM 2014 websites. See image above in 1.  
+
<li> FLASH is not permitted on the iGEM 2014 websites. See image above in 1. <br><br>
*''Note:'' Adobe flash is 100% proprietary and you can't 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.
*''Note:'' Adobe flash is 100% proprietary and you can't 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.
Line 23: Line 23:
<li> All iGEM Team Wikis must include the iGEM header. 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.
<li> All iGEM Team Wikis must include the iGEM header. 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.
</li>
</li>
-
 
+
</ol>
 +
<br>
 +
<p>For wiki FAQs, see the <a href="https://igem.org/FAQ">FAQ</a> page.</p>
<div style="padding-top:15px;">
<div style="padding-top:15px;">
<strong>NOTE:</strong> <br>
<strong>NOTE:</strong> <br>

Revision as of 21:31, 18 August 2014

Please note that all information on this page is in a draft version. Please check back often for details.

Wiki requirements for iGEM 2014:
  1. 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 the following can happen:
  2. FLASH is not permitted on the iGEM 2014 websites. See image above in 1.

    *''Note:'' Adobe flash is 100% proprietary and you can't 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.
  3. 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.
  4. All pages of a team wiki must be in the team's namespace.
  5. The team's wiki must include a link to the completed Safety form and an attributions section.
  6. All iGEM Team Wikis must include the iGEM header. 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.

For wiki FAQs, see the FAQ page.

NOTE:
All content on this wiki is available under the Creative Commons Attribution-ShareAlike 3.0 Unported license (or any later version).