"Local" master component that is still a linked component
I have 2 documents:
- a library file/design system
- project file 1
I have imported the assets and components from my library file into the project file. I reuse a particular button (a linked component) many times throughout the project file.
Now when I go to prototype: all instances of the button in the project file should be prototype linked to the same artboard. Because my "master" component is technically the one in the library file, I can't include the prototype link as part of the component. This means I have to set up a separate prototype link for each instance of the button, even though they all go to the same place.
So we had this idea that maybe one instance of the linked asset could be the "local" master - aka it is the master only for the specific file it is in. This would allow all instances of the button to still be linked to the asset in the source file, but also allow you to set up a prototype link on the local master that would apply automatically to each child instance of the component within that same file.
I realize there could be various problems with this - such as clashes between updates made to the linked asset in the source file vs the local master. I think keeping things in this hierarchy would work:
Changes made to the source file master > changes made to the local master > overrides to the local child components
There are probably things I haven't thought of but it's just a thought! Hopefully some of it makes sense. Thanks for reading!