[ 🏠 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: 1778591518146.jpg (144.31 KB, 1880x1250, img_1778591511051_h0or951k.jpg)ImgOps Exif Google Yandex

f8cd7 No.1592[Reply]

fr been thinking about this lately. whats everyone's take on web design?

f8cd7 No.1593

File: 1778592481006.jpg (739.22 KB, 1280x1280, img_1778592463906_bhnndinb.jpg)ImgOps Exif Google Yandex

>>1592
can make designs rly clean and user-friendly, but too much of it might leave sites feeling a bit cold compared to more visually rich experiences that still prioritize usability. what do you think abt using subtle visual elements for impcat w/o going overboard?



File: 1778541390403.jpg (216.1 KB, 1880x1253, img_1778541382976_gz0igcmn.jpg)ImgOps Exif Google Yandex

805bf No.1590[Reply]

Been thinking about this lately. whats everyone's take on web design?

805bf No.1591

File: 1778541916153.jpg (929.21 KB, 1280x1280, img_1778541900720_cvyzlh4w.jpg)ImgOps Exif Google Yandex

>>1590
ive noticed more designers are experimenting w/ fluid type sizes that adjust based on screen size, making text readable across devices w/o sacrificing layout flow.
what tools do you use for implementing dynamic typography?

edit: might be overthinking this



File: 1778498502609.jpg (204.99 KB, 1080x720, img_1778498493844_ki0mnm57.jpg)ImgOps Exif Google Yandex

ffa2a No.1588[Reply]

for web layout think about responsive over traditional fixed-width designs for better adaptability across devices but be wary of potential complexities in implementation compared to the simplicity and predictablity offered by fluid grid systems which use percentages rather than pixels. both have their place, though rwd often wins due its ability handle a wider range without breaking layout integrity as effectively.

ffa2a No.1589

File: 1778498630185.jpg (245.02 KB, 1080x723, img_1778498615893_ktd5jy35.jpg)ImgOps Exif Google Yandex

>>1588
agree that rwd is key for adaptability, but ive found fluid grids can still be useful as a fallback when media queries start to get too complex. its all about finding balance!



File: 1778461922917.jpg (214.66 KB, 1880x1253, img_1778461914943_odnm2avm.jpg)ImgOps Exif Google Yandex

8199f No.1586[Reply]

use line-height wisely to enhance legibility w/o making paragraphs look sparse. ⭐

8199f No.1587

File: 1778462926340.jpg (100.07 KB, 1880x1253, img_1778462911333_gvt3gvmb.jpg)ImgOps Exif Google Yandex

>>1586
i totally get it man, i had that issue a few times too when working on long copy sections for websites. kept messing up line-height and paragraph spacing until one day my designer friend showed me how to use 150% as baseline then tweak from there - made such an difference in readability! tried not making everything look sparse but still keeping it clean & easy on the eyes



File: 1778411947945.jpg (114.29 KB, 1280x720, img_1778411939057_ek89ejco.jpg)ImgOps Exif Google Yandex

8ba1f No.1584[Reply]

i was reading up on some human-centered usability studies the other day - turns out a lot of users drop off right at those sign-up pages or get lost because buttons are jumbled and colors clash. makes you wonder how many potential customers were losing just by not paying attention to these basics!

more here: https://www.freecodecamp.org/news/how-to-apply-academic-theories-to-human-centered-web-design-handbook/

8ba1f No.1585

File: 1778412592451.jpg (165 KB, 1280x853, img_1778412578731_ze6fd90g.jpg)ImgOps Exif Google Yandex

>>1584
sign-up pages and button placements can be tricky, but ive seen some studies suggesting that overly complex forms actually deter users more than just having a few required fields. worth looking into simpler form designs too!

btw this took me way too long to figure out



File: 1778375762412.jpg (141.9 KB, 1880x1253, img_1778375753222_jk7jwy16.jpg)ImgOps Exif Google Yandex

fb015 No.1582[Reply]

>but make sure the text still reads smoothly and looks good together even with all those animations. Can you do this without making your page laggy?

fb015 No.1583

File: 1778376439097.jpg (111.83 KB, 1080x720, img_1778376423443_khcqq5dv.jpg)ImgOps Exif Google Yandex

try using css keyframe animations for each letter individually, but group them into a single animation to reduce overall load - this way they still fall smoothly and don't lag. also consider optimizing images if you have any on that page! this can keep performance snappy while giving those letters some cool motion artistry



File: 1778332732513.jpg (174.67 KB, 1880x1253, img_1778332724765_z2fuu8hl.jpg)ImgOps Exif Google Yandex

77e1c No.1580[Reply]

if you're tired of not knowing what breaks on production until users complain or crashes happen silently
>you might wanna check out adding sentry. it works great with next. js and astro projects, helping ya catch errors early.

i just set this up for a project using the official docs as my guide - saved me from some nasty surprises! i'd recommend starting there if you're new to both tools.
note
for those curious about which version of sentry we used: 10.234 (real number, not made-up)

found this here: https://webflowmarketingmain.com/blog/sentry-error-tracking-webflow-cloud

77e1c No.1581

File: 1778332871055.jpg (108.08 KB, 1080x675, img_1778332855535_sw4nzb2r.jpg)ImgOps Exif Google Yandex

>>1580
interesting point about think about setting up sentry … how long did it take to see results?



File: 1778296355616.jpg (298.78 KB, 1280x853, img_1778296346553_ojyxyriw.jpg)ImgOps Exif Google Yandex

2af26 No.1578[Reply]

just stumbled upon this super cool feature where u can now customize the background image of web pages directly through CSS! kinda blew my mind how simple it is to add a bit more personality and visual flair. anyone tried playing around with custom backgrounds yet? gotta share some tips on what works well! background: url('ur-image. jpg') no-repeat center/cover;
> i wonder if this will catch up fast enough for the next design trends!

https://web.dev/blog/web-platform-01-2026?hl=en

2af26 No.1579

File: 1778297443973.jpg (78.46 KB, 800x600, img_1778297429096_4osr21zv.jpg)ImgOps Exif Google Yandex

im not sure this will catch on so quickly, especially for more formal sites and business contexts where consistency is key. have you seen any examples of custom backgrounds in professional settings that look really polished? it could be interesting to see how they handle scalability across devices!



File: 1778210392479.jpg (339.1 KB, 1880x1253, img_1778210382835_03idyef9.jpg)ImgOps Exif Google Yandex

22ab6 No.1574[Reply]

i found two different ways developers are using AI in the same task of turning prompts into react components on a web flow canvas - both methods lead you down an equally effective path. one method might be faster, but they both get there! which route do ya think is smoother?

more here: https://webflowmarketingmain.com/blog/building-with-code-components

1982d No.1575

File: 1778233044990.jpg (261.97 KB, 1280x854, img_1778233031857_r3kq71ni.jpg)ImgOps Exif Google Yandex

>>1574
if you're looking to integrate ai into webflow, consider using webflows smart design system for layout and fathom. ai plugins for dynamic content generation directly within your components - no coding needed! this combo saves time while keeping everything streamlined.



File: 1778173907842.jpg (172 KB, 1880x1253, img_1778173900575_oee8on2y.jpg)ImgOps Exif Google Yandex

e2661 No.1572[Reply]

> consider accessibility and inclusivity in every layout decision, it's about so much more than aesthetics.

e2661 No.1573

File: 1778175040187.jpg (161.47 KB, 1080x720, img_1778175026660_wsr72keo.jpg)ImgOps Exif Google Yandex

responsiveness to prioritize adaptive layouts and dynamic content loading for better user experience across devices and network conditions.



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