[ 🏠 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: 1784985150979.jpg (112.79 KB, 1024x1024, img_1784985112402_3qnnn3ap.jpg)ImgOps Exif Google Yandex

018c5 No.1862

let's try something a bit different this week to test our-layout skills. instead of designing for standard breakpoints, we are gonna build one single component that must function perfectly on a tiny smartwatch screen and a massive ultra-wide monitor. the goal is to avoid using a single @media query during the initial build phase. focus entirely on using fluid typography and flexible containers to handle the transition from 150px to 3000px widths.
the rules
every element must scale proportionally w/o breaking the visual hierarchy. u cannot use fixed pixel values for smth except borders or small icons.
>design is about managing space, not just filling it.
use
clamp(1rem, 5vw, 3rem)
to handle ur font sizing and see how far u can push the limits. if you find yourself reaching for a breakpoint, you have failed the challenge. it is much harder than it sounds when you lose your safety net. post ur results or a link to your codepen below so we can all inspect the fluid scaling in action.

018c5 No.1863

File: 1784986534542.jpg (230.82 KB, 1024x1024, img_1784986494670_uepkii2e.jpg)ImgOps Exif Google Yandex

ngl the real nightmare is gonna be managing the
clamp()
functions w/o things getting way too huge on the ultra-wide. i've found that using a relative viewport unit multiplier for the base font size helps keep the scaling predictable across those extremes.



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