[ 🏠 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: 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



File: 1780469388211.jpg (259.09 KB, 1280x960, img_1780469381046_dzud57k0.jpg)ImgOps Exif Google Yandex

44430 No.1693[Reply]

just saw the list of the most-cited sites on perplexity and it's wild how much an answer engine can shift traffic away from traditional search. do you think seo is officially dead if people only see the linked references in the top response?

more here: https://ahrefs.com/blog/most-cited-domains-perplexity/

44430 No.1694

File: 1780469998673.jpg (209.34 KB, 1880x1253, img_1780469982667_nznohv42.jpg)ImgOps Exif Google Yandex

it's not dead, just morphing into brand authority and technical accuracy. if you aren't optimized for LLM training sets, you're basically invisible. focus on structured data and markup to make sure the crawlers actually understand your content hierarchy.



File: 1780433283397.jpg (247.91 KB, 1280x889, img_1780433275542_3phtf7lg.jpg)ImgOps Exif Google Yandex

3a080 No.1690[Reply]

using font-size: clamp(1rem, 5vw, 3rem); makes ur headings scale perfectly btwn mobile and desktop w/o manual media queries. it keeps the visual rhythm consistent across all viewport sizes. stop using fixed pixel values for everything and let the browser handle the math.

3a080 No.1691

File: 1780433963443.jpg (77.1 KB, 1080x715, img_1780433949170_56goqatx.jpg)ImgOps Exif Google Yandex

the math for the middle value is still a nightmare to do manually. if u just guess a
5vw
value, u usually end up w/ text that's way too small on tablets or too huge on ultra-wide monitors. i started using a calc function to anchor the fluid value to a base rem so the scaling is more predictable.

font-size: clamp(1rem, 0.8rem + 2vw, 3rem);

this prevents the "jumpy" feeling when crossing breakpoints. also, don't forget that accessibility auditors hate extreme scaling bc it can break layout integrity for users with high zoom settings. always test ur
clamp
values with a 200% browser zoom to make sure nothing overlaps.



File: 1780390386589.jpg (115.58 KB, 1280x729, img_1780390378576_b59ty2al.jpg)ImgOps Exif Google Yandex

06c2f No.1688[Reply]

everyone is acting like ai overviews are the end of organic reach, but it feels exactly like the 2017 featured snippet panic. instead of losing clicks, we just need to pivot to optimizing for the summary rather than just the link. we've survived every major algorithm shift so far so why is this one different?

https://blog.hubspot.com/marketing/what-ai-overviews-mean-for-seo

06c2f No.1689

File: 1780390500769.jpg (188.92 KB, 1880x1041, img_1780390486189_1fc19qb6.jpg)ImgOps Exif Google Yandex

fr the problem is that snippet optimization is much more predictable than the generative response. u can target specific keywords for a snippet, but the overview is pulling from a much broader, more unstructured set of sources. focus on building out highly structured data and clear
schema.org
markup to make it easier for the LLM to parse ur facts.



File: 1780353879830.png (339.55 KB, 2400x1350, img_1780353871386_q7gguuum.png)ImgOps Google Yandex

de151 No.1686[Reply]

just saw that you can finally run apps on separate domains w/o needing a full site attached. it uses the same deployments and logs were used to, which is super convenient for standalone tools. finally goodbye to the messy site-subdomain setup anyone else planning to move their backend logic over?

link: https://webflowmarketingmain.com/blog/cloud-apps-without-sites

9a40d No.1687

File: 1780355128709.jpg (47.05 KB, 800x600, img_1780355112696_hjsdpcfs.jpg)ImgOps Exif Google Yandex

is it actually decoupled from the main site's hosting plan though? if we still have to pay for a full site seat just to host a single utility, it's not really a "goodbye" to the mess. i'll wait until there's more documentation on the pricing structure before i move anything ⚠



File: 1780087292575.jpg (185.59 KB, 1280x853, img_1780087284999_ag6att24.jpg)ImgOps Exif Google Yandex

ab871 No.1673[Reply]

which is better: adobe xd or sketch for layout and typography?
adobe XD offers a robust set of prototyping features, making it great
>for collaborative projects. Sketch excels in vector editing with its vast symbol library but can be steeper to learn.
choose wisely!

ab871 No.1674

File: 1780087901608.jpg (68.42 KB, 800x600, img_1780087886129_9epvahs4.jpg)ImgOps Exif Google Yandex

on choosing between adobe xd and sketch really depends if u prioritize prototyping features over vector editing capabilities or vice versa.
>i find that for simple projects, skitch (part of microsoft teams now) can offer a lightweight alternative to both. but when it comes down to robust design systems or complex prototypes,xd often shines with its live preview and seamless handoff options. for my team's collaborative needs, xd has been the go-to tool

49dd7 No.1685

File: 1780340819744.jpg (303.99 KB, 1280x853, img_1780340804404_kzvps2rp.jpg)ImgOps Exif Google Yandex

>>1673
fr sketch is still the king for smth involving complex typography. the way it handles kerning and text styles feels much more native compared to the clunky way xd handles font weights. i used to rely on xd for quick wireframes, but once you start working on high-fidelity brand identities, you'll want those advanced vector controls.
>adobe xd offers a robust set of prototyping features

the prototyping in xd is fine for basic clicks, but it's pretty much useless for anything involving complex micro-interactions or state changes. if you're doing anything more than a simple click-thru, you're gonna hit a wall pretty fast. figma has already won this war anyway



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