Alternative Text: html

Showing posts with label html. Show all posts

Saturday, 25 June 2016

Project 03, Part I: Fonts: Bravura London Registration Page

After being on, what I guess we'd refer to, a hiatus due to err... personal, emotional... entanglement (?) I've been out of the HTML game for some time. Like 4 weeks tops. But that's a lot of time to forget things. I feel super behind right now, but I also finally feel ready to get straight back on that horse.

Before it all kicked off, I'd started a project to recreate the registration page on Bravura London's online store. I like this site, it's clean, accessible and it has a kicking colour palette. I also wanted to attempt a project that included forms, after publishing Project 02: Forms & Buttons, putting practise into more practise.

Top: Original, Bottom: Recreate

As usual, there are ~~ever-so-slight~~ differences between the original and my rendition. Mostly to do with positioning. That is something I just can't seem to put to bed. As for styling, in terms of adding custom fonts, matching the tables and buttons, creating spritesheets I'd say that all went rather well indeed.

Adding A Custom Font

As I'm sure we're all aware, there are a select number of font families that are deemed web safe (Read more on W3Schools CSS Web Safe Fonts). These are fonts that can typically be read by any browser, on any computer as they should be installed by default. We're talking your serif, your sans serif, your monospace here.

Within these generic families are a selection of generic typefaces for when you need to specify a particular style. The typefaces within each family generally won't have much variation, once again, they're a selection of big hitters that should be available to most browsers and computers. For example, Times and Georgia would fall within the serif family. But what if you call Georgia and the user doesn't have it installed? Well, you can use a fallback that the browser can refer to if the desired typeface isn't available.

In CSS you would call:

{
font-family: "Times New Roman", Times, serif;
}

Calling font-family, you guessed it, refers to you wanting to change the typeface that is displayed. In this case we're going with Times New Roman. If you want to call a specific typeface, you will always need to do so within quotation marks ("), this is generally to avoid errors with spaces and punctuation. Times is a generic typeface, there are no quotes here because it is a single word and should come pre-installed. If the user does not have Times New Roman available to them, the browser will render Times instead. Finally, if you don't have Times, well, you fallback on serif. All these fonts are serif fonts and therefore, there should not be much visual discrepancy between what you see and what the user sees if they don't have all fonts available.

The rendering order is from left-to-right. If the user does not have the font that is being called, the browser will try the next one in the list.

We all know the classics; Times New Roman, Arial, etc. but there are thousands upon thousands of custom fonts out there, below the radar, waiting to be rendered. The two custom fonts used within the Bravura site are Lato and Dosis. Never heard or them? Nor I. Your browser won't have heard of them either, so you'll have to tell it where to find them. This is done within the <head> section of your HTML sheet.

Thankfully, both these fonts can be found within Google Fonts. This is an archive of elegantly designed open source typography. Google Fonts will also provide you with the characters and the weights for you to easily copy-paste into your code.

In HTML, my <head> code now looks a little like this:

Just like loading in a CSS stylesheet, we are loading in the data for our typefaces, including the font weights we need to use. As Google Fonts set everything up nicely for us, we just have to refer to the correct location in the href and the call the typeface within our CSS document.

This is a very friendly and free way of using custom fonts to improve the design of your site. Be weary that users still may not be able to download these custom fonts, so have comfortable fallback fonts that still render to the desired effect.

As per usual, the accompanying code. I got all fancy this time and called my stylesheet as a separate file, so if you wish to view it correctly, please check the file names.

HTML

CSS

Friday, 22 April 2016

Styling Links with IDs and Classes

As mentioned recently in Project 01: Recreating the Telegraph, I've been struggling to wrap my head around the CSS behind using the <a> tag in conjunction with id and class attributes. I was able to get the functionality to work (somewhat) flawlessly when using the id, but with a class, I had no such luck when trying to apply the same methodology. The thing is, they don't work the same way one bit.

Well, they do kind of work the same way, just a tiny bit backwards.

Referencing from within an id

When referencing an <a> element within an id, you need to put the id first. For example:

#navigation a:link, #navigation a:visited {

color: red

}

Add a space between the id and the element selector and separate multiple selections with a comma and a space. This will work because the chain for id's is:

#id > element selector > decoration

The catch is, the id tag must not be placed within an <a> element, it needs to be coded within a parent tag. The code simply doesn't run if the id is placed within the <a> tag because it is then referencing and invalidating itself.

Referencing from within a class

When referencing an <a> element within a class, you need to put the class name second. For example:

a:link.navigation, a:visited.navigation {

color: red

}

There should be no spaces between the element selector and the class name. Multiple selections should be separated with a comma and a space. My best guess for why the specificity has to be ordered this way is to account for syntax errors if the values were reversed, or had spaces, it would change their meaning entirely. The chain for classes is:

element selector > .class > decoration

With this approach, the class must be defined within the <a> tag, as to correctly reference itself.

While perhaps still a bit blurry around the edges, ordering the syntax in the manner does call correctly. For anyone interested in seeing these methods in action, you can simply copy this code here:

Sunday, 17 April 2016

Project 01: Recreating the Telegraph - The Results Are In

While I am under no illusion that this is a perfect mimicry of the actual Telegraph site design, I feel comfortable enough here, to hang up my hat and call it a day on this project. Working by eye (besides the use of the Photoshop colour-picker tool) is never easy, even more so when it comes to sizes, positioning, widths, etc. As you can see, there are some clear alignment errors - the majority of which, I tried to fix and failed.

Original article: The Telegraph - 15 Maps That Will Change the Way You See the World

For me, padding, border, margin is the clincher. W3Schools has a very clear diagram of this here, but I'm still struggling to visualise this in practice. I have most clearly failed in this area in with the ordered list within the article.

position and float are also two concepts I'm struggling to apply. The distraction of the content definitely isn't helping, so it's probably worth making a playground where I can test all the function of these elements correctly.

Designing and formatting the list numbers in CSS was the most fun part, as it gave the richest reward. To think up a method of creating circular borders (using the border-radius tag with a high value), see it work, then inspect the actual CSS and find it was originally created using a similar method is very rewarding indeed. While mine may be a little rough round the edges, it is fit for purpose.

Once again I'm supplying the HTML/CSS here. I think it's always worth sharing for the shake of learning and evolving. Even if it is learning through not what to do. I haven't seen any good HTML/CSS to know if mine is well-written, well-formatted, correct use of specificity, or class/id overload, but I can safely say that it's probably not. If it's bad, it's bad, but these are all skills to develop.

Thursday, 14 April 2016

Project 01: Recreating The Telephraph

While I'm not one to be found nose-deep in a broadsheet, let alone The Telegraph, I have to admire the simplicity of their site design, especially when learning to recreate existing CSS content. At least that what I expected this project to be like, but when I finally got pen to paper, I realised just how wrong I was.

A job like this takes a lot of planning, and the nuances within the design have proven to be unexpectedly complex. I've struggled with defining the number of <div> elements I require, scared to add more as the list of classes and tags extends longer and longer. Editing headings and other elements that also double up with the <a> tag has also been difficult - having to style a:link, a:visted, a:hover sometimes individually and sometimes not picking up changes at all. Furthermore, trying to style the numbers in a list seemed near impossible until I found this nifty tutorial which instead utilised the <span> tag (Design Shack - 5 Simple and Practical CSS List Styles You Can Copy and Paste).

While I haven't looked around yet, it would also be nice to have a colour-picker desktop app - no more copying images into Photoshop, thank you very much. I suspect there might be a tool out there for this, if not, hold that thought!

The article in particular that I'm trying to mimic is the 15 maps that will change the way you see the world travel piece. It contains a lot of images, lists, links and interesting formatting qualities. I thought it would prove an interesting challenge while not been beyond my range.

At first glance, I'm not sure if my current attempt would fool anyone, but the building blocks are definitely in place. As you can clearly see, I'm struggling with the positioning, trying to wrap my head around absolute and relative, margin and padding in particular.

There are also the colouring issues I mentioned when dealing with an element that is both a heading/p element and a <a> tag. For reasons I don't yet understand, their style only applies correctly on hover.

As a first pass, I'm happy to keep banging my head against the wall until I get to the bottom of this. I hope, by the next major update, to have fixed the positioning and link colouring issues.