I think Kirbs was assuming you were trying to get around learning CSS or something. While his tone might be a bit confrontational, his suggestions are actually valid.
My preferred way of doing stuff is purely text in an IDE. Notepad++ is a simplistic editor with syntax highlighting, and there are others out there.
You will have to learn how to do the text stuff whether you want to or not, since there's no "modern" and "good" WYSIWYG based editors out there that will make standardized documents that will look the same across all browsers. I think Nvu might be a good WYSIWYG editor but I haven't really tried it so I can't say. Even with a near perfect one you will likely have to tweak the source code to get everything working perfectly across all the major browsers.
So you should learn XHTML (a "strict" form of HTML which helps you build pages which look the same across all browsers easier) and CSS levels 1 and 2. HTML 5 and CSS 3 introduce some new stuff you should look at too, it's all about keeping up with the latest standards.
When making pages regularly run them through the official XHTML and CSS validators provided by the W3C (Google for them) so you can catch any errors you make early so they're easy to correct. You should also be keeping an instance of every browser you're making the page for so you can catch and fix rendering/JavaScript problems in one quickly and easily, otherwise you have to hunt them down later.
Don't be afraid to look at the source of other web pages to see how they did something you find interesting. It's probably the best way to learn, although you'd need some basic knowledge first to understand what you're seeing in the source of course.
One last thing I do, but it's mostly up to personal taste, is I try to avoid JavaScript whenever possible. If I can do something in CSS (IE hover effects), I do it there, that way it works even if JavaScript is disabled due to NoScript or whatever. Similarly whenever I use JavaScript in a page for something, I try to make the page work and not be broken when JavaScript is disabled. It takes a bit of extra effort and planning (sometimes you have to code the same thing twice, once server side and once client side, if you're using a server side language like PHP) but I think it's the polish that counts.