I've decided to learn how to make a web site. Nothing fancy, mostly text and a few GIF images, I imagine. I already own Adobde CS so I've turned to GoLive as my authoring tool.
After messing with it for a short bit I've noticed their layout grid and table sections add a lot of code and seem a bit wonky in implementation, sacrificing clarity of display in various browsers for initial ease of use. I'm sure, then, there are other elements of GoLive that also do not resolve very well into proper code. Other people posting in this forum have mentioned this about GoLive (and other WYSIWYG editors).
If I stay with GoLive what do I need to look out for and rewrite? Does anyone use GoLive just for site management while doing the actual code in something else?
I like the site management aspects of the program and the easy way to store reusable elements, but it would seem to me if my web sites don't display well then my gains of productivity are useless. I'd prefer to not start with 100% hand-coding, simply because of time, but is that the only way I'll be able to be certain of having clean code?
After messing with it for a short bit I've noticed their layout grid and table sections add a lot of code and seem a bit wonky in implementation, sacrificing clarity of display in various browsers for initial ease of use. I'm sure, then, there are other elements of GoLive that also do not resolve very well into proper code. Other people posting in this forum have mentioned this about GoLive (and other WYSIWYG editors).
If I stay with GoLive what do I need to look out for and rewrite? Does anyone use GoLive just for site management while doing the actual code in something else?
I like the site management aspects of the program and the easy way to store reusable elements, but it would seem to me if my web sites don't display well then my gains of productivity are useless. I'd prefer to not start with 100% hand-coding, simply because of time, but is that the only way I'll be able to be certain of having clean code?
