4 ms·

I agree with you, that there's a 80/20 objective here for an MVP stylesheet. However, I think wether `<aside>` is semantic HTML or not is specific to the conte

by awb 4y ago

I agree with you, that there's a 80/20 objective here for an MVP stylesheet. However, I think wether `<aside>` is semantic HTML or not is specific to the content inside it. https://developer.mozilla.org/en-US/docs/Web/HTML/Element/aside https://developer.mozilla.org/en-US/docs/Web/HTML/Element/as... > The <aside> HTML element represents a portion of a document whose content is only indirectly related to the document's main content. There's nothing in the spec saying how that tangentially-related content must be displayed. It simply says it's frequently a sidebar or call-out box. So, if a user writes semantically correct HTML and writes tangentially related content using an `<aside>` tag, MVP.css then chooses to render that visually as a "card". So, I think in this respect, it's up to the user to use the tag semantically correct or not. Or am I missing something? I think it's also semantic HTML to have more than one `<aside>`, unless I missed that rule somewhere as well. For example, in the "Little Mermaid" example (https://developer.mozilla.org/en-US/docs/Web/HTML/Element/aside https://developer.mozilla.org/en-US/docs/Web/HTML/Element/as...) the fact "The movie earned $87 million during its initial release." is written inside an `<aside>`. But wouldn't it also be valid to include a 2nd fact as a 2nd `<aside>` and then have those visually represented as cards or call outs?

d1sxeyes 4y ago
Fair point that it’s dependent on usage, but I think most uses of cards are not tangential - the cards themselves are the core content (e.g. a pricing table, feature list, real estate/product listing, etc.). I think you’re right, there’s a case that for some situations where a card contains tangentially related information, <aside> is correct, but I think the majority of cases, it won’t fit. For example, you use cards in two places on https://andybrewer.github.io/mvp/ https://andybrewer.github.io/mvp/. I don’t think either of those uses could really be described as “tangential” to the main page content (perhaps you could argue the toss for the form with suggestions).

by awb 4y ago

d1sxeyes 4y ago

Fair point that it’s dependent on usage, but I think most uses of cards are not tangential - the cards themselves are the core content (e.g. a pricing table, feature list, real estate/product listing, etc.). I think you’re right, there’s a case that for some situations where a card contains tangentially related information, <aside> is correct, but I think the majority of cases, it won’t fit. For example, you use cards in two places on https://andybrewer.github.io/mvp/ https://andybrewer.github.io/mvp/. I don’t think either of those uses could really be described as “tangential” to the main page content (perhaps you could argue the toss for the form with suggestions).