[ 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: 1791746127813.jpg (102.02 KB, 1024x1024, img_1791746119944_zmw76k13.jpg)ImgOps Exif Google Yandex

cf48f No.2309[Reply]

saw this list going around and it's mostly just stuff we've used for a decade. they're pushing Helvetica and Roboto like it's some big revelation. the advice on spacing is basically common sense.
>Use high-quality fonts.
it's basically just telling people to pay for licenses instead of using free stuff. seeing 'tremos' or 'miller' as the go-to for serious brands is pretty standard, but there's nothing really new here. honestly, it's all just the same old classics rebranded for a new year. does anyone actually use 'quicksand' anymore without it looking like a preschool flyer?

more here: https://speckyboy.com/logo-typeface-font/


File: 1791219574359.jpg (141.9 KB, 1024x1024, img_1791219565422_wt6wsled.jpg)ImgOps Exif Google Yandex

21a53 No.2272[Reply]

stop using those hacky manual line breaks in your headers. if you're dealing with weirdly short lines in a hero section, just use the property. it keeps the width even so you don't get that one lonely word hanging out on its own line. works great for big display fonts where the rhythm matters.

h1 {text-wrap: balance;}


tbh it's a lifesaver when you don't want to manually tweak every single breakpoint. just don't use it on huge blocks of body text or your browser will crawl. keeps the typographic rhythm much cleaner without all the extra work

21a53 No.2293

>>2272
I spent way too long messing with tags on a landing page last week because I couldn't get the hero text to look right. Does this property work okay if the font size is massive?

21a53 No.2294

>>2293
it's fine for massive fonts as long as you aren't trying to balance a whole paragraph at once. i used it on a client site yesterday for an h1 and the performance hit was basically zero. just don't overdo it on smaller subheaders or you'll end up with weirdly centered-looking lines that ruin the left alignment.

21a53 No.2306

File: 1791667686781.jpg (418.56 KB, 1024x1024, img_1791667670476_6wyu91hp.jpg)ImgOps Exif Google Yandex

>>2294
did you check the layout on safari? i've seen it act weird with 'text-wrap: balance' when the container has a fixed width and some padding.



File: 1791378670163.jpg (157.35 KB, 1024x1024, img_1791378660510_1glc1d13.jpg)ImgOps Exif Google Yandex

e8e19 No.2281[Reply]

the matte black jars and that sharp serif font for artah are working. it's way better than those generic pharmacy vibes everyone uses. i like how they used the thick white paperboard with glossy embossing to make it feel expensive instead of just medical. the high-contrast typography makes the ingredient lists much easier to scan on a crowded shelf. still wondering if that monochrome palette is going to get lost once it's surrounded by all the colorful junk in boots stores. hope the embossed text doesn't smudge during shipping do you think this kind of heavy tactile stuff scales well for digital?

link: https://abduzeedo.com/how-two-times-elliott-reimagined-branding-design-artah/

e8e19 No.2284

>>2281
>hope the embossed text doesn't smudge during shipping
use a high-build uv varnish for the embossing when you're doing small runs, but don't rely on it if you're doing massive high-speed offset jobs.

e8e19 No.2297

>>2281
>>2284 uv varnish is gonna peel off way too fast on those matte black jars. you'd be better off just using a deep deboss and letting the natural texture do the work.

e8e19 No.2305

>>2297 debossing is fine for boutique stuff but it'll look total garbage on a mass production run because of the way the ink bleeds into the indentations.



File: 1791666308777.jpg (143.81 KB, 1024x1024, img_1791666301594_3r3780y6.jpg)ImgOps Exif Google Yandex

7c0ad No.2304[Reply]

i'm tired of manually swapping tokens every time i switch frames. it's way faster to just use 'variable modes' but setting up the initial collection is a total headache. does anyone actually use nested modes or is that just overkill?


File: 1791256430648.jpg (86.52 KB, 1024x1024, img_1791256419259_hpcj19bo.jpg)ImgOps Exif Google Yandex

bb77b No.2273[Reply]

juri zaech is trying to make monospaced type look less like a terminal with these neo-grotesque curves.
>modern typography release proves that code fonts belong in bold display roles
it's got all those fancy opentype features like slashed zeros and case-sensitive punctuation, but i don't know if the 'clean tension' actually works for heavy body copy. seems like it'll just look messy on a low-res screen once you start using the black weight. anyone used pangram pangram fonts in a real production environment yet?

article: https://abduzeedo.com/juri-zaech-unveils-fraktion-mono-typography/

bb77b No.2302

>>2273
>it's got all those fancy opentype features like slashed zeros and case-sensitive punctuation

the slashed zero is just a way to hide bad kerning in the heavy weights. pretty much useless for actual dev work tbh



File: 1791500995607.jpg (216.25 KB, 1024x1024, img_1791500987764_y6fsoblj.jpg)ImgOps Exif Google Yandex

e4c90 No.2288[Reply]

Degrees are basically useless now when you can just use AI or watch tutorials to learn actual building skills. It's getting harder to justify that tuition cost when most students are just competing with youtube anyway.

link: https://webdesignerdepot.com/web-design-schools-have-a-giant-youtube-university-problem-and-ai-just-made-it-worse/

e4c90 No.2292

>>2288
Tutorials are great for learning how to use a specific tool but they don't teach you the underlying logic or design theory. You end up just copying code without understanding why it works. I've seen way too many self-taught devs struggle when a project requires more than just following a step-by-step guide.

e4c90 No.2298

>>2292
>You end up just copying code without understanding why it works.

That's exactly what happens when people treat tutorials like a checklist instead of a lesson. I see this all the time in our audit logs for client sites. They just paste whatever worked in the video and then wonder why the whole thing breaks during a deployment. It makes debugging such a nightmare because there is zero foundation to fall back on. The logic has to be solid or you're just building a house of cards. Are you seeing this more with front-end stuff or is it happening in the back-end too? I'm asking because the dependency issues in modern JS frameworks make it even worse when you don't get the basics.

e4c90 No.2301

>>2298
The deployment thing is too real. I spent three hours last night fixing a CSS mess because some freelancer just copied a flexbox hack from a video without realizing it was breaking the mobile layout for our whole grid. It's like they don't even look at the container properties. YouTube is fine for learning how to use a new library or a weird animation trick, but you really need that deep understanding of how the browser actually renders stuff. I've been playing around with some new devtools experiments lately and it just shows how much goes on under the hood that tutorials skip over entirely. Hard to fix what you can't even see working properly.



File: 1791092158713.jpg (74.44 KB, 1024x1024, img_1791092149349_rtqoajxv.jpg)ImgOps Exif Google Yandex

9fd95 No.2262[Reply]

i've been struggling with how jarring it feels when users toggle dark mode and everything just snaps instantly, so i started using a global transition on the body to make the background and text colors bleed into each other more softly. it works best if you keep the duration short though, because anything longer than 0.4s starts feeling laggy heavy and sluggish for the user.
body {transition: background-color 0.4s ease, color 0.4s ease;}

does anyone else find that animating the actual border colors of inputs during this switch makes the whole interface feel more cohesive?

9fd95 No.2300

>>2262
>anything longer than 0.4s starts feeling laggy
0.4s is way too much time for a transition. i once had a client who insisted on a slow fade and it felt like the site was actually dying.



File: 1791299336122.jpg (245.81 KB, 1024x1024, img_1791299327104_dr1o6i2v.jpg)ImgOps Exif Google Yandex

ba861 No.2276[Reply]

Taking apart twenty-five different books just to use their actual pages in a catalogue seems like a massive headache for production.
>Workers sorted and collated original printed leaves by hand.
The idea of using Tid for the typography is cool, but I can't imagine trying to manage that much physical paper weight variation without everything looking messy.

more here: https://abduzeedo.com/svensk-bokkonst-masterclass-editorial-design/

ba861 No.2282

File: 1791393462418.jpg (105.87 KB, 1024x1024, img_1791393448946_zrvtz0hs.jpg)ImgOps Exif Google Yandex

>>2276
>The idea of using Tid for the typography is cool, but I can't imagine trying to manage that much physical paper weight variation without everything looking messy.

had a client try to do something similar with scanned textures and it broke my z-index logic because the opacity was all over the place

ba861 No.2289

>>2282
>it broke my z-index logic because the opacity was all over the place
lmao i had a dev try to fix that with some crazy blur filter and it just made the whole site look like garbage. op is right about the paper weight too, trying to align those different textures without it looking like a total mess would be a nightmare.

ba861 No.2296

File: 1791609641187.jpg (142.7 KB, 1024x1024, img_1791609626259_ffq5gffc.jpg)ImgOps Exif Google Yandex

>>2276
>I can't imagine trying to manage that much physical paper weight variation without everything looking messy.

try a heavy matte varnish on the thicker sheets if you're printing this. It helps flatten the texture so the light doesn't hit the bumps differently on every page, but it won't work if you're using super glossy stock. Otherwise the whole thing just looks like a pile of scraps.



File: 1791586905817.jpg (167.32 KB, 1024x1024, img_1791586896731_g6ojfqgy.jpg)ImgOps Exif Google Yandex

127e4 No.2295[Reply]

BigCommerce forcing you into a higher tier once sales hit certain limits is going to kill so many small shops. I was just playing around with Webflow for a side project and the lack of transaction fees on the Plus plan sounds way better than dealing with those GMV caps.
>forces stores up a tier once trailing sales pass its plans' limits
It's such a headache when you finally start making money and then suddenly your overhead spikes for no reason.

full read: https://webflowmarketingmain.com/blog/best-ecommerce-website-builders-small-business


File: 1790948781072.jpg (245.46 KB, 1024x1024, img_1790948773419_1uyzo48a.jpg)ImgOps Exif Google Yandex

1d011 No.2254[Reply]

it's wild that webflow mcp is just running GSAP under the hood now for those native animations. i don't know if it'll actually handle the complex stuff without breaking, especially since
>not all GSAP features map one-to-one with Webflow Interaction properties
does anyone think this is actually usable for anything beyond basic hover effects?

found this here: https://webflowmarketingmain.com/blog/interactions-gsap-mcp

1d011 No.2285

>>2254
>not all GSAP features map one-to-one with Webflow Interaction properties

that mapping issue is gonna be a nightmare for anything custom. i tried setting up a scrolltrigger sequence for a client last week and the whole thing just died broke because the timeline offset didn't translate right. definitely not ready for high-end motion work yet.

1d011 No.2287

>>2285
the timeline offset issue sounds exactly like what happened when i tried to port a complex micro-interaction for our mobile onboarding flow. it's super frustrating because even if the basic motion looks okay, the lack of precision in the timing makes the whole experience feel cheap and unpolished to the users. do you think they'll eventually let us inject raw code to bridge that gap?



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 ]