I don't particularly like coding.
Then employ someone who does.
You are trying to do something (or at least to make use of something)
that's so technically difficult there simply isn't a good product
available to do it with: purely WYSIWYG drag-and-drop design of web
pages. You're also using a tool that's years old, thoroughly obsolete
and was infamously broken when new. This just isn't going to work.
What you'd like to do is to use a good tool to generate a good page
with little effort, and that little would be spent in working through
a GUI. You can't do this - there aren't any tools like that which are
particularly good. Most good web designers, most people reading
c.i.w.a.h, have stopped looking for them and set to doing it by hand-
coding instead.
As things currently stand, hand-coding is the way to build sites that
work cross-browser and are accesible. Using the GUI tools means a
compromise. It's not a terrible compromise - there are some open
source tools that are usable for it (try KompoZer). If you think that
paying money makes the toosl better, then you could even put up with M
$oft Expression.
Frontpage is execrable. Just don't go there.
Before you start, you need to learn some web design. There are very
few books on this that are any good, and almost no web sites. Two
pretty good books are "Head First Web Design" and "Head First HTML
with CSS & XHTML". You might argue that you shouldn't need to buy a
book (which is cheap) before you dive into using your $hundreds worth
of software. Well maybe not, but don't complain to us, we didn't
charge you for the software and we didn't write FrontPage. We just
build web sites that work, and we tell other people how to do it too.
Some people even listen.
There are issues in using your GUI design tool that aren't obvious.
The Head First books cover most of them. So even if you're not
planning to do any hand-coding, even if you're outsourcing it all to
someone else, reading these two books will make you smarter at buying
those services and will lead to a better web site.
You should also read Joe Clark's web accessibility book (free on-line)
