/* define layer order. Not necessary here */
    @layer pico, nils;

    /* import framework into layer */
    @import url("pico.css") layer(pico);

    /* define own styles in own layer, they have precedence. CSS vars are still global. */
    @layer nils {
        p:first-of-type {
            color: green;
        }
    }

Its almost never all you need for an actual project, but it is a nice starting point to get the basics in place.

I find that I look at the endless list of classless stylesheets shared online as a starting point, most have at least one or two interesting tricks worth borrowing. I don't find using the off the shelf ones particularly useful though, it ends up with a very generic look to it like the old default bootstrap site or newer default tailwind site.

Like w3, the makers of the web accessibility checklist have a flash-bang of a website and noone appears to have cared enough to fix it

It's not that complex, there's some minimal frameworks here with 10kB of css code, it's ironic.

I was very curious for the reason and I found it. Cssbed is not hosting css files but loading upstream css and https://vanillacss.com/vanilla.css has been hacked/hijacked, so no css is being loaded but HTML full of crap.

I thought if request origin or content-type was stylesheet no href GET should be triggered (maybe src) but looks like full HTML site is being rendered behind the scenes of a simple css request.

For small/alternative stuff, since nesting/has()/ field sizing and such is native now there's not much to do there, so what's mostly relevant is some classless sheets like what this article is about.

CSS in JS is also still a big thing.

Edited to add: it's not classless though. Marx would disapprove.