2020-02-17
2809
#css
Supun Kavinda
14066
Feb 17, 2020 â‹… 10 min read

The definitive guide to SCSS

Supun Kavinda I started as a self-taught PHP developer before creating my own company, Hyvor. I am particularly interested in physics and machine learning.

Recent posts:

RAG vs. Fine Tuning, A LogRocket Article

Fine-tuning vs. RAG: Which AI strategy fits your frontend project?

Compare fine-tuning vs. RAG to design faster, smarter, and more responsive AI-powered frontend experiences.

Ikeh Akinyemi
Jun 16, 2025 â‹… 8 min read
7 Common CSS Navigation Menu Mistakes And How To Fix Them

7 common CSS navigation menu mistakes and how to fix them

Navigation menu errors are common, even for seasoned developers. Learn seven common navigation menu errors and how to solve them using CSS.

Temitope Oyedele
Jun 13, 2025 â‹… 6 min read
Comparing the top 5 React toast libraries

Comparing the top React toast libraries [2025 update]

Compare the top React toast libraries for when it’s more trouble than it’s worth to create your own custom toast components.

Nefe Emadamerho-Atori
Jun 13, 2025 â‹… 16 min read
Comparison between TanStack Start and Next.js — two modern full-stack React frameworks with different architectural approaches.

TanStack Start vs. Next.js: Choosing the right full-stack React framework

TanStack Start vs. Next.js: both are powerful full-stack React frameworks, but they take fundamentally different approaches to architecture, routing, and developer experience. This guide breaks down their core features from SSR and data fetching to TypeScript support and deployment, to help you choose the right tool for your next React project.

Abiola Farounbi
Jun 12, 2025 â‹… 8 min read
View all posts

4 Replies to "The definitive guide to SCSS"

  1. Thank you so much for this simple and very enlightening tutorial. I knew a basic of css and nothing of scss. Now I can compile the files and update my website easily.

  2. Under “Using & in nesting” you show 2 examples: one in CSS that the SCSS ultimately gets converted to, and one in SCSS. You then state about the SCSS that “you can achieve the same effect much more easily with SCSS by using the & character in nesting. However, both examples are 8 lines of code and not much different. What exactly was “much easier”?

    Though writing in SCSS can save you a lot of repetition in the id/class hierarchy, it is ultimately more complex since you are adding in variables, mixins, and functions that a developer needs to spend a lot of time hunting down and investigating to find out where and how to modify something. And all the SCSS is doing is writing vanilla CSS anyway — something grandpa already knows how to do without needing to learn a new language or use a CSS processor 🙂

Leave a Reply