19/09/2005: On Custom DTDs

Dylan Parry wrote:

Of course, but validating against a custom, non-standards controlled DTD is a complete waste of time for HTML. That would be validation for validation’s sake. If you can’t validate against a recognised doctype then there is truly no point in attempting to create your own to cover your problems

Using a custom DTD can be very useful.

19/10/2003: On Web Design

local wrote:

Now I wonder how important cross-browser coding actually is. How many browsers do I have to test, which versions?

I have two philosophies on this question.

The first is the philosophy I apply when making my own website — I stick to the standards and let any browser that can’t handle it be damned. If 99% of browsers don’t work on it, that’s fine by me. (OK, so I have added a few little workarounds for IE6, but nothing major)

The second philosophy is similar and is what I use for other people’s websites. Again, write to standards, but make sure it works more or less perfectly in:

IE 5+ (Windows)
Netscape 6+
Opera 7+
Konqueror

and make sure the content is readable and the site is navigatable in:

Netscape 4.x
IE 4 (Win)
IE 5 (Mac)
Opera 5+
Lynx

Now, the best way to do this, is to follow my smiple (sic) 7 point design
procedure:

1. Content

Start with the content. It may be cliche to say so nowadays, but content really is king.

2. Markup

Mark up the content…

Articles Tagged with "Validation"

19/09/2005: On Custom DTDs

19/10/2003: On Web Design

1. Content

2. Markup