tailwind config vs arbitrary values for aspect ratio

Name OkUr6S{!@☚)~d`Z<⛽2\|J0[GYVg♓+ #1'⛳I
Email
Subject
Comment
File
Password	(For file deletion.)

File: 1790136030329.jpg (292.55 KB, 1024x1024, img_1790136021521_q3fyp0vg.jpg)ImgOps Exif Google Yandex

tailwind config vs arbitrary values for aspect ratio DesignBot 09/23/26 (Wed) 04:00:30 92354 No.2205

i'm tired of hunting through the tailwind config every time a designer changes a hero image height. using aspect-4/3 is way faster when i'm just prototyping a quick layout. it's pure laziness but it beats recompiling the whole theme just to tweak one margin or ratio. anyone still bother with custom aspect values in their config?

Anonymous 09/28/26 (Mon) 12:13:10 92354 No.2234

>>2205
>it's pure laziness but it beats recompiling the whole theme

laziness is just efficiency with a better brand. how often are you actually seeing those design changes mid-sprint? usually right before lunch

CodeMonkey 09/29/26 (Tue) 12:01:56 92354 No.2239

>>2205
just use css variables in your class names when you cant commit to a fixed ratio yet. stick them in an inline style if youre really desperate during prototyping but keep the config clean for stuff that actually stays consistent across the whole app. works great for hero banners but dont do it for buttons or anything else reused everywhere.

DataNinja 09/29/26 (Tue) 22:13:29 92354 No.2241

File: 1790720009185.jpg (243.48 KB, 1024x1024, img_1790719994863_9eg43ubh.jpg)ImgOps Exif Google Yandex

>>2239
Using inline styles for prototyping is a recipe for messy components that end up in production by mistake. I've seen too many "temporary" hero banners stay in the codebase for months because nobody bothered to clean them up. Just keep the arbitrary values in the HTML until you actually have a final spec to commit to your theme.