The thing about computer languages is that there is some weird heaviness on the actual work involved. People are scared of by codes and although they see the power, they just can't seem to get going because they have no idea where to start.

That is where training comes in. And of course, fun training. You need to be taken by hand and shown exactly what you need to do, where you need to do it, and when you need to take the right action.

The funny thing about CSS is that it allows you to create your website in the fraction of the time when you would do it using tables. It's hard to believe, but still after all these years of promotion for CSS people (and companies!) still heavily rely on tables for layout. They have no idea that they are simply wasting time on old techniques that will be useless in a matter of time.

So where do you need to pay attention on when you are looking for a CSS Guide?

1. The Teacher

The number one thing you need to be sure of is that your teacher knows where he or she is talking about. Why is he or she teaching about Cascading Stylesheet, because they need to from their boss? Because they think they can teach, no matter the subject?

Think of that, how many teachers are only "teaching" stuff, and never practice it their own? Ask yourself "why" are you teaching you me this. Are you the best in the field? Where did you get your knowledge from?

2. Teaching Style

So the teacher may be a great person, has all the required skills, has a passion for the subject and knows about everything of it. But can your teacher deliver? Does he or she KNOW how to explain things? How to take you by hand and show you step-by-step how things work?

Is it fun to follow along with the teacher? CSS is one of those topics that can become boring easily when it's only discussed in a technical way. Make sure you know what you can expect!

An even more important thing is cutting right to the case. You don't want to end up with all kind of knowledge that you will never use in practice. It simply isn't useful to learn every possible css style there is when you just get started. And this brings us to the third point you need to pay attention on when you are looking for a css guide.

3. Teaching / learning speed

Can you keep up with the course? Does your teacher decide the speed, or do you? Of course a great way to follow a course is one that allows you to define your own speed. Home study courses and guides are wonderful for that.

4. Delivery

How is your guide delivered? Are you somebody that likes to read, follow along with a training video or both? Decide what you like, training videos are great, because they allow you to follow along in a real life situation. This means hands on practice, which is exactly what you need if you want to become good in CSS.

5. Contents

Last but not least, content. What is discussed in the guide? What is marked as important? Do you get a total reference, or do you know you don't need that, that the real thing you need is a hands on course with day-to-day subjects? Decide what you want to know, just the basics, how to create full layouts, or just how to create a menu using 100% CSS.

It's up to you now, decide what you need, you know how important the 5 above points are, and where you need to pay attention on. And one last tip, make sure you get some preview videos or sample chapter before following any course, it can save you a lot of time and money at the same time.

Hilco van der Meer
CSS Expert

How's your website, then?

I'm not asking whether it's a good site or not, but what its performance is like. Is it slow to load? Does it have problems with certain web browsers? Occasionally you'll find that code working perfectly on, say Internet Explorer, doesn't work with Firefox. And vice-versa. Any coding problems?

How should I know? Who... who cares? I hear you ask.

Because it's important. You only have seconds -- tenths of seconds, even -- to make an impression on people who come to your site. If the site isn't working, has dead links or some old code that doesn't work and leaves the site with blank areas, you can bet your life those lovely, potential customers will click away at the drop of a pixel. And more than likely they'll be clicking away to the welcoming site of one of your competitors.

Wake up and smell the Mugicha! After reading this post you no longer have any excuses for not knowing. There's a website I often turn to when I want to see how my own site is doing, performance-wise. It makes for uncomfortable reading sometimes, because it doesn't hesitate to tell me stuff I don't particular want to hear -- the site's too heavy, too many images, too many elements, you've failed at life, you're a bad, bad person... et depressing cetera. But it's well worth it.

I have no connection whatsoever with the owners of the site and this isn't an affiliate link, so click in confidence. Here it is:

http://www.websiteoptimization.com/services/analyze/

Put in the full address of your website and have a look at what it says. Pretty eye-opening stuff, eh? You didn't realise it was that bad, did you?!

I'm not particularly interested in contacting the owners of the site to ask for their optimization services, but the results I get when I check my site are very interesting. Useful, too. Oh, and completely free. Check it out.

Reusing pieces of HTML code is a common way of making web sites (or web applications) more consistent, reliable, and more manageable. Even a small web site consisting of perhaps 20 or 30 web pages can benefit from reusing code for header and footer sections, for example. If the same header or footer is used across all the pages on the site, it makes sense to put the header and footer code in separate files, and then call those files to insert their contents where required.

PHP offers two statements that can be used for inserted the contents of one file inside another: include() and require(). These two statements are virtually identical, with the only real difference being that if require() fails, it gives a fatal error, whereas if include() fails it just gives a warning. For this reason I tend to use the include() statement as it just seems slightly more friendly.

So, to include the contents of a file called header.inc inside a web page called index.php, you would just need to insert the following line of code (wrapped in PHP opening and closing tags) inside index.php.

Include 'header.inc';

As PHP takes no notice of the extension used for the included file, you can use whatever extension you want to. Be careful though, if you put passwords inside an include file with a .inc extension, they will be visible. You can get around this by putting include files that contain sensitive information outside the document tree to prevent people from browsing to them.

In Part 2 we'll look at the use of functions when developing web sites and applications.