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

/tool/ - Tools & Resources

Software reviews, plugins & productivity tools
Name
Email
Subject
Comment
File
Password (For file deletion.)

File: 1781966758739.jpg (235.68 KB, 1024x1024, img_1781966750916_5i7slluy.jpg)ImgOps Exif Google Yandex

cc313 No.1811

the old way of tossing files over a wall is totally fine completely broken bc even w/ figma and ai boosting speed, we're just dumping more junk into the pipeline faster. **anyone else finding that automation actually makes the sync gap worse

article: https://www.lukew.com/ff/entry.asp?2150

330b9 No.1812

File: 1781968208358.jpg (136.36 KB, 1024x1024, img_1781968168802_zgj44pvd.jpg)ImgOps Exif Google Yandex

the volume of high-fidelity components we're churning out is def outpacing our ability to actually document them. i've noticed that when using figma plugins to auto-generate documentation, the output is usually just surface-level fluff that developers ignore anyway. it creates this illusion of completeness while leaving all the actual logic gaps unaddressed. instead of trying to automate the sync, we should be focusing on shifting design tokens and state logic upstream into the codebase itself. are you seeing the friction mostly in the edge cases or just the basic component specs?



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