A different wiki

Our way of showing the world what we accomplished - intuitively and thoroughly

Team members working hard to polish the wiki before the European Jamboree wiki-freeze. Most of our team members have never tried creating a wiki, so when Heidi’s boyfriend Kenneth offered to help us out a bit, we were quick to accept. As a professional software developer, Kenneth had a unique perspective, which shone throughout our preliminary meetings. We set out to present the best, most intuitive wiki possible; to improve the standard wiki experience. This very wiki is the result, and below are the keys to the wiki.

Better overview: A metro-map of all pages
A general issue observed on many wikis is that the user struggles to navigate. We designed a metro-style navigation bar at the top of each page, giving the user knowledge of his exact location. While allowing a custom experience and viewing order, the navigation bar ensures that the user is never lost.

Smarter tour: Usable by both casual and thorough readers
A lot of wiki-tours do a great job at introducing the reader to the project. However, users who want details are left to fend for themselves in a jungle of pages. Our fix: Allowing our readers the freedom to choose between a quick and a detailed tour by including all pages in our tour.
The result is an interactive wiki tour, which sets up a choice between digging deeper to detailed pages or fast-forward to the next major chapter. The two buttons (on the bottom of the screen) even have a small text explaining what you can expect to read on the coming pages. Also, take the time to click on our photos; this brings forward a detailed figure description.

Quicker navigation: Tour buttons and menu always visible
Additional ease of navigation was created by ensuring that tour-buttons and menu are always available - even when scrolling through the text! While searching for a topic of interest, a traditional menu as a means of a shortcut may be desirable. Such a menu allows users to access a specific page that they might wish to revisit. Perhaps a certain page sprung to mind after completing the tour, perhaps a user accesses our wiki looking for a particular subject. The menu makes such personalized experiences easier and more user-friendly.

Tooltips: Simplifying the text
To reach broader audiences, we wanted our wiki articles to be easily understandable without compromising the scientific aspect. To solve this, we added tooltips TooltipsAll tooltips are marked with bold, blue text to draw attention. to many of our pages. The tooltips enable us to maintain short and precise texts with great scientific value, while explaining some of the more exotic words and abbreviations.
We also use tooltips when quoting a source without cluttering the text. Source: A reference to our source will be placed here

Stay on track: Many external sites are shown as in-page dialogs
Sometimes we link to external content, such as our submitted parts. These links will open inside the page using a dialog box, which can be easily closed by clicking the escape button in the top right corner. This helps users stay on track when browsing our wiki.

The best part
As with everything else in iGEM regi, the entire structure and underlying HTML code for this website is open source and easy to access for everyone. Just press 'View source' in the top of the page or hit F12 to access the source codes. This is a great way for future iGEM teams to get inspiration and the tools to build great wikis, and was one of our main goals with this wiki, to give the community some tools to make good looking, easy to navigate wikis. Access our Style Sheet, Tour Menu, Header and Footer to get a glimpse of the source codes behind our wikis standard elements.

Compliance with the iGEM 2013 wiki requirements

The wiki requirements’ primary purpose is to ensure that the wiki will continue to function, even several years from now. Also, it is important that future teams can look to previous wikis and learn from them; hopefully resulting in even better wikis in the future in the spirit of iGEM’s community sharing.

All wiki requirements are met. Below is an outline of focal points:

All pages, images, and files are hosted on the server
This also includes all necessary javascript and JQuery code needed for the wiki to function properly.

No flash was used in the making of this wiki
Since flash is not open-source, it would be impossible for other teams to see how it is made. Besides, flash is not visible from many modern mobile devicesModern mobile devicesiPhones, iPads, Windows Phone 8 and Windows tablets. , which would make the wiki less accessible. Consequently, all animations were done using javascript.

Project description on front page
To welcome new readers, the front page focuses on our project description.

All pages are in the team namespace
We made sure that all our pages are created in the correct namespace, in our case under the Team:SDU-Denmark.

There is a link to the completed safety form and an attributions section as part of the wiki
The completed safety form can be viewed on our safety page.
The attributions page can be found here.

iGEM logo and user editing menu is found on the top of every page
We kept the original iGEM logo in the header as a link to The user editing menu is also visible on every page, just above our header. Note that the header collapses to save space, and you may have to scroll to the top of the page to view it, exactly as it does on the site. This way, menus are in their expected positions and easily accessible to future teams.