ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Frameworks & web · #sass
Learn how Sass’s @use rule isolates styles, avoids duplicate code, and lets you configure modules without forking.
Guide to adopting Sass @use with explicit namespaces, forwarding, linting, and verification for a large frontend design system.
Jeet’s <code>column()</code> mixin turns manual width calculations into a single Sass call, automatically handling gutters and nested grids. Learn how to import Jeet, set a gutter, and use <code>column()</code> for clean, fluid layouts.
Learn why @use replaces @import in modern Sass, how to set up modules, and what pitfalls to avoid. A concrete example shows single‑load behavior, scoped namespaces, and public APIs for component libraries.
Stop fighting global namespace collisions in Sass. Learn how to use @use and @forward to encapsulate styles, eliminate duplicate CSS, and build a scalable UI library entry point.
Our Hugo site is growing, and we keep hitting the same fork in the road: some features only work with the extended binary. SCSS compilation through Hugo Pipes ( resources.ToCSS ) requires the embedded Sass transpiler that ships only in the extended edition, and WebP encoding in the image pipeline is documented as extended-only as well (standard builds can de
Bootstrap 5 theming precedence The goal is to determine which theming mechanism—Sass variables defined at build time or CSS custom properties set at runtime—takes effect when both are present for the same theme token (e.g., --bs-primary). Bootstrap 5 compiles Sass variables into static CSS values, yet also exposes CSS custom properties for many tokens. Docum
jeet
bootstrap