Difference between revisions of "Team:NEFU China/Software"
m |
m |
||
| Line 48: | Line 48: | ||
width: 100%; | width: 100%; | ||
} | } | ||
| − | + | .section .navbar h2{ | |
| − | + | margin-top:0; | |
| − | + | } | |
.logo-container{ | .logo-container{ | ||
height: 160px; | height: 160px; | ||
| Line 276: | Line 276: | ||
<div class="row"> | <div class="row"> | ||
<div class="sub-container"> | <div class="sub-container"> | ||
| − | <div class="col-xs-6 col-md-6" style="text-align:center;"> | + | <div class="col-xs-6 col-md-6" style="text-align:center;"><img src="imgs/igemwiki.png" /></div> |
| − | + | ||
| − | + | <div class="col-xs-6 col-md-6 msg"> | |
| − | + | <p>A typical iGEM wiki can be divided into no less than 8 sections (like the home page, project, safety, team, and so on). Under each section, there are a lot of issues which you want to present. Just like the ‘Project’ section, you may need to tell others about your background information, design, etc. Tedious as it is, we, the same as other 52 teams (52/56), believe that online collaboration can improve the efficiency of creating a wiki.</p> | |
| − | + | </div> | |
| − | + | ||
| − | + | ||
</div> | </div> | ||
</div> | </div> | ||
| Line 295: | Line 293: | ||
<div class="row"> | <div class="row"> | ||
<div class="sub-container"> | <div class="sub-container"> | ||
| − | <div class="col-xs-12 col-md-12" style="text-align:center;"> | + | <div class="col-xs-12 col-md-12" style="text-align:center;"><img src="imgs/deadline.png" /></div> |
| − | + | ||
| − | + | <div class="col-xs-12 col-md-12 msg"> | |
| − | + | <p> </p> | |
| − | + | </div> | |
| − | + | ||
</div> | </div> | ||
</div> | </div> | ||
Revision as of 03:15, 13 September 2015
Attitudes towards creating a wiki
According to a survey conducted by us, we found that most teams agrees the thesis that creating wiki is a difficult or tedious work to finish with high quality, especially when time is very limited. So, we’d like to make some changes.
*You can see all raw data by click this.
About half of teams we surveyed hold the opinion that creating a wiki requires superior skills in programming (29/56), which lead them feel hard about it. We sincerely invite you to click the right arrow and discover what giant changes Flight iGEM can make.
Step 1
To create a wiki, a HTML template is necessary neither with Flight iGEM nor without Flight iGEM.
Step 2
Without Flight iGEM
Once the template is done, other teammates can start to summarize the project, record experiments’ data by using their Word or iWork.
With Flight iGEM
Flight iGEM requires you and your teammates to work online. We use CKEditor(a free, Open Source HTML text editor) to set up edit environment like Word or iWork.Step 3
Without Flight iGEM
Without Flight iGEM, you need to upload all images and other media files which involved in your articles to the iGEM server manually.
With Flight iGEM
If you use Flight iGEM, all media files(especially the images) which you insert into the article will be automatically upload to iGEM server.
Step 4
Without Flight iGEM
You need to assign the content which converted from Word or iWork documents to the template. In this step, there will be numerous words and sentences that will be copied and pasted, which cost a lot of time and memory.
With Flight iGEM
Flight iGEM can assign contents with template automatically, all you need to do is to select what you want to display, and then click 'Magic'.
Step 5
Without Flight iGEM
After you merged this two page, there are you should upload the "code soup" to the iGEM server, and this is the final step of the whole procedure.
With Flight iGEM
Flight iGEM will upload your pages to the iGEM server after step 4, and the only thing you need to do is to visit your target page and check if the page is exactly what you want.
A typical iGEM wiki can be divided into no less than 8 sections (like the home page, project, safety, team, and so on). Under each section, there are a lot of issues which you want to present. Just like the ‘Project’ section, you may need to tell others about your background information, design, etc. Tedious as it is, we, the same as other 52 teams (52/56), believe that online collaboration can improve the efficiency of creating a wiki.
