Clavius is NOT down

[JayUtah]

There was a delay in processing the domain name registration and so the DNS entries are temporarily disabled. This should be cleared up relatively quickly.

[JayUtah]

Here is the temporarily link: www.xmission.com/~jwindley/

[JayUtah]

DNS is now working for me. Let me know if you can't get to it.

[Glom]

Didn't even notice it was gone. I notice the code is looking kind of old now. Any plans to update to XHTML and CSS?

[JayUtah]

I lit a fire under my provider and DNS was only unavailable for a couple of hours.

I'm working on CSS. But I don't want to add "glitz" for its own sake. The CSS is just to make the coding easier on new pages.

[LunarOrbit]

CSS is so helpful; it really does save a lot of time and effort in the long run.

[Glom]

Since it is also the w3c recommendation, it means Clavius will be universally accessible.

[JayUtah]

I came to the conclusion about a month ago that CSS was the "right" way to do the site. And it's quite clearly then the best choice in the long run. The problem is that the site already has a lot of content, so the "long run" has probably already been mostly run. If you come up with a good design innovation on Item 99 of a 100-item production run, you don't necessarily want to go back and rebuild the other 99 items.

But rest assured that the site will convert to CSS. It's the best way, the right way, and it's just darn cool too!

[PhantomWolf]

I'm doping mine with CSS, welll whenever I get around to doing a little more. I'm rather slow at it really, lol. Need to get the research going instead of wasting so much time on forums.

[Glom]

I don't think I've noticed a change to the Clavius template since I first saw it four years ago (which isn't surprising since there is no css). And it does look fantastic so the cliche applies. Therefore the need to convert for the sake of convenience is not really there.

For my site, it was a no-brainer to convert to css because I was still working on the look (and still am) and it makes it easier to change things. In fact, I wrote my latest template (the one modelled on Clavius) specifically to allow the most control possible from the stylesheet.

I still think that compatibility is an important reason though. You don't want to fall behind. Aulis use some css, though in a stupid way. Take a look at their validation.

phantomwolf said:

Need to get the research going instead of wasting so much time on forums.

(Almost) everything you wanted to now about css.

One note though: when doing images and tables, the "align" attribute, which you use to nest them in the text neatly has been deprecated and the css attribute is "float". eg

style="float:left"

If you say wanted the image or table to sit in the text on the left. For centering, you need to use margins.

style="margin:0 auto"

Why should I randomly offer this, you ask? It took me ages to find it out because it is buried randomly in the tutorial. It was annoying because when I was converting the site, there were some pages I couldn't do completely because I was still looking for it.

[papageno]

glom said:

For my site, it was a no-brainer to convert to css because I was still working on the look (and still am) and it makes it easier to change things. In fact, I wrote my latest template (the one modelled on Clavius) specifically to allow the most control possible from the stylesheet.

I used CSS from the start, because that's what I learned in my very brief introdution to HTML at the university.

glom said:

Why should I randomly offer this, you ask? It took me ages to find it out because it is buried randomly in the tutorial. It was annoying because when I was converting the site, there were some pages I couldn't do completely because I was still looking for it.

That's why I use a quick reference sheet.

[PhantomWolf]

(Almost) everything you wanted to now about css.

I already use www3schools for most of my webprogramming. I was meaning my research for the information on the webpage, not for the CSS. ;P