/wd/ - Web Design

everything is starting to feel like a closed loop btwn massive gatekeepers, paywalls, and all this AI slop flooding search results. its getting harder to find smth authentic when google just feeds you snippets and apple is busy suing openai. **is anyone even bothering w/ seo anymore

link: https://www.nearmedia.co/future-of-websites-review-abstracts-search-shift-apple-sues-openai/

fr everyy recent high-end portfolio seems to be moving away from smooth transitions and back toward raw, unpolished grids. it feels like the industry is finally rejecting the era of overly polished glassmorphism in favor of smth more tangible .
>everything looks too much like a template lately.

everyone seems to be stuck using the same modular box layouts lately. it feels like we are losing the ability to create organic flow in much of our modern web typography. i miss seeing variable fonts used for more than just weight adjustments, especially when they could define the entire hierarchy.
>grid systems should facilitate movement, not cage it.
maybe we should stop relying on css grid for every single section and experiment with more fluid, layered compositions again. what is your take on this trend toward extreme structure?

found a list of 10 platforms that are actually worth checking out for new clients and steady work. most of them are totally saturated but some are still gold. anyone else finding success on smth other than the usual suspects?

article: https://webflowmarketingmain.com/blog/freelance-websites

fr just stumbled onto this study that looked at 2,000 websites and the results are pretty wild. most sites are basically invisible to answer engines bc they aren't optimized for llms yet. it turns out winning at aeo isn't just about technical seo anymore; it's becoming a massive team sport involving content and dev. it's basically the new era of search marketing . i wonder if we should even bother w/ traditional meta descriptions if the ai is just scraping the whole page anyway. ~~is anyone actually updating their schema for this yet

link: https://webflowmarketingmain.com/blog/aeo-maturity-index

lowkey found this 8-step guide on how to move from random gigs to building a real brand . does anyone else think the transition to retainers is the only way to survive right now?

found this here: https://webflowmarketingmain.com/blog/how-to-start-a-web-design-business

just stumbled onto this new css-tricks update covering some wild stuff like boundary-aware css and time-based layouts. the bit about accessible grid lanes being a game changer is definitely worth a read if you are tired of clunky messy layouts. does anyone else think full-bleed designs are becoming the new standard for every single project?

found this here: https://css-tricks.com/whats-important-15/

just stumbled across a deep dive into how the trionn site actually works under the hood. it is pretty wild seeing how they managed to sync up gsap, three. js, lenis, and web audio without everything turning into a laggy mess. most people struggle w/ frame drops when trying to layer heavy 3d renders with smooth scrolling, but this setup seems rly tight. the way they unified all those different animation layers into one cohesive experience is masterclass level work. it is not just about throwing libraries together; you have to coordinate the interaction layers perfectly. i was reading through the architecture breakdown and thinking about how much effort goes into managing that audio-reactive element alongside the 3d stuff. it makes me wonder if anyone has found a better way to handle

requestAnimationFrame

when dealing with such high-density motion. does anyone else find that integrating lenis with three. js always ends up breaking my scroll physics? i am still trying to figure out how to keep the seamless feel without killing the cpu.

https://tympanus.net/codrops/2026/07/15/the-architecture-behind-trionn-coordinating-gsap-three-js-lenis-and-web-audio/

use

text-align: center;

inside a block element to align inline children. it works for simple layouts if you don't need complex alignment logic

choosing between variable fonts and traditional static font files is a massive debate for modern layouts. using a single file with unlimited weight sliders saves on http requests, but u lose some fine-grained control over specific pixel-perfect glyphs. static families are much easier to manage when u need extreme precision across different viewport sizes.
>static weights are safer for accessibility audits
some people argue that the performance gains of variable fonts are mostly negligible on modern fiber connections . if you aren't animating weight transitions, sticking to a few standard weights might be the smarter move. just check ur

font-weight: 450;

implementation before committing to a heavy file. ➡