Showing posts with label Adjustments. Show all posts
Showing posts with label Adjustments. Show all posts

Sunday, 25 May 2014

A Small Adjustment

A quick update on a small change I've made.

I've added in the 'titles' for each colour section on each of the pages. These were initially designed to look like this.
And that's fine, I've stuck with that design and I like it. When I added the graphics to the HTML and had a look at the end result, though, I noticed an issue. There was a bit of a clash with the layout.

Considering the pages on my website are going to be reasonably long, it's important for the user to be able to easily find out where they are on it. Hence the titles for each chapter that split it up and make each chapter further distinguishable (despite the obvious changes in colour...). To add to the ease of getting to places on the site I've also added a fixed home button, which displays in the top left hand corner no matter how far you are down the page. These are both good additions to the navigation of the page but they display on the page together like this...
They clash. It's okay that the home button sits above it - that's what I want it to do - but them being one on top of the other makes one less readable, doing nothing for my goal of creating a good and easy experience for the user. So, I've switched the subtitles to the other side.
Much better.

How is this aspect responsive? 
When the width of the site goes beneath 769px, this style of subtitle will disappear and text subtitles will replace it.

Above 960px
769px to 960px
470px to 769px
470px and below

Wednesday, 21 May 2014

Media Queries and Design Adjustments

Tonight I started working on Media Queries.

Even though we are required to use the Skeleton Framework for our website, a large proportion on whether or not our site is responsive is dependant on 'media queries'. I've never, ever worked with them before, but I got a general gist of the idea of them in class through listening to other people.

I understood that in a way it is applying CSS to certain elements at certain points depending on the size of the page. In the basic index.html we were given to work off of a layout.css file was attached, with the following in:

/* Smaller than standard 960 (devices and browsers) */
@media only screen and (max-width: 959px) {}

/* Tablet Portrait size to standard 960 (devices and browsers) */
@media only screen and (min-width: 768px) and (max-width: 959px) {}

/* All Mobile Sizes (devices and browser) */
@media only screen and (max-width: 767px) {}

/* Mobile Landscape Size to Tablet Portrait (devices and browsers) */
@media only screen and (min-width: 480px) and (max-width: 767px) {}

/* Mobile Portrait Size to Mobile Landscape Size (devices and browsers) */
@media only screen and (max-width: 479px) {}

From what I understood from here I gathered that within each { } I would put the information for how I'd like an element to display at each point. To gain a further understanding I watched this video:

To explain my new-found understanding!

@media only screen and (min-width: 480px) and (max-width: 767px) {}

'only screen': 'screen' is a media type. Other media types include: print, handheld devices, TV's and projectors. My code defines that this media query is only for screens.

min-width/max-width: This is a media-feature. It does not have to be a 'max' height or width, it can simply be width or height, as well as elements such as colour. 

max - upperbound
min - lower bound

{} : This is where you write your CSS that defines what each element should display like (or if they display at all) at each breakpoint.

Breakpoint: Where a new style kicks in. 

Getting to grips with this inspired me to do something a bit more complex for my site. I started to consider how I could simply my design for when it hit the mobile version - the smallest width. Looking at my existing design, I noticed how cluttered it was. Quite a prominent aspect of the desktop version is the slideshow just under the navigation bar. It is not an element of my site that is 100% necessary - it's there partly for aesthetic benefits. Because of this I came to the conclusion that for the mobile version of the site it was disposable. Removing this slideshow allowed me to trim the length of the (already rather long) central banner. 
Left: Original Banner
Right: New Banner

Implementing this has made me make use of what's now a very useful selection of code:

display: none;
Tells the browser not to display an element (if the page is at a certain size)

display: inherit !important;
Tells the browser to 'inherit' this element and display it. I used this to essentially exchange out the original banner with the new banner.

Combining this with my navigation for the mobile device, my site now displays like this (on mobile). 

You can also see above that I've made the decision to change the colour of my home button to a grey that fits in with the colour scheme (the same grey was used in my iBook). 

I decided to change the colour from red to grey as my chosen red was the exact same red that is featured very heavily in the main, central banner. As you can see above, I have coded the media queries to position the home button halfway over the top of banner when in the mobile state, so having the button and the banner the same colour just did not look good.

New Buttons:
I've kept the same principle of having an over (left) and up (right) state to give a little boost to the users experience.

Monday, 19 May 2014

Navigation Adjustments

Now I'm back from Barcelona I've hit it hard on the physical development of my site, and the first task to accomplish was creating the navigation system. This has to be robust and work efficiently and it's something that in my case can, if I'm not careful, become very complex. 

This was my initial proposed Navigation bar.
Where it says "option 1" "option 2" etc is each of the buttons that would be used for the navigation of the site. They do not have drop-down menus attached to them but will link to the appropriate area of the page that speaks about that category (they will have appropriate names).

2 issues:

1: The central banner is very reliant on size and proportion, and very little room is left for slightly longer Chapter names for each button. On the mobile version of the site these buttons will appear tiny, too. 

2: I had zero clue on how I would build this. I had designed in (purely for aesthetic reason) a dark grey 'ribbon' that runs behind them all, and I'd no idea on how to execute this. The design was more complex than necessary.

I referred back to some original designs and saw a sketch I had made where there were two rows of buttons with two buttons on each. I liked this as it allowed me to have a bit more room to include a longer title for each chapter but didn't mean that the navigation bar took up too much space. A major worry of mine was having to stack each navigation button one on top of the other. The central banner already meets the fold of the page and is very long, the last thing I wanted was to make it even longer.
You can see how I have changed the navigation bar above. This is not a final design (I haven't added any text at all) and I am still trying to finalise the actual style of it. I'm considering removing the 'backs' of the ribbons as they are so tricky to line up with the central ribbon itself. 

As I said above, I was reluctant to change the navigation boxes so that they stacked one on top of the other. Considering the mobile site, though, the buttons are going to need to be as big and as clear and easy to use as possible. If you consider the size of an iPhone screen, the buttons above (2 on one row) are not really quite big enough to enable easy use. The design of the mobile version of the navigation bar has allowed the buttons to stack one on top of the other to ensure ease of use. The buttons still have an 'over' state of changing to yellow. (Whilst on mobile, this does not apply, it's essentially a 'down' state).