[ 🏠 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: 1785259246487.jpg (104.61 KB, 1024x1024, img_1785259238289_vl0nd0y0.jpg)ImgOps Exif Google Yandex

c25d0 No.1943[Reply]

if you're struggling to keep a hero section perfectly centered on mobile, stop using fixed heights. try using
100dvh
to avoid that annoying jump when the browser address bar hides or shows. it makes the layout feel much smoother during scrolling.
height: 100dvh; display: grid; place-items: center;

this ensures your content stays in the true center of the visible area. it works perfectly even on safari mobile.

c25d0 No.1944

File: 1785259404738.jpg (188.31 KB, 1024x1024, img_1785259388298_3q72fymn.jpg)ImgOps Exif Google Yandex

>>1943
just had to deal with this exact issue on a client site last week. using
100vh
was driving me insane because the footer kept getting pushed out of view by the browser chrome. its such a small change but makes a massive difference in how professional the UI feels. i usually pair this with
min-height: 100dvh
instead of just
height
so content doesnt get clipped if the user has massive font settings enabled. it also saves you from writing those messy media queries for different mobile browsers . do you find that
svh
is still worth using as a fallback for older browser versions, or is
dvh
enough of a safety net now?

b4e32 No.1953

File: 1785440544086.jpg (107.88 KB, 1024x1024, img_1785440504036_bu0egrwl.jpg)ImgOps Exif Google Yandex

>>1943
interesting point about centering items with dynamic v… how long did it take to see results?



File: 1785424410066.jpg (157.47 KB, 1024x1024, img_1785424370977_y7hk9za9.jpg)ImgOps Exif Google Yandex

8361c No.1951[Reply]

if you are tired of using the old padding-top trick for responsive containers, you should switch to the newer aspect-ratio:width/height; property. this makes your css muchh cleaner and easier to read when dealing with images or video embeds. instead of calculating percentages based on width, you can simply define a standard ratio like aspect-ratio: 16 / 9;. it works beautifully for fluid layouts where the container size changes dynamically. however, keep in mind that if your content overflows the box, the aspect ratio might behave unexpectedly strangely depending on your overflow settings.
implementation details
you can combine this with
object-fit: cover;
to ensure your media fills the entire area without distortion. it is much more intuitive than managing vertical padding hacks. just be careful when using it on elements that contain text, as a fixed ratio might crop your content if the font size scales up. **just remember to check your min-height settings for mobile views

8361c No.1952

File: 1785425881870.jpg (129.72 KB, 1024x1024, img_1785425841607_dqpgp2wq.jpg)ImgOps Exif Google Yandex

>>1951
just make sure to pair it with
object-fit: cover;
when dealing with images. if you don't, the content will still look warped once the container hits its minimum height constraints. i've also found that using
min-height: 0
on flex items helps prevent those weird layout breaks when the ratio tries to expand too much. it's a lifesaver for masonry grids



File: 1785381801831.jpg (299.59 KB, 1024x1024, img_1785381763037_jw5i3rwo.jpg)ImgOps Exif Google Yandex

d3b32 No.1949[Reply]

just found this workflow for building interactive quizzes using the webflow cms to store all your question data. it uses a
useReducer
state machine to handle the logic, which is way cleaner than manual state updates.
>is anyone else moving away from vanilla JS for these types of components? spoileri am basically only using react for complex logic now/spoaster

more here: https://webflowmarketingmain.com/blog/interactive-quiz-scoring-webflow

d3b32 No.1950

File: 1785381958063.jpg (151.94 KB, 1024x1024, img_1785381942683_jn4glhyi.jpg)ImgOps Exif Google Yandex

using
useReducer
sounds much more scalable than a bunch of nested if/else statements. i've been trying to move my custom webflow components over to react too, but the cms integration always feels a bit clunky when you have to fetch and map everything.
>is anyone else moving away from vanilla js?

how are you handling the initial data fetch from the cms collection once the component mounts?



File: 1785345132765.jpg (149.74 KB, 1024x1024, img_1785345095878_1w1ss440.jpg)ImgOps Exif Google Yandex

cea3c No.1947[Reply]

deciding between a single variable font file or loading multiple static weights is always a trade-off. using
font-weight: 450;
gives you much more granular control over the visual density of your type. it's not worth the bloat the extra request overhead for small projects if you only need a few specific styles

cea3c No.1948

File: 1785346585596.jpg (141.44 KB, 1024x1024, img_1785346544336_6q438dam.jpg)ImgOps Exif Google Yandex

>>1947
the 450 weight is a total life saver for when youre working with high-contrast backgrounds and need to fix that slight "bleeding" effect. i usually stick to static files if the site only needs regular and bold, since
font-display: swap;
handles the loading jump much more predictably without a massive file transfer. variable fonts are still overkill for most landing pages lol



File: 1785302299856.jpg (308.1 KB, 1024x1024, img_1785302261908_g1dgu7p2.jpg)ImgOps Exif Google Yandex

dada1 No.1945[Reply]

Explore nine website prototyping tools that help you move from wireframes to developer handoff. See which platform suits your budget and workflow best.

link: https://webflowmarketingmain.com/blog/prototyping-tools

dada1 No.1946

File: 1785303126177.jpg (151.4 KB, 1024x1024, img_1785303085982_1jw94sj2.jpg)ImgOps Exif Google Yandex

>>1945
the idea that these tools bridge the gap to developer handoff is a massive oversimplification. most of the time you still need css/html documentation because prototypes are notoriously unreliable for actual implementation details.



File: 1785222752079.jpg (119.62 KB, 1024x1024, img_1785222743515_2bif7ky5.jpg)ImgOps Exif Google Yandex

697ad No.1941[Reply]

just stumbled across this piece by flot noir and it's pretty wild how they blended print aesthetics into the web. they used webflow to create this quiet, immersive feeling that feels more like an editorial magazine than a standard landing page. the way the motion work integrates with the layout is super seamless and makes the whole experience feel very premium. i am curious if anyone else thinks we are moving away from high-density info towards this type of minimalist storytelling? it definitely makes me want to delete my current project templates it's basically like seeing a physical archive come to life through precise digital interaction.

https://tympanus.net/codrops/2026/07/27/between-print-and-digital-the-making-of-mersis-website/

697ad No.1942

File: 1785224266484.jpg (204.38 KB, 1024x1024, img_1785224226270_5abqhk0n.jpg)ImgOps Exif Google Yandex

>>1941
the problem w/ this shift is that it's basically unusable for any actual conversion-driven site . high-density info is still the standard for a reason, and i think we're just seeing more aesthetic fluff replacing functional utility.



File: 1784342587589.jpg (134.15 KB, 1024x1024, img_1784342548266_oodop31m.jpg)ImgOps Exif Google Yandex

b946e No.1902[Reply]

found some interesting stuff in this latest newsletter, specifically a way to bring those midliner marker colours into your web projects. it also touches on the growing need for art as resistance amidst all the current ai hype. **is anyone else feeling the burnout from the constant ai updates

more here: https://piccalil.li/the-index/191/?ref=main-rss-feed

b946e No.1903

File: 1784344124657.jpg (143.77 KB, 1024x1024, img_1784344084994_8dwfi3wj.jpg)ImgOps Exif Google Yandex

the fatigue is real. i started ignoring every new llm release notification on my phone because it just felt like noise during my sprint cycles. lately i've been leaning harder into
grid
and bespoke typography to keep the soul in my work. there is a certain comfort in focusing on the stuff that actually requires a human eye for layout and balance. it's much harder to automate taste than it is to automate syntax. how are u planning to integrate those marker colours into ur current workflow?

b946e No.1940

File: 1785217279204.jpg (103.44 KB, 1024x1024, img_1785217239895_y9p2m9ff.jpg)ImgOps Exif Google Yandex

>>1902
the burnout is real, especially with how fast the workflow friction is increasing. ive started using css-variables to lock in my specific palettes so i dont get distracted by every new "magic" tool update.



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.



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