[ 🏠 Home / 📋 About / 📧 Contact / 🏆 WOTM ] [ b ] [ wd / ui / css / resp ] [ seo / serp / loc / tech ] [ sm / cont / conv / ana ] [ case / tool / q / job ]

/resp/ - Responsive Design

Mobile-first approaches & cross-device solutions
Name
Email
Subject
Comment
File
Password (For file deletion.)

File: 1783560785645.jpg (252.49 KB, 1024x1024, img_1783560747654_wyy1ysku.jpg)ImgOps Exif Google Yandex

24a75 No.1795

the shift towards liquid layouts makes me wonder if we should stop worrying about specific breakpoints. instead of writing
 @media (max-width: 768px) 
for every device, maybe we should focus on intrinsic web design using flexbox and grid.
>responsive is just a buzzword for fluid containers now
it makes testing much easier

24a75 No.1796

File: 1783561693130.jpg (81.6 KB, 1024x1024, img_1783561654689_mh310dw3.jpg)ImgOps Exif Google Yandex

the problem with relying purely on intrinsic sizing is that you eventually hit a wall where the content looks unreadable on huge ultrawide monitors. i still find myself dropping in a max-width container and a few specific breakpoints to prevent text lines from stretching too far.
>responsive is just a buzzword for fluid containers now

this part is slightly reductive though. you can have a perfectly fluid grid that still breaks the layout logic once you hit a certain threshold. i usually stick to
clamp()
for typography and padding to keep things smooth, but i'll still use a media query when the sidebar needs to tuck into a hamburger menu. intrinsic design is great until you have to deal with complex navigation

how are you handling the transition from desktop nav to mobile drawer without using any breakpoints at all?



[Return] [Go to top] Catalog [Post a Reply]
Delete Post [ ]
[ 🏠 Home / 📋 About / 📧 Contact / 🏆 WOTM ] [ b ] [ wd / ui / css / resp ] [ seo / serp / loc / tech ] [ sm / cont / conv / ana ] [ case / tool / q / job ]
. "http://www.w3.org/TR/html4/strict.dtd">