Difference between revisions of "Team:Cambridge-JIC/Engagement"
| Line 4: | Line 4: | ||
<body> | <body> | ||
| + | <style> | ||
| + | .darkWhite:hover | ||
| + | { | ||
| + | color:#fff; | ||
| + | } | ||
| − | + | .darkBlue:link | |
| − | + | { | |
| − | + | color:#000; | |
| + | text-decoration:none; | ||
| + | |||
| + | } | ||
| + | .darkBlue:hover | ||
| + | { | ||
| + | color:#B7E2F0; | ||
| + | text-decoration:none; | ||
| + | } | ||
| − | + | .darkWhite, .darkBlue{ | |
| − | + | font-weight: bold; | |
| + | font-size: 150%; | ||
| + | } | ||
| + | .darkBlue:active | ||
| + | { | ||
| + | color:#B7E2F0; | ||
| + | text-decoration:none; | ||
| + | } | ||
| − | < | + | </style> |
| + | <section style="background-color:#fff; text-align: center"> | ||
| + | <center><h1 style="font-family:'Montserrat'; line-height:1.295em">ENGAGEMENT</h1></center> | ||
| + | <div class="scroller" style="color:#000"> | ||
| + | <a href="#docubricks" class="darkBlue" style="font-family: 'Pacifico'"><h2 style="text-align: center">Planting the seed for future iGEM-ers</h3></a> | ||
| + | </div> | ||
| + | <br> | ||
| + | <div class="container"> | ||
| + | <p style="font-family:Arvo ; font-size:160%; text-align:center">In order to integrate best practices for open hardware design within our protocols, we spoke to Tobias Wenzel, co-founder of <a href="http://docubricks.com/" class="darkBlue" style="font-size:100%;">DocuBricks</a>; a website for high quality open source documentation, funded by the OpenPlant program. See what we discussed in the interview:</p> | ||
| + | </div> | ||
| + | |||
| + | </section> | ||
| + | |||
| + | <section id="docubricks" style="background-color: rgba(183,226,240,0.7)"> | ||
| + | <div class="container" style:"padding:0% 0% ; margin:0% 0%"> | ||
| + | <video controls style="width:100%;padding:5% 5%;"> | ||
| + | <source src="https://static.igem.org/mediawiki/2016/f/f9/T--Cambridge-JIC--integratedHPdocubricks.mp4" type="video/mp4"/> | ||
| + | </video> | ||
| + | </div> | ||
| + | </section> | ||
| − | < | + | <section style="background-color:#fff; text-align: center"> |
| − | < | + | <div class="container" style:"padding:0% 0% ; margin:0% 0%"> |
| − | + | <h2 style="font-family:Pacifico ; text-align: center">How we integrated this into our design:</h2> | |
| − | + | <div style="font-family:Arvo; font-size:130%;"> | |
| − | + | <hr> | |
| − | <p> | + | <p style="font-family:Arvo; font-size:130%; text-align:center">Neglect of safety features in open source protocols - as well as the features already included in our designs from community lab feedback, such as contained electrical connections and safety shields, we included instructions on how users can conduct <span class="darkBlue">isolated safety checks</span> when building our hardware. For example, underwater pressure testing of the gun and checking of electrical circuits.</p> |
| − | < | + | <hr> |
| − | < | + | <p style="font-family:Arvo; font-size:130%; text-align:center">Encouragement of designers to document their hardware properly - in addition to our own protocols, we have included <span class="darkBlue">links on our wiki to DocuBricks</span> and an easy-to-follow <span class="darkBlue">checklist of components</span> for anyone considering writing their own open source protocol.</p> |
| − | < | + | <hr> |
| − | </ | + | <p style="font-family:Arvo; font-size:130%; text-align:center">Adaptability of our design for different end users - including <span class="darkBlue">alternative supplier links</span> for parts, where possible, to suit international users of the hardware and also providing an alternative in case the primarily-suggested supplier is out of stock.</p> |
| − | + | <hr> | |
| − | </div> | + | <p style="font-family:Arvo; font-size:130%; text-align:center">Used open source software when designing CAD files for parts of the gene gun and growth facility, so these files can be downloaded and customised by anyone.</p> |
| − | + | <hr> | |
| + | </div> | ||
| + | <br> | ||
| + | <br> | ||
| + | </div> | ||
| + | </section> | ||
</body> | </body> | ||
</html> | </html> | ||
{{Cambridge-JIC/Templates/Footer}} | {{Cambridge-JIC/Templates/Footer}} | ||
Revision as of 10:23, 7 October 2016
ENGAGEMENT
In order to integrate best practices for open hardware design within our protocols, we spoke to Tobias Wenzel, co-founder of DocuBricks; a website for high quality open source documentation, funded by the OpenPlant program. See what we discussed in the interview:
How we integrated this into our design:
Neglect of safety features in open source protocols - as well as the features already included in our designs from community lab feedback, such as contained electrical connections and safety shields, we included instructions on how users can conduct isolated safety checks when building our hardware. For example, underwater pressure testing of the gun and checking of electrical circuits.
Encouragement of designers to document their hardware properly - in addition to our own protocols, we have included links on our wiki to DocuBricks and an easy-to-follow checklist of components for anyone considering writing their own open source protocol.
Adaptability of our design for different end users - including alternative supplier links for parts, where possible, to suit international users of the hardware and also providing an alternative in case the primarily-suggested supplier is out of stock.
Used open source software when designing CAD files for parts of the gene gun and growth facility, so these files can be downloaded and customised by anyone.
