Currently, Webflow’s Shared Libraries are limited in three crucial ways, causing significant manual overhead in multi-brand template management:
Design Tokens:
No ability to override color and font variables per site without breaking the shared library link.
CMS Components:
Components containing CMS collection wrappers cannot be shared, restricting reusability and centralized updates.
Custom Code & Class Prefixes:
Automatic class prefixes disrupt custom CSS and JS selectors, requiring complex workarounds (attribute selectors or duplicate rules).
Resolving these three limitations would greatly enhance the practicality and scalability of Shared Libraries for agencies and template-based projects.
Julian Ortler
.svg){kind=logo}
https://wishlist.webflow.com/ideas/WEBFLOW-I-33546
I wrote a post with a suggestion that would fix 2 of the 3 points you mentioned in your post. The CMS restriction is another story.
It would also be awesome to be able to use classes you defined in your shared library in your projects. This could be done selecting which classes you'd like to export just like with assets. This way you could build complex style guides and just import them to your new project and have everything ready instantly.
Also, shared libs must be removed before a site can be marked as cloneable in Made in Webflow. I'm totally guessing but there are probably similar limits on Templates, Marketplace Libs, and site transfer ( when a Shared Lib is in use )