Are you a Google Analytics enthusiast?
More SEO Content
Posted 18 February 2005 - 09:56 AM
I am checking
I have set my site to html 4.01 trans' as you can see, is this the correct doc type for a starters? im sure it is..
Altho i have 17 errors it seems that i only have 2 little areas to tidy and they both seem to belong to frontpage, i,e borders and navigation. These are items that I cant seem to get control over to correct..
What should i do? Just validate as much as i can or are we supposed to make it perfect?
Posted 18 February 2005 - 11:19 AM
The errors you are getting are all pretty easy to fix, so I can't think of a reason for not doing so.
1 & 2: Seems to me that you can just remove those tags. They are FP proprietary, so the validator isn't going to recognize them no matter what you do.
11 - 17: There is no < nobr > element in HTML 4 (this is an IE-only element), so if you want this page to validate cleanly, it will need to be removed
Personally, I am a bit of a perfectionist, so I would take it as far as I can.
Posted 18 February 2005 - 11:36 AM
simple fixes...just a matter of if you want to take the time to open up note pad. it can't hurt...it can only help.
Posted 18 February 2005 - 01:52 PM
Posted 18 February 2005 - 02:24 PM
Posted 18 February 2005 - 02:35 PM
Not true. As long as you don't use those MS-exclusive doodads, like shared margins or themes, there's no reason an FP site can't validate.
Posted 19 February 2005 - 05:35 PM
It actually seems like i am stuck with it as it is. Sweepthelegmate suggested just editing in notepad, that was sensible but i tinker a lot with the contents so FP overwrites each time of course..didnt really know they were 'exclusive' as such.
Posted 19 February 2005 - 05:55 PM
Just create pages that look like the borders and throw them into the pages as included content.
Posted 19 February 2005 - 06:36 PM
FP Includes, technically, don't require the server extensions, Bob.
Unlike SSI or PHP includes, FP Includes aren't activated by client request, but rather occur when the designer publishes the site to the server. What is sent to the server is the full document, with all the includes already included. That's why a change to an includes means you have to re-publish the whole site (or at least all files affected by the include) and not just the include.
You DO need FP Extensions loaded on the server to publish to it, however. The trick, then, is to NOT publish to the server, but instead, to a directory on your local hard disk. Click File/Publish Web and, rather than entering a http address, type in a local destination, like c:\sitename. FP will publish locally (no server extensions required!), which will also assemble all your Includes, and you can then FTP the results to the server.
FrontPage Includes can be extremely handy. Shared Borders, on the other hand, are evil.
Posted 20 February 2005 - 07:11 PM
Thanks for your thoughts guys
.... why are they evil?
Posted 20 February 2005 - 09:46 PM
Posted 21 February 2005 - 07:11 AM
But they are from MS, so the horns are implicit, even if you can't see them
Posted 25 February 2005 - 10:35 AM
Must admit to being a Git and im not really interested in the 0.2% of people that try to view my site with something other than MS stuff anyway lol
Usually the geek as oppose to the corporate businesses dont you think? :-)
Posted 25 February 2005 - 11:02 AM
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users