Team:UCL/FAQ/WikiDesign

Firstly, the bread and butter: HTML and CSS. HTML is the backbone of your website, and CSS is the design and styling.

Now, if you're familiar with HTML and CSS; let's delve a bit deeper into web design concepts. Javascript was something I stayed away from for a long time (until it came to editing this wiki), simply because it wasn't HTML or CSS, and I believed that since I couldn't understand it, I couldn't possibly use it. Well, I was wrong! Being able to simple incorporate javascript into your website makes it so much better. Over the course of the summer, I have learned to use and manipulate (to a very small degree) jQuery plugins. jQuery plugins offer a huge bunch of formatting and styling opportunities - from dropdown menus, to tabs, to image galleries etc. Below is a list of jQuery repositories I find very useful and interesting when browsing for different plugins to incorporate into your website INSERT LIST HERE WITH LINKS There are other web design languages and other aspects to Javascript as well, but my lack of experience with those means I won't be able to explain any further. When it comes to the basics of web design, the best thing to do is experiment. Download a text editor for coding, and experiment different things you come across. There are many different (and free!) styles, plugins etc. out there; and whilst some may be a little difficult to work with, many are simple and elegant on a variety of web pages.

Firstly, lets talk content. You may be thinking that this is the easy part, but it really isn't. Getting all your content up before the wiki freeze is quite the unexpected challenge. You want to be able to, in detail, explain your entire project on your wiki; and if you don't get your content together before the last few weeks, you'll probably find yourself scrambling to get something onto your wiki as the deadline approaches - not a position you want to be in! Now, lets talk design. It's the most creative and fun part, but you'll have to work as a team to decide what sort of design you want. I suggest researching on good layouts and designs to base your wiki on; and remember, simple and functional beats problematic and complex. If you want to find out more about web design concepts, try googling or have a look at your favourite websites and the approaches they have taken. In terms of getting your wiki together, it's best to start early. Below I have outlined a quick process you should follow to ensure your wiki is ready in time: 1. Build a site map, note down which pages you'll need. -Look at the requirements -Look at what you're doing -Look at what past teams have done -Do you want to do anything new? 2. Get a graphics team together and start brainstorming -A good set of matching graphics can help set a theme to your wiki -Swag 3. Make a team portal page, link it to all the pages on the site map, this can work as a draft page for members to start uploading content. 4. Get your content together, keep revising it until you're 100% happy 5. Once you've got the basics together, start working on the design as a team, once your happy, freeze it and carry on with content. 6. Get it all done by the wiki deadline, and pray that your computer doesn't crash.

First, the header. Lewis Iain was the source of inspiration for this, I think it caught his eye whilst he was browsing for different website design templates. He looked through a bunch of code and managed to pull it out of the bag, and even spice it up a little (if you view our site on a mobile device, or simple make your window smaller; there's a keen feature he managed to fix up). Our team then decided on our colour scheme and it was all set. We decided to go with a simplistic approach, breaking our content into 3 main categories: Project, Science and Humans. It works well because it ensures we avoid having a menu full of clutter, and allows users to go through each aspect of our project step by step. Next, the header images. Oran Maguire, who contributed in UCL iGEM 2013 was happy to lend a hand in the graphics team this year as well. Initially, we used a bunch of photos that were all different sizes; but with a more consistent set of images, everything looks a little neater now. Now, there are a few keen features you may have noticed on our pages. The tabs feature, the expanding box, the hover tooltip, the carousel gallery, and the sticky note! That's all jQuery plugins, something I had a real good bit of fun experimenting with. On some of our pages, you may have come across the mini tutorial feature; that's yet another jQuery plugin. Our wiki does well with a good number of images, as do all wikis. I strongly suggest you keep a camera with you at all times, because those images will go a long way; plus it makes for a great bit of eye candy to go with a bunch of text! Lastly, we have our footer, it's simple yet elegant. All the necessary info, and of course our Twitter feed! Be sure to follow UCL iGEM on Twitter, and keep up with our progress and of course keep up with the 2015 UCL iGEM team!

Firstly, lets talk about loading your js and css files onto your page. Firstly, you'll want to create a template (Team:Name/Template:TemplateName.###(where ### could be js or css depending on your file)). Create the template page and load your css and js files onto them. The next step is to create another template, to hold the links to all your js and css files, for example this page (Team:UCL/Template:BioprocessStyles and Team:UCL/Template:WikiDesignStyles). It simply loads all the js and css templates, and it makes it a lot easier to insert onto your page (it also makes all the clutter disappear!) Once you've done that, load it onto your page, and voilà, it's all working! What we've done to ensure all our members can easily edit the pages, it using comments in the source code (it also makes it easy for you to go through and copy out bits of our code). This allows our members to know exactly where to start typing and what they can touch; it really helps avoid someone coming along and breaking an entire page! Now, you might be wondering if I'm going to explain about the nitty gritty coding that we've got going on. The good thing is, I don't have to! In the process of making all those comments for our own team members to understand the code, you can just as easily look at the source code and understand it yourself! Two birds with one stone!