gouri - 4:55 pm on Nov 10, 2013 (gmt 0)
What that means is within a <p> that contains a list of "things" it's better for source-code semantics to code it as: <p>Some text </p><ul><li>item 1<li>item 2<li>item 3</ul><p>Some other text</p> rather than coding the whole thing as a <p>.
If I was coding a list that contains single words for item 1, item 2 , and item 3, I think that I would code it as you have. Some text within <p>...</p> to introduce the list, then the list coded as you have it, and then some text within <p>...</p> after the list to maybe summarize what I just wrote in the list.
If you have several sentences for each <li>...</li>, however, instead of 1 word, would you code it the same way?
It's common to think of lists only in terms of
but there are situations where you really want a semantic list structure even though the individual items are quite long, up to multiple paragraphs.
That is what I am saying. Sometimes, the individual items are more than a word or two, and in those situations, how would you code it?
What you wrote about which rule takes precedence when coding is something that I think will come up when I code the list that I mention in this thread, but it is going to take me a little time to understand it. Your examples really help.