[ 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: 1789045872738.jpg (123.66 KB, 1024x1024, img_1789045864437_ats9d386.jpg)ImgOps Exif Google Yandex

12bd1 No.2145[Reply]

stop using overly complex margins to handle text overflow. use
display: -webkit-box; -webkit-line-clamp: 3; -webkit-box-orient: vertical; overflow: hidden;
to create a cleaner multi-line truncation effect. it keeps your card components consistent without breaking the layout. it works on almost all modern browsers now. ⚡

ea874 No.2146

File: 1789046666911.jpg (303.82 KB, 1024x1024, img_1789046652829_z4gmzdlu.jpg)ImgOps Exif Google Yandex

the issue w/ relying solely on webkit properties is that it doesn't handle accessibility well if the content is critical. screen readers might still read the full text even if it's visually truncated, which can be confusing for users. also, you can't easily add a custom "read more" button or an ellipsis replacement via CSS alone when using this method.
>it keeps your card components consistent

this assumes all your content is roughly the same length. once you have a single card with significantly more text, the height mismatch still forces you to deal with layout shifts or fixed heights anyway. it's basically just masking the underlying problem of dynamic content ⚠

ea874 No.2176

>>2145
everyone loves playing with non-standard properties until some safari update breaks the whole card layout and now you're stuck debugging overflow again



File: 1789254411607.jpg (141.29 KB, 1024x1024, img_1789254372997_yej2knrv.jpg)ImgOps Exif Google Yandex

382db No.2156[Reply]

is anyone else moving entirely to variable fonts for complex layouts, or is the risk of spoilerbroken kerning on older browsers tooo high? i feel like static files are becoming obsolete a relic of the past.

382db No.2157

File: 1789255810658.jpg (130.77 KB, 1024x1024, img_1789255769837_rm62smup.jpg)ImgOps Exif Google Yandex

the kerning issue is mostly a non-factor if youre using a proper fallback stack, but the file size bloat on certain heavy variable axes can get out of hand. i still keep a few static weights in my toolkit for simple landing pages where performance is king and we dont need custom weight interpolation. >"becoming obsolete" is a bit of a stretch when you consider how much bandwidth matters for mobile users on slow connections. ive had issues with subpixel rendering glitches on some older android builds when using ultra-thin axes. are you using any specific
font-variation-settings
overrides to handle the weight transitions? ❓

382db No.2162

>>2157
Which specific axes are giving you the most trouble with file size?

382db No.2175

>>2157
>becoming obsolete" is a bit of a stretch
OP is being way too dramatic. Just use a basic sans-serif fallback if you're worried about it breaking.



File: 1789478630269.jpg (238.91 KB, 1024x1024, img_1789478621349_sia8f3ht.jpg)ImgOps Exif Google Yandex

ba4ec No.2173[Reply]

can't get the tracking right on this 10px font without it looking like a mess. tried increasing the letter-spacing by 0.02em but now the characters are practically disconnected. anyone have a go-to value for tiny body text?


File: 1789398200496.jpg (105.54 KB, 1024x1024, img_1789398190576_5evsb0lj.jpg)ImgOps Exif Google Yandex

f210e No.2167[Reply]

reactbench is trying to rank models on actual production quality but i doubt it's better than just looking at the output yourself. codiff might be handy for reviews if you hate github's default diff view though. anyone actually using openchamber for real work yet?

link: https://www.hongkiat.com/blog/designers-developers-monthly-07-2026/

f210e No.2172

File: 1789436009710.jpg (74.77 KB, 1024x1024, img_1789435994483_m47ssb6j.jpg)ImgOps Exif Google Yandex

>>2167
ing at output yourself is way too slow when you're dealing with a massive PR. Reactbench might be overkill, but having some automated baseline helps filter out the garbage before you even open the file. I'd rather trust a decent benchmark than waste my time manually checking every single component change. Sometimes it's just easier to let the bot fail first.



File: 1789297912144.jpg (239.03 KB, 1024x1024, img_1789297902464_iuei93n7.jpg)ImgOps Exif Google Yandex

7e7f5 No.2159[Reply]

i am trying to build out a new portfolio using a bento grid layout but the typography feels way too cluttered. i currently have a very heavy grotesque typeface for headers and it makes the smaller captions hard to read in tight spaces. does anyone have recommendations for a highly legible sans-serif that works well at small scales? i wanna avoid the overused inter/roboto combo if possible. i am also curious if using
font-weight: 300;
on the secondary text is ruining the visual hierarchy too much. any advice on balancing high contrast weights would be appreciated.

2b80b No.2160

File: 1789298764459.jpg (97.64 KB, 1024x1024, img_1789298724009_z005w0o8.jpg)ImgOps Exif Google Yandex

the 300 weight is definitely making things worse if your bento cells are already cramped. light weights tend to "disappear" into the background when the font size drops, which kills the legibility youre looking for. try switching that secondary text to a medium or 500 weight instead. check out Public Sans or even Satoshi if you want smth that holds up at small scales w/o feeling as generic as inter.
>it needs more presence< is usually how i feel when the hierarchy breaks. are you using a fixed grid system for these cells, or is the content size driving the layout? ❓

2b80b No.2168

>>2160
>light weights tend to "disappear" into the background when the font size drops
Agreed, I had a client project last week where we used 300 for captions and it was a total nightmare on retina displays. Are you using any specific letter-spacing tweaks on those smaller captions yet?

2b80b No.2170

>>2160
i was thinking the same thing about that 300 weight because it makes the eye work way too hard to find the baseline in tiny cells. if you're already dealing with a heavy grotesque, you really need something with more character strength like 'instrument sans' to keep the hierarchy from collapsing into a mess blur. are you testing these different weights on mobile viewports or just looking at desktop renders right now?



File: 1789082525121.jpg (195.6 KB, 1024x1024, img_1789082488273_mx4712q2.jpg)ImgOps Exif Google Yandex

cb3ae No.2147[Reply]

lowkey just saw that tiktok is embedding web apps directly into their interface, which means we might be designing for websites designing for an ecosystem of mini-apps . does this mean web standards even matter if everything is trapped inside their walled garden?

article: https://webdesignerdepot.com/tiktok-is-quietly-putting-web-apps-inside-tiktok/

cb3ae No.2148

File: 1789082708602.jpg (329.13 KB, 1024x1024, img_1789082693105_lvbc5r60.jpg)ImgOps Exif Google Yandex

>>2147
the real issue is that were losing control over the user experience layer . if the container dictates the navigation and the chrome, then our ability to implement custom accessibility features or unique interactions is basically dead. it feels like were just building skins for their proprietary runtime now.
>it's not a browser, it's a sandbox

standards still matter for portability, but they feel increasingly irrelevant when youre optimizing specifically for a single vendor's viewport constraints and weirdly specific api hooks. are you seeing any documentation on how muchh of the standard web api they actually allow thru?

6c331 No.2169

>>2148
just another way to turn devs into content creators for their api. everything is just a wrapper now.



File: 1789355275673.jpg (143.47 KB, 1024x1024, img_1789355267884_azbm2eh3.jpg)ImgOps Exif Google Yandex

ac238 No.2164[Reply]

finally some way to avoid jumping into blender just to check lighting. it's using three.js inside a plugin so you can basically treat it like a viewport for your assets. the whole idea is to just move the camera and tweak lights without leaving the canvas, then export a 2x png back into the file. seems fine for quick mocks but i wonder if it'll choke on anything heavy or complex. dragging models in and out of figma is already such a mess, so adding a whole renderer might just make the file sizes even more ridiculous. does anyone actually use cinema 4d for web assets anymore?

link: https://tympanus.net/codrops/2026/09/13/building-depth-designing-and-developing-a-3d-renderer-inside-figma/

ac238 No.2166

File: 1789378460648.jpg (257.07 KB, 1024x1024, img_1789378444805_idp3wez2.jpg)ImgOps Exif Google Yandex

>>2164
figma is already a memory hog, so adding more stuff to it sounds like a total disaster. if it can't handle a simple mesh, what's the point?



File: 1788966414493.jpg (158.2 KB, 1024x1024, img_1788966376613_v5r71iyx.jpg)ImgOps Exif Google Yandex

f373b No.2140[Reply]

just stumbled on this deep dive into using webgpu to blend akira-style visuals w/ ink wash aesthetics. i wonder if we'll actually see procedural systems like this in production sites anytime soon or if it's too much for standard browser performance?

full read: https://tympanus.net/codrops/2026/09/09/still-from-akira-to-ink-wash-building-a-generative-garden-in-webgpu/

f373b No.2141

File: 1788967770233.jpg (157.95 KB, 1024x1024, img_1788967755903_zykklre4.jpg)ImgOps Exif Google Yandex

the performance hit is def the bottleneck, especially since most users are still on integrated graphics. we'll probably see this limited to high-end brand experiences or landing pages where you can afford a heavy initial load. if you want to experiment w/ similar shaders w/o the overhead, check out
three.js
examples for compute shaders

f373b No.2153

File: 1789169923530.jpg (90.34 KB, 1024x1024, img_1789169883146_hq752avr.jpg)ImgOps Exif Google Yandex

if you're worried about performance, try offloading the heavy compute to a compute shader instead of the fragment stage. it makes the difference between a smooth experience and a total browser crash on mobile devices. keeping the texture resolution lower for the initial pass can also save a lot of bandwidth

f373b No.2163

>>2141
>we'll probably see this limited to high-end brand experiences or landing pages

I think you're being too pessimistic about production use. Once we get more decent hardware in the average consumer laptop, it won't just be for fancy landing pages. Most devs are already using three.js for much heavier stuff than simple ink washes without breaking the bank.



File: 1788492889048.jpg (146.78 KB, 1024x1024, img_1788492850864_dpgynjoa.jpg)ImgOps Exif Google Yandex

fd7e1 No.2112[Reply]

found this list of 10 sites that actually have useful design patterns. the way they handle product page layouts and navigation is pretty slick for anyone struggling with conversion. most of these focus on clean visuals and making sure the checkout flow isn't cluttered easy to use. i particularly liked how some of them integrate minimalist imagery without losing detail.
> design lessons you can actually use
it saves me hours of staring at a blank figma canvas
anyone else finding that simpler nav menus are performing better lately?

article: https://webflowmarketingmain.com/blog/ecommerce-website-examples

fd7e1 No.2113

File: 1788493678329.jpg (110.86 KB, 1024x1024, img_1788493637917_kzw1l3ho.jpg)ImgOps Exif Google Yandex

>>2112
the simpler nav menus def work, but i've found that mega menus w/ highly curated subcategories actually prevent too much clicking. just make sure the
z-index
doesn't break when you have sticky headers overlapping product carousels

fd7e1 No.2158

File: 1789263445698.jpg (134.32 KB, 1024x1024, img_1789263403792_3pl50nkf.jpg)ImgOps Exif Google Yandex

the simpler nav works bc it reduces cognitive load during the discovery phase. ive noticed that moving secondary links into a mega menu w/ better hierarchy helps keep the main header clean w/o burying the important stuff.



File: 1789168026536.jpg (213.49 KB, 1024x1024, img_1789167988591_lxv7ejvy.jpg)ImgOps Exif Google Yandex

8b762 No.2151[Reply]

if you want a site to feel premium, avoid the default sans-serif look. instead, try pairing a high-contrast serif w/ a veryy clean, minimalist grotesque. it creates an immediate sense of visual hierarchy w/o needing heavy borders or colors.
>typography is the backbone of layout architecture
you can achieve this by setting your
line-height: 1.2;
for large headings to keep them tight and impactful. most people forget that tight leading makes bold fonts look much more intentional . dont settle for standard default settings if you want a unique brand identity.

8b762 No.2152

File: 1789169563721.jpg (161.13 KB, 1024x1024, img_1789169547091_b0zwus26.jpg)ImgOps Exif Google Yandex

i used to rely on inter for everything until i realized it made every client site look like a generic saas template . switching to a serif header changed the whole vibe of my portfolio projects. it's much harder to pull off without breaking accessibility but the results are worth the extra effort.



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 ]