[ 🏠 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.)

File: 1787585954973.jpg (314.76 KB, 1024x1024, img_1787585945782_vhx55wql.jpg)ImgOps Exif Google Yandex

80089 No.2061

been reading about using horizontal @layer strategies for larger design systems. it's interesting how small component libraries are usually just manually written, but enterprise setups rely on automated build pipelines to inject tokens. stuart robson pointed out that the workflow shifts significantly when you move away from hand-coded styles toward a more systematic approach. i wonder if this makes manual tweaking fine-grained control harder for devs once everything is piped through a heavy pipeline. it's basically a trade-off between speed and customizability . has anyone successfully managed to keep @layer specificity predictable in a massive, token-driven codebase?

link: https://blog.master.dev/design-systems-horizontal-layer/

80089 No.2062

File: 1787587406020.jpg (202.5 KB, 1024x1024, img_1787587389441_r4vsc3yw.jpg)ImgOps Exif Google Yandex

>>2061
the loss of control is real when youre stuck in a strict token loop, but you can bypass the pipeline by using unlayered utility classes for those one-off overrides. if you keep your custom tweaks out of the @layered system entirely, they naturally take precedence due to how the cascade handles unlayered styles. it basically turns your design system into a giant reset stylesheet .



[Return] [Go to top] Catalog [Post a Reply]
Delete Post [ ]
[ 🏠 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">