Posts tagged as:

Web Design

Fonts are More Important Than You Think

by Jeff on October 11, 2005

Most of the visitors to your website are going to spend 99% of their time doing one thing: reading your content. Given that the web is a medium mainly devoted to reading, it’s surprising just how ignorant most page authors are about typography. If you use the wrong font, you make your page painful to read – or even impossible.

The right one can make your readers stick around for much longer, and read more than they otherwise would have. But how can you know what to pick?

The Problem.

The web has a big font problem that you might not know about. The problem is this: you can only specify fonts by name in HTML and CSS. That means that, apart from logos (which can be done as images), you’re relying on the people visiting your site to have installed the fonts you’re using for headings and body text. Most people aren’t designers, and so will only have the basic fonts that come with their operating system – and, worse, they don’t even all use the same operating system!

What you end up having to do, then, is providing an order of preference: what this usually comes down to is a list of similar fonts, with your favourite first. The list will then end with either ’serif’ or ’sans’, depending on whether the font had serifs (that is, the extra little parts of the letters, like a little kick after a small d, for example). ‘Sans’ is short for ’sans-serif’, meaning that the font has no serifs.

So what are the ‘web-safe fonts’? In practice, there aren’t that many at all: you’re pretty much limited between choosing either Georgia/Times New Roman/Serif, or Verdana/Arial/Sans. As a general rule, it’s better to use sans-serif fonts on the screen, and serif fonts in print-outs: serif fonts are difficult to read on a monitor because they’re hard to represent in pixels, while sans-serif fonts have a tendency to look ‘chunky’ when printed.

Some Other Choices.

There are a few other fonts that most users have installed and that might be useful to you, although not for body text. These include Courier New (a typewriter-like font), Trebuchet (an interesting font for headings), Impact (a tabloid newspaper-like font) and Webdings (a set of images with things like fast forward and rewind symbols, a tick and a cross, and so on).

Pay Attention to Size.

Having read that, you might be off now to go and set your web page in Verdana, but wait a second. Verdana looks terrible in larger sizes – it’s just too wide and large. You need to set it to around 80% of its default size before it’s really tolerable. This also means that Verdana is largely bad in headlines – you might try Arial instead for this, preferably in bold. An ideal combination for many sites is large Arial for headlines with small Verdana for body text.

However, you should also make sure that you don’t make your fonts too small, as older users or others with bad eyesight may have trouble reading them. Always specify font sizes in relative units (such as percentages), not absolute units (such as pixels). This will make sure that your font sizes pay attention to the preferences the user has set in their browser: if they’ve asked for very large fonts, they’ll get very large fonts. Never forget that it’s ultimately up to your users how they want to see your site, and you have to respect this.

Avoid Comic Sans.

Finally, it’s worth adding a special mention here for a font that is a hate object for designers everywhere: Comic Sans. It’s a font that you’ve no doubt seen, with its trademark child’s handwriting-like letters. It was designed to have a ‘playful’ look, but the use of it has just got out of hand – if you’ve ever tried to read a whole web page in Comic Sans, you’ll know the pain I speak of. In a design sense, using it is a faux pas right up there with misplacing all your apostrophes. Read more at www.bancomicsans.com.

If you enjoyed this post, make sure you subscribe to my RSS feed!

{ 0 comments }

The Importance of Validation

by Jeff on October 9, 2005

Once you’ve written a web page, you can upload it to an HTML validator. This site, run by the web’s standards body, will check that your site is valid (’correct’) HTML, and give you some idea of how to fix it if it isn’t. This is an essential step in the development of any website – as vital as running your text through the spell checker – but whenever I recommend it there’s always someone who wonders why it’s so important. Well, here’s why.

You Know Your Code is Correct.

If your code validates, then it’s correct, and therefore very likely to work as intended on every web browser out there. If you don’t validate your pages, then you might find that people who visit your site with less forgiving browsers see nothing at all.
Correct code is more likely to display correctly on many different browsers, because it puts them into their ’standards’ mode. If code is even slightly incorrect, many browsers will use a different way of displaying it, known as quirks mode, which is designed to handle old and bad HTML, takes a long time and may make your page end up with errors you didn’t expect.

Without web standards, you end up going back to the bad old days of having to develop entirely separate web pages for different browsers. Validating by the standards ensures that all working browsers can view your content – if they can’t, the fault’s with them, not with you.

Search Engines Like Valid Pages.

When it comes time for a search engine to add your page to its results, it’s going to have a much easier time understanding the page if it’s been validated. This will often get you a higher ranking in the results, which means free visitors for you. If your page isn’t valid, search engines will often miss keywords in your pages or not understand your navigation, and may list nonsensical parts of your code under your site’s name in the search results – not exactly helpful to potential visitors who want to know what your site is about.

Mobile Devices.

More and more people are accessing the web using mobile devices like mobile phones and PDAs, and these devices have a lot of trouble with code that isn’t valid. Because they have limited processing power, it would take them a very long time to try to untangle invalid code – they will simply strip out the formatting and do the best they can with it. Writing valid HTML lets users with mobile devices see your pages as you intended.

Disabled People.

When you write valid code, it becomes much easier to view with things that aren’t web browsers, such as screen readers. Technology for disabled people doesn’t tend to be as forgiving as web browsers, so having valid code is important when it comes to working with these programs.

Future-Proofing.

Before your code will validate, you need to explicitly say which version of HTML you had in mind when you created it. This future-proofs your code, as each version of the standard doesn’t change once it’s been decided on: a valid XHMTL 1.1 page will always be a valid XHTML 1.1 page, even if everyone else has moved on to XHTML 5. Once you’ve validated your site once, you can put it on the web and be confident that people are going to be able to read it for a long time to come.

Finding Errors.

If there’s a mistake in your website’s code, validation gives you an easy way to track it down and fix it. Before validation, people had to test their site after each change and look carefully to make sure that nothing had gone wrong. Writing valid code lets you use programs that will examine what you’ve written and point at the exact place where the code doesn’t validate.

A List of Validators.

Here are a few validators that you can try. Most HTML validators are online, but there are a few that you can download and use on your own computer.

The W3C validator: validator.w3c.org

The WDG validator: www.htmlhelp.com/tools/validator

CSE validator: www.htmlvalidator.com (downloadable)

WebTechs validator: www.webtechs.com/html-val-src

Doctor HTML: www.doctor-html.com (downloadable)

You might also be interested in visiting the W3C’s main site at w3c.org, as well as the Web Standards Project at www.webstandards.org.

If you enjoyed this post, make sure you subscribe to my RSS feed!

{ 0 comments }

Finding a Good HTML Editor

by Jeff on October 6, 2005

Once you’ve decided to write your own HTML, and you’ve got some idea of how it all works, there’s one thing left to think about: which program are you going to use to do it? While you can use programs like Notepad or Wordpad that come with Windows, they don’t have any specialised HTML editing features, and that can slow you down more than you’d think.

The choice of HTML editors out there, though, is bewildering: there are literally thousands. Here’s a guide to things you should look for when you’re searching for your perfect HTML partner.

Syntax Highlighting.

One of the most vital features for any editor is syntax highlighting. This means that it understands how HTML works, and will make tags a different colour from text, making it easier for you to see what you’re doing.

You should try to find an editor that has up-to-date syntax highlighting and checks whether your tags are valid or not. Instead of just colouring anything you put between angle brackets, it should check whether what you’re entering is valid HTML, and warn you if it isn’t (usually by turning it red).

Another thing to look out for when it comes to syntax highlighting is what the editor supports that you might want to use with HTML: it’s good to have highlighting for CSS and Javascript, as well as PHP or Perl (or whatever you use server-side). Some editors mark them in the same colour to indicate ‘not HTML’, while some highlight them in a useful way – this is what you want.

Tag Suggestion.

It’s good to get an editor that knows about valid HTML tags and how they’re structured, as that means it can let you know what you should be including and let you browse through tags to find the one you’re thinking of. If you type ‘

Tag-suggesting editors can often save you typing, if they come up with a drop-down when you start typing and allow you to accept their suggestions easily by pressing tab or space. This can speed up your HTML editing significantly.

FTP Upload.

It will save you quite a lot of time if the HTML editor you choose has a built-in FTP upload facility, allowing you to enter your server, username and password, and upload the files you've just edited to the server. If your program doesn't do this, you'll have to use a separate FTP program and mess around finding where you saved your files.

Easy Text to HTML Conversion.

If you're making a lot of text content into HTML, one important feature to look for is easy conversion – otherwise you'll spend a long time putting

tags at the start and end of each paragraph. Ideally, the software should be able to spot pieces of text that are headings, lists and so on, and add HTML tags for you automatically. It won’t be helpful for everyone, but for text-heavy pages it’s indispensable.

You might also be able to find editors that can accept input in text formats that aren’t plain text – Microsoft Word documents, for example – and turn it into sensible HT

A Few Suggestions.

Metapad (www.liquidninja.com/metapad). A good drop-in replacement for Notepad, but lacks HTML-specific features.

SciTE Editor (www.scintilla.org) has excellent syntax highlighting, making it easier to be sure that you’re writing correct HTML tags and you haven’t made any layout mistakes.

Crimson Editor (www.crimsoneditor.com) is popular, although you might find it a little technical. Its biggest advantage is that it has built-in FTP uploads.

HomeSite (www.macromedia.com/software/homesite). Has good tag suggestion features, although it might be a little bulky for some tastes. Very good if you have trouble remembering tags.

As a final note, you might try editing HTML in the ‘code view’ of one of the visual editors – Dreamweaver is especially good at this, if you have it. This lets you switch back and forward easily to see what effect your changes are having.

If you enjoyed this post, make sure you subscribe to my RSS feed!

{ 0 comments }

5 Ways to Avoid the 1998 Look

by Jeff on October 4, 2005

If you’ve looked around at a few websites, you might have noticed that many of them look absolutely terrible. In many cases, this is because they were produced in the early days of the web’s mainstream popularity, but they haven’t been maintained or updated since. The chances are that their creators have never even looked at them in a modern browser, and don’t realise just how bad they look now. These websites have an affliction I like to call the ‘1998 look’ – but, unfortunately for you, even new sites aren’t altogether immune to it. Here, then, are five ways to avoid becoming a victim.

1. Don’t Use Animated GIFs.

The animated GIF is dead. It was a charming idea, once, letting us include animations on our pages as easily as normal graphics. Now, though, it looks extremely dated thanks to the small number of colours used, not to mention jarring and out-of-place. It’s even worse if you use one of those early-web ’stock animations’, like that spinning @ symbol to represent sending email – there are very few things that look more amateurish.

If you don’t want to look like you don’t know what you’re doing, stay away from animated GIFs.

2. Text in Graphics.

Unless it’s your logo or possibly a heading, don’t type text in Photoshop or Paint Shop Pro, save it as an image, and then put it on your site. It’s supremely silly, and gives you no benefit whatsoever – not only does it make the text take much longer to download, but it also stops people from selecting it or doing anything else they might want to do with it. Not to mention that text created this way is usually aligned badly and compressed so that it looks even worse than it would usually.

Keep your text as plain text, and use graphics for pictures. Text as a graphic is almost always bad.

3. Bad Backgrounds.

It’s amazing that people still do it, but there are plenty of websites out there still with absolutely disastrous backgrounds. Either they’ll have a colour that doesn’t provide enough contrast with the text, making the text unreadable, or, even worse, they’ll have a small pattern, tiled to fill the entire background. Wallpaper-style patterns are one of the most 1998 things in existence, and instantly make your website look like a joke, not to mention often making it entirely unusable.

So what should you use as a background colour? In almost all cases, the answer to the question is white – but, if you really want a colour, make sure it’s a restrained background colour that people can still read your text over. If you’re using a pattern, don’t repeat it more than once.

4. System Requirements.

Listing system requirements on your website is no longer fashionable, and thank goodness for that. In the bad old days, sites would write things like “best viewed at 800×600 using Internet Explorer 4″. Did they really think people were going to switch, just to view their website? It acted like a disclaimer, saying they couldn’t be bothered to make the site look good for everyone, and anyone using something unusual had no right to complain. It was, quite simply, terrible.

The end of the Internet Explorer/Netscape war thankfully consigned these messages to history, for the most part, but there are still some sites that have them. Don’t let your site be one – it does nothing but make you look hopelessly out of touch.

5. Open in New Window.

Finally, there’s this one, back from the days when graphic designers were just starting to get to grips with the web and wanted exact control over everything, including the size of the web browser. Going to a site would give you a message like ‘click here to launch’, and the site would then try to open a new window automatically, with none of the browser’s toolbars.

This technique has always been bad (it takes away too much control from the user), but it’s even worse now that so many users have pop-up blockers thanks to the abuse of pop-ups for advertising. If you design your site this way, many people will have trouble seeing it, including people with the latest version of Internet Explorer. Don’t do it.

If you enjoyed this post, make sure you subscribe to my RSS feed!

{ 0 comments }

Building a Budget Website

by Jeff on October 3, 2005

Once upon a time, building a website was very expensive. Now, though, you can have a site up and running for the price of a used book, if you’re frugal and careful. Getting the cheapest website you can is a great first step on the ladder, to get started on the web and see if it’s for you.

Five-Dollar Domains.

If you’re willing to take the less popular domains like .info, or some of the ones for specific countries, then you should easily be able to get your hands on a domain for less than $5. Some countries, such as .tk (the small island of Tokelau), even offer their domains for nothing!

Free Software.

Nowadays, it’s easily possible to build a website using nothing but software you can get for free – most of the best scripting languages are free, and each one has had a lot of free software built for it by hobbyists. Check out sourceforge.net, which is a big repository of free software.

You might think that free software would be less functional than paid-for software, but you’d be wrong. Plenty of free software is simply implementations of standard software, and it works perfectly well – if you want a forum, for example, there’s no clear advantage in paying massive license fees to vBulletin (the biggest seller of forum software) instead of just installing the free phpBB. The free software gives you more flexibility, and yet comes at no cost.

Free software has become an ideological movement, for people who want to be able to modify their own software, and much of the free software out there is quickly becoming widely-used and standard. Using free software doesn’t make you look cheap, because users are used to seeing it everywhere – even better, the chances are that they already know how to use it.

Templates.

Depending on what kind of website you’re running, you could use the design templates that come with your free software – they’re usually perfectly adequate. If you don’t want to do that, then a quick look around at a site like templatemonster.com is sure to turn up something suitable for your website that only costs a few dollars.

Pay as You Go Hosting.

Instead of asking you to pay monthly for hosting, more and more hosts are starting to offer ‘pay as you go’ hosting, which means that you only pay for what you use. This saves you a lot of money, because websites that are starting out rarely use all the features and bandwidth they’re paying their host to provide.

At nearlyfreespeech.net, for example, you add money to an account and then pay one dollar for each gigabyte of bandwidth you use. Most of these hosts allow you to start an account with very little money – the minimum is usually $5. If you keep your site light on graphics, that first $5 can last you a very long time.

Guerrilla Marketing.

Finally, one of the biggest costs associated with any website is marketing it – whether you’re planning to pay for banner ads or ads in search engines, marketing is a big cost. You can save money, though, by resorting to more ‘guerrilla’ techniques, such as becoming involved in online communities than you think might be interested in your website. The biggest free marketing technique out there is SEO (search engine optimisation), which is when you build your website in a way that makes it more attractive to search engines, getting you targeted visitors for free.

Taking it Further.

Once you’ve built your budget website, do you need to upgrade it later on when you start to get lots of visitors? Often, the answer is no. You might wish to buy a more prestigious .com domain name, and you might want to pay a professional designer to improve your design, but in most cases the path from a budget website to a big one isn’t all that costly either. You might think you’re building a website ‘on the cheap’ but, really, that’s the most sensible way to do it now – while you can go and spend thousands of dollars on software and hosting, you’re unlikely to see any real benefits at all.

If you enjoyed this post, make sure you subscribe to my RSS feed!

{ 0 comments }

Cut to the Chase: How to Make Your Website Load Faster

by Jeff on September 29, 2005

So your web pages have great content, a nice design, but hardly anyone seems to click through from them to any other part of your website. In many cases, the problem is the load time – people are abandoning your site for the simple reason that it just takes too long for the thing to load.

How Fast Does It Need to Be?

Fast load times are extremely important: usability studies say users rate them as one of the most important things about a website. Users would much rather use a quick-loading site of average quality than a great one that loads sluggishly – no doubt you’ve done this yourself at some point.

What’s the limit? Well, studies say that over a third of users will leave a website that doesn’t load within ten seconds. You might think that, in the age of broadband, download speeds don’t matter, but remember that in the US, over half of all Internet users are still using slow dial-up connections (if you are, you have my sympathy). Other countries don’t tend to have quite as many dial-up connections left, but broadband penetration is certainly nowhere near universal.

This means that you need to pay attention to the size and download speed of your site: those 10 seconds on a 56k dial-up connection correspond to about 70KB in page size – that means that your HTML and graphics should add up to 70KB as an absolute limit. That’s quite a stringent requirement, and makes every byte count.

Reduce Graphics.

The first thing you should do, then, is to keep the number of graphics your website uses to a minimum. Don’t have graphics for things where text or CSS would do, or where they don’t enhance your information or design significantly. You should consider the web to be a text medium, and justify every graphic you use to yourself.

Compress Your Graphics.

Once you’ve removed the un-needed graphics, you might consider compressing the ones that remain. Try turning up their JPEG compression higher, or reducing the number of colours used – you might try using a GIF, if your graphics don’t have very many different colours.

When you can’t compress your graphics any smaller, don’t miss more traditional steps: you could always resize your graphics to make them smaller!

Clean Up Your HTML.

You’d be surprised just how bloated HTML code can get with unnecessary tags, especially if you use a WYSIWYG editor, or design your site using tables. Design your site using CSS as much as you can, and use HTML Tidy (or another HTML cleaning program) to clean up your HTML. Don’t ignore the extra bandwidth taken by CSS, though, and try to keep that as small as possible too.

In many cases, a simple cleaning-up process can reduce the download size by your pages by as much as half – it’s especially effective for pages that contain long articles, because of the number of unnecessary tags many editors insert at the start of new paragraphs.

Switch Web Hosts.

Finally, you might find that, despite your website’s small download size, it still loads slowly. In these cases, your web host may be to blame. Test from a few different connections and computers to make sure, and try putting up a completely different page to test the speeds – but if it’s consistently bad, then it may be time to move hosts. You should, however, email your host about the problem first and give them a week or so to fix it, as they may just be having short-term problems.

When you’re switching to a host to try to get a good speed, you might want to consider looking around at sites that are already hosted by them. The best way to do this is to do a search for “hosted by [host’s name]” (with the quote marks), as many sites will write who they’re hosted by on one of their pages – you can then check a few sites out to see whether they’re generally fast or slow.

If you enjoyed this post, make sure you subscribe to my RSS feed!

{ 0 comments }

CSS and the End of Tables

by Jeff on September 29, 2005

In the bad old days of the web, the only way to create even slightly complex layouts was to use tables. Some sites featured silly numbers of tables, one inside the other, to create relatively simple-looking effects. With CSS, though, tables can finally be replaced.

What’s So Bad About Tables?

If you’ve ever worked with a site that uses tables, you’ll know just how difficult it can be. Your HTML becomes a mess of confusing rows and columns, with no clear markers of which parts of the page do what. If you want to redesign the site, you’re forced to try to extract your content from the HTML and start building the tables all over again. With tables, building web pages felt a lot like building a house of cards.

What’s CSS?

CSS stands for Cascading Style Sheets. CSS lets you apply styling information to specific parts of your HTML, identified by tag name, or by IDs and classes you specify. This is done using CSS selectors.

CSS Selectors.

The first thing you need to know about CSS is the basics of how selectors work. There are lots of esoteric and mostly useless selectors, but the basics aren’t too hard to grasp.

CSS relies on your tags having classes and IDs – the only real difference between an ID and a class is that an ID refers to one tag and one only, while a class can refer to more than one.

If you just have the name of a tag on its own, then your CSS rules will affect all of those tags. If you use a tag’s name followed by a dot and the name of a class, then you’ll affect all of those tags with that class. Using a tag, a hash and an ID name will affect only the tag with that ID. Using the hash and ID alone will work on any tag with that ID, while using a dot and class name along works on any tag with that class. So:

p - all paragraphs
p.thing - all paragraphs in the ‘thing’ class
p#thing - the paragraph with the ID ‘thing’
.thing - all tags in the ‘thing’ class
#thing - the tag with the ID ‘thing’

To add rules to each one of these selectors, you just put curly brackets ({}) after it, and then put the rules in that space – that’s all you need to do to create CSS.

Useful CSS Rules.

CSS rules look like this:

rule-name: setting;

Here are some of the most useful rule names and the different settings that can be applied to them.

background-color. Lets you set a page’s background colour using HTML colours (they look like this: #123456).

color. Sets colours for text.

font-family. Lets you set fonts for your text – you can add more than one font name, separated by commas, in case your first choice is not available.

font-size. You can set the font size in px or em – it’s better to use em, as these measurements are relative rather than absolute.

width and height. Lets you specify the width and height of things. You can use px or percentages.

margin. The amount of space around the edges of some content. You can add -left, -right, -top and -bottom to margin to specify these margins individually.

padding. Works the same way as margin, but is for the space between the edges of the tag’s box and its content, instead of the space between the tag’s box and other boxes.

border. Puts borders around boxes. Takes three settings (width, type and colour), so you have to put spaces between them, like this: border: 1px solid black;

text-align. Lets you align text on the left or right, or in the centre (’center’).

text-decoration. Controls some text effects – mainly used to stop links from being underlined, like this: a { text-decoration: none; }

float. Tells content to float over other content, instead of starting underneath it on a new line. This is the tag most often used to simulate the kind of effects that you get with tables – floating a div and setting the main content area’s margin to its width is one of the easiest ways to create a sidebar, for example.

If you enjoyed this post, make sure you subscribe to my RSS feed!

{ 0 comments }

How Your Personal Site Can Pay for Itself

by Jeff on August 10, 2005

Has monthly hosting fees got you down? Well cheer up! There are a few simple additions you can make to your site that can help you make your money back and then some.

The easiest thing is to add ads to your site. Google’s Adsense program offers site owners a way to display both text and image ads on their sites which make money when someone clicks on them. What’s unique about these ads is that they are contextual meaning they automatically figure out what your site is about by certain elements on your site such as page text, title and then display ads that are relevant. This increases the chances that a visitor will be interested in them. Text ads usually work better because they do not look like ads, they look like content. You can also customize the look of the ads you display to match your sites color scheme.

Google’s Adsense program can be hard to get approved for. They don’t allow anyone with a site to start displaying ads. Your site should have useful pertinent information first off. It should also have a contact page. You can find out more by visiting their site at http://www.google.com/adsense/

If for some reason you don’t get approved for Adsense there are other programs out there that are similar. Bidclix is one of them located at http://www.bidclix.com. They allow you to display text ads as well that you can customize to the look of your site. The one big difference is that they are not contextual, you have to choose what advertisers you want to display. You can also sell advertising directly to advertisers and choose how much you want to charge.

Another way to help pay for those hosting fees is through affiliate marketing. There are tons of affiliate programs out there and unless your site is about some obscure subject you should be able to find one or more that are related to your site. Once you sign up and are approved for an affiliate program you can log into their affiliate center which should be filled with information and media to promote their products. Here you can start grabbing html code to paste onto your site that will display text or banner ads with your affiliate link embedded. Then when someone clicks on your ad and makes a purchase you will receive a percentage of the sale.

A good way to promote affiliate products and to increase sales is through unbiased reviews. If you are a photographer you could start writing camera reviews and build a separate section to your site for just that. The top affiliates or “super affiliates” buy the product they are promoting which allows them to write educated reviews on the product and the company that they are an affiliate of. And yes, they buy the product through their own affiliate links which makes them some money back.

Your hosting provider might offer an affiliate program you can promote. To promote them include a link at the bottom of every page of your site that says Hosted by “company name” where company name is linked to their site with your affiliate link. Good hosting affiliate programs offer between $50 - $90 dollars for every sale you refer to them so they can be quite lucrative.

If you are continually updating your site and writing quality content then it is a good idea to offer a newsletter to keep your visitors up-to-date. You should send out a newsletter at least once a month with information your members would be interested in. In it you can include article or review blurbs that link back to your site or smaller articles with your affiliate links in them.

These methods can help your site pay for itself and within a little time you will be earning more then you spend.

If you enjoyed this post, make sure you subscribe to my RSS feed!

{ 0 comments }