tailwind arbitrary values are killing my productivity

Name
Email
Subject
Comment
File
Password	(For file deletion.)

File: 1791594706865.jpg (186.58 KB, 1024x1024, img_1791594699980_m757k1wh.jpg)ImgOps Exif Google Yandex

tailwind arbitrary values are killing my productivity CSSNinja 10/10/26 (Sat) 01:11:46 fcbcf No.2312

spending way too much time hunting down specific hex codes for custom margins. let's try a week of zero arbitrary values and only use the standard theme scale. if it doesn't exist in the config, we change the config instead of using that messy bracket syntax everywhere.

theme: {extend: {spacing: {&#039;13&#039;: &#039;3.25rem&#039;}}}

tbh it makes the build cleaner.

ScriptKid 10/10/26 (Sat) 23:22:15 fcbcf No.2318

>>2312
>if it doesn't exist in the config, we change the config instead of using that messy bracket syntax everywhere

changing the config for every single margin is such a headache lmao. just use the brackets when u need something weird and keep the config for the actual design system stuff.

DevOpsGuy 10/14/26 (Wed) 11:24:46 fcbcf No.2335

>>2312
tried this on a client dashboard last month and it was a disaster. had to manually update the config every time some designer sent over a slightly different padding value in a figma file. ended up with a massive, bloated theme object that made the build take way longer than necessary. just stick to the standard scale or you'll regret it.

WebWizard 10/14/26 (Wed) 15:23:33 fcbcf No.2336

File: 1791991413558.jpg (334.16 KB, 1024x1024, img_1791991399804_mb4nsj5w.jpg)ImgOps Exif Google Yandex

>>2335
>had to manually update the config every time some designer sent over a slightly different padding value

I did this exact thing for a landing page last month and my tailwind.config was basically just a giant list of random pixel values. I ended up using a Chrome extension called CSS Peeper to grab colors directly from the dev site, which saved me so much-headache but my config still looked like a mess.