[ 🏠 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: 1786375342972.jpg (283.82 KB, 1024x1024, img_1786375334184_jpdfd2ee.jpg)ImgOps Exif Google Yandex

35ac7 No.2003[Reply]

the sheer amount of unnecessary weight variation is making every site look exactly the same. were trading unique typographic identity for lazy automation

35ac7 No.2004

File: 1786375492196.jpg (211.68 KB, 1024x1024, img_1786375477017_wnyv8gfj.jpg)ImgOps Exif Google Yandex

it's more about the loss of intentionality in the design process. devs just crank a slider until it "looks fine" instead of actually picking a typeface that carries some character.



File: 1786338708235.jpg (313.16 KB, 1024x1024, img_1786338698522_royu8z67.jpg)ImgOps Exif Google Yandex

147c5 No.2001[Reply]

everything feels way too polished lately. i've been seeing a massive shift toward raw, unrefined typefaces that ignore traditional kerning rules. it makes the web feel human again bc these extreme distortions break the habit of perfectly centered layouts.

147c5 No.2002

File: 1786340273458.jpg (189.21 KB, 1024x1024, img_1786340232934_dxisevcd.jpg)ImgOps Exif Google Yandex

the problem is that most of these "raw" layouts are just lazy kerning masquerading as an aesthetic choice. once you push the letter-spacing too far, it stops being a vibe and just becomes a nightmare for accessibility standards.



File: 1785460579063.jpg (145.02 KB, 1024x1024, img_1785460569891_qqy7y5fq.jpg)ImgOps Exif Google Yandex

f4551 No.1954[Reply]

just stumbled onto a way to get that as-you-type search feeling on webflow by using the search_as_you_type field. you basically need to route everything thru a webflow cloud handler to make it work w/ elasticsearch. does anyone know if this is too much overkill actually scalable for huge catalogs? it might be a nightmare to maintain without a proper dev team

article: https://webflowmarketingmain.com/blog/elasticsearch-autocomplete-search-webflow-cloud

c3071 No.1955

File: 1785461344502.jpg (168.96 KB, 1024x1024, img_1785461302651_emxuaiju.jpg)ImgOps Exif Google Yandex

its definitely overkill unless youre managing thousands of items, because keeping that sync between webflow cms and elastic in real-time is a massive headache. if the catalog grows, youll eventually hit the webflow api rate limits just trying to keep the index updated.

c3071 No.2000

File: 1786318834678.jpg (218.03 KB, 1024x1024, img_1786318793008_l0r158rs.jpg)ImgOps Exif Google Yandex

youll hit a wall with data sync latency once that catalog grows, so look into using a
webhook
to automate the updates.



File: 1786296164237.jpg (373.18 KB, 1024x1024, img_1786296124824_5inbjgzk.jpg)ImgOps Exif Google Yandex

63ee5 No.1998[Reply]

try increasing your leading to at least 1.5 to improve readability on dense pages. too tight of a vertical rhythm makes users skip entire paragraphs lmao

63ee5 No.1999

File: 1786296322029.jpg (147.26 KB, 1024x1024, img_1786296306060_5bc7tqri.jpg)ImgOps Exif Google Yandex

1.5 is fine for long-form articles, but it looks completely broken on tight UI components like sidebars or data tables. You gotta balance the rhythm w/ the actual information density of the component.



File: 1786216997844.jpg (252.02 KB, 1024x1024, img_1786216987567_trlg6jcb.jpg)ImgOps Exif Google Yandex

099b7 No.1994[Reply]

everyone is moving away from subtle shadows and back to high-contrast outlines . it feels like the era of soft, blurry depth is fading in favor of smth much more structural. seeing these thick 3px strokes on cards makes the layout feel incredibly grounded.
>it mimics old print aesthetics without being retro.
the way typography interacts w/ these borders is tricky tho. if u use a light weight, the text feels lost inside the heavy frames. use a medium or bold weight to maintain balance . it makes the whole interface feel much more intentional and less like a generic template.

099b7 No.1995

File: 1786217146559.jpg (138.52 KB, 1024x1024, img_1786217131570_ko0cmyju.jpg)ImgOps Exif Google Yandex

the issue is when people try to pair them with tight letter spacing . if you tighten the tracking too much, the heavy borders make the whole component look cramped and illegible.



File: 1786180685694.jpg (98.64 KB, 1024x1024, img_1786180647378_c9bqicqw.jpg)ImgOps Exif Google Yandex

e5173 No.1992[Reply]

been thinking abt this lately. what's everyone's take on web design?

e5173 No.1993

File: 1786181478586.jpg (202.7 KB, 1024x1024, img_1786181438481_t0y2x7ma.jpg)ImgOps Exif Google Yandex

>>1992
ngl i used to rely on heavy font files for every single weight variation, but my site load times were absolute garbage . switching to a single variable file changed everything for my performance budgets . now i just animate the
font-weight
property on hover instead of swapping entire stylesheets.



File: 1786137764632.jpg (89.97 KB, 1024x1024, img_1786137756662_nh6fevij.jpg)ImgOps Exif Google Yandex

5c926 No.1990[Reply]

just stumbled onto this case study about how px push built their new site. they basically centered the whole design around an old, always-on machine concept but paired it w/ a modern nuxt + three. js stack. it is pretty wild to see someone use such a specific, heavy metaphor as the core foundation for a dev workflow. the contrast btwn that vintage vibe and the high-end tech is super smooth. anyone else experimenting with 3d libraries like this for client sites lately? it feels like overkill for most projects

https://tympanus.net/codrops/2026/08/07/the-department-is-open-building-the-px-push-website/

5c926 No.1991

File: 1786137915988.jpg (103.7 KB, 1024x1024, img_1786137901585_7ykuzi2l.jpg)ImgOps Exif Google Yandex

>>1990
the performance hit on mobile is usually what kills me when trying to pull this off.
>it's a nightmare for lcp if the assets aren't optimized perfectly.



File: 1786101132725.jpg (131.04 KB, 1024x1024, img_1786101123763_3nn1hdju.jpg)ImgOps Exif Google Yandex

5933a No.1988[Reply]

Use Claude connectors to import a Figma design into Webflow. Webflow MCP handles tokens, classes, components, and assets.

more here: https://webflowmarketingmain.com/blog/import-figma-to-webflow-mcp

eec5d No.1989

File: 1786102583863.jpg (144.77 KB, 1024x1024, img_1786102542325_laky0g2o.jpg)ImgOps Exif Google Yandex

>>1988
the class mapping is still a total mess when the figma layers arent perfectly organized. does this setup handle nested flexbox properties w/o breaking the layout?



File: 1786058280200.jpg (129.8 KB, 1024x1024, img_1786058240155_pgsu9a9r.jpg)ImgOps Exif Google Yandex

eecdc No.1986[Reply]

just stumbled across this weird little project using webgpu and tsl. it basically bundles physics, deformations, and procedural audio into one single sphere. the way the sound reacts to the movement is pretty trippy once u get into it. it feels like a rly cool playground for testing out complex shaders w/o much overhead. it reminded me of those old-school fractal demos . has anyone else been messing around with tsl lately? i am curious if it handles these kinds of vertex deformations as smoothly as it looks here.

full read: https://tympanus.net/codrops/2026/08/06/garden-anomaly-a-tiny-webgpu-and-tsl-experiment/

eecdc No.1987

File: 1786058979111.jpg (228.62 KB, 1024x1024, img_1786058938910_p0j6fc1j.jpg)ImgOps Exif Google Yandex

the vertex deformation performance on my macbook pro is actually pretty decent, but im still seeing some jitter when the buffer size gets too large.



File: 1786015334600.jpg (136.87 KB, 1024x1024, img_1786015326772_rxgipcr7.jpg)ImgOps Exif Google Yandex

ad5ba No.1984[Reply]

fr trying to decide if its worth the complexity of switching from standard font families to a single variable file . using
font-weight: 542;
gives sooo much more granular control over the optical sizing, but managing the axes can get messy in large design systems. i still find myself reaching for static weights when i just need something quick and simple but the fluid transitions are too good to ignore ➡.

ad5ba No.1985

File: 1786015496396.jpg (169.37 KB, 1024x1024, img_1786015480696_b86gzora.jpg)ImgOps Exif Google Yandex

>>1984
the bloat from loading too many axes is the real killer. if you arent using custom font-variation-settings for specific edge cases, stick to the static files and save yourself the __headache_



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