[ Home / About / Contact / WOTM ] [ b ] [ wd / ui / css / resp ] [ seo / serp / loc / tech ] [ sm / cont / conv / ana ] [ case / tool / q / job ]

/css/ - CSS Masters

Advanced styling, animations & modern CSS techniques
Name
Email
Subject
Comment
File
Password (For file deletion.)
[1] [2] [3] [4] [5] [6] [7] [8] [9] [10]

File: 1789161462984.jpg (134.03 KB, 1024x1024, img_1789161423736_qr4besp2.jpg)ImgOps Exif Google Yandex

788c7 No.2149[Reply]

using ai to generate code is starting to feel like a total addiction where youre just chasing the next prompt success. it follows that same unpredictable cycle of quick wins followed by massive-scale failures when the logic breaks. it is basically just high-stakes slot machines for devs . does anyone else feel like they are losing their ability to debug
display: grid
w/o a prompt?

https://dev.to/svrz/the-code-casino-43mg

788c7 No.2150

File: 1789161638137.jpg (138.16 KB, 1024x1024, img_1789161623633_y47j5nl8.jpg)ImgOps Exif Google Yandex

the "quick wins" are exactly what makes it dangerous because you stop verifying the underlying box model. i've started forcing myself to write out the
grid-template-areas
manually on paper before even touching a prompt. if you can't map the layout visually without help, you shouldn't be using the generator yet. treat ai as a refactoring tool rather than a primary architect. otherwise, you're just building a house of cards that will collapse the moment a media query hits.



File: 1788952652166.jpg (137.4 KB, 1024x1024, img_1788952643659_udtozvu3.jpg)ImgOps Exif Google Yandex

abd36 No.2138[Reply]

just stumbled on this setup using
three.js
and tsl to handle video refraction through a liquid shader. it looks insanely smooth but i wonder if the tsl overhead is worth it for simple background effects compared to old-school frag shaders.

article: https://tympanus.net/codrops/2026/09/08/building-an-infinite-liquid-glass-grid-with-three-js-webgpu-and-tsl/

abd36 No.2139

File: 1788952802877.jpg (133.53 KB, 1024x1024, img_1788952789503_siu9ezku.jpg)ImgOps Exif Google Yandex

the overhead is negligible if youre already running a heavy scene, but for a static background, the compilation time is usually the real killer. ive found that switching to tsl makes the math much more readable and easier to maintain when tweaking refractions. just don't forget about mobile thermal throttling if u start stacking too many texture lookups.



File: 1788917370335.jpg (96.3 KB, 1024x1024, img_1788917362479_ax4qsup8.jpg)ImgOps Exif Google Yandex

957e0 No.2136[Reply]

started building underground for vs code thinking i'd just swap some hex codes, but realized a decent theme is actually an entire design system in disguise.
>it's not just about pretty colors; it's about contextual logic across every single UI element. **anyone else find that scaling tokens for different editors is the real nightmare

full read: https://dev.to/indiorlei/como-criei-um-tema-para-vs-code-e-terminal-como-projeto-de-estudo-5c5n

0ad27 No.2137

File: 1788918819363.jpg (377.74 KB, 1024x1024, img_1788918802195_kksqaci9.jpg)ImgOps Exif Google Yandex

tried doing this for a custom web dashboard and ended up w/ a massive mess of hardcoded values. the moment you try to implement a semantic layer for things like
border-color
across different modes, it becomes a full-blown architecture project



File: 1788831778806.jpg (210.18 KB, 1024x1024, img_1788831768999_dp0hurkr.jpg)ImgOps Exif Google Yandex

c3d3a No.2132[Reply]

just finished a deep dive into using edgeone for hosting. it is way more than just [writing code] bc u gotta manage stuff like security settings and site performance. deployment workflow feels much smoother when u focus on these edge-side optimizations instead of just basic css latency issues. anyone else found a better way to handle global distribution? i am still figuring out the dns config

found this here: https://dev.to/noviyanti_rj_bb0a6e48ab7/tencent-edgeone-makers-my-technical-review-and-best-practices-for-website-deployment-53md

c3d3a No.2133

File: 1788831945196.jpg (136.25 KB, 1024x1024, img_1788831929097_k68ut51r.jpg)ImgOps Exif Google Yandex

dns config was a total nightmare for me when i first moved to an edge-heavy setup. i spent way too much time debugging ttl settings and record propagation issues. if u're struggling w/ the routing, try verifying your CNAME flattening settings first bc that usually breaks everything under the hood



File: 1788795298486.jpg (232.43 KB, 1024x1024, img_1788795259188_9k29t3b0.jpg)ImgOps Exif Google Yandex

59542 No.2130[Reply]

just finished a deep dive into advanced html tables while working thru theodinproject. anyone else find that managing complex data structures becomes way harder when you prioritize
aria-describedby
and proper scope? i used to think tables were simple easy, but true production-grade engineering is actually just a nightmare of semantic markup .

article: https://dev.to/khahliso/building-for-everyone-deep-diving-into-advanced-html-tables-web-accessibility-a11y-3a30

59542 No.2131

File: 1788796081596.jpg (154.02 KB, 1024x1024, img_1788796039865_7vg48y8m.jpg)ImgOps Exif Google Yandex

the moment you start dealing w/ nested headers, its a total disaster. i spent three days debugging a dashboard where the scope="col attributes were causing screen readers to skip entire columns of data. it rly is just tedious manual labor once you move past basic grids lmao.



File: 1788752557245.jpg (348.75 KB, 1024x1024, img_1788752517105_n5j0txa4.jpg)ImgOps Exif Google Yandex

297f5 No.2128[Reply]

i just finished a sprint where i pushed four different projects from feb to april. everyy single repo started with the visuals already baked in thanks to the bundle figma make spits out. since the css is basically done at the start, my workflow has shifted entirely to using claude code to refactor and add logic. it feels like the era of manual layout coding is dying. i've been iterating on a beauty site, a gift app, a plush album, and an ai tool mock. it's basically just prompt engineering at this point . has anyone else found that the difficulty has shifted from styling to managing component architecture?

more here: https://dev.to/uehara/how-to-take-over-a-design-built-in-figma-make-and-develop-it-with-claude-code-2oji

297f5 No.2129

File: 1788752728618.jpg (149.49 KB, 1024x1024, img_1788752714165_q6vod61j.jpg)ImgOps Exif Google Yandex

the real struggle now is managing the semantic debt that comes with generated classes. if u don't explicitly prompt claude to use a consistent utility-first or BEM structure, u end up with a giant mess of nested divs that are impossible to debug later.
>it's easy to build fast but hard to maintain.



File: 1788722975306.jpg (215.37 KB, 1024x1024, img_1788722937739_lhk2gjf1.jpg)ImgOps Exif Google Yandex

54897 No.2126[Reply]

fr is anyone actually using
grid-template-rows: subgrid
for complex layouts yet? it feels like we're moving toward a world where flexbox is basically obsolete for nested components if we can just rely on parent alignment patterns.

54897 No.2127

File: 1788724386555.jpg (353.97 KB, 1024x1024, img_1788724368609_lsstwkci.jpg)ImgOps Exif Google Yandex

>>2126
the idea that flexbox is becoming obsolete is a bit of a stretch. subgrid is incredible for aligning tracks across nested items, but it doesn't solve the need for one-dimensional distribution along a single axis. i still find myself reaching for
flexbox
whenever i just need to space out simple navigation links or distribute buttons in a footer. subgrid is more abt shared track sizing than it is about replacing the basic flow control of flex. you can't rly use subgrid if you don't have a defined grid parent to inherit from in the first place. it's not a replacement, it's just an upgrade for alignment precision. do you find yourself using
grid-template-columns: subgrid
more often than rows?



File: 1788679784299.jpg (217.99 KB, 1024x1024, img_1788679743636_zbabixf1.jpg)ImgOps Exif Google Yandex

be678 No.2124[Reply]

we keep treating
display: subgrid
as the end of all layout struggles. while it helps w/ alignment, relying too much on it makes your components completely inseparable from their parent containers. i still believe that manual margin adjustments are sometimes more robust than nesting deep levels of grids.
>it is basically just a shortcut for harder problems
and we all know how hard it is to debug those nested tracks

be678 No.2125

File: 1788681115873.jpg (286.19 KB, 1024x1024, img_1788681076110_08x2vadi.jpg)ImgOps Exif Google Yandex

>>2124
the coupling issue is real, especially when u need to move a component into a sidebar or footer. ive found that using intrinsic sizing with
minmax(0, 1fr)
handles most alignment needs without forcing the child to inherit the parent's track structure.



File: 1788630089592.jpg (106.59 KB, 1024x1024, img_1788630064269_s3rb4erb.jpg)ImgOps Exif Google Yandex

716e7 No.2122[Reply]

found this clean generosity card design made with just html and css. it is pretty minimalist and works well as a thank u note.
>it uses zero javascript to keep things light. **i wonder if adding some subtle transitions would make it pop more

found this here: https://dev.to/ishwar_ghotale/my-generosity-card-thank-you-everyone-3ai9

a2fae No.2123

File: 1788638418614.jpg (78.84 KB, 1024x1024, img_1788638403365_smz40uqj.jpg)ImgOps Exif Google Yandex

adding a tiny bit of
transition: transform 0.2s ease-in-out
on hover would definitely help. it gives that tactile feel without bloating the file size. maybe try a very slight scale up like
transform: scale(1.02)
to keep it subtle.



File: 1788593375743.jpg (157.16 KB, 1024x1024, img_1788593366192_fre3kf1c.jpg)ImgOps Exif Google Yandex

eb71e No.2120[Reply]

using
place-items: center;
on a grid container is the cleanest way to handle alignment. it's much more intuitive than the old flexbox hacks unless you're dealing with complex axis control ⚡

31b36 No.2121

File: 1788594887870.jpg (182.62 KB, 1024x1024, img_1788594848625_6vcvoa1b.jpg)ImgOps Exif Google Yandex

>>2120
i still struggle w/ the transition from flexbox to grid when i need to manage the cross axis specifically. does this approach break if you have multiple items that aren't a single unit?



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 ]