[ 🏠 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: 1789557998322.jpg (101.08 KB, 1024x1024, img_1789557989361_t1fthqt5.jpg)ImgOps Exif Google Yandex

470c7 No.2177[Reply]

some guy's actually considering ditching his local installs for just a browser. he's talking about figma and even photoshop online like they're perfect enough to replace desktop powerhouses. i'm pretty skeptical because once you need heavy lifting, web standards still feel like a joke. ime seeing more of this trend though and it's getting annoying.

more here: https://speckyboy.com/browser-based-apps-enough-web-designers/


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: 1789521413318.jpg (213.21 KB, 1024x1024, img_1789521405626_9srwhks7.jpg)ImgOps Exif Google Yandex

8bf39 No.2174[Reply]

I just stumbled on this list of icon sites and lucide's packages for stuff like svelte and astro are honestly so convenient. Iconsax looks pretty wild with that ai generation feature too, but I wonder if the sheer volume makes it hard to stay consistent without a huge Figma plugin.

full read: https://www.hongkiat.com/blog/icon-pack-websites-designers-should-bookmark/


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: 1789435820075.jpg (269.79 KB, 1024x1024, img_1789435811410_mp1al3cg.jpg)ImgOps Exif Google Yandex

5a0a7 No.2171[Reply]

everyone's obsessed with those thin strokes but try using a 2px radial-gradient instead of just border-color. it makes the edges look way more organic than that fake glassmorphism nonsense. i'm testing it on some simple div containers today to see if it actually holds up without looking messy


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.



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