Team:SMTexas

From 2014hs.igem.org

(Difference between revisions)
Line 1: Line 1:
-
<!-- *** What falls between these lines is the Alert Box!  You can remove it from your pages once you have read and understood the alert *** -->
+
<!doctype html>
-
 
+
<html>
<html>
-
<div id="box" style="width: 700px; margin-left: 137px; padding: 5px; border: 3px solid #fe2b33; /*background-color: #fe2b33;*/">
+
<head>
-
<div id="template" style="text-align: center; font-weight: bold; font-size: large; /*color: #f6f6f6*/; padding: 5px;">
+
<meta charset="utf-8">
-
This is a template page. READ THESE INSTRUCTIONS.
+
<!-- TemplateBeginEditable name="doctitle" -->
-
</div>
+
<title>Untitled Document</title>
-
<div id="instructions" style="text-align: center; font-weight: normal; font-size: small; /*color: #f6f6f6*/; padding: 5px;">
+
<!-- TemplateEndEditable -->
-
You are provided with this team page template with which to start the iGEM season.  You may choose to personalize it to fit your team but keep the same "look." Or you may choose to take your team wiki to a different level and design your own wiki.  You can find some examples <a href="https://2009.igem.org/Help:Template/Examples">HERE</a>.
+
<!-- TemplateBeginEditable name="head" -->
-
</div>
+
<!-- TemplateEndEditable -->
-
<div id="warning" style="/*text-align: center;*/ font-weight: bold; font-size: small; /*color: #f6f6f6*/; padding: 5px;">
+
<style type="text/css">
-
You <strong>MUST</strong> have the following information on your wiki:
+
<!--
-
<ul style="font-weight:normal;">
+
body {
-
<li>a team description</li>
+
font: 100%/1.4 Verdana, Arial, Helvetica, sans-serif;
-
<li>project description</li>
+
background-color: #42413C;
-
<li>safety information (did your team take a safety training course? were you supervised in the lab?)</li>
+
margin: 0;
-
<li>team attribution (who did what part of your project?)</li>
+
padding: 0;
-
</ul>
+
color: #000;
-
You may also wish to add other page such as:
+
}
-
<ul style="font-weight:normal;">
+
-
<li>lab notebook</li>
+
-
<li>sponsor information</li>
+
-
<li>other information</li>
+
-
</ul>
+
-
REMEMBER, keep all of your pages within your teams namespace. <br><span style="font-weight:normal; font-style:italic;">Example: 2013hs.igem.org/Team:SMTexas/Our_Pets</span>
+
-
</div>
+
-
</div>
+
-
</html>
+
-
<!-- *********************** End of the alert box *********************** -->
+
/* ~~ Element/tag selectors ~~ */
 +
ul, ol, dl { /* Due to variations between browsers, it's best practices to zero padding and margin on lists. For consistency, you can either specify the amounts you want here, or on the list items (LI, DT, DD) they contain. Remember that what you do here will cascade to the .nav list unless you write a more specific selector. */
 +
padding: 0;
 +
margin: 0;
 +
}
 +
h1, h2, h3, h4, h5, h6, p {
 +
margin-top: 0; /* removing the top margin gets around an issue where margins can escape from their containing div. The remaining bottom margin will hold it away from any elements that follow. */
 +
padding-right: 15px;
 +
padding-left: 15px; /* adding the padding to the sides of the elements within the divs, instead of the divs themselves, gets rid of any box model math. A nested div with side padding can also be used as an alternate method. */
 +
}
 +
a img { /* this selector removes the default blue border displayed in some browsers around an image when it is surrounded by a link */
 +
border: none;
 +
}
 +
/* ~~ Styling for your site's links must remain in this order - including the group of selectors that create the hover effect. ~~ */
 +
a:link {
 +
color: #42413C;
 +
text-decoration: underline; /* unless you style your links to look extremely unique, it's best to provide underlines for quick visual identification */
 +
}
 +
a:visited {
 +
color: #6E6C64;
 +
text-decoration: underline;
 +
}
 +
a:hover, a:active, a:focus { /* this group of selectors will give a keyboard navigator the same hover experience as the person using a mouse. */
 +
text-decoration: none;
 +
}
 +
/* ~~this fixed width container surrounds the other divs~~ */
 +
.container {
 +
width: 960px;
 +
background-color: #FFF;
 +
margin: 0 auto; /* the auto value on the sides, coupled with the width, centers the layout */
 +
}
-
{|align="justify"
+
/* ~~ the header is not given a width. It will extend the full width of your layout. It contains an image placeholder that should be replaced with your own linked logo ~~ */
-
|You can write a background of your team here. Give us a background of your team, the members, etc. Or tell us more about something of your choosing.
+
.header {
-
|[[Image:SMTexas_logo.png|200px|right|frame]]
+
background-color: #ADB96E;
-
|-
+
}
-
|
+
-
''Tell us more about your project.  Give us background.  Use this as the abstract of your project.  Be descriptive but concise (1-2 paragraphs)''
+
-
|[[Image:SMTexas_team.png|right|frame|Your team picture]]
+
-
|-
+
-
|
+
-
|align="center"|[[Team:SMTexas | Team SMTexas]]
+
-
|}
+
-
<!--- Team Information Link --->
+
/* ~~ These are the columns for the layout. ~~
-
{| style="color:#1b2c8a;background-color:#0c6;" cellpadding="3" cellspacing="1" border="1" bordercolor="#fff" width="62%" align="center"
+
1) Padding is only placed on the top and/or bottom of the divs. The elements within these divs have padding on their sides. This saves you from any "box model math". Keep in mind, if you add any side padding or border to the div itself, it will be added to the width you define to create the *total* width. You may also choose to remove the padding on the element in the div and place a second div within it with no width and the padding necessary for your design.
-
!align="center"|[https://igem.org/Team.cgi?year=2013&division=high_school&team_name=SMTexas Official Team Profile]
+
-
|}
+
-
===Team===
+
2) No margin has been given to the columns since they are all floated. If you must add margin, avoid placing it on the side you're floating toward (for example: a right margin on a div set to float right). Many times, padding can be used instead. For divs where this rule must be broken, you should add a "display:inline" declaration to the div's rule to tame a bug where some versions of Internet Explorer double the margin.
-
Tell us about your team, your school!
+
-
We are a nondenominational independent school in Dallas, Texas.
+
-
===Project===
+
3) Since classes can be used multiple times in a document (and an element can also have multiple classes applied), the columns have been assigned class names instead of IDs. For example, two sidebar divs could be stacked if necessary. These can very easily be changed to IDs if that's your preference, as long as you'll only be using them once per document.
-
Lung cancer is the leading cause of cancer-related death around the world. Early detection systems would enable us to diagnose the disease at a time when therapeutic intervention would be most effective. Noninvasive breath sampling has the potential to save lives as approximately 86% of lung cancer patients die within five years of diagnosis. Early detection improves survival rate by 50% from stage III to stage I of the cancer. Breath biochemical sensors also have important applications for other diseases. According to the World Health Organization’s latest report on noncommunicable diseases (NCDs), these “diseases are the leading global causes of death, causing more deaths than all other causes combined.” Further research into these noninvasive tests while maintaining the tests’ accuracy and sensitivity could have a major impact on survival rates of other NCDs. Tests of this nature would reduce inequity and provide improved means of treatment for affected individuals regardless of nationality, income, or access to healthcare.
+
-
While invasive techniques, such as immunofluorescence and Western Blotting already exist to detect the Epidermal Growth Factor Receptor (EGFR) biomarker, breath chemical tests via genetically modified Escherichia coli bacteria would be a novel and versatile method of lung cancer screening. Twenty-two volatile organic compounds (VOCs) have been found to be unique to the breath of affected patients, creating a viable “fingerprint” for reliable detection (Horvath et al.). We will utilize these concepts to create a biosensor for lung cancer.
+
4) If you prefer your nav on the left instead of the right, simply float these columns the opposite direction (all left instead of all right) and they'll render in reverse order. There's no need to move the divs around in the HTML source.
-
Our team will design a system combining existing BioBricks along with novel synthesized biological parts to create a whole-cell bacterial sensor. We will attempt to create a breath biosensor through noninvasive intervention of lung cancer. Implementing recombinant DNA technology, the bacteria will be able to respond to environmental queues through a receptor-dependent pathway. The construct will fuse a DNA response element with reporter genes to create a portable biosensor. We are currently investigating E. coli promoters or alternative sigma factors in relation to our intended target compounds.
+
*/
 +
.sidebar1 {
 +
float: right;
 +
width: 180px;
 +
background-color: #EADCAE;
 +
padding-bottom: 10px;
 +
}
 +
.content {
-
===Notebook===
+
padding: 10px 0;
-
On Tuesday, February 18th, Vikrant R, Rohin M, and Gopal R, inoculated bacterial strains A & B onto LB agar with ampicillin & kanamycin and incubated overnight at 37C.
+
width: 780px;
 +
float: right;
 +
}
-
On Wednesday, February 19th, Vikrant R & Rohin M transferred one colony from each of A & B and inoculated in LB BROTH with ampicillin & kanamycin and placed in shaking water bath at 37C.
+
/* ~~ This grouped selector gives the lists in the .content area space ~~ */
 +
.content ul, .content ol {
 +
padding: 0 15px 15px 40px; /* this padding mirrors the right padding in the headings and paragraph rule above. Padding was placed on the bottom for space between other elements on the lists and on the left to create the indention. These may be adjusted as you wish. */
 +
}
-
The next step is to perform a miniprep, which will allow us to extract plasmid from each A & B bacterial strains, which will then allow us do the restriction digest and ligation.
+
/* ~~ The navigation list styles (can be removed if you choose to use a premade flyout menu like Spry) ~~ */
 +
ul.nav {
 +
list-style: none; /* this removes the list marker */
 +
border-top: 1px solid #666; /* this creates the top border for the links - all others are placed using a bottom border on the LI */
 +
margin-bottom: 15px; /* this creates the space between the navigation on the content below */
 +
}
 +
ul.nav li {
 +
border-bottom: 1px solid #666; /* this creates the button separation */
 +
}
 +
ul.nav a, ul.nav a:visited { /* grouping these selectors makes sure that your links retain their button look even after being visited */
 +
padding: 5px 5px 5px 15px;
 +
display: block; /* this gives the link block properties causing it to fill the whole LI containing it. This causes the entire area to react to a mouse click. */
 +
width: 160px;  /*this width makes the entire button clickable for IE6. If you don't need to support IE6, it can be removed. Calculate the proper width by subtracting the padding on this link from the width of your sidebar container. */
 +
text-decoration: none;
 +
background-color: #C6D580;
 +
}
 +
ul.nav a:hover, ul.nav a:active, ul.nav a:focus { /* this changes the background and text color for both mouse and keyboard navigators */
 +
background-color: #ADB96E;
 +
color: #FFF;
 +
}
-
All of these steps can be seen in the 3A Assembly kit protocols
+
/* ~~ The footer ~~ */
 +
.footer {
 +
padding: 10px 0;
 +
background-color: #CCC49F;
 +
position: relative;/* this gives IE6 hasLayout to properly clear */
 +
clear: both; /* this clear property forces the .container to understand where the columns end and contain them */
 +
}
-
===Results/Conclusions===
+
/* ~~ miscellaneous float/clear classes ~~ */
-
What did you achieve over the course of your semester?
+
.fltrt {  /* this class can be used to float an element right in your page. The floated element must precede the element it should be next to on the page. */
 +
float: right;
 +
margin-left: 8px;
 +
}
 +
.fltlft { /* this class can be used to float an element left in your page. The floated element must precede the element it should be next to on the page. */
 +
float: left;
 +
margin-right: 8px;
 +
}
 +
.clearfloat { /* this class can be placed on a <br /> or empty div as the final element following the last floated div (within the #container) if the #footer is removed or taken out of the #container */
 +
clear:both;
 +
height:0;
 +
font-size: 1px;
 +
line-height: 0px;
 +
}
 +
-->
 +
</style></head>
 +
<body>
-
===Safety===
+
<div class="container">
-
What safety precautions did your team take? Did you take a safety training course? Were you supervised at all times in the lab?
+
  <div class="header"><a href="#"><img src="" alt="Insert Logo Here" name="Insert_logo" width="180" height="90" id="Insert_logo" style="background-color: #C6D580; display:block;" /></a>
-
 
+
    <!-- end .header --></div>
-
 
+
  <div class="sidebar1">
-
===Attributions===
+
    <ul class="nav">
-
Who worked on what?
+
      <li><a href="#">Link one</a></li>
-
 
+
      <li><a href="#">Link two</a></li>
-
 
+
      <li><a href="#">Link three</a></li>
-
===Human Practices===
+
      <li><a href="#">Link four</a></li>
-
What impact does/will your project have on the public? 
+
    </ul>
-
 
+
    <p> The above links demonstrate a basic navigational structure using an unordered list styled with CSS. Use this as a starting point and modify the properties to produce your own unique look. If you require flyout menus, create your own using a Spry menu, a menu widget from Adobe's Exchange or a variety of other javascript or CSS solutions.</p>
-
 
+
    <p>If you would like the navigation along the top, simply move the ul.nav to the top of the page and recreate the styling.</p>
-
===Fun!===
+
    <!-- end .sidebar1 --></div>
-
What was your favorite team snack?? Have a picture of your team mascot?
+
  <div class="content">
-
 
+
    <h1>Instructions</h1>
-
 
+
    <p>Be aware that the CSS for these layouts is heavily commented. If you do most of your work in Design view, have a peek at the code to get tips on working with the CSS for the fixed layouts. You can remove these comments before you launch your site. To learn more about the techniques used in these CSS Layouts, read this article at Adobe's Developer Center - <a href="http://www.adobe.com/go/adc_css_layouts">http://www.adobe.com/go/adc_css_layouts</a>.</p>
-
 
+
    <h2>Clearing Method</h2>
-
<forum_subtle />
+
    <p>Because all the columns are floated, this layout uses a clear:both declaration in the .footer rule.  This clearing technique forces the .container to understand where the columns end in order to show any borders or background colors you place on the .container. If your design requires you to remove the .footer from the .container, you'll need to use a different clearing method. The most reliable will be to add a &lt;br class=&quot;clearfloat&quot; /&gt; or &lt;div  class=&quot;clearfloat&quot;&gt;&lt;/div&gt; after your final floated column (but before the .container closes). This will have the same clearing effect.</p>
 +
    <h3>Logo Replacement</h3>
 +
    <p>An image placeholder was used in this layout in the .header where you'll likely want to place  a logo. It is recommended that you remove the placeholder and replace it with your own linked logo. </p>
 +
    <p> Be aware that if you use the Property inspector to navigate to your logo image using the SRC field (instead of removing and replacing the placeholder), you should remove the inline background and display properties. These inline styles are only used to make the logo placeholder show up in browsers for demonstration purposes. </p>
 +
    <p>To remove the inline styles, make sure your CSS Styles panel is set to Current. Select the image, and in the Properties pane of the CSS Styles panel, right click and delete the display and background properties. (Of course, you can always go directly into the code and delete the inline styles from the image or placeholder there.)</p>
 +
    <h4>Backgrounds</h4>
 +
    <p>By nature, the background color on any div will only show for the length of the content. This means if you're using a background color or border to create the look of a side column, it won't extend all the way to the footer but will stop when the content ends. If the .content div will always contain more content, you can place a border on the .content div to divide it from the column.</p>
 +
    <!-- end .content --></div>
 +
  <div class="footer">
 +
    <p>This .footer contains the declaration position:relative; to give Internet Explorer 6 hasLayout for the .footer and cause it to clear correctly. If you're not required to support IE6, you may remove it.</p>
 +
    <!-- end .footer --></div>
 +
  <!-- end .container --></div>
 +
</body>
 +
</html>

Revision as of 20:14, 3 April 2014

<!doctype html> Untitled Document

The above links demonstrate a basic navigational structure using an unordered list styled with CSS. Use this as a starting point and modify the properties to produce your own unique look. If you require flyout menus, create your own using a Spry menu, a menu widget from Adobe's Exchange or a variety of other javascript or CSS solutions.

If you would like the navigation along the top, simply move the ul.nav to the top of the page and recreate the styling.

Instructions

Be aware that the CSS for these layouts is heavily commented. If you do most of your work in Design view, have a peek at the code to get tips on working with the CSS for the fixed layouts. You can remove these comments before you launch your site. To learn more about the techniques used in these CSS Layouts, read this article at Adobe's Developer Center - http://www.adobe.com/go/adc_css_layouts.

Clearing Method

Because all the columns are floated, this layout uses a clear:both declaration in the .footer rule. This clearing technique forces the .container to understand where the columns end in order to show any borders or background colors you place on the .container. If your design requires you to remove the .footer from the .container, you'll need to use a different clearing method. The most reliable will be to add a <br class="clearfloat" /> or <div class="clearfloat"></div> after your final floated column (but before the .container closes). This will have the same clearing effect.

Logo Replacement

An image placeholder was used in this layout in the .header where you'll likely want to place a logo. It is recommended that you remove the placeholder and replace it with your own linked logo.

Be aware that if you use the Property inspector to navigate to your logo image using the SRC field (instead of removing and replacing the placeholder), you should remove the inline background and display properties. These inline styles are only used to make the logo placeholder show up in browsers for demonstration purposes.

To remove the inline styles, make sure your CSS Styles panel is set to Current. Select the image, and in the Properties pane of the CSS Styles panel, right click and delete the display and background properties. (Of course, you can always go directly into the code and delete the inline styles from the image or placeholder there.)

Backgrounds

By nature, the background color on any div will only show for the length of the content. This means if you're using a background color or border to create the look of a side column, it won't extend all the way to the footer but will stop when the content ends. If the .content div will always contain more content, you can place a border on the .content div to divide it from the column.

This .footer contains the declaration position:relative; to give Internet Explorer 6 hasLayout for the .footer and cause it to clear correctly. If you're not required to support IE6, you may remove it.

Retrieved from "http://2014hs.igem.org/Team:SMTexas"