One Library to Rule Them All: Creating a shared component library

Is it possible to create a component library that would work for multiple installations? An example use case would be setting up a design system online at design.site.com where the component library lived, but changes to that library not only updating the components on that installation, but also on site.com (and theoretically other installations). Would this have to be done with a multisite setup, or is there another way to wire components between different Cornerstone installations?

How is ThemeCo’s cloud library maintained and connected? Is there a possible solution there?

2 Likes

Hello @bobbyoliveri,

Thanks for writing to us.

You can export it as a template and then import the template file to your different installation using the template manager. In case you have not seen the template document please have a look at it.

Hope it helps
Thanks

I think that manual process is what he’s trying to avoid. A centrally managed asset library has been talked about before, and the devs were positive about the idea.

Check out these threads:

Hey @JvP

Thanks for chiming in. The enhanced design cloud is not yet on our roadmap, I’ll bump the feature request tracker so that our development team can check on it.

1 Like

Thanks @marc_a

This is very much on our radar, especially as it relates to our AI project which is well underway.

4 Likes

That’s great news, thanks @kyle!

Hi @JvP,

You are most welcome.

This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.