181–190 of 192 posts
Earlier quoted context omitted.
I would like these themes to go beyond a simple article view. We have tags like , , , , and now. Should be possible to build a complete app-shell with classless CSS.
As an exercice, I’m building my neighborhood newspaper website without any classes. It is surprisingly easy. With Grid and min(), I don’t even need media queries. CSS and HTML in 2020 is great, if you take the time to choose only the latest solutions.
Just to point out there are also: https://native-elements.stackblitz.io/
This Github repository tracks a whole bunch of these drop-in CSS files: https://github.com/dohliam/dropin-minimal-css And you can use this demo site to switch between them all on the fly: https://dohliam.github.io/dropin-minimal-css/
Pity I cannot just receive vanilla mark up and pick a client side theme.
HN is pretty vanilla. I use it with https://userstyles.org/styles/92693/dark-hacker-news-solariz...
Not the standardized approach that we should have had long ago but better than nothing.
Earlier quoted context omitted.
I'm pretty sure firefox has this feature. the problem is no website offer custom css. for an example: https://stackoverflow.com/questions/48227413/what-is-the-pur...
Seems Firefox doesn't remember the CSS you have selected (i.e. per page? per domain?) I can think of some uses for this if it were sticky - high contrast and dark mode versions for websites
I don't understand the claims re: font loading. > Vercel's impossibly fast CDN delivers new.css and the font Inter using xz/fonts, so there's virtually no bloat added to your pages. It's 300kb of font downloads, hardly light. And the xz/fonts page says: >Break your users from unethical tracking networks I'm still making a request to a 3rd party CDN with an origin header that says what page I'm looking at, so I'm not…
You can always set a referrer-policy HTTP header on the origin site to prevent the CDN from getting the path (or even the domain) of the web page. They’d still see user IP address but on its own that’s not very useful.
Earlier quoted context omitted.
Thanks! Does anyone know how these stylesheets interact with other frameworks like bootstrap? If I want to use bootstrap in a website, can I still start with one of the above as the base style?
It might be an interesting question to ask why bootstrap couldn’t be mostly classless. I remember learning Bootstrap and thinking it was silly I had to add class=table to a table.
Any frontend dev out there would like to compare this with MVP and Tachyons? I am a bit lost when to pick over another.
By contrast (and not having used it) new.css seems to provide some basic styling to give some elements like input or summary a certain look which you may or may not like. New.css seems like a very lightweight (CSS-only) Bootstrap framework. If you don't like the specific look (including colors and margins) the designer chose for you, there is apparently no easy way to change it or go beyond it -- other than by the usual mechanisms of writing more CSS.
I like the Atomic CSS approach because, for what I do (mainly single-page apps) I just write JavaScript which generates HTML which is almost-entirely styled using existing Tachyons classes (which never collide). By contrast, most other CSS libraries (such as apparently new.css) expect you to write new CSS styles for HTML elements and also semantic CSS classes (e.g. .main-content) if you need something other than exactly what they provided, and so you have to be managing multiple stylesheets and their collisions.
See also: https://css-tricks.com/lets-define-exactly-atomic-css/
Any frontend dev out there would like to compare this with MVP and Tachyons? I am a bit lost when to pick over another.
Tachyons, which I like a lot, is Atomic CSS, which means essentially things do what they say, like .red makes things red, or .ma0 sets a margin of 0. With Tachyons, you can define any look you want by adding these atomic styles to HTML elements. While that might be a lot of work if you style HTML by hand, it is not much of a chore if you are writing JavaScript code which defines widgets which you use by calling a fun…
Earlier quoted context omitted.
I doubt it would work well but you could put a theme in user.css (on Firefox) and block all .css files (with uBlock, say). Not sure if uBlock will block tags, but I think it can.
I think user.css automatically overrides any remote CSS, doesn't it?—so no need for blocking.
This recent vibe of minimal CSS files for plain HTML tags feels the same as the CSS Zen Garden from years ago. Which is very good and quite welcome in the current state of overbloated JS frameworks that do everything. I wonder if this will also drive further the adoption of standard web components https://open-wc.org/guide/
Definitely got me Zen Garden vibes.