Skip to content
Snippets Groups Projects
Commit 771bb748 authored by Fabio Maschi's avatar Fabio Maschi
Browse files

2022 release

parent 23227301
No related branches found
No related tags found
No related merge requests found
Showing
with 1035 additions and 85 deletions
env
venv
.vscode
__pycache__
public
image: python:3.6
pages:
stage: build
script:
- pip install --no-cache-dir -r dependencies.txt
- FLASK_APP=app.py flask freeze
artifacts:
paths:
- public
only:
- main
LICENSE 0 → 100644
Attribution 4.0 International (CC BY 4.0)
https://creativecommons.org/licenses/by/4.0/
=======================================================================
Creative Commons Corporation ("Creative Commons") is not a law firm and
does not provide legal services or legal advice. Distribution of
Creative Commons public licenses does not create a lawyer-client or
other relationship. Creative Commons makes its licenses and related
information available on an "as-is" basis. Creative Commons gives no
warranties regarding its licenses, any material licensed under their
terms and conditions, or any related information. Creative Commons
disclaims all liability for damages resulting from their use to the
fullest extent possible.
Using Creative Commons Public Licenses
Creative Commons public licenses provide a standard set of terms and
conditions that creators and other rights holders may use to share
original works of authorship and other material subject to copyright
and certain other rights specified in the public license below. The
following considerations are for informational purposes only, are not
exhaustive, and do not form part of our licenses.
Considerations for licensors: Our public licenses are
intended for use by those authorized to give the public
permission to use material in ways otherwise restricted by
copyright and certain other rights. Our licenses are
irrevocable. Licensors should read and understand the terms
and conditions of the license they choose before applying it.
Licensors should also secure all rights necessary before
applying our licenses so that the public can reuse the
material as expected. Licensors should clearly mark any
material not subject to the license. This includes other CC-
licensed material, or material used under an exception or
limitation to copyright. More considerations for licensors:
wiki.creativecommons.org/Considerations_for_licensors
Considerations for the public: By using one of our public
licenses, a licensor grants the public permission to use the
licensed material under specified terms and conditions. If
the licensor's permission is not necessary for any reason--for
example, because of any applicable exception or limitation to
copyright--then that use is not regulated by the license. Our
licenses grant only permissions under copyright and certain
other rights that a licensor has authority to grant. Use of
the licensed material may still be restricted for other
reasons, including because others have copyright or other
rights in the material. A licensor may make special requests,
such as asking that all changes be marked or described.
Although not required by our licenses, you are encouraged to
respect those requests where reasonable. More considerations
for the public:
wiki.creativecommons.org/Considerations_for_licensees
=======================================================================
Creative Commons Attribution 4.0 International Public License
By exercising the Licensed Rights (defined below), You accept and agree
to be bound by the terms and conditions of this Creative Commons
Attribution 4.0 International Public License ("Public License"). To the
extent this Public License may be interpreted as a contract, You are
granted the Licensed Rights in consideration of Your acceptance of
these terms and conditions, and the Licensor grants You such rights in
consideration of benefits the Licensor receives from making the
Licensed Material available under these terms and conditions.
Section 1 -- Definitions.
a. Adapted Material means material subject to Copyright and Similar
Rights that is derived from or based upon the Licensed Material
and in which the Licensed Material is translated, altered,
arranged, transformed, or otherwise modified in a manner requiring
permission under the Copyright and Similar Rights held by the
Licensor. For purposes of this Public License, where the Licensed
Material is a musical work, performance, or sound recording,
Adapted Material is always produced where the Licensed Material is
synched in timed relation with a moving image.
b. Adapter's License means the license You apply to Your Copyright
and Similar Rights in Your contributions to Adapted Material in
accordance with the terms and conditions of this Public License.
c. Copyright and Similar Rights means copyright and/or similar rights
closely related to copyright including, without limitation,
performance, broadcast, sound recording, and Sui Generis Database
Rights, without regard to how the rights are labeled or
categorized. For purposes of this Public License, the rights
specified in Section 2(b)(1)-(2) are not Copyright and Similar
Rights.
d. Effective Technological Measures means those measures that, in the
absence of proper authority, may not be circumvented under laws
fulfilling obligations under Article 11 of the WIPO Copyright
Treaty adopted on December 20, 1996, and/or similar international
agreements.
e. Exceptions and Limitations means fair use, fair dealing, and/or
any other exception or limitation to Copyright and Similar Rights
that applies to Your use of the Licensed Material.
f. Licensed Material means the artistic or literary work, database,
or other material to which the Licensor applied this Public
License.
g. Licensed Rights means the rights granted to You subject to the
terms and conditions of this Public License, which are limited to
all Copyright and Similar Rights that apply to Your use of the
Licensed Material and that the Licensor has authority to license.
h. Licensor means the individual(s) or entity(ies) granting rights
under this Public License.
i. Share means to provide material to the public by any means or
process that requires permission under the Licensed Rights, such
as reproduction, public display, public performance, distribution,
dissemination, communication, or importation, and to make material
available to the public including in ways that members of the
public may access the material from a place and at a time
individually chosen by them.
j. Sui Generis Database Rights means rights other than copyright
resulting from Directive 96/9/EC of the European Parliament and of
the Council of 11 March 1996 on the legal protection of databases,
as amended and/or succeeded, as well as other essentially
equivalent rights anywhere in the world.
k. You means the individual or entity exercising the Licensed Rights
under this Public License. Your has a corresponding meaning.
Section 2 -- Scope.
a. License grant.
1. Subject to the terms and conditions of this Public License,
the Licensor hereby grants You a worldwide, royalty-free,
non-sublicensable, non-exclusive, irrevocable license to
exercise the Licensed Rights in the Licensed Material to:
a. reproduce and Share the Licensed Material, in whole or
in part; and
b. produce, reproduce, and Share Adapted Material.
2. Exceptions and Limitations. For the avoidance of doubt, where
Exceptions and Limitations apply to Your use, this Public
License does not apply, and You do not need to comply with
its terms and conditions.
3. Term. The term of this Public License is specified in Section
6(a).
4. Media and formats; technical modifications allowed. The
Licensor authorizes You to exercise the Licensed Rights in
all media and formats whether now known or hereafter created,
and to make technical modifications necessary to do so. The
Licensor waives and/or agrees not to assert any right or
authority to forbid You from making technical modifications
necessary to exercise the Licensed Rights, including
technical modifications necessary to circumvent Effective
Technological Measures. For purposes of this Public License,
simply making modifications authorized by this Section 2(a)
(4) never produces Adapted Material.
5. Downstream recipients.
a. Offer from the Licensor -- Licensed Material. Every
recipient of the Licensed Material automatically
receives an offer from the Licensor to exercise the
Licensed Rights under the terms and conditions of this
Public License.
b. No downstream restrictions. You may not offer or impose
any additional or different terms or conditions on, or
apply any Effective Technological Measures to, the
Licensed Material if doing so restricts exercise of the
Licensed Rights by any recipient of the Licensed
Material.
6. No endorsement. Nothing in this Public License constitutes or
may be construed as permission to assert or imply that You
are, or that Your use of the Licensed Material is, connected
with, or sponsored, endorsed, or granted official status by,
the Licensor or others designated to receive attribution as
provided in Section 3(a)(1)(A)(i).
b. Other rights.
1. Moral rights, such as the right of integrity, are not
licensed under this Public License, nor are publicity,
privacy, and/or other similar personality rights; however, to
the extent possible, the Licensor waives and/or agrees not to
assert any such rights held by the Licensor to the limited
extent necessary to allow You to exercise the Licensed
Rights, but not otherwise.
2. Patent and trademark rights are not licensed under this
Public License.
3. To the extent possible, the Licensor waives any right to
collect royalties from You for the exercise of the Licensed
Rights, whether directly or through a collecting society
under any voluntary or waivable statutory or compulsory
licensing scheme. In all other cases the Licensor expressly
reserves any right to collect such royalties.
Section 3 -- License Conditions.
Your exercise of the Licensed Rights is expressly made subject to the
following conditions.
a. Attribution.
1. If You Share the Licensed Material (including in modified
form), You must:
a. retain the following if it is supplied by the Licensor
with the Licensed Material:
i. identification of the creator(s) of the Licensed
Material and any others designated to receive
attribution, in any reasonable manner requested by
the Licensor (including by pseudonym if
designated);
ii. a copyright notice;
iii. a notice that refers to this Public License;
iv. a notice that refers to the disclaimer of
warranties;
v. a URI or hyperlink to the Licensed Material to the
extent reasonably practicable;
b. indicate if You modified the Licensed Material and
retain an indication of any previous modifications; and
c. indicate the Licensed Material is licensed under this
Public License, and include the text of, or the URI or
hyperlink to, this Public License.
2. You may satisfy the conditions in Section 3(a)(1) in any
reasonable manner based on the medium, means, and context in
which You Share the Licensed Material. For example, it may be
reasonable to satisfy the conditions by providing a URI or
hyperlink to a resource that includes the required
information.
3. If requested by the Licensor, You must remove any of the
information required by Section 3(a)(1)(A) to the extent
reasonably practicable.
4. If You Share Adapted Material You produce, the Adapter's
License You apply must not prevent recipients of the Adapted
Material from complying with this Public License.
Section 4 -- Sui Generis Database Rights.
Where the Licensed Rights include Sui Generis Database Rights that
apply to Your use of the Licensed Material:
a. for the avoidance of doubt, Section 2(a)(1) grants You the right
to extract, reuse, reproduce, and Share all or a substantial
portion of the contents of the database;
b. if You include all or a substantial portion of the database
contents in a database in which You have Sui Generis Database
Rights, then the database in which You have Sui Generis Database
Rights (but not its individual contents) is Adapted Material; and
c. You must comply with the conditions in Section 3(a) if You Share
all or a substantial portion of the contents of the database.
For the avoidance of doubt, this Section 4 supplements and does not
replace Your obligations under this Public License where the Licensed
Rights include other Copyright and Similar Rights.
Section 5 -- Disclaimer of Warranties and Limitation of Liability.
a. UNLESS OTHERWISE SEPARATELY UNDERTAKEN BY THE LICENSOR, TO THE
EXTENT POSSIBLE, THE LICENSOR OFFERS THE LICENSED MATERIAL AS-IS
AND AS-AVAILABLE, AND MAKES NO REPRESENTATIONS OR WARRANTIES OF
ANY KIND CONCERNING THE LICENSED MATERIAL, WHETHER EXPRESS,
IMPLIED, STATUTORY, OR OTHER. THIS INCLUDES, WITHOUT LIMITATION,
WARRANTIES OF TITLE, MERCHANTABILITY, FITNESS FOR A PARTICULAR
PURPOSE, NON-INFRINGEMENT, ABSENCE OF LATENT OR OTHER DEFECTS,
ACCURACY, OR THE PRESENCE OR ABSENCE OF ERRORS, WHETHER OR NOT
KNOWN OR DISCOVERABLE. WHERE DISCLAIMERS OF WARRANTIES ARE NOT
ALLOWED IN FULL OR IN PART, THIS DISCLAIMER MAY NOT APPLY TO YOU.
b. TO THE EXTENT POSSIBLE, IN NO EVENT WILL THE LICENSOR BE LIABLE
TO YOU ON ANY LEGAL THEORY (INCLUDING, WITHOUT LIMITATION,
NEGLIGENCE) OR OTHERWISE FOR ANY DIRECT, SPECIAL, INDIRECT,
INCIDENTAL, CONSEQUENTIAL, PUNITIVE, EXEMPLARY, OR OTHER LOSSES,
COSTS, EXPENSES, OR DAMAGES ARISING OUT OF THIS PUBLIC LICENSE OR
USE OF THE LICENSED MATERIAL, EVEN IF THE LICENSOR HAS BEEN
ADVISED OF THE POSSIBILITY OF SUCH LOSSES, COSTS, EXPENSES, OR
DAMAGES. WHERE A LIMITATION OF LIABILITY IS NOT ALLOWED IN FULL OR
IN PART, THIS LIMITATION MAY NOT APPLY TO YOU.
c. The disclaimer of warranties and limitation of liability provided
above shall be interpreted in a manner that, to the extent
possible, most closely approximates an absolute disclaimer and
waiver of all liability.
Section 6 -- Term and Termination.
a. This Public License applies for the term of the Copyright and
Similar Rights licensed here. However, if You fail to comply with
this Public License, then Your rights under this Public License
terminate automatically.
b. Where Your right to use the Licensed Material has terminated under
Section 6(a), it reinstates:
1. automatically as of the date the violation is cured, provided
it is cured within 30 days of Your discovery of the
violation; or
2. upon express reinstatement by the Licensor.
For the avoidance of doubt, this Section 6(b) does not affect any
right the Licensor may have to seek remedies for Your violations
of this Public License.
c. For the avoidance of doubt, the Licensor may also offer the
Licensed Material under separate terms or conditions or stop
distributing the Licensed Material at any time; however, doing so
will not terminate this Public License.
d. Sections 1, 5, 6, 7, and 8 survive termination of this Public
License.
Section 7 -- Other Terms and Conditions.
a. The Licensor shall not be bound by any additional or different
terms or conditions communicated by You unless expressly agreed.
b. Any arrangements, understandings, or agreements regarding the
Licensed Material not stated herein are separate from and
independent of the terms and conditions of this Public License.
Section 8 -- Interpretation.
a. For the avoidance of doubt, this Public License does not, and
shall not be interpreted to, reduce, limit, restrict, or impose
conditions on any use of the Licensed Material that could lawfully
be made without permission under this Public License.
b. To the extent possible, if any provision of this Public License is
deemed unenforceable, it shall be automatically reformed to the
minimum extent necessary to make it enforceable. If the provision
cannot be reformed, it shall be severed from this Public License
without affecting the enforceability of the remaining terms and
conditions.
c. No term or condition of this Public License will be waived and no
failure to comply consented to unless expressly agreed to by the
Licensor.
d. Nothing in this Public License constitutes or may be interpreted
as a limitation upon, or waiver of, any privileges and immunities
that apply to the Licensor or You, including from the legal
processes of any jurisdiction or authority.
=======================================================================
Creative Commons is not a party to its public licenses.
Notwithstanding, Creative Commons may elect to apply one of its public
licenses to material it publishes and in those instances will be
considered the “Licensor.” The text of the Creative Commons public
licenses is dedicated to the public domain under the CC0 Public Domain
Dedication. Except for the limited purpose of indicating that material
is shared under a Creative Commons public license or as otherwise
permitted by the Creative Commons policies published at
creativecommons.org/policies, Creative Commons does not authorize the
use of the trademark "Creative Commons" or any other trademark or logo
of Creative Commons without its prior written consent including,
without limitation, in connection with any unauthorized modifications
to any of its public licenses or any other arrangements,
understandings, or agreements concerning use of licensed material. For
the avoidance of doubt, this paragraph does not form part of the public
licenses.
Creative Commons may be contacted at creativecommons.org.
# Wiki Fronzen Flask
# iGEM TeamName Wiki
This repository **MUST** contain all coding assets to generate your team's wiki (HTML, CSS, JavaScript, TypeScript, Python, etc).
Images, photos, icons and fonts **MUST** be stored on `static.igem.wiki` using [uploads.igem.org](https://uploads.igem.org), and Videos **must** be embedded from [iGEM Video Universe](https://video.igem.org).
## Getting started
To make it easy for you to get started with GitLab, here's a list of recommended next steps.
Already a pro? Just edit this README.md and make it your own. Want to make it easy? [Use the template at the bottom](#editing-this-readme)!
## Add your files
For up-to-date requirements, resources, help and guidance, visit [competition.igem.org/deliverables/team-wiki](https://competition.igem.org/deliverables/team-wiki).
- [ ] [Create](https://docs.gitlab.com/ee/user/project/repository/web_editor.html#create-a-file) or [upload](https://docs.gitlab.com/ee/user/project/repository/web_editor.html#upload-a-file) files
- [ ] [Add files using the command line](https://docs.gitlab.com/ee/gitlab-basics/add-file.html#add-a-file-using-the-command-line) or push an existing Git repository with the following command:
## Getting started
You should probably only edit the files inside folders `static`, `wiki` and `wiki > pages`.
1. Open the Web IDE
1. Make the changes on the files you wish:
* For the menu, change the file [menu.html](wiki/menu.html)
* For the layout, change the file [layout.html](wiki/layout.html)
* For the pages, change the corresponding file in the foler [pages](wiki/pages)
1. Review the changes you made
1. Once you are done, save the changes by **committing** them to the *main branch* of the repository
1. An automated script will build, test and deploy your wiki, which should take less than 30 seconds.
## About this Template
### Files
The static assets are in the `static` directory. The layout and templates are in the `wiki` directory, and the pages live in the `wiki > pages` directory. Unless you are an experienced and/or adventurous human, you probably shouldn't change other files.
|__ static/ -> static assets (CSS and JavaScript files only)
|__ wiki/ -> Main directory for the pages and layouts
|__ footer.html -> Footer that will appear in all the pages
|__ layout.html -> Main layout of your wiki. All the pages will follow its structure
|__ menu.html -> Menu that will appear in all the pages
|__ pages/ -> Directory for all the pages
|__ *.html -> Actual pages of your wiki
|__ .gitignore -> Tells GitLab which files/directories should not be uploaded to the repository
|__ .gitlab-ci.yml -> Automated flow for building, testing and deploying your website.
|__ LICENSE -> License CC-by-4.0, all wikis are required to have this license - DO NOT MODIFY
|__ README.md -> File containing the text you are reading right now
|__ app.py -> Python code managing your wiki
|__ dependencies.txt -> Software dependencies from the Python code
### Technologies
* [GitLab Pages](https://docs.gitlab.com/ee/user/project/pages/)
* [Python](https://www.python.org): Programming language
* [Flask](https://palletsprojects.com/p/flask/): Python framework
* [Fronzen-Flask](https://pythonhosted.org/Frozen-Flask): Library that builds the wiki to be deployed as a static website
* [Bootstrap](https://getbootstrap.com/docs/5.0/components): CSS and JS components used
### Building locally (advanced users)
To work locally with this project, you'll have to follow the steps below:
#### Install
```bash
git clone https://gitlab.igem.org/templates/wiki-frozen-flask
cd example
python3 -m venv venv
. venv/bin/activate
pip install -r dependencies.txt
```
cd existing_repo
git remote add origin https://gitlab.igem.org/templates/wiki-fronzen-flask.git
git branch -M main
git push -uf origin main
```
## Integrate with your tools
- [ ] [Set up project integrations](https://gitlab.igem.org/templates/wiki-fronzen-flask/-/settings/integrations)
## Collaborate with your team
- [ ] [Invite team members and collaborators](https://docs.gitlab.com/ee/user/project/members/)
- [ ] [Create a new merge request](https://docs.gitlab.com/ee/user/project/merge_requests/creating_merge_requests.html)
- [ ] [Automatically close issues from merge requests](https://docs.gitlab.com/ee/user/project/issues/managing_issues.html#closing-issues-automatically)
- [ ] [Enable merge request approvals](https://docs.gitlab.com/ee/user/project/merge_requests/approvals/)
- [ ] [Automatically merge when pipeline succeeds](https://docs.gitlab.com/ee/user/project/merge_requests/merge_when_pipeline_succeeds.html)
## Test and Deploy
Use the built-in continuous integration in GitLab.
- [ ] [Get started with GitLab CI/CD](https://docs.gitlab.com/ee/ci/quick_start/index.html)
- [ ] [Analyze your code for known vulnerabilities with Static Application Security Testing(SAST)](https://docs.gitlab.com/ee/user/application_security/sast/)
- [ ] [Deploy to Kubernetes, Amazon EC2, or Amazon ECS using Auto Deploy](https://docs.gitlab.com/ee/topics/autodevops/requirements.html)
- [ ] [Use pull-based deployments for improved Kubernetes management](https://docs.gitlab.com/ee/user/clusters/agent/)
- [ ] [Set up protected environments](https://docs.gitlab.com/ee/ci/environments/protected_environments.html)
***
# Editing this README
When you're ready to make this README your own, just edit this file and use the handy template below (or feel free to structure it however you want - this is just a starting point!). Thank you to [makeareadme.com](https://www.makeareadme.com/) for this template.
## Suggestions for a good README
Every project is different, so consider which of these sections apply to yours. The sections used in the template are suggestions for most open source projects. Also keep in mind that while a README can be too long and detailed, too long is better than too short. If you think your README is too long, consider utilizing another form of documentation rather than cutting out information.
## Name
Choose a self-explaining name for your project.
## Description
Let people know what your project can do specifically. Provide context and add a link to any reference visitors might be unfamiliar with. A list of Features or a Background subsection can also be added here. If there are alternatives to your project, this is a good place to list differentiating factors.
## Badges
On some READMEs, you may see small images that convey metadata, such as whether or not all the tests are passing for the project. You can use Shields to add some to your README. Many services also have instructions for adding a badge.
## Visuals
Depending on what you are making, it can be a good idea to include screenshots or even a video (you'll frequently see GIFs rather than actual videos). Tools like ttygif can help, but check out Asciinema for a more sophisticated method.
## Installation
Within a particular ecosystem, there may be a common way of installing things, such as using Yarn, NuGet, or Homebrew. However, consider the possibility that whoever is reading your README is a novice and would like more guidance. Listing specific steps helps remove ambiguity and gets people to using your project as quickly as possible. If it only runs in a specific context like a particular programming language version or operating system or has dependencies that have to be installed manually, also add a Requirements subsection.
## Usage
Use examples liberally, and show the expected output if you can. It's helpful to have inline the smallest example of usage that you can demonstrate, while providing links to more sophisticated examples if they are too long to reasonably include in the README.
## Support
Tell people where they can go to for help. It can be any combination of an issue tracker, a chat room, an email address, etc.
## Roadmap
If you have ideas for releases in the future, it is a good idea to list them in the README.
## Contributing
State if you are open to contributions and what your requirements are for accepting them.
For people who want to make changes to your project, it's helpful to have some documentation on how to get started. Perhaps there is a script that they should run or some environment variables that they need to set. Make these steps explicit. These instructions could also be useful to your future self.
You can also document commands to lint the code or run tests. These steps help to ensure high code quality and reduce the likelihood that the changes inadvertently break something. Having instructions for running tests is especially helpful if it requires external setup, such as starting a Selenium server for testing in a browser.
## Authors and acknowledgment
Show your appreciation to those who have contributed to the project.
## License
For open source projects, say how it is licensed.
## Project status
If you have run out of energy or time for your project, put a note at the top of the README saying that development has slowed down or stopped completely. Someone may choose to fork your project or volunteer to step in as a maintainer or owner, allowing your project to keep going. You can also make an explicit request for maintainers.
#### Execute
```bash
python app.py
```
app.py 0 → 100644
from os import path
from pathlib import Path
from flask import Flask, render_template
from flask_frozen import Freezer
template_folder = path.abspath('./wiki')
app = Flask(__name__, template_folder=template_folder)
#app.config['FREEZER_BASE_URL'] = environ.get('CI_PAGES_URL')
app.config['FREEZER_DESTINATION'] = 'public'
app.config['FREEZER_RELATIVE_URLS'] = True
app.config['FREEZER_IGNORE_MIMETYPE_WARNINGS'] = True
freezer = Freezer(app)
@app.cli.command()
def freeze():
freezer.freeze()
@app.cli.command()
def serve():
freezer.run()
@app.route('/')
def index():
return render_template('pages/index.html')
@app.route('/<page>')
def pages(page):
return render_template(str(Path('pages') / (page.lower() + '.html')))
# Main Function, Runs at http://0.0.0.0:8080
if __name__ == "__main__":
app.run(port=8080)
frozen-flask
This diff is collapsed.
This diff is collapsed.
body { padding-top: 56px; }
.left-aligned { margin-left: auto; }
.bg-dark { background-color: #343a40 !important; }
.bg-hero { background-color: #7952b3; }
/* CALLOUT */
.bd-callout { padding:1.25rem; margin-top:1.25rem; margin-bottom:1.25rem; border:1px solid #e9ecef; border-left-width:.25rem; border-radius:.25rem }
.bd-callout h4 { margin-bottom:.25rem }
.bd-callout p:last-child { margin-bottom:0 }
.bd-callout code { border-radius:.25rem }
.bd-callout+.bd-callout { margin-top:-.25rem }
.bd-callout-info { border-left-color:#5bc0de }
.bd-callout-warning { border-left-color:#f0ad4e }
.bd-callout-danger { border-left-color:#d9534f }
/* footer */
footer a { color: white; font-weight: bold; text-decoration: none; }
footer a:hover { color: white; text-decoration: underline; }
<footer class="pt-5 pb-5 footer py-5 mt-5 bg-dark text-white">
<div class="container">
<div class="row mb-4">
<div class="col-lg-6 col-xs-12">
<h4 class="mb-3">Heading</h4>
<p>Lorem ipsum dolor sit amet, consectetur adipiscing elit. Nullam ac ante mollis quam tristique convallis</p>
</div>
<div class="col-lg-3 col-xs-12">
<h4 class="mt-lg-0 mt-sm-3">Links</h4>
<ul class="m-2 p-2">
<li><a href="#">Lorem ipsum</a></li>
<li><a href="#">Nam mauris velit</a></li>
<li><a href="#">Etiam vitae mauris</a></li>
<li><a href="#">Fusce scelerisque</a></li>
<li><a href="#">Sed faucibus</a></li>
<li><a href="#">Mauris efficitur nulla</a></li>
</ul>
</div>
<div class="col-lg-3 col-xs-12">
<h4 class="mt-lg-0 mt-sm-4 mb-3">Contact</h4>
<p>22, Lorem ipsum dolor, consectetur adipiscing</p>
<p class="mb-0">(541) 754-3010</p>
<p>info@hsdf.com</p>
</div>
</div>
<hr>
<!-- The following MUST be on every page: license information and link to the repository on gitlab.igem.org -->
<div class="row mt-4">
<div class="col">
<p class="mb-0"><small>© 2022 - Content on this site is licensed under a <a class="subfoot" href="https://creativecommons.org/licenses/by/4.0/" rel="license">Creative Commons Attribution 4.0 International license</a>.</small></p>
<p><small>The repository used to create this website is available at <a href="https://gitlab.igem.org/templates/wiki-frozen-flask">gitlab.igem.org/templates/wiki-frozen-flask</a>.</small></p>
</div>
</div>
</div>
</footer>
<!doctype html>
<html lang="en">
<head>
<!-- Required meta tags -->
<meta charset="utf-8">
<meta name="viewport" content="width=device-width, initial-scale=1">
<link rel="shortcut icon" href="https://static.igem.wiki/common/icons/favicons/igem-2022.svg"/>
<link rel="license" href="https://creativecommons.org/licenses/by/4.0/"/>
<!-- Bootstrap CSS -->
<link href="{{ url_for('static', filename = 'bootstrap.min.css') }}" rel="stylesheet">
<!-- Custom CSS -->
<link href="{{ url_for('static', filename = 'style.css') }}" rel="stylesheet">
<title>{% block title %}{% endblock %} | TeamName - iGEM 2022</title>
</head>
<body>
<!-- Navigation -->
{% include 'menu.html' %}
<!-- Header -->
<header class="bg-hero py-5 mb-5">
<div class="container h-100">
<div class="row h-100 align-items-center">
<div class="col-lg-12">
<h1 class="display-4 text-white mt-5 mb-2">{{ self.title() }}</h1>
<p class="lead mb-5 text-white-50">{% block lead %}{% endblock %}</p>
</div>
</div>
</div>
</header>
<!-- Page Content -->
<div class="container">
{% block page_content %}{% endblock %}
</div>
<!-- Footer -->
{% include 'footer.html' %}
<!-- Wiki Tools -->
{% include 'wikitools.html' %}
<!-- Bootstrap Bundle with Popper -->
<script src="{{ url_for('static', filename = 'bootstrap.bundle.min.js') }}"></script>
</body>
</html>
<nav class="navbar navbar-expand-lg navbar-dark bg-dark fixed-top">
<div class="container">
<!---- TEAM NAME ---->
<a class="navbar-brand" href="#">TeamName</a>
<!---- SMALL SCREEN MENU ICON ---->
<button class="navbar-toggler" type="button" data-bs-toggle="collapse" data-bs-target="#navbarSupportedContent" aria-controls="navbarSupportedContent" aria-expanded="false" aria-label="Toggle navigation">
<span class="navbar-toggler-icon"></span>
</button>
<div class="collapse navbar-collapse" id="navbarSupportedContent">
<ul class="navbar-nav ml-auto left-aligned">
<!---- HOME ---->
<li class="nav-item">
<a class="nav-link" href="{{ url_for('index') }}">Home</a>
</li>
<!---- TEAM ---->
<li class="nav-item dropdown">
<a class="nav-link dropdown-toggle" href="{{ url_for('pages', page='team') }}" id="navbarDropdown" role="button" data-bs-toggle="dropdown" aria-expanded="false">
Team
</a>
<ul class="dropdown-menu" aria-labelledby="navbarDropdown">
<li><a class="dropdown-item" href="{{ url_for('pages', page='team') }}">Team</a></li>
<li><a class="dropdown-item" href="{{ url_for('pages', page='attributions') }}">Attributions</a></li>
<li><a class="dropdown-item" href="{{ url_for('pages', page='collaborations') }}">Collaborations</a></li>
</ul>
</li>
<!---- PROJECT ---->
<li class="nav-item dropdown">
<a class="nav-link dropdown-toggle" href="#" id="navbarDropdown" role="button" data-bs-toggle="dropdown" aria-expanded="false">
Project
</a>
<ul class="dropdown-menu" aria-labelledby="navbarDropdown">
<li><a class="dropdown-item" href="{{ url_for('pages', page='communication') }}">Communication</a></li>
<li><a class="dropdown-item" href="{{ url_for('pages', page='contribution') }}">Contribution</a></li>
<li><a class="dropdown-item" href="{{ url_for('pages', page='description') }}">Description</a></li>
<li><a class="dropdown-item" href="{{ url_for('pages', page='engineering') }}">Engineering</a></li>
<li><a class="dropdown-item" href="{{ url_for('pages', page='experiments') }}">Experiments</a></li>
<li><a class="dropdown-item" href="{{ url_for('pages', page='implementation') }}">Implementation</a></li>
<li><a class="dropdown-item" href="{{ url_for('pages', page='notebook') }}">Notebook</a></li>
<li><a class="dropdown-item" href="{{ url_for('pages', page='partnership') }}">Partnership</a></li>
<li><a class="dropdown-item" href="{{ url_for('pages', page='proof-of-concept') }}">Proof of Concept</a></li>
<li><a class="dropdown-item" href="{{ url_for('pages', page='results') }}">Results</a></li>
</ul>
</li>
<!---- PARTS ---->
<li class="nav-item dropdown">
<a class="nav-link dropdown-toggle" href="#" id="navbarDropdown" role="button" data-bs-toggle="dropdown" aria-expanded="false">
Parts
</a>
<ul class="dropdown-menu" aria-labelledby="navbarDropdown">
<li><a class="dropdown-item" href="{{ url_for('pages', page='part-collection') }}">Part Collection</a></li>
<li><a class="dropdown-item" href="{{ url_for('pages', page='parts') }}">Parts</a></li>
<li><a class="dropdown-item" href="{{ url_for('pages', page='improve') }}">Improve</a></li>
</ul>
</li>
<!---- SAFETY ---->
<li class="nav-item">
<a class="nav-link" href="{{ url_for('pages', page='safety') }}">Safety</a>
</li>
<!---- HUMAN PRACTICES ---->
<li class="nav-item">
<a class="nav-link" href="{{ url_for('pages', page='human-practices') }}">Human Practices</a>
</li>
<!---- AWARDS ---->
<li class="nav-item dropdown">
<a class="nav-link dropdown-toggle" href="#" id="navbarDropdown" role="button" data-bs-toggle="dropdown" aria-expanded="false">
Awards
</a>
<ul class="dropdown-menu" aria-labelledby="navbarDropdown">
<li><a class="dropdown-item" href="{{ url_for('pages', page='education') }}">Education</a></li>
<li><a class="dropdown-item" href="{{ url_for('pages', page='entrepreneurship') }}">Entrepreneurship</a></li>
<li><a class="dropdown-item" href="{{ url_for('pages', page='hardware') }}">Hardware</a></li>
<li><a class="dropdown-item" href="{{ url_for('pages', page='inclusivity') }}">Inclusivity</a></li>
<li><a class="dropdown-item" href="{{ url_for('pages', page='measurement') }}">Measurement</a></li>
<li><a class="dropdown-item" href="{{ url_for('pages', page='model') }}">Model</a></li>
<li><a class="dropdown-item" href="{{ url_for('pages', page='plant') }}">Plant</a></li>
<li><a class="dropdown-item" href="{{ url_for('pages', page='software') }}">Software</a></li>
<li><a class="dropdown-item" href="{{ url_for('pages', page='sustainable') }}">Sustainable</a></li>
</ul>
</li>
</ul>
</div>
</div>
</nav>
{% extends "layout.html" %}
{% block title %}Attributions{% endblock %}
{% block lead %}Use this page to attribute work done on your project. This includes the work done by each of the student members on your team and any work that was done by people outside of your team, including the host labs, advisors, instructors, and individuals not on the team roster. This requirement is not about literature references - these can and should be displayed throughout your wiki.{% endblock %}
{% block page_content %}
<div class="row mt-4">
<div class="col">
<div class="bd-callout bd-callout-info">
<h4>Bronze Medal Criterion #2</h4>
<p>Describe what work your team members did and what other people did for your project.</p>
<hr>
<p>Please see the <a href="https://competition.igem.org/judging/medals">2022 Medals Page</a> for more information.</p>
</div>
</div>
</div>
<div class="row mt-4">
<div class="col-8">
<h2>What should this page contain?</h2>
<hr>
<ul>
<li>Clearly state what each member of the team accomplished. We have provided some recommended categories below. Your team may also have other categories you can include.</li>
<ul>
<li><strong>Analysis:</strong> analyzing data generated by your team, another iGEM team (current or previous), and/or from literature as needed for your project</li>
<li><strong>Conceptualization:</strong> brainstorming and developing ideas for the project</li>
<li><strong>Investigation:</strong> performing the experiments and/or collecting data/evidence </li>
<li><strong>Lab Maintenance:</strong> cleaning, organizing, and preparing the research facilities or lab </li>
<li><strong>Fundraising:</strong> raising money, in-kind donations of materials, and/or services for the team’s activities</li>
<li><strong>Public Engagement:</strong> preparing and/or implementing tools/activities to engage the broader community </li>
<li><strong>Entrepreneurship:</strong> developing business models and other commercially relevant materials or activities</li>
<li><strong>Background Research:</strong> reading peer-reviewed scientific research articles, white papers, regulations/guidelines, and other documents</li>
<li><strong>Data Curation:</strong> annotating (producing metadata), cleaning, and maintaining research data for your team's project and for future use by other iGEM teams or members of the synthetic biology community</li>
<li><strong>Software:</strong> developing, implementing, and/or testing computer programs and code</li>
<li><strong>Hardware:</strong> designing, building, and/or testing mechanical, electrical, or optical hardware systems</li>
<li><strong>Project Administration:</strong> managing and coordinating the project activities, planning, and execution</li>
<li><strong>Visualization:</strong> preparation, creation and/or presentation of the work including data visualization, user interfaces, videos and other graphics</li>
<li><strong>Writing:</strong> writing, reviewing or editing content for the wiki or other documents to be shared outside the team</li>
<li><strong>Safety:</strong> performing activities to ensure compliance with the safety guidelines or requirements of iGEM, your institution, and/or government</li>
</ul>
<li>Clearly state who provided the student team members with:</li>
<ul>
<li>General support</li>
<li>Project support and advice</li>
<li>Fundraising help and advice</li>
<li>Lab support</li>
<li>Difficult technique support</li>
<li>Project advisor support</li>
<li>Wiki support</li>
<li>Presentation coaching</li>
<li>Human Practices support</li>
</ul>
<li>Thanks and acknowledgements for all other people involved in helping make your team successful
<li>Literature references: we encourage you to display literature references throughout your entire wiki
</ul>
</div>
<div class="col-4">
<h2>Inspiration</h2>
<hr>
<ul>
<li><a href="https://2019.igem.org/Team:William_and_Mary/Attributions">2019 William and Mary</a></li>
<li><a href="https://2019.igem.org/Team:Thessaloniki/Attributions">2019 Thessaloniki </a></li>
<li><a href="https://2019.igem.org/Team:Sydney_Australia/Attributions">2019 Sydney Australia </a></li>
<li><a href="https://2020.igem.org/Team:AUC-EGYPT/Attributions">2020 AUC EGYPT</a></li>
<li><a href="https://2020.igem.org/Team:Korea-SIS/Attributions">2020 Korea SIS</a></li>
<li><a href="https://2020.igem.org/Team:Manchester/Attributions">2020 Manchester</a></li>
<li><a href="https://2020.igem.org/Team:NJTech_China/Attributions">2020 NJTech China</a></li>
</ul>
</div>
</div>
<div class="row mt-4">
<div class="col-6">
<h2>Why is this page needed?</h2>
<hr>
<p>The Attribution requirement helps the judges know what you did yourselves and what you had help with. You can get help with difficult or complex techniques, but you must report what work your team did and what work was done by others.</p>
<p>For example, you might choose to work with an animal model during your project. Working with animals requires getting a license and applying far in advance to conduct certain experiments in many countries. This is difficult to achieve during the course of a summer, but much easier if you can work with a postdoc or PI who has the right licenses.</p>
</div>
<div class="col-6">
<h2>Can we base our project on a previous one?</h2>
<hr>
<p>Yes! You can have a project based on a previous team, or based on someone else's idea, <b>as long as you state this fact very clearly and give credit for the original project.</b></p>
</div>
</div>
{% endblock %}
\ No newline at end of file
{% extends "layout.html" %}
{% block title %}Collaborations{% endblock %}
{% block lead %}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.{% endblock %}
{% block page_content %}
<div class="row mt-4">
<div class="col">
<div class="bd-callout bd-callout-info">
<h4>Silver Medal Criterion #2</h4>
<p>Collaborate with one (or more) 2022 iGEM team(s) in a meaningful way.</p>
<hr>
<p>Please see the <a href="https://competition.igem.org/judging/medals">2022 Medals Page</a> for more information.</p>
</div>
</div>
</div>
<div class="row mt-4">
<div class="col-6">
<h2>Which teams can we work with?</h2>
<hr>
<p>You can work with any other iGEM 2022 team in the competition. You can also work with non-iGEM research groups, but they do not count towards the iGEM team collaboration silver medal criterion.</p>
</div>
<div class="col-6">
<h2>Some suggestions</h2>
<hr>
<ul>
<li>Improve the function of another team's BioBrick Part or Device</li>
<li>Characterize another team's part</li>
<li>Debug a construct</li>
<li>Model or simulate another team's system</li>
<li>Test another team's software</li>
<li>Help build and test another team's hardware project</li>
</ul>
</div>
</div>
{% endblock %}
{% extends "layout.html" %}
{% block title %}Communication{% endblock %}
{% block lead %}Develop and implement education, science communication, and/or outreach materials related to synthetic biology.{% endblock %}
{% block page_content %}
<div class="row mt-4">
<div class="col">
<div class="bd-callout bd-callout-info">
<h4>Gold Medal Criterion #6: Education & Communication</h4>
<p>Develop and implement education, science communication, and/or outreach materials related to synthetic biology.<p>
<p>All activities must follow Safety policies for <a href="https://responsibility.igem.org/safety-policies/human-subjects">Human Subjects Research</a>.</p>
<hr>
<p>Please see the <a href="https://competition.igem.org/judging/medals">2022 Medals Page</a> for more information.</p>
</div>
</div>
</div>
{% endblock %}
\ No newline at end of file
{% extends "layout.html" %}
{% block title %}Contribution{% endblock %}
{% block lead %}Make a useful contribution for future iGEM teams. Use this page to document that contribution.{% endblock %}
{% block page_content %}
<div class="row mt-4">
<div class="col">
<div class="bd-callout bd-callout-info">
<h4>Bronze Medal Criterion #4</h4>
<p>Make a useful contribution for future iGEM teams. Use this page to document that contribution.<p>
<p>If you are making a contribution by adding information to an existing Part or creating a new Part, you must document your contribution on the Part's Main Page on the <a href="http://parts.igem.org/Main_Page">Registry</a> for your team to be eligible for this criteria. You can use this page to link to that part and include additional information about your contribution.</p>
<hr>
<p>Please see the <a href="https://competition.igem.org/judging/medals">2022 Medals Page</a> for more information.</p>
</div>
</div>
</div>
{% endblock %}
{% extends "layout.html" %}
{% block title %}Project Description{% endblock %}
{% block lead %}Describe how and why you chose your iGEM project.{% endblock %}
{% block page_content %}
<div class="row mt-4">
<div class="col">
<div class="bd-callout bd-callout-info">
<h4>Bronze Medal Criterion #3</h4>
<p>Describe how and why you chose your iGEM project.<p>
<hr>
<p>Please see the <a href="https://competition.igem.org/judging/medals">2022 Medals Page</a> for more information.</p>
</div>
</div>
</div>
<div class="row mt-4">
<div class="col-8">
<h2>What should this page contain?</h2>
<hr>
<ul>
<li>A clear and concise description of your project.</li>
<li>A detailed explanation of why your team chose to work on this particular project.</li>
<li>References and sources to document your research.</li>
<li>Use illustrations and other visual resources to explain your project.</li>
</ul>
</div>
<div class="col-4">
<h2>Inspirations</h2>
<hr>
<ul>
<li><a href="https://2019.igem.org/Team:Leiden/Description">2019 Leiden</a></li>
<li><a href="https://2019.igem.org/Team:ITESO_Guadalajara/Description">2019 ITESO Guadalajara</a></li>
<li><a href="https://2020.igem.org/Team:Technion-Israel/Description">2020 Technion Israel</a></li>
<li><a href="https://2020.igem.org/Team:Botchan_Lab_Tokyo/Description">2020 Botchan Lab Tokyo</a></li>
<li><a href="https://2020.igem.org/Team:St_Andrews/Description">2020 St Andrews</a></li>
<li><a href="https://2020.igem.org/Team:MIT/Description">2020 MIT</a></li>
</ul>
</div>
</div>
<div class="row mt-4">
<div class="col-8">
<h2>Some advice</h2>
<hr>
<p>We encourage you to put up a lot of information and content on your wiki, but we also encourage you to include summaries as much as possible. If you think of the sections in your project description as the sections in a publication, you should try to be concise, accurate, and unambiguous in your achievements. Your Project Description should include more information than your project abstract.</p>
</div>
<div class="col-4">
<h2>References</h2>
<hr>
<p>iGEM teams are encouraged to record references you use during the course of your research. They should be posted somewhere on your wiki so that judges and other visitors can see how you thought about your project and what works inspired you.</p>
</div>
</div>
{% endblock %}
{% extends "layout.html" %}
{% block title %}Education{% endblock %}
{% block lead %}Innovative educational tools and outreach activities have the ability to establish a two-way dialogue with new communities by discussing public values and the science behind synthetic biology.{% endblock %}
{% block page_content %}
<div class="row mt-4">
<div class="col">
<div class="bd-callout bd-callout-info">
<h4>Best Education Special Prize</h4>
<p>How have you developed new opportunities to include more people in shaping synthetic biology? Innovative educational tools and outreach activities have the ability to establish a two-way dialogue with new communities by discussing public values and the science behind synthetic biology. Document your approach and what was learned by everyone involved to compete for this award.</p>
<p>To compete for the Best Education Prize, please describe your work on this page and also fill out the description on the <a href="https://competition.igem.org/deliverables/judging-form">judging form</a>.</p>
<hr>
<p>Please see the <a href="https://competition.igem.org/judging/awards">2022 Awards Page</a> for more information.</p>
</div>
</div>
</div>
<div class="row mt-4">
<div class="col">
<h2>Inspirations</h2>
<hr>
<ul>
<li><a href="https://2020.igem.org/Team:CCA_San_Diego/Education">2020 CCA San Diego</a></li>
<li><a href="https://2020.igem.org/Team:Lambert_GA/Education">2020 Lambert GA</a></li>
<li><a href="https://2020.igem.org/Team:Stanford/Education">2020 Stanford</a></li>
<li><a href="https://2020.igem.org/Team:Waseda/Education">2020 Waseda</a></li>
<li><a href="https://2020.igem.org/Team:Fudan/Education">2020 Fudan</a></li>
<li><a href="https://2020.igem.org/Team:Toulouse_INSA-UPS/Education">2020 Toulouse INSA UPS</a></li>
</ul>
</div>
</div>
{% endblock %}
{% extends "layout.html" %}
{% block title %}Engineering Success{% endblock %}
{% block lead %}Demonstrate engineering success in a part of your project by going through at least one iteration of the engineering design cycle.{% endblock %}
{% block page_content %}
<div class="row mt-4">
<div class="col">
<div class="bd-callout bd-callout-info">
<h4>Silver Medal Criterion #1</h4>
<p>Demonstrate engineering success in a part of your project by going through at least one iteration of the engineering design cycle. This achievement should be distinct from your Contribution for Bronze.<p>
<p>If you plan to show engineering success by creating a new Part that has been shown to work as expected, you must document your contribution on the Part's Main Page on the <a href="http://parts.igem.org/Main_Page">Registry</a> for your team to be eligible for this criteria.</p>
<hr>
<p>Please see the <a href="https://competition.igem.org/judging/medals">2022 Medals Page</a> for more information.</p>
</div>
</div>
</div>
{% endblock %}
{% extends "layout.html" %}
{% block title %}Entrepreneurship{% endblock %}
{% block lead %}The entrepreneurship prize recognizes exceptional effort to build a business case and commercialize an iGEM project.{% endblock %}
{% block page_content %}
<div class="row mt-4">
<div class="col">
<div class="bd-callout bd-callout-info">
<h4>Best Supporting Entrepreneurship Special Prize</h4>
<p>The Best Supporting Entrepreneurship award recognizes exceptional effort to build a business case and commercialize an iGEM project. This award is open to all teams to show that entrepreneurship is something all teams can aspire to do with their project. This award can go to an new project, or to a previous project that a team aimed to commercialize. Have you filed a provisional patent on your project/device/process? Have you raised money to build and ship products? Have you pitched your idea to investors and received money? As always in iGEM, the aim is to impress the judges!</p>
<p>To compete for the Best Supporting Entrepreneurship prize, please describe your work on this page and also fill out the description on the <a href="https://competition.igem.org/deliverables/judging-form">judging form</a>.</p>
<hr>
<p>Please see the <a href="https://competition.igem.org/judging/awards">2022 Awards Page</a> for more information.</p>
</div>
</div>
</div>
<div class="row mt-4">
<div class="col-8">
<h2>Patents and intellectual property</h2>
<hr>
<p>If your team is seriously considering commercializing and looking into building a company after the competition, you may want to look at how you are going to protect your work and secure investment. Investors will usually require some form of intellectual protection, so you may want to investigate how to apply for a patent or provisional patent in your country and region before disclosing your project at iGEM. Remember that you can only be evaluated in iGEM based on what you share on your wiki and at the Jamboree, so any work you don't present can't count towards your project.</p>
<p>This is an area where we are different as we care about sharing, openness and contributing to the community and investors don't always agree with these values. It is up to you and your team to decide what to do. Remember that most universities have a commercialization department and that you can talk to them before coming to a decision.</p>
</div>
<div class="col-4">
<h2>Inspirations</h2>
<hr>
<ul>
<li><a href="https://2019.igem.org/Team:UCopenhagen/Entrepreneurship">2019 UCopenhagen</a></li>
<li><a href="https://2019.igem.org/Team:Thessaly/Entrepreneurship">2019 Thessaly</a></li>
<li><a href="https://2019.igem.org/Team:NCKU_Tainan/Entrepreneurship">2019 NCKU Tainan</a></li>
<li><a href="https://2020.igem.org/Team:TAS_Taipei/Entrepreneurship">2020 TAS Taipei</a></li>
<li><a href="https://2020.igem.org/Team:KCL_UK/Entrepreneurship">2020 KCL UK</a></li>
<li><a href="https://2020.igem.org/Team:Calgary/Entrepreneurship">2020 Calgary</a></li>
</ul>
</div>
</div>
{% endblock %}
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment