aos VS Sass

Thank you. The template I bought is using the AOS library. It was a bit challenging to make it work with the App Router, feel free to check my code on how to implement it.

If you’re having trouble seeing the article content, this is the relevant issue:

https://github.com/michalsnik/aos/issues/541

Are you referring to animate on scroll? You can use this library: https://github.com/michalsnik/aos

It's been brought up before: https://github.com/michalsnik/aos/issues/571

I really recommend reading the Github readme or documentation when using a package or library if you hadn't already. (https://github.com/michalsnik/aos)

thank you! not sure which animation you mean but i used the Animate on Scroll to animate them https://github.com/michalsnik/aos

Thanks man, I’m using AOC to do this animations: https://github.com/michalsnik/aos

Maybe https://github.com/michalsnik/aos/issues/574 will help you

Turns out i deployed with vercel and animate on scroll is not working (https://github.com/michalsnik/aos) im thinking it might be a server side rendering issue? Anybody else use this library in conjunction with next.js and might have a solution?

to ourindex.js file. You can also add additional configuration options to the AOS.init() call. See the AOS docs for details.

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.