Skip to main content

Front end practice: CSS and SCSS


 Let's go through some CSS best practices with examples:

In CSS

  1. Use External Stylesheets:

    Instead of inline styles or internal styles, prefer using external stylesheets. Create a separate CSS file and link it to your HTML documents. This promotes code reusability and maintainability.

    Example: styles.css

      /* styles.css */
 body {
   font-family: Arial, sans-serif;
   background-color: #f0f0f0;
   color: #333;
 }

    index.html

     <!DOCTYPE html>
 <html lang="en">
 <head>
   <meta charset="UTF-8">
   <meta name="viewport" content="width=device-width, initial-scale=1.0">
   <title>My Website</title>
   <link rel="stylesheet" href="styles.css">
 </head>
 <body>
   <!-- Your content here -->
 </body>
 </html>

  2. Follow a CSS Methodology: Use a CSS methodology like BEM (Block, Element, Modifier) to organize your CSS classes and make them more manageable.

    Example:

     <div class="header">
   <h1 class="header__title">Welcome to our website</h1>
 </div>

     /* styles.css */
 .header {
   background-color: #007bff;
   padding: 20px;
 }

 .header__title {
   color: #fff;
   font-size: 24px;
 }

  3. Avoid Using IDs for Styling: IDs have higher specificity than classes, which can lead to issues with overriding styles. Reserve IDs for JavaScript interactions, and use classes for styling.

    HTML:

     <div class="header" id="main-header">
   <h1 class="header-title">Welcome to our Website</h1>
 </div>

    CSS (Avoiding IDs for Styling):

     /* styles.css */
 .header {
   /* Common styles for all headers */
   font-size: 24px;
   color: #333;
   text-align: center;
   padding: 20px;
   background-color: #f0f0f0;
 }

 /* Specific styles for the main header */
 #main-header {
   /* Avoid styling directly using the ID */
   border-bottom: 2px solid #007bff;
 }

  4. Keep Selectors Specificity Low: Use simple selectors and avoid deep nesting of classes. This makes your styles more maintainable and reduces the risk of unintended style overrides.

    HTML:

     <div class="container">
   <h2 class="section-title">Section Title</h2>
   <p class="section-text">This is some text in the section.</p>
 </div>

    CSS (Keeping Selectors Specificity Low):

     /* styles.css */
 .container {
   /* Specificity kept low for container class */
   background-color: #f0f0f0;
   padding: 20px;
 }

 .container .section-title {
   /* Specificity kept low for section title */
   font-size: 24px;
   color: #007bff;
 }

 .container .section-text {
   /* Specificity kept low for section text */
   font-size: 16px;
   color: #333;
 }

    In this example, we keep the selectors' specificity low by using class selectors. We avoid using IDs or element selectors, which would increase the specificity and make it harder to override the styles. By utilizing class selectors for styling, we maintain a more modular and flexible approach, allowing easier style changes and better separation of concerns.

  5. Limit the Use of !important: Avoid using !important to override styles. Instead, refactor your CSS to have better specificity or use more specific selectors.

    HTML:

     <button class="btn btn-primary">Click Me</button>

    CSS (Avoiding !important):

     /* styles.css */
 .btn {
   padding: 10px 20px;
   border: none;
   cursor: pointer;
   font-size: 16px;
 }

 .btn-primary {
   background-color: #007bff;
   color: #fff;
 }

 /* Avoid using !important, and instead, use proper class specificity */

    In this example, we avoid using !important. We rely on class selectors for styling, which helps maintain the proper specificity. By using the appropriate class selectors, we ensure that the .btn-primary styles will take precedence over the base .btn styles. It's crucial to use proper class naming and specificity instead of resorting to !important to maintain a clean and maintainable codebase.

  6. Use Flexbox or Grid for Layouts: Embrace CSS Flexbox or Grid for creating responsive and flexible page layouts, as they provide powerful layout capabilities.

    Example:

     /* styles.css */
 .container {
   display: flex;
   justify-content: space-between;
 }

 .sidebar {
   flex-basis: 30%;
 }

 .main-content {
   flex-basis: 70%;
 }

     <div class="container">
   <div class="sidebar">
     <!-- Sidebar content -->
   </div>
   <div class="main-content">
     <!-- Main content -->
   </div>
 </div>

  7. Use CSS Variables (Custom Properties): Leverage CSS variables to store and reuse values throughout your stylesheet. They promote consistency and make it easier to update global styles.

    Example:

     /* styles.css */
 :root {
   --primary-color: #007bff;
 }

 .button {
   background-color: var(--primary-color);
 }

  8. Optimize and Minify CSS: Minimize your CSS file by removing unnecessary whitespace and comments. You can use various tools and plugins to automate this process during build or deployment.

By following these CSS best practices, you can write cleaner, maintainable, and performant stylesheets, making your front-end development process more efficient and effective.

In SCSS

  1. Use Nested Selectors Wisely: SCSS allows you to nest selectors, but nesting too deeply can result in overly specific CSS output and increase the risk of CSS specificity conflicts. Avoid nesting beyond three levels whenever possible.

    
 .header {
   .nav {
     ul {
       li {
         a {
           color: blue;
         }
       }
     }
   }
 }

 // Better practice: Limit nesting
 .header {
   .nav {
     li {
       a {
         color: blue;
       }
     }
   }
 }

  2. Use Variables: Take advantage of variables to store reusable values like colors, font sizes, or spacing. This makes it easier to maintain and modify your styles consistently.

    
 $primary-color: #007bff;
 $font-size-base: 16px;

 // Usage
 .header {
   background-color: $primary-color;
   font-size: $font-size-base;
 }

  3. Avoid ID Selectors: Prefer using class selectors over ID selectors. ID selectors have higher specificity, making them harder to override and lead to inflexible CSS.

     // Bad practice: Using ID selector
 #main-container {
   // styles...
 }

 // Better practice: Using class selector
 .main-container {
   // styles...
 }

  4. Modularize with Partials: Split your SCSS code into smaller partial files. This helps organize your styles and makes them more manageable.

     styles/
 |-- _variables.scss
 |-- _header.scss
 |-- _footer.scss
 |-- main.scss

  5. Use @extend Sparingly: While @extend can be useful for reusing styles, be cautious as it can lead to bloated CSS. Only use it when you need to share a significant amount of styles between selectors.

     // Bad practice: Overuse of @extend
 .button {
   border: 1px solid #ccc;
   padding: 10px;
 }

 .submit-button {
   @extend .button;
   background-color: #007bff;
 }

 .cancel-button {
   @extend .button;
   background-color: #dc3545;
 }

 // Better practice: Use classes instead of @extend
 .button {
   border: 1px solid #ccc;
   padding: 10px;
 }

 .submit-button {
   @extend .button;
   background-color: #007bff;
 }

 .cancel-button {
   @extend .button;
   background-color: #dc3545;
 }

  6. Use Mixins for Reusable Styles: Mixins allow you to define reusable blocks of styles that can be included in multiple selectors.

     // Mixin
 @mixin button-styles {
   border: 1px solid #ccc;
   padding: 10px;
 }

 // Usage
 .button {
   @include button-styles;
 }

 .submit-button {
   @include button-styles;
   background-color: #007bff;
 }

 .cancel-button {
   @include button-styles;
   background-color: #dc3545;
 }

  7. Use % Placeholder Selectors for Extending: When you need to extend styles but don't want to create additional CSS classes, use placeholder selectors with % to prevent generating extra CSS.

     // Placeholder selector
 %button-styles {
   border: 1px solid #ccc;
   padding: 10px;
 }

 // Usage
 .button {
   @extend %button-styles;
 }

 .submit-button {
   @extend %button-styles;
   background-color: #007bff;
 }

 .cancel-button {
   @extend %button-styles;
   background-color: #dc3545;
 }

  8. Use Parent Selector &: The & symbol allows you to reference the parent selector, enabling you to create more specific styles.

     // Nested selector
 .button {
   &:hover {
     background-color: #ddd;
   }
 }

 // Output
 .button:hover {
   background-color: #ddd;
 }

These best practices should help you write cleaner, more maintainable SCSS code. Remember that the key to good SCSS is organization, reusability, and avoiding overly specific CSS output.

Comments

Post a Comment

Popular posts from this blog

Advanced Next.js URL handling with URLSearchParams

  Video Tutorial Introduction In Next.js, you can work with URL query parameters using the next/router module, which provides a way to access and manipulate the query string parameters of the current URL. Query parameters are typically used to pass data from one page to another or to filter content on a page. Here's how you can work with URL query parameters in Next.js: Step 1: Setup next.js project. if you want more about it  read the article Step 2: Import URL search params in your file  page.tsx|jsx . import { useSearchParams } from 'next/navigation' Step 3: Use the useSearchParams hook into the file like below: export default function Example() { const searchParams = useSearchParams()!; } Step 4: Accessing query params value into your component: export default function Example() { let term; const searchParams = useSearchParams()!; // Set updated value to the term if(searchParams?.has('term')) { term = searchParams.get('term'); } retur...
Post a Comment
Read more

Tailwind CSS theming system detected theme, manual mode dark and light theme with NextJS

Introduction?   In the ever-evolving world of web development, user experience plays a crucial role in determining the success of a website or web application. One aspect of user experience that has gained significant attention in recent years is the choice between light and dark themes. Users prefer different themes based on their surroundings and personal preferences, and as a developer, you can enhance their experience by offering theme options that adapt to their needs. In this guide, we'll explore how to implement system preferences, light and dark themes in a Next.js application with the help of Tailwind CSS. Why Implement System Preferences and Theme Switching? The choice between light and dark themes is not just about aesthetics; it also impacts usability and accessibility. Users often prefer a dark theme in low-light environments, while a light theme is preferred during the day. To provide a seamless user experience, you can implement system preferences to detect the user...
Post a Comment
Read more

Building Cross-Platform PWAs with Next.js: From Web to Mobile

A Progressive Web App (PWA) is a type of web application that offers a user experience similar to that of a traditional native mobile app or desktop application. PWAs are designed to be fast, reliable, and engaging, and they combine the best features of web and mobile apps. Here are some key characteristics and features of PWAs: Progressive Enhancement:  PWAs are designed to work on any platform, whether it's a desktop, mobile device, or tablet. They provide a consistent user experience across various screen sizes and resolutions. Offline Capabilities:  One of the defining features of PWAs is their ability to work offline or in low-network conditions. They achieve this through the use of service workers, which cache essential resources and enable the app to function even when there's no internet connection. Responsive Design:  PWAs are built with responsive web design in mind, ensuring that the user interface adapts to different screen sizes and orientations, providing a ...
Post a Comment
Read more

Step-by-Step Guide to Setting up Next.js with Tailwind CSS

Introduction Web development frameworks and libraries are evolving at a rapid pace, and staying up-to-date with the latest technologies is essential for building modern, responsive web applications. Next.js and Tailwind CSS are two popular tools that have gained significant attention in the web development community. Next.js is a powerful React framework for building server-rendered web applications, while Tailwind CSS is a utility-first CSS framework that simplifies styling and offers a responsive design system. why next.js use over react? Next.js is a framework built on top of React that provides a number of features and benefits that make it a good choice for building modern web applications. Some of the reasons why you might choose to use Next.js over React include: Server-side rendering (SSR). Next.js provides built-in support for SSR, which can improve the performance and SEO of your application. Static site generation (SSG). Next.js can also generate static HTML pages that can...
Post a Comment
Read more

No code API development for front end engineer/web developer

  Creating an API without writing any code might seem impossible, but there are ways to streamline the process and simplify development using low-code or no-code tools. In this blog post, we will explore various approaches to develop APIs without extensive coding. Code demo URL Thanks for reading!
Post a Comment
Read more