Currently, imported libraries become disconnected entities within each Webflow project. This means updates must be applied manually to every project, which is time-consuming and error-prone.

As a Webflow user I believe building components is a great investment. The Webflow libraries are a great tool to share your previously built components like buttons and cards and layouts with other clients and client-projects we work on.

I think libraries need a feature that allows me to not only install libraries across multiple projects, but also add in the ability to change pre-defined values or variables that come with the library.
--

Use case
It would mean that I can install a kickstarter library with a predefined 'rounded corner' variable on all cards for instance. But for this specific project I would change the value to be even rounder than the original. Resetting the overridden variable changes it back to the value that came with the library by default.

Automatic Synchronization changes

• If any changes are accepted in the new project from the library, then it would pull in the new library but keep the overrides in place. Unless of course that pre-defined variable is touched.

• If the variable was overridden in the new project while the library was updated with a deleted variable, then this would mean that the new project would suffer loss of value and so the user is warned.

Benefits

Time Efficiency: Agencies can cooperate to perfect their components used across the projects for clients and develop on them in a centrallized way. Implementing updates across multiple projects in minutes rather than hours.

Consistency: Ensures uniformity in design systems and components across all projects to save re-orienting for new colleagues and helps with building up value long term.

Flexibility: Allows customization per project without losing the benefits of a centralized library built with more functionality in mind.