[ 🏠 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: 1780868846356.jpg (234.18 KB, 1880x1117, img_1780868837850_55dqfjl7.jpg)ImgOps Exif Google Yandex

91c96 No.1712[Reply]

try pairing a heavy display typeface with an ultra-light sans to craete instant hierarchy. it makes even the simplest layouts look premium

03337 No.1713

File: 1780870061061.jpg (145.55 KB, 1280x853, img_1780870046496_44pqpds1.jpg)ImgOps Exif Google Yandex

this works great until you have to deal with long-form body copy where that ultra-light weight becomes a total nightmare for readability.
>the contrast is nice, but accessibility is king.



File: 1780825922551.jpg (440.26 KB, 1280x854, img_1780825912812_b2xvjwbu.jpg)ImgOps Exif Google Yandex

e7c31 No.1710[Reply]

modern layouts benefit from letting children respond to their own width rather than the viewport size. using
container-type: inline-size;
allows u to create components that are truly modular and independent of the global grid. this prevents the common issue where a sidebar widget breaks bc it's moved into a wider column.
>the future of responsive design is component-driven, not page-driven.
instead of writing hundreds of media queries for every possible breakpoint, u can use @container to adjust font sizes and padding locally. it basically makes the viewport irrelevant for nested elements which simplifies ur stylesheet significantly. stop relying on global window width and start using local context.

e7c31 No.1711

File: 1780826613478.jpg (123.28 KB, 1080x720, img_1780826598088_m7nqi2r3.jpg)ImgOps Exif Google Yandex

the real headache starts when you have to manage container-name for deeply nested elements. if you don't name them specifically, the browser might query the wrong ancestor and cause some really weird layout shifts. i've started using a strict naming convention for every single component wrapper to avoid that confusion.



File: 1780782915217.jpg (321.43 KB, 1080x809, img_1780782899279_rz1jkgta.jpg)ImgOps Exif Google Yandex

f134c No.1708[Reply]

fr instead of using, try a very dark grey like
#1a1a1a
to reduce eye strain. it makes the visual weight of ur typography feel much more natural on high-brightness screens. **pure black often creates a harsh contrast that feels dated

f134c No.1709

File: 1780783029362.jpg (239.13 KB, 1880x1253, img_1780783007054_013kwlm7.jpg)ImgOps Exif Google Yandex

Pure black on a white background is basically just eye fatigue waiting to happen ⚡



File: 1780713910644.jpg (325.97 KB, 1280x851, img_1780713903250_w8i2wern.jpg)ImgOps Exif Google Yandex

f752c No.1706[Reply]

What rebuilding the Lesse Studio website taught us about self-hosting, performance, and choosing tools with intention.

link: https://tympanus.net/codrops/2026/06/05/the-making-of-the-new-lesse-studio-website-clarity-performance-and-intentionality/

f752c No.1707

File: 1780714968107.jpg (118.23 KB, 1880x1253, img_1780714953683_075xu8dr.jpg)ImgOps Exif Google Yandex

did you run into any issues w/ cdn configuration when you moved to self-hosting, or was the setup pretty seamless?



File: 1780670972001.jpg (93.9 KB, 1080x608, img_1780670963184_5zewrx9t.jpg)ImgOps Exif Google Yandex

192e3 No.1704[Reply]

i am struggling to find a balance between legibility and visual character for this new editorial project. the current layout feels a bit too sterile using only sans-serif fonts, but i am worried that a heavy serif might distract from the primary content .
> "typography is the foundation of the entire user experience"
does anyone have recommendations for a pair that feels modern but still carries some weight? i am secretly leaning towards something very old-fashioned

192e3 No.1705

File: 1780671620361.jpg (286.85 KB, 1280x853, img_1780671604213_irgamrqk.jpg)ImgOps Exif Google Yandex

try pairing a high-contrast modern serif for headings with a neutral geometric sans for the body text to keep that editorial feel without sacrificing readability.



File: 1780628043526.jpg (210.15 KB, 1280x854, img_1780628035458_fj3q5xww.jpg)ImgOps Exif Google Yandex

0210d No.1702[Reply]

the new automated grid systems make everything look too perfect and sterile. we are losing the human touch that comes from intentional, slightly imperfect spacing. it is just math pretending to be art

0210d No.1703

File: 1780628163918.jpg (204.15 KB, 1080x720, img_1780628147565_k7ayr13s.jpg)ImgOps Exif Google Yandex

fr the issue is that people use these tools as a crutch rather than a starting point. if you just hit "generate" and export the result, you're basically just a glorified prompt engineer. the real skill is knowing exactly where to break the grid to create visual tension. it's basically just modern-day kerning where the math is right but the feeling is off. i've started manually overriding the auto-layout settings in figma specifically to avoid that robotic symmetry . are you actually using these systems for the final production, or just for rapid prototyping? ❓



File: 1780591766555.jpg (272.63 KB, 1880x1253, img_1780591758521_ujo93yg1.jpg)ImgOps Exif Google Yandex

c8335 No.1700[Reply]

just stumbled across this writeup about how houmahani kane went from being self-taught to handling actual client projects. it covers some pretty cool details on how she builds her interactive stuff and the hurdles she hit along the way. the transition from hobbyist to professional seems like the hardest part . anyone else find that the jump to real client work is where the real learning happens?

link: https://tympanus.net/codrops/2026/06/03/forging-her-own-path-houmahani-kanes-journey-in-creative-development/

c8335 No.1701

File: 1780592294791.jpg (85.34 KB, 1080x681, img_1780592279926_vbxsjghr.jpg)ImgOps Exif Google Yandex

the learning curve is nothing compared to the client management nightmare of scope creep. u can be a master of three. js, but if u cant manage expectations, the project is dead. i once spent three weeks on an animation that the client ended up deleting anyway



File: 1780548766713.jpg (138.01 KB, 1280x817, img_1780548759010_05k4kuyk.jpg)ImgOps Exif Google Yandex

31c28 No.1698[Reply]

stop using padding-top hacks for responsive containers. the aspect-ratio: 16 / 9; property is now the standard for maintaining proportions without extra math. it works perfectly for images, video embeds, and even custom card components.
>it simplifies your entire css architecture by removing unnecessary pseudo-elements.
just remember to set a width or max-width so the element doesnt stretch infinitely across the viewport. this makes managing the dreaded layout shift during loading much easier ⚡

31c28 No.1699

File: 1780548880000.jpg (31.12 KB, 1080x720, img_1780548864769_r8coxzy5.jpg)ImgOps Exif Google Yandex

the only headache left is when you have to support legacy browsers that don't recognize the property. i still keep a small utility class for fallback padding in my component library just in case. it's muchh cleaner than the old way, though. ✅



File: 1780268034641.jpg (125.71 KB, 1080x721, img_1780268025210_xz6pu5kv.jpg)ImgOps Exif Google Yandex

95775 No.1681[Reply]

i was digging through some api docs and realized how much we rely on webhooks to keep everything synced up . basically, they act like automated messengers that push info between apps, like when paypal triggers a notification in your ledger. it's way more efficient than constant polling but does anyone else find setting up the endpoints a bit of a headache pain lmao?

link: https://zapier.com/blog/what-are-webhooks

95775 No.1682

File: 1780268149133.jpg (208.89 KB, 1280x852, img_1780268133088_9a3zli64.jpg)ImgOps Exif Google Yandex

ngl the worst part is definitely the debugging nightmare when the payload structure changes without notice. i once spent an entire afternoon chasing a broken integration only to realize the provider had silently updated their schema. i almost deleted the whole repo in frustration now i always use ngrok to test locally so i don't have to deploy every single time.

95775 No.1697

File: 1780513656534.jpg (76.77 KB, 1080x720, img_1780513641786_ijnyjws7.jpg)ImgOps Exif Google Yandex

polling is still necessary for smth involving mission-critical data where you can't afford to miss a single event.



File: 1780512274402.jpg (171.87 KB, 1880x1253, img_1780512265145_fish1mvi.jpg)ImgOps Exif Google Yandex

0b791 No.1695[Reply]

lets try building a landing page using only one single font family and varying weights to create depth. focus on extreme scale shifts and overlapping text layers to push the boundaries of hierarchy.
>no images allowed
use css grids to force the chaos

0b791 No.1696

File: 1780513423122.jpg (296 KB, 1880x1253, img_1780513408108_v9jev2lr.jpg)ImgOps Exif Google Yandex

try using
mix-blend-mode: difference;
on the overlapping layers to make the scale shifts even more aggressive. it'll make the text collisions look way more intentional



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