<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Wahab Shah</title>
    <description>The latest articles on DEV Community by Wahab Shah (@wahab_shahg).</description>
    <link>https://dev.to/wahab_shahg</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F2621758%2F2bd7bc46-ea76-4041-b91e-938c6c7a61c3.jpg</url>
      <title>DEV Community: Wahab Shah</title>
      <link>https://dev.to/wahab_shahg</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/wahab_shahg"/>
    <language>en</language>
    <item>
      <title>Why I Built csstools.io as a Backend Developer</title>
      <dc:creator>Wahab Shah</dc:creator>
      <pubDate>Fri, 22 May 2026 17:49:03 +0000</pubDate>
      <link>https://dev.to/wahab_shahg/why-i-built-csstoolsio-as-a-backend-developer-5667</link>
      <guid>https://dev.to/wahab_shahg/why-i-built-csstoolsio-as-a-backend-developer-5667</guid>
      <description>&lt;p&gt;I’ve always been more comfortable writing backend logic than styling interfaces.&lt;/p&gt;

&lt;p&gt;Give me APIs, databases, or server-side code and I’m happy.&lt;/p&gt;

&lt;p&gt;But CSS?&lt;/p&gt;

&lt;p&gt;That usually meant:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;tweaking random values for 20 minutes&lt;/li&gt;
&lt;li&gt;fighting with gradients&lt;/li&gt;
&lt;li&gt;trying to remember animation syntax&lt;/li&gt;
&lt;li&gt;adjusting borders and shadows over and over&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Over time I realized something:&lt;/p&gt;

&lt;p&gt;A lot of developers don’t actually struggle with &lt;em&gt;ideas&lt;/em&gt; in CSS — they struggle with the repetitive trial-and-error process.&lt;/p&gt;

&lt;p&gt;So instead of searching for snippets every time, I started building small tools to generate CSS visually.&lt;/p&gt;

&lt;p&gt;That project eventually became &lt;a href="https://csstools.io" rel="noopener noreferrer"&gt;CSSTools.io&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;The goal wasn’t to replace learning CSS.&lt;/p&gt;

&lt;p&gt;It was to make common UI effects faster and less frustrating.&lt;/p&gt;

&lt;p&gt;Some tools currently include:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;animation generators&lt;/li&gt;
&lt;li&gt;gradient border generators&lt;/li&gt;
&lt;li&gt;shadow tools&lt;/li&gt;
&lt;li&gt;transform playgrounds&lt;/li&gt;
&lt;li&gt;and other small utilities for experimenting with CSS visually&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;One thing I’ve noticed is that visual experimentation makes CSS much easier to understand.&lt;/p&gt;

&lt;p&gt;Instead of reading documentation and guessing values, you can instantly see what changes.&lt;/p&gt;

&lt;p&gt;I’m still improving the project regularly, but building it has already changed how I work with frontend styling.&lt;/p&gt;

&lt;p&gt;Curious:&lt;br&gt;
What CSS task do you waste the most time on?&lt;/p&gt;

</description>
      <category>css</category>
      <category>showdev</category>
      <category>tooling</category>
      <category>webdev</category>
    </item>
  </channel>
</rss>
