Difference between revisions of "Team:BITSPilani-Goa India"

(Attempt 1)
Line 1: Line 1:
{{IGEM_TopBar}}
+
<html lang="en"><head><meta charset="UTF-8"/><meta name="viewport" content="width=device-width,initial-scale=1"/><title>iGEM BITS Goa</title><link href="css/index.css" rel="stylesheet"></head><body><nav class="navbar navbar-expand-lg d-flex justify-content-between bg-none nav-transparent fixed-top"><a class="navbar-brand d-lg-inline-block" href="/">iGEM <span>BITS Goa</span></a><div id="fullscreenMenuWrapper"><input id="menuToggle" type="checkbox" onclick="makeNavbarTransparent()"/><label for="menuToggle"><div id="menuSwitch"></div></label><div id="fullscreenMenu"><label class="mr-3" for="menuToggle"></label><div class="container w-100 h-100"><div class="h-100" id="menuContent"><div class="row w-100 mb-4"><div class="col-md-4 col-sm-12 py-3"><a class="nav-heading">Overview</a><ul><li><a href="/Description">Description</a></li><li><a href="/Design">Design</a></li><li><a href="/Results">Results</a></li></ul></div><div class="col-md-4 col-sm-12 py-3"><a class="nav-heading">Project</a><ul><li><a href="/Experiments">Experiments</a></li><li><a href="/Notebook">Notebook</a></li><li><a href="/Contribution">Contribution</a></li><li><a href="/Improve">Improve</a></li></ul></div><div class="col-md-4 col-sm-12 py-3"><a class="nav-heading">Parts</a><ul><li><a href="/Overview">Overview</a></li><li><a href="/Basic_Parts">Basic Parts</a></li><li><a href="/Composite_Parts">Composite Parts</a></li><li><a href="/Parts_Collection">Parts Collection</a></li></ul></div><div class="col-md-4 col-sm-12 py-3"><a class="nav-heading">Human Practices</a><ul><li><a href="/Human_Practices">Human Practices</a></li><li><a href="/Outreach">Outreach</a></li></ul></div><div class="col-md-4 col-sm-12 py-3"><a class="nav-heading">Team</a><ul><li><a href="/Team_Members">Team Members</a></li><li><a href="/Attributions">Attributions</a></li><li><a href="/Collaborations">Collaborations</a></li></ul></div><div class="col-md-4 col-sm-12 py-3"><a class="nav-heading">Awards</a><ul><li><a href="/Entrepreneurship">Entrepreneurship</a></li><li><a href="/Model">Model</a></li><li><a href="/Plant">Plant</a></li><li><a href="/Software">Software</a></li></ul></div></div></div></div></div></div></nav><header class="d-flex justify-content-center align-items-center"><div class="container text-center"><div class="heading d-flex justify-content-center align-items-center"><h1></h1></div></div></header><section class="white" id="introduction"><div class="container"><div class="row"><div class="sidebar col-lg-3"><h3>About our project</h3></div><div class="content col-lg-9"><h2>Tonnes of sugar are lost every year as post-harvest losses. <span>We're here to change that.</span></h2><h3>About our project</h3><p>Describe how the sugar industry is doomed and how revolutionary our project is. Basically a textual description of the problem and our solution, essentially repeating content from the animation above. Maybe add some numbers to put it into perspective. For people who don't want to go through the animation but want a quick description.</p><p>The following sections summarize each important aspect of our project. I think it's best if we cover all the medal criteria here (except the boring ones like attributions and all) so that the most important information is highlighted front and center.</p><p>The fact that a syn bio solution is better than just injecting invertase inhibitor also has to be mentioned somewhere prominent. Not sure where though.</p><p>Maybe we'll move to a more sustainable solution later, but for now, <a href="https://docs.google.com/document/d/1rIz6781r7rfrTbcgEW1J4UNyr1bBL3hShowc-FcC2Ow/edit?usp=sharing" target="_blank">here's a Google doc</a> with all this text so you guys can edit.</p><p><a href="href"></a></p><div class="d-flex justify-content-end my-5"><a class="button next long" href="/Description"><span class="circle" aria-hidden="aria-hidden"><span class="icon arrow"></span></span><span class="button-text">Description</span></a></div></div></div></div></section><section class="yellow" id="design"><div class="container"><div class="row"><div class="content col-lg-9"><h2>Design caption goes here. <span>Optional hype.</span></h2><h3>Not sure what goes here but removing this makes it too empty. Maybe an important highlight from the text itself?</h3><p>Summarize the genetic circuit and models. From the iGEM docs: "Explanation of the engineering principles used" and "Experimental plan to test your designs." It also asks for design iterations but home page is probably not the right place for that. Safety section is at the bottom, but maybe briefly mention the killswitch as well?</p><p>Also talk about the delivery mechanism. Maybe this is the right place to mention why we went with a syn bio solution instead of just injecting the inhibitor.</p><div class="d-flex justify-content-end my-5"><a class="button next short" href="/Design"><span class="circle" aria-hidden="aria-hidden"><span class="icon arrow"></span></span><span class="button-text">Design</span></a></div></div><div class="sidebar col-lg-3"><h3>Not sure what goes here but removing this makes it too empty. Maybe an important highlight from the text itself?</h3></div></div></div></section><section class="white" id="safety"><div class="container"><div class="row"><div class="sidebar col-lg-3"><h3>Maybe an important highlight from the text? Or some helpful warnings about (not) leaving plastic tip boxes in the oven.</h3></div><div class="content col-lg-9"><h2>Safety caption goes here. <span>Optional hype.</span></h2><h3>Maybe an important highlight from the text? Or some helpful warnings about (not) leaving plastic tip boxes in the oven.</h3><p>Talk about the killswitch. The whole thing about toxins and anaerobic environment. From the iGEM docs: choosing a non-pathogenic chassis, choosing parts that will not harm humans / animals / plants, substituting safer materials for dangerous materials in a proof-of-concept experiment, and including an induced lethality or "kill-switch" device.</p><p>Unusual safety issues (like the one on the left?) also have to be mentioned but probably not on the home page.</p><div class="d-flex justify-content-end my-5"><a class="button next short" href="/Safety"><span class="circle" aria-hidden="aria-hidden"><span class="icon arrow"></span></span><span class="button-text">Safety</span></a></div></div></div></div></section><section class="green" id="human-practices"><div class="container"><div class="row"><div class="content col-lg-9"><h2>Human-centered design. <span>Optional hype.</span></h2><h3>Not sure what goes here but removing this makes it too empty. Maybe an important highlight from the text itself?</h3><p>Summarize our human practices approach. Write about how we conducted detailed discussions with stakeholders at every step. Also write about how we changed various aspects of the design based on feedback, and how our product solves different issues for different belts across India and the world.</p><p>From the iGEM docs: explore issues relating (but not limited) to the ethics, safety, security, and sustainability of your project, and to show how this exploration feeds back into your project purpose, design, and execution.</p><div class="d-flex justify-content-end my-5"><a class="button next super-long" href="/Human_Practices"><span class="circle" aria-hidden="aria-hidden"><span class="icon arrow"></span></span><span class="button-text">Human Practices</span></a></div></div><div class="sidebar col-lg-3"><h3>Not sure what goes here but removing this makes it too empty. Maybe an important highlight from the text itself?</h3></div></div></div></section><section class="white" id="collaborations"><div class="container"><div class="row"><div class="sidebar col-lg-3"><h3>Not sure what goes here but removing this makes it too empty. Maybe an important highlight from the text itself?</h3></div><div class="content col-lg-9"><h2>Collaborating for the win. <span>Optional hype.</span></h2><h3>Not sure what goes here but removing this makes it too empty. Maybe an important highlight from the text itself?</h3><p>Summarize our collaborations, including various surveys and the language project. Also summarize some conclusions from surveys we created and the impact of the language project (and maybe a little bit about future scope).</p><p>From the iGEM docs: 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.</p><div class="d-flex justify-content-end my-5"><a class="button next super-long" href="/Collaborations"><span class="circle" aria-hidden="aria-hidden"><span class="icon arrow"></span></span><span class="button-text">Collaborations</span></a></div></div></div></div></section><section class="orange" id="science-communication"><div class="container"><div class="row"><div class="content col-lg-9"><h2>Engaging with the scientists of tomorrow. <span>Optional hype.</span></h2><h3>Maybe an important highlight from the text itself? Scroll up for an inverted Indian flag.</h3><p>Headline too cringey? Questionable color choice? Apparently orange is the color of communication. It's a really hard color to work with, though. Increasing saturation any more hurts my eyes, reducing it saturation makes orange lose its effect and reducing brightness makes it dull. Btw, scroll up for an inverted Indian flag.</p><p>Anyway, write about the webinar here. Maybe an intro about why science communication is necessary, specially keeping the current situation in mind. Also write about Abhighyan insta posts? Is that sci-comn or public engagement? I'll just call the button Communication for now.</p><div class="d-flex justify-content-end my-5"><a class="button next super-long" href="/Communication"><span class="circle" aria-hidden="aria-hidden"><span class="icon arrow"></span></span><span class="button-text">Communication</span></a></div></div><div class="sidebar col-lg-3"><h3>Maybe an important highlight from the text itself? Scroll up for an inverted Indian flag.</h3></div></div></div></section><footer><div id="footerBrand"><div class="container"><div class="row"><div id="footerLogo"></div></div><div class="row justify-content-center" id="footerIcons"><a class="gmail" href="mailto:igembitsgoa@gmail.com"></a><a class="insta" href="https://instagram.com/igem_bits"></a><a class="twitter" href="https://twitter.com/igembitsgoa"></a></div></div></div><div id="footerNav"><div class="container"><div class="row justify-content-between"><div class="col-sm-6 col-md-4 col-lg-2 py-2"><a class="footer-heading">Overview</a><ul><li class="py-1"><a href="/Description">Description</a></li><li class="py-1"><a href="/Design">Design</a></li><li class="py-1"><a href="/Results">Results</a></li></ul></div><div class="col-sm-6 col-md-4 col-lg-2 py-2"><a class="footer-heading">Project</a><ul><li class="py-1"><a href="/Experiments">Experiments</a></li><li class="py-1"><a href="/Notebook">Notebook</a></li><li class="py-1"><a href="/Contribution">Contribution</a></li><li class="py-1"><a href="/Improve">Improve</a></li></ul></div><div class="col-sm-6 col-md-4 col-lg-2 py-2"><a class="footer-heading">Parts</a><ul><li class="py-1"><a href="/Overview">Overview</a></li><li class="py-1"><a href="/Basic_Parts">Basic Parts</a></li><li class="py-1"><a href="/Composite_Parts">Composite Parts</a></li><li class="py-1"><a href="/Parts_Collection">Parts Collection</a></li></ul></div><div class="col-sm-6 col-md-4 col-lg-2 py-2"><a class="footer-heading">Human Practices</a><ul><li class="py-1"><a href="/Human_Practices">Human Practices</a></li><li class="py-1"><a href="/Outreach">Outreach</a></li></ul></div><div class="col-sm-6 col-md-4 col-lg-2 py-2"><a class="footer-heading">Team</a><ul><li class="py-1"><a href="/Team_Members">Team Members</a></li><li class="py-1"><a href="/Attributions">Attributions</a></li><li class="py-1"><a href="/Collaborations">Collaborations</a></li></ul></div><div class="col-sm-6 col-md-4 col-lg-2 py-2"><a class="footer-heading">Awards</a><ul><li class="py-1"><a href="/Entrepreneurship">Entrepreneurship</a></li><li class="py-1"><a href="/Model">Model</a></li><li class="py-1"><a href="/Plant">Plant</a></li><li class="py-1"><a href="/Software">Software</a></li></ul></div></div></div></div></footer><script src="index.bundle.js"></script></body></html>
{{BITSPilani-Goa_India}}
+
{{BITSPilani-Goa_India/mainCSS}}
+
<html>
+
 
+
 
+
 
+
<div class="column full_size" >
+
<h1> Welcome to iGEM 2020! </h1>
+
<p>Your team has been approved and you are ready to start the iGEM season! </p>
+
 
+
 
+
<img src="https://placehold.it/1080x320">
+
+
 
+
</div>
+
 
+
 
+
<div class="column full_size" >
+
 
+
<h3>Before you start</h3>
+
<p> Please read the following pages:</p>
+
<ul>
+
<li> <a href="https://2020.igem.org/Competition">Competition Hub</a> </li>
+
<li> <a href="https://2020.igem.org/Competition/Deliverables/Wiki">Wiki Requirements page</a></li>
+
<li> <a href="https://2020.igem.org/Resources/Template_Documentation">Template documentation</a></li>
+
</ul>
+
</div>
+
 
+
 
+
<div class="clear extra_space"></div>
+
<div class="line_divider"></div>
+
<div class="clear extra_space"></div>
+
 
+
 
+
 
+
<div class="column full_size" >
+
<h3> Styling your wiki </h3>
+
<p>You may style this page as you like or you can simply leave the style as it is. You can easily keep the styling and edit the content of these default wiki pages with your project information and completely fulfill the requirement to document your project.</p>
+
<p>While you may not win Best Wiki with this styling, your team is still eligible for all other awards. This default wiki meets the requirements, it improves navigability and ease of use for visitors, and you should not feel it is necessary to style beyond what has been provided.</p>
+
 
+
</div>
+
 
+
 
+
 
+
 
+
<div class="clear extra_space"></div>
+
 
+
 
+
 
+
<div class="column third_size" >
+
 
+
<h3> Uploading pictures and files </h3>
+
<p> You must upload any pictures and files to the iGEM 2020 server. Remember to keep all your pictures and files within your team's namespace or at least include your team's name in the file name. </p>
+
 
+
 
+
<p>When you upload, set the "Destination Filename" to <b> T--YourOfficialTeamName--NameOfFile.jpg</b>. (If you don't do this, someone else might upload a different file with the same "Destination Filename", and your file would be erased!)</p>
+
 
+
<div class="button_link">
+
<a href="https://2020.igem.org/Special:Upload">
+
UPLOAD FILES
+
</a>
+
</div>
+
 
+
</div>
+
 
+
<div class="column third_size" >
+
<h3> Wiki template information </h3>
+
<p>We have created these wiki template pages to help you get started and to help you think about how your team will be evaluated. You can find a list of all the pages tied to awards here at the <a href="https://2020.igem.org/Judging/Pages_for_Awards">Pages for awards</a> link. You must edit these pages to be evaluated for medals and awards, but ultimately the design, layout, style and all other elements of your team wiki is up to you!</p>
+
 
+
</div>
+
 
+
 
+
 
+
<div class="column third_size" >
+
<div class="highlight decoration_B_full">
+
<h3> Editing your wiki </h3>
+
<p>On this page you can document your project, introduce your team members, document your progress and share your iGEM experience with the rest of the world! </p>
+
<p>Use WikiTools - Edit in the black menu bar to edit this page</p>
+
 
+
<div class="button_link">
+
<a href="https://2020.igem.org/wiki/index.php?title=Team:BITSPilani-Goa_India&action=edit">
+
EDIT PAGE
+
</a>
+
</div>
+
 
+
 
+
</div>
+
</div>
+
 
+
 
+
 
+
 
+
 
+
<div class="clear extra_space"></div>
+
<div class="line_divider"></div>
+
<div class="clear extra_space"></div>
+
 
+
 
+
 
+
<div class="column two_thirds_size" >
+
<h3>Tips</h3>
+
<p>This wiki will be your team’s first interaction with the rest of the world, so here are a few tips to help you get started: </p>
+
<ul>
+
<li>State your accomplishments! Tell people what you have achieved from the start. </li>
+
<li>Be clear about what you are doing and how you plan to do this.</li>
+
<li>You have a global audience! Consider the different backgrounds that your users come from.</li>
+
<li>Make sure information is easy to find; nothing should be more than 3 clicks away.  </li>
+
<li>Avoid using very small fonts and low contrast colors; information should be easy to read.  </li>
+
<li>Start documenting your project as early as possible; don’t leave anything to the last minute before the Wiki Freeze. For a complete list of deadlines visit the <a href="https://2020.igem.org/Calendar">iGEM 2020 calendar</a> </li>
+
<li>Have lots of fun! </li>
+
</ul>
+
</div>
+
 
+
 
+
<div class="column third_size">
+
<div class="highlight decoration_A_full">
+
<h3>Inspiration</h3>
+
<p> You can also view other team wikis for inspiration! Here are some examples:</p>
+
<ul>
+
<li> <a href="https://2014.igem.org/Team:SDU-Denmark/"> 2014 SDU Denmark </a> </li>
+
<li> <a href="https://2014.igem.org/Team:Aalto-Helsinki">2014 Aalto-Helsinki</a> </li>
+
<li> <a href="https://2014.igem.org/Team:LMU-Munich">2014 LMU-Munich</a> </li>
+
<li> <a href="https://2014.igem.org/Team:Michigan"> 2014 Michigan</a></li>
+
<li> <a href="https://2014.igem.org/Team:ITESM-Guadalajara">2014 ITESM-Guadalajara </a></li>
+
<li> <a href="https://2014.igem.org/Team:SCU-China"> 2014 SCU-China </a></li>
+
</ul>
+
</div>
+
</div>
+
 
+
 
+
 
+
 
+
</html>
+

Revision as of 03:18, 27 June 2020

iGEM BITS Goa

Tonnes of sugar are lost every year as post-harvest losses. We're here to change that.

About our project

Describe how the sugar industry is doomed and how revolutionary our project is. Basically a textual description of the problem and our solution, essentially repeating content from the animation above. Maybe add some numbers to put it into perspective. For people who don't want to go through the animation but want a quick description.

The following sections summarize each important aspect of our project. I think it's best if we cover all the medal criteria here (except the boring ones like attributions and all) so that the most important information is highlighted front and center.

The fact that a syn bio solution is better than just injecting invertase inhibitor also has to be mentioned somewhere prominent. Not sure where though.

Maybe we'll move to a more sustainable solution later, but for now, here's a Google doc with all this text so you guys can edit.

Design caption goes here. Optional hype.

Not sure what goes here but removing this makes it too empty. Maybe an important highlight from the text itself?

Summarize the genetic circuit and models. From the iGEM docs: "Explanation of the engineering principles used" and "Experimental plan to test your designs." It also asks for design iterations but home page is probably not the right place for that. Safety section is at the bottom, but maybe briefly mention the killswitch as well?

Also talk about the delivery mechanism. Maybe this is the right place to mention why we went with a syn bio solution instead of just injecting the inhibitor.

Safety caption goes here. Optional hype.

Maybe an important highlight from the text? Or some helpful warnings about (not) leaving plastic tip boxes in the oven.

Talk about the killswitch. The whole thing about toxins and anaerobic environment. From the iGEM docs: choosing a non-pathogenic chassis, choosing parts that will not harm humans / animals / plants, substituting safer materials for dangerous materials in a proof-of-concept experiment, and including an induced lethality or "kill-switch" device.

Unusual safety issues (like the one on the left?) also have to be mentioned but probably not on the home page.

Human-centered design. Optional hype.

Not sure what goes here but removing this makes it too empty. Maybe an important highlight from the text itself?

Summarize our human practices approach. Write about how we conducted detailed discussions with stakeholders at every step. Also write about how we changed various aspects of the design based on feedback, and how our product solves different issues for different belts across India and the world.

From the iGEM docs: explore issues relating (but not limited) to the ethics, safety, security, and sustainability of your project, and to show how this exploration feeds back into your project purpose, design, and execution.

Collaborating for the win. Optional hype.

Not sure what goes here but removing this makes it too empty. Maybe an important highlight from the text itself?

Summarize our collaborations, including various surveys and the language project. Also summarize some conclusions from surveys we created and the impact of the language project (and maybe a little bit about future scope).

From the iGEM docs: 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.

Engaging with the scientists of tomorrow. Optional hype.

Maybe an important highlight from the text itself? Scroll up for an inverted Indian flag.

Headline too cringey? Questionable color choice? Apparently orange is the color of communication. It's a really hard color to work with, though. Increasing saturation any more hurts my eyes, reducing it saturation makes orange lose its effect and reducing brightness makes it dull. Btw, scroll up for an inverted Indian flag.

Anyway, write about the webinar here. Maybe an intro about why science communication is necessary, specially keeping the current situation in mind. Also write about Abhighyan insta posts? Is that sci-comn or public engagement? I'll just call the button Communication for now.