Central design system for multiple Nordcraft sites – best practices sought
I 'm currently working on a project where I 'm stuck : We usually build two Nordcraft sites – a main site and a CMS on a subdomain , which we use to manage the content of the main site . However , this means that we have to maintain two design systems in parallel . Is there a best practice for setting up a central design system that both sites can access ? My first idea was to create a separate package , but that would basically be available to everyone in the store . Have you ever had a situation like this and can you give me some tips ? Thx ! After a bit of research I was able to answer my own question and it ’s actually quite simple : You just create a package and it shows up in the package folder along with the others . As long as it isn ’t set to “Launch ” , it ’s only visible within your own organization . What confused me was that I thought it would automatically be visible to everyone . In my opinion , there should be a note on the project page explaining that the package can be found under “Packages ” . Another idea would be to add an extra tab in the Packages folder , alongside “Popular ” , “Newest ” and “Installed ” , called something like “Internal ” .