Saturday, 28 April 2012

New Assignment Brief - Portfolio Website

The Brief 
In this assignment, you will design and build a website containing your FdA work to date, plus any existing work you feel you should include in your portfolio and biography information such as an ‘about’ section and/or a CV.  This will form the starting point to your portfolio website which you will keep up to date with new projects throughout the course. 

Making web pages
To make successful websites with working links you will need to thoroughly understand the folder system that structures your files. You will create a web project folder with your name and make folders within this that offer a sensible navigation structure.  These may be, css, images, scripts, working files.  Please note the index.html page MUST be loose at the top of the hierarchy not inside a folder.

You will use TextWrangler to create all HTML and CSS. The goal of this project is to further your understanding and abilities in hand coding HTML & CSS, therefore you will not be allowed to make any of this assignment in Adobe Dreamweaver or any other visual WYSIWYG editor.

Your site will be constructed as a single page with the different sections made visible using css positioning or by a hide/show or similar jQuery method. CSS3 animation or jQuery will give the smoothest and best results.

You will not use images of text in this assignment. All text elements must be live selectable text and styled using css. You will use either Google Fonts or @fontface for your text elements.

Images are restricted for content, header (masthead) decoration or sprites for use as background to navigation elements but all links must be text based.
Important: You will not use html tables for the purpose of creating layouts at all in this assignment.

Working with CSS
You will use Cascading Style Sheets (CSS) to format and style the elements of your page so that you can:

·  style and distinguish between navigational and content areas of your page,
·  format and control your text and any links,
·  you can create print- friendly versions of your page which restyle the content for print outcomes.

Working with real outcomes
You will also prepare and format your page with CSS for different browsers on different platforms. This will involve testing your pages on both Mac and PC computers.
In order to make sure that your pages work seamlessly in different browsers and on both Macs and PCs, you can use conditional HTML comments to direct Mac and PC browsers (including Internet Explorer and Safari to sets of CSS files).

Working with text and images
Text material in Word .doc format or created in any other word processing package must be converted to 'vanilla' plain text (txt) files before inserting into the web page.

You will use Photoshop or Illustrator to process images that will be optimised for web delivery using Save for Web and Devices as a gif, jpg or png, with care taken over pixel dimensions, file sizes and image qualities. Video content should be displayed using the ‘Video for Everybody’ system.

All the images you make in Photoshop and Illustrator should be placed in the ‘images’ folder in your project folder and will be addressed with the correct routing through HTML. You will make these images accessible through the use of  <alt> and <title> tags.

For the typographic elements of your design you will use webfonts using either @fontface or Google Web Fonts.

Your design work
You should ensure that you take note of screen sizes and that your pages work effectively with current popular screen resolutions.

You should consider creating visually pleasing and legible designs where the design acts to make the content more appealing and readily readable with a standard web browser, rather than dominate or overpower the content.

Your designs must achieve consistency over the sections of your site: you must use common type styling, layout and structural elements between sections.

You need to consider usability and accessibility in the design of your interface and page layout.

You will need to demonstrate your approach to the creative process using methods that are standard to the digital media industries.  As well as your visual research, your sketchbook and blog should show sketches, ideas and experiments for the designs in development so the processes you used to reach decisions on such issues as wireframe layout, colour, typography and navigation are transparent.  Navigation must be planned using flow diagrams. 

 
Pitching your designs
You will pitch your designs to the group and tutors in a presentation.  You have to include your proposed content, layout, interface designs and look and feel in your pitch.  This can include:-

-   Wireframes
-   Flow diagrams
-   Graphics
-   Proposed content
-   Logo and heading designs
-   Interface designs
-   Page mock-ups

This pitch needs to be prepared as if you were selling your idea to a client.  Include technical research, particularly screen resolutions, browsers and platforms.  Show colours and fonts in mock ups rather than on their own – make visualisations rather than lists.

Friday, 27 April 2012

Evaluation

Things that i would do differently next time:

- First of all this was my first attempt at making a website, i was completely new to the HTML code and CSS. I would take more tutorials in how to code both HTML, CSS and javascript.

- I think that the time given between the start of the assignment and he deadline was long enough considering i had to earn the code from scratch. However the time i spent was mostly trying to work out how the site worked and how exactly was put together. I was forever looking online at trouble shooting blogs because it was difficult.

- I would organise my time better for my sketchbook, there wasn't enough drawing or sketches done in order to really solidify my ideas and visual styles.

- Clients missed meeting deadlines

Things that went well:

- I think that towards the end as i became more familiar with the code i was able to understand it better thus being able to work faster at coding HTML and CSS.

- The initial research went well, and the communication between the client went well, despite them not being able to turn up, twice.

What i have learnt overal:

- i have learnt to code HTML and CSS to a satisfactory level, more work needs to be done in this area of design, more experience required in order to fully reach my potential in web design.

Final Critique

Here is the feedback i got from my peers and my teacher:

- Needs more styled CSS, both on the layout and on the typography
- Logos needed to be better positioned, maybe either side of the main header and slogan
- The unbalanced content boxes, maybe try setting a height to one of them if not both of them
- Bottom navigation bar needs tweaking 
- Either put more information in the gallery feed or take it off completely 
- Change the blog placement or get rid of the blog 
- Roll overs on the images/ light box could be added to give the site more of a media flavour

- Colours were good, however another colour needs to be added to give it a bit more depth 
- The content is very good and used appropriately 
- No broken links, or loading issues with images 

Overall there are many improvements to be made and i will make the improvements in time for final submission. 

Final Website



                            








Thursday, 26 April 2012

Trouble Shooting

Here is a list of some of the errors i had trouble with:

First off all writing out the main index page. This was vital because once i had one page done i could then just copy and paste the HTML code and save them as their own HTML sheets in the website folder located on my decktop.

Next was sourcing images from the images folder in my website folder. I then had to figure out how to style the images, in a way on the browser window, for example positioning, padding, margin.

I tried using light box how ever it took me far to long to code the light box because even after looking at tutorials i didnt know how to code and link it all together. So in the end i dropped the light box idea, this was the same with the roll over images.

Inserting line breaks into paragraph divs with in the HTML and CSS

After floating images, i then had to figure out how to use the class known as 'clearfix'.

The Code

Starting off as you see in the image below this was the HTML code, doctype is stating what type of code sheet it is. You then have header, title, link to the stylesheet (CSS), end of header, start of the body tag, then the two <divs> containing two id's, wrapper and header. 



The code above is essential when making any website in HTML and CSS. You must put the tags in the right way or it won't work properly.

Below you see i added my first logo image. I had to source it from the website folder, in which i constructed before i started coding. You must have all of your files organised otherwise nothing will work.


 I had to get into the habit of closing every tag that i opened, if i didnt close the tag, again it wouldnt work.


In the image above, you can see i started to construct my navigation bar in my HTML code. The image below is the navigation bar for the footer, relatively speaking its the same code as i copied and pasted it because they are going to do the same job.



Below you see is th end of the HTML code. As i said earlier, always remember to close your tags. 

-           -        -          -         -          -           -          -          -         -         -         -          -        -         -          - 

The image below is of the web font code i got off of google web fonts.


below is the CSS coding i use in order to style my paragraph of text i order to get it sitting naturally .
 The screen shot below is that of the CSS that goes hand in hand with the beginning of the HTML code i mentioned earlier.

My Website - Explained

First off, this is my header. It contains both the logos provided by the client, and the said text both main header and slogan header.

The colours are very simple and subtle, white space is a visual design element that i was trying to incorporate into this website. The typography is a web font in which i used from Google Web Fonts. It had a handwritten effect which i liked and thought it was in theme with the companies style. 

Next is the navigation bar. Again like the header the colours are very simple, gentle and subtle. nothing to in your face, i was going for a mature theme to this website. each button has an underline roll over. With no visited state.


The next image is of the main content. I used two contents boxes in order to hold my content. This content included Images, text and videos. The grey border is a nice gentle touch of styling. I line broke the text up in order for it to flow nicely, instead of being text heavy in one chunk of text, its a lot easier on the eyes if its formatted like that. 


The footer. The footer as seen below is keeping in theme with the rest of the webpage/ website. mature, subtle and easy on the eyes. it doesnt jump out at you with vibrant colours. The contact details are formatted away from the walls of the website, by using padding.

Below is the gallery page in full view (as close as i could because of the scroll bars). It is a bit bland with no real flavour, it has potential to be so much more then it already is.