Difference between revisions of "Team:SYSU-Software/Project"

(statement.html)
(Undo revision 253396 by Sysu software (talk))
Line 1: Line 1:
 
{{SYSU-Software}}
 
{{SYSU-Software}}
<!DOCTYPE html>
+
<html>
<html lang="en">
+
 
 +
 
 +
<div class="column full_size" >
 +
<img src="http://placehold.it/2000x300/d3d3d3/f2f2f2">
 +
</div>
 +
 
 +
 
 +
 
 +
<div class="column full_size" >
 +
<h1> Welcome to iGEM 2017! </h1>
 +
<p>Your team has been approved and you are ready to start the iGEM season! </p>
 +
</div>
 +
 
 +
<div class="clear"></div>
 +
 
 +
<div class="column half_size" >
 +
<h5>Before you start: </h5>
 +
<p> Please read the following pages:</p>
 +
<ul>
 +
<li>  <a href="https://2017.igem.org/Competition">Competition Hub</a> </li>
 +
<li> <a href="https://2017.igem.org/Competition/Deliverables/Wiki">Wiki Requirements page</a></li>
 +
<li> <a href="https://2017.igem.org/Resources/Template_Documentation">Template documentation</a></li>
 +
</ul>
 +
</div>
 +
 
 +
<div class="column half_size" >
 +
<div class="highlight">
 +
<h5> Styling your wiki </h5>
 +
<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>
 +
 
 +
<div class="column full_size" >
 +
<h5> Wiki template information </h5>
 +
<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://2017.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 half_size" >
 +
<h5> Editing your wiki </h5>
 +
<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> <a href="https://2017.igem.org/wiki/index.php?title=Team:Example&action=edit"> </a>Use WikiTools - Edit in the black menu bar to edit this page</p>
 +
 
 +
</div>
 +
 
 +
 
 +
<div class="column half_size" >
 +
<h5>Tips</h5>
 +
<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://2017.igem.org/Calendar">iGEM 2017 calendar</a> </li>
 +
<li>Have lots of fun! </li>
 +
</ul>
 +
</div>
 +
 
 +
 
 +
<div class="column half_size" >
 +
<h5>Inspiration</h5>
 +
<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 class="column half_size" >
 +
<h5> Uploading pictures and files </h5>
 +
<p> You can upload your pictures and files to the iGEM 2017 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. <br />
 +
When you upload, set the "Destination Filename" to <br><code>T--YourOfficialTeamName--NameOfFile.jpg</code>. (If you don't do this, someone else might upload a different file with the same "Destination Filename", and your file would be erased!)<br><br>
 +
 
 +
<a href="https://2017.igem.org/Special:Upload">
 +
UPLOAD FILES
 +
</a>
 +
</p>
 +
</div>
 +
 
  
<head>
 
  <title>Statements</title>
 
  <meta charset="UTF-8">
 
  <meta http-equiv="X-UA-Compatible" content="IE=edge,chrome=1">
 
  <meta name="viewport" content="width=device-width, initial-scale=1, shrink-to-fit=no">
 
  <link rel="stylesheet" href="../css/specific-style-for-each-page.css">
 
  <link rel="stylesheet" href="../lib/semantic.min.css">
 
  <link href="../css/common.css" rel="stylesheet">
 
</head>
 
  
<body>
 
  <div id="firstnav" class="ui fixed collapsed borderless ten menu">
 
    <a id="sdin-link" href="#">
 
      <img id="sdin-icon" src="../images/common/T--SYSU-Software--sdin-small.png" alt="logo">
 
    </a>
 
  
    <div class="ui simple dropdown item page-nav" id="active-page">
 
      <a href="./project.html" class="page-link">Project</a>
 
      <div class="menu page-category">
 
        <a href="./project.html#description" class="item">Description</a>
 
        <a href="./project.html#design" class="item">Design</a>
 
        <a href="./project.html#feature" class="item">Features</a>
 
      </div>
 
    </div>
 
    <div class="ui simple dropdown item page-nav">
 
      <a href="./modeling.html" class="page-link">Modeling</a>
 
      <div class="menu page-category">
 
        <a href="./modeling.html#overview" class="item">Overview</a>
 
        <a href="./modeling.html#recommendation-system" class="item">Recommendation System</a>
 
        <a href="./modeling.html#simulation" class="item">Simulation for General Genetic Circuits</a>
 
      </div>
 
    </div>
 
    <div class="ui simple dropdown item page-nav">
 
      <a href="./medal.html" class="page-link">Medals</a>
 
      <div class="menu page-category">
 
        <a href="./medal.html#overview" class="item">Overview</a>
 
        <a href="./medal.html#bronze" class="item">Bronze</a>
 
        <a href="./medal.html#silver" class="item">Silver</a>
 
        <a href="./medal.html#gold" class="item">Gold</a>
 
      </div>
 
    </div>
 
    <div class="ui simple dropdown item page-nav">
 
      <a href="#" class="page-link">Human Practice</a>
 
      <div class="menu page-category">
 
        <a href="#" class="item"></a>
 
        <a href="#" class="item"></a>
 
        <a href="#" class="item"></a>
 
      </div>
 
    </div>
 
    <div class="ui simple dropdown item page-nav">
 
      <a href="#" class="page-link">Collaboration</a>
 
      <div class="menu page-category">
 
        <a href="./collaboration.html#overview" class="item">Overview</a>
 
        <a href="./collaboration.html#nju-china" class="item">NJU-China</a>
 
        <a href="./collaboration.html#hkust" class="item">HUKST</a>
 
        <a href="./collaboration.html#sysu-china" class="item">SYSU-CHINA</a>
 
        <a href="./collaboration.html#scau-china" class="item">SCAU-CHINA</a>
 
      </div>
 
    </div>
 
    <div class="ui simple dropdown item page-nav">
 
      <a href="./interlab.html" class="page-link">Interlab</a>
 
      <div class="menu page-category">
 
        <a href="./interlab.html#overview" class="item">Overview</a>
 
        <a href="./interlab.html#experiment-design" class="item">Experiment Design</a>
 
        <a href="./interlab.html#material-and-methods" class="item">Material and Methods</a>
 
        <a href="./interlab.html#results" class="item">Results</a>
 
      </div>
 
    </div>
 
    <div class="ui simple dropdown item page-nav">
 
      <a href="./safety.html" class="page-link">Safety</a>
 
      <div class="menu page-category">
 
        <a href="./safety.html#dry-lab" class="item">Biosafety in Dry Lab</a>
 
        <a href="./safety.html#wet-lab" class="item">Biosafety in Wet Lab</a>
 
      </div>
 
    </div>
 
    <div class="ui simple dropdown item page-nav">
 
      <a href="./attributions.html" class="page-link">Attributions</a>
 
      <div class="menu page-category">
 
        <a href="./attributions.html#overview" class="item">Overview</a>
 
        <a href="./attributions.html#group-structure" class="item">Group Structure</a>
 
        <a href="./attributions.html#attribution-in-project" class="item">Attribution in Project</a>
 
        <a href="./attributions.html#journey-planning" class="item">Journey Planning and Financing</a>
 
        <a href="./attributions.html#acknowledgements" class="item">Acknowledgements</a>
 
      </div>
 
    </div>
 
    <div class="ui simple dropdown item page-nav">
 
      <a href="./team.html" class="page-link">Team</a>
 
      <div class="menu page-category">
 
        <a href="./team.html#biology-group" class="item">Biology Group</a>
 
        <a href="./team.html#programming-group" class="item">Programming Group</a>
 
        <a href="./team.html#modeling-group" class="item">Modeling Group</a>
 
        <a href="./team.html#design-group" class="item">Designer Group</a>
 
      </div>
 
    </div>
 
    <div class="ui simple dropdown item page-nav">
 
      <a href="./statements.html" class="page-link">Statements</a>
 
      <div class="menu page-category">
 
        <a href="./statements.html#term-of-use" class="item">Term of Use</a>
 
        <a href="./statements.html#bio-safety-alerts" class="item">Bio Safety Alerts</a>
 
        <a href="./statements.html#privacy-policy" class="item">Privacy Policy</a>
 
        <a href="./statements.html#cookie-policy" class="item">Cookie Policy</a>
 
      </div>
 
    </div>
 
  </div>
 
  
  <div id="first-page">
 
    <div id="ship-background"></div>
 
    <h1 id="top-title">Statements</h1>
 
    <h2 id="slogan">slogan here</h2>
 
    <h3 id="sysu-software-2017">SYSU-Software 2017</h3>
 
    <!-- CONTENT OF FIRST PAGE -->
 
    <section class="plain" id="term-of-use">
 
      <h2>
 
        Term of Use
 
        <h3>Welcome to S-Din</h3>
 
        <div class="paragraph">
 
          <p>By using this website (the “Site”) and services (together with the Site, the “Services”) offered by SYSU-Software. You are agreeing to these rules.</p>
 
          <p>Every iGEM project stored in the services of S-Din follow the CC 3.0 protocol.</p>
 
          <p>Every Academic Project stored in the services of S-Din follow the Terms of its own Publications. We only provide public information and any other non-public information have been authorized by the Publications.</p>
 
        </div>
 
        <h3>Account</h3>
 
        <div class="paragraph">
 
          <p>You can use S-Din with or without an Account, But to use some of S-Din’s functions, you’ll need to register, choose an account name, and set a password. There’s no limitation in registration. Your information will be stored on the services of S-Din with enough Secure Protection.</p>
 
          <p>You’re responsible for all the activity on your account, and for keeping your password confidential. The account owner is responsible for every operation operated by the account.</p>
 
          <p>You are not allowed to do:</p>
 
          <ul>
 
            <li>Don’t break the law or violent any local regulations.</li>
 
            <li>Don’t try to interfere with the proper workings of the Services.</li>
 
            <li>Don’t bypass any measures we’ve put in place to secure the Services.</li>
 
          </ul>
 
          <p>What you can do:</p>
 
          <ul>
 
            <li>Proper operation of the software.</li>
 
            <li>Access to the public data of S-Din.</li>
 
            <li>Enjoy your Design.</li>
 
          </ul>
 
        </div>
 
        <h3>
 
          Your Intellectual Property
 
        </h3>
 
        <div class="paragraph">
 
          <p>You can create your own project on S-Din, but before you choose to open it in public, you have your right to protect it from any form of plagiarizing. We will do our best to protect your information.</p>
 
        </div>
 
      </h2>
 
    </section>
 
    <section class="plain" id="bio-safety-alerts">
 
      <h2>Bio Safety Alerts</h2>
 
      <div class="paragraph">
 
        <p>All biological parts are labeled with bio-safety level According to the Risk Groups (2017) and White List (2017) by iGEM Foundation <a href="https://2017.igem.org/Safety">https://2017.igem.org/Safety</a>, for other Parts Which Sources remained unknown in the iGEM list, we use DMSZ to confirm its bio-safety level. Every user has obligation to follow local safety protocol to avoid any potential damage that might exert negative influence to the local environment. Use any highly dangerous parts to design circuits will be warned before the design, but the design process won’t be stopped. We declare no responsibility for any inappropriate usage that involved bio-safety of our software, and we seriously condemn such behavior.</p>
 
      </div>
 
    </section>
 
    <section class="plain" id="privacy-policy">
 
      <h2>Privacy Policy</h2>
 
      <div class="paragraph">
 
        <p>This Policy describes the information we collect from you and how we use that information. Thank you for trust us with your information. We guarantee that we take our responsibility to protect your information with all our efforts.</p>
 
      </div>
 
      <h3>What we collect</h3>
 
      <div class="paragraph">
 
        <p>If you create an account and use our Services, the information will be collected to provide a better user experience and help improve our software.</p>
 
        <p>Depending on your use of Services, that may include:</p>
 
        <ul>
 
          <li>The information you fill in for registration.</li>
 
          <li>The information you submit to S-Din (New parts, New circuits).</li>
 
          <li>Information about your activity on and interaction with S-Din (IP address, type of Device you use, your action on the site)</li>
 
          <li>Communication you send to us. (Asking for support, sending questions, report problems)</li>
 
        </ul>
 
      </div>
 
      <h3>How we use this information</h3>
 
      <div class="paragraph">
 
        <p>the information will be used in following purposes</p>
 
        <ul>
 
          <li>Keep your account secure</li>
 
          <li>Enable us to provide you with services, improve and protect our software.</li>
 
        </ul>
 
      </div>
 
    </section>
 
    <section class="plain" id="cookie-policy">
 
      <h2>Cookie Policy</h2>
 
      <div class="paragraph">
 
        <p>Cookies are very small text files that are stored on your computer when you visit websites. We use cookies to help identify your computer so we can tailor your user experience, and remember any parameter settings that you might have changed in S-Din. You can delete/disable cookies already stored on your computer at any time; this will simply restore settings to default and the S-Din website will continue working.</p>
 
      </div>
 
    </section>
 
  </div>
 
  
  <div id="contact">
 
    <div id="contact-content">
 
      <div class="contact-item">
 
        <div class="contact-heading">contact</div>
 
        <div class="contact-value">sysusoftware@126.com</div>
 
      </div>
 
      <div class="contact-item">
 
        <div class="contact-heading">address</div>
 
        <div class="contact-value">135# Xin'gang Rd(W.), Sun Yat-sen University, Guangzhou, China</div>
 
      </div>
 
      <div class="contact-item">
 
        <div class="contact-heading">GET IN TOUCH</div>
 
        <div class="contact-icons">
 
          <a href="https://www.instagram.com/sysusf" class="contact-icon" target="_blank"><img src="../images/common/T--SYSU-Software--instagram.png" alt="instagram"></a>
 
          <a href="https://twitter.com/SYSU_Software" class="contact-icon" target="_blank"><img src="../images/common/T--SYSU-Software--twitter.png" alt="twitter"></a>
 
          <a href="https://plus.google.com/u/0/108675007137699538539" class="contact-icon" target="_blank"><img src="../images/common/T--SYSU-Software--google.png" alt="google+"></a>
 
          <a href="https://www.facebook.com/sysusoftware" class="contact-icon" target="_blank"><img src="../images/common/T--SYSU-Software--facebook.png" alt="facebook"></a>
 
        </div>
 
      </div>
 
    </div>
 
  </div>
 
  <script src="../lib/T--SYSU-Software--jquery.min.js"></script>
 
  <script src="../lib/semantic.min.js"></script>
 
</body>
 
  
 
</html>
 
</html>

Revision as of 13:39, 26 October 2017

SYSU-Software

Welcome to iGEM 2017!

Your team has been approved and you are ready to start the iGEM season!

Before you start:

Please read the following pages:

Styling your wiki

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.

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.

Wiki template information

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 Pages for awards 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!

Editing your wiki

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!

Use WikiTools - Edit in the black menu bar to edit this page

Tips

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:

  • State your accomplishments! Tell people what you have achieved from the start.
  • Be clear about what you are doing and how you plan to do this.
  • You have a global audience! Consider the different backgrounds that your users come from.
  • Make sure information is easy to find; nothing should be more than 3 clicks away.
  • Avoid using very small fonts and low contrast colors; information should be easy to read.
  • 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 iGEM 2017 calendar
  • Have lots of fun!
Inspiration

You can also view other team wikis for inspiration! Here are some examples:

Uploading pictures and files

You can upload your pictures and files to the iGEM 2017 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.
When you upload, set the "Destination Filename" to
T--YourOfficialTeamName--NameOfFile.jpg. (If you don't do this, someone else might upload a different file with the same "Destination Filename", and your file would be erased!)

UPLOAD FILES