o_19m7st4t316nvv6a1bg63l10e4a.pdf

Recommendations

Info

hire a professional web designer, or they use some visual HTML editing software. You could say that hiring a designer is like getting someone to make furniture for you and deliver it, while using an editor is more like buying flat-pack furniture. What I'm here to tell you, though, is that you should consider doing things another way. I'm telling you that you should go get yourself some wood and a saw. In short, you should do it yourself. Why Would I Do That? No matter what you might do, unless you're doing it yourself – that is, coding your website by hand – you're not going to have full control. Doing it yourself gives you control over every tiny, tiny detail, and puts you in a situation where there should never be a problem you can't fix. You're not relying on a company, or a designer, or anyone else – whatever goes wrong, you can fix it. Thanks to XHTML and CSS, creating websites by hand has never been easier – in fact, once you know the basics, it's often easier than fighting with some piece of software to get it to make things look the way you want. Once you know the tag for an image, it's much easier to just type it than go through a bunch of menus. When you know you want something to be a certain width, it's easier to type that in than to try to make it the right size using the mouse. Web design benefits from the kind of preciseness that you get from doing it by hand. At every stage in the process, you know what you've done and you know what you have left to do. If something isn't working the way it should, you can easily look through, find the problem, and make it right. Altogether, not only do you save the money that you would have spent on Dreamweaver or FrontPage, but you also end up with a better website in the end. Tables and Coding. For a long time, the biggest reason to stay away from hand-coding websites was that most complex layouts were done using tables, and tables were hard, especially when you had to put one inside another. Any modern website, though, really shouldn't be using tables at all, which means that you won't have to learn how to do them – that takes down the biggest barrier to hand-coding. HTML is very easy to figure out, and from there all you have to The Web Design Guide for Newbies |38
do is learn a little CSS (there are plenty of good books on it, and there's not that much to learn altogether) and you're away. Re-using Code. There are only a limited number of things that you'd want to do in HTML, and they've all been done by someone, somewhere. When you see an effect you'd like to use on any website, anywhere, knowing HTML means that you can simply use your browser's 'View Source' function to see how it was done and adapt it for your own website – this is generally considered an OK thing to do. You'll also be able to start building up little libraries of code you've written yourself – a two-column layout, a splash page, and so on – and quickly adapt them as they're needed. Even better, if you already have some HTML from a template that you bought or that came with some software, having built websites yourself will give you enough know-how to figure out how to edit it and make it look exactly the way you want. Chapter 17: Understanding Web Jargon. Don't know your HTML from your HTTP? Your cache from your cookies? The web has serious amounts of jargon, and it seems like people come up with new words almost every day. Most of it isn't especially useful, but there are some words that it's good to know to help you along on the web. Here are the essentials. Apache. The most popular web server. It is open source and free for anyone to use. Blog. A short for 'weblog'. A web page that is updated like a diary, with the most recent writing first. Usually done using blogging software instead of being maintained by hand. Browser. A web browser is the software that you use to view pages on the web. Internet Explorer is the most common browser. Cache. A web browser's cache is where it keeps files that it has downloaded from the web and might need to use again. A site's logo and navigation The Web Design Guide for Newbies |39
Page 2 and 3: ABOUT WEB DESIGNER PAD Web Designer
Page 4 and 5: Chapter 1: Why You Need a Website?
Page 6 and 7: Chapter 2: How the Web Works. Many
Page 8 and 9: Resource Location) while hosting is
Page 10 and 11: cost. Prepared to be surprised by s
Page 12 and 13: POP3 accounts. POP stands for 'Post
Page 14 and 15: these), as well as the email addres
Page 16 and 17: website to do. What kind of thing d
Page 18 and 19: professionals, have you? Well, the
Page 20 and 21: If you don't want to deal with desi
Page 22 and 23: If you're willing to take the less
Page 24 and 25: While Mozilla is a web browser itse
Page 26 and 27: GIF stands for Graphics Interchange
Page 28 and 29: As the web grew, the lack of standa
Page 30 and 31: Now, though, you can remove the fon
Page 32 and 33: intended on every web browser out t
Page 34 and 35: the web without ever knowing a thin
Page 36 and 37: out in the lead in terms of market
Page 40 and 41: graphics may be stored in the cache
Page 42 and 43: Note that you will need to save fil
Page 44 and 45: heading is, so h1 for a page's main
Page 46 and 47: 500 - Internal server error. For mo
Page 48 and 49: easons. To begin with, there are tw
Page 50 and 51: that come with Windows, they don't
Page 52 and 53: What's So Bad About Tables? If you'
Page 54 and 55: text-align. Lets you align text on
Page 56 and 57: each down further than the main con
Page 58 and 59: start growing, though, you might fi
Page 60 and 61: the 'glue' that makes a database-dr
Page 62 and 63: Basic-like language named VBScript,
Page 64 and 65: Yet, despite how common databases a
Page 66 and 67: Which Database is Right for You? If
Page 68 and 69: Once you've created your website, y
Page 70 and 71: that is how easy it makes it to cre
Page 72 and 73: mysql_fetch_assoc. Turns the result
Page 74 and 75: Separating the Application Logic. T
Page 76 and 77: written by you or by someone else.
Page 78 and 79: double-click. onmouseover. Runs whe
Page 80 and 81: limits, and do more testing than yo
Page 82 and 83: and no-one else supports it. For be
Page 84 and 85: } } ajax = new ActiveXObject("Micro
Page 86 and 87: is being used - useful when you see
Page 88 and 89:
on. Resizing works especially well,
Page 90 and 91:
provides almost every feature you c
Page 92 and 93:
on the Linux GTK (Gimp Toolkit) sys
Page 94 and 95:
Ikonboard (http://www.ikonboard.com
Page 96 and 97:
the other visitors - your role is t
Page 98 and 99:
asked for it. You should link to it
Page 100 and 101:
own. It's madness to pay thousands
Page 102 and 103:
considering first, but you should b
Page 104 and 105:
usiness with you. However, you shou
Page 106 and 107:
the checkbox a name so you can refe
Page 108 and 109:
same thing goes for lists of states
Page 110 and 111:
One of the biggest issues with prin
Page 112 and 113:
If you're about to write out a big
Page 114 and 115:
don't hide anything from the people
Page 116 and 117:
It's Not a Newspaper. What's the di
Page 118 and 119:
color is a big subject. As soon as
Page 120 and 121:
important in one way: the meta desc
Page 122 and 123:
It's not difficult to switch betwee
Page 124 and 125:
fonts.com and typography.com for a
Page 126 and 127:
sets are red-green; blue-orange, an
Page 128 and 129:
while sans-serif fonts have a tende
Page 130 and 131:
Look at it this way: not only are y
Page 132 and 133:
your content, or, worse, even hide
Page 134 and 135:
sure that your design will work jus
Page 136 and 137:
Smart Tags. Do you think it ends th
Page 138 and 139:
This principle is even more importa
Page 140 and 141:
Each option links through to anothe
Page 142 and 143:
At this point, you'd have a big pro
Page 144 and 145:
one key question you should ask the
Page 146 and 147:
Now, when users hover over the prin
Page 148 and 149:
come to associate its use with that
Page 150 and 151:
tends to provoke is "hey, I was loo
Page 152 and 153:
The Reader Often Crashes. As a fina
Page 154 and 155:
The next problem is the way Java te
Page 156 and 157:
Here's something that many people d
Page 158 and 159:
Trackbacks. Using blog software tha
Page 160:
Chapter 38: Switching Web Hosts. Fi
show all

o_19m7st4t316nvv6a1bg63l10e4a.pdf

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?