"
Our Vision
Synthetic biology in Finland. How to tell about science to a general crowd. Science for business, business for science, us in the middle. Brian.
All the difficulties in biotechnology startups.
Team:Aalto-Helsinki/Outreach
From 2014.igem.org
(Difference between revisions)
| Line 116: | Line 116: | ||
<h3>A Website for the General Public</h3> | <h3>A Website for the General Public</h3> | ||
<p> | <p> | ||
| - | At the very beginning of the project we wanted to create a website that we could link to our friends, new acquaintances and potential sponsors. It included basic info about us and general overview of the project. We started developing it rapidly and it actually got into a presentable shape fairly fast. We expected to attract sponsors with the page, but the most important function turned about to be for media to use as a basis for a story and for our Facebook fans to get a more in-depth introduction to us. | + | At the very beginning of the project we wanted to create a website that we could link to our friends, new acquaintances and potential sponsors. It included basic info about us and a general overview of the project. We started developing it rapidly and it actually got into a presentable shape fairly fast. |
| + | </p> | ||
| + | <p> | ||
| + | We expected to attract sponsors with the page, but the most important function turned about to be for media to use as a basis for a story and for our Facebook fans to get a more in-depth introduction to us. It was also really good practice for making the wiki. Using GitHub together with several people was a new experience and sometimes it was difficult to find out why things weren't working how we thought they should work. | ||
</p> | </p> | ||
</div> | </div> | ||
| Line 125: | Line 128: | ||
</p> | </p> | ||
</div> | </div> | ||
| + | </div> | ||
| - | + | <h3>Creating the Wiki</h3> | |
| - | + | <p> | |
| - | + | Making a good wiki was an important thing for us. It had to be simple, well formatted but also nice to look at and informative. We wanted it to represent our team well. We wanted to take our time with it and develop it with care. So, we started early and proceeded to create our wiki steadily, step by step. It turned out amazingly well. It's completely responsive so it looks good on any platform: phones, pads, desktops. We also hope that you can effortlessly find everything you'd want to, and that scrolling through the content is a pleasent experience for every visitor. | |
| - | + | </p> | |
| - | + | ||
| - | + | ||
| - | + | ||
| - | + | ||
| - | + | ||
| - | + | ||
| - | + | ||
<p> | <p> | ||
| - | We | + | Figuring out the best way to present ourselves in the wiki was a tough problem to solve. We thought about many options but ended up having a little similar layout that we had used in the practice website. Having a sidebar seemed like a fun idea at first but we gave it up to keep things aesthetically pleasing and to make it possible to browse the wiki on all platforms. Scrolling through the content felt like a great choice, so instead of countless different subcategories, we only have eight categories and you can just scroll through them. Also sorting out the categories felt very difficult but in the end it feels like everything found their own place. |
| - | + | </p> | |
| + | <p> | ||
| + | The first thing we did for making the wiki was an upload tool: <a href="http://github.com/iGEM-QSF/igem-wiki">iGEM Wiki Quickifier</a>. With it we could upload content to a our team wiki without using the cumbersome wiki interface. We could write our pages as html files and the script would add the needed template tags as it uploaded the pages to the wiki. Uploading content to other wikis than ours is not implemented (yet), but if you know python, modifying the script should be an easy task. | ||
| + | </p> | ||
| + | <p> | ||
| + | We used GitHub to keep our texts syncronized so you can also browse the work process from our commit history. Here's the <a href="http://github.com/iGEM-QSF/igem-wiki">GitHub page of our wiki</a>. You can, of course, also browse the code that's here on the final version of the wiki. | ||
| + | </p> | ||
<p> | <p> | ||
| - | + | We made the wiki from scratch: we didn't use any templates but we designed and constructed the wiki ourselves. We utilized Bootstrap and JQuery libraries to ease the mission a bit but the layout and the code is our work. | |
</p> | </p> | ||
Revision as of 23:38, 4 October 2014
Outreach
We wanted to make synthetic biology known in Finland. Many activities. Fun.
Starting Up
We took part in Summer of Startups, a startup incubator by Aalto University. We met a lot of other small startups and people interested in them. We found out how to pitch synthetic biology to people that know nothing about it. It just needed a sympathetic mascot and explaining how a bioreactor is a work place for him.
The program included two different occasions where we pitched our startup idea. There was pitching night, where we competed in pitching with all the other teams. Then there was Demo Day, a massive event with hundreds of people where we presented ourselves and run a booth for the whole evening, getting people excited about us and synthetic biology. We presented ourselves to an audience of hundreds and many of them came by our booth later.
Our booth at Demo Day.
[More stuff, maybe explanation of all the difficulties as a SynBio startup]
Media
A Website for the General Public
At the very beginning of the project we wanted to create a website that we could link to our friends, new acquaintances and potential sponsors. It included basic info about us and a general overview of the project. We started developing it rapidly and it actually got into a presentable shape fairly fast.
We expected to attract sponsors with the page, but the most important function turned about to be for media to use as a basis for a story and for our Facebook fans to get a more in-depth introduction to us. It was also really good practice for making the wiki. Using GitHub together with several people was a new experience and sometimes it was difficult to find out why things weren't working how we thought they should work.
This is how the first plan of the "sponsor website" looked like. We developed it further during the project. It might be still available at http://www.aaltohelsinki.com/.
Creating the Wiki
Making a good wiki was an important thing for us. It had to be simple, well formatted but also nice to look at and informative. We wanted it to represent our team well. We wanted to take our time with it and develop it with care. So, we started early and proceeded to create our wiki steadily, step by step. It turned out amazingly well. It's completely responsive so it looks good on any platform: phones, pads, desktops. We also hope that you can effortlessly find everything you'd want to, and that scrolling through the content is a pleasent experience for every visitor.
Figuring out the best way to present ourselves in the wiki was a tough problem to solve. We thought about many options but ended up having a little similar layout that we had used in the practice website. Having a sidebar seemed like a fun idea at first but we gave it up to keep things aesthetically pleasing and to make it possible to browse the wiki on all platforms. Scrolling through the content felt like a great choice, so instead of countless different subcategories, we only have eight categories and you can just scroll through them. Also sorting out the categories felt very difficult but in the end it feels like everything found their own place.
The first thing we did for making the wiki was an upload tool: iGEM Wiki Quickifier. With it we could upload content to a our team wiki without using the cumbersome wiki interface. We could write our pages as html files and the script would add the needed template tags as it uploaded the pages to the wiki. Uploading content to other wikis than ours is not implemented (yet), but if you know python, modifying the script should be an easy task.
We used GitHub to keep our texts syncronized so you can also browse the work process from our commit history. Here's the GitHub page of our wiki. You can, of course, also browse the code that's here on the final version of the wiki.
We made the wiki from scratch: we didn't use any templates but we designed and constructed the wiki ourselves. We utilized Bootstrap and JQuery libraries to ease the mission a bit but the layout and the code is our work.
Social Media
Our own website, blog, Facebook, Twitter, Youtube, Flickr. Links.
Events and Meetings
SoS Meetings, Lab Tours.
Finding Partners
Finding the right people and teaching them what iGEM means.
The Extras
Flappy Coli
We also made a silly game called Flappy Coli, where you are guiding a genetically modified pink bacteria through an iGEM-maze. It grows it's flagellum when you get farther and if you are good enough, it might grow more flagella!
All of the code is available at the project's GitHub page.
Here you can see a screenshot from the game.
