Re: [css-d] *argh* listitis.....!?!?
Eric Shepherd wrote: Also, there's no relationship right now between your top nav bar and the subnav - if the subnav is related to HOME, for example, it should be a nested list (ideally) or less ideally have some sort of heading that identifies it as a subnav. If I look at the page non-styled, the subnav simply lines up as list items following the upper nav, so it appears to be at the same hierarchy. Eric Thank you for all your advice I have taken it all on board. http://24.m-corp.com/ID08_venueDetail.html Re; the topNav and subNav, and subNav being a sublist of topNav - I totally agree and really want to do this. The trouble is I'm really struggling to make it work in the two horizontal lists as they are visually. Do you know of any examples that I could follow and learn from? Thanks again. Kristina __ css-discuss [EMAIL PROTECTED] http://www.css-discuss.org/mailman/listinfo/css-d List wiki/FAQ -- http://css-discuss.incutio.com/ Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
Re: [css-d] *argh* listitis.....!?!?
I don't have time to write about this menu now, and I barely remember making it, but you can check out www.creeksidebanquet.com, and my article on A List Apart, at www.alistapart.com/articles/hybrid/, though it has an extra layer of complexity you don't need. Write me privately if you have questions about these, and I'll respond when I'm not at work. On 9/21/05, Kristina Floyd [EMAIL PROTECTED] wrote: Eric Shepherd wrote: Also, there's no relationship right now between your top nav bar and the subnav - if the subnav is related to HOME, for example, it should be a nested list (ideally) or less ideally have some sort of heading that identifies it as a subnav. If I look at the page non-styled, the subnav simply lines up as list items following the upper nav, so it appears to be at the same hierarchy. Eric Thank you for all your advice I have taken it all on board. http://24.m-corp.com/ID08_venueDetail.html Re; the topNav and subNav, and subNav being a sublist of topNav - I totally agree and really want to do this. The trouble is I'm really struggling to make it work in the two horizontal lists as they are visually. Do you know of any examples that I could follow and learn from? Thanks again. Kristina __ css-discuss [EMAIL PROTECTED] http://www.css-discuss.org/mailman/listinfo/css-d List wiki/FAQ -- http://css-discuss.incutio.com/ Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
[css-d] *argh* listitis.....!?!?
Hello list I'm concerned that i've got listitis!! What I mean is, I think I've gone from div-itis to li-stitis. Please can you tell me if the information on this page is a list? http://24.m-corp.com/ID08_venueDetail.html In general is the information on that page semantically correct? How can I check this? If you are interested in seeing any of the other pages in this prototype please go to http://24.m-corp.com/ Is this something other people are finding, 'that everything is a list'? Is this true, or are we in danger of going crazy with lists? (I want to try and get a better handle on this, before I've got a ga-zillion websites that will need re-doing, in the not so distant future) Thanks Kristina __ css-discuss [EMAIL PROTECTED] http://www.css-discuss.org/mailman/listinfo/css-d List wiki/FAQ -- http://css-discuss.incutio.com/ Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
Re: [css-d] *argh* listitis.....!?!?
Kristina wrote: I'm concerned that i've got listitis!! What I mean is, I think I've gone from div-itis to li-stitis. Kristina: I think much of the content on your page is lists. However, the Venue Detail is not really a list. I would suggest that this information is really a definition list - you have a parent term - the venue - with children definitions or data about the venue. dd definition tags also allow block-level content, so you can put paragraphs in there, for example. Also, there's no relationship right now between your top nav bar and the subnav - if the subnav is related to HOME, for example, it should be a nested list (ideally) or less ideally have some sort of heading that identifies it as a subnav. If I look at the page non-styled, the subnav simply lines up as list items following the upper nav, so it appears to be at the same hierarchy. There's no way to check for sure whether your markup is correct. But rest in the knowledge that there really aren't THAT many HTML tags...think about what the content really IS. In the case of your nav, the secondary nav is (I think) hierarchically nested in the first nav, so build it as a nested list and then style it to position where you want. In the case of lists, think about whether each of the items in your list could be shuffled around without losing meaning. To me, Lighthouse, Poole needs to be at the top - it's the parent, and the rest is just meta data about the venue. So, a dl definition list makes more sense to me than making it equivalent to the other list items. __ css-discuss [EMAIL PROTECTED] http://www.css-discuss.org/mailman/listinfo/css-d List wiki/FAQ -- http://css-discuss.incutio.com/ Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
