Difference between revisions of "Team:Amazonas Brazil/Software"

 
(36 intermediate revisions by 6 users not shown)
Line 16: Line 16:
 
/* Clear the default wiki settings */
 
/* Clear the default wiki settings */
 
#home_logo, #sideMenu { display:none; } #sideMenu, #top_title, .patrollink {display:none;} #content { width:100%; padding:0px; margin-top:-7px; margin-left:0px;margin-right: 0;} body {background-color:white; } #bodyContent h1, #bodyContent h2, #bodyContent h3, #bodyContent h4, #bodyContent h5 { margin-bottom: 0px; }
 
#home_logo, #sideMenu { display:none; } #sideMenu, #top_title, .patrollink {display:none;} #content { width:100%; padding:0px; margin-top:-7px; margin-left:0px;margin-right: 0;} body {background-color:white; } #bodyContent h1, #bodyContent h2, #bodyContent h3, #bodyContent h4, #bodyContent h5 { margin-bottom: 0px; }
−
 
−
.menu-sanfona li ul{
 
−
    display:none;
 
−
}
 
−
.menu-sanfona li:focus ul{
 
−
    display:block;
 
−
}
 
−
 
−
.wrap {
 
−
    max-width: 1200px;
 
−
    margin: 0 auto;
 
−
}
 
−
 
−
  .nav {
 
−
    background: #FFF;
 
−
    z-index: 200;
 
−
    position: fixed;
 
−
    width: 100%;
 
−
    font-size: 1em;
 
−
    overflow: auto;
 
−
  }
 
−
 
−
    .nav ul {
 
−
        padding: 1em;
 
−
      }
 
−
 
−
        li {
 
−
        display: inline-block;
 
−
        margin-right: 2em;
 
−
        }
 
−
 
−
          a {
 
−
          text-decoration: none;
 
−
          color: #444;
 
−
          }
 
−
 
−
            a:hover {
 
−
            color: red;
 
−
            }
 
−
 
−
      .nav-toggle {
 
−
      display: none;
 
−
      }
 
−
 
−
.foto {
 
−
    width: 100%;
 
−
}
 
−
 
−
/*Media Queries*/
 
−
@media only screen and (max-width: 800px) {
 
−
.wrap {
 
−
max-width: 100%;
 
−
margin: 0;
 
−
}
 
−
 
−
  .nav.nav-aberta {
 
−
  position: relative;
 
−
  padding: 0 0 0.5em 0;
 
−
  height: 0;
 
−
}
 
−
 
−
      .nav ul {
 
−
        padding: .5em;
 
−
        margin: 0;
 
−
          background: #444;
 
−
    }
 
−
 
−
      li {
 
−
        margin: 0;
 
−
        padding: 0;
 
−
        display: block;
 
−
        border-bottom: 1px solid #FFF;
 
−
        }
 
−
 
−
          li a {
 
−
          padding: 0.5em 0 0.5em 0;
 
−
          display: block;
 
−
              color: #FFF;
 
−
          }
 
−
 
−
            li:last-child {
 
−
              border-bottom:none;
 
−
            }
 
−
 
−
      .nav-toggle {
 
−
      display: block;
 
−
      padding: .4em;
 
−
      margin: .5em 0;
 
−
      }
 
−
}
 
  
 
</style>
 
</style>
Line 124: Line 34:
  
 
<header>
 
<header>
−
     <nav class="navbar navbar-fixed-top navbar-default" style="background-color: rgba(255, 255, 255, 0);">
+
     <nav class="navbar navbar-fixed-top navbar-default" id="#" style="background-color: rgba(255, 255, 255, 0);">
 
       <ul class="Links_bar" style="background: linear-gradient(to left,#BD314C, #5F254A);opacity:0.75;">
 
       <ul class="Links_bar" style="background: linear-gradient(to left,#BD314C, #5F254A);opacity:0.75;">
 
         <li><a class="Link-pg" href="https://2017.igem.org/Team:Amazonas_Brazil"><img src="https://static.igem.org/mediawiki/2017/d/d4/T--Amazonas_Brazil--LogoBranco.png"  width="104.04";height="90"; class="Menu_image"></a></li>
 
         <li><a class="Link-pg" href="https://2017.igem.org/Team:Amazonas_Brazil"><img src="https://static.igem.org/mediawiki/2017/d/d4/T--Amazonas_Brazil--LogoBranco.png"  width="104.04";height="90"; class="Menu_image"></a></li>
Line 180: Line 90:
 
         <div class="row section-container-spacer">
 
         <div class="row section-container-spacer">
 
           <div class="col-xs-12">
 
           <div class="col-xs-12">
−
             <h2>CRISPeasy</h2>
+
             <h2 style="font-size: 110px;margin-top: 54px;" align="middle">iProGRAm</h2>
−
            <h3>Our perspective is to provide a bacterial genome editing vector based on BioBrick parts assembly easy to engineer as A, B, C… CRISPR.
+
−
              </h3>
+
  
−
              <h4 class="p">What's the boost?</h4>
+
 
 +
            <h3 align="center" style="margin-top:0;font-size:39px;margin-bottom:70px;">A platform for expand the iGEM experience</h3>
 +
 
 +
 
 +
             
 
               <div>
 
               <div>
−
               <p class="p">Scientific community have been achieved great results using CRISPR-Cas9 mediated
+
               <div class="">
−
              genome editing techniques. While these methods are moving forward, some methodological
+
              <h4 style="font-size:30px!important;margin:1em 3.5em;" class="p">What's the boost?</h4>
−
                aspects related to this technique could be further improved to bring up this science
+
               <p style="font-size: 27px !important;margin: 1em 4em;">Protocols are a set of well-documented steps to perform an experiment. It is through protocols that scientists can abstract and engineer their solutions. This standardization is the key to make it possible for scientists from the other side of the globe to reliably reproduce, in their labs, the results obtained by another scientist.</p>
−
                revolution even more.</p>
+
              <p style="font-size: 27px !important;margin: 1em 4em;">The algorithms are to Computer Science as protocols are to Biotechnology. Following the principles that jumpstarted the exponential growth of software development techniques, promoting reuse of code, peer review, and incremental development, the open source community revolutionized the way that software was being made and those principles can easily be translated to Biotechnology.</p>
−
               <p class="p">In prokaryotes, the genome editing based on CRISPR/Cas9 machinery require quite
+
   
−
                laborious days of work in lab due to the multi-plasmid based edition. The system
+
    <p style="font-size: 27px !important;margin: 1em 4em;">Advances in the opening of biological 'codes' has already promoted unpreceded developments in biological systems engineering, the most remarkable is the easily accessible NCBI database, which allows anyone to access detailed genomic and proteomic information of various species.
−
                não é padronizado e, em determinadas metodologias, demands more than one plasmid,
+
</p>
−
                each one carrying a part of the CRISPR/Cas9 apparatus. Other critical problem consist
+
    <p style="font-size: 27px !important;margin: 1em 4em;">We envision a future where the abstraction for the creation of bioengineered living beings becomes more open, enabling anyone with the proper equipment and care, to reproduce reliably experiments and develop solutions.
−
              in the addition of a linear DNA carrying homologous arms to provide a donor
+
</p>
−
                DNA to insert information into the genome during the HDR repair via. However,
+
−
              the linear donor DNA system has low edition efficiency due the action of DNA restriction
+
−
                systems present in wild type and E. coli strains, which can degrade the linear DNAs
+
−
              before integration into genome. All this demands plenty of time and a lot of wet lab
+
−
                hours of work. To verify this information, we got in touch with other iGEM's teams who
+
−
                had work with CRISPR/Cas9 in the previous years, you can check this outreach part with
+
−
                more details here.</p>
+
−
            </div>
+
−
            <div>
+
−
            <ul class="menu-sanfona">
+
−
              <li tabindex="0">Item 1
+
−
                <ul>
+
−
                  <li>Item 1.1</li>
+
−
                </ul>
+
−
              </li>
+
−
              <li tabindex="1">Item 2
+
−
                <ul>
+
−
                  <li>Item 2.1</li>
+
−
                </ul>
+
−
              </li>
+
−
            </ul>
+
−
          </div>
+
  
  
−
          <nav class="nav nav-aberta">
+
−
          <div class="wrap">
+
−
          <ul class="listaNav">
+
−
          <li><a href="#TESTE">Item 1</a></li>
+
−
          <li><a href="#">Item 2</a></li>
+
−
          <li><a href="#">Item 3</a></li>
+
−
          <li><a href="#">Item 4</a></li>
+
−
          <li><a href="#">Item 5</a></li>
+
−
          <li><a href="#">Item 6</a></li>
+
−
          <li><a href="#">Item 7</a></li>
+
−
          <li><a href="#">Item 8</a></li>
+
−
          <li><a href="#">Item 9</a></li>
+
−
          </ul>
+
−
          </div>
+
−
          </nav>
+
  
 +
    <div id="myCarousel" style="max-width:1360px;margin: 58px auto;" class="carousel slide" data-ride="carousel">
 +
  <!-- Indicators -->
 +
  <ol class="carousel-indicators">
 +
    <li data-target="#myCarousel" data-slide-to="0" class="active"></li>
 +
    <li data-target="#myCarousel" data-slide-to="1"></li>
 +
    <li data-target="#myCarousel" data-slide-to="2"></li>
 +
  </ol>
  
−
          <img id="TESTE" src="http://placehold.it/1920x800/&text=Conteúdo" alt="" class="foto">
+
  <!-- Wrapper for slides -->
 +
  <div class="carousel-inner">
 +
    <div class="item active">
 +
      <img src="https://static.igem.org/mediawiki/2017/d/dd/Iprogram_plataform1.gif" alt="Chicago">
 +
    </div>
  
 +
    <div class="item">
 +
      <img src="https://static.igem.org/mediawiki/2017/5/59/Iprogram_plataform2.gif" alt="New York">
 +
    </div>
  
 +
    <div class="item">
 +
      <img src="https://static.igem.org/mediawiki/2017/7/74/Iprogram_plataform3.gif" alt="Los Angeles">
 +
    </div>
 +
  </div>
  
 +
  <!-- Left and right controls -->
 +
  <a class="left carousel-control" href="#myCarousel" data-slide="prev">
 +
    <span class="glyphicon glyphicon-chevron-left"></span>
 +
    <span class="sr-only">Previous</span>
 +
  </a>
 +
  <a class="right carousel-control" href="#myCarousel" data-slide="next">
 +
    <span class="glyphicon glyphicon-chevron-right"></span>
 +
    <span class="sr-only">Next</span>
 +
  </a>
 +
</div>
 +
 +
    <h4 style="font-size:30px!important;margin:1em 3.5em;" class="p">How will we do this?</h4>
 +
    <p style="font-size: 27px !important;margin: 1em 4em;">To make our library available we created a Web Application decoupled from our WebServer, named iProGRAm, iGEM Protocol Git Repository from Amazonas_Brazil team, to deliver an environment to create, store and share lab protocols. </p>
 +
    <p style="font-size: 27px !important;margin: 1em 4em;">Moreover, any current web based application can migrate their data to AlexAPI format and use this database in a unified fashion. And with their own customization many applications can share a common space. </p>
 +
      <p style="font-size: 27px !important;margin: 1em 4em;">This protocols platform will be able to search, cite and create protocols in a easy and fast way, creating an ecosystem to bring people together and generate positive interactions, promoting scientific growth.</p>
 +
    <h4 style="font-size:30px!important;margin:1em 3.5em;" class="p">How will it impact iGEM?</h4>
 +
      <p style="font-size: 27px !important;margin: 1em 4em;">We believe that having such space would help everyone in the development of their project, reducing the amount of time taken in project design plan and increasing the success rate of teams. Helping everyone to achieve their results on time to deliver to the competition.</p>
 +
      <p style="font-size: 27px !important;margin: 1em 4em;">We were inspired by the open software practices that brought github.com to life and over the year has made a tremendous impact on how open source software is being developed. We hope that iProGRAm can be ourProgram and really impact iGEMers from around the world.</p>
 +
 +
<p style="font-size:26px"><b><a href="https://github.com/iGemAmazonas/alexAPI">Checkout our code in GitHub</a></b></p>
 +
 +
 +
 +
</div>
 +
            </div>
 +
         
 
         </div>
 
         </div>
 
       </div>
 
       </div>
Line 283: Line 203:
  
 
</body>
 
</body>
 +
 +
<footer style="position:fixed;">
 +
<div class="subcontainer">
 +
 +
<a href="#"><img src="https://static.igem.org/mediawiki/2017/5/55/T--Amazonas_Brazil--IconTop.png" style="width: 4%;position: absolute;bottom: 0.5em;right: 0.5em;opacity: 0.5;"></a>
 +
</div>
 +
</footer>
  
 
<footer style="background: linear-gradient(to left,#BD314C, #5F254A);">
 
<footer style="background: linear-gradient(to left,#BD314C, #5F254A);">
Line 296: Line 223:
 
         <i class="fa fa-facebook" aria-hidden="true"></i>
 
         <i class="fa fa-facebook" aria-hidden="true"></i>
 
     </a>
 
     </a>
 +
<a href="#"><img src="https://static.igem.org/mediawiki/2017/5/55/T--Amazonas_Brazil--IconTop.png" style="width: 4%;position: absolute;bottom: 5.5em;right: 0.5em;opacity: 0.5;"></a>
 
   </p>
 
   </p>
 
   </div>
 
   </div>

Latest revision as of 00:50, 16 December 2017

Wiki_iGEM_Amazonas

SOFTWARE

A platform to expand the iGEM Experience

iProGRAm

A platform for expand the iGEM experience

What's the boost?

Protocols are a set of well-documented steps to perform an experiment. It is through protocols that scientists can abstract and engineer their solutions. This standardization is the key to make it possible for scientists from the other side of the globe to reliably reproduce, in their labs, the results obtained by another scientist.

The algorithms are to Computer Science as protocols are to Biotechnology. Following the principles that jumpstarted the exponential growth of software development techniques, promoting reuse of code, peer review, and incremental development, the open source community revolutionized the way that software was being made and those principles can easily be translated to Biotechnology.

Advances in the opening of biological 'codes' has already promoted unpreceded developments in biological systems engineering, the most remarkable is the easily accessible NCBI database, which allows anyone to access detailed genomic and proteomic information of various species.

We envision a future where the abstraction for the creation of bioengineered living beings becomes more open, enabling anyone with the proper equipment and care, to reproduce reliably experiments and develop solutions.

How will we do this?

To make our library available we created a Web Application decoupled from our WebServer, named iProGRAm, iGEM Protocol Git Repository from Amazonas_Brazil team, to deliver an environment to create, store and share lab protocols.

Moreover, any current web based application can migrate their data to AlexAPI format and use this database in a unified fashion. And with their own customization many applications can share a common space.

This protocols platform will be able to search, cite and create protocols in a easy and fast way, creating an ecosystem to bring people together and generate positive interactions, promoting scientific growth.

How will it impact iGEM?

We believe that having such space would help everyone in the development of their project, reducing the amount of time taken in project design plan and increasing the success rate of teams. Helping everyone to achieve their results on time to deliver to the competition.

We were inspired by the open software practices that brought github.com to life and over the year has made a tremendous impact on how open source software is being developed. We hope that iProGRAm can be ourProgram and really impact iGEMers from around the world.

Checkout our code in GitHub