Difference between revisions of "Team:UANL/Collaborations"

(Prototype team page)
 
Line 1: Line 1:
−
{{UANL}}
+
{{UANL}}{{UANL/CSS}}
 
<html>
 
<html>
  

Revision as of 00:59, 9 October 2019

<style> body {margin:0;font-family:Arial}

.topnav { 

 overflow: hidden;
 background-color: #333;

}

.topnav a { 

 float: left;
 display: block;
 color: #f2f2f2;
 text-align: center;
 padding: 14px 16px;
 text-decoration: none;
 font-size: 17px;

}

.active { 

 background-color: #4CAF50;
 color: white;

}

.topnav .icon { 

 display: none;

}

.dropdown { 

 float: left;
 overflow: hidden;

}

.dropdown .dropbtn { 

 font-size: 17px;    
 border: none;
 outline: none;
 color: white;
 padding: 14px 16px;
 background-color: inherit;
 font-family: inherit;
 margin: 0;

}

.dropdown-content { 

 display: none;
 position: absolute;
 background-color: #f9f9f9;
 min-width: 160px;
 box-shadow: 0px 8px 16px 0px rgba(0,0,0,0.2);
 z-index: 1;

}

.dropdown-content a { 

 float: none;
 color: black;
 padding: 12px 16px;
 text-decoration: none;
 display: block;
 text-align: left;

}

.topnav a:hover, .dropdown:hover .dropbtn { 

 background-color: #555;
 color: white;

}

.dropdown-content a:hover { 

 background-color: #ddd;
 color: black;

}

.dropdown:hover .dropdown-content { 

 display: block;

}

@media screen and (max-width: 950px) { 

 .topnav a:not(:first-child), .dropdown .dropbtn {
   display: none;
 }
 .topnav a.icon {
   float: right;
   display: block;
 }

}

@media screen and (max-width: 950px) { 

 .topnav.responsive {position: relative;}
 .topnav.responsive .icon {
   position: absolute;
   right: 0;
   top: 0;
 }
 .topnav.responsive a {
   float: none;
   display: block;
   text-align: left;
 }
 .topnav.responsive .dropdown {float: none;}
 .topnav.responsive .dropdown-content {position: relative;}
 .topnav.responsive .dropdown .dropbtn {
   display: block;
   width: 100%;
   text-align: left;
 }

}

body{ 

 overflow-y: scroll;
 overflow-x: hidden;

}

  1. main{
 margin-right:80px;
 margin-left: 80px;
 text-align: justify;
 text-justify: inter-word;

}

p{text-indent: 20px;}

  1. mySidenav a {
 position: fixed;
 transition: 0.3s;
 padding: 15px;
 width: 100px;
 text-decoration: none;
 font-size: 20px;
 color: white;
 bottom: 20px;
 background-color: #555;

}

  1. mySidenav #left:hover {
 left: 0;

}

  1. mySidenav #right:hover {
 right: 0;

}

  1. left {
 left: -80px;
 border-radius: 0 5px 5px 0;
 text-align: left;

}

  1. right {
 right: -80px;
 border-radius: 5px 0 0 5px;
 text-align: right;

} </style>

★ ALERT!

This page is used by the judges to evaluate your team for the medal criterion or award listed below.

Delete this box in order to be evaluated for this medal criterion and/or award. See more information at Instructions for Pages for awards.

Collaborations

Sharing and collaboration are core values of iGEM. We encourage you to reach out and work with other teams on difficult problems that you can more easily solve together.

Silver Medal Criterion #2

Document your collaboration(s) clearly on this page to compete for the silver medal criterion #2 on collaboration. Please see the 2019 Medals Page for more information.

Which other teams can we work with?

You can work with any other team in the competition, including standard, software, open, and high school track teams. You can also work with non-iGEM research groups, but they do not count towards the iGEM team collaboration silver medal criterion.

In order to meet the silver medal criteria on helping another team, you must complete this page and detail the nature of your collaboration with another iGEM team.

Here are some suggestions for projects you could work on with other teams:

  • Improve the function of another team's BioBrick Part or Device
  • Characterize another team's part
  • Debug a construct
  • Model or simulate another team's system
  • Test another team's software
  • Help build and test another team's hardware project
  • Mentor a high-school team