21–30 of 68 posts
The cards of this one look neat, but in case I need something like that I would add it myself to concrete. Nice place to start never the less.
One 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…
> One thing I consistently dislike in these efforts is the misappropriation of HTML tags with certain semantics. As a counterpoint, I don't understand people pushing strict semantics in html elements where they're not really strictly defined or generally useful. Because of how loose the spec with how these things can be used (it it weren't it'd be like schema.org meets html) scraper and other UI tools don't really lo…
[1] https://golang.cafe [2] https://github.com/yegor256/tacit [3] https://tailwindcss.com
One 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…
> One thing I consistently dislike in these efforts is the misappropriation of HTML tags with certain semantics. As a counterpoint, I don't understand people pushing strict semantics in html elements where they're not really strictly defined or generally useful. Because of how loose the spec with how these things can be used (it it weren't it'd be like schema.org meets html) scraper and other UI tools don't really lo…
I do like these frameworks. Far more sites should use one of those or the principle behind them. My page [1] uses concrete [2] and has a page load of 125kb (including my picture) and loads in less than one second. I don't need all that bloat that comes with a lot of pages (checkout wired.com for a negative example). The cards of this one look neat, but in case I need something like that I would add it myself to concr…
Imagine what you could get it down to if you just wrote CSS instead of using a framework.
Quick recommendation: add a focused style on form inputs so it's easy to see which input is active. A bright border color would help.
A great tip was to use an appropriately colored shadow for focus and errors in the forms. It improved legibity a lot.
One 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…
> One thing I consistently dislike in these efforts is the misappropriation of HTML tags with certain semantics. As a counterpoint, I don't understand people pushing strict semantics in html elements where they're not really strictly defined or generally useful. Because of how loose the spec with how these things can be used (it it weren't it'd be like schema.org meets html) scraper and other UI tools don't really lo…
The effects of the semantic abuse are admittedly slight, but they are still present, so all else being equal you should care at least a little about them. Tools like screen readers do distinguish between section, article and div in their landmark handling. By abusing these things, you are making life just a little bit harder for users of screen readers.
- https://github.com/dohliam/dropin-minimal-css
This 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.