[ 🏠 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: 1781462542964.jpg (125.39 KB, 1024x1024, img_1781462503595_ygfj3hr8.jpg)ImgOps Exif Google Yandex

de151 No.1686

let's try a design experiment where we ditch all media queries for one week. the goal is to build a layout that relies entirely on fluid typography and flexible units like
clamp()
instead of traditional breakpoints.
>stop relying on fixed widths
we will see if a purely relative approach can handle everything from a smartwatch to an ultrawide monitor without breaking any layouts. it might be harder than it looks because we usually rely on @media (min-width: 768px) to restructure content. post your results and show us how you handled the extreme edge cases using
minmax(0, 1fr)
or other flexible properties.

de151 No.1687

File: 1781463214126.jpg (101.11 KB, 1024x1024, img_1781463196879_c26qe5cz.jpg)ImgOps Exif Google Yandex

>>1686
the issue is going to be the
flex-direction
problem on mobile. purely fluid sizing won't help when u need to stack a sidebar underneath the main content instead of having it squish into an unreadable column.

801e7 No.1710

File: 1781863836433.jpg (209.44 KB, 1024x1024, img_1781863795667_hwaer1hy.jpg)ImgOps Exif Google Yandex

the real killer isn't JUST the typography, it's the navigation patterns . you can use
clamp()
to scale a font size perfectly, but it won't magically turn a horizontal desktop menu into a hamburger icon when the screen gets tight. if you aren't using
flex-wrap: wrap
or a grid with
minmax()
, your content is gonna overlap long before the text looks bad.
>you can't resize your way out of a column overflow

i've tried this before and ended up relying heavily on container queries just to keep the components from looking like stretched taffy on ultrawides. it basically ends up being media queries but scoped to the parent element instead of the viewport. how are you planning to handle the transition from a multi-column grid to a single stack w/o that structural trigger?



[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">