quote:
PHP and .CSS is not my cup of tea
PHP not your cup of tea? OK, I can buy that. I've only recently taken up PHP myself, and you can still build a perfectly functional website without it. CSS not your cup of tea? Well, I'm afraid I have to take issue with that.
Imagine that you have hired an architect to design your house. He tells you he has some great ideas, so you ask to see some blueprints. "Oh, sorry," he says. "Drafting really isn't my cup of tea."
Or you bring your poodle to the veterinarian because he's hacking up this nasty looking orange stuff. But when you get into his office with Fido in tow, he takes one look at the poodle and says, "Dogs just aren't my cup of tea."
Or your whip out your trusty-dusty, solar-powered (and thus environmentally-friendly) calculator and start to pound the buttons. The final step in your calculations is to divide 93294.4 by 396.2, but instead of the answer your calculator spits out an error: "Division is not my cup of tea."
OK, maybe that was a bit overboard, and I'm not trying to suggest that CSS is like a blueprint, poodle, or mathematical operator, so don't try to read too far into those analogies. What I am trying to say is that CSS is a vital part of any web designer's toolset, and you really don't have the luxury of giving it a by, not in this day and age.
I remember when CSS first came out. I was pretty psyched about the implications, but after seeing the poor support it had in the major browsers, I went back to my tables and spacer .GIFs. I dreamed of the far-off day when CSS would be fairly well supported and widely used. That day, my friend, is today.
I'm not saying that CSS support is perfect, and the deeper you get into it the more cracks you'll find. But most of the basics are supported by most browsers out there. We have the power to do today what we dreamed of yesterday. This means leaving behind our beloved tables, but once you turn to CSS you'll never go back. It's like crack--or at least I guess it's like crack, since I've never actually tried crack (nor would I recommend it). OK, um, it's like color TV. Yeah, that's it. Can you imagine going back to black and white after experiencing color?
There are uses for tables, of course, and I'm not suggesting that we all meet in the village square and burn our tables in a huge, roaring bonfire whose flames lick the midnight sky. No, we still need tables to present tabular data. We just do not need them for layout.
And, of course, before you really get into CSS, you need a solid handle on HTML (a web designer who doesn't know HTML would be like an architect who doesn't know how to build, or a vet who doesn't know how to treat animals, or a calculator that can't even add, subtract or multiply, let alone divide). Fortunately, that's not too hard, and (as you hinted at) you don't have to have it all memorized, since there are plenty of good resources out there. The FAQs that V posted are good places to start.
Now, I must admit that I've never used a WYSIWYG editor--I do all my stuff by hand. So I might not be too sensitive to the details of your case. Even if you continue to use a WYSIWYG editor, though, you should at least know enough to be able to tweak the code yourself, and you should work with something that can do CSS (although I would have no idea if there is anything like that out there... I'm sure there must be).
OK, I guess that's it for this time. I would really encourage you to learn more HTML and CSS. If you have any questions about either, you can always post them in the appropriate forums here.
[This message has been brought to you by V's echo.]