|
|
Posted by sorry.no.email on 11/23/85 11:43
Hi Andy Dingley,
Thanks very much for your comments on the site I am converting to
XHTML. The address has moved an inch to:
http://people.aapt.net.au/~adjlstrong/
I have addressed your very helpfull comments below:
On 27 Mar 2006 08:14:50 -0800, "Andy Dingley" <dingbat@codesmiths.com>
wrote:
>sorry.no.email@spamsux.com wrote:
>
>> I am converting my father's family history over to XHTML from a very
>> daggy frames look.
>
>The whining noise you can hear is the Geek Chorus telling you that
>XHTML is evil and you shouldn't use it.
>
>Hey, it's your call. But there's little benefit to it (for this sort of
>site) and you should only do it after reading some of the past debate
>here and in c.i.w.a.h and reading Appendix C. Otherwise just ignore
>it! - you're doing OK so far.
To tell you the truth I am having a great time and learning a lot as I
go. This is incentive enough for me, especially as this site is not a
commercial one :-)
>
>
>> Can someone please look at the first page and see if I am on the
>> right track?
>
>The nav list on the left is a list, so mark it up as one, not just a
>sequence of <p>s. Use CSS to turn off list bullets etc., if you wish.
>If you need to use "anonymous text blocks" like this, then <div> is
>arguably a bit better than <p> (if you can't really say "This is a
>paragraph" about a small fragment)
I have put a list in place that I took from Listamatic. I noted on
their other pages:
http://css.maxdesign.com.au/listamatic2/index.htm
there were nested lists. Now I love the simple list I have found.
Surely this can be converted to a nested list?
>
>You aren't setting the background color or a default color on the body.
>This becomes more obvious when the background image fails to load (as
>it does just now).
I have lost the image and set a background colour, white for the
moment.
>
>Lay off the "font-size 85%". Leave body text size at _my_ default
>choice, not yours. Or else lend me your screen and eyeballs to read it.
>
>Equally don't mess with line-height. It's rarely a good idea to do
>this.
Line height has gone and I did not miss it Iwill admit. Font
percentages I have mostly lost although I have made the navigation bar
95% to differentiate from body text; I am still considering this one
though.
>
>Consider setting the <a> elements in the body text to display with a
>line break before them. If you're making the URL visible in the text
>like this (OK if that's what you want, or you want it to be visible
>when printed) then it looks best if they're either all in-line, or all
>line-broken beforehand. Stick a <br /> in before them, or else put a
>class on each one and use some CSS
>a.visible-url { display: block; }
Thanks for that one, I have implemented it and it is brilliant!
>
>Take a look at BlueRobot.com, glish.com etc. for some advice on getting
>multi-coloumn layouts to behave themselves across different browsers.
>it's not obvious or easy to do this well (OTOH it's easy to copy a good
>example). Macromedia are clueless here (as ever!)
Thanks for the tip! I have taken the header from BlueRobot and intend
to modify this a little for the site. I will admit to not fully
understanding all of his comments in the CSS so I have left them
intact until I am a little wiser :-)
>
>Instead of WEDEMEYER use <span class="surname" >Wedemeyer</span> and
>the CSS
> .surname { text-transform: uppercase; }
Sound great but to tell the truth all my text arrives in an MS Word
document with the cases already set in place. But I shall store this
one away for future reference.
>
>Linking placenames to the Getty Thesaurus (TGN) can be worthwhile for
>genealogy - there are a lot of "Newcastle"s in the world.
>
>
>Overall though, it looks fine. Keep us posted as it develops.
Thanks very much for your very constructive and highly useful
comments!
Andrew.
Navigation:
[Reply to this message]
|