Quote:
|
Originally Posted by richkoi
Has a WYSIWYG css editor been invented yet? If not, why not? The code is simple enough, someone at Macromedia needs to get on it!
|
No they don't. Between Dr*amw*av*r and the bastardization of Allaire HomeSite (greatest text-based web editor ever, IMHO), the last thing we need is for them to get their grubby little hands into this and create the same disgusting WYSIWYG code Dr*amw*av*r is famous for.
On second thought, that might be fun too. I'd get a pretty good laugh at the dog's breakfast of code the "Macromedia Certified Developers" would pull out. Okay, I'm for this after all. Let's see what sick twisted monstrosities result from this.
The biggest advantage to CSS/XHTML that I've found is search engine optimization. If you have the right kind of layout and the knowledge to do so, you can arrange your code so that the content is loaded first (which is what the SEs are looking for), as opposed to a menu row, followed by maybe a submenu column, and then your content.
As Corey Bryant also pointed out, by putting your various styles for fonts and layout into one CSS folder, maintenance is much easier, since you're working from 1 file instead of 100. Just make sure that you keep inline styles to a minimum, so that editing is less of a hassle.
Be warned though: learning XHTML is a
bitch. You will struggle with it. You will fight with it. You will curse the existence of the various browsers. But if you stick it out, you will learn.
To flatten your learning curve a bit, I'll provide you with this piece of advice: wireframe the layout first, and then fill it in. In other words, figure out where your various sections are to be positioned, and code until you've got them the way you want them. Then fill in each of those sections after. That way, when you have a layout issue, you'll have the section of code causing it relatively isolated.