Monday, 3 June 2013

Validation of html + css

To validate my html I used the website ' http://validator.w3.org/check ' and uploaded my file. At first I got some errors which meant re-adjusting the html text but I modified some of the code so it would be valid. Here is the results of my valid html.











As shown in the screen captures the hmtl file passes.

Here is the modified html text used to pass:



<!DOCTYPE html>
<html>
<head> <meta charset="UTF-8">

<title>Wonders of Nature | Earthquakes </title>
<link href="css/main2.css" rel="stylesheet">
<link href="css/flexslider.css" rel="stylesheet">
<meta name="viewport" content="width=device-width">
  <!-- End SlidesJS Required -->


  <!-- SlidesJS Required: -->
   <!-- SlidesJS Required: Link to jQuery -->
  <script src="http://code.jquery.com/jquery-1.9.1.min.js"></script>
  <!-- End SlidesJS Required -->

<script>
$(function() {
var pull = $('#pull');
menu = $('nav ul');
menuHeight = menu.height();

$(pull).on('click', function(e) {
e.preventDefault();
menu.slideToggle();
});

$(window).resize(function(){
        var w = $(window).width();
        if(w > 721 && menu.is(':hidden')) {
        menu.removeAttr('style');
        }
    });

});


</script>

<script>
$(window).load(function() {
  $('.flexslider').flexslider({
    animation: "slide"
  });
});
</script>
</head>
<body>
  <div id="wrapper">

<header>
<div id="header_inner" class="group">
<div id="logo">
<h1>Wonders of Nature</h1>
</div><!--END logo-->
<nav class="group">
<a href="#" id="pull"><img src="images/pulldownsymbol.png" alt="pulldownsymbol"></a>
<ul class="group">
<li><a href="index.html">Home</a></li>
<li><a href="thecause.html">The Cause</a></li>
<li><a href="richterscale.html">Richter Scale</a></li>
<li><a href="outcome.html">The Outcome</a></li>
</ul>
        </nav>
</div><!--END header_inner-->
</header>

<section id="main_content">

<!-- SlidesJS Required: Start Slides -->
  <div class="flexslider">
  <ul class="slides">
    <li>
      <a href="thecause.html"><img src="images/home_pg_img1.png" alt="cause"></a>
    </li>
    <li>
    <a href="richterscale.html"><img src="images/seismograph.png" alt="seismograph"></a>
    </li>
    <li>
      <a href="outcome.html"><img src="images/theoutcome.png" alt="outcome"></a>
    </li>
       </ul>
</div>
</section> <!--end main_content-->
</div>
<!-- SlidesJS Required: Link to jquery.slides.js -->
  <script src="js/jquery.slides.min.js"></script>
  <script src="js/jquery.flexslider-min.js"></script>

  <footer> Glen Myers Wonders of Nature Earthquakes 2013 </footer>


</html>


Validating my css now:

At first there was 3 errors

242navValue Error : background attempt to find a semi-colon before the property name. add it
406div.infoLLLValue Error : margin-left Parse Error
434.image_containerValue Error : margin-right Parse Error


So I modified the css on these lines so the css would pass...

All it was was one semi colon missing on one line and two lines with 'Margin-left: ;' where I had forgot to delete it as I didnt need any value in there.

After these very small modifications the css passed.



User testing for iBook - Results


I tested my iBook with some of my peers in my class and here are the results I got


How easy was it to read the information

Very hard        Hard     Average      Easy       Very Easy

How easy was it to understand the information

Very hard        Hard     Average      Easy       Very Easy

How easy was to to navigate the interface

Very hard        Hard     Average      Easy       Very Easy

How easy was it to use the interactive elements

Very hard        Hard     Average      Easy       Very Easy

What target audience would you think this would be aimed at

0-5         6-10     11-15     16-18     19+

How enjoyable was the ibook to use

Very boring       Boring        Average        Fun         Very Fun

Overall what would you rate the ibook in terms of being a fun educational resource

Very poor         Poor           Average         Good       Very good

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


How easy was it to read the information

Very hard        Hard     Average      Easy       Very Easy

How easy was it to understand the information

Very hard        Hard     Average      Easy       Very Easy

How easy was to to navigate the interface

Very hard        Hard     Average      Easy       Very Easy

How easy was it to use the interactive elements

Very hard        Hard     Average      Easy       Very Easy

What target audience would you think this would be aimed at

0-5         6-10     11-15     16-18     19+

How enjoyable was the ibook to use

Very boring       Boring        Average        Fun         Very Fun

Overall what would you rate the ibook in terms of being a fun educational resource

Very poor         Poor           Average         Good       Very good

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


How easy was it to read the information

Very hard        Hard     Average      Easy       Very Easy

How easy was it to understand the information

Very hard        Hard     Average      Easy       Very Easy

How easy was to to navigate the interface

Very hard        Hard     Average      Easy       Very Easy

How easy was it to use the interactive elements

Very hard        Hard     Average      Easy       Very Easy

What target audience would you think this would be aimed at

0-5         6-10     11-15     16-18     19+

How enjoyable was the ibook to use

Very boring       Boring        Average        Fun         Very Fun

Overall what would you rate the ibook in terms of being a fun educational resource

Very poor         Poor           Average         Good       Very good


Sunday, 2 June 2013

User testing for the iBook

I created a survey and asked some peers to give me some feedback following the questions asked in the survey:

How easy was it to read the information

Very hard        Hard     Average      Easy       Very Easy

How easy was it to understand the information

Very hard        Hard     Average      Easy       Very Easy

How easy was to to navigate the interface

Very hard        Hard     Average      Easy       Very Easy

How easy was it to use the interactive elements

Very hard        Hard     Average      Easy       Very Easy

What target audience would you think this would be aimed at

0-5         6-10     11-15     16-18     19+

How enjoyable was the ibook to use

Very boring       Boring        Average        Fun         Very Fun

Overall what would you rate the ibook in terms of being a fun educational resource

Very poor         Poor           Average         Good       Very good

Saturday, 1 June 2013

Continuing my website, the work in progress:

From crit my website was probably 40% finished. I had 2 blank pages, and a lot of css to do to style the cause page properly.

I begun trying to style my cause page for each media query. I have managed to complete each media query and this is how it looks like:













At desktop I have the two column layout, I added a nice little bottom border line in a brown colour underneath the title to keep a nice clean divider form the header to the body text.
















At tablet I have the same layout, the only change is that I had to change the percentage width of the header so the line has a similar gap on the right to what it has on the left. I used a 94% width to do this.


For mobile my layout changes to a one column layout, I had to re-adjust values quit a lot, such as: the margin of the header so it wasnt sat behind the nav. The width so the line had a gap on the end like on the left. I had to put padding on the p tag so the text wasnt so close to the line underneath the heading.

I had to put a percentage margin on the images so there was a gap on each side of it so the image wasnt touching the sides. A margin in the bottom of the images so the text wasnt so close to the bottom of the image.

This is pretty much my first content page done apart from my homepage. Just two more pages to do now.














I have finished my Richter scale page, I have kept to the layouts I proposed to begin with, A two column layout, text on the left and media on the right.




On the tablet page I kept the same layout because it still looked clean and not clustered. I styled the css so everything was in line and even spacing around to look as clean as possible.






















The mobile layout is a one column layout, everything styled central with nice gaps each side.

My outcome page was the hardest page to make, I had so many problems making it. I wanted the layout as seen as above consistently down the page with the other content but I kept getting positioning problems with the text and photos, they would go in line with the content above, the text kept making its way in the middle of the page. To overcome it I had to make separate divs for each column and picture and apply specific css so they would both sit next to each other on the same level. I had to trial and error with margin and width sizes. But got there in the end.



















For the tablet layout, again I had to do exactly what I did in desktop by trial and error lots of values till everything was put in the right position it took ages but after a frustrating long time getting it in place it all got there in the end.


















At mobile platform, this was relatively simple, putting everything in a one column layout and in a central clean looking layout.























My website is now finished, I really struggled to make it. I found it so diffcult to understand code and understand why errors were occuring, I was pretty much just guessing by changing random things I think could affect it. I had to open 'inspect element' so many times to find out which element was not working properly then going in to the css and changing loads of things. Overall, I found webcode not as great as the other projects, It was a more a major relief when i got what it want to do. I didn't really enjoy doing webcode due to how hard I found it. But next time, if we got this project again I think I would be 10 times more confident to make it then at the start. I understand some parts of code now, but still a bit edgey on it.