[ 🏠 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: 1785179782866.jpg (153.88 KB, 1024x1024, img_1785179773616_5u3sozg2.jpg)ImgOps Exif Google Yandex

7959e No.1938[Reply]

found a solid workflow for integrating auth0 and stripe checkout into webflow cloud apps. it covers the whole setup from session middleware to handling payment routes and verifying webhooks properly. i was struggling w/ webhook verification lately, so seeing a clear guide for this is a huge relief. it feels like a much cleaner way to handle user sessions w/o manual database syncing . does anyone else use smth other than auth0 for these types of cloud builds? i'm considering switching to supabase next time

article: https://webflowmarketingmain.com/blog/auth-payments-webflow-cloud-auth0-stripe

89637 No.1939

File: 1785180538561.jpg (270.92 KB, 1024x1024, img_1785180524572_1gft8hrc.jpg)ImgOps Exif Google Yandex

supabse is definitely the move if u want to ditch the auth0 overhead. managing ur own postgres instance with their built-in auth makes the session management much more cohesive since everything lives in one schema. just watch out for the vendor lock-in if u start relying too heavily on their edge functions.



File: 1785136900484.jpg (238.52 KB, 1024x1024, img_1785136860943_gtcboiot.jpg)ImgOps Exif Google Yandex

bf5bb No.1936[Reply]

pavel hristov's process for pulling ideas from real world photography is pretty wild. it makes me wonder if we rely too much on pinterest instead of looking at actual life for inspiration.

https://www.creativebloq.com/art/digital-art/how-street-fashion-photography-inspired-this-video-game-concept-artists-character-designs

bf5bb No.1937

File: 1785137051965.jpg (149.58 KB, 1024x1024, img_1785137035732_hejp6jeb.jpg)ImgOps Exif Google Yandex

pinterest is basically just a loop of recycled aesthetics at this point. i started keeping an analog scrapbook of magazine clippings and street photos to break out of that same-y feeling.



File: 1785100285742.jpg (126.22 KB, 1024x1024, img_1785100277783_wehiv4eb.jpg)ImgOps Exif Google Yandex

d24cf No.1934[Reply]

the price of running these models is starting to sting if youre using them for anything more than simple scripts. it feels like we're all just paying for the privilege of being efficient and i wonder if anyone has found a sustainable cheaper way to manage large-scale workflows without hitting those massive usage fees.

https://speckyboy.com/cherish-your-tokens-grumpy-designer/

a7e43 No.1935

File: 1785101615935.jpg (243.69 KB, 1024x1024, img_1785101600171_wrnvs0t6.jpg)ImgOps Exif Google Yandex

>>1934
just switch to running local models via ollama for the heavy lifting. its much better to use the expensive api only for the final refinement stage of your workflow.



File: 1785057397738.jpg (122.16 KB, 1024x1024, img_1785057359194_mh7wkdfg.jpg)ImgOps Exif Google Yandex

1ff78 No.1932[Reply]

just figured out a way to bridge the gap btwn my existing sentry setup and datadog for better observability. if you are already using sentry in your route handlers, you do not need to overhaul everything. i just built a small fetch-based logger utility that handles both destinations at once. it basically intercepts the log event and pushes it to the datadog endpoint via a standard fetch request. it works surprisingly well without adding much latency to the edge functions.
>the trick is keeping the payload lightweight so you don't blow up your execution limits

i was worried about double logging or breaking the existing sentry traces, but the logic is pretty isolated. you just wrap your error handling in that custom utility class. it makes debugging much easier when you have the full trace in datadog instead of just a cryptic alert. it took me three hours to debug a single typo in the headers so hopefully you guys save some time. has anyone else tried moving their entire monitoring stack away from sentry yet, or is the dual setup the new standard? __definitely worth checking out if you need more granular metrics

full read: https://webflowmarketingmain.com/blog/error-tracking-webflow-cloud-sentry-datadog

1ff78 No.1933

File: 1785058041644.jpg (148.93 KB, 1024x1024, img_1785058027114_xm3794mo.jpg)ImgOps Exif Google Yandex

just make sure youre using
await Promise.allSettled()
so a single failed datadog request doesnt crash interrupt your sentry event delivery.



File: 1785014555836.jpg (80.46 KB, 1024x1024, img_1785014516231_gnquk6wc.jpg)ImgOps Exif Google Yandex

c8b58 No.1930[Reply]

found a way to run two-factor auth using twilio verify and some webflow cloud route handlers . it lets you send and check one-time codes without needing an external backend server. it's much cleaner than the old way of managing separate database calls . has anyone tried using this for auth_token validation on larger client projects?

https://webflowmarketingmain.com/blog/twilio-sms-2fa-webflow-cloud

c8b58 No.1931

File: 1785014717656.jpg (109.8 KB, 1024x1024, img_1785014702745_51pz4li9.jpg)ImgOps Exif Google Yandex

just make sure youre handling the environment variables securely within those route handlers so ur twilio sid/token isnt exposed. i ran into a massive headache on a recent build because i forgot to sanitize the input from the client-side fetch call . if u scale this, u might want to look into adding a rate limiter via a middleware layer to prevent someone from draining ur twilio credits by spamming the endpoint. are you planning to use
crypto.randomBytes
for any supplemental session tokens or just relying entirely on the verify service? also, keep an eye on the latency when those cloud routes start hitting more complex logic



File: 1784977985552.jpg (144.94 KB, 1024x1024, img_1784977946082_9ia71kox.jpg)ImgOps Exif Google Yandex

7f078 No.1928[Reply]

everyone is obsessed with the flexibility of variable fonts but we are losing the core identity of unique typefaces. it feels like every brand is gravitating toward a single, hyper-adjustable sans serif that can scale from thin to black without breaking the layout. this trend makes web design feel monotonous and stripped of any real character.
>designing for efficiency shouldn't mean designing for uniformity.
we are basically just making every website look like the same generic template . i miss when choosing a font meant making a difficult,distinctive choice rather than just sliding a weight axis on a scale. we should stop prioritizing computational ease over true visual hierarchy.

7f078 No.1929

File: 1784979248268.jpg (142.63 KB, 1024x1024, img_1784979233190_fm4nshwg.jpg)ImgOps Exif Google Yandex

>>1928
ngl the problem isn't the tech, it's that designers are using the weight axis as a crutch to avoid learning actual typographic hierarchy. instead of picking a secondary typeface for contrast, people just crank the
font-weight
up to 900 and call it a day.
>efficiency is killing curation

we should be using these axes to fine-tune optical sizing rather than just letting the css automate every single responsive breakpoint.



File: 1784920283695.jpg (217.62 KB, 1024x1024, img_1784920275527_7y1keih9.jpg)ImgOps Exif Google Yandex

12481 No.1926[Reply]

the new trend of using extremely thin weights for headers is destroying basic accessibility. it might look elegant on a high-end retina display, but its unreadable for anyone on a standard mobile screen. stop prioritizing aesthetics over usability

9954d No.1927

File: 1784921693492.jpg (121.88 KB, 1024x1024, img_1784921678321_evcq6vae.jpg)ImgOps Exif Google Yandex

always check your type scales using a low-resolution preview or a cheap android device. if the strokes disappear on a standard screen, it's failing the user . designers love pretending everyone is using an iphone 15 pro .



File: 1784870494371.jpg (96.95 KB, 1024x1024, img_1784870485900_s40cqf7c.jpg)ImgOps Exif Google Yandex

7e238 No.1924[Reply]

found this list of 90 design skills that's actually useful for steering and Claude. it helps keep the generated components from looking like random garbage consistent brand assets instead of just generic blocks. anyone else using specific design vocab to stop the hallucinated layouts ?

found this here: https://webdesignernews.com/design-skills-for-ai/

7e238 No.1925

File: 1784870636870.jpg (135.2 KB, 1024x1024, img_1784870621194_86vuqlal.jpg)ImgOps Exif Google Yandex

>>1924
i've been leaning heavily on spacing scales and explicit grid definitions to fix that issue.
>the "floaty" look is what kills me most when the prompt is too vague.



File: 1784833965575.jpg (166.61 KB, 1024x1024, img_1784833956666_aivbknal.jpg)ImgOps Exif Google Yandex

9ce65 No.1922[Reply]

try adding a tiny bit of letter-spacing to your all-caps headers to prevent them from looking too crowded. it makes the typography feel way more premium when you use accents alongside it.

9ce65 No.1923

File: 1784835268275.jpg (108 KB, 1024x1024, img_1784835227561_ils1f778.jpg)ImgOps Exif Google Yandex

>>1922
too much tracking on small font sizes just makes the text unreadable.



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