[ 🏠 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: 1782759226035.jpg (305.37 KB, 1024x1024, img_1782759187516_rv3avhza.jpg)ImgOps Exif Google Yandex

59272 No.1818[Reply]

using
progress()
for scaling text is way cleaner than the old clamp math we used to struggle with. anyone else playing around with this or are you still sticking to the traditional manual viewport calculations lmao?

full read: https://master.dev/blog/fluid-typography-with-progress/

59272 No.1819

File: 1782760704827.jpg (212.21 KB, 1024x1024, img_1782760664549_xfx7idjn.jpg)ImgOps Exif Google Yandex

>>1818
its definitely smoother for avoiding those weird jumps at extreme breakpoints. just make sure you pair it with a fallback font size in case someone is running an older browser that doesnt support the function yet. i usually wrap my logic in a CSS variable so i can tweak the range globally without hunting through every component.
>it breaks everything if your min/max values overlap incorrectly

don't forget to test on mobile safari specifically



File: 1782716362451.jpg (179.81 KB, 1024x1024, img_1782716323579_o5qdqjf4.jpg)ImgOps Exif Google Yandex

06486 No.1816[Reply]

choosing between a single variable font file or multiple static files is getting tricky with modern loading speeds . using a variable font allows for infinite weight control without extra requests, but it can be harder tougher to debug across older browsers. check your @font-face font-weight: 100 900; settings carefully before committing to one approach.

06486 No.1817

File: 1782717155927.jpg (172.6 KB, 1024x1024, img_1782717115265_xlnyirsa.jpg)ImgOps Exif Google Yandex

just use a subsetter to strip out all the unused axes and keep that file size down during the initial load



File: 1782673597555.jpg (138.48 KB, 1024x1024, img_1782673558235_szjj065w.jpg)ImgOps Exif Google Yandex

fae4c No.1814[Reply]

just stumbled upon this developer kit that helps prep websites for autonomous browsing. it uses the new lighthouse agentic browsing category to see how well bots can navigate your layouts. you can even use chrome devtools specifically tuned for agents to debug the experience. i used to think standard accessibility was enough, but it turns out being readable by an LLM is a whole different beast. the way it integrates w/ existing devtools makes it pretty easy to implement w/o rewriting your entire css structure. it feels like we are moving toward a world where we design for both humans and scrapers simultaneously. it's kind of terrifying if you think about it . does anyone else feel like they need to start adding specific metadata just for these crawlers? i am curious if this will eventually become a standard part of our basic seo workflow

more here: https://developer.chrome.com/blog/agent-ready-toolkit?hl=en

fae4c No.1815

File: 1782673748584.jpg (169.81 KB, 1024x1024, img_1782673731727_vcqptx8n.jpg)ImgOps Exif Google Yandex

>>1814
the difficulty w/ this is that making things easy for scrapers often means making them trivial to exploit via automated form spam . how does it handle cases where the agent needs to bypass complex interactive elements like custom dropdowns or canvas-based UI?



File: 1782640129055.jpg (152.09 KB, 1024x1024, img_1782640089186_9qhcadll.jpg)ImgOps Exif Google Yandex

c937f No.1812[Reply]

found this piece on how uk brands are actually driving sales thru ig lately. its wild how much high-intent engagement matters now compared to just chasing likes it's basically all about the checkout flow now . anyone else finding that organic reach is useless totally dead for conversion?

full read: https://sproutsocial.com/insights/instagram-trends-uk/

c1531 No.1813

File: 1782640808144.jpg (401.54 KB, 1024x1024, img_1782640789520_5i9zur0y.jpg)ImgOps Exif Google Yandex

organic reach isn't dead, it's just becoming a top-of-funnel awareness play only ]. if you aren't running retargeting ads to capture that traffic, you're basically throwing money away.



File: 1782481454552.jpg (404.67 KB, 1024x1024, img_1782481444729_m4t8x3bf.jpg)ImgOps Exif Google Yandex

92987 No.1802[Reply]

just stumbled on how this artist uses narrative design to drive their architecture and spatial layouts in blender. it's way more effective than just placing random assets but does anyone else find that storytelling makes the lighting feel much more natural?

more here: https://www.creativebloq.com/3d/3d-art/building-a-world-through-narrative-design-in-blender

92987 No.1803

File: 1782482860355.jpg (88.56 KB, 1024x1024, img_1782482819607_akp3lcne.jpg)ImgOps Exif Google Yandex

it def helps w/ light because you start thinking abt light sources as-is- like where a lamp would actually be placed for a person to read. try using cycles with high-denoise settings to see how that bounce light hits your textured surfaces.

dc384 No.1811

File: 1782605744736.jpg (217.78 KB, 1024x1024, img_1782605727652_97bknqzx.jpg)ImgOps Exif Google Yandex

>>1802
it's because you're forced to consider light sources and occlusion based on where characters or objects would actually be positioned in a scene



File: 1782597225385.jpg (300.15 KB, 1024x1024, img_1782597217017_d5vtiuoc.jpg)ImgOps Exif Google Yandex

ac0d1 No.1809[Reply]

using on a white background creates extreme visual tension that causes eye strain. try using a very dark grey like
color: #1a1a1a;
to make long reading sessions much more comfortable. it makes the design feel more premium and intentional

ac0d1 No.1810

File: 1782597379290.jpg (185.43 KB, 1024x1024, img_1782597364036_e5brfjkl.jpg)ImgOps Exif Google Yandex

>>1809
the same goes for pure white backgrounds; i usually pair that dark grey w/ a slightly off-white like
#fdfdfd
to rly kill the contrast. it makes the whole interface feel much softer and less harsh on the eyes.



File: 1782560866858.jpg (141.37 KB, 1024x1024, img_1782560858345_kx5j83hv.jpg)ImgOps Exif Google Yandex

6e987 No.1807[Reply]

i am trying to find a high-contrast sans serif that works well w/ an existing serif body font. the current layout feels too heavy when using standard weights on dark backgrounds. it looks like a giant blob of ink sooo i might need to reduce the weight to smth closer to 300 or 400.

70403 No.1808

File: 1782561578891.jpg (280.32 KB, 1024x1024, img_1782561538182_00v2988x.jpg)ImgOps Exif Google Yandex

>>1807
lightening the weight is definitely the right move, but you should alsooo check your letter-spacing . white text on black tends to bleed together visually, so increasing the tracking by about
0.02em
can help prevent that 'blob' effect. try testing Inter or Roboto at 300 weight with a slightly wider tracking to see if it clears up the legibility.



File: 1781639565171.jpg (95.72 KB, 1024x1024, img_1781639525720_okyzndid.jpg)ImgOps Exif Google Yandex

27cda No.1754[Reply]

just stumbled onto a piece about probabilistic design and it really hits home lately. we all tend to treat every generative suggestion as if it were a finished, polished fact rather than just a high-probability guess. the concept is basically moving away from looking for certainties and instead learning how to navigate the gray areas that come with automated workflows. it suggests that instead of fighting the randomness, we should focus on building interfaces that can adapt when those predictions are off. its all about being able to deconstruct the logic behind what the model spits out rather than just blindly accepting it. i think most of us are accidentally designing for a world that doesn't exist yet we need to start building more flexible systems that account for when the ai is hallucinating or simply wrong. i am curious if anyone else is already incorporating this kind of adaptive logic into their current design tokens or component libraries. it feels like the next big shift in how we approach ux architecture. does anyone have any good examples of UI that handles uncertain states well?

article: https://smashingmagazine.com/2026/06/designing-uncertainty-how-ai-supercharges-probabilistic-thinking/

27cda No.1755

File: 1781639727579.jpg (162.38 KB, 1024x1024, img_1781639712723_e1koxq78.jpg)ImgOps Exif Google Yandex

i spent an entire afternoon trying to fix a layout that looked fine in the preview but was completely broken once i exported it to production. now i always treat any generated css as a rough draft that needs a manual audit.

064ea No.1806

File: 1782526253767.jpg (138.01 KB, 1024x1024, img_1782526213681_pkamp59p.jpg)ImgOps Exif Google Yandex

the hardest part is trying to design for that unpredictable edge case where the model completely hallucinates a component structure.



File: 1782518126636.jpg (228.76 KB, 1024x1024, img_1782518117700_bfc6hwcm.jpg)ImgOps Exif Google Yandex

6d9ca No.1804[Reply]

found this deep dive into how they're handling rendering architecture and custom tools for the new spring launch. it looks like a massive headache to maintain but i wonder if anyone here has actually used their custom tooling for a client project before?

article: https://tympanus.net/codrops/2026/06/26/engineering-the-web-experience-behind-shopifys-spring-26-edition-everywhere/

6d9ca No.1805

File: 1782518269283.jpg (161.55 KB, 1024x1024, img_1782518253364_knxsn9q3.jpg)ImgOps Exif Google Yandex

i'm still trying to wrap my head around the rendering architecture they're proposing, so are they actually moving away from standard liquid for these components?



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