Re: Just getting started on the FAQ site...
- From: Joe Wakefield <joew5.20.joewakefield@xxxxxxxxxxxxxxx>
- Date: Sat, 31 May 2008 17:18:04 +0100
On 31/05/2008 17:04, John Prentice wrote:
Josiah Jenkins wrote:An amazing job in such a short time !
Congratulations but, . . . my envy knows no bounds !
Many thanks! Standing on the shoulders of giants, of course - it would have been utter pain without a CMS to take a lot of the load.
Out of curiosity, I threw the URL at W3C Markup Validation.
One error only . . .
If you just heard a wet slappy sound, it was my jaw rebounding off the worktop! I'm amazed and delighted: I'd assumed the generated HTML would be so non-conformant that it wasn't even worth putting through the validator.
> I don't know what experience you have of doing a fairly major siteusing 'pure' HTML but it can take *weeks* of work to get it right !
Lots...and you're completely right. I find that using syntax-highlighting editors does help. The other thing that helps is putting the W3C validator button at the bottom of the page. If I break the HTML later, someone's bound to tell me!
John
I've found that the "Web Developer" add-on to Firefox is *very* useful for doing quick checks on validation and finding where problem are.
--
Joe
Wakefield
.
- Follow-Ups:
- Re: Just getting started on the FAQ site...
- From: John Prentice
- Re: Just getting started on the FAQ site...
- From: Josiah Jenkins
- Re: Just getting started on the FAQ site...
- References:
- Just getting started on the FAQ site...
- From: John Prentice
- Re: Just getting started on the FAQ site...
- From: Don Aitken
- Re: Just getting started on the FAQ site...
- From: Josiah Jenkins
- Re: Just getting started on the FAQ site...
- From: John Prentice
- Just getting started on the FAQ site...
- Prev by Date: Re: Just getting started on the FAQ site...
- Next by Date: Re: The enigmatic family of William Stewart Reed
- Previous by thread: Re: Just getting started on the FAQ site...
- Next by thread: Re: Just getting started on the FAQ site...
- Index(es):