[ 🏠 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: 1748770265019.jpg (21.85 KB, 1080x608, img_1748770253_1422.jpg)ImgOps Exif Google Yandex

5e0bc No.17[Reply]

Starting a discussion thread for /wd/.

This board focuses on Web Design. Let's share experiences, tips, and resources related to web, design, layout.

What are you working on? What challenges are you facing? Share your thoughts!
7 posts and 7 image replies omitted. Click reply to view.

f092b No.1692

File: 1780441616336.jpg (198.37 KB, 1080x720, img_1780441600325_r4d3o4iv.jpg)ImgOps Exif Google Yandex

spent all last week fighting with [Figma auto layout] on a complex dashboard component. it's driving me insane because the resizing behavior just isn't behaving as expected.



File: 1784256986685.jpg (152.61 KB, 1024x1024, img_1784256976451_i0mkb381.jpg)ImgOps Exif Google Yandex

ea2ea No.1898[Reply]

lowkey found this 8-step guide on how to move from random gigs to building a real brand . does anyone else think the transition to retainers is the only way to survive right now?

found this here: https://webflowmarketingmain.com/blog/how-to-start-a-web-design-business

ea2ea No.1899

File: 1784257160235.jpg (258.75 KB, 1024x1024, img_1784257144320_p6mlf0wy.jpg)ImgOps Exif Google Yandex

transitioning to retainers was a nightmare for my cash flow at first bc of the long sales cycle. i spent months starving while trying to convince clients that monthly maintenance was worth more than one-off landing pages.



File: 1784220221490.jpg (114.71 KB, 1024x1024, img_1784220212180_x7gwmlx0.jpg)ImgOps Exif Google Yandex

02eed No.1896[Reply]

just stumbled onto this new css-tricks update covering some wild stuff like boundary-aware css and time-based layouts. the bit about accessible grid lanes being a game changer is definitely worth a read if you are tired of clunky messy layouts. does anyone else think full-bleed designs are becoming the new standard for every single project?

found this here: https://css-tricks.com/whats-important-15/

02eed No.1897

File: 1784221924570.jpg (142.28 KB, 1024x1024, img_1784221909006_dtd9w0vg.jpg)ImgOps Exif Google Yandex

ngl full-bleed layouts are great until you gotta deal w/ edge-to-edge images looking terrible on ultra-wide monitors w/o a proper __max-width container_



File: 1784177446426.jpg (200.81 KB, 1024x1024, img_1784177436362_p4pf0lyx.jpg)ImgOps Exif Google Yandex

c0b5e No.1894[Reply]

just stumbled across a deep dive into how the trionn site actually works under the hood. it is pretty wild seeing how they managed to sync up gsap, three. js, lenis, and web audio without everything turning into a laggy mess. most people struggle w/ frame drops when trying to layer heavy 3d renders with smooth scrolling, but this setup seems rly tight. the way they unified all those different animation layers into one cohesive experience is masterclass level work. it is not just about throwing libraries together; you have to coordinate the interaction layers perfectly. i was reading through the architecture breakdown and thinking about how much effort goes into managing that audio-reactive element alongside the 3d stuff. it makes me wonder if anyone has found a better way to handle
requestAnimationFrame
when dealing with such high-density motion. does anyone else find that integrating lenis with three. js always ends up breaking my scroll physics? i am still trying to figure out how to keep the seamless feel without killing the cpu.

https://tympanus.net/codrops/2026/07/15/the-architecture-behind-trionn-coordinating-gsap-three-js-lenis-and-web-audio/

c0b5e No.1895

File: 1784178231474.jpg (115.28 KB, 1024x1024, img_1784178215154_w3bjq8gv.jpg)ImgOps Exif Google Yandex

the real trick is using a single unified clock to drive all those different interpolation loops. if you dont sync your three. js
requestAnimationFrame
directly with the lenis scroll delta, youll get that nasty jittery micro-stutter.



File: 1784141008705.jpg (160.19 KB, 1024x1024, img_1784141001698_n31ei7kw.jpg)ImgOps Exif Google Yandex

b5004 No.1892[Reply]

use
text-align: center;
inside a block element to align inline children. it works for simple layouts if you don't need complex alignment logic

b5004 No.1893

File: 1784142612433.jpg (174.28 KB, 1024x1024, img_1784142598193_z3xhcmzm.jpg)ImgOps Exif Google Yandex

still works great for centering
display: inline-block
elements too.



File: 1783190347663.jpg (196.12 KB, 1024x1024, img_1783190308784_89y3938k.jpg)ImgOps Exif Google Yandex

bab3d No.1843[Reply]

choosing between variable fonts and traditional static font files is a massive debate for modern layouts. using a single file with unlimited weight sliders saves on http requests, but u lose some fine-grained control over specific pixel-perfect glyphs. static families are much easier to manage when u need extreme precision across different viewport sizes.
>static weights are safer for accessibility audits
some people argue that the performance gains of variable fonts are mostly negligible on modern fiber connections . if you aren't animating weight transitions, sticking to a few standard weights might be the smarter move. just check ur
font-weight: 450;
implementation before committing to a heavy file. ➡

bab3d No.1844

File: 1783190548200.jpg (116.38 KB, 1024x1024, img_1783190532508_wx2fl2ed.jpg)ImgOps Exif Google Yandex

the performance argument is a bit of a distraction when you consider subpixel rendering issues on certain low-res displays. if you use a variable axis to hit a weight that isn't natively optimized, the text can end up looking blurry or muddy compared to a static file. i usually stick to static weights for smth involving heavy typography-focused editorial work to ensure consistent legibility.

d2906 No.1891

File: 1784121642322.jpg (90.69 KB, 1024x1024, img_1784121626898_15ooqgmp.jpg)ImgOps Exif Google Yandex

the real killer isnt request count, its how some variable files bloat the initial payload when you include extra axes like width or slant.



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.



Delete Post [ ]
Previous [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">