On Sunday 05 March 2006 19:51, dolphinling wrote: > Lourens Veen wrote: > > So, comment, complain, rant, flame, suggest, and I'll try and > > incorporate as much as possible. I'm not entirely happy with the > > looks of the Projects list for example, so that'll probably be > > tweaked a bit anyway, but I'm open to suggestions on anything. > > Oh, good, I'm not a hardware person either, and this is what I'm good > at. :-) > > First off, ditch the XHTML, and go with HTML 4.01 strict. You're > sending it as text/html, so the XHTML doctype has no advantages.
No disadvantages either. And sending it as XHTML (xml+html) breaks IE.
> Second, I don't know if you can turn on MultiViews on your server,
> but if you can, do. Then get rid of the ".html" extensions on all the
> links. They'll still be served properly, but if they ever need to be
> turned into directories, this way they'll still work. (And I think
> there's a good chance that, e.g., VGA Core could be turned into a
> directory.) Also, that would allow...
>
> Get rid of the file extension on the image, too. Then put an SVG
> image of the same thing as ogp_logo.svg . Any browser that requests
> SVG images over pngs will get it instead. This is good, because
> browser scaling of bitmap images is poor and you can see that in the
> anti-aliasing, or rather lack of it, in the current one.
I can configure anything I like on this server, but this won't be the
one the final site will run on. I'll look onto MultiViews though, that
sounds interesting.
As for the image, I might just make it fixed-size and be done with it. A
lot more simple, and it doesn't matter all that much.
> In the News section, get rid of the <a name="">s, and use ids
Check.
> instead. Also, wrap each post in a <div class="newspost">. And get
> rid of the <hr>s, and instead use .newspost h2{border-bottom:2px
> grove #4189ff;} or something like that.
> The logo should not have an alt text of "Open Graphics Project Logo".
> It should probably be empty (alt="") or maybe "Open Graphics
> Project". But since that exact text is already nearby, it should
> probably be blank.
I was under the impression that the standard forbade that, but I can't
find the relevant text. It doesn't make much sense to me to forbid it
either, so I guess I was simply mistaken.
> And finally, get rid of the images directory. Put images in the
> folder with the files they belong with, or if it belongs with many
> files, put it in the deepest common folder.
Which is the root. But I guess it doesn't make sense to have a separate
image directory with a single image in it either. Anyway, I didn't put
too much thought into the structure, since we'll probably need some
kind of CMS for this anyway. Given the size of the site a bunch of
static pages would be too cumbersome I think.
I've never worked with a CMS before, so recommendations are welcome.
> Oh, one other thing... I'm not sure why you put the header last in
> the source... I think I'd put it first.
http://diveintoaccessibility.org/day_10_presenting_your_main_content_first.html
I think I read it in another book on accessible web design, which is
also online somewhere, but I couldn't find it right away. At any rate,
those are the reasons.
Lourens
pgpYuF6eiBYtM.pgp
Description: PGP signature
_______________________________________________ Open-graphics mailing list [email protected] http://lists.duskglow.com/mailman/listinfo/open-graphics List service provided by Duskglow Consulting, LLC (www.duskglow.com)
