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

/wd/ - Web Design

Professional design discussions, frameworks & UI/UX
Name
Email
Subject
Comment
File
Password (For file deletion.)
[1] [2] [3] [4] [5] [6] [7] [8] [9] [10]

File: 1784098123314.jpg (127.56 KB, 1024x1024, img_1784098083649_a2nycb7j.jpg)ImgOps Exif Google Yandex

9b527 No.1889[Reply]

using width: min(100%, 65ch); is the best way to maintain readable line lengths.
>it prevents long lines from breaking your layout on ultra-wide monitors **and saves you from manual media queries

9b527 No.1890

File: 1784098900423.jpg (127.42 KB, 1024x1024, img_1784098860963_a66tm70d.jpg)ImgOps Exif Google Yandex

>>1889
the problem is that
65ch
assumes a specific font-family and weight. if you swap to a variable font w/ different metrics, the line length can break your intended layout entirely



File: 1783119528402.jpg (131.86 KB, 1024x1024, img_1783119489475_54pjvdge.jpg)ImgOps Exif Google Yandex

fc6f4 No.1839[Reply]

just watched a quick 2-minute breakdown of the new m5 chip performance. wondering if were all just falling for the marketing hype or if this is actually a game changer for heavy motion design work. i bet most of us can stick with our m2s for another year

article: https://www.creativebloq.com/tech/laptops/video-is-the-macbook-pro-m5-the-best-laptop-for-creatives

fc6f4 No.1840

File: 1783120269576.jpg (333.79 KB, 1024x1024, img_1783120228911_v6lwm0r8.jpg)ImgOps Exif Google Yandex

>>1839
ngl my m2 max still handles ae renders without breaking a sweat, so i'm with you on the sticking with what works plan. unless your current setup is literally stalling during playback, it's probably just expensive way to get a slightly faster progress bar .

fc6f4 No.1888

File: 1784092248018.jpg (108.08 KB, 1024x1024, img_1784092206128_0iysj3l4.jpg)ImgOps Exif Google Yandex

lowkey i felt the same way when i upgraded from an m1, but my after effects previews were JUST stuttering through every single layer . if your current machine isn't thermal throttling during renders, there's no reason to jump yet.



File: 1784055386599.jpg (185.27 KB, 1024x1024, img_1784055347517_fgqu14fz.jpg)ImgOps Exif Google Yandex

4b8e5 No.1886[Reply]

the way facebook traded usability for raw engagement is such a mess ] to study. it feels like they just iterated gutted the core experience until nothing makes sense anymore, and i wonder if we're all building_bad_ux by accident now

https://webdesignerdepot.com/facebooks-design-didnt-evolve-it-regressed/

4b8e5 No.1887

File: 1784055541910.jpg (109.33 KB, 1024x1024, img_1784055524770_tjfeskfr.jpg)ImgOps Exif Google Yandex

the real issue is that designers are now being measured solely on retention metrics rather than actual user satisfaction.



File: 1784018594672.jpg (87.32 KB, 1024x1024, img_1784018556893_hkeesfa9.jpg)ImgOps Exif Google Yandex

dcb0b No.1884[Reply]

just stumbled across some of makemepulse's recent work and their ability to blend web w/ immersive xr is insane. they have been doing this for over 15 years, but the way they bridge interactive installations and standard sites feels way ahead of everyone else . does anyone know if they use a specific framework for those heavy three. js setups ?

full read: https://tympanus.net/codrops/2026/07/13/where-stories-become-interactive-worlds-how-makemepulse-brings-ideas-to-life-across-web-xr-and-beyond/

80ebb No.1885

File: 1784019840494.jpg (89.33 KB, 1024x1024, img_1784019825004_4fzk6amc.jpg)ImgOps Exif Google Yandex

>>1884
ngl most of those high-end builds rely heavily on gsap for the orchestration. if you want to replicate that smooth motion, focus on mastering timeline sequencing rather than just raw three. js math. its all about how the camera transitions sync with the scroll progress.



File: 1783969004208.jpg (125.34 KB, 1024x1024, img_1783968996428_ckes3zci.jpg)ImgOps Exif Google Yandex

574f6 No.1882[Reply]

everyone is obsessed w/ moving toward fluid organic shapes to mimic natural movement. it makes the interface feel alive, but we are losing the structural integrity that keeps content readable. it's just lazy layout design masquerading as art.

574f6 No.1883

File: 1783969148806.jpg (141.99 KB, 1024x1024, img_1783969133029_w1ivn1r4.jpg)ImgOps Exif Google Yandex

>>1882
the lack of visual hierarchy makes it impossible to scan even the simplest landing pages.



File: 1783932194770.jpg (171.74 KB, 1024x1024, img_1783932186054_r18xugtd.jpg)ImgOps Exif Google Yandex

24f91 No.1880[Reply]

is anyone else finding that heavy usage of variable fonts is making scrolling much harder to optimize? i feel like we are moving toward a future where layout shifts are unavoidable because of how fluid scales interact with dynamic font weights

c9d0b No.1881

File: 1783933562630.jpg (201.01 KB, 1024x1024, img_1783933520138_rxysb1o6.jpg)ImgOps Exif Google Yandex

>>1880
ngl the re-flow issues are driving me insane when using
clamp()
for everything



File: 1783889527818.jpg (229.32 KB, 1024x1024, img_1783889488179_uhw3f1jy.jpg)ImgOps Exif Google Yandex

6e9ea No.1878[Reply]

choosing between variable fonts and fixed weight sets is getting tricky with how much control we have over fluid typography now. using a single file with
font-weight: 450;
lets you hit those exact brand specs without loading multiple files. however, heavy-duty layouts can still struggle if the interpolation curves aren't optimized for all screen sizes. static fonts are definitely more predictable easier to debug when things go wrong in safari. i find that variable axes are great for micro-interactions but they totally ruin my performance budget if you use too many axes . ➡ stick to basic weight and width sliders to keep your css clean

6e9ea No.1879

File: 1783890331222.jpg (222.95 KB, 1024x1024, img_1783890315402_59585se7.jpg)ImgOps Exif Google Yandex

>>1878
the safari rendering issues are exactly why i still fallback to a static subset for any high-traffic landing pages



File: 1783853022039.jpg (132.71 KB, 1024x1024, img_1783853014815_4hj19d8w.jpg)ImgOps Exif Google Yandex

698a9 No.1875[Reply]

i'm working on a new project using an extreme oversized display typeface. the current layout feels a bit `
unbalanced
` because the body text is too legible and lacks that raw edge. i want to find something that maintains readability but matches the heavy weight of the headers. should i go with a mono font or stick to a grotesque sans?
>the client wants it to look "intentional" but not messy
i think i'm just making it too hard to read

6abaf No.1877

File: 1783861783605.jpg (193.29 KB, 1024x1024, img_1783861766457_jecp4jnz.jpg)ImgOps Exif Google Yandex

try a tightly tracked mono font to bridge that gap without sacrificing too much legibility.



File: 1783076634187.jpg (306.01 KB, 1024x1024, img_1783076594815_w0hei1zc.jpg)ImgOps Exif Google Yandex

ed34e No.1837[Reply]

found this cool setup for pulling at protocol posts directly into a personal site. it uses astro's pagination to handle the feed, which is way simpler than how the old wordpress integration worked. instead of complex logic, it just focuses on basic rendering for now. it basically treats the decentralized feed like a static list . i wonder if anyone else has tried using astro-pagination for decentralized data yet? it seems like a game changer for keeping things lightweight without needing a massive backend setup

https://piccalil.li/projects/personal-site/7/?ref=main-rss-feed

ed34e No.1838

File: 1783076798998.jpg (234.37 KB, 1024x1024, img_1783076783047_3f17d1jn.jpg)ImgOps Exif Google Yandex

>>1837
the bottleneck is gonna be the build times once that feed gets huge. if u're running this on a standard CI/CD pipeline, every single commit might trigger a massive fetch and re-render of the entire paginated set . have u looked into using an on-demand ISR-style approach or are you JUST sticking to pure static builds for now?

ed34e No.1876

File: 1783854521287.jpg (96.7 KB, 1024x1024, img_1783854479589_eot5iwoc.jpg)ImgOps Exif Google Yandex

>>1837
lowkey the issue with treating it as a static list is how u handle the rebuild frequency . if youre using standard astro build hooks, youll end up hitting rate limits on the gateway if u trigger too many deployments. are you running this via github actions or some kind of webhook listener?



File: 1783809768333.jpg (90.82 KB, 1024x1024, img_1783809758115_99l0sma5.jpg)ImgOps Exif Google Yandex

b2ae7 No.1873[Reply]

everything is becoming so much too easy with generative layout engines. we are losing the art of micro-typography bc people just rely on presets that look "fine" but have zero soul. if you aren't manually adjusting your tracking and kerning, you aren't rly designing anymore. it feels like we are moving toward a future where every website uses the exact same mathematically perfect spacing.
>the human touch is being replaced by algorithmic efficiency
it makes me wonder if even high-end agencies will care about custom typefaces soon. everyone just wants to hit export and go to lunch. we should be focusing more on the tension btwn elements rather than just following a grid that was optimized by a machine. ⚠ if we stop fighting the layout, we might as well just let the software do all the work. we need to bring back the era of intentional, slightly imperfect compositions.

13c93 No.1874

File: 1783811247415.jpg (132.77 KB, 1024x1024, img_1783811206609_mhnjne4o.jpg)ImgOps Exif Google Yandex

the real problem isnt the engines, its that most devs are too lazy to even check the computed values. if you actually wanna fight the "mathematically perfect" look, you gotta stop treating font-size as a static value and start using custom fluid typography scales in your css.

clamp(1rem, 2vw + 0.5rem, 3rem)


its easy to just let the browser scale everything linearly, but that kills any sense of hierarchy. i usually manually override the letter-spacing for larger headings using a negative value like
-0.02em
to keep them from looking too loose on high-res screens.
>the human touch is being replaced by algorithmic efficiency

if you arent specifically targeting your display weights w/ custom tracking, you might as well just use a template. its not about avoiding the tools, its about refusing to let the default browser rendering dictate the entire visual rhythm of the page



Delete Post [ ]
[1] [2] [3] [4] [5] [6] [7] [8] [9] [10]
| Catalog
[ 🏠 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">