Earlier quoted context omitted.
I think the right way to do it is to have the parser figure out which words are articles rather than explicitly tagging them. There are only three of them in English, and it's not a hard NLP problem. Of course, it's harder with Chinese, where there are countless measure words. And easier in a language without articles.
I am not sure if this is misunderstanding, satire, or trying to make a point. The article tag refers to the other definition of article -- "magazine article", not "article of speech".
Show HN: Basic.css – Classless CSS Starter File
51–60 of 68 posts
Re: Show HN: Basic.css – Classless CSS Starter File
#52This feels weird. Classes exist for a reason. When I read the title, I thought about a kind of CSS reset, but what I'm seeing is also a template/grid framework? The weird part is that by wrapping an article within a section now I'm designing with columns (which btw, it seems there's no way to control them). And section > article turns out to be the suggested semantics for a blog. It's a nice effort, but what I'd look…
Seems like it would be awesome if HTML allowed you to set a default element and then use as a shorthand for You could be "classless" to the extent of being semantic and succinct but without having to misappropriate elements.
Re: Show HN: Basic.css – Classless CSS Starter File
#53One thing I consistently dislike in these efforts is the misappropriation of HTML tags with certain semantics. In this instance, the elements should not be articles: they’re not complete, standalone items. To be sure, as https://html.spec.whatwg.org/multipage/sections.html#article... says, there’s subjectivity in deciding whether to use or , but I’m content to say that is wrong here. (Last time I looked into one of t…
You're not wrong, but I'll note that the definition of you are referring to seems pretty useless, and I don't think it's wrong for people to generally decide what should mean. I don't see anywhere that defines as being used for cards. But should be used for cards if the card itself is an aside. > Here, have an article within a section. … what? That ain’t semantic. What's not semantic about that? An article =/= a page…
That's exactly how I treat cards with MVP.css. Note: "aside" doesn't mean it visually needs to be "on the side", just complimentary to the body content.
Re: Show HN: Basic.css – Classless CSS Starter File
#54Re: Show HN: Basic.css – Classless CSS Starter File
#55Earlier quoted context omitted.
11.5KB of CSS, looks like you could probably take it to under 1KB. But the biggest weight is the 93KB 460×460 avatar image which is used in a 100×100 circle. That can be reduced to an decent JPEG of about 10KB without even shrinking it to 100×100. At 100×100 (low-DPI displays), it’s under 5KB. I’d probably go for a single 200×200 image weighing about 8KB. If you wanted to make that page really fast, you’d inline all…
What network are you on that gives you 14kb packets from the internet? My loopback has MTU of 16kb, everything else is 1500 or less
Re: Show HN: Basic.css – Classless CSS Starter File
#56Earlier quoted context omitted.
You're not wrong, but I'll note that the definition of you are referring to seems pretty useless, and I don't think it's wrong for people to generally decide what should mean. I don't see anywhere that defines as being used for cards. But should be used for cards if the card itself is an aside. > Here, have an article within a section. … what? That ain’t semantic. What's not semantic about that? An article =/= a page…
> But should be used for cards if the card itself is an aside. That's exactly how I treat cards with MVP.css. Note: "aside" doesn't mean it visually needs to be "on the side", just complimentary to the body content. https://andybrewer.github.io/mvp/
Re: Show HN: Basic.css – Classless CSS Starter File
#57One thing I consistently dislike in these efforts is the misappropriation of HTML tags with certain semantics. In this instance, the elements should not be articles: they’re not complete, standalone items. To be sure, as https://html.spec.whatwg.org/multipage/sections.html#article... says, there’s subjectivity in deciding whether to use or , but I’m content to say that is wrong here. (Last time I looked into one of t…
This can be a challenge for purely classless CSS because a style can correspond to different semantics in different scenarios. For example, the cards as used in Basic.css [1] are semantically s. But in a different context, cards could be used for an [2] or for a social media post which would indeed be an [3].
[1]: https://vladocar.github.io/Basic.css/
[2]: https://getbootstrap.com/docs/4.5/components/card/
[3]: https://html.spec.whatwg.org/multipage/sections.html#article...
Re: Show HN: Basic.css – Classless CSS Starter File
#58Earlier quoted context omitted.
> But should be used for cards if the card itself is an aside. That's exactly how I treat cards with MVP.css. Note: "aside" doesn't mean it visually needs to be "on the side", just complimentary to the body content. https://andybrewer.github.io/mvp/
I still strongly oppose your use of aside there. (And it was indeed that that I was referring to in my original comment here.) Those cards are part of the flow of the document, not tangentially related to the adjacent content.
The 1st `
` talks about the movie and the `` talks about a feature/statistic related to the movie.
In mine, the main content talks about the what the library is and how to use it and `` is used to call out specific features related to the library.
In either, the "feature" content could be part of the main content or called out separately and both would seem reasonable to me.
Sure, if there was a `` element, that would be a better fit, but the definition of an `` is broad enough IMO ("indirectly related content") that feature callouts don't seem totally counter to the spirit of the tag.
Re: Show HN: Basic.css – Classless CSS Starter File
#59Congratulations on releasing this!
Re: Show HN: Basic.css – Classless CSS Starter File
#60Earlier quoted context omitted.
> But should be used for cards if the card itself is an aside. That's exactly how I treat cards with MVP.css. Note: "aside" doesn't mean it visually needs to be "on the side", just complimentary to the body content. https://andybrewer.github.io/mvp/
I still strongly oppose your use of aside there. (And it was indeed that that I was referring to in my original comment here.) Those cards are part of the flow of the document, not tangentially related to the adjacent content.