Material Components Web VS Sass

https://github.com/firebase/firebase-ios-sdk/issues/6115

https://github.com/material-components/material-components-w...

Two examples that come to mind but there are plenty

I highly recommend https://github.com/material-components/material-components-web

Latest stable version: v12.0.0 Github stars: 15.7K Development: active Long of active development: 8 years Active maintainers: 2 Contributors: 380 Number of commits: 6835 License: MIT Used by: 6K Github projects Git repository: https://github.com/material-components/material-components-web

Material design by Google

One other thought: have you tried vanilla JS plus a widget library such as Material Design Web? It might be good to get more comfortable with vanilla JS, using fancy widgets only where needed, and then later when you consider using a framework it will be that much easier to learn and work with.

First off, for your issue, I think it's very helpful to learn design and layout from a design system like Material.

One interesting thing to note about this example is the use of @material/mdc-auto-init which will auto initialize all your material components instead of manually having to attach to each one. That should make it easier with working with the dom.

Today I've managed to scratch-build Material Design's top app bar, in particular its behaviour of sliding up/down if the user scrolls down/up, without relying on libraries like Material Components Web or Material-UI.

SASS(.scss) [ https://sass-lang.com ]

Traditionally CSS lacked features such as variables, nesting, mixins, and functions. This was frustrating for Developers as it often led to CSS quickly becoming complex and cumbersome. In an attempt to make code easier and less repetitive CSS pre-processors were born. You would write CSS in the format the pre-processor understood and, at build time, you'd have some nice CSS. The most common pre-processors these days are Sass, Less, and Stylus. Any examples I give going forward will be about Sass as that's what I'm most familiar with.

CSS stands for Cascading Style Sheets, and is a scripting language used to style web pages. SCSS stands for Syntactically Awesome Style Sheet, and is a superset of CSS. You can think of SCSS as the more advanced version of CSS, which comes with several features that CSS does not support, such as the SCSS nested syntax, as shown below.

Scss

In the past, you’d need to rely on pre-processors such as SaSS or Less, but not anymore… Native CSS nesting has landed on all major modern browsers.

Sass is also a css preprocessor. Op is likely confused

sass -> An improvement over CSS. It provides nice features for managing CSS. good for mid-sized or even larger projects.

Sass (Syntactically Awesome Style Sheets) - A CSS preprocessor that simplifies and enhances your CSS workflow. Website: https://sass-lang.com/

Personally, my preference is Sass: I find that the mixins, partials, and operators are hugely useful when it comes to creating re-usable snippets of code for a design system. And, since it’s “just” a pre-processor and not a framework, it’s not opinionated in a design sense and there’s no default values (colors, spacing values, etc.) that will need to be overwritten.

Preprocessors: SSGs leverage preprocessors to streamline the development process. Preprocessors like SASS for CSS or Babel for JavaScript offer additional features and simplify code development.