Sobral

`aspect-ratio` isn't a hack, but a standard CSS property. I can't see a reason for consider it a tip.

LibSass is behind DartSass.

Not at all! [Take a look!](https://github.com/oficiodesign/initial-css/blob/release/next/stylesheets/abstracts/_index.scss) ```scss @use 'config'; @forward 'config'; @forward 'functions' with ( $my-base-url: config.$base-url, $my-breakpoints: config.$breakpoints, $my-font-weights: config.$font-weights, $my-gutter: config.$gutter, $my-palette: config.$palette, ); @forward 'mixins'; ``` ---...

Ops! I'm sorry. I misunderstood your question! I use them this way: ```scss .foo { @include my.exposed-mixin('bar'); } ```

I chose `my` because I was talking to a PERL developer at the time. I just wanted to feel how would be to code using the namespace idea on my...

I came to the conclusion that to use a namespace is absolutely necessary, to avoid making a mess with new CSS features, like `image-set()`.

Should we bring this back to life?

We're discussing possible and necessary updates to the guidelines, @bjankord .

I came here to open an issue and... I already did! --- I'm testing things. If I came to a conclusion, I come back and tell you!

Hey, big boss! Remembering the current recommendation: - `abstracts/`: - `_font-stacks.scss` - `_mixins.scss` - ... - `base/` - `components/` - `layout/` - `pages/` - `themes/` - `vendor/` - [`index.scss`](https://sass-lang.com/documentation/at-rules/use#index-files) The...