<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Abhishek Mohapatra on Medium]]></title>
        <description><![CDATA[Stories by Abhishek Mohapatra on Medium]]></description>
        <link>https://medium.com/@abhishekmohapatra_84875?source=rss-b85b49726eb8------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*11FK7xR8l7XQiX3E</url>
            <title>Stories by Abhishek Mohapatra on Medium</title>
            <link>https://medium.com/@abhishekmohapatra_84875?source=rss-b85b49726eb8------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 12:33:19 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@abhishekmohapatra_84875/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[The Modern CSS Toolkit: Mastering Custom Properties for Flexible Design Systems]]></title>
            <link>https://medium.com/@abhishekmohapatra_84875/css-is-not-dead-it-has-just-become-better-than-ever-f20ddf647fdd?source=rss-b85b49726eb8------2</link>
            <guid isPermaLink="false">https://medium.com/p/f20ddf647fdd</guid>
            <category><![CDATA[css3]]></category>
            <category><![CDATA[css]]></category>
            <category><![CDATA[scss-to-css-converter]]></category>
            <category><![CDATA[scss]]></category>
            <category><![CDATA[modular-css]]></category>
            <dc:creator><![CDATA[Abhishek Mohapatra]]></dc:creator>
            <pubDate>Sat, 25 Apr 2026 09:31:13 GMT</pubDate>
            <atom:updated>2026-04-25T09:34:52.007Z</atom:updated>
            <content:encoded><![CDATA[<p>CSS had a lot of limitations, no variables, no imports making it so difficult to make reusability a thing here . Then came SCSS which actually changed the dynamics of the entire established css system. It added variables, it added imports, it added recursion etc etc . This made css more programmatic and modular , let’s just say it basically added sense to css. Now with time css also evolved itself and became more and more stronger and smarter. Now time has come with some finer sensibilities added to the newer versions of css it has outsmarted SCSS. In this article let’s dive deep into some of the outsmarting features which now comes out of the box in css and we don’t have to depend on the SCSS for the same anymore.</p><p>1. Now we can have variables in css itself coming out of the box called css custom properties. We can see in the below screenshot the variable is being used directly which stores the red color that is used within the paragraph.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*CCi8uoS8qOCn-TG_55O77w.png" /></figure><p>2. We can use variable scoping to avoid the complex nesting we do in SCSS to achieve a specific styling. Lets see the below video for the same. By just wrapping the card div with the dark-theme the look and feel changes without the extra hassle of having a nested structure of classes we used to have in SCSS earlier.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*NTNDJFLyw9fcNknKpmmczw.gif" /></figure><p>Also since all browser’s now support native nesting we can have nesting in css as well which we did earlier with scss like the below:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/816/1*wVFN_Cy8ddRnIgmySw-94A.png" /></figure><p>3. Runtime Interoperability:</p><p>Now that the variables exist in the browser’s memory JS can write and change them instantly, which was earlier not possible in SCSS. In SCSS we cannot change a — p-bg in JS, but now with the evolved css we can easily do the same like below. This helps us with the added advantage of making user customisable dashboards etc etc</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wARRDUku7dra_cORCjz-qA.png" /></figure><p>4. Microfrontend advantage:</p><p>In Microfrontend architecture we have using SCSS variables can lead to bundles bloat(it means that every MFe will have its own bundle that will have the same variable with diff values lets say –primary-color can be blue in MFe1 and green in MFe2) which is of course safe but the issue is that we lose the central control in this scenario like for eg changing the primary color in Mfe2 would need me to change the value inside it build and redeploy it , also having this kind of theming isn’t a great practice altogether as well as it might lead to brand inconsistency. In css however we can just have one css file in the shell/root application that maintains this $primary-color and we can change it there to reflect in all associated Mfe’s . If in any scenario we want to maintain 2 different styling with the –primary-color we can simply have some classnames as –primary-color-Mfe1 and –primary-color-Mfe2. Also this css changes will be loaded on to the browser, in the dev-tools we can edit those and see the changes instantly.</p><p>So is SCSS dead then ?. Not really SCSS still forms the backbone for the complex logic of generating utility classes using for loops and if/else mixins. SCSS is basically used for complex nesting etc whereas css is used to maintain the central level theming etc.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f20ddf647fdd" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Angular Signals:]]></title>
            <link>https://medium.com/@abhishekmohapatra_84875/angular-signals-fe04ea2b62a1?source=rss-b85b49726eb8------2</link>
            <guid isPermaLink="false">https://medium.com/p/fe04ea2b62a1</guid>
            <category><![CDATA[angular-21]]></category>
            <category><![CDATA[angular-signals]]></category>
            <category><![CDATA[angular-20]]></category>
            <category><![CDATA[angular-zoneless]]></category>
            <category><![CDATA[angular]]></category>
            <dc:creator><![CDATA[Abhishek Mohapatra]]></dc:creator>
            <pubDate>Mon, 06 Apr 2026 20:02:23 GMT</pubDate>
            <atom:updated>2026-04-06T20:02:23.959Z</atom:updated>
            <content:encoded><![CDATA[<p>With the advent of angular 16 we have had the inception/onset for the angular signals which changes a lot of things how they work/function in traditional angular practices and logic.Now as we head into 2026 with fully ready angular 20 features forming the pillar of zoneless app development already they have had signals in a very strong position to be used to change the age old practice of traversing the entire component tree to find out what changed. In layman terms we can consider a big mansion with multiple rooms as our angular component structure when we switch on a light bulb in one room earlier with boolean flag variables angular used to travel to every room to check which room’s light has been switched on, but now with signals angular can directly open the room whose light bulb has been switched on. This saves a lot of effort , time and complexity as compared to the traditional <a href="http://zone.js/">zone.js</a> mechanism of traversing each room/component.</p><p>Let’s take a basic example from the below code snippet and attached screenshot:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3OIG2mikw2Lxt5dbZTYe3A.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/746/1*zKP4fmGSpJx9tHSNtRyJJQ.png" /></figure><p>Now in the above example we have the signal showModal that is being used to show/hide a modal sort of a mimic functionality . So the idea is to replace the boolean variable showModal which we could have used to show/hide the modal.<br>Before that, here are the screenshots for the ts file and how the modal looks on the UI after clicking the `<em>Run the operation</em>` button.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ec8M7gpQJuZEv0QgJRux7w.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mcJwxAADISUisxpB3nI_5A.png" /></figure><p>So as you can see we have used the signal showModal in the ts file. Here the signal creates a reactive state (<em>think of it conceptually similar to a react state if you are a react developer but obviously different in their update approach) </em>within the component that enables angular’s change-detection mechanism <em>(in a separate blog)</em> to exactly identify what changed in the component and find the DOM element where the change is reflecting directly without following the traditional way of the DFS search algorithm it otherwise used to follow to scan everything and then find that one element that changed.<br>So it may have an O(N) complexity relative to the tree whereas the signals will have an O(1) complexity directly to the element.</p><p>Hence we can conclude using signals are highly efficient when compared to the traditional practice of traversal.</p><p><strong><em>BONUS:</em></strong></p><p>As you might see the usage of @if and not the traditional *ngIf directive in the code snippet, below are few advantages of using them, more coming in a different blog about angular 20 advantages.</p><p>Advantages of using @if instead of *ngIf directive 🔜</p><p>No need to import the common Module anymore use the built in @if directly.<br>It’s more readable <br>No need to depend on the &lt;ng-container&gt; / &lt;div&gt; for using the *ngIf directive and a separate &lt;ng-template&gt; for the else block. We can use the @if directly.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fe04ea2b62a1" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Tailwind, tangled With React.]]></title>
            <link>https://medium.com/@abhishekmohapatra_84875/tailwind-tangled-with-react-ebfd0964d9ee?source=rss-b85b49726eb8------2</link>
            <guid isPermaLink="false">https://medium.com/p/ebfd0964d9ee</guid>
            <category><![CDATA[tailwind-css]]></category>
            <category><![CDATA[react]]></category>
            <category><![CDATA[tailwind]]></category>
            <dc:creator><![CDATA[Abhishek Mohapatra]]></dc:creator>
            <pubDate>Sun, 21 May 2023 12:58:58 GMT</pubDate>
            <atom:updated>2023-05-21T13:14:51.775Z</atom:updated>
            <content:encoded><![CDATA[<h3>Tailwind tangled With React.</h3><h3>What is tailwind css?</h3><p>Tailwind CSS is a highly customizable utility-first CSS framework that provides a comprehensive set of pre-built styles and utility classes. It aims to simplify web development by offering a wide range of ready-to-use CSS classes that can be easily applied to HTML elements to style and design your user interface. It allows us to add CSS to the HTML file without leaving the file itself.</p><h3>As a dev, why should I use TailWind css ?</h3><p>As a dev it’s very painful to leave the html file again and again, do changes in the css file and come back to the html file and do the mapping again. So we have the tailwind css to the rescue.</p><p>There is no smell about tailwind when we try to build a webpage we won’t know has been built by tailwind css.</p><p>Some of the common questions asked by Devs are as below ..</p><p>Question:: why will I use tailwind css and not inline css how are both different .</p><p>Question:: Will this tailwind css not increase the bundle size when being deployed</p><p>Question:: If writing this much, css classes will be very hard to maintain.</p><p>Some Collective Answers would be as follows:</p><ol><li>You don’t need to invent new CSS classes again and again.</li><li>You don’t need to think about reusing your classes because u dont have to write a new one.</li><li>Css doesn’t keep piling up along with the html files.</li><li>When changes are made there is no risk of breaking the existing templates.</li><li>No Risk of slowness in site and even the bundle size doesn’t increase.</li><li>We have breakpoints and we can modify the css to apply responsiveness.</li></ol><h3>How to set up Tailwind css in your React project .</h3><p>For setting up tailwind css for your react project you need to do the following steps .</p><ol><li>Create a new react project using create react app.</li><li>Inside the app go to the index.html file inside the public folder add the following script tag inside the head tag.</li><li><em>&lt;script src=”</em><a href="https://cdn.tailwindcss.com/"><em>https://cdn.tailwindcss.com</em></a><em>&quot;&gt;&lt;/script&gt;</em></li><li>Now add a small html element like a paragraph or so in your <em>App.jsx</em> file and use tailwind classes like <em>bg-indigo-500 w-52 h-52 ml-52</em>, that will add background-color to the div, add some width and height as well and some margin-left.</li></ol><p>Developers will face a warning in the console that this cannot be used in the production. This can be simply avoided by installing it with the help of POST css. Run the commands below to install the required packages.</p><p><em>npm install -D tailwindcss postcss autoprefixer</em></p><p><em>npx tailwindcss init</em></p><p>After initing it will create a tailwind.config.json file in the contents add * if you want to use tailwind across your project do the below config in content as shown.</p><figure><img alt="tailwind.config.js" src="https://cdn-images-1.medium.com/max/1024/1*3FfvAnT6EfSeRfUDvw50rw.png" /><figcaption>tailwind.config.js</figcaption></figure><p>Create a <em>postcss.config.js</em> file having the content as follows:</p><figure><img alt="postcss.config.js" src="https://cdn-images-1.medium.com/max/1024/1*Ky4f3Jqg5qR9Y4aYc-cR7g.png" /><figcaption>postcss.config.js</figcaption></figure><p>Create a <em>/src/style/tailwind.css</em> file having the tailwind css properties:</p><p>@tailwind base;</p><p>@tailwind components;</p><p>@tailwind utilities;</p><p>In the package.json file of your project add a script that will output your src/style/main.css file having the css properties that will be used.</p><figure><img alt="script to build css" src="https://cdn-images-1.medium.com/max/1024/1*m8dwfaM0nV6DaOoOZ4uFmQ.png" /><figcaption>script to build css</figcaption></figure><p>After this step in your <em>src/index.js</em> file remove the <em>index.css</em> file and add import the <em>./style/main.css</em> file that is generated. Build the css using the above command you just wrote. Start your react application .And you are good to go with the tailwind css use.</p><h3>Creating responsive designs with tailwind css (because its super easy and fun !!):</h3><p>Wanted to reflect on this part because writing media queries for responsiveness is a major pain-point amongst developers.</p><p>Creating responsive designs is a major pain-point of many developers . But here comes Tailwind CSS to the rescue.</p><p>In Tailwind CSS, responsiveness can be achieved using its built-in utility classes and responsive design features. Tailwind CSS provides a mobile-first approach to responsive design, where styles are applied by default to smaller screens and can be adjusted for larger screens using responsive modifiers.</p><p>Here’s how you can achieve responsiveness in Tailwind CSS:</p><p><em>Using Responsive Utility Classes:</em></p><p>Tailwind CSS provides a range of utility classes that allow you to show, hide, or modify elements based on screen sizes. You can use the sm, md, lg, and xl prefixes to specify different breakpoints.</p><p><em>&lt;div class=”bg-red-500 sm:bg-blue-500 md:bg-green-500 lg:bg-yellow-500 xl:bg-purple-500&quot;&gt;</em>Responsive Background Color&lt;/div&gt;</p><p>In the example above, the background color changes at different breakpoints: red for the default (small screens), blue for small screens and up, green for medium screens and up, yellow for large screens and up, and purple for extra-large screens and up.</p><p>Tailwind provides a comprehensive set of utility classes that cover various aspects of responsive design, including width, height, typography, flex box, and more. You can refer to the Tailwind CSS documentation for more details and explore the available classes and modifiers.</p><p>Customize the tailwind using tailwind.config.js file for different screen breakpoints.</p><p>To customize Tailwind CSS, you can use the tailwind.config.js file. This file allows you to modify various aspects of Tailwind’s default configuration, such as colors, spacing, breakpoints, and more. Here’s a step-by-step guide on how to customize Tailwind CSS using the tailwind.config.js file:</p><p>Generate the tailwind.config.js file:</p><p>If you haven’t already, create a tailwind.config.js file in the root of your project. You can generate this file using the Tailwind CLI by running the following command:</p><p><em>npx tailwindcss init</em></p><p>Open the file in any editor and add the property u want to extend inside the extend block. For eg:</p><figure><img alt="adding properties inside the extend block" src="https://cdn-images-1.medium.com/max/1022/1*MhXspwds95NFLdI-MWAmOw.png" /><figcaption>adding properties inside the extend block</figcaption></figure><p>However for adding breakpoints for different screen sizes we have to overwrite it outside of the extended block. As given below:</p><figure><img alt="breakpoints for different screen sizes" src="https://cdn-images-1.medium.com/max/768/1*kPYnVv864gg7KI5R9JTG6w.png" /><figcaption>breakpoints for different screen sizes</figcaption></figure><p>Note - So, there will be some properties that will be added inside the extend block and some properties that we have to be add outside of it .</p><p>After making the desired changes in the tailwind.config.js file, save the file. Once the CSS is rebuilt, your Tailwind CSS will reflect the customisations you made.</p><h3>Conclusion:</h3><p>In conclusion, the integration of Tailwind CSS with React provides developers with a powerful toolset for building modern, efficient, and visually appealing user interfaces. The seamless combination of Tailwind’s utility-first approach and React’s component-based structure streamlines the development process, promotes code reusability, and enhances the overall developer experience. By leveraging Tailwind’s extensive library of predefined utility classes and React’s modular nature, developers can rapidly create dynamic and responsive UIs while maintaining clean and maintainable code. Together, Tailwind CSS and React form a winning combination for building high-quality web applications.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ebfd0964d9ee" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>