Move GitLab design library to its own repository to better manage updates
We can move the design library to its own repository to better manage releases, similar to how gitlab-svgs is its own repo. This keeps the gitlab-design repo, which is the source for design compositions, clean of updates to the design library.
Closely tied to this topic, is the topic of Nested Libraries. In this excellent Sketch Together video, Pablo Stanley talks about how to nest Libraries. Doing so allows us to split things like colors and components into different Sketch files and then reference symbols across those files. If we make an update to a symbol in one of the files, it is propagated to the other files that reference that symbol.
This can help us maintain the design library with smaller updates to individual files.
How exactly the design library can be split is up for discussion. The smaller the library, the smaller updates we can do. But we must be conscious in avoiding over-fragmentation of the library into many small pieces.
Currently, this issue is blocked. Moving the pattern library sketch file to its own repository would currently mean another repository to keep up to date when working in the current project. This is due to the fact that we still often have to copy elements over from either the main "pattern library" file or the "instance sheet" due to the nature of sketch symbols.
Until sketch will support opening emote sketch files directly in Sketch this move would not mean additional unnecessary work.
Additionally, we have a PoC that shows off being able to directly add a remote sketch library from a custom URL. This is described in the following comment #136 (comment 88351558) and can be found at https://gitlab.com/dimitrieh/sketch-library-demo