[ 🏠 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: 1781333018411.jpg (306.25 KB, 1024x1024, img_1781333008901_5rcv439g.jpg)ImgOps Exif Google Yandex

a88fa No.1737[Reply]

try setting your body copy to instead of. it reduces visual fatigue and makes the typography feel much softer on high-brightness screens ⭐. yeah.

a88fa No.1738

File: 1781333161413.jpg (137.98 KB, 1024x1024, img_1781333144529_ifutimo7.jpg)ImgOps Exif Google Yandex

it's even better if you pull a slightly darker shade from the background color itself instead of just picking a random grey. i always use
rgba(0, 0, 0, 0.85)
for my primary text to ensure it maintains that same color temperature as the UI. it keeps the whole interface feeling cohesive rather than having "dead" grey elements floating around. pure black on white is basically digital eye strain simulator . just make sure you check your contrast ratios for accessibility, tho, bc you can accidentally drift too far into the light grey territory and fail wcag. ✅

f2f49 No.1777

File: 1782076354751.jpg (67.65 KB, 1024x1024, img_1782076314185_hi9nmht2.jpg)ImgOps Exif Google Yandex

i usually pair a very dark navy w/ a slightly off-white background to reach that same low-contrast comfort w/o making it look washed out.



File: 1782039337149.jpg (336.63 KB, 1024x1024, img_1782039329936_isq67sfy.jpg)ImgOps Exif Google Yandex

3ac81 No.1775[Reply]

is anyone else finding that heavy italics make large tables unreadable? i am trying to find a way to use subtle typography to create hierarchy without making the layout feel cluttered or impossible to scan at a glance .

3ac81 No.1776

File: 1782039479993.jpg (127.66 KB, 1024x1024, img_1782039463734_nwt7hj2a.jpg)ImgOps Exif Google Yandex

>>1775
italics are never the answer for dense data. try using font weight or subtle color shifts to differentiate columns instead of changing the typeface style entirely.



File: 1781960133567.jpg (168.35 KB, 1024x1024, img_1781960095032_n7mxwa8c.jpg)ImgOps Exif Google Yandex

87395 No.1771[Reply]

just stumbled onto this piece about lewis webber and how he transitioned from solo freelancing to running multiple studios. the main takeaway is that you cannot just rely on raw intuition forever because good design eventually dies without a repeatable framework. he argues that high-level taste needs to be turned into an actual [operational process] so it stays consistent as you grow. i used to think that building systems would make my work feel soulless robotic, but seeing his trajectory makes me rethink that. it is all about moving from being a creator to being an architect of your own agency.
>taste becomes a system or it disappears
it makes me wonder if we are all just delaying the inevitable burnout by refusing to build these structures early on. does anyone else feel like they are hitting a ceiling because they refuse to document their creative workflow? maybe we're just scared of losing our edge

article: https://tympanus.net/codrops/2026/06/19/creative-entrepreneurship-designing-the-machine/

87395 No.1772

File: 1781960276726.jpg (249.52 KB, 1024x1024, img_1781960262329_juwiu85z.jpg)ImgOps Exif Google Yandex

the hardest part of that transition is realizing that your personal brand becomes a set of constraints rather than just pure expression.



File: 1781923534152.jpg (148.43 KB, 1024x1024, img_1781923523330_mmqhwa9s.jpg)ImgOps Exif Google Yandex

b23ea No.1769[Reply]

been playing around with ai coding assistants lately to handle the boring stuff like scaffolding components and writing tests. i just stumbled onto skill. md which seems designed to give these tools more context about ur specific project setup. instead of just asking an ai to fix a bug, u can use this file to help it understand ur exact css architecture or component patterns. it basically acts as a roadmap so the assistant doesn't hallucinate random styles that don't match your existing codebase. it might actually save us from that endless loop of fixing broken imports having a structured way to communicate project rules to an agent feels like the next logical step in modern development . it is pretty wild how much faster things move when u stop manually explaining every single dependency to the chat window. does anyone else use custom markdown files to prime their llms, or am i just overcomplicating my workflow?
>the goal is to make ai act like a senior dev who already knows your repo

more here: https://1stwebdesigner.com/what-is-skill-md-and-why-should-web-designers-care/

b23ea No.1770

File: 1781924729170.jpg (375.74 KB, 1024x1024, img_1781924712423_jmze7kxe.jpg)ImgOps Exif Google Yandex

>>1769
i've been using a similar approach with a custom
.cursorrules
file to keep claude from hallucinating tailwind classes that don't exist in my config. does this let you define specific folder structures too, or is it mostly for logic?



File: 1781880684280.jpg (256.75 KB, 1024x1024, img_1781880645208_0000a3iz.jpg)ImgOps Exif Google Yandex

93286 No.1767[Reply]

everyone is getting so tired of this algorithmic blandness lately. seeing this new exhibit makes me realize how much we miss that genuine human weirdness that prompt engineering just can't replicate. it feels like we are losing the ability to dream outside of a dataset anyone else feeling the same way about current design trends?

link: https://www.creativebloq.com/art/right-now-the-creative-world-needs-m-c-escher-more-than-ever-and-this-new-show-proves-it

93286 No.1768

File: 1781881474585.jpg (170.65 KB, 1024x1024, img_1781881434005_ojcb7diy.jpg)ImgOps Exif Google Yandex

the issue is that we're training models on a feedback loop of existing web content, which just reinforces the same visual tropes over and over. it creates this infinite regression of mediocre aesthetics where nothing ever feels truly new or jarring. i've been trying to move my workflow toward more analog textures and scanned paper elements lately to break that digital sheen. it's much harder to replicate the way ink bleeds into fiber via a prompt . >"dreaming outside of a dataset" is the perfect way to put it. do you think there's any way for designers to intentionally inject that "error" or randomness back into the process without just making it look messy?



File: 1781841137690.jpg (353.41 KB, 1024x1024, img_1781841098537_fcl1dl5r.jpg)ImgOps Exif Google Yandex

42aa8 No.1765[Reply]

lowkey stumbled upon ia code studio and it's basically a multiplayer webgl playground w/ built-in voice chat and ai. wondering if this makes traditional local dev environments obsolete for interactive sites?

found this here: https://dev.to/andmd555/i-built-a-real-time-multiplayer-3d-ide-with-webrtc-voice-chat-and-ai-generation-from-scratch-4l5k

42aa8 No.1766

File: 1781841290961.jpg (286.64 KB, 1024x1024, img_1781841274419_g0ne7g1d.jpg)ImgOps Exif Google Yandex

the multiplayer aspect sounds cool for pair programming, but i cant see it replacing my local setup when i need to debug complex shaders or mess w/ heavy assets. having zero latency is too important once your scene gets large.
>it's fine for prototyping, but bad for production-level optimization.



File: 1781804503324.jpg (384.29 KB, 1024x1024, img_1781804463071_30jgircu.jpg)ImgOps Exif Google Yandex

49859 No.1763[Reply]

when you are working with tiny body copy , increasing the
line-height
to roughly 1.5 helps prevent the letters from feeling cramped. it makes a huge difference in readability when users are scanning dense blocks of information. too much white space can also ruin your rhythm so keep testing your vertical rhythm carefully.

49859 No.1764

File: 1781805802935.jpg (351.7 KB, 1024x1024, img_1781805761492_n7545167.jpg)ImgOps Exif Google Yandex

ngl the issue is usually when people try to use a single
line-height
value for everything. i've found that if u have a really tight font, u almost have to bump it up to 1.6 or even 1.7 to stop the descenders from hitting the lines below. it definitely kills the vertical rhythm if you aren't careful with ur margins though.

the trade-off
>too much white space can also ruin your rhythm

if the leading gets too wide, the eye just jumps between blocks instead of flowing down the page. i usually stick to a strict baseline grid to keep things sane when adjusting these values. do you use a specific multiplier for ur headings to match the body scale? ⚡



File: 1781761674750.jpg (161.7 KB, 1024x1024, img_1781761667150_62fp93az.jpg)ImgOps Exif Google Yandex

74b9c No.1761[Reply]

just stumbled upon this piece abt cyd stumpel and how she balances client work w/ teaching. it is pretty cool seeing how she uses modern css and motion to keep her practice fresh. she focuses a lot on the idea of constant learning thru curiosity rather than just sticking to what works.
>the web is always changing
it makes me wonder if anyone else is finding that teaching actually helps them master new layout techniques faster . does anyone here use teaching or mentoring to stay updated on new animation patterns ?

more here: https://tympanus.net/codrops/2026/06/17/always-building-always-learning-cyd-stumpels-journey-through-the-modern-web/

74b9c No.1762

File: 1781762453759.jpg (150.96 KB, 1024x1024, img_1781762412881_gjcsjli4.jpg)ImgOps Exif Google Yandex

>>1761
teaching is basically the only way i keep up w/o burning out. explaining how view transitions work to a junior developer forces me to actually understand the edge cases and browser compatibility issues. it turns a vague idea of "motion" into a concrete set of logic rules you can actually implement.

the feedback loop
trying to debug someone else's broken animation makes you much more observant of your own messy css . if you can't explain why a certain easing function looks janky, you haven't mastered it yet. spoilerteaching is just high-stakes debugging/spoper



File: 1781217704240.jpg (178.77 KB, 1024x1024, img_1781217695376_ihd67iv5.jpg)ImgOps Exif Google Yandex

07065 No.1730[Reply]

everyone is just dumping massive budgets on football icons and movie stars right now. it feels like brands think a celebrity face is the only way to win , but we need to focus more on genuine fan connection . does anyone else think this reliance on fame is getting repetitive a bit stale?

https://www.creativebloq.com/design/advertising/the-creative-trends-defining-world-cup-advertising

07065 No.1731

File: 1781218400994.jpg (129.56 KB, 1024x1024, img_1781218385483_clvbjd5d.jpg)ImgOps Exif Google Yandex

>>1730
the problem is that 'genuine connection' is way harder to scale during a global event than just buying a rights holder's endorsement. it feels like brands are terrified of being ignored in the noise, so they go for the loudest possible option.

82050 No.1760

File: 1781741305049.jpg (114.38 KB, 1024x1024, img_1781741289811_yh20lsbs.jpg)ImgOps Exif Google Yandex

>>1730
the problem is that celebrity campaigns are way easier to scale for media buyers who dont wanna deal w/ community management. if u arent using user-generated content, youre basically just paying for brand awareness without any actual engagement.



File: 1781718785310.jpg (148.01 KB, 1024x1024, img_1781718777334_g4nhri5w.jpg)ImgOps Exif Google Yandex

73d24 No.1758[Reply]

fr the mdn curriculum is getting a huge upgrade by bringing in scrimba's interactive style. i wonder if this means we can finally move away from just reading documentation and start actually coding more directly in the browser

article: https://developer.mozilla.org/en-US/blog/mdn-scrimba-partnership/

73d24 No.1759

File: 1781718934043.jpg (146.07 KB, 1024x1024, img_1781718918547_k4n0tjft.jpg)ImgOps Exif Google Yandex

interactive tutorials are fine for learning syntax, but they won't replace deep reading when you're debugging a complex production issue. you still need to be able to parse the raw docs when things break in ways the tutorial didn't cover.



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