BTW, closing the top <div> at the end of <span> is awkward to read because one does not know that the <div> has been closed without scrolling the code box and looking for it. Indented tags, just like indented CSS, is waaay easier to read.
Did you understand the part about the parent - child relationship? That’s my response to your question.
The bit about indented tags, especially those with inline styles, is an “extra” tidbit that I threw in. Look at your own screen and think about what I have very briefly described. It’s easier and cleaner to scroll vertically to see the code than it is to have to scroll horizontally to see code that is hidden offscreen (or out of the box, in the forum) to the right. Uniformly indented code, one level per indent, is a treat to read compared to the stuff that a lot of CMS’s churn out. I’m just rambling.
Sometimes ronpat gives in too easily. Initially, I said that a semantically appropriate block tag would be appropriate, but you weren’t interested, so … what can I say.
Knowing only what you’ve told us about a web page that has only a side bar as its content, <div> for the outer element and <p> for the inner element would be my choices.
You play it very “close to the vest” as we say which makes it tough to guess the context.
But then I’d be putting all this code into div? You said it didn’t look good like that? font-family: New Times Roman; font-size: 20px;color: #0059dd;line-height