|
|
Posted by Bill on 04/21/06 19:01
What part of "No URL yet" did you miss? The site I posted is the one I
initially threw together using FrontPage and is not one I'm currently
working with, I just wanted to show what the finished page should resemble
to the group.
I guess I missed posting that I'm now using Dreamweaver 8 and not FrontPage
for the new version of the site, my bad. Dreamweaver handles css in a much
better fashion than FrontPage so I jumped to it. I do have a question why
do you think I'm fixated with IE?? It happens to be the browser I use on my
system so I naturally started with that in mind. The fact that I'm looking
into writing for a proper browser should tell you I'm not 'fixated' with IE.
Besides which doesn't IE dominate the web at the moment? If I view my stats
for the old page I see a much larger slice of the pie going to IE than to
other browsers. With that in mind why wouldn't I initially design around IE
instead of another browser. It's only after I've gotten into this a bit
that I questioned the method I was using to support IE and was looking for
alternatives.
Bill
"Beauregard T. Shagnasty" <a.nony.mous@example.invalid> wrote in message
news:_%62g.28784$az4.11064@bgtnsc04-news.ops.worldnet.att.net...
> Bill wrote:
>
> > No URL yet, the original site is www.faithecchurch.org .
>
> Ok, your first goal should be to fix the errors, which will put you well
> on your way to being a cross-browser compatible site.
>
>
<http://validator.w3.org/check?verbose=1&uri=http%3A%2F%2Fwww.faithecchurch.
org%2F>
>
> and some CSS errors and warning as well:
>
>
<http://jigsaw.w3.org/css-validator/validator?profile=css2&warning=2&uri=htt
p%3A%2F%2Fwww.faithecchurch.org%2F>
>
> > I started out with a badly botched up site and completely rewrote it
> > using FrontPage 2003.
>
> FrontPage. Your next step would be to stop using that. Probably why you
> are fixated on writing for IE...
>
> --
> -bts
> -Warning: I brake for lawn deer
Navigation:
[Reply to this message]
|