<?xml version="1.0" encoding="utf-8"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">

    <title type="text">Hagablog</title>
    <subtitle type="text">Blog:</subtitle>
    <link rel="alternate" type="text/html" href="http://hagablog.co.uk/blog/" />
    <link rel="self" type="application/atom+xml" href="http://hagablog.co.uk/feeds/atom/" />
    <updated>2012-01-18T14:16:11Z</updated>
    <rights>Copyright (c) 2012, Alex Clarke</rights>
    <generator uri="http://expressionengine.com/" version="1.6.7">ExpressionEngine</generator>
    <id>tag:hagablog.co.uk,2012:01:18</id>


    <entry>
      <title>How to Get Around Wikipedia’s Blackout</title>
      <link rel="alternate" type="text/html" href="http://hagablog.co.uk/site/how_to_get_around_wikipedias_blackout/" />
      <id>tag:hagablog.co.uk,2012:blog/2.44</id>
      <published>2012-01-18T12:29:10Z</published>
      <updated>2012-01-18T14:16:11Z</updated>
      <author>
            <name>Alex Clarke</name>
            <email>alex.clarke@hagablog.co.uk</email>
                  </author>

      <category term="The rest"
        scheme="http://hagablog.co.uk/site/category/rest/"
        label="The rest" />
      <content type="html"><![CDATA[
        <p>Firstly, I would like to make clear that I am in full support of Wikipedia’s blackout in protest against SOPA and PIPA. I would also like to point out that despite the usefulness of Wikipedia, there is no substitute for going back to the original source of information. Maybe it&#8217;s a good thing for us not to have Wikipedia for a day. </p>

<p>But I know few people who disagree that Wikipedia is a fantastic source of knowledge and a platform from which to explore a subject in detail. I am also conscious of how many last-minute homework assignments that owe their grades to Wikipedia and such, I would like to share an easy way bypass the blackout; although I urge you not to use it without necessity, Wikipedia did this for a reason. </p>

<p>The blackout is achieved by way of a JavaScript snippet — there is no need here to go into what that means — but to get around it, all you need to do is disable JavaScript!</p>

<p>Exactly how you do that varies from browser to browser and I don&#8217;t have the time to give instructions on how to do it in every browser. Simple google “Disable JavaScript in [BROWSER]” and substitute [BROWSER] with the name of your browser. </p>

<p>If you use Safari, you can do it by enabling the “Develop” menu item by going into Preferences, Advanced, and clicking the tickbox to show the develop menu. From there, go to the develop menu and click “Disable JavaScript”.  </p>

 <p>Javascript is something you’ll want to have enabled normally, so don’t forget to re-enable it afterwards.
</p>
      ]]></content>
    </entry>

    <entry>
      <title>How to Start Making Websites the Modern Way (Part Two)</title>
      <link rel="alternate" type="text/html" href="http://hagablog.co.uk/site/how_to_start_making_websites_the_modern_way_part_two1/" />
      <id>tag:hagablog.co.uk,2011:blog/2.43</id>
      <published>2011-02-18T11:54:31Z</published>
      <updated>2011-02-20T16:24:33Z</updated>
      <author>
            <name>Alex Clarke</name>
            <email>alex.clarke@hagablog.co.uk</email>
                  </author>

      <category term="Work"
        scheme="http://hagablog.co.uk/site/category/work/"
        label="Work" />
      <content type="html"><![CDATA[
        <p>Before we get going, I have a present for you. <a href="http://dl.dropbox.com/u/24673/yourwebsite.zip">Download</a> this collection of files and we&rsquo;ll get going. Today we&rsquo;ll deal with <code>index.html</code> and everything else I&rsquo;ll introduce when we need it; for the purposes of making a basic web page, you don&rsquo;t need to understand what is between the <code>&lt;head&gt;</code> tags (not to be confused with <code>&lt;header&gt;</code> that we will cover later) but I&rsquo;ll talk about them in a future article. Anything between the <code>&lt;body&gt;</code> tags will be visible on the site&mdash;copy your marked-up content from last week into there.</p>

<h2>Structure</h2>

<p>The web isn&rsquo;t just a collection of plain, one-column pages like we built last time; it has layout and structure. To do this, we need to start dividing your content.</p>

<p>We do this by putting some of your existing content into containers; you write an opening tag before the first bit of content in the group and a closing tag after the last bit. There a several of these containers and all have a slightly different part to play:</p>

<ul>

<li><code>&lt;div&gt;</code> (division) a generic container for any content.</li>

<li><code>&lt;section&gt;</code> a generic container for related content.</li>

<li><code>&lt;nav&gt;</code> (navigation) a list of some of links to other pages on the site&mdash;you know what navigation is.</li>

<li><code>&lt;article&gt;</code> a specialised container for a news article, story or other self-contained piece of work.</li>

<li><code>&lt;header&gt;</code> a specialised container for the kind of information that goes in a header area&mdash;be that of the whole page or a single article.</li>

<li><code>&lt;footer&gt;</code> just like a header, it is a specialised container for the kind of content you need, but want to put out of the way in a footer. This can be for the whole page or a single article.</li>

<li><code>&lt;aside&gt;</code> this is a specialised container for information that is related to that of the main article but isn't crucial to understanding it.</li>

</ul>

<h2>Picture this…</h2>

<p>You have the page title, below it a tagline and below that a list of other pages on the site. Then you have two articles, each with a title, the article itself, a few sentences about the author (you!) and some other information such as the date it was published, any references and copyright.</p>

<p>Here it is:</p>

<img src="http://www.hagablog.co.uk/assets/img/nocode.jpg"/>

<p>Around the page title and the tagline we&rsquo;ll put a <code>&lt;header&gt;</code> because this is the main heading of the page and around the list of other pages (the navigation), we'll put a <code>&lt;nav&gt;</code>.</p>

<p>Then you open a <code>&lt;section&gt;</code> and then an <code>&lt;article&gt;</code>, don&rsquo;t close either of them just yet. Then put a <code>&lt;header&gt;</code> around the article&rsquo;s title and a <code>&lt;footer&gt;</code> around the author information, copyright and publishing date.</p>

<p>Now close the <code>&lt;article&gt;</code> and open another one; repeat what you just did for the <code>&lt;header&gt;</code> and <code>&lt;footer&gt;</code> of the last article. Now close the <code>&lt;section&gt;</code>. </p>

<p>This is what your site should look like now; the boxes are just to illustrate, you wont see them</p>

<img src="http://www.hagablog.co.uk/assets/img/code.jpg"/>

<h2>ARIA roles</h2>

<p>Now that you have broken down your content into blocks, you might want to tell the computer what each of these blocks is for. These roles are important for two reasons: one, because not everybody views the Internet like we do&mdash;if someone is having the page read out for them by a screen-reader they probably don't want to hear the name of the site and tagline on every page&mdash;they want to get straight to the actual content. And two, because we can use these roles to specify which object we want to style&mdash;we’ll get onto that next time.</p>

<p>Just like we used <code>alt=""</code> to describe an image for those who can&rsquo;t see it we use <code>role=""</code> to describe what each part of your page does. Put this in a structural tag like those we just used. For example <code>&lt;header role="banner"&gt;</code>.</p>

<ul>

<li><code>banner</code> The primary branding area or masthead of the page&mdash;this can go on a <code>&lt;header&gt;</code> that is the heading of the page, but not the heading of an article.</li>

<li><code>main</code> The main content on the site, in our example above it would go on the <code>&lt;section&gt;</code> because all of the content is inside it.</li>

<li>If you use an <code>&lt;aside&gt;</code> then you should probably give it a <code>role="complementary"</code> and if use a <code>&lt;footer&gt;</code> then you should give it a <code>role="contentinfo"</code>. Likewise, the same applies for <code>&lt;nav&gt;</code> and <code>role="navigation"</code>.</li>

</ul>

<p>This may feel like doing things twice but you&rsquo;ll thank me for it next time.</p>

<p>Okay&hellip; so I lied to you. That wasn't nearly as fun as I made it out to be last week&mdash;but you wouldn&rsquo;t have read it if I said it was boring. If you compare your page before and after this lesson in a browser then it shouldn't have made any difference; what you can't see is we are now ready to start adding some style to your web page&mdash;but that is for next week! =P</p>
 
      ]]></content>
    </entry>

    <entry>
      <title>How to Start Making Websites the Modern Way</title>
      <link rel="alternate" type="text/html" href="http://hagablog.co.uk/site/how_to_start_making_websites_the_modern_way3/" />
      <id>tag:hagablog.co.uk,2011:blog/2.41</id>
      <published>2011-02-09T13:10:39Z</published>
      <updated>2011-02-13T06:45:41Z</updated>
      <author>
            <name>Alex Clarke</name>
            <email>alex.clarke@hagablog.co.uk</email>
                  </author>

      <category term="Work"
        scheme="http://hagablog.co.uk/site/category/work/"
        label="Work" />
      <content type="html"><![CDATA[
        <p>Although I complained about it at the time, our lecturer&rsquo;s advice wasn&rsquo;t bad; just outdated. That doesn&rsquo;t matter&mdash;he&rsquo;s a scientist, not a web designer&mdash;he doesn&rsquo;t need to keep up with the changing ways that websites are written.</p>

<p>That said, <em>you</em> shouldn&rsquo;t learn techniques that are already at least a decade out of date. For that reason, I hope I&rsquo;ll be able to teach you some of the basics of how to start making websites the modern way.</p>

<p>This will be an ongoing series, starting today with how to turn a page of text into something a computer can make sense of and gradually building up your skills until you can make a whole website using modern techniques.</p>

<h2>Start with your content</h2>

<p>It is very tempting to dive straight into designing your site but spare a moment to think about what matters most; it&rsquo;s your content.</p>

<p>Go away and write your content first; at the end of the day, most of our marks will come from what we write, not from how the page looks and in the real world no one will visit your site in the first place if it doesn't have decent content.</p>

<img src="http://www.hagablog.co.uk/assets/img/nohtml.jpg" alt="A page of text">

<p>See this? It&rsquo;s actually an extract from some of our lecture notes. It&rsquo;s not a webpage, just a good-ol&rsquo;-fashioned page. To turn this into a webpage we need to &lsquo;mark it up&rsquo;&mdash;that is just a fancy way of saying we need to tell the computer what to do with our text. You can do this in Word, TextEdit, NotePad or the HTML editor in DreamWeaver, it doesn&rsquo;t matter.</p>

<h2>Tell the computer what to do</h2>

<p>Everywhere you have a paragraph, write <code>&lt;p&gt;</code> before it and <code>&lt;/p&gt;</code> after. This is known as &lsquo;wrapping&rsquo; the text in a &lsquo;tag&rsquo;; in this case you are wrapping a paragraph in a <code>&lt;p&gt;</code> tag. Once you open a tag with a <code>&lt;p&gt;</code> you must close it with a <code>&lt;/p&gt;</code>.</p>

<p>Lists may look a little more complicated but really they&rsquo;re not. If you think about it, there are two types of lists, those that have a specific order to them: olivine, pyroxene, amphibole; and lists that are just in the order you think of them: sandstone, limestone, mudstone.</p>

<p>Lists with an order are marked up with an <code>&lt;ol&gt;</code> (ordered list) and lists with no order are done with <code>&lt;ul&gt;</code> (unordered list). You can think of <code>&lt;ol&gt;</code>s as numbered lists and <code>&lt;ul&gt;</code>s as bulleted lists.</p>

<p>The individual points in your lists, be they ordered or unordered, are all wrapped in an <code>&lt;li></code> for list item.</p>

<p>There are different types of headings, major headings that signal the start of a piece of work and smaller headings that denote different sections in the same piece of work.</p>

<p>Wrap your major heading in an <code>&lt;h1&gt;</code> and your smaller heading in an <code>&lt;h2&gt;</code>. Headings that divide up an <code>&lt;h2&gt;</code> can be marked up with an <code>&lt;h3&gt;</code> and headings in an <code>&lt;h3&gt;</code> can be marked up in an <code>&lt;h4&gt;</code> etc. all the way to <code>&lt;h6&gt;</code>.</p>

<img src="http://www.hagablog.co.uk/assets/img/html.jpg" alt="A page of text that has been marked up">

<h3>Links and Images</h3> 

<p>That was pretty easy, all things considered. Now we want to put a link in.</p>

<p>The technical name for links are <strong>hyper</strong>links. They are written with an <code>&lt;a&gt;</code> tag (the <code>a</code> stands for anchor&hellip; don&rsquo;t ask). Between the <code>&lt;a&gt;</code> and the <code>&lt;/a&gt;</code> you write what you want the link to say, for example <code>&lt;a&gt;download the supporting documentation&lt;/a&gt;</code>. That is all well and good but unless your computer is telepathic it doesn&rsquo;t know where to take you; so you write <code>href=""</code> <em>inside</em> the opening <code>&lt;a&gt;</code> tag to make this: <code>&lt;a href=""&gt;</code>. Inside the speech marks you put the web address that you want the link to take you to.</p>

<p>Now for images. This is actually quite easy but is where HTML (yes, you&rsquo;re writing HTML) gets a bit abstract. The code goes something like this: <code>&lt;img src="img/image.jpg" alt="This is a picture"&gt;</code>.</p>

<p>Let&rsquo;s dissect that a moment: we have an <code>&lt;img&gt;</code> tag and inside it we have two other things. <code>src</code> means source, this is where you tell the computer where to find your image; you write <code>src=""</code> and in the speech marks you write the path that the computer follows to get to the image, then the image name. In the example above I have a folder called  <code>img</code> and in that folder I have an image called <code>image.jpg</code> (the .jpg is the file format and should be next to the name of the image), the forward slash indicates a progression from one folder to another.</p>

<p>The <code>alt="" </code> is where you describe the image for someone who can&rsquo;t see it. Blind people use the Internet too and it is for them that you must use an alt. You don’t need to close an <code>&lt;img&gt;</code> tag.</p>

<p>If you&rsquo;re not confident, sit and digest that for a moment. Unfortunately, that is the direction we&rsquo;re heading.</p>

<p>Brilliant! You have just turned a regular page into the beginnings of a webpage. Sit back, make yourself some tea and let me write the next bit. I&rsquo;ll be teaching you how to divide a linear page of text and images into different blocks of content (it&rsquo;s actually more interesting than it sounds).</p>
 
      ]]></content>
    </entry>

    <entry>
      <title>Physics revision notes</title>
      <link rel="alternate" type="text/html" href="http://hagablog.co.uk/site/physics_revision_notes/" />
      <id>tag:hagablog.co.uk,2010:blog/2.37</id>
      <published>2010-05-27T00:08:28Z</published>
      <updated>2010-05-26T18:47:29Z</updated>
      <author>
            <name>Alex Clarke</name>
            <email>alex.clarke@hagablog.co.uk</email>
                  </author>

      <category term="Work"
        scheme="http://hagablog.co.uk/site/category/work/"
        label="Work" />
      <content type="html"><![CDATA[
         
      ]]></content>
    </entry>

    <entry>
      <title>How I revise</title>
      <link rel="alternate" type="text/html" href="http://hagablog.co.uk/site/how_i_revise/" />
      <id>tag:hagablog.co.uk,2010:blog/2.36</id>
      <published>2010-05-05T00:18:04Z</published>
      <updated>2010-05-04T18:21:05Z</updated>
      <author>
            <name>Alex Clarke</name>
            <email>alex.clarke@hagablog.co.uk</email>
                  </author>

      <category term="Work"
        scheme="http://hagablog.co.uk/site/category/work/"
        label="Work" />
      <content type="html"><![CDATA[
        <p>With your exams coming up, you may be fretting about revision. Believe me, I am, that is why I’m so busy. For the next couple of months there is nothing more important than your future so put everything else to one side, it doesn’t matter any more.</p>

<p>I can’t tell you how you should revise; all I can tell you is how I like to revise. I’m not that smart (what? you thought I was? I’m flattered) but I generally do well because I put my absolute all into it. I can’t possibly do well if I don’t put absolutely 100% in 100% of the time.</p>

<p>So here goes; tips and methods that I have found useful:</p>

<h3>Do something</h3>

<p>You are not a sponge and information won’t soak into you. You have to work at it and pump it rather than expecting osmosis to do it for you.</p>

<h3>Work hard</h3>

<p>The more you think you’re going to fail, the more work you have to do. There are effective ways of revising that minimise the time, but there is no way of instantly revising everything.</p>

<h3>Don’t overdose</h3>

<p>Take breaks from revising every-so-often. If you tied for time and don’t think you can afford to take breaks then mix it up; while having a break from one subject, revise for a completely different one.</p>

<h3>Sleep</h3>

<p>Once your brain has gone, you’ve had it. Go to sleep, rest and make sure you aren’t tired during your exam.</p>

<h2>How I revise</h2>

<p>I download the syllabus and go through it, addressing each point in detail, then I make a note of how to do every skill I need to know—be those equations, methods or essay structures—I then make note of every ‘key definition’; going through the whole syllabus before moving on. This will end up being absolutely huge and completely the opposite of what everyone says is good practice (condensing down to a side of A4) but what you are doing is not making notes to then revise off, you are compiling a comprehensive list of everything you need to know and in the process are going through the entire syllabus a number of times. If you want quick references that is fine, assess where you need to work on and take out what you are already rock-solid on, leaving only the bits you struggle with.</p>

<p>For other methods of revising (for example ‘mind maps’ which I find stupidly chaotic and I can’t revise from but I know they are popular right now), just take a google. I had planned to detail a few here but there are just so many that it isn’t worth it.</p>

<p>So how do you revise? Please share ’cause you might help someone else.</p> 
      ]]></content>
    </entry>

    <entry>
      <title>Mixing Fonts</title>
      <link rel="alternate" type="text/html" href="http://hagablog.co.uk/site/mixing_fonts/" />
      <id>tag:hagablog.co.uk,2010:blog/2.35</id>
      <published>2010-04-21T23:36:27Z</published>
      <updated>2010-04-21T17:38:29Z</updated>
      <author>
            <name>Alex Clarke</name>
            <email>alex.clarke@hagablog.co.uk</email>
                  </author>

      <category term="Elsewhere"
        scheme="http://hagablog.co.uk/site/category/elsewhere/"
        label="Elsewhere" />
      <content type="html"><![CDATA[
         
      ]]></content>
    </entry>

    <entry>
      <title>Vector Polishing Techniques</title>
      <link rel="alternate" type="text/html" href="http://hagablog.co.uk/site/vector_polishing_techniques/" />
      <id>tag:hagablog.co.uk,2010:blog/2.34</id>
      <published>2010-03-30T14:08:02Z</published>
      <updated>2010-03-30T08:09:03Z</updated>
      <author>
            <name>Alex Clarke</name>
            <email>alex.clarke@hagablog.co.uk</email>
                  </author>

      <category term="Elsewhere"
        scheme="http://hagablog.co.uk/site/category/elsewhere/"
        label="Elsewhere" />
      <content type="html"><![CDATA[
         
      ]]></content>
    </entry>

    <entry>
      <title>Adobe Illustrator Mesh Reshape</title>
      <link rel="alternate" type="text/html" href="http://hagablog.co.uk/site/adobe_illustrator_mesh_reshape/" />
      <id>tag:hagablog.co.uk,2010:blog/2.33</id>
      <published>2010-01-29T20:41:06Z</published>
      <updated>2010-01-29T14:42:08Z</updated>
      <author>
            <name>Alex Clarke</name>
            <email>alex.clarke@hagablog.co.uk</email>
                  </author>

      <category term="Elsewhere"
        scheme="http://hagablog.co.uk/site/category/elsewhere/"
        label="Elsewhere" />
      <content type="html"><![CDATA[
         
      ]]></content>
    </entry>

    <entry>
      <title>How to Get a Professional Look With Color</title>
      <link rel="alternate" type="text/html" href="http://hagablog.co.uk/site/how_to_get_a_professional_look_with_color/" />
      <id>tag:hagablog.co.uk,2009:blog/2.32</id>
      <published>2009-12-24T19:49:17Z</published>
      <updated>2009-12-24T13:50:18Z</updated>
      <author>
            <name>Alex Clarke</name>
            <email>alex.clarke@hagablog.co.uk</email>
                  </author>

      <category term="Elsewhere"
        scheme="http://hagablog.co.uk/site/category/elsewhere/"
        label="Elsewhere" />
      <content type="html"><![CDATA[
         
      ]]></content>
    </entry>

    <entry>
      <title>UCAS Typography</title>
      <link rel="alternate" type="text/html" href="http://hagablog.co.uk/site/ucas_typography/" />
      <id>tag:hagablog.co.uk,2009:blog/2.31</id>
      <published>2009-12-16T22:48:01Z</published>
      <updated>2009-12-16T17:01:03Z</updated>
      <author>
            <name>Alex Clarke</name>
            <email>alex.clarke@hagablog.co.uk</email>
                  </author>

      <category term="Work"
        scheme="http://hagablog.co.uk/site/category/work/"
        label="Work" />
      <content type="html"><![CDATA[
        <p>I really wanted to add a little extra class by using ligatures, but since it is a simple web form I can&rsquo;t. More importantly, I can&rsquo;t even use the right dashes and correct quotes for fear that they will be rendered incorrectly.</p>

<p>I presume that it is supposed to level the playing field so that it is the best written, not the best typeset, statement that stands out; but still, presentation is very important, and typography&mdash;even just at a basic level&mdash;should be taught in school and be a mark of attention to detail, just like correct spelling and grammar.</p>

<p>Instead, even those who know better have to use bad typography in what has been described as &lsquo;the most important piece of writing so far&rsquo;. I don&rsquo;t know how the paper system worked&mdash;I&rsquo;m sure there were restrictions in place&mdash;but I&rsquo;m also sure it gave much greater flexibility and allowed applicants to use the right glyphs in the right places.</p>

<p>I know it&rsquo;s too late for any change to make a difference to me, but I&rsquo;d really like to see a future version of UCAS Apply that has support for correct typography. I know computers are still very young and the focus of innovation has been in moving forward, but we are losing something in our haste; we are forgetting centuries of tradition and I would think the universities would be the perfect people to try and protect that while still being progressive. That may even be the case but UCAS really isn’t helping the matter.</p>

<p>P.S. If you are a university checking me out, please <a href="mailto:2009@hagablog.co.uk">email me</a> from a university email address and I will give you my personal statement typeset as I intended it.</p> 
      ]]></content>
    </entry>

    <entry>
      <title>Harry Potter enters the Twilight zone</title>
      <link rel="alternate" type="text/html" href="http://hagablog.co.uk/site/harry_potter_enters_the_twilight_zone/" />
      <id>tag:hagablog.co.uk,2009:blog/2.30</id>
      <published>2009-12-08T23:40:36Z</published>
      <updated>2009-12-08T17:49:37Z</updated>
      <author>
            <name>Alex Clarke</name>
            <email>alex.clarke@hagablog.co.uk</email>
                  </author>

      <category term="Elsewhere"
        scheme="http://hagablog.co.uk/site/category/elsewhere/"
        label="Elsewhere" />
      <content type="html"><![CDATA[
         
      ]]></content>
    </entry>

    <entry>
      <title>Grammer for geeks</title>
      <link rel="alternate" type="text/html" href="http://hagablog.co.uk/site/grammer_for_geeks/" />
      <id>tag:hagablog.co.uk,2009:blog/2.29</id>
      <published>2009-11-30T11:18:19Z</published>
      <updated>2009-11-30T05:19:20Z</updated>
      <author>
            <name>Alex Clarke</name>
            <email>alex.clarke@hagablog.co.uk</email>
                  </author>

      <category term="Elsewhere"
        scheme="http://hagablog.co.uk/site/category/elsewhere/"
        label="Elsewhere" />
      <content type="html"><![CDATA[
         
      ]]></content>
    </entry>

    <entry>
      <title>Design your school work—Part 3: Typefaces</title>
      <link rel="alternate" type="text/html" href="http://hagablog.co.uk/site/design_your_school_workpart_3_typefaces/" />
      <id>tag:hagablog.co.uk,2009:blog/2.28</id>
      <published>2009-11-10T10:12:22Z</published>
      <updated>2009-11-11T04:39:23Z</updated>
      <author>
            <name>Alex Clarke</name>
            <email>alex.clarke@hagablog.co.uk</email>
                  </author>

      <category term="Work"
        scheme="http://hagablog.co.uk/site/category/work/"
        label="Work" />
      <content type="html"><![CDATA[
        <p>Maybe it is because I know the most about this particular aspect but I think this really needs to be split into two and so I will teach you some of the basics of type in terms of what kinds of typefaces to use when and what to use for emphasis. Next week I ask you to bring your magnifying glass to look at some of the really fine details that set apart the poseurs from the people who really know what they are doing.</p>

<p>So, I would hope that you can tell the difference between different typefaces, even if you can’t accurately describe them or put a name to them. So... Spot the difference:</p>

<p><img src="/assets/img/spot-the-difference.png" alt=""></p>

<p>While there are many different ways of classifying typefaces, I tend to use the simplest, most obvious and probably the most flawed system. They either have serifs or they don’t, either closely resemble handwriting or they don’t.</p>

<p><img src="/assets/img/4faces.png" alt=""></p>

<p>The most useful to us are the top two. A serif typeface (like Times New Roman, Georgia, Garamond, Caslon, ect.) has little details on the ends of the letter-forms which help to guide the eye along the lines; a sans-serif (like Arial, Helvetica, Verdana, Calibri, ect.) doesn’t have these but they can be just as useful.</p>

<p><img src="/assets/img/sans-vs-serif.jpg" alt=""></p>

<p>While there are sub-divisions within these, I don’t think we really need to go into them—there are enough places on the internet where that kind of knowledge can be found.</p>

<p>Generally speaking, serifs are more readable in large blocks and so I would recommend that you use them for the text in your essays. Sans-serifs are more legible meaning they are easier to read at a glance and so I maybe put your name, word count and title in a sans. I personally prefer to do everything in pretty serifs, regardless of the implications to legibility. You don’t have to take my every word as gospel but make your own decisions what looks good and when visual appearance out-weighs functionality—in an essay situation, this rarely happens.</p>

<p>While in most situations I would strongly advise against using any kind of script or handwriting font in an essay—and <strong>never</strong> use one for large blocks of text—but there are times (for example in a pull-quote (I’ll come on to them later) or if you are writing something that should be hand written.</p>

<p>In <a href="http://www.stepheniemeyer.com/">Stephenie Meyer’s</a> Twilight books, each character has their own distinct handwriting font which helps to show a little bit more character and allows the reader to see, at a glance who has written the letter. I can’t really see how you would integrate that into an essay but if it calls for it then I better give you some advise on what to do with them.</p>

<p><img src="/assets/img/eclipse-script.jpg" alt=""></p>

<p>For one, I don’t care what you prefer normally, never justify the text, when was the last time you saw someone doing this in their handwriting. Secondly, the size and shape of the letters dictate how big to make the font and what the line-spacing/leading should be like. Finally, most scripts have interconnecting letters so don’t change the letter-spacing/tracking or this effect will be ruined.</p>

<p>It could be argued that this would be a pull-quote (I said I would get on to them), and I’m sure everyone who has ever read a newspaper has seen one of them—those quotes from people, usually set in larger text that breaks out from the rest of the page. While they are normally used in newspapers, a variation can be used to add some visual spark to your essays. You don’t have to have a quote from someone, maybe you have an important statistic or point to make that you want to show off, why not <em>design</em> that into your essays?</p>

<p><img src="/assets/img/stats.jpg" alt=""></p>

<p>So now that we have talked about calling attention to a block of text, now lets look at calling attention to individual words. Firstly with italic or oblique (both slanted) text; with bold type; with colour; with small caps and with another typeface.</p>

<p><img src="/assets/img/em-italic.png" alt=""></p>

<p>Probably the most used form of emphasis is slanted text, and for good reason;it is definitely noticeable, calls attention to itself subtly and doesn’t require a colour printer.</p>

<p><img src="/assets/img/italoblique.png" alt=""></p>

<p>Most people would think that all slanted text is italics, but there are actually two types. Italics are redrawn to be more cursive while the second type—oblique—is just skewed slightly.</p>
 
<p><img src="/assets/img/em-bold.png" alt=""></p>

<p>Second to that is probably the mighty bold. Simple and effective, this calls more attention to itself that italics and so should be used less.</p>

<p><img src="/assets/img/em-colour.png" alt=""></p>

<p>As I mentioned last week, colour can be used for emphasis but make sure that you change the weight to bold to compensate for the power of the black text around it.</p>

<p><img src="/assets/img/em-sc.png" alt=""></p>

<p>Small-caps are exactly what they say on the tin; small capital letters that can be used for emphasis.</p>

<p><img src="/assets/img/cd-vs-td.png" alt=""></p>

<p>Unfortunately, not all typefaces have them and if you let the computer draw them for you by simply scaling down full-sized capitals it’ll lose the effect.</p>

<p><img src="/assets/img/em-sans.png" alt=""></p>

<p>Another method of emphasis is to use a different typeface altogether. If you are using a serif then a sans for emphasis can work really well and because it is so rarely done it can give a nice, unusual effect.</p>

<p>Headings can be another matter altogether. Although you must be careful not to go overboard, you can use pretty much whatever font you like here. This is the time to show off your sassy personality with a snazzy typeface. Bear in mind though, that it is still a piece of school work. Don’t use the yellow submarine font in your IT essays.</p>

<p><img src="/assets/img/funny-head.jpg" alt=""></p>

<p>The most important thing is that here is a definite difference between heading and body text. You can do this with size, all-caps, small-caps, bold, different face... Sound familiar?</p>

<p><img src="/assets/img/head-allcaps.jpg" alt=""></p>

<p>Finally, as you can see in the example above, drop-caps give a lovely effect. Follow <a href="http://thenewpaperclip.com/2007/05/04/insert-a-drop-cap-in-word-2007/">this guide</a> to use them in Microsoft Word. Don’t use them on every line, again the more you use something, the less effective it becomes. Try using them on the first paragraph of your essay or at the start of a new chapter.</p>

<p>I think the key is to use functional typefaces and make your essay stand out with the embellishments. Your teacher will most likely appreciate you making your work easier to read and more visually appealing.</p>

 
      ]]></content>
    </entry>

    <entry>
      <title>Typesetting Tables</title>
      <link rel="alternate" type="text/html" href="http://hagablog.co.uk/site/typesetting_tables/" />
      <id>tag:hagablog.co.uk,2009:blog/2.27</id>
      <published>2009-11-04T10:47:40Z</published>
      <updated>2009-11-04T04:48:41Z</updated>
      <author>
            <name>Alex Clarke</name>
            <email>alex.clarke@hagablog.co.uk</email>
                  </author>

      <category term="Elsewhere"
        scheme="http://hagablog.co.uk/site/category/elsewhere/"
        label="Elsewhere" />
      <content type="html"><![CDATA[
         
      ]]></content>
    </entry>

    <entry>
      <title>Design your school work—Part 2: Colour</title>
      <link rel="alternate" type="text/html" href="http://hagablog.co.uk/site/design_your_school_workpart_2_colour/" />
      <id>tag:hagablog.co.uk,2009:blog/2.26</id>
      <published>2009-11-03T22:38:17Z</published>
      <updated>2009-11-03T17:33:18Z</updated>
      <author>
            <name>Alex Clarke</name>
            <email>alex.clarke@hagablog.co.uk</email>
                  </author>

      <category term="Work"
        scheme="http://hagablog.co.uk/site/category/work/"
        label="Work" />
      <content type="html"><![CDATA[
        <p>Colour can really make a piece of work, but it can also totally destroy it. In the context of an essay, where the content is the primary focus, it is a good idea to keep colour to a minimum. If there is even the slightest doubt that you will be able to use a colour printer then I would do everything in black and white.</p>

<p><img src="/assets/img/geology.jpg" alt="" /></p>

<p>Embarrassing confession moment. This was my GCSE geology coursework. While the content was actually alright, the design is plainly awful for so many reasons. The most obvious one is the orange gradients on the tables. </p>

<p><img src="/assets/img/table-grad.png" alt="" /></p>

<p>The scary thing was at the time I thought it looked good. For this reason I am begging you to stay away from gradients like that. </p>

<p><img src="/assets/img/table-colour.png" alt="" /></p>

<p>I think this is perfectly acceptable and wont give your teacher a headache.</p>

<p><img src="/assets/img/table-minimal.png" alt="" /></p>

<p>This is how I do tables. I took my inspiration from this <a href="http://24ways.org/2007/typesetting-tables">24 Ways article by Mark Boulton</a> and I find this to be the cleanest and most printer friendly way of setting tables. I highly recommend reading that article as it goes into so much more detail than I will be able to do specifically on the topic of tables.</p>

<p>As far as colour in pictures go, I would leave it there. Making pictures black and white can make the page look a bit boring, especially if you remove the colour and don’t up the contrast. If you don’t have access to a colour printer then make them black and white.</p>

<p><img src="/assets/img/em-red.jpg" alt="" /></p>

<p>Colour can also be used for emphasis, red typically stands out strongly on a page and you don’t need much of it to make an impact, in fact too much can ruin the effect.</p>

<p><img src="/assets/img/em-blue.jpg" alt="" /></p>

<p>Blue can also be used for emphasis but because it recedes from the page you can use much more of it, but still use in moderation.</p>

<p><img src="/assets/img/em-yellow.jpg" alt="" /></p>

<p>Yellow is far too pale to use for emphasis, make sure that whatever colour you use it is dark enough to be able to see it easily. Unless you have a good knowledge of colour theory I would stay away from using large amounts of it in your essays and don’t use colour for emphasis if you don’t have access to a colour printer.</p>

<p>By making things look simple you aren’t removing the design, just designing it to be functional, which is ultimately the most important thing where an essay is concerned. However, if you’re really feeling creative and you have a good knowledge of Photoshop or similar then you could have a go at producing something like this:</p>

<p><img src="/assets/img/rip.jpg" alt="" /></p>

<p>Again, only use in moderation, the less frequently you use something the more impact it will have. Also make sure you have a good reason for styling that paragraph so differently, again it all comes down to setting your content in such a way that it gets the best attention in the right places for the right reasons.</p>



 
      ]]></content>
    </entry>


</feed>
