Difference between revisions of "Team:Cologne-Duesseldorf/Parts"

(Prototype team page)
 
Line 1: Line 1:
−
{{Cologne-Duesseldorf}}
+
{{Template:Cologne-Duesseldorf/css}}
 +
{{Template:Cologne-Duesseldorf/header}}
 
<html>
 
<html>
 +
<body>
 +
<div id="overlay"></div>
 +
<div id="container">
 +
<div id="paper">
 +
<section id="article">
 +
<!-- Headings are written as <h1>NameOfYourHeading</h1>, <h2>NameOfYourHeading</h2> and so on. The number corresponds to the level of the heading, just alike in google docs ect. -->
 +
<!-- Following the heading tag a <hr> -tag creates a nice horizontal line. It is not necessary, but i like it -->
 +
<!-- Normal text is written within paragraph tags: <p>Your text here</p> -->
 +
<!-- Images are embedded via the img tag, with the wiki url insige the src="" parentheses: <img src="https://static.igem.org/mediawiki/2017/8/8a/T--Cologne-Duesseldorf--Nootkatone-Expression-3D.svg"> Note that there is no closing </img> tag -->
 +
<!-- Bold text is within <b></b>, italic text inside <i></i> tags. -->
 +
<!-- Links: <a href="the url includng http...">The text visible on the page</a> -->
 +
<!-- Highlight boxes: <span class="label">visible on the page</span> -->
 +
<!-- For callouts, tables etc. look at the source code of https://2017.igem.org/Team:Cologne-Duesseldorf/Test or just ask Marvin -->
 +
 +
<!-- Pro tip: Don't write your stuff inside the iGEM edit box, but use a proper text editor like notepad++ or atom. And use indents (tab key) so that the text remains legible.  -->
 +
 +
  
−
 
+
−
 
+
−
 
+
<!-- Begin writing here -->
−
 
+
<!-- Change the following template as you write along: -->
−
 
+
<h1>Heading 1</h1>
−
<div class="column full_size">
+
<hr>
−
 
+
<p>Some sample text</p>
−
<h1>Parts</h1>
+
<h2>Heading 2</h2>
−
 
+
<hr>
−
<p>Each team will make new parts during iGEM and will submit them to the Registry of Standard Biological Parts. The iGEM software provides an easy way to present the parts your team has created. The <code>&lt;groupparts&gt;</code> tag (see below) will generate a table with all of the parts that your team adds to your team sandbox.</p>
+
<p>Some <b>sample text</b>, <i>sample text</i>, <span class="label">sample text</span>.</p>
−
<p>Remember that the goal of proper part documentation is to describe and define a part, so that it can be used without needing to refer to the primary literature. Registry users in future years should be able to read your documentation and be able to use the part successfully. Also, you should provide proper references to acknowledge previous authors and to provide for users who wish to know more.</p>
+
−
 
+
−
 
+
−
</div>
+
−
 
+
−
 
+
−
 
+
−
 
+
−
 
+
−
<div class="column half_size">
+
−
<div class="highlight">
+
−
<h5>Note</h5>
+
<!-- End writing here -->
−
<p>Note that parts must be documented on the <a href="http://parts.igem.org/Main_Page"> Registry</a>. This page serves to <i>showcase</i> the parts you have made. Future teams and other users and are much more likely to find parts by looking in the Registry than by looking at your team wiki.</p>
+
</section>
−
</div>
+
<!-- End Paper-->
−
</div>
+
</div>
−
 
+
<!-- End Container -->
−
 
+
</div>
−
 
+
</body>
−
 
+
−
<div class="column half_size">
+
−
 
+
−
<h5>Adding parts to the registry</h5>
+
−
<p>You can add parts to the Registry at our <a href="http://parts.igem.org/Add_a_Part_to_the_Registry">Add a Part to the Registry</a> link.</p>
+
−
<p>We encourage teams to start completing documentation for their parts on the Registry as soon as you have it available. The sooner you put up your parts, the better you will remember all the details about your parts. Remember, you don't need to send us the DNA sample before you create an entry for a part on the Registry. (However, you <b>do</b> need to send us the DNA sample before the Jamboree. If you don't send us a DNA sample of a part, that part will not be eligible for awards and medal criteria.)</p>
+
−
</div>
+
−
 
+
−
 
+
−
 
+
−
 
+
−
 
+
−
<div class="column half_size">
+
−
 
+
−
<h5>What information do I need to start putting my parts on the Registry?</h5>
+
−
<p>The information needed to initially create a part on the Registry is:</p>
+
−
<ul>
+
−
<li>Part Name</li>
+
−
<li>Part type</li>
+
−
<li>Creator</li>
+
−
<li>Sequence</li>
+
−
<li>Short Description (60 characters on what the DNA does)</li>
+
−
<li>Long Description (Longer description of what the DNA does)</li>
+
−
<li>Design considerations</li>
+
−
</ul>
+
−
 
+
−
<p>
+
−
We encourage you to put up <em>much more</em> information as you gather it over the summer. If you have images, plots, characterization data and other information, please also put it up on the part page. </p>
+
−
 
+
−
</div>
+
−
 
+
−
 
+
−
<div class="column half_size">
+
−
 
+
−
<h5>Inspiration</h5>
+
−
<p>We have a created  a <a href="http://parts.igem.org/Well_Documented_Parts">collection of well documented parts</a> that can help you get started.</p>
+
−
 
+
−
<p> You can also take a look at how other teams have documented their parts in their wiki:</p>
+
−
<ul>
+
−
<li><a href="https://2014.igem.org/Team:MIT/Parts"> 2014 MIT </a></li>
+
−
<li><a href="https://2014.igem.org/Team:Heidelberg/Parts"> 2014 Heidelberg</a></li>
+
−
<li><a href="https://2014.igem.org/Team:Tokyo_Tech/Parts">2014 Tokyo Tech</a></li>
+
−
</ul>
+
−
</div>
+
−
 
+
−
<div class="column full_size">
+
−
<h5>Part Table </h5>
+
−
 
+
−
<p>Please include a table of all the parts your team has made during your project on this page. Remember part characterization and measurement data must go on your team part pages on the Registry. </p>
+
−
 
+
−
<div class="highlight">
+
−
 
+
−
 
+
−
</html>
+
−
<groupparts>iGEM17 Cologne-Duesseldorf</groupparts>
+
−
 
+
−
<html>
+
−
</div>
+
−
</div>
+
−
 
+
−
 
+
−
 
+
−
 
+
 
</html>
 
</html>
 +
{{Template:Cologne-Duesseldorf/footer}}
 +
{{Template:Cologne-Duesseldorf/js}}

Revision as of 09:39, 6 September 2017

Heading 1

Some sample text

Heading 2

Some sample text, sample text, sample text.