Name your images according to the project and keep them all in a folder on your computer.
#Wikipedia screenshot editor pdf
In the end you will have a printable version of your project that you can share as a pdf file with other people! 4. Divide the documentation into smaller files and assign a team member to fully document that topic. This was a good thing that we did we created a common file that more than one person can edit at a time. Start working on your documentation early on. See what you liked that they did and strive to improve! 3. It is always good to get inspiration from other iGEM teams. Look at other teams’ code, see how they documented and what resources they used. If someone wants to read your abstract, their path should be something like this (Menu –> Project –> Project Description -> Abstract) 2. It wasn’t for the people evaluating us.Īlso, stick to the 3 click rule: content must reachable within 3 clicks so the user does not feel lost or confused.
It was obvious for me how things were laid out and organized. I made the terrible mistake of not asking for a third party’s opinion about the layout of information on our site. Test your webpage layout: is information easy to find? I am by no means an expert but let me share with you some of the things I learned with two wiki freezes under my belt. In 20 my role was to design and create our team’s wiki. You are required to host all content on the iGEM servers (see above) Load your CSS and Javascript into the wiki, either directly into your page or using templates.ĭon't try to host your CSS and Javascript on a third party server Using unique names makes searching/identification of uploaded files easier. Name uploaded files clearly and uniquely (T-TeamName-Filename.png)ĭon't use generic names for you files (Header.png) This can be a difficult time to make larger changes or additions to your wiki. Just before the Wiki Freeze, iGEM websites experience increased traffic and server loads. Work on your wiki throughout the year and save small edits for lastĭon't wait to add/edit large portions of wiki content the day of the Wiki Freeze When content is stored on other sites/servers, links may become broken, sites may go down, and information will be lost. IGEM content is preserved on our servers so future teams can learn from what you've done. Don't include scripts or stylesheets from other servers. (This includes text, files, HTML, CSS, Javascript, and other scripts.)ĭon't host your wiki or parts of your wiki elsewhere. Make sure all wiki content is hosted on. This includes uploaded files, templates, CSS and Javascript pages, not just your main wiki pages. You should keep ALL your content within your team's namespace. Try things out and see what results they yield. It doesn't have to be perfect before you can take a look at what it looks like. Then all you have to do is go to the source (either view source if you're not logged in, or edit if you are logged in), copy it, and modify it to fit your needs. The key is to take a look at other wiki pages and see what you like. Editing the wiki is a simple, fun thing to do and you definitely get better the more you play around with it. Using/editing the wiki is a trial-and-error process.
#Wikipedia screenshot editor how to
See the Mediawiki Help page ⇗ for details on how to edit wiki pages and more. And finally tips on wikis dos and dont's and tips for working on your wiki.Īll iGEM wiki sites are powered by Mediawiki.
On this page you will find general information on how to: upload a file, create a page, upload videos, and use wiki templates.Īs well as a quick introduction to HTML, CSS, Javascript, MathJax.