I have a few pages here ready for y'all to look at and critique. I would appreciate comments on the accuracy of the information as well as readability.

Please remember I set out to meet certain goals and cover a limited number of topics. Those goals and topics are outlined in my previous post in this thread. I am not prepared to expand the goals and topics but I would like opinions on whether I've accomplished what I set out to do and where it could be polished a bit more.

The HTML standard is stuck somewhere between 2.0 and 3.1 which sucks but it will do for now.

Didactylos, if you would like to incorporate my pages into a site you're working on then please feel free to use whatever I've written. Link to it, swipe bits and pieces or swipe entire pages. It's all public domain, no acknowlegemnts required. The intention has always been it should become part of a larger work and I simply don't have the facility to host such a work myself. Nor will I in the future.

I am not familiar with CSS as you can tell and I don't really want to get too familiar so if you already have a style sheet in the works then let me know and I'll incorporate it into my pages if that fits with your longterm plans.

Thanks for those hints, Sekerob. I will make appropriate revisions soon
In the meantime, the finally came on regarding CSS. I think I'm going to like it a lot!

And my goodness HTML has come a long way since I last played with it! We have classes now.

OK, there'll be some big changes in the look of my pages soon, for anybody who saw the plain Jane version.

You have some nice clean html there. All you need to do is include the DOCTYPE and take out the deprecated tags, and it's a thing of beauty.

Brief CSS tutorial (for others as well as you, Dag)

CSS can be applied in several ways. The best way is to change the formatting for all the tags. For example, you can centre your headings using

h1 { text-align: center; }

You can make things clearer by applying a formatting style to lots of tags, for example

body, p, th, td, li { font-family: Arial, Helvetica, sans-serif; }

Use classes only for situations where you have several elements that use the same style, but not the default. Add the class="myclass" attribute to the element, then define the class:

.myclass { ... }

If you have a style for a single element, either use the id or the style attribute. (Details omitted for clarity.)

Finally, you can do really clever things with nesting. For example, suppose you have a navigation bar, and you have cleverly opted to create it using an unordered list. Instead of dumping a class attribute on every single li element, add it to the ul element. Then, use this syntax to specify a format for all the li elements within that list:

.myclass li { ... } /* note the space instead of a comma */

Translates perfectly here, it. (synthetic as opposed to syntactic)

Didactylos, thanks for the h1 {text-align: center}. I just couldn't get it.

I stumbled across a stylesheet that implements a navigation bar using what I think is the same method you posted above. I've incorporated it and Sekerob's suggestions into my pages.

This is the CSS I found:

body {
padding-left: 11em;
font-family: Georgia, "Times New Roman", Times, serif;
color: #AADEA9;
background-color: #358333 }

ul.navbar {
list-style-type: none;
padding: 0;
margin: 0;
position: absolute;
top: 4em;
left: 1em;
width: 9em }

h1 {
font-family: Helvetica, Geneva, Arial, SunSans-Regular, sans-serif;
text-align: center }

ul.navbar li {
background: #AADEA9;
margin: 0.5em 0;
padding: 0.3em;
border-right: 1em solid black }

ul.navbar a {
text-decoration: none }

a:link {
color: blue }

a:visited {
color: purple }

How do we control line width and/or the right margin? My lines all run up against the right side of the screen. The TABLE used to be the way to do it, does 4.1 have a better way?

Quick clarification -

96% of results that are ever returned are returned in the first 4 days. However, somewhere around 6-9% (rough estimate - I would need to look this up to give you a precise number) are never returned. Those results that are not returned cause much longer delays in validation.